RE: NIC in FAILED status -- MIDRANGE-L

× 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.

On your line description, is your Ethernet standard *ALL, *ETHV2
or *IEEE8023? We had some trouble years ago with a Cisco router when we
had the standard set to *ALL. We ran some traces and saw that the
iSeries NIC would negotiate with the router about the standard. They
would agree on *IEEE8023 then for some reason the iSeries NIC would
switch to *ETHV2 and the connection would fail. We reconfigured the
line to *ETHV2 and everything started to work.

Guy Murphy
murphyfa@xxxxxxxx
University of Illinois Foundation
217-333-8979

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Monday, January 07, 2008 10:09 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: NIC in FAILED status

It is the standard NIC in a 520. Will run at 1GB and shows that it is
connected at 1GB right now. Connected to a Cisco switch (not sure of the
model). Cisco admin says his side was set to auto also (although I have
read that switch ports should not be set to auto, our switch admins
insist it is "best practice" to set auto on all ports). 520's come
standard with a pair of copper nics and one was working when the second
one was not.

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.