topic Re: lan0 problem in Operating System - HP-UX

lan0 problem

Co van Berkel — Thu, 10 May 2007 01:59:18 GMT

Hey,
We hava three rp3440 servers.
On two of the servers i can't get the lan0 working.

What I see is that in the "lanadmin -x card_ifno 0" output there is stated that:
"Driver State: IGELAN_OFFLINE"

# lanadmin -x card_info 0
*********** Version Information **********
Driver version: B.11.11.24
Firmware version: 1.0.5/1.10
Chip version: 0x15
PCI Sub-System ID: 0x12a4 (Core I/O 1000Base-T)
PCI Sub-Vendor ID: 0x103c
Board Revision: A0
Software Key: 0
Engineering Date Code:

********** Card Setting ***********
Driver State: IGELAN_OFFLINE <====
Auto Negotiation: On
Flow Control: On
Send Max Buf Descriptors: 10
Recv Max Buf Descriptors: 1
Send Coalesced Ticks: 150
Recv Coalesced Ticks: 0

# ifconfig lan0
lan0: flags=1843
inet 192.168.1.33 netmask fffffff0 broadcast 192.168.1.47

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/2/0 0x0018FE8C0F61 0 UP lan0 snap0 1 ETHER Yes 119
0/2/1/0/6/0 0x00110A427ED6 1 UP lan1 snap1 2 ETHER Yes 119
0/2/1/0/6/1 0x00110A427ED7 2 UP lan2 snap2 3 ETHER Yes 119
0/6/1/0/6/0 0x001560DE57D4 3 UP lan3 snap3 4 ETHER Yes 119
0/6/1/0/6/1 0x001560DE57D5 4 UP lan4 snap4 5 ETHER Yes 119

# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
lan 0 0/1/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Co
re
lan 1 0/2/1/0/6/0 iether CLAIMED INTERFACE HP AB290-60001 PCI/P
CI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter
lan 2 0/2/1/0/6/1 iether CLAIMED INTERFACE HP AB290-60001 PCI/P
CI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter
lan 3 0/6/1/0/6/0 iether CLAIMED INTERFACE HP AB290-60001 PCI/P
CI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter
lan 4 0/6/1/0/6/1 iether CLAIMED INTERFACE HP AB290-60001 PCI/P
CI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter

# linkloop -i 0 0x0018FE8C0F61
Link connectivity to LAN station: 0x0018FE8C0F61
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message

Re: lan0 problem

Duncan Edmonstone — Thu, 10 May 2007 03:13:52 GMT

And you're sure you have link on the card?

What's the output of :

lanadmin << EOF
lan
ppa 0
display

quit
EOF

HTH

Duncan

Re: lan0 problem

Co van Berkel — Thu, 10 May 2007 03:18:06 GMT

Hey Duncan,

# lanadmin <> lan
> ppa 0
> display
>
> quit
> EOF

LOCAL AREA NETWORK ONLINE ADMINISTRATION, Version 1.0
Thu, May 10,2007 10:16:37

Copyright 1994 Hewlett Packard Company.
All rights are reserved.

Test Selection mode.

lan = LAN Interface Administration
menu = Display this menu
quit = Terminate the Administration
terse = Do not display command menu
verbose = Display command menu

Enter command:
LAN Interface test mode. LAN Interface PPA Number = 0

clear = Clear statistics registers
display = Display LAN Interface status and statistics registers
end = End LAN Interface Administration, return to Test Selection
menu = Display this menu
ppa = PPA Number of the LAN Interface
quit = Terminate the Administration, return to shell
reset = Reset LAN Interface to execute its selftest
specific = Go to Driver specific menu

Enter command: Enter PPA Number. Currently 0: 0

LAN Interface test mode. LAN Interface PPA Number = 0

clear = Clear statistics registers
display = Display LAN Interface status and statistics registers
end = End LAN Interface Administration, return to Test Selection
menu = Display this menu
ppa = PPA Number of the LAN Interface
quit = Terminate the Administration, return to shell
reset = Reset LAN Interface to execute its selftest
specific = Go to Driver specific menu

Enter command:
LAN INTERFACE STATUS DISPLAY
Thu, May 10,2007 10:16:37

PPA Number = 0
Description = lan0 HP PCI Core I/O 1000Base-T Release B.11.1
1.24
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 1000000000
Station Address = 0x18fe8c0f61
Administration Status (value) = up(1)
Operation Status (value) = down(2)
Last Change = 100
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 = 7
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367

Press to continue

Ethernet-like Statistics Group

Index = 1
Alignment Errors = 0
FCS Errors = 0
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0

LAN Interface test mode. LAN Interface PPA Number = 0

clear = Clear statistics registers
display = Display LAN Interface status and statistics registers
end = End LAN Interface Administration, return to Test Selection
menu = Display this menu
ppa = PPA Number of the LAN Interface
quit = Terminate the Administration, return to shell
reset = Reset LAN Interface to execute its selftest
specific = Go to Driver specific menu

Re: lan0 problem

Senthil Kumar .A_1 — Thu, 10 May 2007 03:32:52 GMT

Hi,

From your tests...

"# linkloop -i 0 0x0018FE8C0F61
Link connectivity to LAN station: 0x0018FE8C0F61
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
"

Pardon me if this question is too basic. Does this not mean that the card may not be connected to the network switch or it might have connection problem with the switch or it could be an issue with the LAN cable. I observe that you link looped the MAC address of lan0 itself. A better test would be to try Linklooping any other MAC ID which is on the same network for confirmation.

SK

Re: lan0 problem

Mridul Shrivastava — Thu, 10 May 2007 03:34:06 GMT

Administration Status (value) = up(1)
Operation Status (value) = down(2) <== This means there is no cable connected to this interface or cable connected is faulty.

Please try swapping the cable with the working one..

Re: lan0 problem

Co van Berkel — Thu, 10 May 2007 03:39:51 GMT

Hey Sk,
Yes, your right.
But a linkloop to lan0 on the system is the first to check?
If this don't work than a linkloop on a other MAC ID don't work.
Regards,
CvB

Re: lan0 problem

Co van Berkel — Thu, 10 May 2007 03:52:58 GMT

Hey,
Problem solved.

1. New crosscabel.
2. /sbin/init.d/net stop
3. ifconfig lan0 umplumb
4. /sbin/init.d/net start

Now "linkloop -i 0 " works and
"linkloop -i 0 " works.
Regards,
CvB

Re: lan0 problem

Co van Berkel — Thu, 10 May 2007 03:54:49 GMT

Solved, new cable!

Re: lan0 problem

rick jones — Fri, 11 May 2007 11:23:05 GMT

FWIW, Gigabit Ethernet (1000Base-T) requires support for Auto MDIX, which means that for back-to-back/switch-to-switch one does not need a cross-over cable.