The initial release of the Cisco Virtual Switching System supports only a single supervisor per chassis. If a second, or redundant, supervisor is installed in an individual chassis then the redundant supervisor will not fully boot. The redundant supervisor will stop the boot process at the ROMMON stage.
In this configuration any device connected to the chassis in a single-homed, or single-attach, manner must rely on the availability of the single supervisor. Therefore the recommendation for connecting to the VSS is to always dual-attach devices.
As a result of the single supervisor per chassis support the recovery period for replacing a failed supervisor module is undeterministic in that the recover process requires manual intervention in order to install and initialize a new supervisor in the chassis.
Beginning in the 12.2(33)SXI4 software release, Quad-Sup Uplink Forwarding is supported which allows for a redundant supervisor to fully boot Cisco IOS Software, thereby providing a deterministic recovery option for redundant supervisors in a VSS chassis.
Thanks for your reply. I checked the SX/Y eFSU (ISSU Phase 1) Compatibility Matrix, the status for upgrade from 12.2(33)SXI4a to 12.2(33)SXI12 is "P (Pruned) : The two images are not tested for an eFSU. eFSU upgrade or downgrade is only fully supported between images released within 18-month window"
It make me some confuse.... What is the correct procedule to upgrade the Cay#talyst 6509 VSS IOS ( each chassis with 2 supervisor engine )?
Doing an IOS upgrade of a chassis with dual supervisor card is easy. Doing this on a VSS with dual cards (per chassis) can get mighty confusing.
Before you start doing the below steps it is VERY IMPORTANT you compare the MD5 has value of the IOS found in your TFTP server against the MD5 hash value found in the Cisco website. If they do not match, then you need to download the IOS again and compare. They must match. If they don't match and you put them into your chassis, the supervisor cards will go into ROMmon.
Here's how it's done.
1. Copy the IOS from your TFTP server to your sup-bootdisk: (primary card, primary chassis);
2. Then issue this command: tftp flash sup-bootdisk:IOS.bin
3. Next, copy the IOS from your sup-bootdisk to the redundant supervisor card. I don't remember what the command is but it should be something like this: copy sup-bootdisk:IOS.bin backup-sup-bootdisk:
4. Once that is done, copy the IOS from your sup-bootdisk: to your secondary chassis using the command (again, I am recalling): copy sup-bootdisk:IOS.bin slavesup-bootdisk:
5. Do the same to copy the IOS from the sup-bootdisk: to the secondary chassis' secondary card.
6. Once you've done this, change the bootstatement.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...