- play_arrow Understanding MC-LAG
- play_arrow Implementing MC-LAG
- play_arrow Other MC-LAG Configurations
- play_arrow Best Practices and Usage Notes
- play_arrow Troubleshooting Multichassis Link Aggregation
- play_arrow Configuration Statements and Operational Commands
MC-LAG Upgrade Guidelines
Upgrade Guidelines
Upgrade the MC-LAG peers according to the following guidelines.
Upgrade both MC-LAG nodes to the same software version in order to achieve no loss during stable and failover conditions. The protocol states, data forwarding, and redundancy are guaranteed only after both nodes are upgraded to the same software version successfully.
After a reboot, the multichassis aggregated Ethernet interfaces come up immediately and might start receiving packets from the server. If routing protocols are enabled, and the routing adjacencies have not been formed, packets might be dropped.
To prevent this scenario, issue the set interfaces interface-name aggregated-ether-options mc-ae init-delay-time time command to set a time by which the routing
adjacencies are formed.
On QFX and EX Series switches, the default session establishment hold time is 300 seconds. However, the session establishment time must be at least 100 seconds higher than the init delay time. You can optionally update the session establishment time to be 340 seconds and the init delay time to be 240 seconds.
Make sure that both of the MC-LAG peers (node1 and node2) are in the active-active state by using the following command on any one of the MC-LAG peers:
content_copy zoom_out_mapuser@switch> show interfaces mc-ae id 1 Member Link : ae0 Current State Machine's State: mcae active state Local Status : active<<<<<<< Local State : up Peer Status : active<<<<<<< Peer State : up Logical Interface : ae0.0 Topology Type : bridge Local State : up Peer State : up Peer Ip/MCP/State : 10.1.1.2 ae2.0 upUpgrade node1 of the MC-LAG.
When node1 is upgraded, it is rebooted, and all traffic is sent across the available LAG interfaces of node2, which is still up. The amount of traffic lost depends on how quickly the neighbor devices detect the link loss and rehash the flows of the LAG.
Verify that node1 is running the software you just installed by issuing the
show versioncommand.Make sure that both nodes of the MC-LAG (node1 and node2) are in the active-active state after the reboot of node1.
Upgrade node2 of the MC-LAG.
Repeat Step 1 through Step 3 to upgrade node2.
