Configure PCI 100Base-T LAN adaptor (product code A5230A)

[Jon Sharp]

We have and A-series machine with HPUX 11

We have the standard 'Built-in' ethernet adaptor (lan0) and recently installed
a PCI 100Base-T LAN adaptor (product code A5230A) (lan1).
We loaded the driver for A5230A via swinstall from the CD set, and configured
the IP address, mask etc via sam.

However after clicking OK we get the error message - invalid duplex setting -
although the IP addr settings are saved, and the adaptor appears to function -
although with a ping response time around 250 ms - whereas the built-in is
about 10ms.
Running linkloop we however get an error:

milton/d/crms/src(931)# linkloop -i snap1 0x001083F6ED07
Link connectivity to LAN station: 0x001083F6ED07
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1

milton/d/crms/src(930)# linkloop -i snap0 0x001083276AB7
Link connectivity to LAN station: 0x001083276AB7
-- OK

Other info:

milton/etc/rc.config.d(928)# ioscan -fkC lan
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
lan 1 8/0/1/0 btlan5 CLAIMED INTERFACE PCI Ethernet
(10110019)
lan 0 8/0/20/0 btlan3 CLAIMED INTERFACE PCI(10110019) --
Built-in #1

milton/d/crms/src(928)# lanscan
#Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/0/1/0 0x001083F6ED07 1 UP lan1 snap1 1 ETHER Yes 119
8/0/20/0 0x001083276AB7 0 UP lan0 snap0 2 ETHER Yes 119


Do you know why we get the - invalid duplex - setting error?
Why does lanscan fail by interface appear to work?
Could you point me to detailed docs on this card?

thanks

[Dave Wherry_1]

Jon,
I won't be able to help you. I wanted to add some more information that I have
found. We also are using the 100Base-T LAN adapters and have very bad
performance. We are using them in several K boxes. Last fall we did a large
rcp of data, around 120GB, and it completed in 6 hours. Since then we have
upgraded to UX 11.0. When attempting the rcp again it took nearly 18 hours.
Same hardware, just running UX 11.0.
When configuring one of these cards they by default come up with
autonegotiation on. If I try to modify this and turn Autoneg off, speed comes
up as 100 and duplex as FULL. However, when I try to accept these settings in
sam I get the following error:
ERROR: lan1 interface | PPA 1 : btlan4 : ERROR: Setting 1 is unsupported
Valid types :10HD, 10FD, 100HD, 100FD, AUTO_ON
Old Station Address = 0x0060b04bcb0d
New Station Address = 0x0060b04bcb0d

I have to cancel out and the changes do not take. The error contradicts the
settings. If Autoneg is on the other setting should not matter. If it is off,
100 full duplex is a valid setting.
I believe there is something broken in UX 11 and the Response Center has not
been able to help.

[Berlene Herren_1]

Make sure in the files /etc/rc.config.d/hpbase100conf AND hppci100conf you do
NOT have the station address in there, either in the second line or the third.

Berlene

[Jason Luginbuhl_1]

Dave,

The answer to your problem is in the error code that you presented. You can see
that the duplex is being set to a station address instead of a valid setting
like 100FD, 100HD, auto_on, 10HD, or 10FD. Check the values for the SPEED
variable in the 100Base-T config files with:

# cd /etc/rc.config.d
# grep SPEED hp*conf

The station address problem is normally a result of using SAM to configure the
interface. If the latest SAM patch is loaded this should not be a problem but
without it, this is a known problem. It is also recommended that the latest
appropriate network and 100Base-T patches be loaded for the best performance.

[Alan Riggs_1]

If the latest networking patches are installed you can check teh speed and
duplex settings with:

lanadmin -x

You can set them with:

lanadmin -X

Once you have verified a working speed/duplex setting (autonegotiate should be
turned off, the port on the switch/hub should be set explicitely) then you can
code the appropriate values into the configuration file in /etc/rc.config.d/