Slide 1 - CAROLINA CISCO USERS GROUP (CCUG)

Download Report

Transcript Slide 1 - CAROLINA CISCO USERS GROUP (CCUG)

Understanding Virtual Switching System on the Cisco Catalyst 6500 Cisco Users Group Tommy Dodd ( [email protected]

) SE, Cisco Systems

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 1

Current Network Challenges Enterprise Campus

Traditional Enterprise Campus deployments have been designed in such a way that allows for scalability, differentiated services and high availability. However they also face many challenges, some of which are listed in the below diagram… L3 Core Extensive routing topology, Routing reconvergence L2/L3 Distribution FHRP, STP, Asymmetric routing, Policy Management Access Single active uplink per VLAN (PVST), L2 reconvergence

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 2

Current Network Challenges Data Center

Traditional Data Center designs are requiring ever increasing Layer 2 adjacencies between Server nodes due to prevalence of Virtualization technology. However, they are pushing the limits of Layer 2 networks, placing more burden on loop-detection protocols such as Spanning Tree… FHRP, HSRP, VRRP Spanning Tree Policy Management L2/L3 Core Single active uplink per VLAN (PVST), L2 reconvergence, excessive BPDUs L2 Distribution Dual-Homed Servers to single switch, Single active uplink per VLAN (PVST), L2 reconvergence

BRKRST-3468

L2 Access

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 3

Virtual Switching System

Virtual Switch System is a new technology break through for the Catalyst 6500 family…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 4

Introduction to Virtual Switch Concepts

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 5

Virtual Switch System Enterprise Campus

A Virtual Switch-enabled Enterprise Campus network takes on multiple benefits including simplified management & administration, facilitating greater high availability, while maintaining a flexible and scalable architecture… L3 Core L2/L3 Distribution Access Reduced routing neighbors, Minimal L3 reconvergence No FHRPs No Looped topology Policy Management Multiple active uplinks per VLAN, No STP convergence

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 6

Virtual Switch Architecture

VSL Initialization

Before the Virtual Switch domain can become active, the Virtual Switch Link (VSL) must be brought online to determine Active and Standby roles. The initialization process essentially consists of 3 steps: 1 Link Bringup to determine which ports form the VSL 2 Link Management Protocol (LMP) used to track and reject Unidirectional Links, Exchange Chassis ID and other information between the 2 switches LMP RRP LMP RRP

BRKRST-3468

3 Role Resolution Protocol (RRP) form the VSL as well as determine which switch becomes Active and Hot Standby from a control plane perspective used to determine compatible Hardware and Software versions to

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 7

Virtual Switch Architecture

Link Bringup

Each member of the Virtual Switch domain must determine which links are candidate for VSL very early on in the bootup cycle. The Switch Processor (SP) pre-parses the configuration to determine which links are configured for VSL… Pre-Parse Config Switch 1 Pre-Parse Config Switch 2 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 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 The SP will then bring up the line card/s where the VSL is configured, download the required configuration and initiate Link Management Protocol (LMP)

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential BRKRST-3468 8

Virtual Switch Architecture

Link Management Protocol (LMP)

LMP runs on each individual link that is part of the VSL, and is used to program information such as member details, forwarding indices, as well as perform the following checks: 1 2 3 Verify neighbor is Bi-Directional Ensure the member is connected to another Virtual Switch Transmit and receive keepalives to maintain health of the member and the VSL LMP LMP LMP LMP After successful LMP negotiation, a Peer Group (PG) is formed which is a collection of all VSL members that connects to the same VS. For each PG, a Peer Group Control Link (PGCL) is elected to carry further control information…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 9

Virtual Switch Architecture

Role Resolution Protocol (RRP)

RRP also runs on each individual link of the VSL. It will run on each Peer Group and will elect one of them to resolve the role between the 2 Virtual Switches. It is also part of VSLP and performs the following functions: 1 2 Determine whether hardware and software versions allow a Virtual Switch to form Determine which chassis will become Active and Hot Standby from a control plane perspective RRP RRP RRP RRP VSL

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 10

Virtual Switch Architecture VSLP Ping

A new Ping mechanism has been implemented in VSS mode to allow the user to objectively verify the health of the VSL itself. This is implemented as a VSLP Ping… VSL VSLP VSLP VSLP VSLP Switch 1 Switch 2 The VSLP Ping operates on a per-physical interface basis and parameters such as COUNT, DESTINATION, SIZE, TIMEOUT may also be specified… vss# ping vslp output interface tenGigabitEthernet 1/5/4

Type escape sequence to abort.

