Configuring the A6847A card

[Leif Halvarsson_2]

Hi
I have installed a A6847A GBit ethernet card in an A400 server. I have also installed the software:
GigEther-01 B.11.11.07 PCI GigEther;Supptd HW=A6794A/A6825A/A6847A

ioscan -f show the card as:
lan 1 0/4/0/0 igelan CLAIMED INTERFACE HP A6847-60101 PCI 1000Base-SX Adapter

But if i try to configure the card, using SAM (as recommended) I get the error:

"Configuration of this Network Interface card is not supported with this version of the driver product. Please install the latest version or contact the support personal for further assistance"

Which version orf the software is correct and is there any patch avilable for upgrading ?

[Bill McNAMARA_1]

Patch SAM:
http://www4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_25902&context=hpux:700:11:00

[Bill McNAMARA_1]

latest patch: 11.00
http://www4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_27375&context=hpux:700:11:00

11i
http://www4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_27374&context=hpux:800:11:11

[Jeff Schussele]

Hi Leif,

What are you trying to configure?
The speed/duplex has to remain 1000/FD for gig-E fibre cards.

If you're just trying to set IP, mask, etc., then I'd suspect you'll need the most current SAM/Obam cumulative patch.
These are very new cards & need very new drivers, so I suspect that SAM doesn't really "understand" these cards.
Regardless, you should still be able to configure them with ifconfig. I had to load Dec '02 HWE patch bundle to get mine to work correctly, but I didn't use SAM (prefer not to actually) to config them, I used ifconfig.

HTH,
Jeff

[Cheryl Griffin]

The LAN patches used to have special installation instructions that said to copy the LAN card config file from /usr/newconfig/etc/rc.config.d to /etc/rc.config.d.

Be sure you have done this. Looking at the latest Gig LAN patch the file would be /usr/newconfig/etc/rc.config.d/hpgelanconf

Then try SAM again.

[Leif Halvarsson_2]

Hi,
Thanks to all of you.
SAM was already patched but (as Cheryl suggested) I had to copy the
/usr/newconfig/etc/rc.config.d/hpgelanconf
to
/etc/rc.config.d/hpgelanconf
before it worked.

I assignet a new IP adress to the card (different from the adress for the internal network card).

But, if I enable the card I lose all contact with the box (also with the internal network card). If I disable the card again I get contact back with the internal card.

I can ping internal to both cards but, if the
A6847A is enabled, not ping from external to any of the cards.

OS is HP-UX 11.11 with GOLDBASE11i B.11.11.0212.4 Gold Base Patches for HP-UX 11i, December 2002
GigEther-01 B.11.11.07 PCI GigEther;Supptd HW=A6794A/A6825A/A6847A HWEnable11i B.11.11.0103.2 Hardware Enablement Patches for HP-UX 11i, PHCO_27374 1.0 cumulative SAM patch

Is there any other configuration to do or software to install before I can get the card working ?

[Michael Tully]

Hi Leif,

What happens if you make your Gb card lan0 and the standard card lan1?
You can change the order in /etc/rc.config.d/netconf.

Below is how I have a Gb card set in /etc/rc.config.d/hpgelanconf

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

HP_GELAN_INIT_ARGS="HP_GELAN_STATION_ADDRESS HP_GELAN_SPEED HP_GELAN_MTU HP_GELAN_FLOW_CONTROL HP_GELAN_AUTONEG HP_GELAN_SEND_COAL_TICKS HP_GELAN_RECV_COAL_TICKS HP_GELAN_SEND_MAX_BUFS HP_GELAN_RECV_MAX_BUFS"

HP_GELAN_INTERFACE_NAME[0]=lan0
HP_GELAN_STATION_ADDRESS[0]=
HP_GELAN_SPEED[0]=auto_on
HP_GELAN_MTU[0]=1500
HP_GELAN_FLOW_CONTROL[0]=1
HP_GELAN_AUTONEG[0]=
HP_GELAN_SEND_COAL_TICKS[0]=1000
HP_GELAN_RECV_COAL_TICKS[0]=0
HP_GELAN_SEND_MAX_BUFS[0]=16
HP_GELAN_RECV_MAX_BUFS[0]=1

