Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring Multichassis Link Aggregation for Layer 3 Multicast Using VRRP

Note: Multichassis Link Aggregation (MC-LAG) is supported on QFX3500 and QFX3600 standalone switches running the original CLI and QFX5100 standalone switches running Enhanced Layer 2 Software (ELS).

There are two methods for enabling Layer 3 multicast functionality across a multichassis link aggregation group (MC-LAG) to control traffic. You can choose either to configure the Virtual Router Redundancy Protocol (VRRP) or synchronize the MAC addresses for the Layer 3 interfaces of the switches participating in the MC-LAG. The procedure to configure VRRP for use in a Layer 3 multicast MC-LAG is included in this example.

Requirements

• Junos OS Release 12.3 or later for the QFX3500 and QFX3600 standalone switches and Junos OS Release 13.2X51-D10 or later for the QFX5100 standalone switches.
• Two QFX3500 or QFX3600 standalone switches, or two QFX5100 standalone switches.

• Configure aggregated Ethernet interfaces on a switch. See Example: Configuring Link Aggregation Between a QFX Series Product and an Aggregation Switch.
• Configure the Link Aggregation Control Protocol (LACP) on aggregated Ethernet interfaces on a switch. See Example: Configuring Link Aggregation with LACP Between a QFX Series Product and an Aggregation Switch.

Overview

In this example, you configure two MC-LAGs across two switches, consisting of two aggregated Ethernet interfaces (ae1 and ae2). To support the MC-LAG, create a third aggregated Ethernet interface (ae0) for the interchassis control link-protection link (ICL-PL). Configure a multichassis protection link for the ICL-PL, the Inter-Chassis Control Protocol (ICCP) for the peers hosting the MC-LAG, and Layer 3 connectivity between MC-LAG peers.

Note: Layer 3 connectivity is required for ICCP.

To complete the configuration, enable VRRP by completing the following steps for each MC-LAG:

1. Create a routed VLAN interface (RVI).
2. Create a VRRP group and assign a virtual IP address that is shared between each switch in the VRRP group.
3. Enable a member of a VRRP group to accept all packets destined for the virtual IP address if it is the master in the VRRP group.
4. Configure Layer 3 connectivity between the VRRP groups.

Topology

The topology used in this example consists of two switches hosting two MC-LAGs—ae1 and ae2. The two switches are connected to a multicast source (Server 1) over the MC-LAG ae1, and a multicast receiver (Server 2) over the MC-LAG ae2. Figure 1 shows the topology of this example.

Figure 1: Configuring a Multichassis LAG for Layer 3 Multicast Using VRRP

Table 1 details the topology used in this configuration example.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them in a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level , and then enter commit from configuration mode.

Note: This example shows how to configure MC-LAG using both the original CLI and Enhanced Layer 2 Software (ELS). In ELS, there are three different statements and one different option from the original CLI: The port-mode statement in the [edit interfaces interface-name unit number family ethernet-switching] hierarchy is not supported. Use the interface-mode statement instead. The vlan statement in the [edit interfaces interface-name] hierarchy is not supported. Use the irb statement instead. The vlan.logical-interface-number hierarchy in the [edit vlans vlan-name l3-interface] option is not supported. Use the irb.logical-interface-number option instead. The service-id statement in the [edit switch-options] hierarchy is required in the ELS CLI.

Configuring MC-LAG for Layer 3 Multicast Using VRRP on Two Switches

Step-by-Step Procedure

1. Configure the number of LAGs on both Switch A and Switch B.
   [edit chassis]user@switch# set aggregated-devices ethernet device-count 3
2. Add member interfaces to the aggregated Ethernet interfaces on both Switch A and Switch B.

   Switch A and Switch B:

   [edit interfaces]user@switch# set xe-0/0/12 ether-options 802.3ad ae0user@switch# set xe-0/0/13 ether-options 802.3ad ae0

   Switch A:

   [edit interfaces]user@switch# set xe-0/0/44 ether-options 802.3ad ae1user@switch# set xe-0/0/45 ether-options 802.3ad ae2

   Switch B:

   [edit interfaces]user@switch# set xe-0/0/46 ether-options 802.3ad ae1user@switch# set xe-0/0/47 ether-options 802.3ad ae2
3. Configure ae0 as the trunk interface between Switch A and Switch B.

   Switch A and Switch B:

   [edit interfaces]user@switch# set ae0 unit 0 family ethernet-switching port-mode trunk

   Switch A and Switch B Using ELS:

   [edit interfaces]user@switch# set ae0 unit 0 family ethernet-switchinginterface-mode trunk
