btlan3 - config and product information

[steven Burgess_2]

Hi all

I'm switching off auto negotiation on a lan card and switch.

I have the doc which links the product code and the driver with the config file

Here's my card

btlan3 CLAIMED INTERFACE PCI Ethernet

100BT : btlan3.c Core 100BT Cleanup PHNE_21687 B.11.00.06

Below is the info from the config doc

PCI built-in, A5838A btlan3 /etc/rc.config.d/hpbase100conf
To disable auto negotiation

lanadmin -X auto_off 0

The question I have is with regard to keeping the above setting once change. I would expect to see the current values in the config file

This is currently

HP_BASE100_INTERFACE_NAME[0]=
HP_BASE100_STATION_ADDRESS[0]=
HP_BASE100_SPEED[0]=

###########################################################################
# The HP_BASE100_INIT_ARGS are reserved by HP. They are NOT user changable.

HP_BASE100_INIT_ARGS="HP_BASE100_STATION_ADDRESS HP_BASE100_SPEED"

:/ # lanadmin -x 0
Current Speed = 100 Full-Duplex Auto-Negotiation-ON
:/ # lanadmin -s 0
Speed = 100000000

Are the values I have already default settings and any new values entered into the config file to enable the new settings at boot time

Thanks in advance

Steve

[Pete Randall]

Steven,

I was recently puzzled by this as well. My conclusion was that, if nothing is present in the config file, the card defaults to auto-negotiate. In order to permanently disable auto-negotiation, you fill in the required values for your card in the config file.

HTH,
Pete

[steven Burgess_2]

Hi Pete

Therefore

HP_BASE100_INTERFACE_NAME[0]=lan0
HP_BASE100_STATION_ADDRESS[0]=0x10837ca290
HP_BASE100_SPEED[0]=100FD auto_off

Looks about right doesn't it

Thanks

Steve

[Pete Randall]

Hi Steven,

Yeah, that looks pretty good, though I've never seen the auto-off in the config file. I assumed that expicitly specifying a speed (100FD) disables auto-negotiation.

Pete

[Pete Randall]

Hi (again) Steven,

Just an FYI - you don't have to specify the station (MAC) address, either.

Pete

[steven Burgess_2]

Hi Pete

Thanks. Will see If I get confirmation from another as per the auto_off setting

Steve

[T G Manikandan]

Steven

your btlan3 checks the file

/etc/rc.config.d/hpbase100.conf

So during startup
the /sbin/init.d/hpbase100 calls this script.

Eventhough you have
HP_BASE100_SPEED[0]=auto_off

I am not sure it will work

because the hpbase100 in the /sbin/init.d
has this

//*
set -- ${HP_BASE100_SPEED[i]}; SPEED=$*

if [ -n "$SPEED" ]; then
if [ $SPEED = "auto_on" -o $SPEED = "auto_ON" -o $SPEED = "AUTO_on" -o $SPEED = "AUTO_ON" ];
then
SPEED="-X auto_on"

elif [ $SPEED = "100fd" -o $SPEED = "100fD" -o $SPEED = "100Fd" -o $SPEED = "100FD" ];
then
SPEED="-X 100FD"

elif [ $SPEED = "100hd" -o $SPEED = "100hD" -o $SPEED = "100Hd" -o $SPEED = "100HD" ];
then
SPEED="-X 100HD"

elif [ $SPEED = "10fd" -o $SPEED = "10fD" -o $SPEED = "10Fd" -o $SPEED = "10FD" ];
then
SPEED="-X 10FD"

elif [ $SPEED = "10hd" -o $SPEED = "10hD" -o $SPEED = "10Hd" -o $SPEED = "10HD" ];
then
SPEED="-X 10HD"

else
echo "ERROR: invalid speed value for $NAME interface" >&2
SPEED=""
fi
*//

Here there is no elif statement for auto_off.

Is that a new elif should be added for auto_off,
--to disable auto-neg at startup?

Thanks

[Pete Randall]

Hi (again) Steven,

For confirmation, here's the setup of the machine I was recently configuring:

#ioscan -kfnClan
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core


#lanadmin -x 0
Current Config = 100 Full-Duplex MANUAL


