3. MARCO TEÓRICO
3.1. Introducción al método del hcm 2010
3.1.3. Datos de entrada necesarios
3.1.3.2. Modos no motorizados
The conversion process requires configuration of both switches that will form part of the Virtual Switch Domain and requires a reboot on the part of both switches during the
conversion…
It is recommended to have the interfaces forming the VSL be connected prior to the conversion process as it will minimize the number of times the chassis will be reloaded.
It is also recommended to begin the conversion process using a default configuration as the conversion process will remove any previous configuration that pre-exists on the
Conversion Process
Conversion to VSS
For the purposes of this explanation - let’s assume the following setup is required…
Switch - 1 Switch - 2
VSL Link Bundle
T5/4
T5/5
T5/4
T5/5
Port-Channel 1 Port-Channel 2
Switch Virtual Domain #10
Conversion Process
Step 1: Configure Virtual Switch ID and Domain
On the two switches, configure the same VS Domain number (in this case it is 10), but unique Switch IDs
Switch - 1 Switch - 2
Router(config)#host VSS
VSS(config)#switch virtual domain 10
Domain ID 10 config will take effect only after the exec command 'switch convert mode virtual' is issued
VSS(config-vs-domain)#switch 1 VSS(config-vs-domain)#exit
Router(config)#host VSS
VSS(config)#switch virtual domain 10
Domain ID 10 config will take effect only after the exec command 'switch convert mode virtual' is issued
VSS(config-vs-domain)#switch 2 VSS(config-vs-domain)#exit
Note: The Domain ID is retained in the configuration, but the Switch ID is not – this is stored as a variable in ROMMON. To see this value:
Conversion Process
Step 2: VSL Configuration – Configure the VSL Port Channel and member ports
Choose unique Port Channel IDs for each chassis to form the VSL and configure them with the corresponding Switch ID
Add the ports on each switch to the port channel that corresponds to the respective side of the VSL
Switch - 1 Switch - 2
VSS(config)#interface port-channel 1
! Associates Switch 1 as owner of port channel 1 VSS(config-if)#switch virtual link 1
VSS(config-if)#interface range tenG 5/4 - 5
! Adds this interface to channel group 1
VSS(config-if-range)#channel-group 1 mode on
VSS(config-if)#interface port-channel 2
! Associates Switch 2 as owner of port channel 2 VSS(config-if)#switch virtual link 2
VSS(config-if)#interface range tenG 5/4 - 5
! Adds this interface to channel group 2
VSS(config-if-range)#channel-group 2 mode on
Conversion Process
Step 3: Convert to Virtual Switch Mode
Convert both switches to Virtual Switch mode using the following exec command:
Switch - 1 Switch - 2
vss#switch convert mode virtual
This command will convert all interface names to naming convention "interface-type switch-number/slot/port", save the running config to startup-config and reload the switch.
Do you want to proceed? [yes/no]: yes Converting interface names
Building configuration...
[OK]
Saving converted configuration to bootflash:
...
Destination filename
[startup-config.converted_vs-20071031-150039]?
vss#switch convert mode virtual
This command will convert all interface names to naming convention "interface-type switch-number/slot/port", save the running config to startup-config and reload the switch.
Do you want to proceed? [yes/no]: yes Converting interface names
Building configuration...
[OK]
Saving converted configuration to bootflash:
...
Destination filename
[startup-config.converted_vs-20071031-150018]?
AT THIS POINT THE SWITCH WILL REBOOT
Conversion Process
When the two switches are brought online, they will proceed with VSL initialization and bring up their respective VSL ports.
The two switches communicate with each other and determine Active and Standby role.
Switch - 1 Switch - 2
SWITCH CONSOLE OUTPUT
<…snip…>
System detected Virtual Switch configuration...
Interface TenGigabitEthernet 1/5/4 is member of PortChannel 1
Interface TenGigabitEthernet 1/5/5 is member of PortChannel 1
<…snip…>
00:00:26: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch
Initializing as Virtual Switch ACTIVE processor
<…snip…>
00:01:19: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE by VSLP
00:01:19: %VSL-5-VSL_CNTRL_LINK: New VSL
SWITCH CONSOLE OUTPUT
<…snip…>
System detected Virtual Switch configuration...
Interface TenGigabitEthernet 2/5/4 is member of PortChannel 2
Interface TenGigabitEthernet 2/5/5 is member of PortChannel 2
<…snip…>
00:00:26: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch
Initializing as Virtual Switch STANDBY processor
<…snip…>
00:01:02: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP
Conversion Process
Step 4: Finalize Virtual Switch Configuration
This command will get the VSL related commands from the Standby Switch and update the startup-configuration with the new merged configurations
Note that only VSL-related configurations are merged with this step – all other configuration will be lost and requires manual intervention.
This step is only applicable for a first-time conversion.
Switch - 1
SWITCH CONSOLE OUTPUT
<…snip…>
vss-demo#switch accept mode virtual
This command will populate the above VSL configuration from the standby switch into the running configuration.
The startup configuration will also be updated with the new merged configuration if merging is successful.
Do you want to proceed? [yes/no]: yes Merging the standby VSL configuration...
Building configuration...
00:11:33: %PFINIT-SW1_SP-5-CONFIG_SYNC: Sync'ing the startup configuration to the standby Router. [OK]
Conversion Process
Conversion to VSS
Configuration for the conversion takes the following path…
Switch - 1 Switch - 2
vss#sh switch virtual
Switch mode : Virtual Switch Virtual switch domain number : 10
Local switch number : 1
Local switch operational role: Virtual Switch Active Peer switch number : 2
Peer switch operational role : Virtual Switch Standby vss-demo#
vss-sdby>en
Standby console disabled vss-sdby>
Both switches are now converted with Switch 1 as the Master (Active) and Switch 2 as the Standby
Switch 2 console is now disabled for normal console activity…