# End of hpgelanconf configuration file

Are they defined for a different subnet?

Regards
Michael

[malay boy]

HP_GELAN_INTERFACE_NAME[0]=lan0
HP_GELAN_STATION_ADDRESS[0]=
HP_GELAN_SPEED[0]=auto_on
HP_GELAN_MTU[0]=1500
HP_GELAN_FLOW_CONTROL[0]=1
HP_GELAN_AUTONEG[0]=
HP_GELAN_SEND_COAL_TICKS[0]=1000
HP_GELAN_RECV_COAL_TICKS[0]=0
HP_GELAN_SEND_MAX_BUFS[0]=16
HP_GELAN_RECV_MAX_BUFS[0]=1


Hi Guy's,
what are the different between normal HP card as below with the LAN Card above:

INTERFACE_NAME[0]="lan0"
IP_ADDRESS[0]="172.23.112.13"
SUBNET_MASK[0]="255.255.0.0"
BROADCAST_ADDRESS[0]="172.23.112.255"
INTERFACE_STATE[0]="up"
DHCP_ENABLE[0]=0
ROUTE_COUNT[0]="1"
ROUTE_GATEWAY[0]="158.25.112.254"
ROUTE_DESTINATION[0]="default"

Just corious ....

regards
mB

[rick jones]

FWIW

If you configure two physical NICs to be in the same IP subnet, and they are not both connected to the same broadcast domain (set of switches), then you can have unpleasant effects like loss of connectivity.

Basically, the stack will receive traffic on both NICs but will only send traffic out one of the NICs. If the network is partitioned, this will cause things like ping to not work.

Now, there are some things you can do:

1) don't configure multiple physical (from the standpoint of the transport) NICs into the same IP subnet

2) define static routes pointing through the specific interfaces

3) use ndd to set ip_strong_es_model to one

btw, linkloop can be used to verify physical connectivity on a link without having working IP - so long as there is another system on the network (or each partition) that will respond to the packets sent by linkloop (XID or TEST frames)

[Leif Halvarsson_2]

Hi
Still have no luck with this. When rebooting the server I get error about "Configuring unconfigured filesets" and "Configuring igelan cards". The system complained about patch PHNE_24492 was missing. This patch was not installed but PHNE_25388 which superseds PHNE_24492. I deinstalled GigEther-01 and PHNE_25388 and installed PHNE_24492 and reinstalled GigEther-01 again. Now the system rebooted without errors but the problems remains. Trying linkloop gives the following result (0x00306E2BFDBC is the A6847A card):
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x00306E1B3F07 0 UP lan0 snap0 1 ETHER Yes 119
0/4/0/0 0x00306E2BFDBC 1 UP lan1 snap1 2 ETHER Yes 119
# linkloop 0x00306E1B3F07
Link connectivity to LAN station: 0x00306E1B3F07
-- OK
# linkloop 0x00306E2BFDBC
Link connectivity to LAN station: 0x00306E2BFDBC
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1

[Brian Hackley]

Lief,
You have to specify the card to send the linkloop packet. By default that is the first card ("PPA"). Try:

linkloop -i 1 0x00306E2BFDBC

Hope this helps,

-> Brian Hackley

[Brian Hackley]

Lief,
You have to specify the card to send the linkloop packet. By default that is the first card ("PPA"). Try:

linkloop -i 1 0x00306E2BFDBC

Hope this helps,

-> Brian Hackley

[Leif Halvarsson_2]

Hi,

If using the -i option I get:

# linkloop -i 0 0x00306E1B3F07
Link connectivity to LAN station: 0x00306E1B3F07
-- OK
# linkloop -i 1 0x00306E2BFDBC
Link connectivity to LAN station: 0x00306E2BFDBC
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message