#cat /etc/rc.config.d/btlanconf
HP_BTLAN_INTERFACE_NAME[0]=lan0
HP_BTLAN_STATION_ADDRESS[0]=
HP_BTLAN_SPEED[0]=100FD

###########################################################################
# The HP_BTLAN_INIT_ARGS are reserved by HP. They are NOT user changable.
###########################################################################

HP_BTLAN_INIT_ARGS="HP_BTLAN_STATION_ADDRESS HP_BTLAN_SPEED"

# End of hpbtlanconf configuration file


Pete

[steven Burgess_2]

Hi

So I will have to add another elif in the script ?

elif [ -n "$SPEED" ]; then
if [ $SPEED = "auto_off" -o $SPEED = "auto_OFF" -o $SPEED = "AUTO_off" -o $SPEED = "AUTO_OFF" ];
then
SPEED="-X auto_off"

Why is there no initial statement to check if this setting is off ?

Steve

[Pete Randall]

Steven,

No, I wouldn't mess with the script. Just use the conf file.

Pete

[steven Burgess_2]

Pete

That's what I thought

T G , any more input ?

Thanks

Steve

[T G Manikandan]

There is no need to reboot the machine.
You can check & confirm that by executing
/sbin/init.d/hpbase100 stop
/sbin/init.d/hpbase100 start
after modifying your /etc/rc.config.d/hpbase100.conf file
for

HP_BASE100_SPEED[0]=
auto_off
and checking your output from
#lanadmin -x

Revert
Thanks

[sven verhaegen]

I would like to put in my 5 cents here because this AUTO_OFF function might be completely misunderstood

you should know that the rules for negotiation or non-negotiation ar clearly defined in the RFC's , they state that we either have negotiation or fixed settings on both end for it to work OK , the way HP implements this is so that the card by default sets itself to auto_negotiation , for it to work fine we need both sides to negotiate otherwise the action doesn't function so :

fixed to fixed is ok
auto to auto is ok
auto to fixed or non-negotiating is not ok

non-negotiating to non-negotiating is also a bit wrong as what should normally happen depends entirely on the vendors point of view , HP when not able to set a negotiation will revert to speed sensing and set 100 or 10 HD as standard , a cisco device will normally revert to 100 FD so you could en up with duplex issues , the changing in the hp...conf file is indeed the way to go but know that the change only takes place after the card has initialised by the lanadmin -x command so the card did do some negotiation before , the lanadmin -x that is executed during the script siply overwrites the initial findings , i have no idea why you would like to set the card to auto_of I would advise eithetr to go for the fixxed 110FD/HD int he hp...conf file together with a fixed setting on the switch/router device as this leave the lease room for negotiation and/or duplex mismatch issues

[Sajid_1 · Accepted solution]

This document clearly explains your solution:
http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000048403577

Doc ID - KBRC00001505

[steven Burgess_2]

Sajid

Could you please explain how you found the document within the knowledge trees

I searched for all sorts of strings and couldn't find that type of doc

Thanks in advance

Steve

[Sajid_1]

Steven:
1) The TKB search function and limit *clearly* depend up on the type of support contract you have with HP.
2) If you have a support from HP, then get the system handle and link the handle to your ITRC account. This can be done from your profile page.
3) Once linked, open the Technical Knowledge base and give your search string there. For eg: I gave "btlan3 configuration"
4) This will list you all documents which contains these keywords.

gl,

[Cheryl Griffin]

Make sure your system handle is linked to your support contract, otherwise you will not have full access to the ITRC Knowledge Base. If the system handle is not linked, you will get only limited access to some documents.

Cheryl

[James R. Ferguson]

Hi Steve:

For more network information, I think you'll find this url quite useful:

http://techsolutions.hp.com/

You can follow it futher, for instance to:

http://techsolutions.hp.com/fe/configs.html

...and...

http://techsolutions.hp.com/fe/an.html

Regards!

...JRF...

[steven Burgess_2]

Hi Cheryl - Sajjid

I have a support contract and have just linked it to my id. Just getting to know the best way to search through the vast area within the site

Thanks

Steve

[Sajid_1]

Hi Steven,

Yes, once you linked you will feel the difference in the search outputs. For a complete detail about your search limitations - go to your profile and see the description about your system handler. You can also place hardware and software calls through the same ID.

gl,