Sending 5, 100-byte VSLP ping to peer-sup via output port 1/5/4, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/16 ms vss#

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 11

Virtual Switch Architecture VSL Configuration Consistency Check

After the roles have been resolved through RRP, a Configuration Consistency Check is performed across the VSL switches to ensure proper VSL operation. The following items are checked for consistency: Switch Virtual Domain ID Switch Virtual Node Type Switch Priority Switch Preempt VSL Port Channel Link ID VSL Port state, interfaces… Power Redundancy mode Power Enable on VSL cards

BRKRST-3468

Note that if configurations do not match, the standby switch will revert to RPR mode, disabling all non-VSL interfaces…

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 12

Virtual Switch Architecture Forwarding Operation

In Virtual Switch Mode, while only one Control plane is active, both Data Planes (Switch Fabric’s) are active, and as such, each can actively participate in the forwarding of data … Switch 1 - Control Plane Active Switch 2 - Control Plane Hot Standby Virtual Switch Domain Switch 1 - Data Plane Active Switch 2 - Data Plane Active Virtual Switch Domain

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 13

Virtual Switch Architecture Virtual Switch Domain

A Virtual Switch Domain ID is allocated during the conversion process and represents the logical grouping the 2 physical chassis within a VSS. It is possible to have multiple VS Domains throughout the network… VS Domain 10 VS Domain 20 VS Domain 30 The configurable values for the domain ID are 1-255. It is always recommended to use a unique VS Domain ID for each VS Domain throughout the network…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 14

Virtual Switch Architecture Router MAC Address

In a standalone Catalyst 6500 system, the router MAC address is derived from the Chassis MAC EEPROM and is unique to each Chassis. In a Virtual Switch System, since there is only a single routing entity now, there is also only ONE single router MAC address… Router MAC = 000f.f8aa.9c00

The MAC address allocated to the Virtual Switch System is negotiated at system initialization. Regardless of either switch being brought down or up, the same MAC address will be retained such that neighboring network nodes and hosts do not need to re-ARP for a new address.

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 15

EtherChannel Concepts

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 16

Etherchannel Concepts

An Etherchannel combines multiple physical links into a single logical link. Ideal for load sharing or link redundancy – can be used by both layer 2 and Layer 3 subsystems…

Physical View

Multiple ports are defined as being part of an Etherchannel group

Logical View

Subsystems running on the switch only see one logical link An Etherchannel can be defined on Ethernet, Fast Ethernet, Gigabit Ethernet or 10 Gigabit Ethernet Ports

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential BRKRST-3468 17

Etherchannel Concepts Multichassis EtherChannel (MEC)

Prior to Virtual Switch, Etherchannels were restricted to reside within the same physical switch. In a Virtual Switch environment, the 2 physical switches form a single logical network entity - therefore Etherchannels can now also be extended across the 2 physical chassis… Virtual Switch Virtual Switch Both LACP and PAGP Etherchannel protocols and Manual ON modes are supported… Regular Etherchannel on single chassis

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Multichassis EtherChannel across 2 VSL enabled Chassis

18

Etherchannel Concepts Multichassis EtherChannel

Support for Etherchannel management is performed by the Control plane on the Active Switch in the Virtual Switch Domain… Standby Control Plane Active Control Plane MEC links on both the switches in the VS domain are managed by PAgP or LACP running on the Master Switch via internal control messages. PAgP or LACP packets destined to a MEC link on the standby core will be sent across VSL

19 BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Etherchannel Concepts Etherchannel Hash for MEC

Deciding on which link of a Multi-chassis Etherchannel to use in a Virtual Switch is skewed in favor towards local links in the bundle - this is done to avoid overloading the Virtual Switch Link (VSL) with unnecessary traffic loads… Blue Traffic the Server will result in Link A1 destined for in the MEC link bundle being chosen as the destination path… Orange Traffic destined for the Server will result in Link B2 in the MEC link bundle being chosen as the destination path… Link A1 Link B2

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Server

20

Etherchannel Concepts Etherchannel Hash for MEC

Localizing the decision to use a link in the bundle that is resident on the local Switch (thus avoiding forwarding over the VSL) is done as follow… Virtual Switch The BUNDLE_SELECT register in the port ASIC is programmed to see only the local links of the Etherchannel bundle even though links may exist in the same bundle are resident in the VS peer chassis… This behavior is fixed and cannot be changed by any configuration option… NOTE: If all links in the local bundle go down, then the BUNDLE_SELECT register is programmed to point packets to the VSL…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 21