Any idea ?

[Ajit Natarajan]

I need to clarify several points here.

1. A6847-60101 is controlled by the igelan driver. The configuration file is /etc/rc.config.d/hpigelanconf. hpgelanconf is used for A4926A.

2. When the igelan driver is installed for the first time, /usr/newconfig/etc/rc.config.d/hpigelanconf is automatically copied to /etc/rc.config.d/hpigelanconf. No user action is needed.

The automatic copy will not happen if /etc/rc.config.d/hpigelanconf is already present on the system and has been modified.

3. Refer to the Gigabit Ethernet release notes for patch dependency information.

The release note can be found at:

http://docs.hp.com/hpux/onlinedocs/J5683-90006/J5683-90006.html

If a certain patch number is mentioned, any patch that supersedes that will also work. If you find that this is not the case, you should contact your HP support representative.

4. linkloop's syntax is:

linkloop -i

where is the PPA of the card instance through which you want the packet sent and is the MAC address of a remote system. Doing a linkloop to self does not cause a packet to go out on the network.

Thanks.

Ajit
HP Gigabit Ethernet

[Ajit Natarajan]

I notice that your linkloop failed with the UNIX errno 57 which corresponds to an ENOLINK. This means that either the cable is not connected or the cable is bad or for some other reason the link is not being established with the link partner.

You may want to do a

lanadmin -x card_info

to find out the driver state. If it is not ONLINE, you have some cable/link problem.

Ajit
HP Gigabit Ethernet

[Leif Halvarsson_2]

Hi,
The link seems to be down.
# lanadmin -x card_info 1
*********** Version Information **********
Driver version: B.11.11.07
Firmware version: 1.0.4
Chip version: 0x15
PCI Sub-System ID: 0x128b (1000Base-SX)
PCI Sub-Vendor ID: 0x103c
Board Revision: A3
Software Key: 0
Engineering Date Code: C-4230

********** Card Setting ***********
Driver State: IGELAN_OFFLINE
Auto Negotiation: On
Flow Control: On
Send Max Buf Descriptors: 10
Recv Max Buf Descriptors: 1
Send Coalesced Ticks: 150
Recv Coalesced Ticks: 0

The link status LED is not ON and the Activity LED is not flashing. I have tried with a new cable and a different switch port with no difference. I will check tomorrow if there is any mismatch with the switch port setteins.

[Jeff Schussele]

Hi Leif,

Sometimes it's the simple things...
Have you switched the cable ends on the NIC end? They are RX & TX specific.
I don't think there are any switch settings to set on the switch. Gig-E fibre is 1000 FD & that can't be changed. There should be no auto-negotiate as the speed is fixed & since Gig-E fibre has both RX & TX, full duplex is explicit.

Rgds,
Jeff

[Leif Halvarsson_2]

Hi,

If I connect the cable I get no indication on the card LEDs but the LEDs on the switch port changes. the RX LED flashes green and the TX led to steady green. This is not correct, if everything is OK both LEDs should flash. If I disconnect one of the parts the switch LEDs changes as when the cable is completly disconnected but if disconnecting the other part nothing happens, the switch LED indication is the same as with both parts connected.

If I shift the cable parts the switch port indication is the same as with disconnected cable.

I begin wondering if it is a hardware error (faulty card, perhaps one of the transmitters). The problem is that I have no other card to try with.

[Jeff Schussele]

Hi Leif,

Yep, I'm beginning to think it's an HW issue as well.
Could be that the card isn't fully, properly seated.
Log an HW call, have them bring another card & ask that they reseat this one first.
On my card, when I get a good link, I get a solid link LED on the card. You getting that?

Rgds,
Jeff

[Sachin Patel]

Hi Leif,

No one has said anything about this so let me say it.

Do you have proper switch on other side of cable? VGLAN has different swith then normal ethernet switch.

Sachin