cancel
Showing results for 
Search instead for 
Did you mean: 

MLAG health check message configuration

MLAG health check message configuration

Renne_Stuart
New Contributor
How and where do you configure MLAG health check message config? I have read in the Exos userguide 15_7 that this is now a feature however it does not give to much information on how and where to configure this. Has anyone configured this and had it working? Is this feature available in summitX-15.5.3.4-patch1-5.xos or do i need to upgrade to get this feature?

(page 278 of userguide)
"Starting in ExtremeXOS 15.5, health check messages can also be exchanged on an alternate path byseparate configuration – typically the “Mgmt” VLAN. If the peer is alive when the ISC link alone goes down, one of the MLAG peers disables its MLAG ports to prevent duplicate south-bound traffic to the remote node. To reduce the amount of traffic on the alternate path, health check messages are initiated on the alternate path only when the ISC link goes down. When the ISC link is up, no health check messages are exchanged on the alternate path.

When the MLAG switch misses 3 consecutive health check messages from the peer, it declares that the MLAG peer is not reachable on the ISC link. It then starts sending out health check messages on the alternate path to check if the peer is alive. When the first health check message is received from the MLAG peer on the alternate path, it means that the peer is alive. In this scenario, one of the MLAG peersdisables its MLAG ports to prevent duplication of south-bound traffic to the remote node.

Note
The MLAG switch having the lower IP address for the alternate path VLAN disables its ports.

When the ISC link comes up and the switch starts receiving health check messages on the ISC control VLAN, the ports that were disabled earlier have to be re-enabled. This action is not performed immediately on the receipt of the first health check message on the ISC control VLAN. Instead the switch waits for 2 seconds before enabling the previously disabled ports. This is done to prevent frequent enabling and disabling of MLAG ports due to a faulty ISC link up event.
10 REPLIES 10

StephenW
Extreme Employee
Renne,

15 5 does support this feature.

MLAG relies on the peer communication to prevent duplicate south bound traffic. If the peer communication is down, and both devices are up, traffic can will be duplicated down to both MLAG ports.

The ISC is a single point, that can cause this issue. The alternate path health checks add one more layer of protection. If the MLAG peer connection is down it will check to see if the MLAG alternate IP address is configured. If it is, and working then mlag will disable one side of it's mlag ports to prevent this duplicate traffic.

Where to deploy it: I would deploy it on any other network and connection between the switches, not the MLAG ISC or the ISC vlan. The documentation recommends the management network.

How to configure it:
Just configure both peers pointing to each other on a different network that uses a path that is not the ISC. It's almost like when you configured MLAG the first time.

configure { mlag peer } alternate ipaddress [ { vr } | none]”

Hope this helps.
GTM-P2G8KFN