Cisco Cisco 1700 2600 3600 3700 Series VPN Module White Paper

 

 

© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 26 of 55 

If a switchover occurs and switch 2 becomes the active virtual switch, the console becomes active on that 

supervisor engine. 

Interface Numbering 

After conversion to a Virtual Switching System, the interface numbering changes from a traditional scheme: 

To a new 3-number scheme: 

This new naming scheme allows a single configuration file to uniquely address the physical interfaces on both 

chassis that are part of the same virtual switch domain. 

Interface IP-Address OK? Method Status Protocol  

Vlan1 unassigned YES NVRAM administratively down down  

Vlan10 192.168.10.1 YES NVRAM up up  

Vlan20 192.168.20.1 YES NVRAM up up  

Loopback0 3.3.3.3 YES NVRAM up up  

Port-channel1 unassigned YES NVRAM up up  

Port-channel2 unassigned YES NVRAM up up  

Port-channel10 unassigned YES unset up up  

Port-channel20 unassigned YES unset up up  

File-System Naming 

To facilitate the ability to uniquely identify multiple file systems on each supervisor engine or module across the 

Cisco Virtual Switching System, a new role-independent file-system naming scheme has been implemented: 

SW<SWITCH_ID>-SLOT<MODULE>-<FILESYSTEM>: 

This naming scheme allows all unique file systems to be addressed and identified across the entire virtual switch 

domain, regardless of supervisor-engine redundancy state: 

vss#dir sw1-slot?  

sw1-slot1-dfc-bootflash: sw1-slot5-const_nvram: sw1-slot5-disk0:  

sw1-slot5-nvram: sw1-slot5-sup-bootdisk: sw1-slot5-sup-  

bootflash:  

sw1-slot7-dfc-bootflash: sw1-slot8-dfc-bootflash:  

vss#dir sw2-slot?  

sw2-slot1-dfc-bootflash: sw2-slot5-bootflash: sw2-slot5-  

const_nvram:  

sw2-slot5-disk0: sw2-slot5-nvram: sw2-slot5-sup-