
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Inf ormation. Page 27 of 62
You can still use the existing file-system naming scheme, but you need to determine the role of the switch (active or
standby) before you access the file systems.
Reloading the Cisco Virtual Switching System and Its Members
It may sometimes be desirable to reload the entire system or to reset individual members of the Virtual Switching
System; you can perform these tasks through the console of the active virtual switch.
Reloading the Cisco Virtual Switching System
If you need to reload the entire Cisco Virtual Switching System (both active virtual switch and standby virtual switch),
the following command achieves this reload:
vss#reload
Proceed with reload? [confirm]
Reloading a Member of the Cisco Virtual Switching System
It may be more desirable to reload a member of the Cisco Virtual Switching System rather than the entire system.
You can accomplish this reloading in multiple ways.
You can reset the active virtual switch in two ways. First, you can issue the command redundancy force-switchover,
which essentially forces a SSO or RPR switchover from active to standby, reloading the previous active virtual switch
in the process:
vss#redundancy force-switchover
This will reload the active unit and force switchover to standby[confirm]
Preparing for switchover..
You can also use the redundancy reload shelf command, where either switch 1 or switch 2 can be specified:
vss#redundancy reload shelf 1
Reload this shelf [confirm]
You also have two options to reset the standby virtual switch. First, you can use the same command as before,
replacing the switch ID with the switch ID of the standby virtual switch:
vss#redundancy reload shelf 1
Reload the entire remote shelf[confirm]
Preparing to reload remote shelf
Alternatively, use the command redundancy reload peer to reload the standby virtual switch:
vss#redundancy reload peer
Reload peer [confirm]
Preparing to reload peer
Systemwide PFC Mode
Although only PFC3C or PFC3CXL modes are supported with Cisco Virtual Switching System, you can mix these
modules to configure a lowest-common-denominator mode fallback.
In a standalone Cisco Catalyst 6500 system, the supervisor-engine module is the first module initiated in the system.
As a result, a combination of the PFC of the supervisor engine as well as the inserted modules in the chassis during
bootup determines the operational mode of the system. If you add a lower-revision module, the module will be
disabled until the system is reloaded.
Comentarios a estos manuales