October 05, 2004
Products Affected
|
Product |
Comments |
|---|---|
|
8800 - PXM45 |
Loaded with 2.1 software. |
|
8800 - PXM45/B |
Loaded with 2.1 software. |
|
MGX - PXM45 |
Loaded with 2.1 software. |
|
MGX - PXM45/B |
Loaded with 2.1 software. |
|
8800 - PXM45 |
Loaded with 2.1 software. |
|
8800 - PXM45/B |
Loaded with 2.1 software. |
Problem Description
The Standby PXM45 or PXM45/B fails to boot up in the MGX.
Background
If a Standby PXM45 or PXM45/B with 2.1 or earlier boot code is installed in an MGX8800 operating with 4.0 MGX software, the Standby PXM45 or PXM45/B may fail to boot up. The boot failure is due to the inability of the Standby PXM45 or PXM45/B with 2.1 boot code to communicate with the PXM45 or PXM45/B operating with MGX 4.0 software.
Problem Symptoms
The Standby PXM45 or PXM45/B will display as follows:
test_lab.7.PXM.a > DSPREVS test_lab System Rev: 04.00 Apr. 19, 2004 11:09:59 CST MGX8850 Node Alarm: CRITICAL Phy. Log. Inserted Cur Sw Boot FW Slot Slot Card Revision Revision ---- ---- -------- -------- -------- 01 01 AXSME_2OC12 4.0(15.202) 4.0(15.202) 02 02 AXSME_8OC3 4.0(15.202) 4.0(15.202) 03 03 --- --- --- 04 04 AXSME_8OC3 4.0(15.202) 4.0(15.202) 05 05 AXSME_2OC12 4.0(15.202) 4.0(15.202) 06 06 --- --- --- 07 07 PXM45B 4.0(15.202) 4.0(15.202) 08 07 PXM45B 4.0(15.202) 2.1(80.0) 09 09 --- --- --- 10 10 --- --- --- 11 11 AXSM_16OC3_B 4.0(15.203) 4.0(15.202) 12 12 --- --- --- 13 13 --- --- --- 14 14 --- --- --- 15 15 --- --- --- 16 15 --- --- ---
Workaround/Solution
WorkAround:
Follow this procedure to recover from failure and reach Standby State due to boot code issue.
On standby pxm45 shellConn
-
Console in to the standby card
-
cd FW
-
ll and note down the PXM45 boot file name
This file name will be used in step 8. The filename is in bold text below.
XXXXXXD1.8.PXM.is > cd FW XXXXXXD1.8.PXM.is > ll Listing Directory .: drwxrwxrwx 1 0 0 13312 Oct 11 15:27 ./ drwxrwxrwx 1 0 0 13312 Oct 31 20:52 ../ -rwxrwxAwx 1 0 0 3039536 Feb 13 11:18 axsm_003.000.020.000.fw -rwxrwxAwx 1 0 0 725112 Feb 13 11:19 axsm_003.000.020.000_bt.fw -rwxrwxAwx 1 0 0 2765136 Feb 13 11:19 axsme_003.000.020.000.fw -rwxrwxAwx 1 0 0 722136 Feb 13 11:20 axsme_003.000.020.000_bt.fw -rwxrwxAwx 1 0 0 1038376 Feb 13 11:20 pxm45_003.000.020.000_bt.fw -rwxrwxAwx 1 0 0 6328340 Feb 13 11:21 pxm45_003.000.020.100_mgx.fw -rwxrwxrwx 1 0 0 2769888 May 19 14:33 axsme_003.000.020.100.fw -rwxrwxrwx 1 0 0 7004612 Oct 1 14:58 pxm45_004.000.011.201_mgx.fw -rwxrwxrwx 1 0 0 1144136 Oct 1 14:56 pxm45_004.000.012.200_bt.fw -rwxrwxrwx 1 0 0 9976016 Jul 17 17:55 rpm-ios-pr-image -rwxrwxrwx 1 0 0 9976016 Jul 17 17:52 rpm-js-mz.122-15.T4a -rwxrwxrwx 1 0 0 3202728 Jul 17 17:50 rpm-boot-mz.122-15.T4a -rwxrwxrwx 1 0 0 44504 Jun 11 03:16 sar_check_task.o -rwxrwxAwx 1 0 0 634352 Jun 27 2002 axsm_002.001.080.000_bt.fw -rwxrwxAwx 1 0 0 2760744 Jun 27 2002 axsm_002.001.080.000.fw XXXXXXD1.8.PXM.is >
The card should be in standby mode. In shellconn execute the command sysBackupBoot
1.8.PXM.s > shellConn pxm45>sysBackupBoot sysBackupBoot rst type & STATUS: aaee000a 3400ff04 C0_EPC & CAUSE : 00e8f778 00008000 C0_CNFG & ErrPC : 5061e4bb 00216504 RA_reg & SPR_reg: bfc00524 02eb4cb8 reset reason : 000000c1 Testing 1FF FFF0... Testing 200 0000... Testing 400 0000... Testing 800 0000... Testing FFF FFF0... Bank 0 is 256 Bank 1 is zero -
If you encountered a TLB exception in the boot, hit ESC ESC (ESCape key twice) to go to Manufacturing boot. If it is a Tlb Store Exception, then this message comes after the first MGX 8850 banner. See capture below:
M M GGGGGGG XXX XXX 88888 88888 5555555 00000 MM MM GG GG XX XX 88 88 88 88 55 00 00 MMM MMM GG GG XX XX 88 88 88 88 55 00 00 MMMM MMMM GG XX XX 88 88 88 88 55 00 00 MM MMMMM MM GG GGGGG XXXX 88888 88888 555555 00 00 MM MMM MM GG GG XX XX 88 88 88 88 55 00 00 MM MM GG GG XX XX 88 88 88 88 55 00 00 MM MM GG GG XX XX 88 88 88 88 55 00 00 MMMM MMMM GGGGGGG XXX XXX 88888 88888 555555 00000 PXM45 BACKUP BOOT Entering sysCardInit ... [ssCardInit]:sysPciInitGT() ... GT64111 PCI init: Device 6 done. [sysCardInit]:ssiInit() ... Initializing Base IPC Base IPC initialized Tlb Store Exception Exception Program Counter: 0x8014afec Status Register: 0x3004ff00 Cause Register: 0x0000000c Access Address : 0x0ff714e0 Task: 0x83017d80 "tRootTask" Tlb Store Exception Exception Program Co^[This causes the PXM45 or PXM45/B to reboot again dumping the core you will get the MGX banner and will indicate that it is entering the Engineering Manufacture Mode.
-
When prompted "Press Return key to stop auto-boot", press ENTER key.
M M GGGGGGG XXX XXX 88888 88888 5555555 00000 MM MM GG GG XX XX 88 88 88 88 55 00 00 MMM MMM GG GG XX XX 88 88 88 88 55 00 00 MMMM MMMM GG XX XX 88 88 88 88 55 00 00 MM MMMMM MM GG GGGGG XXXX 88888 88888 555555 00 00 MM MMM MM GG GG XX XX 88 88 88 88 55 00 00 MM MM GG GG XX XX 88 88 88 88 55 00 00 MM MM GG GG XX XX 88 88 88 88 55 00 00 MMMM MMMM GGGGGGG XXX XXX 88888 88888 555555 00000 PXM45 BACKUP BOOT Entering manufacturing mode ... pxm45bkup>To avoid reset from the Active card, use sysPxmRemove() Use sysFWLoad() for FW download from active PXM. bootusrRoot device: initialized telnet daemon... : lnPci processor number : 0 host name : XXXXXXD1 inet on ethernet (e) : 32.95.230.37:ffffff00 user (u) : auto flags (f) : 0x0 Get MAC Address from ID PROM NV...OK: 00 01 64 44 55 EE [lnPci] Mac address: 00 01 64 44 55 ee Press Return key to stop auto-boot... 3 <<<----- -
Next in [MFG BOOT] prompt, enter "x".
Get MAC Address from ID PROM N
[MFG BOOT]: x
pxm45bkup>
-
Issue the sysPxmRemove command:
pxm45bkup> sysPxmRemove Simulating PXM Card removal. value = 29 = 0x1d
-
Issue the sysFlashBootBurn command using the file name observed in step 3, above.
pxm45bkup>sysFlashBootBurn "C:FW/pxm45_004.000.012.200_bt.fw" Burning backup boot from file=C:FW/pxm45_004.000.012.200_bt.fw Please confirm:[y/n]y ImgHdr: image_type=2,shelf_type=5,card_type=3000 Checksum size is 1145352 ... Simulating PXM Card removal. Downloading C:FW/pxm45_004.000.012.200_bt.fw into the flash ... QUERY TABLE: flash_size=8388608 block_size=131072 write_buf_size=32 buf_wr_time=2048 write_time=2048 erase_time=16384000 burning 0xbfc00000 verify ... ok burning 0xbfc20000 verify ... ok burning 0xbfc40000 verify ... ok burning 0xbfc60000 verify ... ok burning 0xbfc80000 verify ... ok burning 0xbfca0000 verify ... ok burning 0xbfcc0000 verify ... ok burning 0xbfce0000 verify ... ok burning 0xbfd00000 verify ... ok Verify checksum: addr=0xbfc00000 chksum=0x70674e24 size=(0x117a08,1145352)...ok Flash download completed ... -
The last step is to reboot the Standby PXM45 or PXM45/B. Use the resetcd Standby_PXM45_slot_number command.
Solution:
See Workaround. There is currently no solution to this issue.
Note:?issuing RMAs may resolve this problem, however, the delay an RMA introduces will also delay the recovery that could be implemented quickly by following the directions in the Workaround section above.
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 |
|---|---|
|
CSCee77948 (registered customers only) |
TBl exception error occur when during bootcode upgrade |
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:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.