4. Configure ae0 as the multichassis protection link between Switch A and Switch B.

   Switch A:

   [edit]user@switch# set multi-chassis multi-chassis-protection 3.3.3.1 interface ae0

   Switch B:

   [edit]user@switch# set multi-chassis multi-chassis-protection 3.3.3.2 interface ae0

Step-by-Step Procedure

1. Configure the local IP address to be in the ICCP connection on Switch A and Switch B.

   Switch A:

   [edit protocols]user@switch# set iccp local-ip-addr 3.3.3.2

   Switch B:

   [edit protocols]user@switch# set iccp local-ip-addr 3.3.3.1
2. Configure the peer IP address, minimum receive interval, and minimum transmit interval for a Bidirectional Forwarding Detection (BFD) session for ICCP on Switch A and Switch B.

   Switch A:

   [edit protocols]user@switch# set iccp peer 3.3.3.1 liveness-detection minimum-receive-interval 1000user@switch# set iccp peer 3.3.3.1 liveness-detection transmit-interval minimum-interval 1000

   Switch B:

   [edit protocols]user@switch# set iccp peer 3.3.3.2 liveness-detection minimum-receive-interval 1000user@switch# set iccp peer 3.3.3.2 liveness-detection transmit-interval minimum-interval 1000
3. (Optional) Configure the time during which an ICCP connection must succeed between MC-LAG peers on Switch A and Switch B.

   Note: Configuring session establishment hold time helps to establish a faster ICCP connection . The recommended value is 50 seconds.

   Switch A:

   [edit protocols]user@switch# set iccp peer 3.3.3.1 session-establishment-hold-time 50

   Switch B:

   [edit protocols]user@switch# set iccp peer 3.3.3.2 session-establishment-hold-time 50
4. (Optional) Configure the backup IP address to be used for backup liveness detection on both Switch A and Switch B.

   Note: By default, backup liveness detection is not enabled. Configuring a backup IP address helps achieve sub-second traffic loss during an MC-LAG peer reboot.

   Switch A:

   [edit protocols]user@switch# set iccp peer 3.3.3.1 backup-liveness-detection backup-peer-ip 10.207.64.233

   Switch B:

   [edit protocols]user@switch# set iccp peer 3.3.3.2 backup-liveness-detection backup-peer-ip 10.207.64.234
5. Configure Layer 3 connectivity between the MC-LAG peers on both Switch A and Switch B.

   Note: In ELS, use the irb.logical-interface-number instead.

   Switch A and Switch B:

   [edit vlans]user@switch# set v500 vlan-id 500user@switch# set v500 l3-interface vlan.500

   Switch A and Switch B Using ELS:

   [edit vlans]user@switch# set v500 vlan-id 500user@switch# set v500 l3-interface irb.500

   Switch A and Switch B:

   [edit interfaces]user@switch# set ae0 unit 0 family ethernet-switching vlan members v500

   Switch A:

   [edit interfaces]user@switch# set vlan unit 500 family inet address 3.3.3.2/24

   Switch A Using ELS:

   [edit interfaces]user@switch# set irbunit 500 family inet address 3.3.3.2/24

   Switch B:

   [edit interfaces]user@switch# set vlan unit 500 family inet address 3.3.3.1/24

   Switch B Using ELS:

   [edit interfaces]user@switch# set irb unit 500 family inet address 3.3.3.1/24

Step-by-Step Procedure

1. Enable LACP on the MC-LAG interfaces on Switch A and Switch B.

   Note: At least one end needs to be active. The other end can be either active or passive.

   [edit interfaces]user@switch# set ae1 aggregated-ether-options lacp activeuser@switch# set ae2 aggregated-ether-options lacp active
2. Specify the same multichassis aggregated Ethernet identification number for each MC-LAG peer on Switch A and Switch B.
   [edit interfaces]user@switch# set ae1 aggregated-ether-options mc-ae mc-ae-id 3user@switch# set ae2 aggregated-ether-options mc-ae mc-ae-id 4
3. Specify the same service ID on Switch A and Switch B.

   ELS:

   [edit]set switch-options service-id 10
4. Specify a unique chassis ID for the MC-LAG on the MC-LAG peers on Switch A and Switch B.

   Switch A:

   [edit interfaces]user@switch# set ae1 aggregated-ether-options mc-ae chassis-id 0user@switch# set ae2 aggregated-ether-options mc-ae chassis-id 0

   Switch B:

   [edit interfaces]user@switch# set ae1 aggregated-ether-options mc-ae chassis-id 1user@switch# set ae2 aggregated-ether-options mc-ae chassis-id 1
