Lancard stops working ... after a week

[Muthukumar_5]

Just try to configure lan3 as,

ifconfig lan3 netmask gw

Are you able to configure? Try to see the configuration now as,

# netstat -ian

See the ping check to that lan card ip-address.

--
Muthu

[Muthukumar_5]

Use appropriate syntax in ifconfig with up statement. See Examples in ifconfig man page.

check the connectivity now.

--
Muthu

[Elmar P. Kolkman]

The links are of no use. The first one is for a disabled card, which isn't the case... My card is enabled, but just refuses to work anymore. The second link is broken (at least for me).

As for using ifconfig: I tried, but it doesn't help. And as long as linkloop from another server doesn't work, I don't really see the point in trying to assign an IP address: linkloop operates below IP level.

[Robert-Jan Goossens]

Hoi Elmar,

Could you post your servers model and firmware version ?

Looks like there could be an update for this card.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=421118&prodTypeId=329290&prodSeriesId=421119&swLang=8&taskId=135&swEnvOID=7

Regards,
Robert-Jan

[Elmar P. Kolkman]

Robert-Jan,

This is something worth looking into...
The system is a rp3410, and the driver version we use is B.11.11.15, while the link you privided is for B.11.11.17 (which isn't strange, since we update once per year, and this driver is from a time after our update).

But I guess it's a reboot patch, resulting in what I didn't want...

I will install this patch if no other solution can be found.

Thanx...

[Elmar P. Kolkman]

We are going to reboot the system, because we need it to work. The driver upgrade suggested by Robert-Jan will be done next week, in combination with the September 2005 patch bundle and some additional patches. We are still looking into which patches are needed for our system(s).

But any other suggestions as to how to handle this problem are still welcome.

[Steven E. Protter]

Shalom Elmar,

You may need a new NIC card.

After boot. ping it from a linux/unix server or workstation. If the ping response times increase, run xstm or mstm or cstm and exercize the card.

If those ping times increase, you should be able to convince HP to replace the NIC.

SEP

[Jay Kidambi]

Hi,

Could you please clarify which of the 3 interfaces listed (lan0, lan1, lan2) is showing the problem? I think you hinted that it is lan0, but it wasn't very clear from your message. When the problem occurs next time, please run lanadmin -g on that interface and post the output on this forum.

Jay

[John Payne_2]

What about a duplicate MAC address on your network? That would certainly cause the symptoms you are describing.

If possible, have the Network guys do a findhost on that MAC when the card stops working. (I'm assuming you're not the network guy also in your shop. If you are, I beg your pardon. :) )

We have had this happen before in our environment.

Hope it helps

John

[Elmar P. Kolkman]

Thanks for the suggestions so far...

I will look into them when I'm in the office again tomorrow.

The lancard with the problems is lan2, which is located on a combi FC/IGE card.

If the MAC address was on another card somewhere in the network, I would think the linkloop would be succesfull (as long as it's the same vlan), which it wasn't, but if possible I will ask the network guys (of which I'm not one) if they can do such a thing for me.

And the patches are now planned for next week. They would be installed in the near future anyway, so we just swapped some systems in the planning. It is one of 3 storagenodes on the location, so even if we break it down completely with the newest patches, at least the backups keep working.