Etherchannel Concepts Etherchannel Hash for MEC

RBH values are reprogrammed for each core to reflect only the local links that are in the Etherchannel bundle… Switch 1 Virtual Switch Switch 2 1 2 3 4 5 6 7 8 MEC RBH (No MEC) 8 Link Bundle Example Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Link 1 Link 2 Link 3 Link 4 Link 5 Link 6 Link 7 Link 8

BRKRST-3468

RBH (for MEC) 8 Link Bundle Example Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Link 1 Link 1 Link 2 Link 2 Link 3 Link 3 Link 4 Link 4

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 22

Hardware Requirements

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 23

Hardware Requirements Supervisor

In order to enable the Virtual Switch feature and configure the Virtual Switch Links (VSL) between 2 Catalyst 6500 chassis, the new Catalyst 6500 Virtual Switching Supervisor 720 is required to be used. It is the only Supervisor that will support VSS as it supports both the new PFC3C/XL forwarding engine… VS-S720-10G-3C/XL

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

The PFC3C/XL contains new hardware to support the extra LTL indices and mappings required to forward traffic across multiple physical chassis, lookup enhancements as well as MAC address table handling enhancements…

24

Hardware Requirements VSL-Capable Interfaces

The VSL is a special link that requires extra headers to be imposed onto the frame. These require new port ASICs that exist only on the 10 GigabitEthernet interfaces on the following modules… Supervisor 720-10G Note that these interfaces may also be used as standard network interfaces WS-X6708-10G-3C/XL These interfaces are based off the new R2D4 ASIC, allowing for frames across the VSL to be encapsulated / de-encapsulated with the VSH…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 25

Hardware Requirements Other Supported Modules…

Other modules that may exist in the VSL domain include all CEF720 and dCEF720 cards (WS X67xx-series), as well as SVC-NAM-1 and SVC-NAM-2. Classic, CEF256 and dCEF256 cards are not supported… CEF720, dCEF720 and NAM only

26 BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Hardware Requirements Distributed Forwarding Cards

Distributed Forwarding Cards (DFCs) improve the performance of the Catalyst 6500 by offloading the lookup processing from the PFC to the ingress linecard. Only DFC3C or DFC3CXL is supported in a Virtual Switch domain. If DFCs are not used on CEF720 modules, a Centralized Forwarding Card (CFC) must be installed in its place… Note that if a lower revision DFC (3A, 3B or 3BXL) is used in a VSL domain, the system will fall to a lowest common denominator mode which will not allow support for VSL…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 27

Conversion Process

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 28

Conversion Process Conversion to VSS

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…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 29

Conversion Process Conversion to VSS

For the purposes of this explanation - let’s assume the following setup is required… Switch - 1 Switch - 2 T5/4 T5/5 VSL Link Bundle T5/4 T5/5 Port-Channel 1 Port-Channel 2 Switch Virtual Domain #100

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 30

Conversion Process Conversion to VSS

Configuration for the conversion takes the following path… Switch - 1 Switch - 2 Router(config)# host VSS VSS(config)# switch virtual domain 100 VSS(config-vs-domain)# switch 1 VSS(config-vs-domain)# exit VSS(config)# interface port-channel 1 VSS(config-if)# switch virtual link 1 VSS(config-if)# interface tenG 5/4 VSS(config-if)# channel-group 1 mode on VSS(config-if)# interface tenG 5/5 VSS(config-if)# channel-group 1 mode on VSS(config-if)# ^Z VSS #

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Router(config)# host VSS VSS(config)# switch virtual domain 100 VSS(config-vs-domain)# switch 2 VSS(config-vs-domain)# exit VSS(config-if)# interface port-channel 2 VSS(config-if)# switch virtual link 2 VSS(config-if)# interface tenG 5/4 VSS(config-if)# channel-group 2 mode on VSS(config-if)# interface tenG 5/5 VSS(config-if)# channel-group 2 mode on VSS(config-if)# ^Z VSS #

31

Conversion Process Conversion to VSS

Configuration for the conversion takes the following path… 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 proceed? [yes/no]: yes Converting interface names Building configuration...

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 proceed? [yes/no]: yes Converting interface names Building configuration...

AT THIS POINT THE SWITCH WILL REBOOT AT THIS POINT THE SWITCH WILL REBOOT

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 32

Conversion Process Conversion to VSS

Configuration for the conversion takes the following path… Switch - 1 Switch - 2 SWITCH CONSOLE OUTPUT

< … snip … >

System detected Virtual Switch configuration...

