— Exhibit –{primary:node0}
user@host> show configuration chassis | display inheritance
cluster {
redundancy-group 1 {
node 0 priority 200;
node 1 priority 100;
interface-monitor {
ge-0/0/12 weight 255;
ge-5/0/12 weight 255;
}
}
}
— Exhibit –Click the Exhibit button.
A customer reports that their SRX failover is not working as expected. They expected node1 to
become the primary node for the control plane when interface ge-0/0/12 failed. However, when ge-0/0/12 failed, node0 remained the primary node. They send you the output shown in the exhibit.
What is causing this problem?
A.
The interface-monitor configuration should be applied to redundancy-group 0.
B.
The redundancy-group configuration should include the preempt parameter.
C.
The weight parameter applied to ge-5/0/12 is too high.
D.
The weight parameter applied to ge-0/0/12 is too low.
Answer B is correct, RG 0 is for Routing engine
0
0
is for control plane RG0 so A is correct
0
0
A is correct because node1 is expected to be primary for control plane if ge-0/0/12 goes down
0
0
A is correct, node 0 remains the master for the routing engine and therefore the “control plane”, because the configuration applies to RG1 not RG0. The data plane or the forwarding for RG1 would failover in this instance which might mean nothing for the customer.
0
0