Cisco Cisco 1700 2600 3600 3700 Series VPN Module White Paper

Page 24 of 55

Although not required, it is possible to verify that all modules have been automatically provisioned and their module

types stored in the configuration by issuing the following command on the active virtual switch:

VSS#sh run | begin module provision

module provision switch 1

slot 1 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60
number 2 virtual-slot 17

slot 2 slot-type 148 port-type 60 number 4 virtual-slot 18

slot 3 slot-type 147 port-type 61 number 48 virtual-slot 19

module provision switch 2

slot 1 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60
number 2 virtual-slot 33

slot 2 slot-type 148 port-type 60 number 4 virtual-slot 34

slot 3 slot-type 147 port-type 61 number 48 virtual-slot 35

Modules are provisioned in the configuration to allow for parsing, even if they are not present in the chassis. This

situation occurs when one of the member switches is not yet online but the configuration needs to be parsed.

With the following command you can determine that the Cisco Virtual Switching System is now operating and that

the two switches are acting as a single, logical network node.

VSS#show switch virtual

Switch mode : Virtual Switch

Virtual switch domain number : 100

Local switch number : 1

Local switch operational role: Virtual Switch Active

Peer switch number : 2

Peer switch operational role : Virtual Switch Standby

If the conversion process is performed using software release 12.2(33)SXI3 or newer, it is complete once the two

supervisors reach the SSO Standby Hot redundancy mode. If the conversion is performed using a software release

prior to 12.2(33)SXI3, there is one more critical step to perform in order to finalize the conversion.

Again, this final, critical step is applicable only for a first-time conversion, and only applicable to systems converted

using a software release prior to 12.2(33)SXI3.

During the conversion process, the configuration of the standby virtual switch (in this case, Switch 2) is cleared,

including the configuration of the two VSL interfaces on the switch. If the switch were to reload at this point it would

not have the information available to determine which interfaces to use for VSL communication. Therefore the

configuration for the VSL interfaces on the standby switch must be applied, or merged from the active switch

configuration. In order to facilitate this information to be repopulated again, you must complete Step 4.

Step 4. Finalize the Virtual Switch Conversion

When the standby virtual switch is in SSO hot mode, you must execute the following command to automatically

configure the standby virtual switch configuration on the active virtual switch:

VSS#switch accept mode virtual

This command will bring in all VSL configurations from the standby switch and
populate it into the running configuration.