MCT Hitless Sequential Upgrade
Prior to FastIron 09.0.10a, devices with different software versions were not compatible to form an MCT cluster. This posed a limitation for MCT peers with different software versions to provide the normal forwarding behavior during a software upgrade. To overcome this limitation and achieve MCT hitless upgrade, the MCT protocol version check is introduced in FastIron 09.0.10a. The MCT protocol version check replaces the existing FastIron software release or build string compatibility check. This solution allows two units running FastIron 09.0.10a and later releases to form MCT peers, as long as their MCT protocol versions match and both the peers are from the same model family. In addition to checking the MCT protocol version, the existing platform check will be performed too.
The MCT protocol version will be
incremented whenever there is any enhancement or change in the MCT messages that are
exchanged between the MCT peers. The MCT version starts from version 2, and the version
number is displayed in the show
cluster command output. The MCT hitless upgrade will keep CCP down when
the MCT protocol version check fails.
MCT protocol version can be checked on
cluster peers using the show
cluster command output on 09.0.10a or later releases. The following
example of the show
cluster command output indicates the MCT version is version
2.
device# show cluster Cluster mct_mm_stk 1000, version 2 >>>>>> version 2 represents mct protocol version 2 here. ==================== Rbridge Id: 1019, Session Vlan: 1000, Keep-Alive Vlan: 1999 Cluster State: Deploy Client Isolation Mode: Loose Member Vlan Range: 1001 to 1002 2406 to 2407 3001 to 3150 MCT Peer's Reachability using Keep-Alive Vlan: Peer Reachable ICL Info: --------- Name Port Trunk icl_mm lg1 1 Peer Info: ---------- Peer IP: 11.1.1.2, Peer Rbridge Id: 1029, ICL: icl_mm KeepAlive Interval: 30 , Hold Time: 90, Fast Failover Active Vlan Range: 1001 to 1002 2406 to 2407 3001 to 3150 Last Reason for CCP Down: ICL interface down Peer State: CCP Up (Up Time: 0 days:10 hr:44 min:39 sec) Client Info: Config CCEP Up Delay 300, Oper CCEP Up Delay 0 ------------ Number of Clients configured: 44 Name Rbridge-id Config Port Trunk FSM-State C1 3 Deployed lg3 3 Up C2 4 Deployed lg4 4 Up
In-Service Software Upgrade (ISSU) between minor releases is used for image upgrade of stacking units within the same cluster node. Stack units within the cluster node must be upgraded one after the other to minimize traffic disruption. Refer to the RUCKUS FastIron Software Upgrade Guide for more information on ISSU and upgrading a stack.