Unable to set NIC to 100 Full-Duplex on the fly or on boot

[Kirk Reindl]

HPUX11.0
N4000
NIC A5506A
driver btlan

I have two (4port) NICs and I'm unable to set/lockdown any of the available ports to 100FD. Initially, I edited the /etc/rc.config.d/hpbtlanconf file. Then I noticed on boot that the cards were not locked down to 100Full.

@osihpn01::super_ /etc/rc.config.d> 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 0x0010837C821D 0 UP lan0 snap0 1 ETHER Yes 119
0/10/0/0/4/0 0x001083F880F6 1 UP lan1 snap1 2 ETHER Yes 119
0/10/0/0/5/0 0x001083F880CB 2 UP lan2 snap2 3 ETHER Yes 119
0/10/0/0/6/0 0x001083F880E8 3 UP lan3 snap3 4 ETHER Yes 119
0/10/0/0/7/0 0x001083F880F1 4 UP lan4 snap4 5 ETHER Yes 119
1/0/0/0/4/0 0x001083F8B09E 5 UP lan5 snap5 6 ETHER Yes 119
1/0/0/0/5/0 0x001083F8B022 6 UP lan6 snap6 7 ETHER Yes 119
1/0/0/0/6/0 0x001083F8B00A 7 UP lan7 snap7 8 ETHER Yes 119
1/0/0/0/7/0 0x001083F8D0B4 8 UP lan8 snap8 9 ETHER Yes 119


@osihpn01::super_ /etc/rc.config.d> lanadmin -x 8
Current Speed = 100 Half-Duplex

@osihpn01::super_ /etc/rc.config.d> lanadmin -X 100FD 8

WARNING: an incorrect setting could cause serious network problems!!!

Driver is attempting to set the new speed
Reset will take approximately 11 seconds

@osihpn01::super_ /etc/rc.config.d> I waited for a minute
ksh: I: not found
@osihpn01::super_ /etc/rc.config.d> lanadmin -x 8
Current Speed = 100 Half-Duplex
@osihpn01::super_ /etc/rc.config.d>

Please know that the cards that I can't lock down are not assigned IP addresses. However, I didn't think this should be significant.

@osihpn01::super_ /etc/rc.config.d> ifconfig lan8
ifconfig: no such interface

Thanks in advance for responses.

Kirk Reindl

[Ashwani Kashyap · Accepted solution]

Check the ports on the switch where these cards are connected to are also 100FD and also turn AUTO_NEGOTIATION to off on the lan cards .

[Craig Rants]

Agreed, you need to communicate with your networking guys to get on the same page for the speed assignments.

GL,
C

[rick jones]

If one asks for 100FD and the switch is set to auto or 100HD, then the 100FD setting on the NIC should "work" - hardcoding one side means the other's attempt to autoneg will fail and they will fall-back on HD.

This is why I myself prefer to keep autoneg on both sides.

It is interesting that you have observed that an unassigned (wrt IP) interface is having the problem. You might try assigning a dummy IP address to one of those interfaces and try again (ie an IP from the private range if you are not using that, or perhaps even just 1.2.3.4 - remember to unplumb after the experiment.

If hardcoding duplex then "works" it implies (IMO) a bug in either DLPI or the driver. At that point check for more recent driver and DLPI patches, and if those don't resolve it, a call to the RC to log a defect would seem to be in order.

[Alain HONOREZ]

In reply to Rick,

you MUST have both side at 100FD or 100HD or auto.
Any other settings will conduct to poor performance.
If you have 100FD and auto, auto side will fall to 100HD but 100FD will stay at 100FD (and so with collision detection DISABLED !!)

[Kirk Reindl]

Thanks for all responses.

I guess the angle I was taking and what I found out was that the switch is an important component in the mix.


My standpoint was:

I don't care what the switch is set to. I want to force/lockdown a card at 100FD using lanadmin -X 100FD card ins #

Well apparently this is not the case as you can see from my original question.