For what it is worth, we had to replace the network card. We noted issues with network card in the system history log at the time of the failure. Surprisingly, the only other place we were able to see was from the QMGTOOLS collect DASD data which showed numerous occurrences of the following:
We ended doing a shutdown from front panel, which means the system went down hard and resulted in some damaged objects that I spent most of today resolving.
Card failed at 15:30, tech arrived around 21:30, we finished just after 2 (in time to start the backup).
from: Jim Hawkins <jhawkins@xxxxxxxxxxxx>
subject: No communication
About 3:30 I got a call from the factory that people can't punch out for the end of the day, foreman can't sign in to review the days work activity. I try to look and my screen goes blank. Look at the Lan Console-it's gone.
With the network guy we tested a few things. Can't ping the Power9. I unplug the network cables from the back and the switch reflects it. Front of the system looks normal (B side N, etc. no error code). Call IBM with system down. 45 minutes later I get call back to get more detailed information and diagnose. (Seemed to take forever talking to this guy) The diagnoses: bad network card. Trying to get the tech and part here by 7, but later is more likely.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.