Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

LTRCRS-2004
Cisco Catalyst Virtual Switching System - Instant
Access (VSS - IA) Hands On Lab

LAB GUIDE

Lab Overview
Cisco Catalyst Virtual Switching System (VSS) combined with Instant Access (IA) solution brings
operational simplicity and high availability to the Campus Catalyst Ethernet switching network. It creates a
single Virtual Switch across the distribution and access layers enabling a single network touch point;
ultimately driving simplified operations, distribution layer (Catalyst 6500/6800) features at the access
layer, consistent CLI and lower total cost of ownership (TCO).

The Virtual Switching System (VSS) is an innovative technology that allows the bonding of two VSS-
enabled Catalyst switches chassis such that it is represented as a single logical entity to the rest of the
network from a control plane perspective as well as from a configuration and management standpoint.

The VSS technology provides increased uptime with less configuration complexity by embracing new
innovations in EtherChanneling, NSF/SSO (Non-stop forwarding; stateful switchover) and EFSU
(Enhanced Fast Software Upgrade), whilst replacing the existing reliance on STP, HSRP and Fast
Routing hellos.

Cisco Catalyst Instant Access (IA) brings “fabric extension” (also known as FEX) technology, with high
availability and operational simplicity, to the Catalyst Campus Ethernet Switching line. This technology
creates a single configuration & management environment, across both Distribution and Access-layer

Copyrighted Cisco® Systems Inc. December 2015 1  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

switches and has been specifically tailored to meet the needs of Campus / Enterprise network
deployments.

This demonstration lab was developed to give you hands-on experience with the fundamental simplicity of
provisioning, configuring and managing the VSS and IA solutions.

Product Overview

Cisco Catalyst Virtual Switching System

The Cisco Catalyst 6500/6800 Series Virtual Switching System (VSS) allows the merging of two
physical Cisco Catalyst 6500/6800 Series switches together into a single, logically managed entity.
The figure below graphically represents this concept, where you can manage two Cisco Catalyst
6509 chassis as a single, 18-slot chassis after enabling Cisco Virtual Switching System.

Cisco Virtual Switching System Physical to Logical Representation  

 
Benefits of Catalyst Virtual Switching Systems:

• Increases operational efficiency: By leveraging Multichassis EtherChannel it eliminates the need of

next hop redundancy technologies (HSRP/VRRP/GLBP)
• Boosts nonstop communication: Leverages Multichassis EtherChannel for link failover and
eliminates Layer 2 and 3 protocol reconvergence resulting in a deterministic, subsecond virtual switch
recovery
• Scales system bandwidth capacity: Provides automatic, even load sharing by using all the
available Layer 2 bandwidth across redundant Cisco Catalyst 6500/6800 Series Switches.
• Uses existing multilayer switching architecture: Leverages standards-based 10G connections
between Cisco Catalyst 6500/6800 Series Switches which results in flexible distances between
connections.
• Increases throughput: VSS allows for all uplinks to be active simultaneously.
• Improves resiliency: Leverages technologies like NSF/SSO (Non-stop forwarding; stateful
switchover) and EFSU (Enhanced Fast Software Upgrade)
Copyrighted Cisco® Systems Inc. December 2015 2  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Cisco Catalyst Instant Access

Cisco Catalyst Instant Access enables the merging of physically separate Distribution and Access-layer
switches into a single logical entity, with a single point of configuration, management & troubleshooting,
without the complexities of protocol-based configuration & convergence.

The solution simplifies enterprise campus networks by providing provisioning and operational simplicity.

Benefits of Catalyst Instant Access:

• Single point of configuration and management
• Single software image across distribution & access
• "Plug and Play" provisioning of access switches
• Automatic uplink configuration at the access layer
• Automatic image provisioning of access switches
• Rich Catalyst 6500/6800 feature set across layers

The image below depicts an example of a single touch-point for a 21 Access switch Distribution block
(1008 ports).

 
Starting with version 15.2SY scalability has increased to up to 2,016 ports with specific platforms. For
more specific information please refer to the release notes at www.cisco.com.

Copyrighted Cisco® Systems Inc. December 2015 3  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Topology
POD Assignment
Each POD includes:

1. VSS and IA Parent - Two C6500-E Sup2T VSS distribution-layer switch

2. IA Client – Two stacks of two C6800IA switches

3. Compact Switch (C3560CX-8XPD-S) to be deployed in IA mode

NOTE: Every 2 students will share 1 POD. Each student can work on one 6500/6800 chassis and one IA
stack. You will be assigned a POD number by the proctor.

Lab Topology
Refer to the topology diagram below, for lab use.
 

 
Copyrighted Cisco® Systems Inc. December 2015 4  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Getting Started
This hand on lab consists on two separate sections. In the first section we will provision the VSS system
while in the second section we will configure the Instant Access solution. Please note that VSS needs to
be configured in order to enable Instant Access.

For each of the sections, we will provide a list of exercises together with the information on how to access
the assigned POD

Section 1: Cisco Catalyst Virtual Switching

System (VSS)
Lab Exercises
This section includes the following exercises:

• Lab Exercise 1: VSS Conversion Process

• Lab Exercise 2: Testing VSS Redundancy (optional)

Access your POD

The instructor will provide the lab access information.

Lab Exercise 1: VSS Conversion Process

Exercise Description

The conversion of the two 6500 switches into a single VSS is relatively straightforward and can be
summarized into the following steps:

1. Configure the Virtual Switch Domain on both devices and designate each switch as either Switch
1 or Switch 2
2. Configure the Virtual Switch Links
3. Execute the Conversion command after which the switches will reboot
4. Re-configure Standby Switch’s VSL on the Active Switch and save the configuration

Configuring the Virtual Switch Domain

The Virtual Switch Domain is defined as the grouping of the 2 members of the Virtual Switching System
as is assigned an ID; this ID is configured in global configuration mode and is recommended to be unique
for the Layer 2 network it will be part of. Virtual Switch Domain IDs can be in the range of 1-255, and must
match on both members of the Virtual Switch Domain. Refer to the figure below for more information on
this relationship.

Copyrighted Cisco® Systems Inc. December 2015 5  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Exercise Objective
The objective of this lab is to allow the student experience the simplicity of the VSS conversion as well as
to become familiar with the VSS infrastructure and terminology.
 

NOTE:  For the purposes of this lab, use your Pod number as the Virtual Switch Domain ID.  

Lab Exercise Steps

Step 1 Connect to the console of the two switches you will be converting into VSS
Router>en
Password: lab-cert
Router#

Step 2 We are going to configure the Virtual Switch Domain on both devices using the POD number as
the domain id and we will designate each switch as either Switch 1 or Switch 2. Connect to the
console of the first switch to enter the commands below.
Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#hostname podX-VSS-SW1 ß    configure  hostname  for  easier  identification;  X=POD#  
podX-VSS-SW1(config)#switch virtual domain X ß    configure  the  virtual  switch  domain  with  your  POD  NUMBER
Domain ID X config will take effect only after the exec command 'switch convert mode
virtual' is issued
Copyrighted Cisco® Systems Inc. December 2015 6  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-VSS-SW1(config-vs-domain)#switch 1 ß  we  identify  this  switch  as  switch  #1

podX-VSS-SW1(config-vs-domain)#exit
Step 3 Connect to the console of the second CAT6K switch and enter the commands below on Switch
2:

Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#hostname podX-VSS-SW2 ß    configure  hostname  for  easier  identification;  X=POD#  
Enter configuration commands, one per line. End with CNTL/Z.
podX-VSS-SW2(config)#switch virtual domain X ß    configure  the  virtual  switch  domain  with  your  POD  NUMBER
Domain ID X config will take effect only after the exec command 'switch convert mode
virtual' is issued
podX-VSS-SW2(config-vs-domain)#switch 2 ß  we  identify  this  switch  as  switch  #2
podX-VSS-SW2(config-vs-domain)# exit

Configure the Virtual Switch Link (VSL)

The Virtual Switch Link is a special link, containing one or more physical ports that will allow configuration
and stateful (SSO) information to be exchanged between the two physical switches. The VSL appends a
special header (Virtual Switch Header) onto each frame that is sent across the wire. Refer the figure
below for more details:

Only specific interfaces can be used to form the VSL. For the purposes of this lab, the 10GE uplink ports
on the Supervisor 2T will be used to form the VSL. For complete lists of the interfaces that can be used
for the VSL, consult the VSS Configuration chapters of the 12.2SX, 15..0(1)SY and 15.1(1)SY
Configuration Guides for the Catalyst 6500/6800.

Copyrighted Cisco® Systems Inc. December 2015 7  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 4 In the next two steps we will be configuring the interfaces for VSL and bundle them into a port
channel. Enter the commands below on Switch 1

podX-VSS-SW1(config)#interface port-channel 1
podX-VSS-SW1(config)#no shut
podX-VSS-SW1(config-if)#switch virtual link 1
podX-VSS-SW1(config-if)#exit
podX-VSS-SW1(config)#interface range tenGigabitEthernet 1/4 - 5
podX-VSS-SW1(config-if-range)#no shut
podX-VSS-SW1(config-if-range)#channel-group 1 mode on
podX-VSS-SW1(config-if-range)#end

NOTE: The Supervisor 2T comes with 3 x 1G (1/1,1/2 and 1/3) and 2 x 10Gig uplink interfaces (Ten1/4
and Ten1/5). For the VSL configuration we are using the 2 x 10G uplinks.

Step 5 We will now be creating the VSL interfaces in the second switch. Enter the commands below on
Switch 2

podX-VSS-SW2(config)#  interface port-channel 2

podX-VSS-SW2(config-if)#no shut
podX-VSS-SW2(config-if)#switch virtual link 2
podX-VSS-SW2(config-if)#exit
podX-VSS-SW2(config)#interface range tenGigabitEthernet 1/4 – 5
podX-VSS-SW2(config-if-range)#no shut
podX-VSS-SW2(config-if-range)#channel-group 2 mode on
podX-VSS-SW2(config-if-range)#end

podX-VSS-SW2#show etherchannel summary ß  verify  that  the  port-­‐channel  is  up

<..snip..>
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
2 Po2(RU) - Te1/4(P) Te1/5(P)
<..snip..>

Executing the Conversion

To proceed with the conversion process, execute the “switch convert mode virtual” command in
enable mode. By doing so, it will convert the interface names to a 3-numbered notation (switch-
number/slot/port), save the configuration and reload the switch. The reload is necessary for a few
reasons:

• The merging of the 2 configurations into a single configuration

• The re-numbering of port conventions from slot/port to switch-number/slot/port
• The negotiation of Active/Standby role through NSF/SSO which only occurs on bootup

Step 6 In the next two steps we will be converting the two standalone chassis into VSS mode. That is,
we will first save the configuration and we will then enter the commands for the VSS conversion:

podX-VSS-SW1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-VSS-SW1(config)#  boot sys bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin ß  set    
                                               the  boot  variable  for  the  current  IOS  version)
Copyrighted Cisco® Systems Inc. December 2015 8  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-VSS-SW1(config)#end

podX-VSS-SW1#wr mem
Destination filename [startup-config]? ß  Press  <ENTER>  to  accept  the  destination  filename
Building configuration...
[OK]
podX-VSS-SW1#

podX-VSS-SW1#switch convert mode virtual ß  note  that  we  are  in  enable  mode
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 ß  accept  the  reload
Converting interface names
Building configuration...
<..snip..>
Destination filename [startup-config.converted_vs-20140325-123157]? Enter ß  accept    
 
Step 7 We will now proceed with the conversion of switch 2. First we will save the configuration and
then we will proceed with conversion of switch 2:

podX-VSS-SW2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-VSS-SW2(config)#  boot sys bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.binß  set    
                                               the  boot  variable  for  the  current  IOS  version)
podX-VSS-SW2(config)#end
podX-VSS-SW2#wr mem
Destination filename [startup-config]?
Building configuration...
[OK]
podX-VSS-SW2#

podX-VSS-SW2#switch convert mode virtual ß  note  that  we  are  in  enable  mode
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 ß  accept  the  reload
Converting interface names
Building configuration...
<..snip..>
Destination filename [startup-config.converted_vs-20140325-123157]? Enter ß  accept  

Step 8 At this stage, you will observe the reboot messages scrolling across the screen. On switch 1:
Initializing ATA monitor library...

bootdisk:s2t54-adventerprisek9-mz.SPA.151-2.SY3.bin: Digitally Signed Release Software

with key version A

Self extracting the image... [OK]

<…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
Initializing as Virtual Switch ACTIVE processor

Copyrighted Cisco® Systems Inc. December 2015 9  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

<…snip…>

*Oct 11 13:38:07.571: %VSL_BRINGUP-6-MODULE_UP: VSL module in slot 1 switch 1 brought

up
*Oct 11 13:38:44.959: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE by VSLP

Step 9 Observe the reboot messages on switch 2. As you can see in the output below, each switch
reboots independently, but during the boot process, the configuration is pre-parsed to detect
which interfaces form the VSL. The switch will then negotiate Active and Standby roles using
VSL Protocol (VSLP) and will continue the boot up process.

Initializing ATA monitor library...

bootdisk:s2t54-adventerprisek9-mz.SPA.151-1.SY3.bin: Digitally Signed Release Software

with key version A

Self extracting the image... [OK]

<…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
Initializing as Virtual Switch STANDBY processor

<…snip…>
*Oct 11 13:31:45.555: %VSL_BRINGUP-6-MODULE_UP: VSL module in slot 1 switch 2 brought
up
*Oct 11 13:32:19.323: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP

Step 10 Upon the completion of the bootup process, you will notice that only the Active switch (Switch 1
in this case) CLI is accessible. Switch 2’s console is no longer available, since all management
and troubleshooting can be accomplished on the Active Switch’s console. Also note that the
prompt of Switch 2 has changed:

podX-VSS-SW1-sdby>
Standby console disabled

podX-VSS-SW1-sdby>
Standby console disabled

podX-VSS-SW1-sdby>
Standby console disabled

podX-VSS-SW1-sdby>

Step 11 CONGRATULATIONS!! At this stage, both 6500 switches have been converted into a single
Virtual Switching System, so you might want to rename your newly-configured VSS device and
proceed to save the configuration:
podX-VSS-SW1>en
Password:
podX-VSS-SW1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-VSS-SW1(config)#hostname podX-vss ß X is POD number, eg. POD #1 would be pod1-vss
podX-vss(config)#exit

Copyrighted Cisco® Systems Inc. December 2015 10  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss#
00:13:40: %SYS-5-CONFIG_I: Configured from console by console
podX-vss#
podX-vss#wr mem
Building configuration...
[OK]
podX-vss#

NOTE: Configuration changes cannot be made till the two switches and Line cards have completely
come online and the two supervisors are in complete SSO sync them.

podX-VSS-SW1#conf t
Config mode cannot be entered during Standby initialization

After the conversion process, you can now take some time to get familiar with the Virtual Switch System
environment. First, you can verify the modules you now have control of from the Active Virtual Switch:

podX-vss#show module switch 1 ß “switch” keyword has been added to select either Switch 1 or Switch 2 of the VSS
Switch Number: 1 Role: Virtual Switch Active
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL16052XQX
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL1019MC05
4 20 DCEF2T 4 port 40GE / 16 port 10GE C6800-16P10G-XL SAL1834ZAKB

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 588d.098a.c5ad to 588d.098a.c5b4 1.2 12.2(50r)SYS 15.2(1)SY1 Ok
2 0017.95b8.087c to 0017.95b8.087f 2.2 12.2(14r)S5 15.2(1)SY1 Ok
4 1005.caea.d482 to 1005.caea.d495 1.0 15.1(58r)SYL 15.2(1)SY1 Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 4 VS-F6K-PFC4 SAL16052UGC 1.1 Ok
1 CPU Daughterboard VS-F6K-MSFC5 SAL16052SLX 1.3 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAL1121PPJG 3.1 Ok
4 Distributed Forwarding Card C6800-DFC-XL SAL1834ZAKB 1.0 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass
4 Pass

podX-vss#sh module switch 2 ß new “switch” keyword has been added to select either Switch 1 or Switch 2 of the VSS
Switch Number: 2 Role: Virtual Switch Standby
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Hot) VS-SUP2T-10G SAL16127TU2
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL08435CUF
4 20 DCEF2T 4 port 40GE / 16 port 10GE C6800-16P10G SAL1834ZAA7

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
Copyrighted Cisco® Systems Inc. December 2015 11  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

1 588d.09e6.d652 to 588d.09e6.d659 1.3 12.2(50r)SYS 15.2(1)SY1 Ok

2 0012.4301.c524 to 0012.4301.c527 2.0 12.2(14r)S5 15.2(1)SY1 Ok
4 1005.caea.d356 to 1005.caea.d369 1.0 15.1(58r)SYL 15.2(1)SY1 Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 4 VS-F6K-PFC4 SAL16127M2D 1.2 Ok
1 CPU Daughterboard VS-F6K-MSFC5 SAL16127W7F 1.4 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAD0804067A 2.0 Ok
4 Distributed Forwarding Card C6800-DFC SAL1834ZAA7 1.0 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass
4 Pass

NOTE: If you run these commands before the initialization process is completed, some modules with
show up with “Unknown”

