cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
428
Views
0
Helpful
3
Replies

ISSU error messages appear after updating and rebooting redundant Sup6L-E

Hi guys,

after updating two Sup6L-E to 12.2(53)SG2 (License is IP-Base) without issu and rebooting the complete 4507R-E chassis I got the following cli messages after the ios was loaded:

===

The following ISSU base level clients have not negotiated:
  Client_ID = 2002, Client_Name = CEF Push ISSU client
  Client_ID = 2023, Client_Name = FIB HWIDB ISSU client
  Client_ID = 2024, Client_Name = FIB IDB ISSU client
  Client_ID = 2025, Client_Name = FIB HW subblock ISSU client
  Client_ID = 2026, Client_Name = FIB SW subblock ISSU client
  Client_ID = 2027, Client_Name = Adjacency ISSU client
  Client_ID = 2028, Client_Name = FIB IPV4 ISSU client

===

ISSU state of both sups is in init state (as expected) and redundacy mode is sso (active/hot standby), ip routing is disabled (access switch).

The messages appear everytime after rebooting the switch.

Does anybody know what's the meaning of these issu messages?

Many thanks in advance

Thorsten

3 Replies 3

Ganesh Hariharan
VIP Alumni
VIP Alumni

Hi guys,

after updating two Sup6L-E to 12.2(53)SG2 (License is IP-Base) without issu and rebooting the complete 4507R-E chassis I got the following cli messages after the ios was loaded:

===

The following ISSU base level clients have not negotiated:
  Client_ID = 2002, Client_Name = CEF Push ISSU client
  Client_ID = 2023, Client_Name = FIB HWIDB ISSU client
  Client_ID = 2024, Client_Name = FIB IDB ISSU client
  Client_ID = 2025, Client_Name = FIB HW subblock ISSU client
  Client_ID = 2026, Client_Name = FIB SW subblock ISSU client
  Client_ID = 2027, Client_Name = Adjacency ISSU client
  Client_ID = 2028, Client_Name = FIB IPV4 ISSU client

===

ISSU state of both sups is in init state (as expected) and redundacy mode is sso (active/hot standby), ip routing is disabled (access switch).

Does anybody know what's the meaning of these issu messages?

Many thanks in advance

Thorsten

Thorsten,

Following is the description of the filed are as follows:-

Client_ID                              The identification number used by ISSU for that client.

Client_Name                         A character string describing the client."Base Clients" are a subset, which includes:

                                             •Inter-Process Communications (IPC)

                                             •Redundancy Framework (RF)

                                             •Checkpoint Facility (CF)

                                             •Cisco Express Forwarding

                                             •Network RF (for IDB stateful switchover)

                                             •EHSA Services (including ifIndex)

                                             •Configuration Synchronization.

Entity_Count                         The number of entities within this client. An entity is a logical group of sessions with some common attributes.

Hope to Help !!

Ganesh.H

Amit Singh
Cisco Employee
Cisco Employee

This is a known bug on SUP6L-E with ISSU. Please enable the IP routing as a work around and these messages will disappear.

Bug :

CSCta61751

Cheers,

-amit singh

Hi Amit,

the description of the bug you mentioned is

ISSU fails into RPR if ip routing disabled
Symptom:
After ISSU upgrade the device ends in RPR mode

Conditions:
when ip routing is disabled

Workaround:
enable ip routing

Are you sure that this is the same symptom?

I didn't use issu to upgrade the sups and further the sups are running in sso mode.

However I'll test enabling ip routing asap.

Regards,

Thorsten

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card