which configuration would resolve this problem?

— Exhibit –

— Exhibit —

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 –

— Exhibit —

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?

A.
user@SRX-3> set chassis cluster cluster-id 1 node 0 reboot
user@SRX-4> set chassis cluster cluster-id 1 node 1 reboot

B.
user@SRX-3# set chassis cluster redundancy-group 1 node 0 priority 100
user@SRX-3# commit

C.
user@SRX-3# set chassis cluster redundancy-group 1 preempt
user@SRX-3# commit

D.
user@SRX-3> set chassis cluster cluster-id 2 node 0 reboot
user@SRX-4> set chassis cluster cluster-id 2 node 1 reboot

Explanation:

Show Hint

Leave a Reply 2

Your email address will not be published. Required fields are marked *

Fred

Fred

Answer D
Is the Cluster ID the same on both nodes? In order to check the Cluster ID value, connect a console to both nodes. Run the command ‘show chassis cluster status’.

No – Set the Cluster ID on both nodes to the same value. This is a requirement. See note below. Then reboot both devices simultaneously. If this does not resolve the issue, go to Step 7.
Note: If you have more than one Chassis Cluster on the same switch or L2 domain, then each pair of Chassis Cluster nodes must have a different Cluster ID. For example, if there are two pairs of Chassis Cluster nodes connected to the same switch — Juniper_mktg (node0 and node1) is one pair, and Juniper_eng (node 0 and node1) is another pair. Juniper_mktg node0 and node1 may be assigned the Cluster ID of 1. Juniper_mktg node0 and node1 may be assigned the Cluster ID of 2; Juniper_mktg should not be assigned a Cluster ID of 1 because the other pair is using 1. This is because 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.

Reply

JNCSP-MIKE

JNCSP-MIKE

Answer D is correct because of the last statement. The virtual MAC addresses are calculated based on the cluster ID.

Reply