January 10, 2003
Products Affected
-
Cisco 10000 Series Edge Service Routers
-
Cisco 12000 Series Gigabit Service Routers
Problem Description
When upgrading from Cisco IOS® Software Releases 12.0(22)S or 12.0(22)S1 using Fast Software Upgrade (FSU), the standby Performance Routing Engine (PRE) or Gigabit Route Processor (GRP) continuously reloads after the hw-module reset command is entered.
Background
This issue exists if either Cisco IOS Software Release 12.0(22)S or 12.0(22)S1 is running in a system with redundant PREs or GRPs and an attempt is made to upgrade to 12.0(22)S2 or later using the fast software upgrade (FSU) method.
The basic procedure of a FSU is as follows and the corresponding commands are shown below in bold.
Lines 1 and 2: Copy new image to both PREs or GRPs. Lines 3 through 6: Configure PREs or GRPs to boot from the new image. Lines 7: Reset the secondary PRE or GRP so it will be running with new image. Line 8: Cutover to secondary PRE or GRP. copy tftp disk0: copy tftp stby-disk0: configure terminal boot system flash disk0:c10k-p10-mz.120-23.S end write hw-module sec-cpu reset redundancy force-failover main-cpu
Problem Symptoms
The standby PRE or GRP is continuously reset by the active PRE or GRP and alarm messages will appear in the log similar to the following:
Dec 5 12:09:45: %C10K_ALARM-6-INFO: CLEAR MAJOR RP A Secondary failure
Dec 5 12:10:15: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)
Dec 5 12:10:15: %C10K_ALARM-6-INFO: ASSERT MAJOR RP A Secondary failure
Dec 5 12:14:51: %REDUNDANCY-3-IPC: IOS versions do not match,
redundancy mode fallback
Dec 5 12:14:52: %C10K_ALARM-6-INFO: CLEAR MAJOR RP A Secondary failure
Dec 5 12:15:22: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)
Dec 5 12:15:22: %C10K_ALARM-6-INFO: ASSERT MAJOR RP A Secondary failure
Dec 5 12:19:58: %REDUNDANCY-3-IPC: IOS versions do not match,
redundancy mode fallback
Workaround/Solution
A workaround is only required when Cisco IOS Software release 12.0(22)S or 12.0(22)S1 is being upgraded to a later release. The workaround is to do the upgrade with a system reload as shown in the example below.
Note:?This method will be service disruptive.
copy tftp disk0: copy tftp stby-disk0: configure terminal boot system flash disk0:c10k-p10-mz.120-23.S end write reload
DDTS
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
|
DDTS |
Description |
|---|---|
|
Consolidate RF client ids and seq numbers |
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
