nerdexam
Juniper

JN0-696 · Question #23

Click the Exhibit button. There is an existing chassis cluster connected to the corporate network 192.168.1.0/24. You are asked to connect another department to this VLAN. To achieve this, you add a…

The correct answer is D. user@SRX-3> set chassis cluster cluster-id 2 node 0 reboot. The reth MAC addresses are calculated based on the cluster IDs and two similar cluster IDs in the same network might cause a network impact due to overlapping virtual MAC entries.

Troubleshooting High Availability

Question

Click the Exhibit button. There is an existing chassis cluster connected to the corporate network 192.168.1.0/24. You are asked to connect another department to this VLAN. To achieve this, you add a new chassis cluster to the network. After connecting to the network, the cluster experiences traffic problems. You have verified that the addresses and VLAN IDs are configured correctly. Referring to the exhibit, which configuration would resolve this problem?

Exhibit

JN0-696 question #23 exhibit

Options

  • Auser@SRX-3> set chassis cluster cluster-id 1 node 0 reboot
  • Buser@SRX-3# set chassis cluster redundancy-group 1 node 0 priority 100
  • Cuser@SRX-3# set chassis cluster redundancy-group 1 preempt
  • Duser@SRX-3> set chassis cluster cluster-id 2 node 0 reboot

How the community answered

(34 responses)
  • A
    9% (3)
  • B
    3% (1)
  • C
    15% (5)
  • D
    74% (25)

Explanation

The reth MAC addresses are calculated based on the cluster IDs and two similar cluster IDs in the same network might cause a network impact due to overlapping virtual MAC entries.

Topics

#chassis cluster#cluster ID conflict#redundancy group priority#multi-cluster

Community Discussion

No community discussion yet for this question.

Full JN0-696 Practice