December 11, 1997
Products Affected
This field notice affects the following products:
-
RSP2
This field notice also affects the following HSA configurations:
-
RSP2 Master, RSP2 Slave (Cisco 7507 and Cisco 7513)
-
RSP4 Master, RSP2 Slave (Cisco 7507 and Cisco 7513)
Problem Description
In a Cisco 7507 or Cisco 7513 system, OIR (On-line Insertion and Removal) of any xIP or VIP on either CyBus may cause the slave RSP2 to reboot with a bus error or a processor memory parity error. The master RSP will recover from this event by issuing a "Cbus Complex Restart".
Note:?Cisco 7507 and Cisco 7513 systems that are configured with RSP4 slaves are not affected and will not experience this problem.
Problem Symptoms
Customers that attempt OIR of an xIP or VIP card with an RSP2 installed as a slave will see the following errors:
Sep 24 12:01:06.422: %OIR-6-INSCARD: Card inserted in slot 0, interfaces administratively shut down Sep 24 12:01:08.278: %RSP-3-SLAVECHANGE: Slave changed state from Slave to Non-participant Sep 24 12:01:09.782: %IPC_RSP_CBUS-3-NOHWQ: Hardware queue for card at slot 0 not found Sep 24 12:01:09.794: %DBUS-3-WCSCTRLRERR: Slot 6, WCS Controller Instruction Error Sep 24 12:01:10.822: %LINK-3-UPDOWN: Interface FastEthernet0/0/0, changed state to up Sep 24 12:01:11.258: %LINK-3-UPDOWN: Interface FastEthernet0/1/0, changed state to up Sep 24 12:01:12.662: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant to Slave Sep 24 12:01:14.782: %IPC_RSP_CBUS-3-NOHWQ: Hardware queue for card at slot 0 not found Sep 24 12:01:18.142: %RSP-3-SLAVECHANGE: Slave changed state from Slave to Non-participant Sep 24 12:01:19.782: %IPC_RSP_CBUS-3-NOHWQ: Hardware queue for card at slot 0 not found Sep 24 12:01:20.330: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant to Slave Sep 24 12:02:06.803: %RSP-3-RESTART: cbus complex Sep 24 12:02:06.803: %RSP-3-SLAVECHANGE: Slave changed state from Slave to Non-participant Sep 24 12:02:08.988: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant to Slave Sep 24 12:02:31.952: %RSP-3-SLAVECHANGE: Slave changed state from Slave to Non-participant Sep 24 12:02:34.136: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant to Slave Sep 24 12:02:57.549: %LINEPROTO-5-UPDOWN: Line protocol on Interface Fddi9/0/0, changed state to down description from unknown neighbor 60.0.0.5 Sep 24 12:02:58.549: %LINEPROTO-5-UPDOWN: Line protocol on Interface Fddi9/0/0, changed state to up 64MB, slave 80MB Sep 24 12:03:10.689: %RSP-5-SLAVEUP: Slave changed to state Running
SLAVE CONSOLE OUTPUT
Slave#
Error: primary data cache, fields: data, SysAD
virtual addr 0x5800FF84, physical addr(21:3) 0x00FF80, vAddr(14:12) 0x3000(GDB)
Queued messages:
*** System received a Cache Parity Exception ***
signal= 0x14, code= 0xa400ff83, context= 0x6015c830
PC = 0x60010a14, Cause = 0x420, Status Reg = 0x34008802
DCL Masked Interrupt Register = 0x000000ff
DCL Interrupt Value Register = 0x0000001c
MEMD Int 6 Status Register = 0x00000000
rommon 1 >
System Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1)
Copyright (c) 1994 by cisco Systems, Inc.
SLOT 6 RSP2 is system slave
SLOT 7 RSP2 is system master
RSP2 processor with 81920 Kbytes ?
System Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1)
Copyright (c) 1994 by cisco Systems, Inc.
SLOT 6 RSP2 is system slave
SLOT 7 RSP2 is system master
RSP2 processor with 81920 Kbytes of main memory
rommon 1 >
System Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1)
Copyright (c) 1994 by cisco Systems, Inc.
SLOT 6 RSP2 is system slave
SLOT 7 RSP2 is system master
RSP2 processor with 81920 Kbytes of main memory
rommon 1 >
System Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1)
Copyright (c) 1994 by cisco Systems, Inc.
SLOT 6 RSP2 is system slave
SLOT 7 RSP2 is system master
RSP2 processor with 81920 Kbytes of main memory
rommon 1 >
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-DW-M), Experimental Version 11.1(4315) [ganesh 108]
Synced to mainline version: 11.1(13)
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Wed 24-Sep-97 10:14 by
Image text-base: 0x60010900, data-base: 0x600E2000
cisco RSP2 (R4600) processor with 81920K bytes of memory.
R4600 processor, Implementation 32, Revision 2.0
Last reset from power-on
123K bytes of non-volatile configuration memory.
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Press RETURN to get started!
%LINK-4-NOMAC: A random default MAC address of 0000.0c81.3abe has
been chosen. Ensure that this address is unique, or specify MAC
addresses for commands (such as 'novell routing') that allow the
use of this address as a default.
%SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-DW-M), Experimental Version 11.1(4315) [ganesh 108]
Synced to mainline version: 11.1(13)
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Wed 24-Sep-97 10:14 by
View bug details for CSCdi92564 (registered customers only)
Workaround/Solution
To avoid the cBus "Complex Restarts", Cisco recommends that the following steps be followed when OIR of an xIP or VIP is required:
-
OIR (remove) Slave RSP2
-
Wait 15 seconds
-
OIR xIP or VIP
-
Wait 15 Seconds
-
OIR (insert) Slave RSP2
You can determine the processor model (RSP2 or RSP4) by using the global Cisco IOS command show controller cbus from the master console as follows:
Router# sh cont cbus
<text omitted>
slot3: RSP2, hw 1.2, sw 11.02, ccb 0, cmdq 48000098, vps 8192
software loaded from system
<text omitted>
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: