To examine any ISSU client, you must specify its unique client ID when entering the show issu sessions command. If you do not already know that client ID, enter the show issu clientscommand 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 in the following example:
Router# show issu clients
Client_ID = 2, Client_Name = ISSU Proto client, Entity_Count = 1
Client_ID = 3, Client_Name = ISSU RF, Entity_Count = 1
Client_ID = 4, Client_Name = ISSU CF client, Entity_Count = 1
Client_ID = 5, Client_Name = ISSU Network RF client, Entity_Count = 1
Client_ID = 7, Client_Name = ISSU CONFIG SYNC, Entity_Count = 1
Client_ID = 8, Client_Name = ISSU ifIndex sync, Entity_Count = 1
Client_ID = 9, Client_Name = ISSU IPC client, Entity_Count = 1
Client_ID = 10, Client_Name = ISSU IPC Server client, Entity_Count = 1
Client_ID = 11, Client_Name = ISSU Red Mode Client, Entity_Count = 1
Client_ID = 12, Client_Name = ISSU EHSA services client, Entity_Count = 1
Client_ID = 100, Client_Name = ISSU rfs client, Entity_Count = 1
Client_ID = 110, Client_Name = ISSU ifs client, Entity_Count = 1
Client_ID = 1001, Client_Name = OC3POS-6, Entity_Count = 4
Client_ID = 1002, Client_Name = C10K ATM, Entity_Count = 1
Client_ID = 1003, Client_Name = C10K CHSTM1, Entity_Count = 1
Client_ID = 1004, Client_Name = C10K CT3, Entity_Count = 1
Client_ID = 1005, Client_Name = C10K GE, Entity_Count = 1
Client_ID = 1006, Client_Name = C10K ET, Entity_Count = 1
Client_ID = 1007, Client_Name = C10K CHE1T1, Entity_Count = 1
Client_ID = 1009, Client_Name = C10K MFE, Entity_Count = 1
Client_ID = 1010, Client_Name = C10K APS, Entity_Count = 1
Client_ID = 1013, Client_Name = C10K CARD OIR, Entity_Count = 1
Client_ID = 2002, Client_Name = CEF Push ISSU client, Entity_Count = 1
Client_ID = 2003, Client_Name = ISSU XDR client, Entity_Count = 1
Client_ID = 2004, Client_Name = ISSU SNMP client, Entity_Count = 1
Client_ID = 2005, Client_Name = ISSU HDLC Client, Entity_Count = 1
Client_ID = 2006, Client_Name = ISSU QoS client, Entity_Count = 1
Client_ID = 2007, Client_Name = ISSU LSD Label Mgr HA Client, Entity_Count = 1
Client_ID = 2008, Client_Name = ISSU Tableid Client, Entity_Count = 1
Client_ID = 2009, Client_Name = ISSU MPLS VPN Client, Entity_Count = 1
Client_ID = 2010, Client_Name = ARP HA, Entity_Count = 1
Client_ID = 2011, Client_Name = ISSU LDP Client, Entity_Count = 1
Client_ID = 2012, Client_Name = ISSU HSRP Client, Entity_Count = 1
Client_ID = 2013, Client_Name = ISSU ATM Client, Entity_Count = 1
Client_ID = 2014, Client_Name = ISSU FR Client, Entity_Count = 1
Client_ID = 2015, Client_Name = ISSU REDSSOC client, Entity_Count = 1
Client_ID = 2019, Client_Name = ISSU TCP client, Entity_Count = 1
Client_ID = 2020, Client_Name = ISSU BGP client, Entity_Count = 1
Client_ID = 2021, Client_Name = XDR Int Priority ISSU client, Entity_Count = 1
Client_ID = 2022, Client_Name = XDR Proc Priority ISSU client, Entity_Count = 1
Client_ID = 2023, Client_Name = FIB HWIDB ISSU client, Entity_Count = 1
Client_ID = 2024, Client_Name = FIB IDB ISSU client, Entity_Count = 1
Client_ID = 2025, Client_Name = FIB HW subblock ISSU client, Entity_Count = 1
Client_ID = 2026, Client_Name = FIB SW subblock ISSU client, Entity_Count = 1
Client_ID = 2027, Client_Name = Adjacency ISSU client, Entity_Count = 1
Client_ID = 2028, Client_Name = FIB IPV4 ISSU client, Entity_Count = 1
Client_ID = 2030, Client_Name = MFI Pull ISSU client, Entity_Count = 1
Client_ID = 2031, Client_Name = MFI Push ISSU client, Entity_Count = 1
Client_ID = 2051, Client_Name = ISSU CCM Client, Entity_Count = 1
Client_ID = 2052, Client_Name = ISSU PPP SIP CCM Client, Entity_Count = 1
Client_ID = 2053, Client_Name = ISSU MPLS TE Client, Entity_Count = 1
Client_ID = 2054, Client_Name = ISSU process client, Entity_Count = 1
Client_ID = 2089, Client_Name = MPLS LSPV Push client, Entity_Count = 1
.
.
.
.
Base Clients:
Client_Name = ISSU Proto client
Client_Name = ISSU RF
Client_Name = ISSU CF client
Client_Name = ISSU Network RF client
Client_Name = ISSU CONFIG SYNC
Client_Name = ISSU ifIndex sync
Client_Name = ISSU IPC client
Client_Name = ISSU IPC Server client
Client_Name = ISSU Red Mode Client
Client_Name = ISSU EHSA services client
Client_Name = ISSU rfs client
Client_Name = ISSU ifs client
Client_Name = ISSU EM client
Client_Name = ISSU Platform Medialayer Client
Client_Name = ISSU FM Client
Client_Name = ISSU TCAM Manager Client
Client_Name = ISSU L2 Cmn Client
Client_Name = ISSU L3 Manager HA Client
Client_Name = ISSU L3 Manager Client
Client_Name = ISSU CFIB BASE Client
Client_Name = ISSU PF CONFIG SYNC Client
Client_Name = ISSU MLS CEF Client
Client_Name = ISSU Cat6k Logger Client
Verifying the ISSU Process for an MPLS LDP Client Example
This example shows how to verify the ISSU process for an 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 Session
UniqueID Sid Role Result GroupID GroupID Signature
4 34 PRIMARY COMPATIBLE 1 1 0
(no policy)
Negotiation Session Info for This Message Session:
Nego_Session_ID = 46
Nego_Session_Name = LDP Session
Transport_Mtu = 3948
Now 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 46
Session_ID = 46 :
Message_Type = 1, Negotiated_Version = 2, Message_MTU = 20
Message_Type = 2, Negotiated_Version = 2, Message_MTU = 20
Message_Type = 3, Negotiated_Version = 2, Message_MTU = 4
Next you can enter the same session ID into the following command to display the capability negotiation result:
Router# show issu negotiated capability 46
Session_ID = 46 :
Negotiated_Cap_Entry = 1
Finally, 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 ~ 2
Message_Ver = 2, Message_Mtu = 20
Message_Type = 2, Version_Range = 2 ~ 2
Message_Ver = 2, Message_Mtu = 20
Message_Type = 3, Version_Range = 2 ~ 2
Message_Ver = 2, Message_Mtu = 4
Verifying the ISSU Process for an MPLS VRF ("Table ID") Client Example
This example shows how to verify the ISSU process for an MPLS VRF ("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 Session
UniqueID Sid Role Result GroupID GroupID Signature
4 13 PRIMARY COMPATIBLE 1 1 0
(no policy)
Negotiation Session Info for This Message Session:
Nego_Session_ID = 19
Nego_Session_Name = TABLEID ISSU CF
Transport_Mtu = 3948
Now 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 19
Session_ID = 19 :
Message_Type = 1, Negotiated_Version = 1, Message_MTU = 44
Message_Type = 2, Negotiated_Version = 1, Message_MTU = 4
Next you can enter the same session ID into the following command to display the capability negotiation result:
Router# show issu negotiated capability 19
Session_ID = 19 :
Negotiated_Cap_Entry = 1
Finally, 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 ~ 1
Message_Ver = 1, Message_Mtu = 44
Message_Type = 2, Version_Range = 1 ~ 1
Message_Ver = 1, Message_Mtu = 4
Verifying the ISSU Process for an MPLS LSPV Push Client Example
This example shows how to verify the ISSU process for an MPLS LSVP 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 Session
UniqueID Sid Role Result GroupID GroupID Signature
7 36 PRIMARY COMPATIBLE 1 1 0
(no policy)
Negotiation Session Info for This Message Session:
Nego_Session_ID = 45
Nego_Session_Name = MPLS LSPV Push ( 6)
Transport_Mtu = 1438
Now 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 45
Session_ID = 45:
Message_Type = 0, Negotiated_Version = 1, Message_MTU = 74
Message_Type = 1, Negotiated_Version = 1, Message_MTU = 120
Message_Type = 2, Negotiated_Version = 1, Message_MTU = 120
Message_Type = 3, Negotiated_Version = 1, Message_MTU = 5122
Message_Type = 4, Negotiated_Version = 1, Message_MTU = 6
Next you can enter the same session ID into the following command to display the capability negotiation result:
Router# show issu negotiated capability 45
Session_ID = 45:
Cap_Type = 0 Cap_Result = 1 No cap value assigned
Finally 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 ~ 1
Message_Ver = 1, Message_Mtu = 74
Message_Type = 1, Version_Range = 1 ~ 1
Message_Ver = 1, Message_Mtu = 120
Message_Type = 2, Version_Range = 1 ~ 1
Message_Ver = 1, Message_Mtu = 120
Message_Type = 3, Version_Range = 1 ~ 1
Message_Ver = 1, Message_Mtu = 5122
Message_Type = 4, Version_Range = 1 ~ 1
Message_Ver = 1, Message_Mtu = 6