RP8420 rebooted twice

[moonchild]

Hi

RP8420 rebooted twice this month with no messages in syslog, OLDSyslog, shutdownlog or rc.log

Please help me with ts99 analysis

attached are GSP and ts99 files

Thanks in advance

[Prashanth.D.S]

Hi,

It seems there is some hardware issue with the server "BOOT_PD_RENDEZ_TIMEOUT" error in MP log confirms the same.

Can you collect the raw ts99 file from

#/var/tombstones

Best Regards,
Prashanth

[moonchild]

attached is the raw ts99

thanks

[melvyn burnard]

I recommend you log a call with your local HP Response Centre

[Prashanth.D.S]

Hi,

Analysed the log, seems to be issue with Cell 1 recommendation is to have it repalced..

Before that as the earlier recommendation you need to get intouch with HP for a complete analysis of the issue.

Best Regards,
Prashanth

[Sameer_Nirmal · Accepted solution]

The issue releated information in MP logs is

Log Entry 17079: 02/27/2007 11:31:57
Alert level 3: Warning Keyword: FABRIC_CELL_LINK_NOT_TRAVERSABLE_PORT_BAD The fabric link is not useable due to errors on this port.
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 2
Actual Data: 0x0300b00000000000 0x638006b212e000d6 0x0300b00000000000 0x6b0006b212e000d7 0x0100000045e416ad
Log Entry 17080: 02/27/2007 11:31:57
Alert level 3: Warning Keyword: FABRIC_CELL_PORT_NOT_TRAVERSABLE The target XBC's link to the the target cell is not useable.
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 2
Actual Data: 0x0300000000000000 0x638006b512e000d8 0x0300000000000000 0x6b0006b512e000d9 0x0100000045e416ad
Log Entry 17081: 02/27/2007 11:37:54
Alert level 2: Informational Keyword: FABRIC_XIN_TRY_LINK_INIT About to initalize the CC link
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 0 0x4b000f6210e000da 0x0100000045e41812
Log Entry 17082: 02/27/2007 11:48:55
Alert level 3: Warning Keyword: BOOT_PD_RENDEZ_TIMEOUT End of 10 minute waiting period for other cells to rendezvous.
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 0
Actual Data: 0x0000000000000002 0x63800a5510e000db 0x0000000000000002 0x6b000a5510e000dc 0x0100000045e41aa7
Log Entry 17083: 02/28/2007 00:00:07

So probable cause for the reboot could be bad cell board 0. Place a h/w call to HP and get the logs analyased and h/w replaced.