1833420 Members
2881 Online
110052 Solutions
New Discussion

Network card error

 
Krishnan Viswanathan
Frequent Advisor

Network card error

I am seeing a high collision rate for outbound/inbound traffic on the network card of my HP UX 9000 K class server

How do I pinpoint the error (is it the switch/cable/card ?)

What commands do you recommend ? I already used lanadmin and traceroute to check , but couldnt find out the source of error

(also traceroute fails to reach the host which I am trying to reach. See below)

ljcks001-root> traceroute bu-loki
traceroute to bu-loki (10.0.12.10), 30 hops max, 20 byte packets
1 r1011 (10.1.1.1) 1 ms 1 ms 1 ms
2 ilk8540-01.cnf.com (10.0.5.1) 1 ms 1 ms 1 ms
3 * * *
4 * * *
5 * * *
6 * * *

Thanks
Krishnan
8 REPLIES 8
Patrick Wallek
Honored Contributor

Re: Network card error

The first thing I'd check here is that you do not have a duplex mis-match between your NIC on the 9000 and the switch.

Use 'lanadmin' to check how the card is set.

If both the 9000 and the swithc are set to auto-negotiate, I'd reset them both so that they are fixed at whatever speed and duplex you desire.
harry d brown jr
Honored Contributor

Re: Network card error

Full or half-duplex?

10BT or 100BT, and what kind of card?

Are you using cat-5 cables?

What kind of switch?

Can you do an nslookup on bu-loki?

What is the percentage of IO errors, as a count of errors is meanless without the number of IO's?

How many, and what kind of devices are on your network?

Have you tried to isolate your network?


live free or die
harry
Live Free or Die
Krishnan Viswanathan
Frequent Advisor

Re: Network card error

I have checked the duplex settings. They are the same on the card and the switch (Full Duplex, auonegation off). Type of card is 100BT.

We are using cat 5 cable. I can do nslookup of bu-loki.

The primary network card(10.1.1...) is working, it is the secondary one which is giving errors. This is used for the backup network (10.0.12..)

The net collision rate is close to 100 %

thanks
Sprint Unix Team
Frequent Advisor

Re: Network card error

check whether the ports on the switch corresponds to the correct Vlan...
Bill Hassell
Honored Contributor

Re: Network card error

If the secondary card is showing collisions, and it is supposed to be 100 Mbit fuill duplex, something is definitely broken as it is impossible to have have collisions on a full duplex connection. Did you use lanadmin -x to view the settings for both cards?


Bill Hassell, sysadmin
Krishnan Viswanathan
Frequent Advisor

Re: Network card error

Yup, I checked the settings with lanadmin -x command as well and it seems fine.

I also changed the network cable, changed port at the switch. We would be replacing the card itself today. Hopefuly the problem will get resolved

Thanks so much for all your help
Helen French
Honored Contributor

Re: Network card error

Hi Krishnan,

It seems like a Network Card problem. But before changing it, you can try some more options:

1) R u using the same type of network card ?
2) Compare the network settings / parameters with the primary card.
3) Swap the network cable, if you have not done yet.
4) Try resetting the network card through lanadmin command and reconfigure it.
5) Check the network patch level on your system are up to date.
6) Check the resistance ( hardware) on the network.
7) Check for any ip collision in the second network card's subnet.

HTH,
Shiju
Life is a promise, fulfill it!
Krishnan Viswanathan
Frequent Advisor

Re: Network card error

Thanks Shiju. I compared the settings and reset the card a couple of times already yesterday but it looks like changing the card is the only option now.