lanadmin error when changing to 100FD

[Jerry L. Sims]

Received the following error from lanadmin, when trying to set lancard ( lan 2 ) to 100FD.
Also, What file is used to set "Autonegotiation = Off"?

Current Configuration :
# lanadmin -x 2
Speed = 100 Half-Duplex.
Autonegotiation = On.

# lanadmin -X 100FD 2
WARNING: The link settings you have specified for this card must match the settings of its link partner.

ADDITIONAL INFO :
**********************
# /etc/ioscan -nfC lan
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
lan 0 0/0/8/0/0/4/0 igelan CLAIMED INTERFACE HP A6794-60001 PCI 1000Base-T
lan 1 0/0/12/0/0 btlan CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon
/dev/diag/lan1 /dev/ether1 /dev/lan1
lan 2 1/0/1/0/0/4/0 igelan CLAIMED INTERFACE HP A6794-60001 PCI 1000Base-T
lan 3 1/0/4/0/0 igelan CLAIMED INTERFACE HP A6847-60101 PCI 1000Base-SX Adapter
lan 4 1/0/6/0/0 btlan CLAIMED INTERFACE HP A5230A/B5509BA PCI 10/100Base-TX Addon
/dev/diag/lan4 /dev/ether4 /dev/lan4

*******************
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
192.168.20.141 192.168.20.141 UH 0 lan0 4136
192.168.20.142 192.168.20.142 UH 0 lan2 4136
192.168.20.128 192.168.20.142 U 2 lan2 1500
192.168.20.128 192.168.20.141 U 2 lan0 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 192.168.20.129 UG 0 lan0 0

******************
netconf
HOSTNAME="it-hp54"
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1


INTERFACE_NAME[0]="lan0"
IP_ADDRESS[0]="192.168.20.141"
SUBNET_MASK[0]="0xffffff80"
BROADCAST_ADDRESS[0]="192.168.20.255"
INTERFACE_STATE[0]=""
DHCP_ENABLE[0]=0

INTERFACE_NAME[1]="lan2"
HOSTNAME="it-hp54"
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1

INTERFACE_NAME[0]="lan0"
IP_ADDRESS[0]="192.168.20.141"
SUBNET_MASK[0]="0xffffff80"
BROADCAST_ADDRESS[0]="192.168.20.255"
INTERFACE_STATE[0]=""
DHCP_ENABLE[0]=0

INTERFACE_NAME[1]="lan2"
IP_ADDRESS[1]="192.168.20.142"
SUBNET_MASK[1]="255.255.255.128"
BROADCAST_ADDRESS[1]="192.168.20.255"
INTERFACE_STATE[1]=""
DHCP_ENABLE[1]=0

GATED=0
GATED_ARGS=""

RDPD=0

RARP=0

ROUTE_GATEWAY[0]="192.168.20.129"
ROUTE_DESTINATION[0]="default"
ROUTE_COUNT[0]="1"

*********************
ifconfig
# ifconfig lan0
lan0: flags=1843
inet 192.168.20.141 netmask ffffff80 broadcast 192.168.20.255
it-hp54 [/etc/rc.config.d]#
# ifconfig lan2
lan2: flags=1843
inet 192.168.20.142 netmask ffffff80 broadcast 192.168.20.255

****************************
# cat hpbtlanconf | grep -v "#"

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

HP_BTLAN_INTERFACE_NAME[1]=lan2
HP_BTLAN_STATION_ADDRESS[1]=
HP_BTLAN_SPEED[1]=100FD

HP_BTLAN_INIT_ARGS="HP_BTLAN_STATION_ADDRESS HP_BTLAN_SPEED"

*********************
# cat hpigelanconf | grep -v "#"

HP_IGELAN_INIT_ARGS="HP_IGELAN_STATION_ADDRESS HP_IGELAN_SPEED HP_IGELAN_MTU HP_IGELAN_FLOW_CONTROL HP_IGELAN_AUTONEG HP_IGELAN_SEND_COAL_TICKS HP_IGELAN_RECV_COAL_TICKS HP_IGELAN_SEND_MAX_BUFS HP_IGELAN_RECV_MAX_BUFS"

