C H A P T E R 4 Configuring Virtual Switching Systems This chapter describes how to configure a virtual switching system (VSS) for the Catalyst 6500 series switch. Cisco IOS Release 12.2(33)SXH1 and later releases support VSS. Note For complete syntax and usage information for the commands used in this chapter, see these publications: • The Cisco IOS Virtual Switch Command Reference at this URL: http://www.cisco.com/en/US/docs/ios/vswitch/command/reference/vs_book.html • The Cisco IOS Release 12.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems • Packet Handling, page 4-16 • System Monitoring, page 4-20 • Dual-Active Detection, page 4-22 • VSS Initialization, page 4-24 • VSS Configuration Guidelines and Restrictions, page 4-27 VSS Overview Network operators increase network reliability by configuring redundant pairs of network devices and links. Figure 4-1 shows a typical switch network configuration.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Key Concepts The VSS incorporates the following key concepts: • Virtual Switching System, page 4-3 • VSS Active and VSS Standby Chassis, page 4-3 • Virtual Switch Link, page 4-4 • Multichassis EtherChannel, page 4-5 Virtual Switching System A VSS combines a pair of switches into a single network element.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Virtual Switch Link For the two chassis of the VSS to act as one network element, they need to share control information and data traffic. The virtual switch link (VSL) is a special link that carries control and data traffic between the two chassis of a VSS, as shown in Figure 4-3. The VSL is implemented as an EtherChannel with up to eight links.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Note • mls ipx • mls netflow • mls rp • mls switching • no • shutdown The mls qos command is not available when a port is in VSL restricted mode. Multichassis EtherChannel An EtherChannel (also known as a port channel) is a collection of two or more physical links that combine to form one logical link. Layer 2 protocols operate on the EtherChannel as a single logical entity.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems VSS Functionality The following sections describe the main functionality of a VSS: • Redundancy and High Availability, page 4-6 • Packet Handling, page 4-6 • System Management, page 4-6 • VSS Quad-Sup Uplink Forwarding, page 4-7 • Interface Naming Convention, page 4-8 • Software Features, page 4-8 Redundancy and High Availability In a VSS, supervisor engine redundancy operates between the VSS active and VS
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems VSS Quad-Sup Uplink Forwarding When you use VSS quad-supervisor uplink forwarding, the in-chassis standby (ICS) supervisor engine acts as a DFC line card. Only one processor, the SP processor, acts as the DFC line card; the RP processor is reset to ROMMON. During the bootup, once the chassis level role is resolved, the ICS downloads the image from the in-chassis active (ICA) supervisor engine.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems • In-chassis RPR switchover—ICS supervisor engines in the supervisor engine 1 and supervisor engine 2 positions boot up as RPR-Warm. RPR-Warm is when a supervisor engine acts as a DFC. When a VSS stateful switchover occurs, the supervisor engine is reset to ROMMON and boot ups with the supervisor engine image. You can verify the switchover mode of the supervisor engines by entering the show module command.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems • Multichassis EtherChannel Requirements, page 4-10 • Service Module Support, page 4-10 Chassis and Modules Table 4-1 describes the hardware requirements for the VSS chassis and modules. Table 4-1 VSS Hardware Requirements Hardware Chassis Count Requirements 2 The VSS is available on chassis that support VS-S720-10G supervisor engines and WS-X6708-10G switching modules.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Note • When using the 10-Gigabit Ethernet ports on the WS-X6716-10G or WS-X6716-10T switching module as VSL links, you must operate the ports in performance, not oversubscription, mode. If you enter the no hw-module switch x slot y oversubscription command to configure non-oversubscription mode (performance mode), then only ports 1, 5, 9, and 13 are configurable; the other ports on the module are disabled.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Understanding VSL Topology A VSS contains two chassis that communicate using the VSL, which is a special port group. We recommend that you configure both of the 10-Gigabit Ethernet ports on the supervisor engines as VSL ports. Optionally, you can also configure the VSL port group to contain switching module 10-Gigabit Ethernet ports. This configuration provides additional VSL capacity.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems RPR and SSO Redundancy A VSS operates with stateful switchover (SSO) redundancy if it meets the following requirements: • Both supervisor engines must be running the same software version. • VSL-related configuration in the two chassis must match. • PFC mode must match. • SSO and nonstop forwarding (NSF) must be configured on each chassis.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Failed Chassis Recovery If the VSS active chassis or supervisor engine fails, the VSS initiates a stateful switchover (SSO) and the former VSS standby supervisor engine assumes the VSS active role. The failed chassis performs recovery action by reloading the supervisor engine. If the VSS standby chassis or supervisor engine fails, no switchover is required.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems User Actions From the VSS active chassis command console, you can initiate a VSS switchover or a reload. If you enter the reload command from the command console, the entire VSS performs a reload. To reload only the VSS standby chassis, use redundancy reload peer command. To force a switchover from the VSS active to the VSS standby supervisor engine, use the redundancy force-switchover command.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Figure 4-8 MEC Topology Router, switch or server MEC Virtual switch Supervisor engine Active chassis Standby chassis 181327 Supervisor engine MEC Failure Scenarios We recommend that you configure the MEC with at least one link to each chassis.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems All MEC Links to the VSS Standby Chassis Fail If all links fail to the VSS standby chassis, the MEC becomes a regular EtherChannel with operational links to the VSS active chassis. Control protocols continue to run in the VSS active chassis. All control and data traffic from the VSS standby chassis reaches the MEC by crossing the VSL to the VSS active chassis.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems The following sections describe packet handling in a VSS: • Traffic on the VSL, page 4-17 • Layer 2 Protocols, page 4-17 • Layer 3 Protocols, page 4-18 • SPAN, page 4-20 Traffic on the VSL The VSL carries data traffic and in-band control traffic between the two chassis.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Spanning Tree Protocol The VSS active chassis runs Spanning Tree Protocol (STP). The VSS standby chassis redirects STP BPDUs across the VSL to the VSS active chassis. The STP bridge ID is commonly derived from the chassis MAC address. To ensure that the bridge ID does not change after a switchover, the VSS continues to use the original chassis MAC address for the STP Bridge ID.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Hardware forwarding is distributed across all DFCs on the VSS. The supervisor engine on the VSS active chassis sends FIB updates to all local DFCs, remote DFCs, and the VSS standby supervisor engine PFC. All hardware routing uses the router MAC address assigned by the VSS active supervisor engine. After a switchover, the original MAC address is still used.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Software Features Software features run only on the VSS active supervisor engine. Incoming packets to the VSS standby chassis that require software processing are sent across the VSL. For features supported in hardware, the ACL configuration is sent to the TCAM manager on the VSS active supervisor engine, the VSS standby supervisor engine, and all DFCs. SPAN The VSS supports all SPAN features for non-VSL interfaces.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems File System Access You can access file systems of both chassis from the VSS active chassis. Prefix the device name with the switch number and slot number to access directories on the VSS standby chassis. For example, the command dir sw2-slot6-disk0: lists the contents of disk0 on the VSS standby chassis (assuming switch 2 is the VSS standby chassis).
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Network Management The following sections describe network management for a VSS: • Telnet over SSH Sessions and the Web Browser User Interface, page 4-22 • SNMP, page 4-22 • Command Console, page 4-22 Telnet over SSH Sessions and the Web Browser User Interface A VSS supports remote access using Telnet over SSH sessions and the Cisco web browser user interface.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems If the original VSS active chassis is still operational, both chassis are now VSS active. This situation is called a dual-active scenario. A dual-active scenario can have adverse affects on network stability, because both chassis use the same IP addresses, SSH keys, and STP bridge ID. The VSS must detect a dual-active scenario and take recovery action.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Dual-Active Detection Using IP BFD To use the IP BFD detection method, you must provision a direct Ethernet connection between the two switches. Regular Layer 3 ping will not function correctly on this connection, as both chassis have the same IP address. The VSS instead uses the Bidirectional Forwarding Detection (BFD) protocol. If the VSL fails, both chassis create BFD neighbors, and try to establish adjacency.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems VSS initialization is described in the following sections: • Virtual Switch Link Protocol, page 4-25 • SSO Dependencies, page 4-25 • Initialization Procedure, page 4-26 Virtual Switch Link Protocol The Virtual Switch Link Protocol (VSLP) consists of several protocols that contribute to virtual switch initialization.
Chapter 4 Configuring Virtual Switching Systems Understanding Virtual Switching Systems Each chassis in the VSS determines its system PFC mode. If the supervisor engine of a given chassis is provisioned with PFC3CXL and all the switching modules in the chassis are provisioned with DFC3CXL, the PFC mode for the chassis is PFC3CXL. However, if any of the switching modules is provisioned with DFC3C, the chassis PFC mode will be set to PFC3C.
Chapter 4 Configuring Virtual Switching Systems VSS Configuration Guidelines and Restrictions VSL Down If the VSL is down when both chassis try to boot up, the situation is similar to a dual-active scenario. One of the chassis becomes VSS active and the other chassis initiates recovery from the dual-active scenario. For further information, see the “Configuring Dual-Active Detection” section on page 4-45.
Chapter 4 Configuring Virtual Switching Systems VSS Configuration Guidelines and Restrictions Multichassis EtherChannel Restrictions and Guidelines When configuring MECs, note the following guidelines and restrictions: • All links in an MEC must terminate locally on the VSS active or VSS standby chassis of the same virtual domain. • For an MEC using the LACP control protocol, the minlinks command argument defines the minimum number of physical links in each chassis for the MEC to be operational.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS – exit – load-interval – logging – no – shutdown • ASIC-specific QoS commands are not configurable on dual-active detection fast hello ports directly, but are allowed to remain on the fast hello port if the commands were configured on another non-fast hello port in that same ASIC group. For a list of these commands, see the “PFC QoS Configuration Guidelines and Restrictions” section on page 43-52.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Converting to a VSS By default, the Catalyst 6500 series switch is configured to operate in standalone mode (the switch is a single chassis). The VSS combines two standalone switches into one virtual switch, operating in virtual switch mode. Note When you convert two standalone switches into one VSS, all non-VSL configuration settings on the VSS standby chassis will revert to the default configuration.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Backing Up the Standalone Configuration Save the configuration files for both chassis operating in standalone mode. You need these files to revert to standalone mode from virtual switch mode. On Switch 1, perform this task: Command Step 1 Step 2 Purpose (Optional) Saves the running configuration to startup configuration. Switch-1# copy running-config startup-config Copies the startup configuration to a backup file.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Command Purpose Step 3 Switch-2(config-red)# exit Exits redundancy configuration mode. Step 4 Switch-2(config)# router routing_protocol processID Enables routing, which places the router in router configuration mode. Step 5 Switch-2(config-router)# nsf Enables NSF operations for the routing protocol. Step 6 Switch-2(config-router)# end Exits to privileged EXEC mode.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Configuring VSL Port Channel and Ports The VSL is configured with a unique port channel on each chassis. During the conversion, the VSS configures both port channels on the VSS active chassis. If the VSS standby chassis VSL port channel number has been configured for another use, the VSS comes up in RPR mode. To avoid this situation, check that both port channel numbers are available on both of the chassis.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Perform the following task on Switch 2: Step 1 Command Purpose Switch-2(config)# interface range tengigabitethernet 5/2-3 Enters configuration mode for interface range tengigabitethernet 5/2-3 on Switch 2. Step 2 Switch-2(config-if)# channel-group 20 mode on Adds this interface to channel group 20. Step 3 Switch-2(config-if)# no shutdown Activates the port.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS To convert Chassis 2 to virtual switch mode, perform this task on Switch 2: Command Purpose Switch-2# switch convert mode virtual Converts Switch 2 to virtual switch mode. After you enter the command, you are prompted to confirm the action. Enter yes. The system creates a converted configuration file, and saves the file to the RP bootflash.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Displaying VSS Information To display basic information about the VSS, perform one of these tasks: Command Purpose Router# show switch virtual Displays the virtual switch domain number, and the switch number and role for each of the chassis. Router# show switch virtual role Displays the role, switch number, and priority for each of the chassis in the VSS. Router# show switch virtual link Displays the status of the VSL.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Copying the VSS Configuration to a Backup File Save the configuration file from the VSS active chassis. You may need this file if you convert to virtual switch mode again. You only need to save the file from the VSS active chassis, because the configuration file on the VSS standby chassis is identical to the file on the VSS active chassis.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Configuring VSS Parameters These sections describe how to configure VSS parameters: • Configuring VSL Switch Priority, page 4-38 • Configuring PFC Mode, page 4-39 • Configuring PFC Mode, page 4-39 • Configuring a VSL, page 4-40 • Displaying VSL Information, page 4-40 • Configuring VSL QoS, page 4-41 • Subcommands for VSL Port Channels, page 4-42 • Subcommands for VSL Ports, page 4-42 • Configuring the Router MAC Address As
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Note If you make configuration changes to the switch priority, the changes only take effect after you save the running configuration to the startup configuration file and perform a reload. The show switch virtual role command shows the operating and priority values. You can manually set the VSS standby switch to VSS active using the redundancy force-switchover command.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Configuring a VSL To configure a port channel to be a VSL, perform this task: Command Purpose Step 1 Router(config)# interface port-channel channel_num Enters configuration mode for the specified port channel. Step 2 Router(config-if)# switch virtual link switch_num Assigns the port channel to the virtual link for the specified switch. Note We recommend that you configure the VSL prior to converting the chassis into a VSS.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS R - Layer3 S - Layer2 U - in use N - not in use, no aggregation f - failed to allocate aggregator M m u w - not in use, no aggregation due to minimum links not met not in use, port not aggregated due to minimum links not met unsuitable for bundling waiting to be aggregated Group Port-channel Protocol Ports ------+-------------+-----------+--------------------------------------------10 Po10(RU) Te1/5/4(P) Te1/5/5(P) 20 Po20(RU) Te2/5/4(P)
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Subcommands for VSL Port Channels On a VSL port channel, only a subset of interface subcommands are available in the command console. Table 4-2 describes the available interface subcommands. Table 4-2 Interface Subcommands for VSL Port Channels Subcommand Description default Sets a command to its defaults. description Enters a text description for the interface. exit Exits from interface configuration mode.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Configuring the Router MAC Address Assignment When the VSS is started for the first time, the initial VSS active supervisor engine assigns a router MAC address for the VSS. By default, the supervisor engine assigns a MAC address from its own chassis. After a switchover to the second chassis, the VSS continues to use the MAC address from the previously VSS active chassis as the router MAC address.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Configuring Deferred Port Activation During VSS Standby Recovery Instead of allowing all ports to be activated simultaneously when a failed chassis is restarted as the VSS standby chassis, you can configure the system to defer activation of non-VSL ports and then activate the ports in groups over a period of time.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS The Configuring Port Load Share Deferral on the Peer Switch section provides additional details about MECs: Configuring Port Load Share Deferral on the Peer Switch To configure the load share deferral feature for a port channel, perform this task on the switch that is an MEC peer to the VSS: Step 1 Command Purpose Router(config)# port-channel load-defer seconds (Optional) Configures the port load share deferral interval for all port c
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Note Before changing PAgP dual-active detection configuration, ensure that all port channels with trust mode enabled are in administrative down state. Use the shutdown command in interface configuration mode for the port channel. Remember to use the no shutdown command to reactivate the port channel when you are finished configuring dual-active detection.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Router(config-vs-domain)# dual-active detection pagp trust channel-group 20 Trusted port-channel 20 is not administratively down. To change the pagp dual-active trust configuration, “shutdown” the port-channel first. Remember to “no shutdown” the port-channel afterwards. Configuring BFD Dual-Active Detection For the BFD dual-active detection, you must configure dual-active interface pairs that will act as BFD messaging links.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Router (config-vs-domain)# dual-active detection bfd Router (config-vs-domain)# dual-active pair interface g 1/9/48 interface g 2/1/48 bfd adding a static route 200.230.230.0 255.255.255.0 Gi2/1/48 for this dual-active pair adding a static route 201.230.230.0 255.255.255.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS WARNING: Interface FastEthernet1/2/40 placed in restricted config mode.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Fast-hello dual-active detection enabled: Yes No interfaces excluded from shutdown in recovery mode In dual-active recovery mode: No This example shows how to display information for BFD dual-active detection: Router# show switch virtual dual-active bfd Bfd dual-active detection enabled: Yes Bfd dual-active interface pairs configured: interface1 Gi1/9/48 interface2 Gi2/1/48 This example shows how to display information for fast-hello dua
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Note The show switch virtual dual-active pagp command displays the same output as the show pagp dual-active command. Configuring Service Modules in a VSS To configure a service module in a VSS, you must add the switch number to many of the configuration commands, as described in this section. Note For detailed instructions on configuring a service module in a VSS, see the configuration guide and command reference for the service module.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Assigning a VLAN Group to a Firewall Service Module in a VSS To assign a VLAN group to a FWSM, perform this task: Command Purpose Router(config)# firewall switch num slot slot vlan-group [vlan_group | vlan_range] Assigns VLANs to a firewall group in the specified module. • num—Specifies the switch to access; valid values are 1 and 2. • slot—Specifies the slot number of the module. • vlan_group—Specifies the group ID as an integer.
Chapter 4 Configuring Virtual Switching Systems Configuring a VSS Verifying Injected Routes in a Service Module in a VSS To view route health injection (RHI) routes, perform this task: Command Purpose Router# show svclc rhi-routes switch num slot slot Displays injected RHI routes in the specified service module. • num—Specifies the switch to access; valid values are 1 and 2. • slot—Specifies the slot number of the module.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Upgrading a VSS Cisco IOS Rel ease 12.2(33)SXH supports a fast software upgrade (FSU) of the VSS using RPR. Cisco IOS Release 12.2(33)SXI and later releases support an enhanced fast software upgrade (eFSU) of the VSS using SSO.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Step 8 Command Purpose Router# redundancy reload peer Reloads the VSS standby chassis and brings it back online running the new version of the Cisco IOS software. Due to the software version mismatch between the two chassis, the VSS standby chassis will be in RPR redundancy mode.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS eFSU Restrictions and Guidelines When performing an eFSU, note the following guidelines and restrictions: • 7600-SIP-400 is powered down during an eFSU and is powered up at the Commitversion Stage or at Abortversion (Optional). • An eFSU can install a full image upgrade or a patch upgrade.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS eFSU Stages for a VSS Upgrade The eFSU sequence consists of several stages, each explicitly initiated by entering a specific issu command in the CLI. At each stage, you can verify the system status or roll back the upgrade before moving to the next stage.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS previous software version. To stop the rollback timer, enter the issu acceptversion command. Prior to starting the eFSU process, you can disable the rollback timer or configure it to a value up to two hours (the default is 45 minutes). Operating with an upgraded VSS active chassis, this stage allows you to examine the functionality of the new software image.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Changing the eFSU Rollback Timer To view or change the eFSU rollback timer, perform the following task before beginning an upgrade: Command Purpose Step 1 Router# config terminal Enters configuration mode. Step 2 Router(config)# issu set rollback-timer {seconds | hh:mm:ss} (Optional) Sets the rollback timer to ensure that the upgrade process does not leave the VSS nonoperational.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Command Purpose Step 4 Router# issu runversion Forces a switchover, causing the VSS standby chassis to become VSS active and begin running the new software. The previously VSS active chassis becomes VSS standby and boots with the old image. Step 5 Router# issu acceptversion (Optional) Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Command Purpose Step 6 Router# issu commitversion Loads the new software image onto the standby chassis. Step 7 Router# show issu state [switch/slot][detail] Verifies the status of the upgrade process. If the upgrade was successful, both the active and standby chassis are running the new software version. If you intend to bring up the ICS supervisor engine with Cisco IOS Release 12.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Step 5 Command Purpose Router# issu runversion Forces a switchover, causing the standby engine chassis to become active and begin running the new software. The previously active chassis becomes standby and boots with the old image.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Step 4 Command Purpose Router# issu loadversion [active_switch/slot] active-image [standby_switch/slot] standby-image Starts the downgrade process by loading the new software image onto the standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the standby chassis to transition to SSO mode.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Performing an eFSU Downgrade from a Future Cisco IOS Release to Cisco IOS Release 12.2(33)SXI4 To perform an eFSU downgrade of a VSS from a future Cisco IOS Release to Cisco IOS Release 12.2(33)SXI4, perform this task: Command Purpose Step 1 Router# copy tftp disk_name Uses TFTP to copy the new software image to the ICSs and flash memory on the active and standby chassis (disk0: and slavedisk0:).
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Command Purpose Step 7 Router# issu commitversion Loads the new software image onto the standby chassis. Step 8 Router# show issu state [switch/slot][detail] Verifies the status of the downgrade process. If the downgrade was successful, both the active and standby chassis are running the new software version.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Step 8 Command Purpose Router# issu commitversion Loads the new software image onto the VSS standby chassis. Note This command will cause the VSS standby chassis to reload. Step 9 Router# show issu state [switch/slot][detail] Verifies the status of the upgrade process; status should display ‘Init’.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Boot Variable Operating Mode Primary Version Secondary Version Current Version = = = = = disk0:s72033-oldversion.v1,12; sso N/A N/A disk0:s72033-oldversion.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS RP State = Active ISSU State = Run Version Boot Variable = bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; Slot = RP State = ISSU State = Boot Variable = Router# issu commitversion %issu commitversion executed Router# show issu state Slot = RP State = ISSU State = Boot Variable = 1/6 Standby Run Version bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; successfully 2/6 Active Init bootdisk:/sys/s72033/base/s72033-advip
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Verify the New Image on the VSS Standby Chassis You can now enter the show issu state detail command and the show redundancy command to check that both chassis are in the ISSU Load Version state and SSO redundancy state. In this example, the VSS standby chassis is now running the “newversion” image.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Cat6k-Sup720/RP platform with 1048576 Kbytes of main memory Download Start !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (Deleted many lines) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Download Completed! Booting the image.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS keep_alive count = 1 keep_alive threshold = 18 RF debug mask = 0x0 Commit the New Image to the VSS Standby Chassis When the active chassis is successfully running the new image in the SSO redundancy state, you can enter either the issu acceptversion command to stop the rollback timer and hold this state indefinitely, or the issu commitversion command to continue with the eFSU.
Chapter 4 Configuring Virtual Switching Systems Upgrading a VSS Operating Mode Primary Version Secondary Version Current Version = = = = sso N/A N/A disk0:s72033-newversion.
