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?
A.
An SRX Series device will not enter chassis-clustering mode unless the fxp0 and fxp1
interfaces are defined in the configuration.
B.
An SRX Series device will only enter chassis-clustering mode when it finds a peer that is also
configured for chassis-clustering mode.
C.
Cluster ID 0 is not valid for a chassis cluster.
D.
Node ID 0 is not valid for a chassis cluster.
Explanation:
Agree . Answer is C .
Cluster-id numbering can range from 1-15. Configuring a cluster-id of 0 is equivalent to disabling chassis cluster.
0
0
Setting a cluster ID to 0 is equivalent to disabling a cluster. A cluster ID greater than 15 can only be set when the fabric and control link interfaces are connected back-to-back.
Node ID’s can go about 15 when the devices are connected back to back. This is to do with the virtual MAC’s that are created.
https://www.juniper.net/documentation/en_US/junos12.3×48/topics/reference/command-summary/set-chassis-cluster-clusterid-node-reboot.html
0
0