5. Specify the operating mode of the MC-LAGs on both Switch A and Switch B.

   Note: Only active-active mode is supported at this time.

   [edit interfaces]user@switch# set ae1 aggregated-ether-options mc-ae mode active-activeuser@switch# set ae2 aggregated-ether-options mc-ae mode active-active
6. Specify the status control for the MC-LAGs on Switch A and Switch B.

   Note: You must configure status control on both Switch A and Switch B hosting the MC-LAGs. If one peer is in active mode, the other must be in standby mode.

   Switch A:

   [edit interfaces]user@switch# set ae1 aggregated-ether-options mc-ae status-control activeuser@switch# set ae2 aggregated-ether-options mc-ae status-control active

   Switch B:

   [edit interfaces]user@switch# set ae1 aggregated-ether-options mc-ae status-control standbyuser@switch# set ae2 aggregated-ether-options mc-ae status-control standby
7. Specify the number of seconds by which the bring-up of the MC-LAG interfaces should be deferred after you reboot Switch A or Switch B.

   Note: The recommended value for maximum VLAN configuration (for example, 4,000 VLANS) is 240 seconds. If IGMP snooping is enabled on all of the VLANs, the recommended value is 420 seconds.

   [edit interfaces]user@switch# set ae1 aggregated-ether-options mc-ae init-delay-time 420user@switch# set ae2 aggregated-ether-options mc-ae init-delay-time 420
8. Specify the same LACP system ID for each MC-LAG on Switch A and Switch B.
   [edit interfaces]user@switch# set ae1 aggregated-ether-options lacp system-ID 00:01:02:03:04:05user@switch# set ae2 aggregated-ether-options lacp system-ID 00:01:02:03:04:06
9. Specify the same LACP administration key on both Switch A and Switch B.
   [edit interfaces]user@switch# set ae1 aggregated-ether-options lacp admin-key 3user@switch# set ae2 aggregated-ether-options lacp admin-key 3
10. Enable a VLAN for each MC-LAG on Switch A and Switch B.
    [edit vlans]user@switch# set v100 vlan-id 100user@switch# set v200 vlan-id 200
    [edit interfaces]user@switch# set ae1 unit 0 family ethernet-switching vlan members v100user@switch# set ae2 unit 0 family ethernet-switching vlan members v200
11. Configure ae1 and ae2 as trunk interfaces between Switch A and Switch B.
    [edit interfaces]user@switch# set ae1 unit 0 family ethernet-switching port-mode trunk user@switch# set ae2 unit 0 family ethernet-switching port-mode trunk

    ELS:

    [edit interfaces]user@switch# set ae1 unit 0 family ethernet-switching interface-mode trunk user@switch# set ae2 unit 0 family ethernet-switching interface-mode trunk

Step-by-Step Procedure

1. Create a routed VLAN interface (RVI) for each MC-LAG, assign a virtual IP address that is shared between each switch in the VRRP groups, and assign an individual IP address for each switch in the VRRP groups.

   Switch A:

   [edit interfaces]user@switch# set vlan unit 100 family inet address 10.1.1.11/24 vrrp-group 1 virtual-address 10.1.1.1user@switch# set vlan unit 200 family inet address 10.1.1.21/24 vrrp-group 2 virtual-address 10.1.1.2

   Switch A Using ELS:

   [edit interfaces]user@switch# set irb unit 100 family inet address 10.1.1.11/24 vrrp-group 1 virtual-address 10.1.1.1user@switch# set irb unit 200 family inet address 10.1.1.21/24 vrrp-group 2 virtual-address 10.1.1.2

   Switch B:

   [edit interfaces]user@switch# set vlan unit 100 family inet address 10.1.1.10/24 vrrp-group 1 virtual-address 10.1.1.1user@switch# set vlan unit 200 family inet address 10.1.1.20/24 vrrp-group 2 virtual-address 10.1.1.2

   Switch B Using ELS:

   [edit interfaces]user@switch# set irb unit 100 family inet address 10.1.1.10/24 vrrp-group 1 virtual-address 10.1.1.1user@switch# set irb unit 200 family inet address 10.1.1.20/24 vrrp-group 2 virtual-address 10.1.1.2
