vMX
Highlighted
vMX

MC-LAG is not working as expected on vMX of "Juniper cloud labs" devices

‎04-14-2020 07:49 AM

Hi All,

 

I am observing issue in JCL lab vMX router about mc-lag where the same config works fine in physical appliance MX devices.

 

Issue:  "With below config, mc-ae interface is not coming up on one of the device".

 

Here especially in JCL vMX router, why "lacp force-up" command required to bring the AE interface up (for lacp enabled interfaces), but in physicall appliance we will not use "lacp force-up" command to bring the AE interface UP, In appliance once config done and physical interface connected, the AE interface with lacp enabled will bring up automatically without "force-up" command.

 

Kindly suggest why the "mc-ae" interface is not coming up in this case, or any additional config is required to bring the mc-ae interfaces UP.

 

Below is the config i have done for testing on JCL vMX routers (vMX-1 and vMX-2). Also, have attached the config .txt file fyr.

 

vMX-1:

set chassis aggregated-devices ethernet device-count 10
set interfaces ge-0/0/0 gigether-options 802.3ad ae0
set interfaces ge-0/0/6 description "ICCP LINK"
set interfaces ge-0/0/6 unit 0 family inet address 10.100.100.1/30
set interfaces ge-0/0/7 description "ICL LINK"
set interfaces ge-0/0/7 flexible-vlan-tagging
set interfaces ge-0/0/7 encapsulation flexible-ethernet-services
set interfaces ge-0/0/7 unit 0 encapsulation vlan-bridge
set interfaces ge-0/0/7 unit 0 vlan-id-range 10-100
set interfaces ae0 flexible-vlan-tagging
set interfaces ae0 encapsulation flexible-ethernet-services
set interfaces ae0 aggregated-ether-options lacp active
set interfaces ae0 aggregated-ether-options lacp system-priority 100
set interfaces ae0 aggregated-ether-options lacp system-id 00:00:00:00:00:05
set interfaces ae0 aggregated-ether-options lacp admin-key 1
set interfaces ae0 aggregated-ether-options lacp force-up
set interfaces ae0 aggregated-ether-options mc-ae mc-ae-id 5
set interfaces ae0 aggregated-ether-options mc-ae redundancy-group 10
set interfaces ae0 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae0 aggregated-ether-options mc-ae mode active-active
set interfaces ae0 aggregated-ether-options mc-ae status-control active
set interfaces ae0 unit 0 encapsulation vlan-bridge
set interfaces ae0 unit 0 vlan-id-range 10-100
set interfaces ae0 unit 0 multi-chassis-protection 10.100.100.2 interface ge-0/0/7.0
set protocols iccp local-ip-addr 10.100.100.1
set protocols iccp peer 10.100.100.2 redundancy-group-id-list 10
set protocols iccp peer 10.100.100.2 liveness-detection minimum-interval 1000
set bridge-domains bd0 domain-type bridge
set bridge-domains bd0 vlan-id all
set bridge-domains bd0 service-id 20
set bridge-domains bd0 interface ae0.0
set bridge-domains bd0 interface ge-0/0/7.0
set switch-options service-id 10

 

vMX-1 Output status:

jcluser@MX-1# run show iccp

Redundancy Group Information for peer 10.100.100.2
TCP Connection : Established
Liveliness Detection : Up
Redundancy Group ID Status
10 Up

Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: None

Client Application: lacpd
Redundancy Group IDs Joined: 10

 

jcluser@MX-1# run show interfaces mc-ae extensive
Member Link : ae0
Current State Machine's State: mcae active state
Local Status : active
Local State : up
Peer Status : active
Peer State : down
Logical Interface : ae0.0
Topology Type : bridge
Local State : up
Peer State : up
Peer Ip/MCP/State : 10.100.100.2 ge-0/0/7.0 up

MCAE Configuration
Redundancy Group : 10
MCAE ID : 5
MCAE Mode : active_active
Status Control : active
Chassis ID : 1
LACP Configuration
System ID : 00:00:00:00:00:05
Admin Key : 1
LACP Information
Local Partner System ID : 00:00:00:00:00:00
Peer Partner System ID : 00:00:00:00:00:00

 

jcluser@MX-1# run show lacp interfaces
Aggregated interface: ae0
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/0 FUP Actor Yes No Yes Yes Yes Yes Fast Active
ge-0/0/0 FUP Partner No Yes No No Yes Yes Fast Passive
LACP protocol: Receive State Transmit State Mux State
ge-0/0/0 FUP Current Fast periodic Collecting distributing

 

