Campus and Branch
Campus and Branch

Expert Advice: MC-LAG Configuration Guide to Achieve Zero Down Time

by Recognized Expert on ‎09-16-2016 10:54 AM - edited on ‎09-19-2017 11:01 AM by Administrator Administrator (2,593 Views)

In my earlier blog (Junos High Availability Design Guide) I discussed how to make use of redundant routing engines by configuring features like (GRES, NSR, NSB)  for reducing downtime to the minimum possible level.

 

The real problem is that one RE is active at one time and all PFEs must be connected with the active RE. In case of failure of the primary Routing Engine (RE), the backup RE will take over, and all PFEs will now need to connect to the new primary RE. This scenario can cause momentary disruption of services.

 

MC-LAG (Active-Active) is the correct solution to above described problem as it offers 2 active REs in 2 different devices/ chassis. Read the full solution in my blog here.

'
Comments
Nov 30, 2016
s702

Thank you for taking the tim to put this together. The explenation of the mc-ae id and mc-ae chassis-id was exactly what I was looking for. I couldn't find that identified in any MC-LAG documentation. Thanks!