Network cable reconnection

[Yu Zhen_1]

I have just done a 100base-t network cable replacement for my K370, K260 and V2250. The application was down and OS was up during the replacement. After the replacement, I found I can't ping out from any of these boxes, I had to reboot the system then everything is ok. I wonder if it's the bug of HPUX or it's due to the network autonegotiation.
The switch is Cisco 8510.
many thanks

[Bill Hassell]

Do you mean:

1. You just replaced the copper cables?

2. You changed from one interface in the K and V-class to a different interface?

3. You changed the network attachment to a 10/100 switch?

Autonegotiation will fail into 100 half-duplex if the card and switch are unable to agree on full or half at 100 BaseT (10BaseT is always half-duplex), but communication will work OK. What does lanscan say? Are the LAN cards up? Do the switch ports show an active link connection?

[Jim Turner]

Hi Yu,

If I've replaced an ethernet cable "hot" and subsequently the connection is not acting right, I usually try the following (assume the i/f in question is "lan1"):

ifconfig lan1 down
ifconfig lan1 up

If no joy, then use lanadmin to reset the i/f in question and ifconfig it back up.

If *still* no soup, a reboot is probably your only recourse.

All the best!
Jim

[John Bolene]

You must have taken more time than the normal TCP/IP timeout value which is normally 3 minutes.

But that should not have caused your problem.

Sounds like a negotiation problem or possibly DHCP lost lease?

What was the time period?

More info needed.

I have taken several hours at times to do network stuff and just plugged the cables back in and never had to reboot the server. So I doubt that it is a HPUX problem.