Enabling an NIC after IP/Hostname Change

[daniel figueroa]

I have a K370 that has known good network
cards, which I'm attempting to bring back online after it has be de-commissioned for a few months.

The problem working in SAM I changed the computer name and IP successfully, but LAN0 will not stay in ENABLED state. If I take the SAM action of enabling it, it does not enable.

What would be a couple of things to check why this is happening, please?

Thank you,
Dan

[Sridhar Bhaskarla]

Hi Dan,

Check the physical connectivity. If you have another system on the same subnet, find out it's MAC address (if it is HP, then use lanscan) and run linkloop.

linkloop -n 2 -i 0 mac_addr_of_other_sys

lan0 is mostly the built-in interface. If not, then you may have to change the speed settings. Post your 'lanscan' and 'netstat -in' outputs so that someone can help you.

-Sri

[Robert-Jan Goossens]

Hi Dan,

Sam is great tool, just not for changing the hostname and IP :-)

# set_parms initial
or
# set_parms hostname
and
# set_parms ip_address

Kind regards,
Robert-Jan

[Jeff Schussele]

Hi Dan,

Check with your network folks for:

1) The speed & duplex setting of the port you're connecting it to & make sure the card is capable of & set to them.

2) If it's an intelligent switch, that the port is set for the proper VLAN that the IP is residing in.

Then check that there's no /etc/rc.config.d/hp??????conf file that's setting an erroneous MAC address for this lan instance.

HTH,
Jeff

[daniel figueroa]

I ran the lanadmin test and received the following error mesg:"HPPB 10/100BASE-T driver detected bad cable connection
between the adapter in slot 2 and the hub or switch."

Would this be the cause of not being able to enable my card? I have the LAN cable connected at LAN0. That must be the adapter in slot 2, correct?

Based on HP-UX patch PHNE_21883:
1. JAGac86612
When the switch is at 100FD/100HD and the cable length
is approximately between 35 and 41 meters,
autonegotiation fails and the link does not come up. The
following nettl DISASTER message will be displayed on the
console repeatedly.
"HPPB 10/100BASE-T driver detected bad cable connection
between the adapter in slot and
the hub or switch."

[Sridhar Bhaskarla]

Dan - Can you post your 'lanscan' and 'netstat -in' outputs?. You can actually look at the interfaces configured from netstat output and correlate them to lanscan to get the hardware path and then verify the cable connections.

-Sri

[daniel figueroa]

OK, I'm using LAN1 instead of LAN0, and its enabled. The problem is when I can not ping the gateway. I'm getting "no route to host" when I try and ping the gateway. I can of course ping 127.0.0.1.

Is this no a network issue outside of the server itself, if I can not ping the gateway?

Thanks All

[daniel figueroa]

Thanks All, the problem was resolved when the NetAdmin configured the switch/port to run a 100 Full/Duplex. As soon as that was done, and because I was attempting to initiate at that rate, the card enabled.

Dan