Step 12 The same “switch” keyword can be used for others commands like “show running-configuration”.
In this step we will be checking the configuration for SW1 and SW2 (and we will do this from the
VSS active):

podX-vss#sh run switch 1 ß Checking the configuration for SW1

Building configuration...

Current configuration : 1963 bytes

!
interface GigabitEthernet1/1/1 ß Note interface number starts with “1” being SW#1
no switchport
no ip address
shutdown
!
interface GigabitEthernet1/1/2
no switchport
no ip address
shutdown
!
interface GigabitEthernet1/1/3
no switchport
no ip address
shutdown
!
interface TenGigabitEthernet1/1/4
no switchport
no ip address
no cdp enable
channel-group 1 mode on
!
!
<…snip…>

Copyrighted Cisco® Systems Inc. December 2015 12  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss#sh run switch 2 ß Checking the configuration for SW2

Building configuration...

Current configuration : 1963 bytes

!
interface GigabitEthernet2/1/1 ß Note interface number starts with “2” being SW#2
no switchport
no ip address
shutdown
!
interface GigabitEthernet2/1/2
no switchport
no ip address
shutdown
!
interface GigabitEthernet2/1/3
no switchport
no ip address
shutdown
!
<…snip…>

Step 13 Verify the status of the VSS:

podX-vss#sh switch virtual
Switch mode : Virtual Switch
Virtual switch domain number : X ß X is your POD number
Local switch number : 1
Local switch operational role: Virtual Switch Active
Peer switch number : 2
Peer switch operational role : Virtual Switch Standby

podX-vss#sh switch virtual link

VSL Status : UP
VSL Uptime : 8 minutes
VSL SCP Ping : Pass
VSL ICC Ping : Pass
VSL Control Link : Te1/1/5 ß The VSL Control Link may vary: you will see Te1/1/5 or Te1/1/4
VSL Encryption : Configured Mode - Off, Operational Mode – Off

podX-vss#sh switch virtual role

RRP information for Instance 1
--------------------------------------------------------------------
Valid Flags Peer Preferred Reserved
Count Peer Peer
--------------------------------------------------------------------
TRUE V 1 1 1

Switch Switch Status Priority Role Local Remote

Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1 UP 100(100) ACTIVE 0 0
REMOTE 2 UP 100(100) STANDBY 5016 887

Peer 0 represents the local switch

Flags : V - Valid

In dual-active recovery mode: No

Copyrighted Cisco® Systems Inc. December 2015 13  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 14 Configuring the VSS for connectivity: Now that you have your Pod converted to VSS mode, we
should complete the remainder of the configuration for connectivity to the rest of the network.
The following diagram depicts the layout of your Pod, where X represents your Pod number.

Step 15 The next steps will take place in Virtual Switching System: first we set up a loopback address for
routing purposes

NOTE: Replace X with your pod’s ID. Pod’s ID can be captured from Host name (“ podX-vss” ) of
devices your logged-in

podX-vss#config t
podX-vss(config)#interface loopback 0
podX-vss(config-if)#ip address 1X.1X.1X.1X 255.255.255.255 ß    X  is  POD  number
podX-vss(config-if)#exit

Step 16 Also in the Virtual Switching System, we will set up the Port Channel interface and its
associated members that connect to the Core switch

podX-vss(config)#interface port-channel X0 ß X is POD number, eg, POD1, it will be interface port-channel 10

podX-vss(config-if)#no shut
podX-vss(config-if)#ip address 10.252.X.2 255.255.255.0 ß X is POD number
podX-vss(config-if)#exit
podX-vss(config)#interface range tenGigabitEthernet 1/2/1,tenGigabitEthernet 2/2/1
podX-vss(config-if-range)#no shut
podX-vss(config-if-range)#channel-group X0 mode desirable ß X is POD number
podX-vss(config-if-range)#exit

Step 17 Next, we configure OSPF as the routing protocol to peer to the Core switch, and enable NSF:
podX-vss(config)#router ospf 10
podX-vss(config-router)#network 1X.1X.1X.1X 0.0.0.0 area 0 ß X is POD number
podX-vss(config-router)#network 10.252.0.0 0.0.255.255 area 0

Copyrighted Cisco® Systems Inc. December 2015 14  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss(config-router)#exit

Step 18 Still in the Virtual Switching System configure connectivity to the 4948-10G as a Layer 3
Etherchannel:
podX-vss(config)#interface range tenGigabitEthernet 1/2/2,tenGigabitEthernet 2/2/2
podX-vss(config-if-range)#no shut
podX-vss(config-if-range)#no switchport
podX-vss(config-if-range)#channel-group 3 mode on
podX-vss(config-if-range)#exit
podX-vss(config)#int port-channel 3
Creating a port-channel interface Port-channel 3
podX-vss(config-if)#no shut
podX-vss(config-if)#no switchport
podX-vss(config-if)#ip address 10.252.5X.1 255.255.255.0 ß X is POD number
podX-vss(config-if)#end
podX-vss#wr mem

Step 19 Now we are going to proceed to configure the 4948-10G to setup the connectivity to the VSS in
your POD as Layer 3 Etherchannel. Connect to the console of the 4948-10G switch and enter
the following commands:

Switch>en
Password: lab-cert

Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)#hostname podX-4948-sw ß X is POD number

pod1-49480-sw(config)#

podX-4948-sw(config)#interface port-channel 3
podX-4948-sw(config-if)#no shut
podX-4948-sw(config-if)#no switchport
podX-4948-sw(config-if)#ip address 10.252.5X.2 255.255.255.0 ß    X  is  POD  number
podX-4948-sw(config-if)#exit

podX-4948-sw(config)#interface range tenGigabitEthernet 1/49 – 50

podX-4948-sw(config-if-range)#no switchport
podX-4948-sw(config-if-range)#no shut
podX-4948-sw(config-if-range)#channel-group 3 mode on
podX-4948-sw(config-if-range)#exit
podX-4948-sw(config)#ip route 100.100.100.100 255.255.255.255 10.252.5X.1 ß    X  is  POD  number

Step 20 You can now verify connectivity of the 4948-10G by pinging its default gateway on the VSS and
by pinging the core:

podX-4948-sw#ping 10.252.5X.1 ß    X  is  POD  number

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.252.5X.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

podX-4948-sw#ping 100.100.100.100

Type escape sequence to abort.

Copyrighted Cisco® Systems Inc. December 2015 15  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Sending 5, 100-byte ICMP Echos to 100.100.100.100, timeout is 2 seconds:

!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

 
Step 21 We will proceed to enable the IP address for management in the VSS pair so that we can use
telnet to access the VSS distribution in the next section:  

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

podX-vss#conf t
podX-vss(config)#vlan 100 ß  add  management  vlan
podX-vss(config)#exit
% Applying VLAN changes may take few minutes. Please wait...

podX-vss(config)#int range gig 1/1/1, gig 2/1/1

podX-vss(config-if)#switchport
podX-vss(config-if)#switchport mode access
podX-vss(config-if)#switchport access vlan 100 ß  management  vlan  configured  above
podX-vss(config-if)#no shutdown
podX-vss(config-if)#exit

podX-vss(config)#int vlan 100

podX-vss(config-if)#ip address 128.107.65.63+X 255.255.255.0 ß  X  is  the  POD#
podX-vss(config-if)#no shut
podX-vss(config-if)#exit
podX-vss(config)#  ip route 0.0.0.0 0.0.0.0 128.107.65.125 ß  route  for  management  interface
podX-vss(config)#line vty 0 4 ß  we  will  set  password  for  telnet  access
podX-vss(config-line)#password labops
podX-vss(config-line)#end
podX-vss# wr mem ß  save  the  configuration  
 
Step 22 We will proceed to enable the IP address for management for the CAT-4948 so that we can use
telnet to access in the next section:  
 
podX-4948-sw#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-4948-sw(config)#int gigabitEthernet 1/3
podX-4948-sw(config-if)#no switchport
podX-4948-sw(config-if)#ip address 128.107.65.80+X 255.255.255.0 ß  X  is  the  POD#
podX-4948-sw(config-if)#no shut
podX-4948-sw(config-if)#exit
podX-4948-sw(config)#ip route 0.0.0.0 0.0.0.0 128.107.65.125
podX-4948-sw(config)#line vty 0 4
podX-4948-sw(config-line)#password labops
podX-4948-sw(config-line)#end
pod1-4948-sw#wri mem

Step 23 You can confirm the correct configuration of the management IP address with the commands
below (you can also try to access the VSS pair directly via telnet using the MGMT IP address in
the table provided in “Access to the Lab” section”):  
 
podX-vss#show run int gig 1/1/1
Building configuration...

Current configuration : 102 bytes

!
interface GigabitEthernet1/1/1
switchport
Copyrighted Cisco® Systems Inc. December 2015 16  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

switchport access vlan 100

switchport mode access
end

podX-vss#show run int gig 2/1/1

Building configuration...

Current configuration : 102 bytes

!
interface GigabitEthernet2/1/1
switchport
switchport access vlan 100
switchport mode access
end

podX-vss#show run int vlan 100

Building configuration...

Current configuration : 65 bytes

!
interface Vlan100
ip address 128.107.65.63+X 255.255.255.128 ß  X  is  the  POD#
end

pod6-vss#show ip int br | i Vlan100

Vlan100 128.107.65.63+X YES NVRAM up up ß  X  is  the  POD#

 
Step 24 The next exercise in this section, Exercise #2, is optional. If you are planning on doing
Exercise #2 please skip this step (it will be taken care of when doing the exercise).
Otherwise, please configure NSF (Non Stop Forwarding) for the OSPF process. NSF must be
explicitly configured:  

podX-vss#conf t
podX-vss(config)#router ospf 10
podX-vss(config-router)#nsf
podX-vss(config-router)#end
podX-vss#show run partition router ospf 10
<..snip..>
router ospf 10
nsf
network 10.252.0.0 0.0.255.255 area 0
network 1X.1X.1X.1X 0.0.0.0 area 0 ß  X  is  the  POD#
!
!
end
podX-vss#write mem ß  Save  your  configuration  

þ End of Exercise: You have successfully completed this exercise!

Save your configuration and proceed to the next section…

Copyrighted Cisco® Systems Inc. December 2015 17  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 2: Testing VSS Redundancy (Optional)

Exercise Description

Now that you have your Pod all up and running, it’s time to break it and see how it behaves. We will
examine 3 different failure scenarios and verify the effect on traffic as it passes through the VSS domain.
We will be performing the following tests:

• Access Switch Uplink Failure

• Core Uplink Failure

• Switch Failure

Exercise Objective
The objective of this section is to verify how well a VSS environment handles anomalies in the network.

Lab Exercise Steps

Step 1 First we will ensure that you have connectivity to a Loopback on the vsslab-core from the 4948
podX-4948-sw#ping 100.100.100.100

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 100.100.100.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

NOTE: You will be using extended ping on the 4948 as your testing mechanism for this exercise
 

Step 2 The first test will be the Access Switch Uplink Failure. In this test, we will test the uplink failure
that connects the 4948-10G to the VSS.
Have your 4948 configured as follows, but do not accept “Sweep range of sizes [n]:” until
you are ready to shut down your first interface of the test. We will generate traffic via this
ping sweep and let it run until it finishes.

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß DO NOT accept right now. Leave it ready for next step

Copyrighted Cisco® Systems Inc. December 2015 18  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 3 On the VSS issue the following command to determine which interfaces to shut down:
podX-vss#show etherchannel 3 summary | beg Number ß portchannel to the 4948 access switch
Number of channel-groups in use: 4
Number of aggregators: 4

Group Port-channel Protocol Ports

------+-------------+-----------+--------------------------------------------
3 Po3(RU) - Te1/2/2(P) Te2/2/2(P) ß The output you want to see is (RU)
for Po3 and (P) for the interfaces

Step 4 You can now proceed to shut/no shut each of the above member ports and verify the traffic loss
experienced when this action is issued. You should notice the traffic loss to be minimal – at
most 1 or 2 ping losses. We are also going to start the <ping> from step above.

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß    accept  the  ping  in  the  4948  

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#interface tengigabitEthernet 1/2/2
podX-vss(config-if)#shut ß  shut  one  interface  connecting  to  the  access  switch
podX-vss(config-if)#no shut ß  no  shut  one  interface  connecting  to  the  access  switch
podX-vss(config-if)#exit
podX-vss(config)#interface tengigabitEthernet 2/2/2
podX-vss(config-if)#shut ß  shut  the  other  interface  connecting  to  the  access  switch
podX-vss(config-if)#no shut ß  no  shut  the  other  interface  connecting  to  the  access  switch
podX-vss(config-if)#end

Step 5 Check the output of the ping command in the 4948 and you will see that packet loss in minimal
<..snip..>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 99 percent (39999/40000), round-trip min/avg/max = 1/1/168 ms podX-
4948-sw#

Step 6 The second test will be the core uplink failure. We will perform a similar test as above, but this
time, we will test the re-convergence between the VSS and the Core Switch, by shut/no shut the
member interfaces of the EtherChannel connecting the 2 devices.
Have your 4948 configured as follows, but do not accept “Sweep range of sizes [n]:” until
you are ready to shut down your first interface of the test:

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Copyrighted Cisco® Systems Inc. December 2015 19  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Extended commands [n]:

Sweep range of sizes [n]: ß DO NOT accept right now. Leave it ready for next step

Step 7 To determine which member interfaces make up this bundle, you can execute the following
command, replacing the ‘X’ in the port channel number with your own Pod assignment.
We will also accept the ping from the step above. Let it run until it finishes. Once again, you
should notice that by shut/no-shutting these member interfaces, the loss on the 4948 is also
minimal.

podX-vss#sh etherchannel X0 sum | begin Group ß    portchannel  to  the  core    switch  /  X  is  the  POD#
Group Port-channel Protocol Ports
------+-------------+-----------+--------------------------------------------
10 Pox(RU) PAgP Te1/2/1(P) Te2/2/1(P) ß  X  is  the  POD#

Last applied Hash Distribution Algorithm: Adaptive

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß    accept  the  ping  in  the  4948  

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#interface tengigabitEthernet 1/2/1
podX-vss(config-if)#shut ß  shut  one  interface  connecting  to  the  core  switch
podX-vss(config-if)#no shut ß  no  shut  one  interface  connecting  to  the  core  switch
podX-vss(config-if)#exit
podX-vss(config)#interface tengigabitEthernet 2/2/1
podX-vss(config-if)#shut ß  shut  the  other  interface  connecting  to  the  core  switch
podX-vss(config-if)#no shut ß  no  shut  the  other  interface  connecting  to  the  core  switch
podX-vss(config-if)#end

Step 8 Check the output of the ping command in the 4948 and you will see that packet loss in minimal

<..snip..>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 99 percent (39999/40000), round-trip min/avg/max = 1/1/1412 ms
podX-4948-sw#

Step 9 The third test will be the switch failure. This exercise will involve the complete switchover of the
active Supervisor (switch) by reloading the box. First, we can identify which particular switch is
the active switch and the code level that is in operation, by executing the following commands:

podX-vss#sh switch virtual

Switch mode : Virtual Switch
Virtual switch domain number : X ß  X  is  the  POD#
Local switch number : 1
Copyrighted Cisco® Systems Inc. December 2015 20  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Local switch operational role: Virtual Switch Active

Peer switch number : 2
Peer switch operational role : Virtual Switch Standby
Step 10 In the above output, we can see that Switch 1 is the Active switch and Switch 2 is the Standby
member of the Virtual Switching System. Furthermore, if we inspect the following output we can
also note the individual configured and operating priorities:

podX-vss#sh switch virtual role

<..snip..>
Switch Switch Status Priority Role Local Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 1 UP 100(100) ACTIVE 0 0
REMOTE 2 UP 100(100) STANDBY 9149 7484

<..snip..>
In dual-active recovery mode: No

Step 11 Have your 4948 configured as follows, but do not accept “Sweep range of sizes [n]:” until
you are ready to accept the reload:

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß DO NOT accept right now. Leave it ready for next step

Step 12 We can now proceed to reload the Active Virtual Switch by executing the command below. We
will also be starting the <ping> from the step above:

podX-vss#redundancy reload shelf 1

System configuration has been modified. Save? [yes/no]:yes ß  Save  configuration
Reload this shelf [confirm] ß  Confirm  reload  
Preparing to reload this shelf

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß    accept  the  ping  in  the  4948

Step 13 Once again, if you are observing the ping results on the 4948, you should notice only 1 or 2
packets lost as a result of this operation.
If you lost more than 1 or 2 packets, check to see how many packets you lost by looking at the
“Success rate” information at the end of the extended ping. Note how many packets you
lost. Why do you think this happened?

Copyrighted Cisco® Systems Inc. December 2015 21  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Here is a clue: check your OSPF configuration with the “show run partition router
ospf 10” command. Is anything missing that could have prevented these packet drops?
We’ll fix this in a minute.

Step 14 Now that the console of Switch 2 is active, you are able to execute the following commands:

podX-vss#sh switch virtual

witch mode : Virtual Switch
Virtual switch domain number : X ß X is the POD#
Local switch number : 2
Local switch operational role: Virtual Switch Active