2. Assign the priority for each switch in the VRRP groups:

   Note: The switch configured with the highest priority is the master.

   Switch A:

   [edit interfaces]user@switch# set vlan unit 100 family inet address 10.1.1.11/24 vrrp-group 1 priority 200user@switch# set vlan unit 200 family inet address 10.1.1.21/24 vrrp-group 2 priority 200

   Switch A Using ELS:

   [edit interfaces]user@switch# set irb unit 100 family inet address 10.1.1.11/24 vrrp-group 1 priority 200user@switch# set irb unit 200 family inet address 10.1.1.21/24 vrrp-group 2 priority 200

   Switch B:

   [edit interfaces]user@switch# set vlan unit 100 family inet address 10.1.1.10/24 vrrp-group 1 priority 150user@switch# set vlan unit 200 family inet address 10.1.1.20/24 vrrp-group 2 priority 150

   Switch B Using ELS:

   [edit interfaces]user@switch# set irb unit 100 family inet address 10.1.1.10/24 vrrp-group 1 priority 150user@switch# set irb unit 200 family inet address 10.1.1.20/24 vrrp-group 2 priority 150
3. Enable the switch to accept all packets destined for the virtual IP address if it is the master in a VRRP group:

   Switch A:

   [edit interfaces]user@switch# set vlan unit 100 family inet address 10.1.1.11/24 vrrp-group 1 accept-datauser@switch# set vlan unit 200 family inet address 10.1.1.21/24 vrrp-group 2 accept-data

   Switch A Using ELS:

   [edit interfaces]user@switch# set irb unit 100 family inet address 10.1.1.11/24 vrrp-group 1 accept-datauser@switch# set irb unit 200 family inet address 10.1.1.21/24 vrrp-group 2 accept-data

   Switch B:

   [edit interfaces]user@switch# set vlan unit 100 family inet address 10.1.1.10/24 vrrp-group 1 accept-datauser@switch# set vlan unit 200 family inet address 10.1.1.20/24 vrrp-group 2 accept-data

   Switch B Using ELS:

   [edit interfaces]user@switch# set irb unit 100 family inet address 10.1.1.10/24 vrrp-group 1 accept-datauser@switch# set irb unit 200 family inet address 10.1.1.20/24 vrrp-group 2 accept-data
4. Configure Layer 3 connectivity between Switch A and Switch B.
   [edit interfaces]user@switch# set v100 l3-interface vlan.100user@switch# set v200 l3-interface vlan.200

   ELS:

   [edit interfaces]user@switch# set v100 l3-interface irb.100user@switch# set v200 l3-interface irb.200

Step-by-Step Procedure

1. Enable IGMP snooping for all VLANs on Switch A and Switch B.
   [edit protocols]user@switch# set igmp-snooping vlan all

Step-by-Step Procedure

1. Configure an OSPF area on Switch A and Switch B.
   [edit protocols ospf]user@switch# set area 0.0.0.0
2. Assign the VLAN interfaces for the MC-LAGs as interfaces to the OSPF area on Switch A and Switch B.
   [edit protocols ospf area 0.0.0.0]user@switch# set interface vlan.100user@switch# set interface vlan.200
3. Configure the minimum receive interval, minimum transmit interval, and transmit interval threshold for a Bidirectional Forwarding Detection (BFD) session for the OSPF interfaces on Switch A and Switch B.

   Note: On a QFX5100 switch, the minimum transmit interval must be 1000 milliseconds or greater. Sub-second timers are not supported in Junos OS 13.2X51-D10 and later. If you configure the minimum transmit interval timer lower than 1000 milliseconds, the state of the MC-LAG can be affected.

   [edit protocols ospf area 0.0.0.0]user@switch# set interface vlan.100 bfd-liveness-detection minimum-receive-interval 700user@switch# set interface vlan.100 bfd-liveness-detection transmit-interval minimum-interval 350user@switch# set interface vlan.100 bfd-liveness-detection transmit-interval threshold 500user@switch# set interface vlan.200 bfd-liveness-detection minimum-receive-interval 700user@switch# set interface vlan.200 bfd-liveness-detection transmit-interval minimum-interval 350user@switch# set interface vlan.200 bfd-liveness-detection transmit-interval threshold 500

Step-by-Step Procedure

1. Configure a static rendezvous point (RP) address on Switch A and Switch B.
   [edit protocols pim]user@switch# set rp static address 1.0.0.3
2. Configure the address ranges of the multicast groups for which Switch A and Switch B can be a rendezvous point (RP).
   [edit protocols pim rp static address 1.0.0.3]user@switch# set group-ranges 239.0.0.0/8
3. Enable PIM on the VLAN interfaces for the MC-LAGs on Switch A and Switch B.
   [edit protocols pim]user@switch# set interface vlan.100 dual-druser@switch# set interface vlan.200 dual-dr
