Some things learned, READ the release notes, don’t assume anything even if you have done it a thousand times before!
#1 (From 5.1.1.1 release notes)
[singlepic id=32 w=320 h=240 mode=web20 float=left]When upgrading a pair of IST Core peer switches, special care must be taken due to SMLT architectural change. Unlike previous upgrades, when moving from pre-5.0.1.0 code to any 5.1.0 or higher code, the IST peer switch operation will be different during the upgrade process. When the first peer switch is upgraded (secondary SSF/CPU first, and then primary SSF/CPU), this switch will go into an ALL port lock state, with the IST_MLT being the only links/ports up and active. The SMLT connected portion of the network will continue to operate on the second IST Core switch, still running the pre-5.0.1.0 image. The user should now wait approximately 5 minutes until the following message is seen on the upgraded 5.1.0 switch:
CPU5 [05/15/08 05:33:55] MLT ERROR SMLT initial table sync is delayed or failed. Please check the peer switch for any partial config errors. All the ports in the switch except IST will remain locked.
The second IST Core peer switch can then be upgraded. When the first switch, now running 5.1.0, sees its IST MLT connection go down, it unlocks all its ports and starts learning and then forwarding traffic. This upgrade process will cause some user traffic impact, even for the SMLT connected portion of the network. The second IST Core switch, after upgrading, should show the following messages in its log. These should be checked to confirm proper upgrade and operation:
CPU5 [06/05/08 05:05:45] MLT INFO SMLT MAC/ARP Sync Requested: CAUTION do not take ANY action with the peer at this time
CPU5 [06/05/08 05:05:46] MLT INFO SMLT MAC /ARP Sync is Complete : Peer can now be used normally
After both IST Core peer switches are upgraded and the network is running ’normally’, it is now recommended to power-cycle (reboot only for single SSF/CPU systems) the one peer switch which was upgraded first so that a complete sync occurs.
After upgrading to 5.1.0 or higher code, the future upgrade process will return to the behavior previously documented. When one IST Core peer switch is upgraded, the SMLT portion of the network will continue operation without user impact on the other IST Core peer. The second IST Core peer switch can then be upgraded in the same manner, resulting in little to no user traffic impact for the SMLT connected portion of the network.
#2
NEVER save a config file when there is a pulled modules, if you do the process will strip out the ports from that module. Then the fun begins…
- Dan Gorham