podX-vss#sh switch virtual role

<..snip..>

Switch Switch Status Priority Role Local Remote

Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 2 UP 100(100) ACTIVE 0 0

In dual-active recovery mode: No

Step 15 Shortly after this, Switch 1 will complete the bootup process and assume a Standby role after it
has completed being brought up:

podX-vss#sh switch virtual

Switch mode : Virtual Switch
Virtual switch domain number : X ß  X  is  the  POD#
Local switch number : 2
Local switch operational role: Virtual Switch Active
Peer switch number : 1 ß  SW1  is  now  standby
Peer switch operational role : Virtual Switch Standby

podX-vss#sh switch virtual role

<..snip..>
Switch Switch Status Priority Role Local Remote
Number Oper(Conf) SID SID
--------------------------------------------------------------------
LOCAL 2 UP 100(100) ACTIVE 0 0
REMOTE 1 UP 100(100) STANDBY 2038 8419

In dual-active recovery mode: No

NOTE: It is OK if the Session IDs are different on your pod

 

Copyrighted Cisco® Systems Inc. December 2015 22  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 16 Now, let’s fix the packet drop issue. Going back to the “show run partition router ospf
10” command, your output should look something like this:

podX-vss#show run partition router ospf 10

Building configuration...

Current configuration : 151 bytes

!
Configuration of Partition - router ospf 10
!
!
!
router ospf 10
network 10.252.0.0 0.0.255.255 area 0
network 1X.1X.1X.1X 0.0.0.0 area 0 ß  X  is  the  POD#
!
!
end

Step 17 What is missing is NSF (Non Stop Forwarding). Remember that NSF must be explicitly
configured, but we forgot to do this when we did the initial ospf configuration in Exercise 1.
Therefore we will do it in this step. You should then see nsf in the ospf configuration.

podX-vss#conf t
podX-vss(config)#router ospf 10
podX-vss(config-router)#nsf
podX-vss(config-router)#end
podX-vss#show run partition router ospf 10
<..snip..>
router ospf 10
nsf
network 10.252.0.0 0.0.255.255 area 0
network 1X.1X.1X.1X 0.0.0.0 area 0 ß  X  is  the  POD#
!
!
end
podX-vss#write mem ß  Save  your  configuration  
 
Step 18 Check that your VSS system is in SSO and that the second switch is ready for the switchover

podX-vss#show switch virtual redundancy

My Switch Id = 2
Peer Switch Id = 1
Last switchover reason = user forced
Configured Redundancy Mode = sso
Operating Redundancy Mode = sso

Switch 1 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = ACTIVE
Uptime in current state = 3 days, 17 hours, 37 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-
ADVENTERPRISEK9-M), Version 15.1(2)SY3, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Thu 28-Nov-13 12:58 by prod_rel_team
BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.151-
2.SY3.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.151-2.SY4.bin,12;
Copyrighted Cisco® Systems Inc. December 2015 23  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = ACTIVE

Switch 2 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = STANDBY HOT (switchover target)
Uptime in current state = 3 days, 17 hours, 32 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-
ADVENTERPRISEK9-M), Version 15.1(2)SY3, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Thu 28-Nov-13 12:58 by prod_rel_team
BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.151-
2.SY3.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.151-2.SY4.bin,12;
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = STANDBY

Step 19 Have your 4948 configured as follows, but do not accept “Sweep range of sizes [n]:” until you
are ready to accept the reload:

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß DO NOT accept right now. Leave it ready for next step

Step 20 We can now proceed to reload the Active Virtual Switch by executing the command below. We
will also start the <ping> from step above:

podX-vss#redundancy reload shelf 2

System configuration has been modified. Save? [yes/no]:yes ß  Save  configuration  if  asked
Reload this shelf [confirm] ß  Confirm  reload  
Preparing to reload this shelf

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 100.100.100.100
Repeat count [5]: 40000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß    accept  the  ping  in  the  4948

Copyrighted Cisco® Systems Inc. December 2015 24  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 21 How many pings were dropped this time? With NSF enabled, the hardware forwarding table is
maintained while the software forwarding table is rebuilt. Once the software table is complete,
only incremental changes are made to the hardware forwarding changes. Since none of our
forwarding entries changed, the only packet loss is associated with the switchover of traffic in
the MEC, if that needs to happen. Since that is a sub-second process, there should only be
1 or 2 pings lost at most.

Type escape sequence to abort.

Sending 40000, 100-byte ICMP Echos to 100.100.100.100, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (40000/40000), round-trip min/avg/max = 1/1/28 ms

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…
 

Copyrighted Cisco® Systems Inc. December 2015 25  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Section 2: Cisco Catalyst Instant Access (IA)

Lab Exercises
This section includes the following exercises:

• Lab Exercise 1: Provisioning Instant Access (C6800IA) - Configuration and Verification

• Lab Exercise 2: Single Point of Management - IA clients managed on distribution VSS

• Lab Exercise 3: Provisioning additional C6800IA stack members and verification

• Lab Exercise 4: C6800IA Host ports configuration and verification of traffic

• Lab Exercise 5: Provisioning of additional Fabric Links.

• Lab Exercise 6: Adding a Compact Switch as Instant Access Client.

• Lab Exercise 7: Fabric Link Failure and Recovery (MEC Convergence)

• Lab Exercise 8: Enhanced Fast Software Upgrade Process (EFSU)

Access your POD

The instructor will provide the lab access information.

Lab Exercise 1: Provisioning Instant Access Client

(C6800IA)
Exercise Description

In this lab exercise, each student will automatically provision their IA Client in 2 simple steps, using 2 new
CLI commands, directly on the C6K VSS.
1. Create the Port-channel to connect the fabric links to the IA client…
1.1. Set the Port-channel to operate in FEX mode
1.2. Associate a unique FEX ID to the Port-channel
2. Associating the physical fabric links to the Port-channel created in Step 1
Throughout this section we will be configuring and using the topology below:

 
 
 

Copyrighted Cisco® Systems Inc. December 2015 26  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

 
 

NOTE: Both students will be working simultaneously in this lab since there’s one IA stack per student.
We are going to use 2 x FEX ID’s = FEX 101 (student 1) and FEX 102 (student 2).
During the steps we will be referring to FEX 10Z; Z=1 for student 1 and Z=2 for student 2
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask intructors IP addresses and
credentials).
 

Exercise Objective
The objective of this exercise is to demonstrate the overall simplicity of the IA solution, where the access
devices get provisioned automatically, without any direct console access or manual configuration at
access layer.

This exercise will also demonstrate that the only “work” required is a physical (L1) connection between
the IA Parent & IA Client switches, and 2 simple configuration steps on the IA Parent.

Copyrighted Cisco® Systems Inc. December 2015 27  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise Steps

Step 1 We are now going to create the Port-channel to be used for the fabric links to the IA client. We
will then set it to FEX mode and associate a unique FEX ID

NOTE: Both students will be working simultaneously in this lab since there’s one IA stack per student.
We are going to use 2 x FEX ID’s = FEX101 (student 1) and FEX 102 (student 2).
During the steps we will be referring to FEX 10Z; Z=1 for student 1 and Z=2 for student 2
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask instructors for IP addresses and
credentials).
 

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#interface port-channel 10Z ß  Create  a  PortChannel    (Z=1  for  student  1  and    
slno  Z=2  for  student  2)  
 

podX-vss(config-if)#switchport
podX-vss(config-if)#switchport mode fex-fabric ß  Enables  Fex  fabric
All extraneous configs removed from interface Port-channel101!
podX-vss(config-if)#fex associate 10Z ß  Associate  FEX-­‐ID  to  Port  Channel  (Z=1  for  student  1  and    
 Z=2  for  student  2)  
 
podX-vss(config-if)#load-interval 30 ß  To  verify  traffic  stats  in  30s  interval
podX-vss(config-if)#no shut
podX-vss(config-if)#end

Step 2 Associate the Port-channel interface with its Physical member interface

podX-vss#conf t
podX-vss(config)#interface TenGigabitEthernet 1/4/4+Z ß    port  connected  to  FEX  ;  Z=1  for  student  1  and    
 Z=2  for  student  2)  
podX-vss(config-if)#switchport  
podX-vss(config-if)#switchport mode fex-fabric  
All extraneous configs removed from interface TenGigabitEthernet1/4/4+Z

podX-vss(config-if)#channel-group 10Z mode on ß  Associate  Physical  port  to  Port  Channel;  Z=1  for  student  1  and    
 Z=2  for  student  2)  
podX-vss(config-if)#no shut
podX-vss(config-if)#end

NOTE: We are associating only one TenGig interface to the Port-channel for this exercise. Only one
physical link is required for IA to operate. We will add the other TenGig interface in a later exercise (for 2
x 10G fabric links), to demonstrate the simplicity of provisioning additional fabric link bandwidth.

Copyrighted Cisco® Systems Inc. December 2015 28  

 Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 3 Verify if the IA Client is provisioned over the TenGigabitEthernet link and bound to the IA Parent

podX-vss#show interface fex-fabric

Fabric Fabric Port FEX FEX
FEX Port State Uplink Model Serial
---------------------------------------------------------------------
101 Te1/4/5 bound Te1/0/1 C6800IA-48TD FOC1737W0PS
102 Te1/4/6 bound Te2/0/1 C6800IA-48TD FOC1737S245

podX-vss#show fex 10Z detail ß  Z=1  for  student  1  and  Z=2  for  student  2  
FEX: 10Z Description: FEX010Z state: online ß  Indicates  the  IA  status  (*)
FEX version: 15.0(2)EX5
Extender Model: C6800IA-48TD, Extender Serial: FOC1737W0PS
FCP ready: yes

Image Version Check: enforced

Fabric Portchannel Ports: 1
Fabric port for control traffic: Te1/4/5
Fabric interface state:
Po101 - Interface Up.
Te1/4/4+Z - Interface Up. state: bound ß  Indicates  the  fabric  link  is  in  operational  state

(*) NOTE: You might see other states (e.g. “state: connected”) before you see “state: online”
(*) NOTE: The output above is for FEX101. Student 2 will have a slightly different output

Step 4 Get familiar with new “fex” commands in the VSS pair

podX-vss#show interface fex-fabric

Fabric Fabric Port FEX FEX
FEX Port State Uplink Model Serial
---------------------------------------------------------------------
101 Te1/4/5 bound Te1/0/1 C6800IA-48TD FOC1737W0PS
102 Te1/4/6 bound Te2/0/1 C6800IA-48TD FOC1737S245

podX-vss#show fex
FEX FEX FEX FEX
Number Description State Model Serial
---------------------------------------------------------------------------
101 FEX0101 online C6800IA-48TD FOC1737W0PS
102 FEX0102 online C6800IA-48TD FOC1737S245

Copyrighted Cisco® Systems Inc. December 2015 29  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Optional Exercise Steps

Step 1 (Optional) IA also allows you to pre-provision a new FEX even before physically connecting it to
the parent C6K VSS. Below is an example of pre-provisioning a new FEX client, with 2 stack
members. Use the following command to pre-provision at the enable prompt (not config prompt)
 
podX-vss# module provision create fex 15Z type C6800IA-48TD slot 1 ß  Z=1  for  student  1  and    
   Z=2  for  student  2  
FEX 15Z slot 1 module provisioning entry added. ß  Pre-­‐Provisions  FEX  15Z  in  as  stack  member  1  

podX-vss#module provision create fex 15Z type C6800IA-48TD slot 2 ß  Z=1  for  student  1  and    
   Z=2  for  student  2  
FEX 15Z slot 2 module provisioning entry added. ß  Pre-­‐Provisions  FEX  15Z  in  as  stack  member  2

podX-vss#show run fex 15Z ß  Z=1  for  student  1  and  Z=2  for  student  2.  Show  run  fex  confirms  the  pre-­‐provisioning,  and  now    
all  IA  hosts  ports  can  be  configured  at  this  point.  
Building configuration...

Current configuration : 11795 bytes

!
interface GigabitEthernet15Z/1/0/1
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto
shutdown
!
interface GigabitEthernet15Z/1/0/2
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto
shutdown
!

podX-vss#show run fex 15Z mod 2 ß  Z=1  for  student  1  and  Z=2  for  student  2.  Show  interfaces  in  the  second  member  
of  the  FEX  stack  
Building configuration...

Current configuration : 5900 bytes

!
interface GigabitEthernet151/2/0/1
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto
shutdown
!

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

Copyrighted Cisco® Systems Inc. December 2015 30  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 2: Single Point of Management

Exercise Description
In this lab exercise, each student will verify that all interfaces on the IA Clients are available to the IA
Parent. Hence, the student will be able to configure and monitor all of the IA Client interfaces entirely from
the IA Parent.
Each IA Client operates and behaves in the same way that a traditional module (Line Card) directly
installed in the IA Parent, which automatically provisions internal communication channels, downloads
local software, and manages interface statistics, from one single point.

Exercise Objective
The purpose of the exercise is to demonstrate the overall simplicity of managing the IA solution, which
provides the following benefits:
• Single point of management for all configuration

• Single point of verification & troubleshooting (across distribution and access-layer)

• Automatic provisioning and image management  

Lab Exercise Steps

Step 1 Verify that the IA Client interface configuration shows up in C6K VSS running-config

NOTE: Both students will be working simultaneously in this lab since there’s one IA stack per student.
We are going to use 2 x FEX ID’s = FEX101 (student 1) and FEX 102 (student 2).
During the steps we will be referring to FEX 10Z; Z=1 for student 1 and Z=2 for student 2
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask instructors for IP addresses and
credentials).
 

podX-vss#show run fex 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2
Building configuration...

Current configuration : 11795 bytes

!
interface GigabitEthernet10Z/1/0/1
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto
shutdown
!
interface GigabitEthernet10Z/1/0/2
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto
shutdown
!
interface GigabitEthernet10Z/1/0/3
switchport
switchport trunk allowed vlan 1
Copyrighted Cisco® Systems Inc. December 2015 31  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

switchport mode dynamic auto

shutdown
Step 2 Verify that your C6800IA Client shows up as remote module to the C6K VSS.

podX-vss#show module fex 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2
Switch Number: 10Z Role: FEX
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 C6800IA 48GE C6800IA-48TD FOC1737W0PS

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 c025.5ca1.fe80 to c025.5ca1.feb3 0.0 Unknown 15.2(3m)E1 Ok ß  SW  version    
                                       may  vary

Mod Online Diag Status

---- -------------------
1 Pass

Step 3 Verify the current Port-Channel & Fabric Link Status between IA Client & Parent

podX-vss#show etherchannel 10Z summary ß  Z=1  for  student  1  and  Z=2  for  student  2
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
f - failed to allocate aggregator

M - not in use, no aggregation due to minimum links not met

m - not in use, port not aggregated due to minimum links not met
u - unsuitable for bundling
d - default port

w - waiting to be aggregated
Number of channel-groups in use: 5
Number of aggregators: 5

Group Port-channel Protocol Ports

------+-------------+-----------+-----------------------------------------------
10Z Po10Z(SU) - Te1/4/4+Z(P) ß  Z=1  for  student  1  and    Z=2  for  student  2  

Last applied Hash Distribution Algorithm: Adaptive

NOTE: Remember that we have only associated one TenGig interface to the Port-channel for this
exercise. Only one physical link is required for IA to operate. We will add the other TenGig interface in a
later exercise (for 2 x 10G), to demonstrate the simplicity of provisioning additional fabric link bandwidth.

Step 4 Verify the environment (temperature) of your IA Client

podX-vss#show environment status fex 10Z ß  Enables  env  check  of  remote  IA  line  card  from  Cat6k.  
Z=1  for  student  1  and  Z=2  for  student  2
Fex 10Z Fan 1
FEX 10Z Fan 1 type: Built-in
FEX 10Z Fan 1 mode: Auto
Fex 10Z fan-tray 1 fan-fail: OK
Copyrighted Cisco® Systems Inc. December 2015 32  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Fex 10Z Fan 2

FEX 10Z Fan 2 type: Built-in
FEX 10Z Fan 2 mode: Auto
Fex 10Z fan-tray 2 fan-fail: OK
FEX 10Z module 1 cooling requirement: 84 cfm
Fex 10Z module 1 inlet temperature: 36C

Step 5 Verify the power supply of your IA Client

podX-vss#show power fex 10Z ß  Check  the  PSU  of  IA  Client.    Z=1  for  student  1  and  Z=2  for  student  2  
FEX Switch Number: 10Z
system power redundancy mode for module:1 = non-redundant
system power total for module:1 = 135.00 Watts (11.25 Amps @ 12V)
system power used for module:1 = 41.04 Watts ( 3.42 Amps @ 12V)
system power available for module:1 = 93.96 Watts ( 7.83 Amps @ 12V)
Power-Capacity PS-Fan Output Oper
PS Type Watts A @12V Status Status State
---- ------------------ ------- ------ ------ ------ -----
1 Built-in 135.00 11.25 -- -- on
Pwr-Allocated Oper
Fan Type Watts A @12V State
---- ------------------ ------- ------ -----
1 Built-in 5.04 0.42 on
Pwr-Requested Pwr-Allocated Admin Oper
Slot Card-Type Watts A @12V Watts A @12V State State
---- ------------------ ------- ------ ------- ------ ----- -----
1 C6800IA-48TD 36.00 3.00 36.00 3.00 on on

