156-587 · Question #117
What is NOT monitored as a PNOTE by ClusterXL?
The correct answer is D. VPND. VPND (VPN Daemon) is not listed as a standard Critical Device (PNOTE) in the Check Point ClusterXL documentation. While VPN functionality is crucial in many deployments, the specific vpnd process itself is not a PNOTE that directly triggers a cluster failover by default in the…
Question
What is NOT monitored as a PNOTE by ClusterXL?
Options
- ATED
- BPolicy
- CRouteD
- DVPND
How the community answered
(26 responses)- A4% (1)
- B4% (1)
- D92% (24)
Explanation
VPND (VPN Daemon) is not listed as a standard Critical Device (PNOTE) in the Check Point ClusterXL documentation. While VPN functionality is crucial in many deployments, the specific vpnd process itself is not a PNOTE that directly triggers a cluster failover by default in the same way as other core components.
Topics
Community Discussion
6
Bahar F.Jun 3, 2026The answer is D, VPND. ClusterXL uses the PNOTE mechanism to track the health of critical daemons and trigger failover when one of them goes down, and the monitored list includes TED, Policy, and RouteD, but VPND is intentionally excluded. VPN connectivity itself is not what drives a cluster failover decision at the PNOTE level because VPND state is handled through a separate synchronization path rather than the problem-note health check. If you see this framed as "which daemon does NOT cause a failover via PNOTE," the reasoning is the same, VPND failures do not register as a PNOTE condition even though VPN tunnels absolutely depend on cluster health. Keep this one in your notes because Check Point likes to test the boundary between what ClusterXL actively polls versus what it just synchronizes.
Ola B.Jun 6, 2026Good catch on VPND being the odd one out, and worth adding that in some cluster configurations you can actually see VPND state reflected in cphaprob list output without it triggering a failover, which is a solid way to verify this behavior in a lab rather than just memorizing it.
Dejan C.May 26, 2026VPND is not monitored as a PNOTE by ClusterXL because VPN daemon health is tracked through a separate mechanism outside the cluster notification framework. ClusterXL watches TED, Policy sync, and RouteD via PNOTE so it can trigger failover when those critical processes go sideways, but VPND sits outside that scope.
Mei-Ling H.Jun 12, 2026Leaned toward C first, but "PNOTE" does not track VPND, so D.
Ola B.Jun 21, 2026VPND trips people up here because VPN is all over ClusterXL documentation, so you assume it must be watched as a PNOTE process, but go spin up a lab cluster and run cphaprob stat yourself and you will see that TED, Policy, and RouteD all show up as monitored PNOTE processes while VPND does not. The answer is D.
Brenda K.Jun 26, 2026I almost picked C because RouteD feels like the wild card in cluster monitoring, but then I remembered that VPND runs as a separate process outside the ClusterXL PNOTE scope, which is exactly why it is not on that monitored list. Once you lock in that VPND handles VPN tunnels independently, D becomes the only answer you can defend on the clock.