JN0-696 · Question #22
{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…
The correct answer is A. The interface-monitor configuration should be applied to redundancy-group 0. 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.
Question
{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; } } } 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?
Options
- AThe interface-monitor configuration should be applied to redundancy-group 0.
- BThe redundancy-group configuration should include the preempt parameter.
- CThe weight parameter applied to ge-5/0/12 is too high.
- DThe weight parameter applied to ge-0/0/12 is too low.
How the community answered
(56 responses)- A82% (46)
- B2% (1)
- C7% (4)
- D9% (5)
Explanation
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.
Topics
Community Discussion
No community discussion yet for this question.