system auxiliary power mode = off

system auxiliary power redundancy operationally = non-redundant
system primary connector power limit = N/A
system auxiliary connector power limit = N/A
system primary power used = 41.04 Watts ( 3.42 Amps @ 12V)
system auxiliary power used = 0 Watt
podX-vss#

Step 6 In situations where it is required to issue commands on the IA Client, like console access, the
user can open a remote session using the “attach” CLI command. Note that there is also a
traditional RJ45 Console port on the IA Client

podX-vss#attach fex-id 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2.  Equivalent  of  doing  a  session  to  a  C6k  line  card  
Attach FEX:10Z ip:192.1.1.101
Trying 192.1.1.101 ... Open
????????

User Access Verification

Password: cisco ß Default password of IA client “cisco”

FEX-10Z>en
Password: cisco ß Default password of IA client “cisco”
FEX-10Z#show etherchannel summary ß Connected to IA Client
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator

M - not in use, minimum links not met

u - unsuitable for bundling
w - waiting to be aggregated
Copyrighted Cisco® Systems Inc. December 2015 33  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

d - default port

Number of channel-groups in use: 24

Number of aggregators: 24

Group Port-channel Protocol Ports

------+-------------+-----------+-----------------------------------------------
1 Po1(SU) - Te1/0/1(P) ß  Use  this  interface  number  for  command  below

<..snip..>

FEX-10Z#show int teng 1/0/1 ß Verify the FEX “Uplink” interface towards C6k which are
not visible from C6k CLI – Note: use the interface number
from the output above. In this example is Te1/0/1
TenGigabitEthernet1/0/1 is up, line protocol is up (connected)
Hardware is Ten Gigabit Ethernet, address is c025.5ca1.feb3 (bia c025.5ca1.feb3)
MTU 9198 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 10Gb/s, link type is auto, media type is SFP-10GBase-CX1
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 3000 bits/sec, 1 packets/sec
5 minute output rate 3000 bits/sec, 1 packets/sec
1470 packets input, 928937 bytes, 0 no buffer
Received 1378 broadcasts (1377 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1377 multicast, 0 pause input
0 input packets with dribble condition detected
1677 packets output, 915917 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

Step 7 To exit back to C6K VSS Console, simply type “exit”

FEX-10Z#exit

[Connection to 192.1.1.101 closed by foreign host]

podX-vss#

Step 8 Verify the FEX system usage across all FEX- ID’s
podX-vss#show fex system platform usage
FEX id usage details
Fex-ids inuse: 101, 102
Fex-ids online: 101, 102
Total Used Free
----- ---- ----
42 2 40 ß  Highlights  the  FEX-­‐ID  (MAX,  USED  &  FREE)  usage  &  how  many  are  available

Copyrighted Cisco® Systems Inc. December 2015 34  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

FEX slot usage details

FEX-id Switch-id Vslot Pslot Status
------ --------- ----- ----- ------
101 3 50 1 In-use
102 4 51 1 In-use
Total Used Reserved Temp-Use/Free Free
----- ---- -------- ------------- ----
47 2 0 0/5 45 ß  Highlights  Switches  max/usage/available

Current Temp vslot allowed FEXs:

FEX ports usage details

FEX-id Switch-id Ports
------ --------- -----
101 3 48
102 4 48
Total Used Free
----- ---- ----
2016 96 1920 ß  Highlights  the  FEX  Ports  max/usage/available

Stack members usage details

FEX-id Switch-id Used Free
------ --------- ---- ----
101 3 1 4
102 4 1 4 ß  Stacking  Usage/Available  per  FEX-­‐ID,  Show  Max  of  5  stack  members    

VNTAG MGR Usage ß  VNTAG  usage  (internal  to  system  functioning)

-----------------------
Max unicast VIFs available 2048
Total unicast VIFs used 96
Max non-mdest VIFs available 1019
Total non-mdest VIFs used 2
Max mdest VIFs available 16380
Total mdest VIFs used 0

LTL MGR Usage

-------------------
MAX unicast LTLs avaialble 2048
Total unicast LTLs used 96

NOTE: The command above shows scalability with the IOS version currently running in the system. For
scalability information on specific platforms and IOS versions, please refer to the release notes

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

Copyrighted Cisco® Systems Inc. December 2015 35  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 3: Provisioning Additional Stack Members

and Verification
Exercise Description
In this exercise, the student will provision additional stack member to the FEX already provisioned.
Students will be able to verify the additional stack member using commands like “show module” and
“show fex” and also will verify the IA client stack member host ports show up in the running configuration
automatically without any additional configuration.

Exercise Objective
The purpose of the exercise is to give users the hands on experience of truly plug and play simplicity of
provisioning additional stack members.

Lab Exercise Steps

Step 1 First, Verify the status of FEX 10Z

NOTE: Both students will be working simultaneously in this lab since there’s one IA stack per student.
We are going to use 2 x FEX ID’s = FEX101 (student 1) and FEX 102 (student 2).
During the steps we will be referring to FEX 10Z; Z=1 for student 1 and Z=2 for student 2
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask instructors for IP addresses and
credentials).
 

podX-vss#show fex 10Z detail ß  Z=1  for  student  1  and  Z=2  for  student  2
FEX: 10Z Description: FEX010Z state: online ß  FEX  10Z  online
FEX version: 15.0(2)EX2 ß  You  might  see  a  different  software  version
Extender Model: C6800IA-48TD, Extender Serial: FOC1741S1F9
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 1
Fabric port for control traffic: Te1/2/(4+Z)
Fabric interface state:
Po10Z - Interface Up.
Te1/4/(4+Z) - Interface Up. state: bound

Step 2 Verify FEX 10Z shows up as line card module. We will use the command “show module fex
10Z” to verify how many stack members (modules) are part of FEX 10Z

Copyrighted Cisco® Systems Inc. December 2015 36  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss#show module fex 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2
Switch Number: 10Z Role: FEX
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 C6800IA 48GE C6800IA-48TD FOC1741S1F9 ß
Shows one module of C6800IA-48TD

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 34db.fdf9.9180 to 34db.fdf9.91b3 0.0 Unknown 15.0(2)EX2 Ok

Mod Online Diag Status

---- -------------------
1 Pass

Step 3 The purpose of this exercise is to demonstrate the simplicity of adding stack members to an
existing IA stack. The stack members are already pre-cabled using flex-stack cable to your FEX
10Z, however they are not booted up. In this step we will simulate the stack member addition by
booting up the stack member manually.
To manually boot the stack member, connect to the console of the second FEX in the stack.

switch: ß  This  is  the  ROMMON  prompt  of  IA  Client  to  allow  us  to  do  manual  booting.

Step 4 Manually boot the additional stack member

Switch: boot ß  Type  “boot”  to  manually  boot  the  Stack  member.  Note  in  real  world  IA  deployments,  all  IA  Clients  
automatically  boot  up  and  would  not  require  any  manual  boot  step.

Loading "flash:/c6800ia-universalk9-mz.150-2.EX2/c6800ia-universalk9-mz.150-
2.EX2.bin"...Verifying image flash:/c6800ia-universalk9-mz.150-2.EX2/c6800ia-
universalk9-mz.150-
2.EX2.bin.............................................................................
......................................................................................
.........................................................................Image passed
digital signature verification
@@@@@@@@@@@@@@@...

Step 5 The bootup process of the stack member will take approx. 5 minutes. After 5 minutes the IA
client stack members will automatically associate and show up as part of show module output
on C6k.

Copyrighted Cisco® Systems Inc. December 2015 37  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss#show module fex 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2
Switch Number: 10Z Role: FEX
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 C6800IA 48GE C6800IA-48TD FOC1741S1F9
2 48 C6800IA 48GE C6800IA-48TD FOC1741S1FF ß
Module  2  automatically  shows  up  as  Stack  member  2  boots  up  

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 34db.fdf9.9180 to 34db.fdf9.91b3 0.0 Unknown 15.0(2)EX2 Ok
2 34db.fde9.6980 to 34db.fde9.69b3 0.0 Unknown 15.0(2)EX2 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass

Step 6 Verify the module 2 configuration shows up in the running-configuration

podX-vss#show run fex 10Z module 2 ß  Z=1  for  student  1  and  Z=2  for  student  2
Building configuration...

Current configuration : 5912 bytes

!
interface GigabitEthernet10Z/2/0/1 ß  shows  configuration  of  stack  member  2
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto
!
interface GigabitEthernet10Z/2/0/2 ß  Stack  member  2  interface
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto

podX-vss#write mem ß  Save  the  configuration

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

Copyrighted Cisco® Systems Inc. December 2015 38  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 4: Host Ports Configuration and Verification

of Traffic
Exercise Description
In this exercise, the student will configure IA Client host ports connected to an external host. We are
going to use the 4948 switch for this purpose and we will use this switch as traffic generator.
Students will be able configure L2 interfaces and verify interface counters statistics by generating traffic
from external host (that we will call a traffic generator). Additionally, users will be able to verify
configuration of Layer 3 (IPv4 and/or IPv6) for routed access, and or MPLS/VRF CLI directly at IA host
ports, without any need to configure routing protocols between the distribution & access-layer.

Exercise Objective
The purpose of the exercise is to give users the hands on experience of Catalyst 6500/6800 feature
richness with the Instant Access solution.

Lab Exercise Steps

Step 1 First, check the default configuration for a host port in the IA client

NOTE: The C6K VSS & IA interface naming convention is as follows…

Interface GigabitEthernet <FEX-ID> / Stack Member # / Sub Module / Port #

FEX-ID = 10Z, where Z = 1 for student 1 and Z = 2 for student 2

Stack Member # = 1 or 2 since we are using stack of 2 IA Client
Sub Module = 0 for C6800IA client (default).

NOTE: Both students will be working simultaneously in this lab since there’s one IA stack per student.
We are going to use 2 x FEX ID’s = FEX101 (student 1) and FEX 102 (student 2).
During the steps we will be referring to FEX 10Z; Z=1 for student 1 and Z=2 for student 2
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask instructors for IP addresses and
credentials).
 

podX-vss#show run int gig 10Z/1/0/1 ß  Z=1  for  student  1  and  Z=2  for  student  2
Building configuration...

Current configuration : 127 bytes

!
interface GigabitEthernet10Z/1/0/1 ß    Z=1  for  student  1  and  Z=2  for  student  2  -­‐  Default  configuration  of  IA  host  port
switchport
switchport trunk allowed vlan 1
switchport mode dynamic auto
shutdown
end

Copyrighted Cisco® Systems Inc. December 2015 39  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 2 Add VLAN101 (for student 1) and VLAN102 (for student 2) for host access and assign an IP
address
podX-vss#conf t
podX-vss(config)#vlan 10Z ß    Z=1  for  student  1  and  Z=2  for  student  2  
podX-vss(config-vlan)#exit
% Applying VLAN changes may take few minutes. Please wait...

podX-vss(config)#int vlan 10Z ß    Z=1  for  student  1  and  Z=2  for  student  2  
podX-vss(config-if)#ip add 10X.10Z.1.100 255.255.255.0 ß    X  is  the  POD#;      
ß    Z=1  for  student  1  and  Z=2  for  student  2  
podX-vss(config-if)#no shut
podX-vss (config-if)#end

podX-vss#show run int vlan 10Z ß    Z=1  for  student  1  and  Z=2  for  student  2
Building configuration...

Current configuration : 65 bytes

!
interface Vlan10Z
ip address 10X.10Z.1.100 255.255.255.0 ß    X  is  the  POD#;  Z=1  for  student  1  and  Z=2  for  student  2
end

podX-vss #write mem ß    Save  the  configuration  

Step 3 Configure the first IA Client host port (interface Gig10Z/1/0/1) like any regular Access switch
host port. We are going to use access VLAN 10Z (Z = 1 for student 1 and Z = 2 for student 2)
podX-vss#conf t
podX-vss(config)#int gig 10Z/1/0/1 ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-if)#switchport mode access
podX-vss(config-if)#switchport access vlan 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-if)#load-interval 30 ß  To  verify  traffic  stats  in  30s  interval
podX-vss(config-if)#logging event link
podX-vss(config-if)#no shutdown
podX-vss(config-if)#end
podX-vss#write mem ß  Save  the  configuration

Step 4 We are going to add the network from the vlan into the OSPF process:

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#router ospf 10
podX-vss(config-router)#network 10X.10Z.0.0 0.0.255.255 area 0 ß  X=POD  number;    
ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-router)#end

podX-vss#show run partition router ospf 10

<..snip..>
router ospf 10
nsf
Copyrighted Cisco® Systems Inc. December 2015 40  
 Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

network 10.252.0.0 0.0.255.255 area 0

network 1X.1X.1X.1X 0.0.0.0 area 0
network 10X.10Z.0.0 0.0.255.255 area 0 ß  X=POD  number;    Z=1  for  student  1  and  Z=2  for  student  2

Step 5 Configure the 4948 switch as the host for Instant Access.

podX-4948-sw#conf t
podX-4948-sw(config)#int gig 1/Z ←  Z=1  for  student  1  and  Z=2  for  student  2
podX-4948-sw(config-if)#no switchport
podX-4948-sw(config-if)#ip add 10X.10Z.1.2 255.255.255.0
podX-4948-sw(config-if)#no shut
podX-4948-sw(config)#ip route 10X.10Z.10.1 255.255.255.255 10X.10Z.1.100
ß  X=POD  number;    Z=1  for  student  1  and  Z=2  for  student  2
podX-4948-sw(config)#end
podX-4948-sw#write mem ß  Save  the  configuration

Step 6 We are now going to generate traffic from the host (4948 switch) to the core switch but first we
are going to test basic connectivity:

podX-4948-sw#ping 10X.10Z.10.1 ß X= POD number / Z=1 for student 1 and Z=2 for student 2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 101.101.10.1, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms

podX-4948-sw#ping ß  Generate  extended  ping

Protocol [ip]:
Target IP address: 10X.10Z.10.1 ß  X=  POD  number  /  Z=1  for  student  1  and  Z=2  for  student  2
Repeat count [5]: 15000 ßGenerate  15,000  packets
Datagram size [100]: 4096 ß  Choose  a  frame  size
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 15000, 4096-byte ICMP Echos to 10X.10Z.10.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
…

Step 7 Verify the interface stats on IA Client host port directly from C6k console CLI

podX-vss#sho int gig 10Z/1/0/1 ßZ=1  for  student  1  and  Z=2  for  student  2  -­‐    Verify  the  IA  Host  port  counters  on  C6k  console  
GigabitEthernet10Z/1/0/1 is up, line protocol is up (connected)
Hardware is C6k 1000Mb 802.3, address is ece1.a959.6581 (bia ece1.a959.6581)
MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 2/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseT
input flow-control is off, output flow-control is unsupported
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters 6d02h
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 106000 bits/sec, 12 packets/sec ß  Ingress  traffic  from  4948

Copyrighted Cisco® Systems Inc. December 2015 41  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

30 second output rate 106000 bits/sec, 12 packets/sec