Interface TenGigabitEthernet 1/1/4 is member of PortChannel 1 Interface TenGigabitEthernet 1/1/5 is member of PortChannel 1

< … snip … > 00:00:22: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch < … snip … > 00:00:28: %VSL_BRINGUP-6-MODULE_UP: VSL module in slot 1 switch 1 brought up

Initializing as Virtual Switch active

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

SWITCH CONSOLE OUTPUT

< … snip … >

System detected Virtual Switch configuration...

Interface TenGigabitEthernet 2/1/4 is member of PortChannel 2 Interface TenGigabitEthernet 2/1/5 is member of PortChannel 2

< … snip … > 00:00:23: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch < … snip … > 00:00:28: %VSL_BRINGUP-6-MODULE_UP: VSL module in slot 1 switch 2 brought up

Initializing as Virtual Switch standby

33

Conversion Process Conversion to VSS

Configuration for the conversion takes the following path… Switch - 1 Switch - 2 VSS-sdby> en Standby console disabled VSS-sdby> VSS# sh switch virtual role

Switch Switch Status Preempt Priority Role Session ID Number Oper(Conf) Oper(Conf) Local Remote ----------------------------------------------------------------- LOCAL 1 UP FALSE(N) 110(110)

ACTIVE

0 0 REMOTE 2 UP FALSE(N) 100(100)

STANDBY

4217 6561

Both switches are now converted with Switch 1 as the Master (Active) and Switch 2 as the Standby

In dual-active recovery mode: No

Switch 2 console is now disabled for normal console activity…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 34

Conversion Process Boot-up Priority

Normal operation is for first switch to boot to assume VS Active role - this behavior can be changed allowing a pre defined switch to assume Active role by specifying a priority (higher priority uses a higher number)… Virtual Switch Switch 1 Switch 2 VSS#sh switch virtual role

Switch Switch Status Preempt Priority Role Session ID Number Oper(Conf) Oper(Conf) Local Remote ----------------------------------------------------------------- LOCAL 1 UP FALSE(N)

110(110)

ACTIVE 0 0 REMOTE 2 UP FALSE(N)

100(100)

STANDBY 9114 1391 In dual-active recovery mode: No BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 35

Operational Management

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 36

Operational Management Virtual Switch CLI

Multiple console interfaces exist within a Virtual Switch Domain, but only the active RP/SP consoles are enabled for command interaction…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 37

Operational Management Reloading the VSS

Should there be a requirement to reload the entire Virtual Switch System (both chassis), the command “reload” can be used to accomplish this task…

BRKRST-3468

vss# reload Proceed with reload? [confirm]

1d04h: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.

*** *** --- SHUTDOWN NOW -- *** 1d04h: %SYS-SP-5-RELOAD: Reload requested System Bootstrap, Version 8.5(1) Copyright (c) 1994-2006 by cisco Systems, Inc.

Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory <…snip…> © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 38

Operational Management Reloading a member of the VSS

It is also possible to reload each chassis individually by specifying the Switch ID assigned through the following command set… vss#redundancy reload shelf ?

<1-2> shelf id

vss# redundancy reload shelf 2 Reload the entire remote shelf[confirm]

Preparing to reload remote shelf vss# BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 39

Operational Management Setting the System-wide PFC Mode

Only PFC/DFC 3C/CXL are supported in a VSS. However, it is possible to mix modules in a 3C and 3CXL system, bearing in mind that the system will take the lowest common denominator as the system-wide PFC mode. A new CLI has been implemented to allow the user to pre configure the system mode to prevent modules from not powering up… vs-vsl#

vs-vsl#

conf t

Enter configuration commands, one per line. End with CNTL/Z.

vs-vsl(config)# platform hardware vsl pfc mode pfc3c

vs-vsl(config)#^Z

vs-vsl# sh platform hardware pfc mode PFC operating mode : PFC3C Configured PFC operating mode : PFC3C

vs-vsl# BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 40

Operational Management SNMP Support for VSS

The SNMP process for a VSS necessitates support for “Put’s” and “Get’s” across 2 physical chassis, changes to existing MIB’s and support for a new MIB… SNMP Server SNMP Put’s Switch 1 Active SNMP Get’s Switch 2 Standby SNMP Modified MIB’s SNMP New MIB’s SNMP Process Active Virtual Switch Domain

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

SNMP Process Inactive

41

Operational Management SNMP Modified MIB’s

