What command would you run to verify the communication between the Security Gateway and the Identity Collector?

Question

Options

• Afw ctl debug -m IDAPI
• Bpdp connections idc
• Cfw ctl debug -m fw + nac
• Dadlog

• A
  5% (1)
• B
  86% (19)
• D
  9% (2)

Explanation

pdp connections idc is the correct command because it directly queries the Policy Decision Point (PDP) - Check Point's identity engine running on the Security Gateway - and displays the live connection status with the Identity Collector (IDC). It gives you a clear view of whether the IDC is connected, authenticated, and actively sending identity data to the gateway.

• A (fw ctl debug -m IDAPI) is a kernel debug flag for the Identity Awareness API; it generates low-level debug output for troubleshooting, not a status check on IDC connectivity.
• C (fw ctl debug -m fw + nac) enables kernel debugging for the firewall and NAC modules - useful for packet-level analysis, but unrelated to Identity Collector communication.
• D (adlog) is used to view AD Query logs and Active Directory identity events; it is not the tool for checking IDC-to-gateway connectivity.

Memory tip: Break it down - pdp = Policy Decision Point (the gateway's identity brain), connections = show me what's connected, idc = Identity Collector. The command reads almost like plain English: "PDP, show me your IDC connections."

No community discussion yet for this question.