515785191 packets input, 528163973262 bytes, 0 no buffer
Received 494697086 broadcasts (494697053 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1450 packets output, 198002 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out

Step 8 Verify the traffic is traversing from all the way up to C6k via Interface port-Channel (the port-
channel interface is the one we are using for the ports connected to the IA client)

podX-vss#show interface port-channel 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2
Port-channel101 is up, line protocol is up (connected)
Hardware is EtherChannel, address is 0019.5507.4170 (bia 0019.5507.4170)
MTU 1500 bytes, BW 40000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 10Gb/s, media type is unknown
input flow-control is on, output flow-control is off
Members in this channel: Te1/2/15 Te2/2/15
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters 6d03h
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 1851000 bits/sec, 166 packets/sec <- Packet switching @ C6K
30 second output rate 1851000 bits/sec, 166 packets/sec
517281346 packets input, 534068995937 bytes, 0 no buffer
Received 495849496 broadcasts (495847353 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
22710165 packets output, 21876977237 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out

Copyrighted Cisco® Systems Inc. December 2015 42  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Optional Exercise Steps

NOTE: The following steps simply demonstrate the capability to configure any of the advanced C6K
routing & switching features (e.g. L3 (IPv4/IPv6), VRF, MPLS, etc.) on IA Client host ports.

Step 9 (Optional) Configure L3 interface enabling routed access at IA client host port.

podX-vss#conf t
podX-vss(config)#int gig 10Z/1/0/15 ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-if)#no switchport ß  Routed  Access  Interfaces
podX-vss(config-if)#ip add 10Z.15.1.1 255.255.255.0 ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-if)#no shut
podX-vss(config-if)#end

podX-vss#show run int gig 10Z/1/0/15

Building configuration...

Current configuration : 95 bytes

!
interface GigabitEthernet10Z/1/0/15
no switchport
ip address 10Z.15.1.1 255.255.255.0 ß  Routed  Access  Interfaces  at  IA  Client  
 
Step 10 (Optional) Con Configured MPLS at IA client host port interface

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss (config)#vrf definition RED-Z ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss (config-vrf)#vnet tag 10Z ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss (config-vrf)#address-family ipv4
podX-vss (config-vrf-af)#end

podX-vss#conf t
podX-vss(config)#int gig 10Z/1/0/25 ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-if)#no switchport
podX-vss(config-if)#vrf forwarding RED-Z ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-if)#ip address 10Z.25.1.1 255.255.255.0 ß  Z=1  for  student  1  and  Z=2  for  student  2
podX-vss(config-if)#mpls ip
podX-vss(config-if)#no shut
podX-vss(config-if)#end

podX-vss#sh run int gig 10Z/1/0/25

Building configuration...
Current configuration : 115 bytes
!
interface GigabitEthernet10Z/1/0/20
no switchport
vrf forwarding RED-Z ß  MPLS  VRF  forwarding  at  IA  Client  host  ports
ip address 10Z.25.1.1 255.255.255.0
mpls ip
end
þ End of Exercise: You have successfully completed this exercise!
Proceed to the next section…

Copyrighted Cisco® Systems Inc. December 2015 43  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 5: Provisioning Additional Fabric Links

Exercise Description
In this exercise, the student will configure an additional 10G fabric link between IA Parent (C6K VSS) and
their IA Client, from the IA Parent console (without doing any configuration at IA Client).

Exercise Objective
The purpose of the exercise is to demonstrate the simplicity of provisioning additional bandwidth using a
single CLI command on C6K. This allows customers to deploy additional bandwidth directly from C6k
without any changes and configuration at access layer.

Lab Exercise Steps

Step 1 Verify how many fabric links we have between IA Client and IA Parent

NOTE: Both students will be working simultaneously in this lab since there’s one IA stack per student.
We are going to use 2 x FEX ID’s = FEX101 (student 1) and FEX 102 (student 2).
During the steps we will be referring to FEX 10Z; Z=1 for student 1 and Z=2 for student 2
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask the instructors for IP addresses and
credentials).
 

podX-vss#show fex 10Z detail ß  Z=1  for  student  1  and  Z=2  for  student  2
FEX: 10Z Description: FEX010Z state: online
FEX version: 15.0(2)EX2
Extender Model: C6800IA-48TD, Extender Serial: FOC1709Z2V9
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 1
Fabric port for control traffic: Te1/2/(4+Z)
Fabric interface state:
Po10Z - Interface Up. ß  Z=1  for  student  1  and  Z=2  for  student  2
Te1/4/4+Z - Interface Up. state: bound ß  Z=1  for  student  1  and  Z=2  for  student  2.    
We  have  one  10G  uplink  deployed        
 

Step 2 Add additional 10G links between IA Client and IA Parent.

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#int ten 2/4/4+Z ß  Z=1  for  student  1  and  Z=2  for  student  2.
podX-vss(config-if)#switchport
podX-vss(config-if)#switchport mode fex-fabric
podX-vss(config-if)#channel-group 10Z mode on ß Z=1  for  student  1  and  Z=2  for  student  2.    
Adding  an   additional  tenGigEthernet  member  of  Port-­‐Channel  10Z  
podX-vss(config-if)#logging event link
podX-vss(config-if)#no shutdown
podX-vss(config-if)#end
podX-vss#wr mem
 

Copyrighted Cisco® Systems Inc. December 2015 44  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 3 Verify the additional Uplinks are provisioned to IA Fabric link between IA client and IA Parent
podX-vss#show fex 10Z detail ß Z=1  for  student  1  and  Z=2  for  student  2
FEX: 10Z Description: FEX010Z state: online
FEX version: 15.0(2)EX2
Extender Model: C6800IA-48TD, Extender Serial: FOC1709Z2V9
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te1/2/(4+Z)
Fabric interface state:
Po10Z - Interface Up.
Te1/4/4+Z - Interface Up. state: bound ß Z=1  for  student  1  and  Z=2  for  student  2
Te2/4/4+Z - Interface Up. state: bound ß Two 10G Fabric Links

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

Copyrighted Cisco® Systems Inc. December 2015 45  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 6: Adding a Compact Switch as Instant

Access Client
Exercise Description
In this exercise, the student will provision a compact switch in instant access mode. We will also test IOS
features that allow for automatic provisioning of FEX clients.

Exercise Objective
Compact switches can be deployed in standalone mode like traditional switches and the can be deployed
in FEX mode with Instant Access. The student will have hands-on experience on how to convert compact
switches to instant access mode. For this lab we will be using compact switch WS-C3560CX-8XPD-S.

We will also leverage IOS commands that allow for auto-provisioinng of FEX clients.
 

Lab Exercise Steps

Step 1 In the previous exercises we manually provisioned the Instant Access clients. In this section, we
will leverage the automatic provisioning of FEX clients by leveraging the “auto” commands.
Since this command is required in the VSS pair in global configuration mode, only one student
needs to configure this step. Please check with the other student in the POD so that only
one configures this command.

podX-vss#conf t
podX-vss(config)#fex auto-config ß enables  automatic  provisioning  of  FEX  clients  for  the  whole  system  
podX-vss(config)#end
podX-vss#wr mem ß saves  configuration

NOTE: Both students will be working simultaneously in this lab since there’s one IA compact switch per student.
We are going to use 2 x FEX ID’s. Since this exercise uses the “auto-config” command, the IA parent will
automatically assign a FEX ID. Since we don’t know which FEX ID’s each student will be assigned, we will use
FEX XYZ to refer to the compact switch prosivioned as a FEX.
We will still use the concept of Z=1 for student 1 and Z=2 for student 2 for uplinks
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask instructors for IP addresses and
credentials). Each student will access the console of the assigned compact switch.
 

Step 2 Each student will connect to one compact switch via the console. Once connected, we will
check the fex mode for the compact switch. Compact switches can be deployed in standalone
mode like traditional switches and the can be deployed in FEX mode with Instant Access. The
compact switches are currently in standalone mode so we will convert them into FEX mode.

NOTE:
Student 1 should connect to Compact Switch 1 and use parameter Z=1 below.
Student 2 should connect to Compact Switch 2 and use parameter Z=2 below.
 
Copyrighted Cisco® Systems Inc. December 2015 46  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Switch>en ß if  prompted  for  password  use  “lab-­‐cert”

Switch#show fex-mode ß Check  for  FEX  mode  in  compact  switch
Switch is in non Fex mode

Step 3 We are now going to enable the interfaces connected to the Compact Switch Instant Access
client

podX-vss#conf t
podX-vss(config)#int rang teng 1/4/Z+2, teng 2/4/Z+2 ß    Z=1  for  student  1  and    Z=2  for  student  2)
podX-vss(config-if-range)#no shut
podX-vss(config)#end
podX-vss#wr mem ß saves  configuration

Step 4 We are now convert the standalone compact switch into FEX mode

Switch#fex-mode enable ß    Enter  this  commmand  from  the  console  of  the  compact  switch  
System will reload after mode conversion.
Do you want to continue? [no]: yes ß Enter  “Yes”  and  <ENTER>  

Step 5 We will now wait for the switch to reload which will take a few minutes. Once the FEX reloads,
we will check the FEX configuration for the IA parent / CAT6K-VSS

podX-vss#sh fex
FEX FEX FEX FEX
Number Description State Model Serial
---------------------------------------------------------------------------
101 FEX0101 online C6800IA-48TD FOC1737W0Q9
102 FEX0102 online C6800IA-48TD FOC1736W19L
XYZ FEX0XYZ online WS-C3560CX-8XPD-S FHH1840P00B ß  Locate  FEX  id    
assigned  by  auto-­‐fex

podX-vss#show fex XYZ ß    Use  FEX  id  assigned  by  auto-­‐fex  

FEX: XYZ Description: FEX0102+Z state: online ß  FEX  id  assigned  by  auto-­‐fex
FEX version: 15.2(3m)E1
Extender Model: WS-C3560CX-8XPD-S, Extender Serial: FOC1852Z00C
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te1/4/Z+1
Fabric interface state:
Po? - Interface Up. ß    The  portchannel  number  will  also  be  assigned  
 automatically  
Te1/4/Z+1 - Interface Up. state: bound ß    Z=1  for  student  1  and    Z=2  for  student  2)
Te2/4/Z+2 - Interface Up. state: bound ß    Z=1  for  student  1  and    Z=2  for  student  2)  
 
Step 6 We are now going to test how to remove the newly added FEX and convert it back to
standalone mode. WAIT! Before performing this step, check with your POD partner if the
finished converting their compact switch.
 
 
podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#no fex auto-config
podX-vss(config)#end

podX-vss#reload fex XYZ standalone dissociate ß    Use  FEX  id  assigned  by  auto-­‐fex  
ß    We  are  going  to  reload  the  compact  
             switch  in  standalone  mode  
Proceed with reload of fex module and Convert to Standalone mode?[confirm] ß[ENTER]

podX-vss#sh fex
Copyrighted Cisco® Systems Inc. December 2015 47  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

FEX FEX FEX FEX

Number Description State Model Serial
---------------------------------------------------------------------------
101 FEX0101 online C6800IA-48TD FOC1737W0Q9
102 FEX0102 online C6800IA-48TD FOC1736W19L
XYZ FEX0XYZ --- WS-C3560CX-8XPD-S FHH1840P00B ß    Use  FEX  id    
assigned  by  auto-­‐fex

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#no fex XYZ ß    Use  FEX  id  assigned  by  auto-­‐fex;  we  are  now  removing  the  FEX
podX-vss(config)#end

podX-vss#sh fex
FEX FEX FEX FEX
Number Description State Model Serial
---------------------------------------------------------------------------
101 FEX0101 online C6800IA-48TD FOC1737W0Q9
102 FEX0102 online C6800IA-48TD FOC1736W19L

Step 7 Connect to the console of the compact switch and confirm that the switch is once again in
standalone mode. Please note that the reload has to finish in order to be able to log into the
switch. You can check on the boot up process via the console.

Switch>en ß if  prompted  for  password  use  “lab-­‐cert”

Switch#show fex-mode ß Check  for  FEX  mode  in  compact  switch
Switch is in non Fex mode

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

Copyrighted Cisco® Systems Inc. December 2015 48  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 7: Fabric Link Failure and Recovery

Exercise Description
In this exercise, the student will simulate failure of one TenGigabitEthernet fabric link between IA Client
and the C6K VSS IA Parent, and observe that the IA client remains up and both the control & data traffic
moves to the remaining fabric link, without any impact to IA uptime or sub-second data loss.

Exercise Objective
In this exercise, the goal is to demonstrate high availability across multiple fabric links when one of the
fabric link fails and data plane continues to forward traffic across the VSS pair with minimal loss.  
 

Lab Exercise Steps

NOTE: Both students will be working simultaneously in this lab since there’s one IA stack per student.
We are going to use 2 x FEX ID’s = FEX101 (student 1) and FEX 102 (student 2).
During the steps we will be referring to FEX 10Z; Z=1 for student 1 and Z=2 for student 2
The output of some of the “show” commands may vary based on the student number
Each student will now use TELNET access to the VSS and to the 4948 (ask instructors for IP addresses and
credentials).
 

Step 1 Telnet to the 4948 switch and generate traffic to the core switch (for telnet access information
refer to the table in section “Access your POD”)

podX-4948-sw#ping ß  Generate  extended  ping

Protocol [ip]:
Target IP address: 10X.10Z.10.1 ß  X=  POD  number  /  Z=1  for  student  1  and  Z=2  for  student  2
Repeat count [5]: 15000 ßGenerate  15,000  packets
Datagram size [100]: 4096 ß  Choose  a  frame  size
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 15000, 4096-byte ICMP Echos to 10X.10Z.10.1 , timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
…

Step 2 Now from the CAT6K VSS verify the traffic across 2 fabric links
podX-vss#sh int ten 1/4/4+Z | inc rate ß  Z=1  for  student  1  and  Z=2  for  student  2
Queueing strategy: fifo
30 second input rate 4200000 bits/sec, 380 packets/sec ß  Traffic  on  one  10G  link
30 second output rate 4200000 bits/sec, 380 packets/sec ß

podX-vss#sh int ten 2/4/4+Z| inc rate ß  Z=1  for  student  1  and  Z=2  for  student  2
Queueing strategy: fifo
30 second input rate 0 bits/sec, 0 packets/sec ß
Copyrighted Cisco® Systems Inc. December 2015 49  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

30 second output rate 0 bits/sec, 0 packets/sec ß

Step 3 Shut the TenGig fabric link carrying data traffic and observe the traffic redistribution to the other
10G fabric link. Note down the interface that you will be shutting down so we can restore it at the
end of the lab.

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#int ten 1/4/4+Z ß  Chose  the  interface  to  shutdown  from  the  step  above;    
                     Z=1  for  student  1  and  Z=2  for  student  2  
podX-vss(config-if)#shutdown
podX-vss(config-if)#end

podX-vss#sh int ten 1/4/4+Z | inc rate ß  Z=1  for  student  1  and  Z=2  for  student  2
Queueing strategy: fifo
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec

podX-vss#sh int ten 2/4/4+Z | inc rate ß  Z=1  for  student  1  and  Z=2  for  student  2
Queueing strategy: fifo
30 second input rate 1851000 bits/sec, 166 packets/sec
30 second output rate 1851000 bits/sec, 166 packets/sec ß  Traffic  switched  to  other    
                         10G  link  

Step 4 Verify the traffic loss on 4948 switch:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 99 percent (14999/15000), round-trip min/avg/max = 1/4/151 ms

Note: The traffic loss, in this case 1 packet loss during the switchover across the fabric links
Step 5 Now restore the shutdown 10G fabric link back up.

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#int ten 1/4/4+Z ß  Chose  the  interface  to  shutdown  from  the  step  2
podX-vss(config-if)#no shutdown   ß  Restore  fabric  link
podX-vss(config-if)#end
podX-vss#

Step 6 In this step we will verify which 10G link is carrying the control information (heartbeat and control
packets) between C6k and C6800IA client.

podX-vss#show fex 10Z detail

FEX: 10Z Description: FEX010Z state: online
FEX version: 15.0(2)EX2
Extender Model: C6800IA-48FPD, Extender Serial: FHH1707P00S
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te 2/4/4+Z ß  Control  traffic  between  IA  Client  and  IA  Parent  
                       ß  Z=1  for  student  1  and  Z=2  for  student  2
Fabric interface state:
Po10Z - Interface Up.
Copyrighted Cisco® Systems Inc. December 2015 50  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Te1/4/4+Z - Interface Up. state: bound ß  Both  interfaces  UP

Te2/4/4+Z - Interface Up. state: bound

Step 7 Shutdown the 10G link that is carrying the control information (heartbeat and control packets)
between C6k and C6800IA client and verify that IA Client maintains steady state of control plane
and data plane between C6k and C6800IA client. Note the interface number we will be shutting
down so that we can restore it later.

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#int ten 2/4/4+Z ß  Chose  the  interface  to  shutdown  from  the  step  above
podX-vss(config-if)#shutdown ß  Shut  the  control  traffic  10G  fabric  link
podX-vss(config-if)#end

podX-vss#sh fex 10Z detail

FEX: 10Z Description: FEX010Z state: online
FEX version: 15.0(2)EX2
Extender Model: C6800IA-48FPD, Extender Serial: FHH1707P00S
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 1
Fabric port for control traffic: 1/4/4+Z ß  Control  Traffic  switched  to  other  fabric    
                     link  and  IA  client  was  up  and  stable  
ß  Z=1  for  student  1  and  Z=2  for  student  2
 
Fabric interface state:
Po10Z - Interface Up.
Te1/4/4+Z - Interface Up. state: bound
Te2/4/4+Z - Interface Down. state: idle    ßShutdown    

Step 8 Now restore the shutdown 10G fabric link back up.

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#int ten 2/4/4+Z ß  Chose  the  interface  to  shutdown  from  the  step  2
podX-vss(config-if)#no shutdown     ß  Restore  fabric  link
podX-vss(config-if)#end
podX-vss#write mem ß  Save  the  configuration

Copyrighted Cisco® Systems Inc. December 2015 51  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Optional Exercise Steps

Step 9 (Optional) Next, we will verify the load sharing hash for port channel. Change the load sharing
hash from default (src-dst-ip) to src-mac that and observe how changing load sharing algorithm
on C6k automatically changes the load sharing hash in IA client and ensures symmetrical traffic
distribution.

podX-vss#show etherchannel load-balance

EtherChannel Load-Balancing Configuration:
src-dst-ip enhanced ß  Load  sharing  hash  on  port  channel  (Global)
mpls label-ip

EtherChannel Load-Balancing Mode on FEX Modules:

src-dst-ip ß  Load  sharing  hash  at  IA  Client  level

EtherChannel Load-Balancing Addresses Used Per-Protocol:

Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address
IPv6: Source XOR Destination IP address

podX-vss#conf t
Enter configuration commands, one per line. End with CNTL/Z.
podX-vss(config)#port-channel load-balance src-mac ß  change  Load  hash  at  C6k
podX-vss(config)#end
podX-vss#

Step 10 Verify the changes in Load balancing hash for both C6k and IA Client
podX-vss#show etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-mac ß  Load  sharing  hash  on  interface  port-­‐channel  on  C6k
mpls label-ip

EtherChannel Load-Balancing Mode on Satellites

src-mac ß  Load  sharing  hash  on  IA  Client

EtherChannel Load-Balancing Addresses Used Per-Protocol:

Non-IP: Source MAC address
IPv4: Source MAC address
IPv6: Source MAC address (bridged packets)
Source IP address (routed packets)
MPLS: Label or IP

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

 
Copyrighted Cisco® Systems Inc. December 2015 52  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Lab Exercise 8: Enhanced Fast Software Upgrade Process

(EFSU)

Exercise Description

The Cisco Catalyst 6500E and 6800X Series support enhanced Fast Software Upgrade (eFSU) in order
to increase network availability by reducing the downtime caused by software upgrades across two
supervisors in a VSS pair. It brings the active and standby supervisors into synchronous Stateful
Switchover (SSO) mode across two supervisor running two different software versions. It maintains an
active data plane on both switches in the VSS pair, providing increased network availability during the
upgrade process.

Enhanced Fast Software Upgrade is a software upgrade feature that has been supported since
12.2(33)SXI software release onwards.

Using EFSU, traffic loss during the upgrade process is minimized such that customers can perform
software upgrades without requiring scheduled maintenance windows. Using FSU with VSS (pre-
12.2(33)SXI), it is expected to lose 100% of the bandwidth available on VSS for at least 3-4 minutes
during RPR switchover. However, EFSU always allows VSS to maintain at least 50% of bandwidth during
a software upgrade provided the devices are dual-homed to the VSS pair (for single homed devices, VSS
Quad-SUP is recommended). EFSU allows different images on Active and Standby supervisors to coexist
while they are operating in SSO Redundancy mode.

EFSU capability is extended to support Instant Access client upgrades similar to how a line card is
upgraded. The client software image is bundled with the Catalyst 6500/6800 software image. A new CLI
is introduced, enabling the upgrade of the Instant Access client stack (FEX-IDs), which in turn enables an
upgrade of the Instant Access client's software version before the “issu commitversion (step 4)” of
the EFSU process.

EFSU is a process that requires the user to go through 4 steps to perform software upgrade on VSS. The
process is depicted in the picture below:

Copyrighted Cisco® Systems Inc. December 2015 53  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Exercise Objective
 

The objective of this lab is to allow users experience the Enhanced Fast Software Upgrade (eFSU)
procedure and to test the High Availability (HA) capability during software upgrade of both the distribution
switches of VSS pair and all the access layer Instant access clients from single point of management
while having minimal impact of traffic.

We will also be able to demonstrate the simplicity of upgrading the Instant Access clients.

Lab Exercise Steps

Step 1 In order to leverage the EFSU software upgrade functionality with Instant Access, Catalyst
6500/6800 systems should already be booted with an IOS version that supports the EFSU
feature. The minimum IOS version to support EFSU is 15.1(2)SY. Ensure that the Catalyst
6500/6800 system in this lab is loaded with EFSU capable version of software.

NOTE: For this lab, we are going to upgrade from 15.2(1)SY1 to 15.2(1)SY1a

Both students will be working together in this software upgrade using just the console for the Active VSS
Switch. We recommend students have 3 windows opened: console to active VSS switch; console to
standby VSS switch and telnet to 4948 switch
 

Copyrighted Cisco® Systems Inc. December 2015 54  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Connect to the VSS active console using the information provided in section “Access your POD”
(please read the note in the blue box above). Both students will be working together during
the upgrade process. Issue the “show version” command in the VSS system to check the
IOS version used.

podX-vss #show version

Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M), Version 15.2(1)SY1,
RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
<..snip..>

podX-vss#show version | include image file

System image file is "bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin"
podX-vss#

NOTE: Mark below, which is the version of software you are using (we will call it OLD_CODE) and also note
the version you will be upgrading to (we will call it NEW_CODE). You are going to use this information throughout
this lab:

OLD CODE NEW CODE

15.2(1)SY1 ßà 15.2(1)SY1a

Step 2 Ensure that the NEW_CODE is present in the disk of both the Active Virtual Switch and the
Standby Virtual Switch:

podX-vss#dir bootdisk:
Directory of bootdisk:/

1 -rw- 33554432 Oct 3 2012 21:53:50 +00:00 sea_console.dat

2 -rw- 6476 Aug 5 2015 13:00:52 +00:00 startup-config.converted_vs-20150805-130045
3 -rw- 33554432 Oct 3 2012 21:54:38 +00:00 sea_log.dat
4 -rw- 159291524 Aug 20 2015 17:58:28 +00:00 s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin
5 -rw- 159299212 Oct 29 2015 18:59:30 +00:00 s2t54-adventerprisek9-mz.SPA.152-1.SY1a.bin

1024557056 bytes total (239681536 bytes free)

podX-vss#dir sw2-slot1-bootdisk:
Directory of slavebootdisk:/

1 -rw- 33554432 Mar 20 2012 07:04:16 +00:00 sea_console.dat

2 drw- 0 Sep 14 2015 20:56:00 +00:00 onep
3 -rw- 33554432 Mar 20 2012 07:10:32 +00:00 sea_log.dat
4 -rw- 6476 Aug 5 2015 13:02:10 +00:00 startup-config.converted_vs-20150805-130208
5 -rw- 159291524 Aug 20 2015 18:30:10 +00:00 s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin
6 -rw- 7265 Oct 5 2015 10:37:50 +00:00 startup-config.converted_vs-20151005-103747
7 -rw- 159299212 Oct 29 2015 19:08:44 +00:00 s2t54-adventerprisek9-mz.SPA.152-1.SY1a.bin

1024557056 bytes total (239616000 bytes free)

Step 3 We will confirm that FEX 101 and FEX 102 are online and both links connected. We will also
check that both compact switches have been removed from the Instant Access domain

podX-vss#show fex
FEX FEX FEX FEX
Number Description State Model Serial

Copyrighted Cisco® Systems Inc. December 2015 55  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

---------------------------------------------------------------------------
101 FEX0101 online C6800IA-48TD FOC1737W0Q9
102 FEX0102 online C6800IA-48TD FOC1736W19L

podX-vss#show fex 101

FEX: 101 Description: FEX0101 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1737W0Q9
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te1/4/5
Fabric interface state:
Po101 - Interface Up.
Te1/4/5 - Interface Up. state: bound
Te2/4/5 - Interface Up. state: bound

podX-vss#show fex 102

FEX: 102 Description: FEX0102 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1736W19L
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te1/4/6
Fabric interface state:
Po102 - Interface Up.
Te1/4/6 - Interface Up. state: bound
Te2/4/6 - Interface Up. state: bound

Step 4 In Instant Access solution, the software image of C6800IA client is bundled with C6k image. To
verify what version of Image is running on IA Client. Please note that the image version of the
client will differ from the image version of the parent. However, all clients should be running the
same image. Issue the following command:

podX-vss#show version fex 101

==> Showing version for FEX 101:
Cisco IOS Software, C6800IA Software (C6800IA-UNIVERSALK9-M), Version 15.2(3m)E1, RELEASE
SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Tue 28-Apr-15 22:53 by prod_rel_team

ROM: Bootstrap program is C2960X boot loader

BOOTLDR: C6800IA Boot Loader (C6800IA-HBOOT-M) Version 15.0(2r)EX2, RELEASE SOFTWARE (fc1)

FEX-101 uptime is 6 days, 11 hours, 47 minutes

System returned to ROM by power-on
System restarted at 01:41:04 UTC Tue Dec 1 2015
System image file is "flash:/c6800ia-universalk9-mz.152-3m.E1/c6800ia-universalk9-mz.152-
3m.E1.bin"
Last reload reason: Unknown reason

<..snip..>
podX-vss#show version fex 102
==> Showing version for FEX 102:
Cisco IOS Software, C6800IA Software (C6800IA-UNIVERSALK9-M), Version 15.2(3m)E1, RELEASE
SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Tue 28-Apr-15 22:53 by prod_rel_team

Copyrighted Cisco® Systems Inc. December 2015 56  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

ROM: Bootstrap program is C2960X boot loader

BOOTLDR: C6800IA Boot Loader (C6800IA-HBOOT-M) Version 15.0(2r)EX2, RELEASE SOFTWARE (fc1)

FEX-102 uptime is 6 days, 11 hours, 47 minutes

System returned to ROM by power-on
System restarted at 01:41:24 UTC Tue Dec 1 2015
System image file is "flash:/c6800ia-universalk9-mz.152-3m.E1/c6800ia-universalk9-mz.152-
3m.E1.bin"
Last reload reason: Unknown reason

<..snip..>

Step 5 The software version that is running in each stack member can be verified by the following

podX-vss#show mod fex 101

pod8-vss#show mod fex 101
Switch Number: 101 Role: FEX
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 C6800IA 48GE C6800IA-48TD FOC1737W0Q9
2 48 C6800IA 48GE C6800IA-48TD FOC1737W0P2

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 34db.fd09.3980 to 34db.fd09.39b3 0.0 Unknown 15.2(3m)E1 Ok
2 c025.5ca1.ef00 to c025.5ca1.ef33 0.0 Unknown 15.2(3m)E1 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass

podX-vss#show mod fex 102

Switch Number: 102 Role: FEX
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 C6800IA 48GE C6800IA-48TD FOC1736W19L
2 48 C6800IA 48GE C6800IA-48TD FOC1737S20T

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 e8ed.f3f5.8280 to e8ed.f3f5.82b3 0.0 Unknown 15.2(3m)E1 Ok
2 c025.5ca1.c380 to c025.5ca1.c3b3 0.0 Unknown 15.2(3m)E1 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass

Step 6 The Software version running on each of C6800IA client will be same as the software version
bundled with C6k image. To verify that you can issue the following command on C6k.
Copyrighted Cisco® Systems Inc. December 2015 57  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss#show fex image bundle version

1. Bundled version of 'c6800ia-universalk9-mz.152-3m.E1.tar' image - 15.2(3m)E1
2. Bundled version of 'c3560cx-universalk9-mz.152-3m.E1.tar' image - 15.2(3m)E1

Step 7 There are whole set of new commands introduced with EFSU upgrade process. EFSU uses the
same infrastructure as ISSU (In Service Software Upgrade) so we will be leveraging ISSU-
based commands. Throughout this labs, we will be using the ISSU commands shown in the
output below to perform each of the steps to complete a software upgrade using EFSU:
podX-vss#issu ?
ISSU commands
abortversion abort ISSU process
acceptversion accept new IOS version on new Active
commitversion commit IOS version on Standby
loadversion load new IOS version on Standby
runversion run new IOS version on Standby and make it Active

Step 8 We will now get ready to generate traffic during our upgrade process. Open a window
connecting to the 4948 and have it configured as follows, but do not accept “Sweep range of
sizes [n]:” until you are ready to perform the “issu loadversion” command in the steps
below:

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 10X.101.10.1
Repeat count [5]: 50000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß  WAIT!  Don’t  accept  the  “Sweep  range”  until  mid    next  step  

 
Step 9 The first step of the EFSU process is “issu loadversion” and the purpose of this step is to
load the new software image onto the standby supervisor of the VSS pair. During this step, the
Standby switch will reload and boot up with the new software image. Please refer to the
“Exercise Description” section for the image that shows this action.

Now we are going to perform an “ISSU loadversion” typing the command from the output
below (use the image name of the NEW_IMAGE).
Note that you can use tab/autocomplete to make sure you type the correct image name.

podX-vss#issu loadversion bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1a.bin

System configuration has been modified. Save? [yes/no]: yes ß  accept  save  configuration  if  asked
%issu loadversion initiated successfully, upgrade sequence will begin shortly

Copyrighted Cisco® Systems Inc. December 2015 58  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss#
*Mar 14 14:24:51.626: %ISSU_PROCESS-SW1-3-LOADVERSION: Loadversion sequence will begin
in 60 seconds. Enter 'issu abortversion' to cancel.

*Mar 14 14:25:21.626: %ISSU_PROCESS-SW1-6-LOADVERSION_INFO: Resetting Standby shortly

While Switch-1 is booting with the new image, the VSS will run at 50% capacity (Standby Switch
2 reloading). We are going to generate traffic. So accept “Sweep Range of sizes [n]:”
on the 4948 now.

podX-4948-sw#
Sweep range of sizes [n]: ß    Hit  Enter  for  the  ping  sweep  in  4948  when  issuing  issu  loadversion
Type escape sequence to abort.
Sending 50000, 100-byte ICMP Echos to 10X.101.10.1, timeout is 2 seconds:

Step 10 Pay attention to the telnet window opened for VSS Standby (Switch 2) Console. You will
observe that the VSS Standby (Switch 2) is booting with the new-image. You will also notice that
even though the standby is running a different image when compared to VSS Active (Switch 1),
redundancy mode negotiated between them is SSO.
podX-vss-sdby>
*Mar 14 14:25:21.630: %ISSU_PROCESS-SW2_STBY-6-SELF_RELOAD: slot 33 countdown to self-
reload started, 30 second delay

*Mar 14 14:25:51.626: %RF-SW2_STBY-5-RF_RELOAD: Self reload. Reason: Loadversion

*Mar 14 14:25:51.698: %VSLP-SW2_STBY-3-VSLP_LMP_FAIL_REASON: Te2/1/4: Disabled by
Admin reload
*Mar 14 14:25:51.702: %VSLP-SW2_STBY-3-VSLP_LMP_FAIL_REASON: Te2/1/5: Disabled by
Admin reload
*Mar 14 14:25:51.702: %VSLP-SW2_STBY-2-VSL_DOWN: Last VSL interface Te2/1/5 went
down

*Mar 14 14:25:51.706: %VSLP-SW2_STBY-2-VSL_DOWN: All VSL links went down while

switch is in Standby role

*Mar 14 14:25:51.706: %DUAL_ACTIVE-SW2_STBY-1-VSL_DOWN: VSL is down - switchover, or

possible dual-active situation has occurred
*Mar 14 14:25:53.930: %SYS-SW2_STBY-5-SWITCHOVER: Switchover requested by UP Helper
process. Reload Reason: Loadversion.
Resetting .......

<..snip..>

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 2011 by cisco Systems, Inc.
PYRAMID platform with 2097152 Kbytes of main memory

Autoboot executing command: "boot bootdisk:s2t54-adventerprisek9-mz.  SPA.152-

1.SY1a.bin"

bootdisk:%s72044-atafslib-m: Digitally Signed Release Software with key version A

Initializing ATA monitor library...

<..snip..>

System detected Virtual Switch configuration...

Copyrighted Cisco® Systems Inc. December 2015 59  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

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

Interface TenGigabitEthernet 2/1/5 is member of PortChannel 2
Initializing as Virtual Switch STANDBY processor

<…snip…>

*Mar 14 14:05:08.423: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this

switch

*Mar 14 14:05:19.027: %VSL_BRINGUP-6-MODULE_UP: VSL module in slot 1 switch 2 brought

up
*Mar 14 14:05:46.919: %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as STANDBY by VSLP
*Mar 14 14:05:46.919: %VSL-5-VSL_CNTRL_LINK: New VSL Control Link 2/1/5

*Mar 14 14:05:46.971: %VSLP-5-VSL_UP: Ready for control traffic

*Mar 14 14:05:57.959: %PFREDUN-SW2_STBY-6-STANDBY: Initializing for SSO mode in

Default Domain

<..snip..>

Step 11 After successful boot up of the Switch 2 (Standby VSS) to the NEW_IMAGE, verify that the
redundancy mode between the two Supervisors is SSO state (Hot Standby). At this stage, the
VSS will be operating at 100 % capacity. Verify the redundancy state using the “show switch
virtual redundancy” command:

podX-vss#show switch virtual redundancy

My Switch Id = 1
Peer Switch Id = 2
Last switchover reason = none
Configured Redundancy Mode = sso
Operating Redundancy Mode = sso ß  Standby  running  in  SSO  mode

Switch 1 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = ACTIVE
Uptime in current state = 16 hours, 59 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M),
Version 15.2(1)SY1, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Mon 11-May-15 00:54 by prod_rel_team
BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12;
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = ACTIVE

Switch 2 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = STANDBY HOT (switchover target)
Uptime in current state = 0 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-ADVENTERPRISEK9-M),
Version 15.2(1)SY1a, RELEASE SOFTWARE (fc6)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Tue 29-Sep-15 15:57 by prod_rel_team
BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Copyrighted Cisco® Systems Inc. December 2015 60  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Control Plane State = STANDBY

Step 12 In the console of the VSS active switch you will receive an ISSU message when the loadversion
stage is completed:

podX-vss#
*Mar 25 17:20:51.006: %ISSU_PROCESS-SW1-3-LOADVERSION: Loadversion has completed.
Please issue the 'issu runversion' command after all modules come online. ß  Note,  We  need    
                to  wait  for  all  the  line  cards  to  be  up  before  we    
                proceed  here.  

Verify that all the Line cards are up in Standby Supervisor before issuing “issu runversion”. Also we
are going to check that the new code has been loaded. To verify this, run the command below:  
 
