A3495 in K-Class won't come up in 100HD/FD mode

[Chris Campbell_4]

Hi -

I recently added an A3495 to a K-class HP-UX 11.0 box. As far as I know the correct driver, latest patches, and config settings are in place.

The board self-tests fine, and works fine in either 10HD or 10FD mode. When I try to switch it to 100mbit mode using: "lanadmin -X 100FD 1" the command returns normally; however, the link is dropped. The FDX and 100MB LED's on the port on my (non-HP) switch flash, and the LINK LED is off.

Same result if I try to use auto-sense (which appears to try to switch into 100FD anyway).

When I do lanadmin -X 10FD 1 it reinitializes fine and the link comes back up.

Is there some known issue/patch preventing this adapter from working in 100FD mode?

No errors spotted in rc.log or syslog.log. Cable is new 2m Cat-5 (switch is in same rack as server) so it is not a length issue.

Any tips? Thanks...

[Patrick Wallek]

What is the port on your switch set at?

The consensus in the Forums is to NOT use auto negotiation for anything. Hard set the speed on both the switch and the NIC and see what happens.

[Sridhar Bhaskarla]

I never had good luck with HP-PB 100/10 card with Auto-off on both swith and the server. But it works fine with all other cards. This is what I have been doing as a work around for HP-PB cards.

1. Install all the latest patches related to 100BT.

2. Set the switch port to AUTO-ON.
3. On the server do

lanadmin -X 100FD nmid (or ppa if it is 11.0)

4. Make sure the interface is up and you can ping.

5. Set the switch port to 100FD (AUTO-OFF)
6. Verify the connectivity again.

Edit /etc/rc.configd./hpbasetconf and make changes.

Points only if the above works for you.


-Sri

[Chris Campbell_4]

Thanks guys...I will check into that. Seems like probably an issue with the switch. The A3495 seems to be trying to do what I ask it to do.

It's a "low-end" switch that I don't know much about; hopefully it has a way to defeat the auto-sense.

I may also try a different switch or hub to help isolate the problem.

Thanks again

[melvyn burnard]

Another possible point is to check the cable, ensuring it is CAT5 at least. There have also been issues seen when the cable is between about 35-45 metres long.
Just an extra thing to check.

[Jerry Jaynes]

We have had this discussion in detail here. You have to set the sewithc and the port to 100FD autonegotiate off. If you don't it is a crapshoot as to whether the system will come up full or half.

On the server, edit the /etc/rc.config.d/hpbase100conf and change the following to:
HP_BASE100_INTERFACE_NAME[0]=lan0
HP_BASE100_STATION_ADDRESS[0]=
HP_BASE100_SPEED[0]=100FD

If the card is an addon as you say, the hpbase100conf may be hppci100conf or hpsppci100conf or whatever. Make the same changes there. Do a lanscan to determine what lan card your looking at and the NMID or ppa.

# 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 0x001083F5A5C9 0 UP lan0 snap0 1 ETHER Yes 119
0/4/0/0 0x0060B0B3B5E9 1 UP lan1 snap1 2 ETHER Yes 119

Have the switch locked down to 100FD autonegotiate off as well. Reboot your server and things will settle down to 100FD. Do this on ALL our workstations as well that rely on 100FD. If you don't you will experience EXTREME performance issues, loss of data unhappy customers, etc. etc. etc...

Good luck!

Jerry