Which of the following commands should you run to stop a VSX Gateway Cluster?

Question

Options

• Acphastop
• Bcpstop
• Cvsxstop
• Dvsxhastop
• Evsx cpstop

• B
  96% (26)
• E
  4% (1)

Explanation

cpstop is the correct command because it universally stops all Check Point processes on any gateway type - including VSX Gateway Clusters - by halting the firewall kernel, daemons, and all associated services, regardless of whether the environment uses virtualization or clustering.

Why the distractors are wrong:

• A. cphastop - Stops the High Availability (ClusterXL) daemon only, not the full Check Point stack; used to gracefully remove a node from a cluster, not shut everything down.
• C. vsxstop - Not a valid Check Point command; it does not exist in the CLI.
• D. vsxhastop - Also not a valid Check Point command; fabricated to sound plausible by combining "vsx" and "hastop."
• E. vsx cpstop - Invalid syntax; vsx is a utility that takes its own subcommands (like vsx stat), not a wrapper for cpstop.

Memory tip: "VSX is still Check Point - cpstop stops CP, always." The cp prefix commands (cpstop, cpstart, cpstat) are the authoritative lifecycle commands across all Check Point product types, so a VSX cluster is no exception.

No community discussion yet for this question.