HP_IGELAN_INTERFACE_NAME[0]=lan0
HP_IGELAN_STATION_ADDRESS[0]=
HP_IGELAN_SPEED[0]=100fd
HP_IGELAN_MTU[0]=
HP_IGELAN_FLOW_CONTROL[0]=
HP_IGELAN_AUTONEG[0]=
HP_IGELAN_SEND_COAL_TICKS[0]=
HP_IGELAN_RECV_COAL_TICKS[0]=
HP_IGELAN_SEND_MAX_BUFS[0]=
HP_IGELAN_RECV_MAX_BUFS[0]=

[Steven E. Protter · Accepted solution]

WARNING: The link settings you have specified for this card must match the settings of its link partner.

This indicates that lanadmin believes that the device the card is hooked up to does not support 100 BaseT Full Duplex.

I ran some tests on a 100 BaseT hub, one of the earliest ones a consumer was able to purchase and found out it doesn't support full duplex. It supports only half.

I would investigate the device you are connecting to.

SEP

[Ashwani Kashyap]

The switch/hub where you are conencted to , either does not support full duplex or is not set to full duplex .

Consult your network administrator .

[Jerry L. Sims]

The users will be utilizing an application
called "loadrunner" to gather application "performance" information via : /usr/lib/netsvc/rstat/rpc.rstatd.

The appl. folks have indicated they need
the lancard set to: "100FD $ autonegotiated off". Currently lan0 is set correctly. Would
I be correct to assume "lan0" would be the primary card used? The netconf file indicated
:ROUTE_DESTINATION[0]="default

The netstat -rn indicated
:default 192.168.20.129 UG 0 lan0 0

So, I don't have to worry abount "lan2" ?

[Jay Kidambi]

The message you see is only a WARNING, *not* an ERROR. It just tells you that when you are manually configuring a link, you must make sure that the link partner has the same setting. For example, if you are setting the speed to 100FD, you should ensure that the link partner is operating in the same mode. Otherwise the link may not come up or experience performance problems.

Jay

[rick jones]

Unless one knows that aunotneg isn't working properly, it is best to leave it enabled. Having said that:

How Autoneg is supposed to work:

When both sides of the link are set to autoneg, they will "negotiate"
the duplex setting and select full duplex if both sides can do
full-duplex.

If one side is hardcoded and not using autoneg, the autoneg process
will "fail" and the side trying to autoneg is required by spec to use
half-duplex mode.

If one side is using half-duplex, and the other is using full-duplex,
sorrow and woe is the usual result.

So, the following table shows what will happen given various settings
on each side:

Auto Half Full

Auto Happiness Lucky Sorrow

Half Lucky Happiness Sorrow

Full Sorrow Sorrow Happiness

Happiness means that there is a good shot of everything going well.
Lucky means that things will likely go well, but not because you did
anything correctly :) Sorrow means that there _will_ be a duplex
mis-match.

When there is a duplex mismatch, on the side running half-duplex you
will see various errors and probably a number of late collisions. On
the side running full-duplex you will see things like FCS errors.
Note that those errors are not necessarily conclusive, they are simply
indicators.


From the ioscan data, your lan2 interface is a rather new copper gigabit card. Those cards handle autoneg quite well.

FWIW, a _hub_ will always be half-duplex. A switch can support either half-duplex, or full-duplex. A hub is _not_ a switch, and a switch isnot a hub, and anyone trying to sell you a "switching hub" is spouting nonsense.

[Lee Harris_5]

Lucky Sorrow Sorrow Happiness??? Thats the funniest thing I've ever heard ever! :o)

[Florian Heigl (new acc)]

'real' hubs never can run full-duplex ;)

[though I wonder were anyone can still find a hub, unless maybe for network monitoring scenarios]