jcluser@MX-1# run show interfaces terse | match ae0
ge-0/0/0.0 up up aenet --> ae0.0
ge-0/0/0.32767 up up aenet --> ae0.32767
ae0 up up
ae0.0 up up bridge
ae0.32767 up up multiservice

 

vMX-2:
set chassis aggregated-devices ethernet device-count 10
set interfaces ge-0/0/0 gigether-options 802.3ad ae0
set interfaces ge-0/0/6 description "ICCP LINK"
set interfaces ge-0/0/6 unit 0 family inet address 10.100.100.2/30
set interfaces ge-0/0/7 description "ICL LINK"
set interfaces ge-0/0/7 flexible-vlan-tagging
set interfaces ge-0/0/7 encapsulation flexible-ethernet-services
set interfaces ge-0/0/7 unit 0 encapsulation vlan-bridge
set interfaces ge-0/0/7 unit 0 vlan-id-range 10-100
set interfaces ae0 flexible-vlan-tagging
set interfaces ae0 encapsulation flexible-ethernet-services
set interfaces ae0 aggregated-ether-options lacp active
set interfaces ae0 aggregated-ether-options lacp system-priority 100
set interfaces ae0 aggregated-ether-options lacp system-id 00:00:00:00:00:05
set interfaces ae0 aggregated-ether-options lacp admin-key 1
set interfaces ae0 aggregated-ether-options lacp force-up
set interfaces ae0 aggregated-ether-options mc-ae mc-ae-id 5
set interfaces ae0 aggregated-ether-options mc-ae redundancy-group 10
set interfaces ae0 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae0 aggregated-ether-options mc-ae mode active-active
set interfaces ae0 aggregated-ether-options mc-ae status-control standby
set interfaces ae0 unit 0 encapsulation vlan-bridge
set interfaces ae0 unit 0 vlan-id-range 10-100
set interfaces ae0 unit 0 multi-chassis-protection 10.100.100.1 interface ge-0/0/7.0
set protocols iccp local-ip-addr 10.100.100.2
set protocols iccp peer 10.100.100.1 redundancy-group-id-list 10
set protocols iccp peer 10.100.100.1 liveness-detection minimum-interval 1000
set bridge-domains bd0 domain-type bridge
set bridge-domains bd0 vlan-id all
set bridge-domains bd0 service-id 20
set bridge-domains bd0 interface ae0.0
set bridge-domains bd0 interface ge-0/0/7.0
set switch-options service-id 10

 

vMX2 output status:

jcluser@MX-2# run show iccp

Redundancy Group Information for peer 10.100.100.1
TCP Connection : Established
Liveliness Detection : Up
Redundancy Group ID Status
10 Up

Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: None

Client Application: lacpd
Redundancy Group IDs Joined: 10

 

jcluser@MX-2# run show interfaces mc-ae extensive
Member Link : ae0
Current State Machine's State: mcae active state
Local Status : active
Local State : down
Peer Status : active
Peer State : up
Logical Interface : ae0.0
Topology Type : bridge
Local State : up
Peer State : up
Peer Ip/MCP/State : 10.100.100.1 ge-0/0/7.0 up

MCAE Configuration
Redundancy Group : 10
MCAE ID : 5
MCAE Mode : active_active
Status Control : standby
Chassis ID : 0
LACP Configuration
System ID : 00:00:00:00:00:05
Admin Key : 1
LACP Information
Local Partner System ID : 00:00:00:00:00:00
Peer Partner System ID : 00:00:00:00:00:00

 

jcluser@MX-2# run show lacp interfaces
Aggregated interface: ae0
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/0 FUP Actor No Yes No No No Yes Fast Passive
ge-0/0/0 FUP Partner No Yes No No No Yes Fast Passive
LACP protocol: Receive State Transmit State Mux State
ge-0/0/0 Current No periodic Attached


jcluser@MX-2# run show interfaces terse | match ae0
ge-0/0/0.0 up up aenet --> ae0.0
ge-0/0/0.32767 up up aenet --> ae0.32767
ae0 up down
ae0.0 up down bridge
ae0.32767 up down multiservice

Attachments

1 REPLY 1
Highlighted
vMX

Re: MC-LAG is not working as expected on vMX of "Juniper cloud labs" devices

‎04-14-2020 08:57 AM

This actually depends on what is connected on the other side, wether they are LACP talkable. If it's a legacy server which most likely not supporting LACP, you need force-up. However, if it's a switch or other devices that support LACP, it should come up even without force-up on your mc-lag side 


Mengzhe Hu
JNCIE x 3 (SP DC ENT)