Setting RP34xx NIC Speed

[Dave Goodwin_1]

I have a new RP34xx server, our first, and I cannot get the built in 10/100/1000 NIC to link up with our switch. How can I go about changing the port speed so it is fixed at 100 full duplex?

Thanks!

Dave

[Pete Randall]

Dave,

lanadmin -X 100FD

should do it!



Pete

[Pete Randall]

Dave,

lanadmin -X 100FD 0 (where 0 is the id of the NIC - from lanscan)

should do it!



Pete

[Sridhar Bhaskarla]

Hi Dave,

From teh command line use

lanadmin -X 100FD 0 (Replace 0 with the ppa# of the lan card from lanscan command. For built-in cards, you most likely get the device file as lan0).

To hardcode the speed so that the system will pick up the speed when it reboots, edit /etc/rc.config.d/hpbase100conf file and add the lines

HP_BASE100_INTERFACE_NAME[0]=lan0
HP_BASE100_SPEED[0]=100FD

-Sri

[Helen French]

Did you try 'lanadmin' command:

# man lanadmin
# lanadmin -X 100FD PPA_num

Also, change it in the config file in /etc/rc.config.d

[Sridhar Bhaskarla]

Hi (Again),

I forgot to add that you will need to check your switch setting. With lanadmin -X 100FD 0, you are setting it to 100 Full duplex with auto negotiation off. If your switch is set to Auto Negotiation on, it may not work. So you will need to ensure that the switch port is also set to 100 Full duplex with Auto Negotiation off.

-Sri

[Ted Buis]

Dave,

If you are new to HP-UX, I would suggest using 'sam'. You can set it from that tool.

TB

[Dave Goodwin_1]

Thanks all. Each of your suggestions did work, though I ended up using SAM to finalize it. Everything's up and running. Also required our Network team to fix the switch port at 100Mb as it would seemingly not auto-negotiate even with the RP's port locked at 100.

Dave

[Steven E. Protter]

It is useful with 100 BaseT switches to hard code the settings you want in a file called /etc/rc.config.d/hpbtlanconf

Attaching mine as a reference.

SEP

[Ted Buis]

'sam' can fix the speed and duplicity. I have seen plenty of problems with auto-negotiation not working as advertised.

[rick jones]

If you hardcode one side, autoneg will "fail" - as it is supposed to. If autoneg "fails" then the side that is trying to do the autoneg is _required_ by the specification to enter half-duplex mode (because it must assume the other side is older kit that does not understand full duplex).

So, you either set autoneg on _both_ sides, or you set it on none.

Is your switch very old, or very low-end?

[Brian Hackley]

Dave,

The rp34*0 servers can come with one of 3 different Gigabit in the core I/O. Find out which one you have with:
# ioscan -kfClan
Look under the field listed for "driver" e.g. # ioscan -kfClan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/1/2/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Ba
se-T Adapter

This could be "gelan", "igelan" or "iether" on your system. The config file should be in /etc/rc.config.d/hp{yourdrivername}conf
For example /etc/rc.config.d/hpigelanconf

Edit the file so that the speed will be set at the next boot time. e.g.
HP_IGELAN_INTERFACE_NAME[0]=
to reflect the lan#, e.g. lan0
HP_IGELAN_INTERFACE_NAME[0]="lan0"
and
HP_IGELAN_SPEED[0]="100FD"

You may need to adjust the index [0] and lan card name. The indexes are all relative to 0, and do not have to match the lan# of the lan card. For example if you have an igelan card is lan6, but is the only igelan card on the system, you would specify:
HP_IGELAN_INTERFACE_NAME[0]="lan6"
and
HP_IGELAN_SPEED[0]="100FD"

Then run the startup script to test:
e.g.
# /sbin/init.d/hpigelan start
Then examine speed/duplex with
# lanadmin -x 0

I hope this isn't too confusing,

-> Brian Hackley