Mailing List Archive: nsp: extreme

Fault on BD6808 48t blade

Index | Next | Previous | View Threaded

term at northnet

Apr 9, 2006, 2:15 PM

Post #1 of 2 (837 views)
Permalink

Fault on BD6808 48t blade

Hi,

Over the weekend i noticed a hardware fault in the logs from a 48t
card in one of our LAN BlackDiamonds.
IP traffic was passing with out a problem but IPX seems to have
dropped off the card that reported a fault
after re seating the card all ipx was back up and working.

anyone here know what these errors are about, I've looked in the
extreme error PDF handbook but nothing listed

SYST: Sys-health-check [ACTION] (hardware failure)
(CARD_HWFAIL_CPU_CNTRL_QUAKE0_TIMEOUT) slot 8
SYST: Sys-health-check [ACTION] (hardware failure)
(CARD_HWFAIL_CPU_CNTRL_QUAKE0_TIMEOUT) slot 8
KERN: ngRxFirst failed WTX2 - (8, 2f, 8000, 4f)
KERN: ngRxFirst failed WTX2 - (8, 2f, 8000, 4f)
SYST: Sys-health-check [ACTION] (hardware failure)
(CARD_HWFAIL_CPU_CNTRL_QUAKE0_TIMEOUT) slot 8
SYST: Sys-health-check [ACTION] (hardware failure)
(CARD_HWFAIL_CPU_CNTRL_QUAKE0_TIMEOUT) slot 8
KERN: ngRxFirst failed WTX2 - (8, 48, 40, 46)
KERN: ngRxFirst failed WTX2 - (8, 48, 40, 46)

here is some tech info that might help
slot 8 module f48t

Platform: BD6808

MSM: MSM-A MSM-B
------------ ------------
Module Type: MSM64i MSM64i
Current State: MASTER SLAVE

Default Cfg Mode: Standard

Image Selected: Primary Primary
Image Booted: Primary

Config Selected: Primary Primary
Config Booted: Primary

EW Versions:
MSM-A
------------
Primary EW Ver: 7.4.2.6 [non-ssh] [wlan]
Secondary EW Ver: 7.4.2.6 [non-ssh] [wlan]

MSM-B
------------
Primary EW Ver: 7.4.2.6 [non-ssh] [wlan]
Secondary EW Ver: 7.4.2.6 [non-ssh] [wlan]

mike at linx

Apr 9, 2006, 11:15 PM

Post #2 of 2 (771 views)
Permalink

Fault on BD6808 48t blade [In reply to]

--On 10 April 2006 10:15 +1200 Term <term at northnet.net.nz> wrote:

> Over the weekend i noticed a hardware fault in the logs from a 48t
> card in one of our LAN BlackDiamonds.
> IP traffic was passing with out a problem but IPX seems to have
> dropped off the card that reported a fault
> after re seating the card all ipx was back up and working.
>
> anyone here know what these errors are about, I've looked in the
> extreme error PDF handbook but nothing listed

Reseating the card may have done the trick, as the BD can do very strange
things because of seating problems, or the card could be on it's way out.

Run the following commands against the card next time you can schedule
downtime for it:

run diagnostics extended slot <foo>
run diagnostics packet-memory slot <foo>

This should tell you what state the card itself is in. The second one
particularly will map out any "bad" areas of packet memory, so they won't
be used again. A certain amount of bad packet memory can be worked around
this way - any more and the card would need RMA-ing.

Both commands above will take the card offline.

Cheers,
Mike
--
Mike Hughes Chief Technical Officer London Internet Exchange
mike at linx.net http://www.linx.net/
"Only one thing in life is certain: init is Process #1"

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads