syslog message about "AUI Loopback Failed at 0/0/0/0"

[Carol Yu]

I have seen the following message in the syslog when server reboots:

Jul 11 14:04:59 atldxi9 vmunix: Memory Information:
Jul 11 14:04:59 atldxi9 vmunix: physical page size = 4096 bytes, logical page size =
4096 bytes
Jul 11 14:04:59 atldxi9 vmunix: Physical: 8388608 Kbytes, lockable: 6477848 Kbytes,
available: 7439916 Kbytes
Jul 11 14:04:59 atldxi9 vmunix:
Jul 11 14:04:59 atldxi9 vmunix: btlan3: NOTE: MII Link Status Not OK - Switch Connection
to AUI at 0/0/0/0....
Jul 11 14:04:59 atldxi9 vmunix: btlan3: Reset looper timeout: DMA timeout occurred at 0/
0/0/0
Jul 11 14:04:59 atldxi9 vmunix: btlan3: reset state is 550 at 0/0/0/0....
Jul 11 14:04:59 atldxi9 vmunix: btlan3: WARNING: AUI Loopback Failed at 0/0/0/0....

I am worried about the "WARNING: AUI Loopback Failed at 0/0/0/0....". What does it mean? What should I do to solve this?

Thanks a lot for your help.
Carol

[Bernhard Mueller]

Carol,

0/0/0/0 is the Core IO LAN card HW path,

maybe you have no network connection on this card?

# lanscan
# ioscan -fnkClan
# netstat -rn

should give you an idea which NICs you have and which IP is on which card (0/0/0/0 should be lan0)

Regards,
Bernhard

[Carol Yu]

Thanks a lot Bernhard, I ran the command you sent and got the following result:
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x00306E5CAFF2 0 UP lan0 snap0 1 ETHER Yes 119
0/8/0/0 0x00306E4A47B7 1 UP lan1 snap1 2 ETHER Yes 119
0/9/0/0 0x00306E4A77F2 2 UP lan2 snap2 3 ETHER Yes 119

So it is lan0

# ioscan -fnkClan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0
lan 1 0/8/0/0 btlan5 CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon
/dev/diag/lan1 /dev/ether1 /dev/lan1
lan 2 0/9/0/0 btlan5 CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon
/dev/diag/lan2 /dev/ether2 /dev/lan2

# netstat -rn
Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 876079 lo0 4136
10.26.17.41 10.26.17.41 UH 0 159911864 lan1 4136
10.26.17.0 10.26.17.41 U 2 0 lan1 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
default 10.26.17.1 UG 0 0 lan1 1500

Does this mean that we don't have network connection on the path at all? SO that I don't need to worry about this?

Thanks again,
Carol

[Bernhard Mueller · Accepted solution]

Carol,

at least you have only lan1 configured.

This looks pretty much like a machine that was setup to be a MC/SG node with lan2 as a standby NIC for lan1 and lan0 as a separate heartbeat NIC. However, there is no IP address on lan0 (you can check using ifconfig lan0).

If you cannot take a look at the machine itself and suspect that all cards have do have a network connection, you can use linkloop to verify Layer 2 connectivity.

e.g.
linkloop -i 1 0x00306E4A77F2
would send try to check the link from lan1 (-i 1) to lan2 (given MAC address).

Regards,
Bernhard

[Carol Yu]

Hi, Bernhard,

This server is not clustered with MC/SG, but it does connect to a VA and share that VA with another server.

# ifconfig lan0
ifconfig: no such interface

# linkloop -i 1 0x00306E4A77F2 (lan2)
Link connectivity to LAN station: 0x00306E4A77F2
-- OK

# linkloop -i 1 0x00306E5CAFF2 (lan0)
Link connectivity to LAN station: 0x00306E5CAFF2
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1

So it is safe to say that since lan0 doesn't have connection at all, that's why it shows the warning message in syslog. Since we are not using lan0 at all, so we don't need to worry about the message?

Thanks a lot.
Carol

[Bernhard Mueller]

Carol,

yes basically there is nothing to worry about.

Regards,
Bernhard

[Carol Yu]

Thanks a lot! :)