Downloads |
Table Of Contents
ISSU-Capable Protocols and Applications: "Clients"
Loading New Cisco IOS Software onto the Standby Route Processor
Discovering Impending Line Card Outage Times
Examples of Examining ISSU Coordination of MPLS Clients
ISSU MPLS Clients
The In Service Software Upgrade (ISSU) process allows Cisco IOS Software at the router level to be updated or otherwise modified while packet forwarding continues. At the linecard level, an enhanced Fast Software Upgrade (eFSU) process minimizes linecard downtime during such upgrades to between 30 and 90 seconds, by pre-loading the new linecard image before the ISSU switchover occurs from the active to the standby Route Processor.
This document provides information about upgrading MPLS-related applications through ISSU and eFSU. Those MPLS applications are considered ISSU's MPLS "clients".
For information on the entire ISSU and eFSU procedure, please see the document, Cisco IOS In Service Software Upgrade and Enhanced Fast Software Upgrade Process.
For information specific to eFSU on the Cisco 7600 series router, please refer to the chapter, "ISSU and eFSU on Cisco 7600 Series Routers," within the book, Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SR, (Part No. OL-10113-03).
Feature History for ISSU and eFSU
12.2(28)SB
The ISSU feature was introduced.
12.2(33)SRB-1
The LSPV Push and TE clients and the eFSU functionality were added.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
ISSU-Capable Protocols and Applications: "Clients"
•
•
ISSU-Capable Protocols and Applications: "Clients"
Protocols and applications which can be upgraded through the ISSU process are considered clients of ISSU. These include at least the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
and
•
MPLS
Within the MPLS technology, ISSU currently supports the following eight feature-sets as clients:
•
•
•
•
•
•
Beginning with Cisco IOS Release 12.2(33)SRB1, the following MPLS features are also supported as ISSU clients:
•
•
Prerequisites
Before you perform an upgrade, you need to verify that the clients you are concerned about are compatible with the intended switchover. The commands you will need to enter, in order to determine that, are given in the "Examining MPLS Clients" section.
Because the success of some clients performing on the upgraded network will depend upon the compatibility of other clients in the two images, it is recommended that you check the following table before assuming that any particular MPLS client will survive the upgrade.
Table 1 MPLS client interdependencies
Restrictions
Because linecards in the Cisco Series 7600 routers do not support Minimum Disruption Restart (MDR), they reset when eFSU is performed. That causes IGP adjacencies to flap, bringing down the MPLS Traffic Engineering tunnels. Therefore, after an eFSU operation, it may take as long as two minutes for TE tunnels to be re-signalled and re-established.
For this reason, we recommend that before you begin eFSU you first disable RSVP GR full mode. If you don't, RSVP can inadvertently delay the re-establishment of TE tunnels while it waits for the recovery of the pre-existing TE tunnel state.
To see how long each line card will be placed out-of-service during the eFSU process, use the show issu outage slot all command as described in the "Discovering Impending Line Card Outage Times" section.
Loading New Cisco IOS Software onto the Standby Route Processor
This task describes how to use ISSU to load new Cisco IOS software onto the standby Route Processor (RP).
Note
Prerequisites for this Task
1.
2.
Optionally, you may perform additional tests and commands to determine the current state of peers and interfaces for later comparison.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
issu loadversion active-slot active-image standby-slot standby-image [force]
Example:Router# issu loadversion a disk0:c10k2-p11-mz.2.20040830 b stby-disk0:c10k2-p11-mz.2.20040830Starts the ISSU process.
It may take several seconds after entering this command for Cisco IOS software to load onto the standby RP and for the standby RP to transition into SSO mode. Therefore, don't rush to begin Step 3 too soon.
Step 3
show issu state [detail]
Example:Router# show issu state
Displays the state of the during the ISSU process. Use this command now to check that the standby RP is loaded and is in SSO mode.
Step 4
show issu clients
Example:Router# show issu clients
Client_ID=2010, Client_Name=ARP HA, Entity_Count=1
Client_ID=2011, Client_Name=ISSU LDP Client, Entity_Count=1
Shows which clients are active and gives you their client IDs.
Step 5
show issu sessions client_ID
Example:Router# show issu sessions 2011
Client_ID=2011, Entity_ID=11 :*** Session_ID=33, Session_Name=MFI Push (3) :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature4 19 PRIMARY COMPATIBLE 1 11 0(no policy)Tells whether the specified client can be compatibly handled by the impending upgrade. (More details on this command and its output are given in the following section of this document, Examining MPLS Clients).
Discovering Impending Line Card Outage Times
After the issu loadversion command has run, you can enter the command show issu outage in SP console mode, to learn the maximum length of time each line card could be down when your use of the command issu runversion will trigger eFSU.
For example in the following display, the column "Max Outage Time" shows the longest down time that should be expected for each of the four listed line card types:
Router# show issu outage slot allSlot # Card Type MDR Mode Max Outage Time------ ------------------------------------- ----------- ---------------1 CEF720 24 port 1000mb SFP WARM_RELOAD 300 secs2 1-subslot SPA Interface Processor-600 WARM_RELOAD 300 secs3 4-subslot SPA Interface Processor-400 WARM_RELOAD 300 secs4 2+4 port GE-WAN RELOAD 360 secsMore details about the show issu outage command and its usage are given on page 26.
Note
Examining MPLS Clients
Use the following command sequence to discover whether a particular client can be upgraded successfully during a particular ISSU session. These commands also display other details about the ISSU MPLS clients.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples of Examining ISSU Coordination of MPLS Clients
This section presents the following examples:
To examine any ISSU client, you must enter its unique Client_ID into the CLI. If you don't already know that Client_ID, enter the command show issu clients in user EXEC or privileged EXEC mode. Each ISSU client on the network will then be listed, with its Client_ID and Client Name on the same line, as shown here below. (The eight MPLS clients have been highlighted in red for your convenience).
Router# show issu clientsClient_ID = 2, Client_Name = ISSU Proto client, Entity_Count = 1Client_ID = 3, Client_Name = ISSU RF, Entity_Count = 1Client_ID = 4, Client_Name = ISSU CF client, Entity_Count = 1Client_ID = 5, Client_Name = ISSU Network RF client, Entity_Count = 1Client_ID = 7, Client_Name = ISSU CONFIG SYNC, Entity_Count = 1Client_ID = 8, Client_Name = ISSU ifIndex sync, Entity_Count = 1Client_ID = 9, Client_Name = ISSU IPC client, Entity_Count = 1Client_ID = 10, Client_Name = ISSU IPC Server client, Entity_Count = 1Client_ID = 11, Client_Name = ISSU Red Mode Client, Entity_Count = 1Client_ID = 12, Client_Name = ISSU EHSA services client, Entity_Count = 1Client_ID = 100, Client_Name = ISSU rfs client, Entity_Count = 1Client_ID = 110, Client_Name = ISSU ifs client, Entity_Count = 1Client_ID = 1001, Client_Name = OC3POS-6, Entity_Count = 4Client_ID = 1002, Client_Name = C10K ATM, Entity_Count = 1Client_ID = 1003, Client_Name = C10K CHSTM1, Entity_Count = 1Client_ID = 1004, Client_Name = C10K CT3, Entity_Count = 1Client_ID = 1005, Client_Name = C10K GE, Entity_Count = 1Client_ID = 1006, Client_Name = C10K ET, Entity_Count = 1Client_ID = 1007, Client_Name = C10K CHE1T1, Entity_Count = 1Client_ID = 1009, Client_Name = C10K MFE, Entity_Count = 1Client_ID = 1010, Client_Name = C10K APS, Entity_Count = 1Client_ID = 1013, Client_Name = C10K CARD OIR, Entity_Count = 1Client_ID = 2002, Client_Name = CEF Push ISSU client, Entity_Count = 1Client_ID = 2003, Client_Name = ISSU XDR client, Entity_Count = 1Client_ID = 2004, Client_Name = ISSU SNMP client, Entity_Count = 1Client_ID = 2005, Client_Name = ISSU HDLC Client, Entity_Count = 1Client_ID = 2006, Client_Name = ISSU QoS client, Entity_Count = 1Client_ID = 2007, Client_Name = ISSU LSD Label Mgr HA Client, Entity_Count = 1Client_ID = 2008, Client_Name = ISSU Tableid Client, Entity_Count = 1Client_ID = 2009, Client_Name = ISSU MPLS VPN Client, Entity_Count = 1Client_ID = 2010, Client_Name = ARP HA, Entity_Count = 1Client_ID = 2011, Client_Name = ISSU LDP Client, Entity_Count = 1Client_ID = 2012, Client_Name = ISSU HSRP Client, Entity_Count = 1Client_ID = 2013, Client_Name = ISSU ATM Client, Entity_Count = 1Client_ID = 2014, Client_Name = ISSU FR Client, Entity_Count = 1Client_ID = 2015, Client_Name = ISSU REDSSOC client, Entity_Count = 1Client_ID = 2019, Client_Name = ISSU TCP client, Entity_Count = 1Client_ID = 2020, Client_Name = ISSU BGP client, Entity_Count = 1Client_ID = 2021, Client_Name = XDR Int Priority ISSU client, Entity_Count = 1Client_ID = 2022, Client_Name = XDR Proc Priority ISSU client, Entity_Count = 1Client_ID = 2023, Client_Name = FIB HWIDB ISSU client, Entity_Count = 1Client_ID = 2024, Client_Name = FIB IDB ISSU client, Entity_Count = 1Client_ID = 2025, Client_Name = FIB HW subblock ISSU client, Entity_Count = 1Client_ID = 2026, Client_Name = FIB SW subblock ISSU client, Entity_Count = 1Client_ID = 2027, Client_Name = Adjacency ISSU client, Entity_Count = 1Client_ID = 2028, Client_Name = FIB IPV4 ISSU client, Entity_Count = 1Client_ID = 2030, Client_Name = MFI Pull ISSU client, Entity_Count = 1Client_ID = 2031, Client_Name = MFI Push ISSU client, Entity_Count = 1Client_ID = 2051, Client_Name = ISSU CCM Client, Entity_Count = 1Client_ID = 2052, Client_Name = ISSU PPP SIP CCM Client, Entity_Count = 1Client_ID = 2053, Client_Name = ISSU MPLS TE Client, Entity_Count = 1Client_ID = 2054, Client_Name = ISSU process client, Entity_Count = 1Client_ID = 2089, Client_Name = MPLS LSPV Push client, Entity_Count = 1. . .Base Clients:Client_Name = ISSU Proto clientClient_Name = ISSU RFClient_Name = ISSU CF clientClient_Name = ISSU Network RF clientClient_Name = ISSU CONFIG SYNCClient_Name = ISSU ifIndex syncClient_Name = ISSU IPC clientClient_Name = ISSU IPC Server clientClient_Name = ISSU Red Mode ClientClient_Name = ISSU EHSA services clientClient_Name = ISSU rfs clientClient_Name = ISSU ifs clientClient_Name = ISSU EM clientClient_Name = ISSU Platform Medialayer ClientClient_Name = ISSU FM ClientClient_Name = ISSU TCAM Manager ClientClient_Name = ISSU L2 Cmn ClientClient_Name = ISSU L3 Manager HA ClientClient_Name = ISSU L3 Manager ClientClient_Name = ISSU CFIB BASE ClientClient_Name = ISSU PF CONFIG SYNC ClientClient_Name = ISSU MLS CEF ClientClient_Name = ISSU Cat6k Logger ClientEach example section below now shows you the sequence of commands that can display for you useful information about its respective MPLS client.
LDP Client
The first command shows you whether the LDP client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2011---------------------------------------------------------------------Client_ID = 2011, Entity_ID = 1 :*** Session_ID = 46, Session_Name = LDP Session :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature4 34 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 46Nego_Session_Name = LDP SessionTransport_Mtu = 3948Now you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 46Session_ID = 46 :Message_Type = 1, Negotiated_Version = 2, Message_MTU = 20Message_Type = 2, Negotiated_Version = 2, Message_MTU = 20Message_Type = 3, Negotiated_Version = 2, Message_MTU = 4Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 46Session_ID = 46 :Negotiated_Cap_Entry = 1Finally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2011---------------------------------------------------------------------Client_ID = 2011, Entity_ID = 1 :Message_Type = 1, Version_Range = 2 ~ 2Message_Ver = 2, Message_Mtu = 20Message_Type = 2, Version_Range = 2 ~ 2Message_Ver = 2, Message_Mtu = 20Message_Type = 3, Version_Range = 2 ~ 2Message_Ver = 2, Message_Mtu = 4MPLS VPN Client
The first command shows you whether the VPN client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2009---------------------------------------------------------------------Client_ID = 2009, Entity_ID = 1 :*** Session_ID = 39, Session_Name = MPLS VPN ISSU Session :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature3 33 PASSIVE COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 39Nego_Session_Name = MPLS VPN ISSU SessionTransport_Mtu = 3980Now you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 39Session_ID = 39 :Message_Type = 1, Negotiated_Version = 1, Message_MTU = 32Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 39Session_ID = 39 :Negotiated_Cap_Entry = 1Finally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2009---------------------------------------------------------------------Client_ID = 2009, Entity_ID = 1 :Message_Type = 1, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 32VRF ("Table ID") Client
The first command shows you whether the VRF client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2008---------------------------------------------------------------------Client_ID = 2008, Entity_ID = 1 :*** Session_ID = 19, Session_Name = TABLEID ISSU CF :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature4 13 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 19Nego_Session_Name = TABLEID ISSU CFTransport_Mtu = 3948Now you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 19Session_ID = 19 :Message_Type = 1, Negotiated_Version = 1, Message_MTU = 44Message_Type = 2, Negotiated_Version = 1, Message_MTU = 4Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 19Session_ID = 19 :Negotiated_Cap_Entry = 1Finally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2008---------------------------------------------------------------------Client_ID = 2008, Entity_ID = 1 :Message_Type = 1, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 44Message_Type = 2, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 4LSD Label Manager HA Client
The first command shows you whether the LSD client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2007---------------------------------------------------------------------Client_ID = 2007, Entity_ID = 1 :*** Session_ID = 40, Session_Name = lsd_ha :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature4 30 PRIMARY COMPATIBLE 1 1 0(policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 40Nego_Session_Name = lsd_haTransport_Mtu = 3948Compat_Result: raw_result = COMPATIBLE, policy_result = COMPATIBLENow you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 40Session_ID = 40 :Message_Type = 1, Negotiated_Version = 2, Message_MTU = 8Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 40---------------------------------------------------Client_ID = 2007, Entity_ID = 1, Session_ID = 40 :Negotiated_Cap_Entry = 1Finally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2007---------------------------------------------------------------------Client_ID = 2007, Entity_ID = 1 :Message_Type = 1, Version_Range = 1 ~ 2Message_Ver = 1, Message_Mtu = 12Message_Ver = 2, Message_Mtu = 8MFI Pull Client
The first command shows you whether the MFI Pull client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2030---------------------------------------------------------------------Client_ID = 2030, Entity_ID = 1 :*** Session_ID = 131073, Session_Name = MFI Pull (6):Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature7 35 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 131073Nego_Session_Name = MFI Pull (6)Transport_Mtu = 4056Now you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 131073Session_ID = 131073:Message_Type = 1006, Negotiated_Version = 1, Message_MTU = 4Message_Type = 3003, Negotiated_Version = 1, Message_MTU = 12Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 131073Session_ID = 131073 :Negotiated_Cap_Entry = 1Finally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2030---------------------------------------------------------------------Client_ID = 2030, Entity_ID = 1 :Message_Type = 1006, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 4Message_Type = 2004, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 12MFI Push Client
The first command shows you whether the MFI Push client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2031---------------------------------------------------------------------Client_ID = 2031, Entity_ID = 1 :*** Session_ID = 196646, Session_Name = MFI Push (6):Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature7 36 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 196646Nego_Session_Name = MFI Push (6)Transport_Mtu = 4056Now you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 196646Session_ID = 196646:Message_Type = 101, Negotiated_Version = 1, Message_MTU = 17Message_Type = 105, Negotiated_Version = 1, Message_MTU = 31Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 196646Session_ID = 196646 :Negotiated_Cap_Entry = 1Finally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2031---------------------------------------------------------------------Client_ID = 2031, Entity_ID = 1 :Message_Type = 5002, Version_Range = 1 ~ 2Message_Ver = 1, Message_Mtu = 10Message_Type = 5018, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 39LSPV Push Client
The first command shows you whether the LSPV Push client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2089---------------------------------------------------------------------Client_ID = 2089, Entity_ID = 1 :*** Session_ID = 45, Session_Name = MPLS LSPV Push (6 ):Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature7 36 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 45Nego_Session_Name = MPLS LSPV Push ( 6)Transport_Mtu = 1438Now you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 45Session_ID = 45:Message_Type = 0, Negotiated_Version = 1, Message_MTU = 74Message_Type = 1, Negotiated_Version = 1, Message_MTU = 120Message_Type = 2, Negotiated_Version = 1, Message_MTU = 120Message_Type = 3, Negotiated_Version = 1, Message_MTU = 5122Message_Type = 4, Negotiated_Version = 1, Message_MTU = 6Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 45Session_ID = 45:Cap_Type = 0 Cap_Result = 1 No cap value assignedFinally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2089---------------------------------------------------------------------Client_ID = 2089, Entity_ID = 1 :Message_Type = 0, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 74Message_Type = 1, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 120Message_Type = 2, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 120Message_Type = 3, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 5122Message_Type = 4, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 6TE Client
The first command shows you whether the TE client's old and new software versions are compatible, and therefore are able to make use of the ISSU opportunity:
Router# show issu sessions 2053---------------------------------------------------------------------Client_ID = 2053, Entity_ID = 1 :*** Session_ID = 84, Session_Name = RSVP HA Session :Peer Peer Negotiate Negotiated Cap Msg SessionUniqueID Sid Role Result GroupID GroupID Signature22 94 PRIMARY COMPATIBLE 1 1 0(no policy)Negotiation Session Info for This Message Session:Nego_Session_ID = 84Nego_Session_Name = RSVP HA SessionTransport_Mtu = 1392Now you can take the Session_ID displayed in the previous command's output and enter it into the next command, in order to see the negotiated message version:
Router# show issu negotiated version 84Session_ID = 84 :Message_Type = 1, Negotiated_Version = 2, Message_MTU = 1024Next you can enter the same session_ID into the following command, to display the capability negotiation result:
Router# show issu negotiated capability 84Session_ID = 84 :Cap_Type = 0, Cap_Result = 1 No cap value assignedFinally, to see which message types and versions are supported by this particular client, you enter the Client_ID into the following command:
Router# show issu message types 2053---------------------------------------------------------------------Client_ID = 2053, Entity_ID = 1 :Message_Type = 1, Version_Range = 1 ~ 2Message_Ver = 1, Message_Mtu = 1024Message_Ver = 2, Message_Mtu = 1024Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS High Availability Command Reference, Release 12.2SR.
show issu clients
To display a list of the current In Service Software Upgrade (ISSU) clients—that is, the network applications and protocols supported by ISSU—use the show issu clients command in user EXEC or privileged EXEC mode.
show issu clients
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
12.2(28)SB
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
This command lists all ISSU clients currently operating in the network, along with their Client ID numbers and the number of entities each client contains.
You should enter this command before you enter the issu runversion command, because if a client (application or protocol) that needs to continue operating in the network does not appear in the displayed list, you will know not to continue the software upgrade (because proceeding further with ISSU would then halt the operation of that application or protocol).
Examples
The following example shows a client list displayed by entering this command:
Router# show issu clientsClient_ID = 2, Client_Name = ISSU Proto client, Entity_Count = 1Client_ID = 3, Client_Name = ISSU RF, Entity_Count = 1Client_ID = 4, Client_Name = ISSU CF client, Entity_Count = 1Client_ID = 5, Client_Name = ISSU Network RF client, Entity_Count = 1Client_ID = 7, Client_Name = ISSU CONFIG SYNC, Entity_Count = 1Client_ID = 8, Client_Name = ISSU ifIndex sync, Entity_Count = 1Client_ID = 9, Client_Name = ISSU IPC client, Entity_Count = 1Client_ID = 10, Client_Name = ISSU IPC Server client, Entity_Count = 1Client_ID = 11, Client_Name = ISSU Red Mode Client, Entity_Count = 1Client_ID = 12, Client_Name = ISSU EHSA services client, Entity_Count = 1Client_ID = 100, Client_Name = ISSU rfs client, Entity_Count = 1Client_ID = 110, Client_Name = ISSU ifs client, Entity_Count = 1Client_ID = 1001, Client_Name = OC3POS-6, Entity_Count = 4Client_ID = 1002, Client_Name = C10K ATM, Entity_Count = 1Client_ID = 1003, Client_Name = C10K CHSTM1, Entity_Count = 1Client_ID = 1004, Client_Name = C10K CT3, Entity_Count = 1Client_ID = 1005, Client_Name = C10K GE, Entity_Count = 1Client_ID = 1006, Client_Name = C10K ET, Entity_Count = 1Client_ID = 1007, Client_Name = C10K CHE1T1, Entity_Count = 1Client_ID = 1009, Client_Name = C10K MFE, Entity_Count = 1Client_ID = 1010, Client_Name = C10K APS, Entity_Count = 1Client_ID = 1013, Client_Name = C10K CARD OIR, Entity_Count = 1Client_ID = 2002, Client_Name = CEF Push ISSU client, Entity_Count = 1Client_ID = 2003, Client_Name = ISSU XDR client, Entity_Count = 1Client_ID = 2004, Client_Name = ISSU SNMP client, Entity_Count = 1Client_ID = 2005, Client_Name = ISSU HDLC Client, Entity_Count = 1Client_ID = 2006, Client_Name = ISSU QoS client, Entity_Count = 1Client_ID = 2007, Client_Name = ISSU LSD Label Mgr HA Client, Entity_Count = 1Client_ID = 2008, Client_Name = ISSU Tableid Client, Entity_Count = 1Client_ID = 2009, Client_Name = ISSU MPLS VPN Client, Entity_Count = 1Client_ID = 2010, Client_Name = ARP HA, Entity_Count = 1Client_ID = 2011, Client_Name = ISSU LDP Client, Entity_Count = 1Client_ID = 2012, Client_Name = ISSU HSRP Client, Entity_Count = 1Client_ID = 2013, Client_Name = ISSU ATM Client, Entity_Count = 1Client_ID = 2014, Client_Name = ISSU FR Client, Entity_Count = 1Client_ID = 2015, Client_Name = ISSU REDSSOC client, Entity_Count = 1Client_ID = 2019, Client_Name = ISSU TCP client, Entity_Count = 1Client_ID = 2020, Client_Name = ISSU BGP client, Entity_Count = 1Client_ID = 2021, Client_Name = XDR Int Priority ISSU client, Entity_Count = 1Client_ID = 2022, Client_Name = XDR Proc Priority ISSU client, Entity_Count = 1Client_ID = 2023, Client_Name = FIB HWIDB ISSU client, Entity_Count = 1Client_ID = 2024, Client_Name = FIB IDB ISSU client, Entity_Count = 1Client_ID = 2025, Client_Name = FIB HW subblock ISSU client, Entity_Count = 1Client_ID = 2026, Client_Name = FIB SW subblock ISSU client, Entity_Count = 1Client_ID = 2027, Client_Name = Adjacency ISSU client, Entity_Count = 1Client_ID = 2028, Client_Name = FIB IPV4 ISSU client, Entity_Count = 1Client_ID = 2030, Client_Name = MFI Pull ISSU client, Entity_Count = 1Client_ID = 2031, Client_Name = MFI Push ISSU client, Entity_Count = 1Client_ID = 2051, Client_Name = ISSU CCM Client, Entity_Count = 1Client_ID = 2052, Client_Name = ISSU PPP SIP CCM Client, Entity_Count = 1Client_ID = 2054, Client_Name = ISSU process client, Entity_Count = 1Base Clients:Client_Name = ISSU Proto clientClient_Name = ISSU RFClient_Name = ISSU CF clientClient_Name = ISSU Network RF clientClient_Name = ISSU CONFIG SYNCClient_Name = ISSU ifIndex syncClient_Name = ISSU IPC clientClient_Name = ISSU IPC Server clientClient_Name = ISSU Red Mode ClientClient_Name = ISSU EHSA services clientTable 2 describes the significant fields shown in the display.
Related Commands
show issu entities
To display information about entities within one or more In Service Software Upgrade (ISSU) clients, use the show issu entities command in user EXEC or privileged EXEC mode.
show issu entities [client_id]
Note
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
12.2(28)SB
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
Enter a Client_ID if you are interested in seeing information only about one client's entities. If a Client_ID is not specified, the command will display all ISSU clients' entities known to the device.
If you are not sure of the precise Client_ID number to enter for the client you are interested in, use the show issu clients command to display the current list of clients with their names and ID numbers.
Examples
The following example shows detailed information about the entities within the virtual routing and forwarding (VRF) ("Table ID") client:
Router# show issu entities 2008Client_ID = 2008 :Entity_ID = 1, Entity_Name = Tableid Entity :MsgType MsgGroup CapType CapEntry CapGroupCount Count Count count Count2 2 1 2 2
Related Commands
show issu message types
To display formats ("types"), versions, and maximum packet size of the In Service Software Upgrade (ISSU) messages supported by a particular client, use the show issu message types command in user EXEC or privileged EXEC mode.
show issu message types client-id
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
12.2(28)SB
This command was introduced.
12.2(33)SRB1
ISSU is supported on the Cisco 7600 series routers in Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
If you are not sure of the Client_ID number to enter into this command, use the show issu clients command. It displays the current list of clients, along with their names and ID numbers.
Examples
The following example displays the message type, version, and maximum message size supported by the Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) client:
Router# show issu message types 2009Client_ID = 2009, Entity_ID = 1 :Message_Type = 1, Version_Range = 1 ~ 1Message_Ver = 1, Message_Mtu = 32Table 4 describes the significant fields shown in the display.
