RE: LAN adapter down on our 510 -- Is there a way to tell whether it's the card, the FSIOP book, or the whole damn sidecar?

This is rather humorous after your comments about maintenance just over a
week ago:

http://archive.midrange.com/midrange-l/200810/msg00140.html

If neither card reports it sounds like rather more than just the card, but
I'd be calling IBM about now if that was an option.

What shows up in SST ? What do the service logs tell you ?

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Saturday, 11 October 2008 12:52 p.m.
To: Midrange Systems Technical Discussion
Subject: Re: LAN adapter down on our 510 -- Is there a way to tell whether
it's the card, the FSIOP book, or the whole damn sidecar?

I wrote:

We had a power failure, long enough to drain one UPS dry. In order to
conserve battery power on the one our 510 is on, we did a normal
PWRDWNSYS on the 510.
When it came back up, the LAN interface (a 2838 card in a 6617 book, in
a "sidecar") refused to come up.

I've tried re-seating the 6617 FSIOP book; no joy.
I've tried re-seating both the 6617 and the 2838; no joy.
I've tried re-seating everything connecting the main cabinet to the sidecar.

The FSIOP and LAN adapter appear to be the only active components in the
sidecar; both show up in WRKHDWRSC as "Not detected."

Is there a way to tell whether it's the card, the book, or the whole
sidecar?