podX-vss#show module sw 2 ß  Verify  if  the  Line  cards  on  Standby  chassis  are  up.
Switch Number: 2 Role: Virtual Switch Standby
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Hot) VS-SUP2T-10G SAL16127TU2
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL08435CUF
4 20 DCEF2T 4 port 40GE / 16 port 10GE C6800-16P10G SAL1834ZAA7

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 588d.09e6.d652 to 588d.09e6.d659 1.3 12.2(50r)SYS 15.2(1)SY1a Ok
2 0012.4301.c524 to 0012.4301.c527 2.0 12.2(14r)S5 15.2(1)SY1a Ok
4 1005.caea.d356 to 1005.caea.d369 1.0 15.1(58r)SYL 15.2(1)SY1a Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 4 VS-F6K-PFC4 SAL16127M2D 1.2 Ok
1 CPU Daughterboard VS-F6K-MSFC5 SAL16127W7F 1.4 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAD0804067A 2.0 Ok
4 Distributed Forwarding Card C6800-DFC SAL1834ZAA7 1.0 Ok

Mod Online Diag Status

---- -------------------
1 Pass ß  Indicates  that    all  Line  cards  are  up  so  process  is  finished.
2 Pass ß  If  you  get  a  Status  other  than  “Pass”  it  means  that  the    
4 Pass ß  process  is  not  yet  finished.

We are also going to check, that the active switch still has the old code:

podX-vss#show module sw 1
Switch Number: 1 Role: Virtual Switch Active
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL16052XQX
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL1019MC05
4 20 DCEF2T 4 port 40GE / 16 port 10GE C6800-16P10G-XL SAL1834ZAKB

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 588d.098a.c5ad to 588d.098a.c5b4 1.2 12.2(50r)SYS 15.2(1)SY1 Ok
2 0017.95b8.087c to 0017.95b8.087f 2.2 12.2(14r)S5 15.2(1)SY1 Ok
Copyrighted Cisco® Systems Inc. December 2015 61  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

4 1005.caea.d482 to 1005.caea.d495 1.0 15.1(58r)SYL 15.2(1)SY1 Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 4 VS-F6K-PFC4 SAL16052UGC 1.1 Ok
1 CPU Daughterboard VS-F6K-MSFC5 SAL16052SLX 1.3 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAL1121PPJG 3.1 Ok
4 Distributed Forwarding Card C6800-DFC-XL SAL1834ZAKB 1.0 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass
4 Pass

Step 13 Since the TenGig intefaces on module 4 (int tengig 2/4/5, int tengig 2/4/6) on SW2 are
connected to FEX 101 and FEX 102 respectively,they will be in link state “down” till the line card
comes up. We will wait till then before proceeding:

podX-vss#show fex 101 detail

FEX: 101 Description: FEX0101 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1737W0Q9
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te1/4/5
Fabric interface state:
Po101 - Interface Up.
Te1/4/5 - Interface Up. state: bound
Te2/4/5 - Interface Down. state: idle ß  Ports  connected  SW2/Module  4    not  ready    

podX-vss#show fex 102 detail

FEX: 102 Description: FEX0102 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1736W19L
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te1/4/6
Fabric interface state:
Po102 - Interface Up.
Te1/4/6 - Interface Up. state: bound
Te2/4/6 - Interface Down. state: idle ß  Ports  connected  SW2/Module  4  not  ready

Step 14 Eventually when running “show fex 101/102 detail” you should get to the output below
which indicates that you are ready for the next step in the issu process

podX-vss#show fex 101 detail

FEX: 101 Description: FEX0101 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1737W0Q9
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Copyrighted Cisco® Systems Inc. December 2015 62  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Fabric port for control traffic: Te1/4/5

Fabric interface state:
Po101 - Interface Up.
Te1/4/5 - Interface Up. state: bound
Te2/4/5 - Interface Up. state: bound ß  Fabric  link  up

podX-vss#show fex 102 detail

FEX: 102 Description: FEX0102 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1736W19L
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te1/4/6
Fabric interface state:
Po102 - Interface Up.
Te1/4/6 - Interface Up. state: bound
Te2/4/6 - Interface Up. state: bound ß  Ports  connected  SW2/Module  4

Step 15 Check the results of the ping’s in the 4948 during the “issu loadversion”:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (50000/50000), round-trip min/avg/max = 1/1/36 ms
podX-4948-sw#

Step 16 We will now check the output of the command “show issu state”. Notice that there are two
boot variables for the Standby RP. This is because there is a timer running. If the conversion is
not complete by the time the timer expires, then the system will fall back to the older code,
which is listed second in the list.

podX-vss#show issu state

The system is configured to be upgraded in staggered mode.
2 supervisor nodes are found to be online.
Summary: an in-tandem upgrade is in progress.

Slot = 1/1
RP State = Active
ISSU State = Load Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12; ß  “OLD  IMAGE”

Slot = 2/1
RP State = Standby
ISSU State = Load Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1a.bin,12;bootdisk:s2t54-
adventerprisek9-mz.SPA.152-1.SY1.bin,12 ß  “NEW  IMAGE”  followed  by  “OLD  IMAGE”

This system is Fex-capable

Fex-ID ISSU Status

102 FEX_UPGRADE_INIT ß  FEX  will  be  considered  as  a  part  of  ISSU  upgrade
101 FEX_UPGRADE_INIT ß  FEX  will  be  considered  as  a  part  of  ISSU  upgrade

Copyrighted Cisco® Systems Inc. December 2015 63  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 17 In this step we will run the “issu runversion” command, which causes the supervisor or
chassis switchover such that Switch 2 (previous Standby VSS) now assumes the Active role
whilst Switch 1 (previous Active VSS) is reloaded. At this time, Switch 2 transitions from an SSO
Hot Standby state to the Active state. During switchover ~200msec of traffic loss is expected.
Please refer to the “Exercise Description” section for the image that shows this action.
Verify traffic loss experienced with this step on the 4948, you should notice loss of 1 or less ping
packets. If tested with traffic generator, usually 200 msec of traffic loss is seen.

Have your 4948 configured as follows, but do not accept “Sweep range of sizes [n]:” until you
are ready to proceed with the “issu runversion” command in the step below:

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 10X.101.10.1
Repeat count [5]: 50000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:       ß  WAIT!  Don’t  accept  the  “Sweep  range”  until  mid    next  step  

Now run the “issu runversion” command in the VSS system and hit <ENTER> in the 4948
to launch the ping sweep just before running “issu runversion”. You can check the output
taken from Switch 1 below:

podX-4948-sw#
Sweep range of sizes [n]: ß    Hit  Enter  for  the  ping  sweep  in  4948  just  prior  to  issuing  issu  runversion
Type escape sequence to abort.
Sending 50000, 100-byte ICMP Echos to 10X.101.10.1, timeout is 2 seconds:

podX-vss#issu runversion
System configuration has been modified. Save? [yes/no]: yes ß  Save  if  prompted
This command will reload the Active unit. Proceed ? [confirm] ß  Enter  to  confirm  the  runversion
%issu runversion initiated successfully

*Mar 14 14:43:55.406: %RF-SW1-5-RF_RELOAD: Self reload. Reason: Admin ISSU runversion

CLI

<..snip..>

System Bootstrap, Version 12.2(50r)SYS2, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2011 by cisco Systems, Inc.
PYRAMID platform with 2097152 Kbytes of main memory

Autoboot executing command: "boot bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin"

bootdisk:%s72044-atafslib-m: Digitally Signed Release Software with key version A

Initializing ATA monitor library...

<..snip..>  
 

Copyrighted Cisco® Systems Inc. December 2015 64  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss-sdby> ß  previous  active  switch  now  is  standby  switch

Standby console disabled

Step 18 Switch 2 immediately takes over as the Active Supervisor while previously active supervisor
(SW1) reloads. During this transition there is minimal packet loss (1 Packet). We can check this
in the output of the ping sweep in the 4948 switch:

Type escape sequence to abort.

Sending 50000, 100-byte ICMP Echos to 106.101.10.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

<Snip>

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!! ß1  Packet  loss
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  

Step 19 Shortly afterwards, Switch 1 will also return online with the old version of software. Verify the
redundancy state of the VSS using the “show switch virtual redundancy” command
(please note that we will have to enter this command in the console of the new active switch; the
console of the new standby switch is now disabled)
podX-vss#show switch virtual redundancy ß  new  active  switch  
My Switch Id = 2
Peer Switch Id = 1
Last switchover reason = user forced
Configured Redundancy Mode = sso
Operating Redundancy Mode = sso

Switch 2 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = ACTIVE
Uptime in current state = 5 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-
ADVENTERPRISEK9-M), Version 15.2(1)SY1a, RELEASE SOFTWARE (fc6)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Tue 29-Sep-15 15:57 by prod_rel_team
BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = ACTIVE

Switch 1 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = STANDBY HOT (switchover target)
Uptime in current state = 0 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-
ADVENTERPRISEK9-M), Version 15.2(1)SY1, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Mon 11-May-15 00:54 by prod_rel_team

Copyrighted Cisco® Systems Inc. December 2015 65  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1.bin,12;
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = STANDBY

Step 20 Check that all linecards in switch 1 are up. Also Note that the data path from FEX 101 is UP for
both Active Switch (SW2) running the new code and the HotStandby Switch (SW1) running the
old code. You can optionally look also at FEX 102 and at switch 2.

podX-vss#show mod sw 1
Switch Number: 1 Role: Virtual Switch Standby
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Hot) VS-SUP2T-10G SAL16052XQX
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL1019MC05
4 20 DCEF2T 4 port 40GE / 16 port 10GE C6800-16P10G-XL SAL1834ZAKB

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 588d.098a.c5ad to 588d.098a.c5b4 1.2 12.2(50r)SYS 15.2(1)SY1 Ok
2 0017.95b8.087c to 0017.95b8.087f 2.2 12.2(14r)S5 15.2(1)SY1 Ok
4 1005.caea.d482 to 1005.caea.d495 1.0 15.1(58r)SYL 15.2(1)SY1 Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 4 VS-F6K-PFC4 SAL16052UGC 1.1 Ok
1 CPU Daughterboard VS-F6K-MSFC5 SAL16052SLX 1.3 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAL1121PPJG 3.1 Ok
4 Distributed Forwarding Card C6800-DFC-XL SAL1834ZAKB 1.0 Ok

Mod Online Diag Status

---- -------------------
1 Pass ß
2 Pass ß
4 Pass ß Line cards are up

podX-vss#show mod sw 2
Switch Number: 2 Role: Virtual Switch Active
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL16127TU2
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL08435CUF
4 20 DCEF2T 4 port 40GE / 16 port 10GE C6800-16P10G SAL1834ZAA7

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 588d.09e6.d652 to 588d.09e6.d659 1.3 12.2(50r)SYS 15.2(1)SY1a Ok
2 0012.4301.c524 to 0012.4301.c527 2.0 12.2(14r)S5 15.2(1)SY1a Ok
4 1005.caea.d356 to 1005.caea.d369 1.0 15.1(58r)SYL 15.2(1)SY1a Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
Copyrighted Cisco® Systems Inc. December 2015 66  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

1 Policy Feature Card 4 VS-F6K-PFC4 SAL16127M2D 1.2 Ok

1 CPU Daughterboard VS-F6K-MSFC5 SAL16127W7F 1.4 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAD0804067A 2.0 Ok
4 Distributed Forwarding Card C6800-DFC SAL1834ZAA7 1.0 Ok

Mod Online Diag Status

---- -------------------
1 Pass ß
2 Pass ß
4 Pass ß Line cards are up

podX-vss#show fex 101 detail

FEX: 101 Description: FEX0101 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1737W0Q9
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te2/4/5
Fabric interface state:
Po101 - Interface Up.
Te1/4/5 - Interface Up. state: bound ß  
Te2/4/5 - Interface Up. state: bound ß  100%  data  path  Up.

podX-vss#show fex 102 detail

FEX: 102 Description: FEX0102 state: online
FEX version: 15.2(3m)E1
Extender Model: C6800IA-48TD, Extender Serial: FOC1736W19L
FCP ready: yes
Image Version Check: enforced
Fabric Portchannel Ports: 2
Fabric port for control traffic: Te2/4/6
Fabric interface state:
Po102 - Interface Up.
Te1/4/6 - Interface Up. state: bound
Te2/4/6 - Interface Up. state: bound

Step 21 Verify current ISSU state using the “show issu state” command. Notice that Switch 1 still
has OLD_CODE as the only option in its Boot Variable, but Switch 2 has both OLD_CODE and
NEW_CODE.

podX-vss#show issu state

The system is configured to be upgraded in staggered mode.
2 supervisor nodes are found to be online.
Summary: an in-tandem upgrade is in progress.

Slot = 2/1
RP State = Active
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12

Slot = 1/1
RP State = Standby
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12;

This system is Fex-capable

Copyrighted Cisco® Systems Inc. December 2015 67  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Fex-ID ISSU Status

101 FEX_UPGRADE_INIT ß  FEX  will  be  considered  as  a  part  of  ISSU  upgrade
102 FEX_UPGRADE_INIT ß  FEX  will  be  considered  as  a  part  of  ISSU  upgrade  

Step 22 “Issu Acceptversion” provides a window of time to try out the new software version
running on switch 2 and check if things are working as expected. If the “issu
acceptversion” command is not applied within the rollback timer period, the EFSU software
upgrade process will be terminated and the system will try to rollback to the old-image. In this
step we will verify the rollback timer using the “show issu rollback-timer” command

podX-vss#show issu rollback-timer ß  In  this  step  we  only  verify  that  the  rollback-­‐timer  is  runnung  
Rollback Process State = In progress
Configured Rollback Time = 00:45:00
Automatic Rollback Time = 00:31:02

Step 23 In this step we will proceed to stop the rollback timer

podX-vss#issu acceptversion
% Rollback timer stopped. Please issue the 'issu commitversion' command.

podX-vss#show issu rollback-timer ß  In  this  step  we  only  verify  that  the  rollback-­‐timer  is  runnung  
Rollback Process State = Not in progress
Configured Rollback Time = 00:45:00

Step 24 Since our network also has Instant Access clients, we are going to proceed and upgrade those
clients in this step using the added command “issu runversion fex”. We have different
options to proceed with this upgrade: all the clients at once of in stages. We will look at the
options available running the command below:

podX-vss#issu runversion fex ?

WORD Comma-separated list of fex switch id's
all Upgrade all enabled fex switches
 

Step 25 We are now going to upgrade all the Instance access clients at once running the command
“issu runversion fex all”

NOTE: Instead of doing “issu runversion fex all”. The FEX clients can be upgraded one at a time by issuing “issu
runversion fex <fex-id>. Or It can have rolling upgrade across multiple FEX’s by issuing “issu run version fex <fex-
id1>, <fex-id2>…
 
podX-vss#issu runversion fex all

% Successfully initiated 'runversion fex' for Fex IDs: 102 101.

Use 'show issu state' for more information.

*Dec 7 14:15:10.159: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download : In

progress
*Dec 7 14:15:10.191: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download : In
progress
Copyrighted Cisco® Systems Inc. December 2015 68  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

*Dec 7 14:15:30.323: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download : Checking

the versions
*Dec 7 14:15:30.791: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download : Checking
the versions
*Dec 7 14:15:33.383: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download : Removing
partially installed images(if any).
*Dec 7 14:15:33.831: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download : Removing
partially installed images(if any).
*Dec 7 14:15:36.387: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download : Checking
available space in flash
*Dec 7 14:15:36.835: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download : Checking
available space in flash
*Dec 7 14:15:39.407: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download :
Downloading the images to flash
*Dec 7 14:15:39.851: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download :
Downloading the images to flash
*Dec 7 14:16:13.175: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download : In
progress
*Dec 7 14:16:13.199: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download : In
progress
*Dec 7 14:16:47.235: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download : Extracting
images from archive into flash
*Dec 7 14:16:47.531: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download : Extracting
images from archive into flash
*Dec 7 14:16:50.299: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download : Extracting
images from archive into flash on switch 2
*Dec 7 14:16:50.599: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download : Extracting
images from archive into flash on switch 2

Step 26 We can now monitor the status of the upgrade using the “show issu state” command.

podX-vss#show issu state

The system is configured to be upgraded in staggered mode.
2 supervisor nodes are found to be online.
Summary: an in-tandem upgrade is in progress.

Slot = 2/1
RP State = Active
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12

Slot = 1/1
RP State = Standby
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12;

This system is Fex-capable

Fex-ID ISSU Status

101 FEX_UPGRADE_IN_PROGRESS ß  Image  download  initiated  for  FEX.  FEX  will  start  image  download    and  
           extraction  of  downloaded  tar  image  and  rebooting  with  new  image.
102 FEX_UPGRADE_IN_PROGRESS

Step 27 You will see the following output from VSS active console during the FEX upgrade:

podX-vss#
*Dec 7 14:28:50.423: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download :
In progress
*Dec 7 14:28:50.439: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download :
In progress

Copyrighted Cisco® Systems Inc. December 2015 69  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

*Dec 7 14:29:31.727: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download :

