1833758 Members
2420 Online
110063 Solutions
New Discussion

netstat -in shows lan1*

 
Rich Wright
Trusted Contributor

netstat -in shows lan1*

Configuring new gigabit fibre lan interfaces.
Have not baan able to reboot yet.
netstat -in shows lan1*.
What does the '*' mean here?
Everything else looks good.
The host can ping itself at the new IP number, but linkloop of the interface to its own mac address fails.
7 REPLIES 7
Jeff Schussele
Honored Contributor

Re: netstat -in shows lan1*

Hi Rich,

That's the sort of indication you'll get when that NIC is in standby mode to accept failover from another, primary NIC or it's been ifconfig'd with a 0.0.0.0 IP.
It's "up" but it doesn't have an IP yet essentially.

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Hazem Mahmoud_3
Respected Contributor

Re: netstat -in shows lan1*

Try resetting the card through lanadmin. Also, what is the model # for that card and driver? We had a problem with a gigabit card that we tried installing (using the "igelan" driver). We swapped it out with an A4929A card (which used the "gelan" driver) and it worked great.

-Hazem
Sridhar Bhaskarla
Honored Contributor

Re: netstat -in shows lan1*

Hi,

The interfaces in 'plumb'ed state are shown in netstat -in output. What do you get if you run 'ifconfig lan1'?.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Rich Wright
Trusted Contributor

Re: netstat -in shows lan1*

That helps somewhat.
Here is the problem.
Hopefully is will be resolved by reboot.
New interface is lan3.
lanscan
8/8/1/0 0x0... 3 UP lan3 UP 5 ETHER Yes 114
ping (self) no others work
PING 192.0.0.2: 64 byte packets
64 bytes from 192.0.0.2:icmp_seq=0.time=0.ms
linkloop -i # 0x0...
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1
netstat -in
lan3 1500 192.0.0 192.0.0.20 0 45 0 66 0
After lanadmin reset, showed with '*'.
The next day, the '*' was gone.
lanadmin
"display"
LAN INTERFACE STATUS DISPLAY
Thu, Mar 11,2004 07:53:34
Network Management ID = 5
Description = lan3 HP HSC 1000Base-SX Release B.10.20.11
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 1000000000
Station Address = 0x3...
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 0
Inbound Octets = 0
Inbound Unicast Packets = 0
Inbound Non-Unicast Packets = 0
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 0
Outbound Octets = 0
Outbound Unicast Packets = 0
Outbound Non-Unicast Packets = 0
Outbound Discards = 66
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367

lanadmin
"reset"
Resetting LAN Interface to run selftest.
LAN Interface test mode. LAN Interface Net Mgmt ID = 5
netstat -in | grep lan3
lan3* 1500 192.0.0 192.0.0.20 0 45 0 66 0

Is there any way to avoid a reboot?
Can I be sure a reboot will fix?



Hazem Mahmoud_3
Respected Contributor

Re: netstat -in shows lan1*

Rich,
What error message are you getting with linkloop?
If the issue is with linkloop failing, take a look at the following threads:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=20618
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=17196

They may shed some light as to where the problem may be.
Is this affecting connectivity in any way?

-Hazem
Hoefnix
Honored Contributor

Re: netstat -in shows lan1*

Hi,

If its an interface in the same subnet as one of the others, try to disable the other interface.
(ifconfig unplumb...)
Then do the same for lan3 and plumb it again and see if you are able to set the IP address to this interface using ifconfig.

HTH,
Peter
Ralph Grothe
Honored Contributor

Re: netstat -in shows lan1*

From my experience with manual plumbing and up'ping of NICs on HP-UX, which I occassionally do when I need to plug-in a laptop P2P in a multiport NIC during some maintenance, I realized that the aterisk '*' appears as soon as the link disappears (e.g. when you pull the cable).
This seems to aggree with your observation of the failing of the linkloop command.
I realized that one cannot really trust the LEDs on the NIC that should indicate a link.
It sometimes happened to me that although the LED was lit green a P2P connection with another multiport NIC of another HP-UX box wasn't yet established on link layer, at least according to linkloop.
The easiest "onboard" test tool for HP-UX boxes seems to be the linkloop command.
When you feed it with the PPA of your connection and the MAC address of the link partner it should return with OK.

When you plumbed and up'ped the NIC can you ping any other host of the subnet (e.g. do you get echos other than from your own IP on broadcasts)?
Can you ping this host from another host of the subnet?
Does the ifconfig set up a host route?
Madness, thy name is system administration