RE: NIC in FAILED status

["Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>]

First question, how is the NIC configured?  Half/Full/Auto duplex?
10/100/1000/auto speed?  If you have a mismatch between the switch and
the iSeries configuration, it will remain failed.


Chris Bipes
Director of I.S.
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Monday, January 07, 2008 5:34 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: NIC in FAILED status

Might anyone be able to explain this one.

Our network team did some switch software upgrades last Friday morning.
Our iSeries is connected to the switch that was upgraded. Friday and
Saturday after the upgrade the iSeries NIC was active and communicating.
Sunday morning the NIC went to FAILED status (no one was working the
weekend) during the system restart after our backup finished (we do an
ENDTCP and take down all subsystems before backup and then do a restart
of everything - no a power down). We have multiple NICs so I connected
on another port and varied off/on the FAILED NIC but it would always go
back to FAILED. Sunday night we do a full powerdown/restart  so I waited
for that. This morning no change. Device was still in FAILED status and
would not go active after multiple attempts. We decided to wait for the
network team to come in and check on things. Then magic happened!
Without anyone doing anything (or so they say) the line went active. Are
IBM NICs so smart that they are self-healing?