Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring the Network Between the Data Center Core and the Data Center PODs

    The steps required to configure network between the data center core and data center PODs are shown in the following section:

    • Configure MC-LAG on the VDC POD to the Core
    • Configure MC-LAG at Core Switch 1
    • Configure MC-LAG at Core Switch 2
    • Verify the configuration

    To configure the network between the data center core and the data center PODs, follow these steps:

    1. Configure MC-LAG ae0 between VDC-pod1-sw1 to VDC-core-sw1 and VDC-core-sw2.
      1. Enable the Ethernet bundle on the chassis.
        [edit]set chassis node-group NW-NG-0 aggregated-devices ethernet device-count 10Configure the DSCP BA classifier for IPv6.
      2. Configure the AE bundle toward Core-sw1 and Core-sw2 as a single AE bundle in VDC-pod1-sw1.
        [edit]set interfaces NW-NG-0:ae0 description POD1-to-core-MC-LAG-UPLINKset interfaces NW-NG-0:ae0 aggregated-ether-options minimum-links 1set interfaces NW-NG-0:ae0 aggregated-ether-options link-speed 10gset interfaces NW-NG-0:ae0 aggregated-ether-options lacp activeset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching port-mode trunk
      3. Enable all the application VLANs on the POD switches toward the core-switches.
        [edit]set interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members MGMTset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Infraset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Tera-VMset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Security-Mgmtset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Vmotionset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members VM-FTset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Remote-Accessset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Core-transport-1
      4. Configure the member links connected to Core-sw1 and Core-sw2 under the AE bundle.

        Note: n0:xe-0/0/[0-11] is connected to VDC-core-sw1.

        n1:xe-0/0/[0-11] is connected to VDC-core-sw2.

        [edit]set interfaces interface-range MC-LAG-ae0-members member "n0:xe-0/0/[0-11]"set interfaces interface-range MC-LAG-ae0-members member "n1:xe-0/0/[0-11]"set interfaces interface-range MC-LAG-ae0-members description "MC-LAG to Core-sw ae0"set interfaces interface-range MC-LAG-ae0-members ether-options 802.3ad NW-NG-0:ae0
      5. Configure MC-LAG ae0 between VDC-pod1-sw1 to VDC-core-sw1 and VDC-core-sw2 and enable Ethernet bundle on the chassis:
        [edit]set chassis node-group NW-NG-0 aggregated-devices ethernet device-count 10Configure the DSCP BA classifier for IPv6.
      6. Configure the AE bundle toward Core-sw1 and Core-sw2 as a single AE bundle in VDC-pod1-sw1.
        [edit]set interfaces NW-NG-0:ae0 description POD1-to-core-MC-LAG-UPLINKset interfaces NW-NG-0:ae0 aggregated-ether-options minimum-links 1set interfaces NW-NG-0:ae0 aggregated-ether-options link-speed 10gset interfaces NW-NG-0:ae0 aggregated-ether-options lacp activeset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching port-mode trunk
      7. Enable all the applications VLAN on the POD switches toward the core-switches.
        [edit]set interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members MGMTset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Infraset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Tera-VMset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Security-Mgmtset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Vmotionset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members VM-FTset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Remote-Accessset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching vlan members Core-transport-1
      8. Configure the member links connected to Core-sw1 and Core-sw2 under the AE bundle.

      9. [edit]set interfaces interface-range MC-LAG-ae0-members member "n0:xe-0/0/[0-11]"set interfaces interface-range MC-LAG-ae0-members member "n1:xe-0/0/[0-11]"set interfaces interface-range MC-LAG-ae0-members description "MC-LAG to Core-sw ae0"set interfaces interface-range MC-LAG-ae0-members ether-options 802.3ad NW-NG-0:ae0

        Note: n0:xe-0/0/[0-11] is connected to VDC-core-sw1

        n1:xe-0/0/[0-11] is connected to VDC-core-sw2

    2. Configure MC-LAG at VDC-core-sw1 (EX9214-1).
      1. Specify the number of aggregated Ethernet interfaces to be created.
        [edit]set chassis aggregated-devices ethernet device-count 30
      2. Specify the members to be included within the aggregated Ethernet bundle ae0.
        [edit]set interfaces NW-NG-0:ae0 description POD1-to-core-MC-LAG-UPLINKset interfaces NW-NG-0:ae0 aggregated-ether-options minimum-links 1set interfaces NW-NG-0:ae0 aggregated-ether-options link-speed 10gset interfaces NW-NG-0:ae0 aggregated-ether-options lacp activeset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching port-mode trunk
      3. Configure LACP parameters with static system-id and admin-key on the aggregated Ethernet bundle.
        [edit]set interfaces ae0 description "MC-LAG to VDC-pod1-sw1-nng-ae0"set interfaces ae0 aggregated-ether-options lacp activeset interfaces ae0 aggregated-ether-options lacp system-priority 100set interfaces ae0 aggregated-ether-options lacp system-id 00:00:00:00:00:01set interfaces ae0 aggregated-ether-options lacp admin-key 1
      4. Configure MC-AE interface parameters.
        [edit]set interfaces ae0 aggregated-ether-options mc-ae mc-ae-id 1set interfaces ae0 aggregated-ether-options mc-ae redundancy-group 1set interfaces ae0 aggregated-ether-options mc-ae chassis-id 0set interfaces ae0 aggregated-ether-options mc-ae mode active-activeset interfaces ae0 aggregated-ether-options mc-ae status-control activeset interfaces ae0 aggregated-ether-options mc-ae init-delay-time 520set interfaces ae0 aggregated-ether-options mc-ae events iccp-peer-down force-icl-downset interfaces ae0 aggregated-ether-options mc-ae events iccp-peer-down prefer-status-control-activeset interfaces ae0 unit 0 multi-chassis-protection 192.168.168.5 interface ae9.0

        Note: Please review the following caveats and guidelines:

        • The multi-chassis aggregated Ethernet identification number (mc-ae-id) specifies the link aggregation group to which the aggregated Ethernet interface belongs. The ae0 interfaces on VDC-core-sw1 and VDC-core-sw2 are configured with mc-ae-id 1. The ae1 interfaces on VDC-core-sw1 and VDC-core-sw2 are configured with mc-ae-id 2.
        • The redundancy-group 1 statement is used by ICCP to associate multiple chassis that perform similar redundancy functions and to establish a communication channel so that applications on peering chassis can send messages to each other. The ae0 and ae1 interfaces on VDC-core-sw1 and VDC-core-sw2 are configured with the same redundancy group redundancy-group 1.
        • The chassis-id statement is used by LACP for calculating the port number of the MC-LAG's physical member links. VDC-core-sw1 uses chassid-id 0 to identify both its ae0 and ae1 interfaces. VDC-core-sw2uses chassis-id 1 to identify both its ae0 and ae1 and other interfaces.
        • The mode statement indicates whether an MC-LAG is in active-standby mode or active-active mode. Chassis that are in the same group must be in the same mode. Here we have configured active-active.
        • Status-control must be active on one PE and standby on the other node.
        • mc-ae events iccp-peer-down prefer-status-control-active is needed to pre-configure the active node during ICCP failover scenarios. By default one device will be active and other node will be standby
        • To get better convergence on node reboot scenarios, both nodes can be configured as prefer-status-control-active. We have to make sure that the ICCP session goes down due to physical link failures by configuring ICCP peering with the loopback address.
        • mc-ae init-delay-time is configured to be a higher value, which delays the start-up of the MC-AE links during device recovery. This allows the protocol convergence to complete and be ready to forward packets coming from MC-AE to the core-switch.
      5. Configure allowed VLANS on this MC-LAG link.
        [edit]set interfaces ae0 unit 0 family ethernet-switching interface-mode trunkset interfaces ae0 unit 0 family ethernet-switching vlan members MGMTset interfaces ae0 unit 0 family ethernet-switching vlan members Infraset interfaces ae0 unit 0 family ethernet-switching vlan members Tera-VMset interfaces ae0 unit 0 family ethernet-switching vlan members Security-Mgmtset interfaces ae0 unit 0 family ethernet-switching vlan members Vmotionset interfaces ae0 unit 0 family ethernet-switching vlan members VM-FTset interfaces ae0 unit 0 family ethernet-switching vlan members Remote-Accessset interfaces ae0 unit 0 family ethernet-switching vlan members POD1-Transport-1
      6. Configure ae bundle (ae20) connected between the core switches as a Layer 3 link to enable ICCP.
        [edit]set interfaces ae20 vlan-taggingset interfaces ae20 aggregated-ether-options lacp activeset interfaces ae20 unit 0 description " ICCP link between core-sw1 and core-sw2"set interfaces ae20 unit 0 vlan-id 4000set interfaces ae20 unit 0 family inet address 192.168.2.1/30
      7. Configure another ae bundle (ae9) connected between the core switches as a Layer 2 link . This will function as the multi-chassis protection link (ICL-PL) between the core switches.
        [edit]set interfaces ae9 aggregated-ether-options lacp activeset interfaces ae9 aggregated-ether-options lacp periodic fastset interfaces ae9 unit 0 description "ICL Link for all VLANS"set interfaces ae9 unit 0 family ethernet-switching interface-mode trunk
      8. Configure the ICL link members with a hold-time value higher than the configured BFD timer(1s) to have zero loss convergence during recovery of failed devices.
        [edit]set interfaces xe-0/3/6 hold-time up 100set interfaces xe-0/3/6 hold-time down 3000set interfaces xe-0/3/7 hold-time up 100set interfaces xe-0/3/7 hold-time down 3000set interfaces xe-1/3/6 hold-time up 100set interfaces xe-1/3/6 hold-time down 3000set interfaces xe-1/3/7 hold-time up 100set interfaces xe-1/3/7 hold-time down 3000set interfaces xe-3/3/6 hold-time up 100set interfaces xe-3/3/6 hold-time down 3000set interfaces xe-3/3/7 hold-time up 100set interfaces xe-3/3/7 hold-time down 3000set interfaces xe-5/3/6 hold-time up 100set interfaces xe-5/3/6 hold-time down 3000set interfaces xe-5/3/7 hold-time up 100set interfaces xe-5/3/7 hold-time down 3000
      9. Configure allowed VLANs on this bundle.
        [edit]set interfaces ae9 unit 0 family ethernet-switching vlan members Exchangeset interfaces ae9 unit 0 family ethernet-switching vlan members Infraset interfaces ae9 unit 0 family ethernet-switching vlan members SQLset interfaces ae9 unit 0 family ethernet-switching vlan members SharePointset interfaces ae9 unit 0 family ethernet-switching vlan members Firewallset interfaces ae9 unit 0 family ethernet-switching vlan members MGMTset interfaces ae9 unit 0 family ethernet-switching vlan members Wikimediaset interfaces ae9 unit 0 family ethernet-switching vlan members Exchange-Clusterset interfaces ae9 unit 0 family ethernet-switching vlan members Tera-VMset interfaces ae9 unit 0 family ethernet-switching vlan members Load-balancer-Extset interfaces ae9 unit 0 family ethernet-switching vlan members Security-Mgmtset interfaces ae9 unit 0 family ethernet-switching vlan members Vmotionset interfaces ae9 unit 0 family ethernet-switching vlan members VM-FTset interfaces ae9 unit 0 family ethernet-switching vlan members Remote-Accessset interfaces ae9 unit 0 family ethernet-switching vlan members OOB-Transportset interfaces ae9 unit 0 family ethernet-switching vlan members Load-balancer-Ext-Tera-VMset interfaces ae9 unit 0 family ethernet-switching vlan members TrafficGenerator-502set interfaces ae9 unit 0 family ethernet-switching vlan members TrafficGenerator-503set interfaces ae9 unit 0 family ethernet-switching vlan members TrafficGenerator-504set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-1set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-2set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-3set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-4set interfaces ae9 unit 0 family ethernet-switching vlan members POD2-Transport-1set interfaces ae9 unit 0 family ethernet-switching vlan members POD2-Transport-2
      10. Configure IRB on both the core-sw1 and core-sw2 and enable VRRP on the IRBs.
        [edit]set interfaces irb unit 50 family inet address 192.168.50.1/24 arp 192.168.50.2 l2-interface ae9.0set interfaces irb unit 50 family inet address 192.168.50.1/24 arp 192.168.50.2 mac 4c:96:14:68:83:f0set interfaces irb unit 50 family inet address 192.168.50.1/24 arp 192.168.50.2 publishset interfaces irb unit 50 family inet address 192.168.50.1/24 vrrp-group 1 virtual-address 192.168.50.254set interfaces irb unit 50 family inet address 192.168.50.1/24 vrrp-group 1 priority 125set interfaces irb unit 50 family inet address 192.168.50.1/24 vrrp-group 1 fast-interval 100set interfaces irb unit 50 family inet address 192.168.50.1/24 vrrp-group 1 preemptset interfaces irb unit 50 family inet address 192.168.50.1/24 vrrp-group 1 accept-dataset interfaces irb unit 50 family inet address 192.168.50.1/24 vrrp-group 1 authentication-type md5set interfaces irb unit 50 family inet address 192.168.50.1/24 vrrp-group 1 authentication-key "$9$Asx6uRSKvLN-weK4aUDkq"
      11. Configure VLAN and enable “domain-type bridge” to configure IRB as the routing-interface under this bridge domain.
        [edit]set vlans POD1-Transport-1 vlan-id 50set vlans POD1-Transport-1 l3-interface irb.50set vlans POD1-Transport-1 domain-type bridge

        Note: The enhanced Layer 2 software (ELS) CLI doesn’t need an MC-AE interface, ICL under the bridge configuration. It picks the appropriate MC-AE interface from the VLAN association on the configured links.

      12. Configure ICCP protocol parameters.
        [edit]set protocols iccp local-ip-addr 192.168.168.4set protocols iccp peer 192.168.168.5 redundancy-group-id-list 1set protocols iccp peer 192.168.168.5 backup-liveness-detection backup-peer-ip 192.168.168.5set protocols iccp peer 192.168.168.5 liveness-detection minimum-interval 500set protocols iccp peer 192.168.168.5 liveness-detection multiplier 2
      13. Configure the switch service-id for MC-LAG.
        [edit]set switch-options service-id 1

        Note: You must configure the same unique network-wide configuration for a service in the set of PE routers providing the service. This service ID is required if the multi-chassis aggregated Ethernet interfaces are part of a bridge domain.

    3. Configure MC-LAG at VDC-core-sw2 (EX9214-2).
      1. Specify the number of aggregated Ethernet interfaces to be created.
        [edit]set chassis aggregated-devices ethernet device-count 30
      2. Specify the members to be included within the aggregated Ethernet bundle ae0.
        [edit]set interfaces interface-range POD1-MC-LAG-ae0-members member "xe-0/0/[0-7]"set interfaces interface-range POD1-MC-LAG-ae0-members member "xe-0/1/[0-3]"set interfaces interface-range POD1-MC-LAG-ae0-members description "MC-LAG to POD1 ae0"set interfaces interface-range POD1-MC-LAG-ae0-members ether-options 802.3ad ae0
      3. Configure LACP parameters with static system-id and admin-key on the aggregated Ethernet bundle.
        [editset interfaces ae0 description "MC-LAG to VDC-pod1-sw1-nng-ae0"set interfaces ae0 aggregated-ether-options lacp activeset interfaces ae0 aggregated-ether-options lacp system-priority 100set interfaces ae0 aggregated-ether-options lacp system-id 00:00:00:00:00:01set interfaces ae0 aggregated-ether-options lacp admin-key 1
      4. Configure MC-AE interface parameters.
        [edit]set interfaces ae0 aggregated-ether-options mc-ae mc-ae-id 1set interfaces ae0 aggregated-ether-options mc-ae redundancy-group 1set interfaces ae0 aggregated-ether-options mc-ae chassis-id 1set interfaces ae0 aggregated-ether-options mc-ae mode active-activeset interfaces ae0 aggregated-ether-options mc-ae status-control standbyset interfaces ae0 aggregated-ether-options mc-ae init-delay-time 520set interfaces ae0 aggregated-ether-options mc-ae events iccp-peer-down force-icl-downset interfaces ae0 aggregated-ether-options mc-ae events iccp-peer-down prefer-status-control-activeset interfaces ae0 unit 0 multi-chassis-protection 192.168.168.4 interface ae9.0
      5. Configure allowed VLANS on this MC-LAG link.
        [edit]set interfaces ae0 unit 0 family ethernet-switching interface-mode trunkset interfaces ae0 unit 0 family ethernet-switching vlan members MGMTset interfaces ae0 unit 0 family ethernet-switching vlan members Infraset interfaces ae0 unit 0 family ethernet-switching vlan members Tera-VMset interfaces ae0 unit 0 family ethernet-switching vlan members Security-Mgmtset interfaces ae0 unit 0 family ethernet-switching vlan members Vmotionset interfaces ae0 unit 0 family ethernet-switching vlan members VM-FTset interfaces ae0 unit 0 family ethernet-switching vlan members Remote-Accessset interfaces ae0 unit 0 family ethernet-switching vlan members POD1-Transport-1
      6. Configure ae bundle (ae20) connected between the core switches as a Layer 3 link to enable ICCP.
        [edit]set interfaces NW-NG-0:ae0 description POD1-to-core-MC-LAG-UPLINKset interfaces NW-NG-0:ae0 aggregated-ether-options minimum-links 1set interfaces NW-NG-0:ae0 aggregated-ether-options link-speed 10gset interfaces NW-NG-0:ae0 aggregated-ether-options lacp activeset interfaces NW-NG-0:ae0 unit 0 family ethernet-switching port-mode trunk
      7. Configure ae bundle (ae9) connected between the core switches as a Layer 2 link.

        This will function as the multi-chassis protection link between the core switches.

        [edit]set interfaces ae9 aggregated-ether-options lacp activeset interfaces ae9 aggregated-ether-options lacp periodic fastset interfaces ae9 unit 0 description "ICL Link for all VLANS"set interfaces ae9 unit 0 family ethernet-switching interface-mode trunkset interfaces ae9 unit 0 family ethernet-switching vlan members Exchangeset interfaces ae9 unit 0 family ethernet-switching vlan members Infraset interfaces ae9 unit 0 family ethernet-switching vlan members SQLset interfaces ae9 unit 0 family ethernet-switching vlan members SharePointset interfaces ae9 unit 0 family ethernet-switching vlan members Firewallset interfaces ae9 unit 0 family ethernet-switching vlan members MGMTset interfaces ae9 unit 0 family ethernet-switching vlan members Wikimediaset interfaces ae9 unit 0 family ethernet-switching vlan members Exchange-Clusterset interfaces ae9 unit 0 family ethernet-switching vlan members Tera-VMset interfaces ae9 unit 0 family ethernet-switching vlan members Load-balancer-Extset interfaces ae9 unit 0 family ethernet-switching vlan members Security-Mgmtset interfaces ae9 unit 0 family ethernet-switching vlan members Vmotionset interfaces ae9 unit 0 family ethernet-switching vlan members VM-FTset interfaces ae9 unit 0 family ethernet-switching vlan members Remote-Accessset interfaces ae9 unit 0 family ethernet-switching vlan members OOB-Transportset interfaces ae9 unit 0 family ethernet-switching vlan members Load-balancer-Ext-Tera-VMset interfaces ae9 unit 0 family ethernet-switching vlan members TrafficGenerator-502set interfaces ae9 unit 0 family ethernet-switching vlan members TrafficGenerator-503set interfaces ae9 unit 0 family ethernet-switching vlan members TrafficGenerator-504set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-1set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-2set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-3set interfaces ae9 unit 0 family ethernet-switching vlan members POD1-Transport-4set interfaces ae9 unit 0 family ethernet-switching vlan members POD2-Transport-1set interfaces ae9 unit 0 family ethernet-switching vlan members POD2-Transport-2
      8. Configure the ICL link members with a hold-time value higher than the configured BFD timer(1s) to have zero loss convergence during recovery of failed devices.
        [edit]set interfaces xe-0/3/6 hold-time up 100set interfaces xe-0/3/6 hold-time down 3000set interfaces xe-0/3/7 hold-time up 100set interfaces xe-0/3/7 hold-time down 3000set interfaces xe-1/3/6 hold-time up 100set interfaces xe-1/3/6 hold-time down 3000set interfaces xe-1/3/7 hold-time up 100set interfaces xe-1/3/7 hold-time down 3000set interfaces xe-3/3/6 hold-time up 100set interfaces xe-3/3/6 hold-time down 3000set interfaces xe-3/3/7 hold-time up 100set interfaces xe-3/3/7 hold-time down 3000set interfaces xe-5/3/6 hold-time up 100set interfaces xe-5/3/6 hold-time down 3000set interfaces xe-5/3/7 hold-time up 100set interfaces xe-5/3/7 hold-time down 3000
      9. Configure IRB on both the core-sw1 and core-sw2 and enable VRRP.
        [edit]set interfaces irb unit 50 family inet address 192.168.50.2/24 arp 192.168.50.1 l2-interface ae9.0set interfaces irb unit 50 family inet address 192.168.50.2/24 arp 192.168.50.1 mac 4c:96:14:6b:db:f0set interfaces irb unit 50 family inet address 192.168.50.2/24 arp 192.168.50.1 publishset interfaces irb unit 50 family inet address 192.168.50.2/24 vrrp-group 1 virtual-address 192.168.50.254set interfaces irb unit 50 family inet address 192.168.50.2/24 vrrp-group 1 priority 250set interfaces irb unit 50 family inet address 192.168.50.2/24 vrrp-group 1 fast-interval 100set interfaces irb unit 50 family inet address 192.168.50.2/24 vrrp-group 1 preemptset interfaces irb unit 50 family inet address 192.168.50.2/24 vrrp-group 1 accept-dataset interfaces irb unit 50 family inet address 192.168.50.2/24 vrrp-group 1 authentication-type md5set interfaces irb unit 50 family inet address 192.168.50.2/24 vrrp-group 1 authentication-key "$9$Asx6uRSKvLN-weK4aUDkq"
      10. Configure LACP on the AE links.
        [edit]set interfaces ae0 description "MC-LAG to VDC-pod1-sw1-nng-ae0"set interfaces ae0 aggregated-ether-options lacp activeset interfaces ae0 aggregated-ether-options lacp system-priority 100set interfaces ae0 aggregated-ether-options lacp system-id 00:00:00:00:00:01set interfaces ae0 aggregated-ether-options lacp admin-key 1
      11. Configure VLAN and enable “domain-type bridge” to configure IRB as the routing-interface under this bridge domain.
        [edit]set vlans POD1-Transport-1 vlan-id 50set vlans POD1-Transport-1 l3-interface irb.50set vlans POD1-Transport-1 domain-type bridge

        Note: The ELS CLI doesn’t need an MC-AE interface ICL under the bridge configuration. It picks the appropriate MC-AE interface from the VLAN association on the configured links.

      12. Configure ICCP protocol parameters.
        [edit]set protocols iccp local-ip-addr 192.168.168.5set protocols iccp peer 192.168.168.4 redundancy-group-id-list 1set protocols iccp peer 192.168.168.4 backup-liveness-detection backup-peer-ip 192.168.168.4set protocols iccp peer 192.168.168.4 liveness-detection minimum-interval 500set protocols iccp peer 192.168.168.4 liveness-detection multiplier 2
      13. Configure switch service-id for MC-LAG.
        [edit]set switch-options service-id 1

        Note: You must configure the same unique network-wide configuration for a service in the set of PE routers providing the service. This service ID is required if the multi-chassis aggregated Ethernet interfaces are part of a bridge domain.

    Published: 2015-04-20