topic Re: checking full duplex with lanadmin in Operating System - HP-UX

checking full duplex with lanadmin

Scott_20 — Tue, 31 Aug 2004 07:38:36 GMT

all,
how do you check for half/full duplex with lanadmin.

how do you set 100base T with lanadmin?

permanently hardcode?

thanks,
scott

Re: checking full duplex with lanadmin

Pete Randall — Tue, 31 Aug 2004 07:45:50 GMT

Scott,

Use "lanadmin -x 0" where 0 is the PPA number of the card from lanscan.

You can set the speed/duplex with "lanadmin -X 100FD 0". To make this permanent, you'll need to edit the appropriate conf file, based on the driver for your card:

btlan hpbtlanconf
btlan0 hpeisabtconf
btlan1 hpbasetconf
btlan3 hpbase100conf
btlan4 hpgsc100conf
btlan5 hppci100conf
btlan6 hpsppci100conf

Pete

Re: checking full duplex with lanadmin

Sunil Sharma_1 — Tue, 31 Aug 2004 07:46:34 GMT

Hi,

#lanadmin -x

You can get nmid using lanscan command.

You can set speed using
#lanadmin -X 100FD

100FD is for 100Mbps Full Duplex
100HD
10FD
10HD and auto_neg is value can be set

For permanent setting you have to modify NIC config file in /etc/rc.config.d directory name of file depends on NIC.

Sunil

Re: checking full duplex with lanadmin

Geoff Wild — Tue, 31 Aug 2004 07:56:23 GMT

To check:

for i in `/usr/sbin/lanscan | awk '/ETHER/ {print $3}'`; do
x=`/usr/sbin/lanadmin -x $i 2>&1 | awk -F= '{print $2}' | sed -e 's/^ *//' -e 's/ *$//'`
echo echo "ppa $i " $x
done

To set:

lanadmin -X 100FD 1

Also, vi the appropiate drive file in /etc/rc.config.d

Example:

hpbtlanconf

HP_BTLAN_INTERFACE_NAME[0]=lan0
HP_BTLAN_STATION_ADDRESS[0]=
HP_BTLAN_SPEED[0]=100FD

Rgds...Geoff

Re: checking full duplex with lanadmin

Franky_1 — Tue, 31 Aug 2004 08:39:07 GMT

Hi,

you can type "lanscan" to see the available NIC's
Then select the In# Number

lanadmin -x to display
lanadmin -X to set

and edit /etc/rc.config.d/hp.conf file
to permanently change the settings

Regards

Franky

Re: checking full duplex with lanadmin

rick jones — Tue, 31 Aug 2004 19:30:31 GMT

If you suspect a duplex mismatch, first verify it my looking a the full lanadmin statistics - check for FCS errors if the description of the interface is full-duplex and check for _late_ collisions if the description of the interface is half-duplex:

lanadmin -g mibstats

keep in mind that both ends of a link must be at the same setting - both must be half, or both full or both auto, you cannot mix, even with auto on one side.