Ethernet Card hardware issue - C3700

[net_senthilkumar]

Dear All,

Model - Workstation model C3700
Version - B.11.11

I had an issue with inbuilt ethernet card, while giving lanscan hwt state down (status) but ifconfig and sam database showing card is enabled and up status.

If i give ifconfig lan0 - status showing up and SAM database - card is enabled. Can anyone explain this scenario what went wrong. Is there any physical hardware issue with builtin ethernet card or I have to install any patches for this issue.

Regards,
Senthilkumar

[Tim Nelson]

If your interface is working ( e.g. you have IP connectivity over this interface ) then I would suspect patches..

If the NIC is not working then lanscan is right and SAM is wrong, there are always plenty of patches for SAM.

[net_senthilkumar]

If I try to ping local ethernet card is working fine but i could not ping next station. I tried to connect with cross over cable but no response from local ethernet card. Any I tried ioscan funC lan0 - interface showing CLAIMED

Is there any patches for this issue to resove as early as possible

regards,
Senthilkumar

[Tim Nelson]

from workstation:

ping localhost

ping default gateway.

If you cannot ping the default gateway then either you have the wrong gateway, it is down, it is on the wrong vlan or the NIC in the workstation is bad.

Also, do not forget to check the status lights on the NIC. If you have no link then you have NIC or cable problems.

You can also check with lanadmin.

lanadmin -x 0 ( returns speed info for lan0 ). If this fails then again either the NIC is bad or your media or the switch port that it is plugged into.

[net_senthilkumar]

from workstation:

ping localhost

-----------------> working fine I dont have any issue localhost and local ip address

ping default gateway. -- standalone system - i didnt assign any gateway for this station

If you cannot ping the default gateway then either you have the wrong gateway, it is down, it is on the wrong vlan or the NIC in the workstation is bad.

Also, do not forget to check the status lights on the NIC. If you have no link then you have NIC or cable problems.

-- light are glowing no issues with status lights

You can also check with lanadmin.

lanadmin -x 0 ( returns speed info for lan0 ). If this fails then again either the NIC is bad or your media or the switch port that it is plugged into.

lanadmin -x 0

# lanadmin -sx 0
Speed = 10000000
Current Config = NO LINK AUTONEG

[Steven Schweda]

> I had an issue [...]

Is that anything like a _problem_?

Has this stuff ever worked before, or is this
the first time you've tried it?

> ping localhost

This does not use the card. It should work.

> -- light are glowing no issues with status
> lights

Great. _Which_ lights are doing _what_?

> # lanadmin -sx 0
> Speed = 10000000
> Current Config = NO LINK AUTONEG

Around here:

dy # lanadmin -sx 0
Speed = 100000000
Current Config = 100 Full-Duplex AUTONEG


Apparently ("NO LINK"), your card is bad, or
else it's not connected to anything. (I
assume that "10000000" is what it says when
it's never seen anyone with whom to
negotiate.) To what do you _think_ it's
connected? (How?)

If you ever get a working cable and a good
connection to some hub or switch (not "NO
LINK"), then, if "ping" still fails, you
might wish to reveal what the IP addresses
are for this interface and the one you're
trying to "ping".

> -- standalone system - i didnt assign any
> gateway for this station

It's standing alone, all right. How alone do
you want it to be?

[rick jones]

At the risk of replaing some things:

* linkloop can be used to do a "link-level" ping without an IP address assigned - it uses MAC/Ethernet addresses - there is also a Linux port at http://www.freshmeat.net/linkloop some switches - ProCurve managed ones at least, with MAC addresses for the switch - will respond to the link-level query linkloop issues.

* there are *two* states for an interface in HP-UX - there is the administrative or "what we want it to be" state and then there is the operational or "what it really is" state - you have probably already seen that in the output of lanadmin...