The following MIB’s have been modified to allow the collection of data in a Virtual Switch configuration… Virtual Switch MIB Name CISCO-LAG-MIB CISCO-EXT-BRIDGE-MIB CISCO-VLAN-MEMBERSHIP-MIB CISCO-ENVMON-MIB CISCO-STACK-MIB CISCO-OLD-CHASSIS-MIB CISCO-CAT6K-CROSSBAR-MIB Description of Change Extended to support 6000 ports Supports extension of BRIDGE-MIB (which is a standard and cannot be changed. Extended to support up to 6000 ports.

Extended to support 6000 ports Virtual Switch Chassis number will be included in the “Description” field No longer supported. Use ENTITY-MIB instead.

No longer supported. Use ENTITY-MIB instead.

Support Standby Core with a different naming scope

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 42

Operational Management New Virtual Switch MIB

CISCO-VIRTUAL-SWITCH-MIB has been defined to support SNMP access to the Virtual Switch Configuration - the following MIB variables are accessible to an SNMP manager… CISCO-VIRTUAL-SWITCH-MIB cvsGlobalObjects - Domain #, Switch #, Switch Mode cvsCoreSwitchConfig - Switch Priority and Preempt cvsChassisTable - Chassis Role and Uptime cvsVSLConnectionTable - VSL Port Count, Operational State cvsVSLStatsTable - Total Packets, Total Error Packets cvsVSLPortStatsTable - TX/RX Good, Bad, Bi-dir and Uni-dir Packets This MIB will be the main vehicle though which Network Management stations access information relevant to the operation of the Virtual Switch…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 43

Operational Management Slot/Port Numbering

After conversion, port definitions for switches within the Virtual Switch Domain inherit the Chassis ID as part of their naming convention… PORT NUMBERING: Chassis-ID WILL ALWAYS be either a “1” or a “2” Router# show ip interface brief

Interface IP-Address OK? Method Status Protocol Vlan1 unassigned YES NVRAM up up Port-channel1 unassigned YES NVRAM up up Te1/1/1 10.1.1.1 YES unset up up Te1/1/2 192.168.1.2 YES unset up up Te1/1/3 Te1/1/4 GigabitEthernet1/2/1 GigabitEthernet1/2/2 unassigned YES unset up up unassigned YES unset up up 10.10.10.1 YES unset up up 10.10.11.1 YES unset up up 44 BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Operational Management File System Naming

After the conversion to a Virtual Switch, some of the File System naming conventions have changed to accommodate the new setup - an example of the new setup is shown below… SWSLOTFILESYSTEM e.g.

OLD: disk0: NEW: sw1-slot5-disk0: AN EXAMPLE e.g.

OLD: slavedisk0: NEW: sw2-slot5-disk0: Virtual Switch Domain Active Supervisor - Slot 5 Switch 1 Hot Standby Supervisor - Slot 5 Switch 2

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 45

Operational Management File System Naming

Some filenames have remained the same - others have changed - some examples of file system names in a Virtual Switch include the following… PREVIOUS disk0: slavedisk0: bootflash: slavebootflash: sup-bootdisk: slavesup-bootdisk: nvram: const_nvram:

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

VIRTUAL SWITCH swslotdisk0: slavedisk0: swslotbootflash: slavebootflash: swslotsup-bootdisk: slavesup-bootdisk: swslotnvram: swslotconst_nvram:

46

Operational Management NVRAM Considerations

The Sup720 is equipped with 2Mb of NVRAM, but considerations must be made to evaluate the impact of combining the configurations of each switch into a combined configuration … Config Switch A Combining the configurations is done automatically during the VS conversion… Config Switch B Combined Config Switch A + B Note: Internal Testing estimates show combining two switch configurations into one with VS yields a saving of up to ~30% when compared to the size of the two original configurations …

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

6506#dir sw1-slot5-nvram:

Directory of nvram:/

1964024 bytes total

(1950786 bytes free)

47

Operational Management Netflow

In a Virtual Switch, with both Data Planes active, Netflow data collection is performed on each Supervisor’s PFC - while Netflow export is only performed by the Control Plane on the VS Active … Virtual Switch Domain Switch 1 Supervisor Switch 2 Supervisor VSL VS State : Active Control Plane: Active Data Plane: Active Netflow Collection: Active Netflow Export: Active VS State : Standby Control Plane: Standby Data Plane: Active Netflow Collection: Active Netflow Export: In-Active Netflow operation in a Virtual Switch is similar to the way in which Netflow operates in a single chassis with Distributed Forwarding Card’s (DFC) present…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 48

Operational Management Netflow Export

The Virtual Switch Link will be used as the transit path to allow the standby Sup to forward Netflow data to the active Supervisor for Netflow export - the VS Link should be dimensioned to accommodate the expected Netflow export load… Netflow Collector Netflow Data Netflow Export Virtual Switch Domain VSL

BRKRST-3468

VS State : Active Netflow Collection: Active Netflow Export: Active

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

Netflow Data VS State : Standby Netflow Collection: Active Netflow Export: In-Active

49

Operational Management SPAN

In a Virtual Switch Domain, the number of SPAN sessions is limited to what the VS Active Supervisor can provide. SPAN capacity on the VS Standby is not factored into available SPAN sessions… Switch 1 Supervisor Virtual Switch Domain Switch 2 Supervisor VSL VS State : Active Control Plane: Active Data Plane: Active SPAN Management: Active Replication: Active VS State : Standby Control Plane: Standby Data Plane: Active SPAN Management: In-Active Replication: Active Virtual Switch is supported in Whitney 1 which introduces the following SPAN capabilities per Virtual Switch Domain… Virtual Switch Domain TX SPAN Sessions

14

RX/Both SPAN Sessions

2

Total SPAN Sessions

16 BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 50

Operational Management CiscoWorks LMS 3.0.1

CiscoWorks LAN Management Solution (LMS) 3.0.1 release will support an additional plugin that will allow for it to support various functions to manage a Virtual Switching System… LMS will support the following functions: 4 5 1 2 3 Conversion from Standalone to VSS Inventory Management and Reporting Configuration Collection and Archive Management Image Upgrade - Base image and Patch CiscoView Management

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 51

Operational Management Conversion

A new feature of LMS 3.0 will allow for the conversion from two Standalone chassis to a single VSS domain. This is achieved through a Wizard that will guide the user through the necessary steps… 1 Select the Standalone Switches to be converted - note that these devices must be already seen by RME… 2 Verify the appropriate Hardware and Software versions have been installed…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 52

Operational Management Conversion

After the conversion process has executed, the appropriate configuration changes will be applied and the switches will be reset… 3 Specify the interfaces to be used to set up the VSL…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

4 Confirm the configuration changes and apply the configurations…

53

Operational Management Inventory Management (RME)

Inventory Data can be collected and Reported through Resource Management Essentials (RME) from both the Active and Standby Chassis… The Detailed Inventory Report can show the Entire Inventory along with both Hardware and Software information…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 54

Operational Management Configuration Collection (RME)

RME will also support the ability to fetch the running configuration from the VSS as well as provide Archive and configuration version management abilities…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 55

Operational Management CiscoView

CiscoView is designed to show the view of both Active and Standby chassis INDIVIDUALLY. The user can switch between the views using Device-level menu options… Each chassis is identified by a label indicating whether it is Active or Standby

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 56

High Availability

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 57

High Availability Redundancy Schemes

The default redundancy mechanism between the 2 VSS chassis and their associated supervisors is NSF/SSO, allowing state information and configuration to be synchronized. Additionally, only in NSF/SSO mode does the Standby supervisor PFC, Switch Fabric, modules and their associated DFCs become active… Switch 1 12.2(33)SXH1 Active Switch 2 12.2(33)SXH1 NSF/SSO VSL Should a mismatch of information occur between the Active and Standby Chassis, the Standby Chassis will revert to RPR mode, where only configuration is synchronized, but PFC, Switch Fabric and modules will not be brought up Switch 1 12.2(33)SXH1 Active Switch 2 12.2(33)SXH2 RPR VSL

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 58

High Availability NSF/SSO Requirements

After the roles have been resolved through RRP, a Configuration Consistency Check is performed across the VSL switches to ensure proper VSL operation. The following items are checked for consistency: Switch Virtual Domain ID Switch Virtual Node Type Switch Priority Switch Preempt VSL Port Channel Link ID VSL Port state, interfaces… Power Redundancy mode Power Enable on VSL cards

BRKRST-3468

Additionally, software version, installed patches and PFC modes also need to be consistent for NSF/SSO mode to be entered…

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 59

High Availability Dual-Active Detection

In a Virtual Switch Domain, one switch is elected as Active and the other is elected as Standby during bootup by VSLP. Since the VSL is always configured as a Port Channel, the possibility of the entire VSL bundle going down is remote, however it is a possibility… Virtual Switch Domain Switch 1 Supervisor Switch 2 Supervisor VSL VS State : Active Control Plane: Active Data Plane: Active VS State : Standby Control Plane: Standby Data Plane: Active It is always recommended to deploy the VSL with 2 or more links and distribute those interfaces across multiple modules to ensure the greatest redundancy

60 BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

High Availability Dual-Active Detection

If the entire VSL bundle should happen to go down, the Virtual Switch Domain will enter a Dual Active scenario where both switches transition to Active state and share the same network configuration (IP addresses, MAC address, Router IDs, etc…) potentially causing communication problems through the network… Virtual Switch Domain Switch 1 Supervisor Switch 2 Supervisor VSL VS State : Active Control Plane: Active Data Plane: Active VS State : Active Control Plane: Active Data Plane: Active 2 mechanisms have been implemented in the initial release to detect and recover from a Dual Active scenario: 1 2 Enhanced Port Aggregation Protocol (PAgP) Dual-Active Detection over IP-BFD

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential BRKRST-3468 61

High Availability Dual-Active Detection - Enhanced PAgP

Enhanced PAgP allows for new TLVs to be relayed from the individual Virtual Switches to a remote device that is EtherChanneled to the Virtual Switch Domain. During normal operation the Virtual Switches will send the ID of the Active VS to the PAgP neighbor, and it will respond with the same Active ID… Switch 1 Switch 2 Switch 1 Switch 2 Active: Switch 1 Active: Switch 1 Active: Switch 1 Active: Switch 2 Should the VSL go down, the Standby switch will transition immediately to Active state and start sending PAgP message with the new Active switch ID

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 62

High Availability Dual-Active Detection - Enhanced PAgP

The Enhnaced PAgP-capable neighbor will proceed to send the new Active Switch ID to all member ports of the port channel that it received the new Active Switch ID on, including the previous-active Virtual switch (Switch 1) … Dual-Active!!

Switch 1 Switch 2 Switch 1 Switch 2 Active: Switch 2 Active: Switch 2 Active: Switch 2 On Switch 1, Upon reception of PAgP messages with the Active ID of Switch 2, it will be aware that a Dual-Active scenario has occurred and will proceed to bring down all local interfaces*

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 63

High Availability Dual-Active Detection - Enhanced PAgP

Dual-Active Detection capabilities require that the neighboring device be Dual-Active Detection Aware. This can be verified with the following command… vs-vsl# sh switch virtual dual-active pagp

Channel group 10 dual-active detect capability w/nbrs Dual-Active version: 1.1

Dual-Active configured: Yes

Dual-Active Partner Partner Partner Port Detect Capable Name Port Version Gi1/8/1 Yes vs-access-1 Gi5/1 1.1

Gi2/8/1 Yes vs-access-1 Gi5/2 1.1

Enhanced PAgP Dual-Active recovery is enabled by default and may be disabled globally under the switch virtual configuration sub-mode… vs-vsl# conf t

Enter configuration commands, one per line. End with CNTL/Z.

vs-vsl(config)#switch virtual domain 100 vs-vsl(config-vs-domain)# no dual-active detection pagp vs-vsl(config-vs-domain)# ^Z vs-vsl#

64 BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

High Availability Dual-Active Detection - IP-BFD

Dual-Active Detection with IP-BFD allows for the detection of a Dual-Active scenario subsequent to the Standby RP becoming Active. This mechanism requires that a direct heartbeat link be used to carry the IP-BFD frames from Switch 1 to Switch 2… VSL IP-BFD Heartbeat Link Switch 1 Switch 2 VSL BFD IP-BFD Heartbeat Link BFD Switch 1 Switch 2 The IP-BFD Heartbeat link may exist on any interface but must have an IP address assigned to it on a different network

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 65

High Availability Dual-Active Detection - IP-BFD

To enable IP BFD as the detection mechanism, two directly-connected interfaces must be configured as BFD message links… vss(config)#interface gigabitethernet 1/5/1 vss(config-if)#no switchport vss(config-if)#ip address 200.230.230.231 255.255.255.0

vss(config-if)# bfd interval 100 min_rx 100 multiplier 50 vss(config-if)#no shutdown vss(config-if)#interface gigabitethernet 2/5/1 vss(config-if)#no switchport vss(config-if)#ip address 201.230.230.231 255.255.255.0

vss(config-if)# bfd interval 100 min_rx 100 multiplier 50 vss(config-if)#no shutdown vss(config-if)#exit vss(config)#switch virtual domain 100 vss(config-vs-domain)# dual-active detection ipbfd vss(config-vs-domain)# dual-active pair interface g 1/5/1 interface g 2/5/1 ipbfd

adding a static route 200.230.230.0 255.255.255.0 Gi2/5/1 for this dual-active pair adding a static route 201.230.230.0 255.255.255.0 Gi1/5/1 for this dual-active pair

vss(config-vs-domain)#

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 66

High Availability Dual-Active Detection - Exclude Interfaces

Upon detection of a Dual Active scenario, all interfaces on the previous-Active switch will be brought down so as not to disrupt the functioning of the remainder of the network. The exception interfaces include VSL members as well as pre-determined interfaces which may be used for management purposes… vs-vsl# conf t

Enter configuration commands, one per line. End with CNTL/Z.

vs-vsl(config)#switch virtual domain 100 vs-vsl(config-vs-domain)# dual-active exclude interface Gig 1/5/1 vs-vsl(config-vs-domain)# dual-active exclude interface Gig 2/5/1 vs-vsl(config-vs-domain)# ^Z vs-vsl#

67 BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

High Availability Dual-Active Recovery

Upon the restoration of one or more VSL interfaces, VSLP will detect this and will proceed to reload Switch 1 so that it may be able to re-negotiate Active/Standby role after bootup… Switch 1 Switch 2 Switch 1 VSLP VSL Up! Reload… VSLP Switch 2 After role has been resolved and SSO Hot Standby mode is possible, interfaces will be brought up and traffic will resume back to 100% capacity…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 68

High Availability Generic OnLine Diagnostics (GOLD)

Some enhancements to the GOLD framework have been implemented in a VSS environment, which leverages a Distributed GOLD environment. In this case, each supervisor runs an instance of GOLD, but is centrally managed by the Active Supervisor in the Active chassis… Switch 1 Switch 2 VSL VS State : Active Local GOLD: Active Distributed GOLD Manager There are 4 new tests that are available in VSS mode: 1 TestVSLLocalLoopback 2 TestVSLBridgeLink 3 TestVSLStatus 4 TestVSActiveToStandbyLoopback

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential

VS State : Standby Local GOLD: Active

69

High Availability DHCP Snooping & Integrated Security

The 12.2(33)SXH release allows for the stateful synchronization of the binding and posture tables to be statefully synchronized across the members of the VSS. This will alleviate the requirement for the Standby VS to re-learn DHCP and posture information in the case of a switchover… Switch 1 Virtual Switch Switch 2 IP Add 10.10.10.10

172.26.18.2

172.26.19.34

10.10.10.43

DHCP Snooping Binding Table MAC Add 00:50:56:01:e1:02 00:02:b3:3f:3b:99 00:16:a1:c2:ee:32 00:16:cb:03:d3:44 VLAN 10 18 19 10 Interface Po10 Po10 Po20 Po20

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 70

Quality of Service

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 71

Quality of Service Classification & Policing

Both Classification and Policing functions are handled by PFC QoS, and is executed by either the PFC on the Active and Hot Standby Supervisor, or the ingress linecard DFC. There are 2 important caveats which must be understood whilst implementing these functions… 1 Policies must either be applied on L3 interfaces (SVIs or Physical interfaces), or Port Channels. Policies on L2 interfaces are not supported in this release.

policy-map CLASSIFY class class-default set ip dscp 40 interface GigabitEthernet 2/3/48 switchport service-policy input CLASSIFY policy-map CLASSIFY class class-default set ip dscp 40 interface PortChannel 10 switchport service-policy input CLASSIFY

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 72

Quality of Service Classification & Policing

2 Aggregate policers that are applied on SVIs or Port Channels that have interfaces distributed across multiple forwarding engines are subject to Distributed Policing caveats… policy-map POLICE class class-default police average 10000000 Interface GigabitEthernet 1/2/10 channel-group 20 mode desireable Interface GigabitEthernet 2/2/10 channel-group 20 mode desireable interface PortChannel 20 service-policy input POLICE

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 73

Quality of Service QoS on the VSL

The VSL itself has QoS provisioned by default and in the FCS release of the software, it is not configurable. A few important aspects relating to VSL QoS are as follows: 1 2 VSLP and other Control frames are always marked as Priority packets and are always queued and classified as such VSL is always configured as “Trust CoS” and hence ingress queuing is enabled 3 4 Service Policies are not supported on the VSL CoS Maps, Thresholds and Queues are not configurable on the VSL VSL HTTP FTP VSLP Switch 1 Switch 2

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 74

Summary

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 75

Virtual Switching System Deployment Considerations

Virtual Switch will incorporate some deployment considerations as best practice…

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 76

Virtual Switching System Benefits

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 77

Virtual Switching System Summary

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 78

Q and A

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 79

BRKRST-3468 © 2007 Cisco Systems, Inc. All rights reserved.

Cisco Confidential 80