btlan3

[maria paschali]

Hi,

I recieved this error message in my dmesg on both my A500 and A400 today.

btlan3: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/0/0/0....

when i checked the syslog today, i found that i had two problems worth noting

May 1 13:34:58 kermit EMS [1099]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/system/events/core_hw
/core_hw" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 72024066
-r /system/events/core_hw/core_hw -n 72024065 -a
May 2 12:04:36 kermit vmunix: btlan3: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/0/0/0....


i have gone into the GSP and checked configuration settings. ran ls and xd and it all looks fine.

both boxes are connected and traffic is flowing through because users are still connected.

I am not sure what else i need to look at to make sure that i _really_ don't have a problem.

any ideas?

Thanks Maria

[T G Manikandan]

Hello,
Did you check the configuration on the switch.Set the port to 100Mbps(autoneg off full duplex).Also 100Mbps setting on your NIC card.

use 'lanadmin' to check whether there are some collisions.

Thanks
G Manikandan

[Michael Tully]

Hi Maria,

The first error indicates that the cable or
the connection to your switch did not test
100% accurate. The first thing I would do
is change the cable. With the second error
you need to run the command exactly as
mentioned in the log. This will provide
some further information on the problem.

Cheers
~Michael~

[maria paschali]

Hi

thanks for getting back to me.
I did a lanscan and lanadmin,
lanadmin displays the card and the configuration correctly. So I am assuming that it is ok.

I havne't checked the switch, as i don't have access to that sector. But i will do that when the people are available.

As for the EMS Event Notification. I did run the command before and asked me to check GSP which i did.

So is there anything else i should check?


Thanks

Maria

[T G Manikandan]

#lanadmin

choose lan
choose display

check for the collisions.
As micheal has suggested replace your network cable.

Thanks
G Manikandan

[Michael Tully]

Maria,

What was the exact return of running the command from EMS?

Also what has been mentioned before, the late collisions is a good indicator that you have a mis-match on duplexing between your LAN card and your switch.

If the LAN card is set as auto-neg, you can turn it off and make it hard-coded. You will still need to make a change to your corresponding config file in /etc/rc.config.d

To change it on the fly:
# lanadmin -X 100FD 0 (lan card number)

~Michael~

[maria paschali]

hi again.

thanks for the suggestions. i have checked re-checked the collisions as suggested.

LOCAL AREA NETWORK ONLINE ADMINISTRATION, Version 1.0
Thu, May 2,2002 15:32:32

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

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: display

LAN INTERFACE STATUS DISPLAY
Thu, May 2,2002 15:32:39

PPA Number = 0
Description = lan0 Hewlett-Packard 10/100 TX Full-Duplex TT = 1500
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x306e1395c1
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 800357871
Inbound Octets = 3447025303
Inbound Unicast Packets = 44542296
Inbound Non-Unicast Packets = 49966296
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 37563045
Outbound Octets = 3555177082
Outbound Unicast Packets = 43655448
Outbound Non-Unicast Packets = 43996
Outbound Discards = 4
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

Enter command: quit


Also the GSP is working properly. So i don't think that there is an issue with that. i also checked the logs. and no error messages were reported.

[Michael Tully]

Hi Maria,

Have a look in Appendix A in this document. It describes the indicators from you output.

http://docs.hp.com/hpux/pdf/J3622-90011.pdf

This is a valuable document and worth having a look also in the troubleshooting section.

HTH
~Michael~

[maria paschali]

thanks for all your help.

Maria

[Jim Keeble]

Hi Maria,

If the error occurred at the same time on both systems, check to see if they are both connected to a common switch. The driver will log a message like this if the switch were powered off or rebooted, just as if the cable were disconnected.