4. Configure each PIM interface’s priority for being selected as the designated router (DR).

   An interface with a higher priority value has a higher probability of being selected as the DR.

   Switch A:

   [edit protocols pim]user@switch# set interface vlan.100 priority 200user@switch# set interface vlan.200 priority 600

   Switch B:

   [edit protocols pim]user@switch# set interface vlan.100 priority 100user@switch# set interface vlan.200 priority 500
5. Configure the minimum receive interval, minimum transmit interval, and transmit interval threshold for a Bidirectional Forwarding Detection (BFD) session for the PIM interfaces on Switch A and Switch B.
   [edit protocols pim]user@switch# set interface vlan.100 bfd-liveness-detection minimum-receive-interval 700user@switch# set interface vlan.100 bfd-liveness-detection transmit-interval minimum-interval 350user@switch# set interface vlan.100 bfd-liveness-detection transmit-interval threshold 500user@switch# set interface vlan.200 bfd-liveness-detection minimum-receive-interval 700user@switch# set interface vlan.200 bfd-liveness-detection transmit-interval minimum-interval 350user@switch# set interface vlan.200 bfd-liveness-detection transmit-interval threshold 500

Step-by-Step Procedure

1. Enable RSTP on Switch A.
   [edit protocols rstp]user@switch# set interface ae1.0 mode point-to-point
2. Enable RSTP on Switch B.
   [edit protocols rstp]user@switch# set interface ae1.0 mode point-to-point
3. Disable RSTP on the ICL-PL interfaces on Switch A and Switch B.

   Note: This command does not apply on ELS.

   [edit protocols rstp]user@switch# set interface ae0.0 disable
4. Configure the MC-LAG interfaces as edge ports on Switch A and Switch B.

   Note: The ae1 and ae2 interfaces are downstream interfaces. This is why RSTP and bpdu-block-on-edge need to be configured.

   [edit protocols rstp]user@switch# set interface ae1.0 edgeuser@switch# set interface ae2.0 edge
5. Enable BPDU blocking on all interfaces except for the ICL-PL interfaces on Switch A and Switch B.

   Note: The ae1 and ae2 interfaces are downstream interfaces. This is why RSTP and bpdu-block-on-edge need to be configured.

   [edit protocols rstp]user@switch# set bpdu-block-on-edge

Results

From configuration mode on Switch A, confirm your configuration by entering the show chassis, show interfaces, show multi-chassis, show protocols, and show vlans commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Switch A—Original CLI:

Switch A—ELS

From configuration mode on Switch B, confirm your configuration by entering the show chassis, show interfaces, show multi-chassis, show protocols, and show vlans commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Switch B--Original CLI

Switch B–-ELS

Verification

Verify that the configuration is working properly.

• Verifying That Switch A is the Master Designated Router
• Verifying That Switch B is the Backup Designated Router

Verifying That Switch A is the Master Designated Router

Purpose

Verify that Switch A is the master designated router (DR).

Action

From operational mode, enter the show pim interfaces command.

Stat = Status, V = Version, NbrCnt = Neighbor Count,
S = Sparse, D = Dense, B = Bidirectional,
DR = Designated Router, P2P = Point-to-point link,
Active = Bidirectional is active, NotCap = Not Bidirectional Capable

Name               Stat Mode IP V State        NbrCnt JoinCnt(sg/*g) DR address
pime.32769         Down S     4 2   P2P,NotCap         0 0/0
vlan.100           Up   S     4 2   DDR-DR,NotCap      1 0/0           10.1.1.11
vlan.200           Up   S     4 2   DDR-DR,NotCap      2 0/0           10.1.1.21

Meaning

The DDR-DR state of the VLAN interfaces in the output shows that Switch A is the master designated router.

Verifying That Switch B is the Backup Designated Router

Purpose

Verify that Switch B is the backup designated router (BDR).

Action

From operational mode, enter the show pim interfaces command.

Stat = Status, V = Version, NbrCnt = Neighbor Count,
S = Sparse, D = Dense, B = Bidirectional,
DR = Designated Router, P2P = Point-to-point link,
Active = Bidirectional is active, NotCap = Not Bidirectional Capable

Name               Stat Mode IP V State        NbrCnt JoinCnt(sg/*g) DR address
pime.32769         Down S     4 2   P2P,NotCap         0 0/0
vlan.100           Up   S     4 2   DDR-BDR,NotCap     1 0/0           10.1.1.11
vlan.200           Up   S     4 2   DDR-BDR,NotCap     2 0/0           10.1.1.21

Meaning

The DDR-BDR state of the VLAN interfaces in the output shows that Switch B is the backup designated router.