×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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?
This mailing list archive is Copyright 1997-2024 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
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