Installing the images
*Dec 7 14:29:38.419: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download :
Software Installation completed
*Dec 7 14:29:41.427: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 101) ISSU Image Download :
Reloading the FEX
7 14:29:42.437: %SYS-5-RELOAD: Reload requested by FEX Rolling Upgrade ICC process.
Reload Reason: ISSU requested for reload. (FEX-101)
*Dec 7 14:29:48.531: %SATMGR-SW2-5-FABRIC_PORT_DOWN: SDP down on interface Te1/4/5,
connected to FEX 101, uplink 51 (reason: link down)
*Dec 7 14:29:48.531: %SATMGR-SW2-3-ERR_DUAL_ACTIVE_DETECT_INCAPABLE: channel group
101 is no longer dual-active detection capable
*Dec 7 14:29:50.531: %SATMGR-SW2-5-FEX_MODULE_OFFLINE: FEX 101, module 1 offline
(reason: all fabric links down)
*Dec 7 14:29:50.531: %SATMGR-SW2-5-FABRIC_PORT_DOWN: SDP down on interface Te2/4/5,
connected to FEX 101, uplink 107 (reason: link down)
*Dec 7 14:29:50.547: %SATMGR-SW2-5-FEX_MODULE_OFFLINE: FEX 101, module 2 offline
(reason: all fabric links down)
*Dec 7 14:29:50.571: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet2/4/5, changed
state to down
*Dec 7 14:29:50.647: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface
TenGigabitEthernet2/4/5, changed state to down
*Dec 7 14:29:50.671: %OIR-SW2-6-INSREM: Switch 101 Physical Slot 1 - Module Type
LINE_CARD removed
*Dec 7 14:29:50.763: %OIR-SW2-6-INSREM: Switch 101 Physical Slot 2 - Module Type
LINE_CARD removed

<..snip..>

*Dec 7 14:30:50.775: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download :

Installing the images
*Dec 7 14:30:55.995: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download :
Software Installation completed
*Dec 7 14:30:56.443: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download :
In progress
*Dec 7 14:30:58.999: %FEXMGR-SW2-6-IMAGE_DNLD_STATUS: (FEX 102) ISSU Image Download :
Reloading the FEX
7 14:30:59.584: %SYS-5-RELOAD: Reload requested by FEX Rolling Upgrade ICC process.
Reload Reason: ISSU requested for reload. (FEX-102)
*Dec 7 14:31:06.091: %SATMGR-SW2-5-FABRIC_PORT_DOWN: SDP down on interface Te1/4/6,
connected to FEX 102, uplink 51 (reason: link down)
*Dec 7 14:31:06.091: %SATMGR-SW2-3-ERR_DUAL_ACTIVE_DETECT_INCAPABLE: channel group
102 is no longer dual-active detection capable
*Dec 7 14:31:08.107: %SATMGR-SW2-5-FEX_MODULE_OFFLINE: FEX 102, module 1 offline
(reason: all fabric links down)
*Dec 7 14:31:08.107: %SATMGR-SW2-5-FABRIC_PORT_DOWN: SDP down on interface Te2/4/6,
connected to FEX 102, uplink 107 (reason: link down)
*Dec 7 14:31:08.123: %SATMGR-SW2-5-FEX_MODULE_OFFLINE: FEX 102, module 2 offline
(reason: all fabric links down)
*Dec 7 14:31:08.147: %LINK-SW2-3-UPDOWN: Interface TenGigabitEthernet2/4/6, changed
state to down
*Dec 7 14:31:08.215: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface
TenGigabitEthernet2/4/6, changed state to down
*Dec 7 14:31:08.231: %OIR-SW2-6-INSREM: Switch 102 Physical Slot 1 - Module Type
LINE_CARD removed
*Dec 7 14:31:08.347: %OIR-SW2-6-INSREM: Switch 102 Physical Slot 2 - Module Type
LINE_CARD removed

<..snip..>

*Mar 14 17:23:34.366: %OIR-SW2-6-SP_INSCARD: Card inserted in Switch_number = 101,

physical slot 1, interfaces are now online
Copyrighted Cisco® Systems Inc. December 2015 70  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

*Mar 14 17:23:34.366: %OIR-SW2-6-SP_INSCARD: Card inserted in Switch_number = 101,

physical slot 2, interfaces are now online
 

Step 28 We can now monitor the completion of the upgrade using the “show issu state” command.
This step takes a few minutes to you will have to wait to get to the
“FEX_UPGRADE_COMPLETE” state.
podX-vss#show issu state
The system is configured to be upgraded in staggered mode.
2 supervisor nodes are found to be online.
Summary: an in-tandem upgrade is in progress.

Slot = 2/1
RP State = Active
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12

Slot = 1/1
RP State = Standby
ISSU State = Run Version
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12;

This system is Fex-capable

Fex-ID ISSU Status

101 FEX_UPGRADE_COMPLETE ß  FEX  is  successfully  upgraded  to  new  image  

102 FEX_UPGRADE_COMPLETE

Step 29 The final step of the EFSU process is “issu commitversion”. Once the new image is ready
to be rolled out, perform the “issu commitversion” command. It will cause a reload of
Switch 1 (VSS Standby) so that it can load with the new software image. We will verify and we
will verify traffic loss experienced with this step on the 4948. You should notice a maximum of 1
ping packet being lost. If tested with traffic generator, usually 200 msec of traffic loss is seen.
Have your 4948 configured as follows, but do not accept “Sweep range of sizes [n]:” until you
are ready to run with the “issu commitversion” command in the step below:

podX-4948-sw#ping
Protocol [ip]:
Target IP address: 10X.101.10.1
Repeat count [5]: 50000
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]: ß  WAIT!  Don’t  accept  the  “Sweep  range”  until  mid    next  step  
 
Perform the “issu commitversion” in the VSS system and you can compare with the output
below taken from Switch 2, current active switch:

podX-4948-sw#
Sweep range of sizes [n]: ß    Hit  Enter  for  the  ping  sweep  in  4948  just  prior  to  issuing  issu  commitversion
Type escape sequence to abort.
Sending 50000, 100-byte ICMP Echos to 106.101.10.1, timeout is 2 seconds:

Copyrighted Cisco® Systems Inc. December 2015 71  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

podX-vss#issu commitversion
%issu commitversion initiated successfully, upgrade sequence will continue shortly

podX-vss#
*Dec 7 15:39:45.699: %ISSU_PROCESS-SW2-3-COMMITVERSION: issu commitversion;
Commitversion sequence will begin in 60 seconds. Enter 'issu abortversion' to cancel.
*Dec 7 15:40:03.483: %SYS-SW2-5-CONFIG_I: Configured from console by console
*Dec 7 15:40:15.699: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Resetting Standby
shortly

*Dec 7 15:40:15.703: %ISSU_PROCESS-SW1_STBY-6-SELF_RELOAD: slot 17 countdown to self-

reload started, 30 second delay
*Dec 7 15:40:45.767: %VSLP-SW2-3-VSLP_LMP_FAIL_REASON: Te2/1/4: Link down
*Dec 7 15:40:45.803: %VSLP-SW2-3-VSLP_LMP_FAIL_REASON: Te2/1/5: Link down
*Dec 7 15:40:45.803: %VSLP-SW2-2-VSL_DOWN: Last VSL interface Te2/1/5 went down
*Dec 7 15:40:45.811: %VSLP-SW2-2-VSL_DOWN: All VSL links went down while switch is
in ACTIVE role
*Dec 7 15:40:45.887: %PFREDUN-SW2-6-ACTIVE: Standby processor removed or reloaded,
changing to Simplex mode
*Dec 7 15:40:46.043: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 1 - Module Type
LINE_CARD removed
*Dec 7 15:40:46.095: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 2 - Module Type
LINE_CARD removed
*Dec 7 15:40:46.179: %SATMGR-SW2-5-FEX_MODULE_OFFLINE: FEX 101, module 1 offline
(reason: all fabric links down)
*Dec 7 15:40:46.179: %SATMGR-SW2-5-FABRIC_PORT_DOWN: SDP down on interface Te1/4/5,
connected to FEX 101, uplink 51 (reason: link down)
*Dec 7 15:40:46.183: %SATMGR-SW2-5-FEX_MODULE_OFFLINE: FEX 102, module 1 offline
(reason: all fabric links down)
*Dec 7 15:40:46.183: %SATMGR-SW2-5-FABRIC_PORT_DOWN: SDP down on interface Te1/4/6,
connected to FEX 102, uplink 51 (reason: link down)
*Dec 7 15:40:46.215: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 4 - Module Type
LINE_CARD removed
*Dec 7 15:40:46.263: %OIR-SW2-6-INSREM: Switch 101 Physical Slot 1 - Module Type
LINE_CARD removed
*Dec 7 15:40:46.311: %OIR-SW2-6-INSREM: Switch 102 Physical Slot 1 - Module Type
LINE_CARD removed
*Dec 7 15:41:00.699: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby has gone offline
<..snip..>

*Dec 7 15:43:18.051: %VSLP-SW2-5-VSLP_LMP_PASS_REASON: interface Te2/1/4: Link up

*Dec 7 15:43:27.423: %PFREDUN-SW2-6-ACTIVE: Standby initializing for SSO mode
*Dec 7 15:43:30.699: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby has come online,
wait for terminal state

<..snip..>
*Dec 7 15:45:42.439: %OIR-SW2-6-INSREM: Switch 1 Physical Slot 4 - Module Type
LINE_CARD inserted
Copyrighted Cisco® Systems Inc. December 2015 72  
Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

*Dec 7 15:45:45.707: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Standby has reached

terminal state

*Dec 7 15:45:45.707: %ISSU_PROCESS-SW2-6-COMMITVERSION_INFO: Upgrade has completed,

updating boot configuration

Step 30 Verify traffic loss experienced with this step on the 4948. You should notice a maximum of 1
ping packet being lost. If tested with traffic generator, usually ~200 msec traffic loss is seen. At
this point, the VSS will forward traffic with 50% bandwidth capacity until Switch 1 completely
boots up with the NEW_IMAGE

Step 31 Once Switch 1 has come online, execute “show issue state” and notice the process is
completed and returned to “Init” state:

podX-vss#show issu state

The system is configured to be upgraded in staggered mode.
2 supervisor nodes are found to be online.
Summary: the system will be upgraded in in-tandem mode.

Slot = 2/1
RP State = Active
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12

Slot = 1/1
RP State = Standby
ISSU State = Init
Boot Variable = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12

This system is Fex-capable

Fex-ID ISSU Status

101 FEX_INIT ß  FEX    is  online  sate  (exists  only  when  ISSU  is  not  in  progress)
102 FEX_INIT

Step 32 Once again we now need to manually boot the second switch in the stack for FEX 101 and FEX
102.

Console into FEX 101:

Switch: boot ß  Type  “boot”  to  manually  boot  the  Stack  member.  Note  in  real  world  IA  deployments,  all  IA  Clients  
automatically  boot  up  and  would  not  require  any  manual  boot  step.

Loading "flash:/c6800ia-universalk9-mz.152-3m.E2/c6800ia-universalk9-mz.152-
3m.E2.bin"...Verifying image flash:/c6800ia-universalk9-mz.152-3m.E2/c6800ia-
universalk9-mz.152-
3m.E2.bin.............................................................................
......................................................................................
......................................................................................
..........................Image passed digital signature
verification..........................................................................
......................................................................................

Copyrighted Cisco® Systems Inc. December 2015 73  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

............................................................................Image
passed digital signature verification
@@@@@@@@@@@@@@@...

Console into FEX 102:

Switch: boot ß  Type  “boot”  to  manually  boot  the  Stack  member.  Note  in  real  world  IA  deployments,  all  IA  Clients  
automatically  boot  up  and  would  not  require  any  manual  boot  step.

Loading "flash:/c6800ia-universalk9-mz.152-3m.E2/c6800ia-universalk9-mz.152-
3m.E2.bin"...Verifying image flash:/c6800ia-universalk9-mz.152-3m.E2/c6800ia-
universalk9-mz.152-
3m.E2.bin...........................................................

Step 33 Once Switch 1 has come online, execute “show module switch 1” and notice that the
version of code in the “Sw” column is NEW_IMAGE running on C6k. Execute “show module
switch 2”. Is the same information there for Standby C6k switch?

podX-vss#show module switch 1

Switch Number: 1 Role: Virtual Switch Standby
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Hot) VS-SUP2T-10G SAL161282WL
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL1103EENU
4 20 DCEF2T 4 port 40GE / 16 port 10GE WS-X6904-40G SAL1801K47W

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 588d.09e6.d8fb to 588d.09e6.d902 1.3 12.2(50r)SYS 15.1(2)SY4 Ok ß  Should  see    
                 “NEW_IMAGE”  here
2 001a.6cf5.8104 to 001a.6cf5.8107 2.5 12.2(14r)S5 15.1(2)SY4 Ok
4 c471.fe83.9b5c to c471.fe83.9b6f 1.0 12.2(50r)SYL 15.1(2)SY4 Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 4 VS-F6K-PFC4 SAL161286VM 1.2 Ok
1 CPU Daughterboard VS-F6K-MSFC5 SAL161281NC 1.4 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAL1101DBC7 3.1 Ok
4 Distributed Forwarding Card WS-F6K-DFC4-E SAL1743F2ZY 1.2 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass
4 Pass

podX-vss#show module switch 2

Switch Number: 2 Role: Virtual Switch Active
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL16095XRR
2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL1104F8RT
4 20 DCEF2T 4 port 40GE / 16 port 10GE WS-X6904-40G SAL1752JJJ4

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

Copyrighted Cisco® Systems Inc. December 2015 74  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

1 588d.098a.df27 to 588d.098a.df2e 1.3 12.2(50r)SYS 15.1(2)SY4 Ok ß  Should  see    

                         “NEW_IMAGE”  here
2 001a.a10e.8330 to 001a.a10e.8333 2.5 12.2(14r)S5 15.1(2)SY4 Ok
4 24e9.b3e1.e2dc to 24e9.b3e1.e2ef 1.0 12.2(50r)SYL 15.1(2)SY4 Ok

Mod Sub-Module Model Serial Hw Status

---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 4 VS-F6K-PFC4 SAL16095ZM0 1.1 Ok
1 CPU Daughterboard VS-F6K-MSFC5 SAL16095WFN 1.4 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAD11080AHL 3.1 Ok
4 Distributed Forwarding Card WS-F6K-DFC4-E SAL1802KKLX 1.0 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass
4 Pass

Step 34 Verify the software image in C6800IA clients are also upgraded. Issue the following command:
podX-vss#show version fex 101
==> Showing version for FEX 101:
Cisco IOS Software, C6800IA Software (C6800IA-UNIVERSALK9-M), Version 15.2(3m)E2,
RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Fri 18-Sep-15 09:59 by prod_rel_team

ROM: Bootstrap program is C2960X boot loader

BOOTLDR: C6800IA Boot Loader (C6800IA-HBOOT-M) Version 15.0(2r)EX2, RELEASE SOFTWARE
(fc1)

FEX-102 uptime is 40 minutes

System returned to ROM by power-on
System restarted at 15:43:51 UTC Mon Dec 7 2015
System image file is "flash:/c6800ia-universalk9-mz.152-3m.E2/c6800ia-universalk9-
mz.152-3m.E2.bin"
Last reload reason: Unknown reason

<..snip..>

podX-vss#show mod fex 101

Switch Number: 101 Role: FEX
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 C6800IA 48GE C6800IA-48TD FOC1737W0Q9
2 48 C6800IA 48GE C6800IA-48TD FOC1737W0P2

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------
1 34db.fd09.3980 to 34db.fd09.39b3 0.0 Unknown 15.2(3m)E2 Ok
2 c025.5ca1.ef00 to c025.5ca1.ef33 0.0 Unknown 15.2(3m)E2 Ok

Mod Online Diag Status

---- -------------------
1 Pass
2 Pass

Copyrighted Cisco® Systems Inc. December 2015 75  

Cisco Catalyst Virtual Switching System and Instant Access Lab Guide

Step 35 Lastly run “show switch virtual redundancy”

podX-vss#show switch virtual redundancy
My Switch Id = 2
Peer Switch Id = 1
Last switchover reason = user forced
Configured Redundancy Mode = sso
Operating Redundancy Mode = sso

Switch 2 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = ACTIVE
Uptime in current state = 2 hours, 28 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-
ADVENTERPRISEK9-M), Version 15.2(1)SY1a, RELEASE SOFTWARE (fc6)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Tue 29-Sep-15 15:57 by prod_rel_team
BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = ACTIVE

Switch 1 Slot 1 Processor Information :

-----------------------------------------------
Current Software state = STANDBY HOT (switchover target)
Uptime in current state = 41 minutes
Image Version = Cisco IOS Software, s2t54 Software (s2t54-
ADVENTERPRISEK9-M), Version 15.2(1)SY1a, RELEASE SOFTWARE (fc6)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Tue 29-Sep-15 15:57 by prod_rel_team
BOOT = bootdisk:s2t54-adventerprisek9-mz.SPA.152-
1.SY1a.bin,12;bootdisk:s2t54-adventerprisek9-mz.SPA.152-1.SY1.bin,12
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = STANDBY

þ End of Lab: Congratulations! You have successfully completed the lab… J

Please let your proctor know you’re finished & provide any feedback to help improve the lab experience.

Copyrighted Cisco® Systems Inc. December 2015 76