nerdexam
Juniper

JN0-696 · Question #36

In preparation for future expansion, a user decides to configure a stand-alone SRX Series device for chassis-clustering mode. The user enters the command set chassis cluster cluster-id 0 node 0…

The correct answer is C. Cluster ID 0 is not valid for a chassis cluster. Cluster-id numbering can range from 1-15. Configuring a cluster-id of 0 is equivalent to disabling chassis cluster. summary/set-chassiscluster-clusterid-node-reboot.html

Troubleshooting High Availability (HA)

Question

In preparation for future expansion, a user decides to configure a stand-alone SRX Series device for chassis-clustering mode. The user enters the command set chassis cluster cluster-id 0 node 0 reboot on the device. After the device reboots, the user sees this output:

user@host> show chassis cluster status error: Chassis cluster is not enabled. user@host> The device does not enter chassis-clustering mode. What is the problem?

Options

  • AAn SRX Series device will not enter chassis-clustering mode unless the fxp0 and fxp1 interfaces
  • BAn SRX Series device will only enter chassis-clustering mode when it finds a peer that is also
  • CCluster ID 0 is not valid for a chassis cluster.
  • DNode ID 0 is not valid for a chassis cluster.

How the community answered

(27 responses)
  • A
    4% (1)
  • B
    7% (2)
  • C
    78% (21)
  • D
    11% (3)

Explanation

Cluster-id numbering can range from 1-15. Configuring a cluster-id of 0 is equivalent to disabling chassis cluster. summary/set-chassiscluster-clusterid-node-reboot.html

Topics

#chassis cluster#cluster-id#HA configuration#clustering mode

Community Discussion

No community discussion yet for this question.

Full JN0-696 Practice