Problem with NIC SysKonnect gigabit adapter SK-98xx ver 2.0

[Vinh Nguyen_2]

Hi all,
Because of some work requirement, I need to add a second NIC to my HP C240 workstation which running HP-UX 11.0. The goal is to have this second NIC connect to a special private network 192.168.0.X.

I installed the NIC (SysKonnect gigabit adapter SK-98xx ver 2.0) and the drivers supplied by SysKonnect for HP-UX 11.0 32 bit version.

I edited the /etc/rc.config.d/netconf to include this new NIC and rebooted the system.

INTERFACE_NAME[1]=skge0
IP_ADDRESS[1]=192.168.0.3
SUBNET_MASK[1]=255.255.255.0
BROADCAST_ADDRESS[1]="192.168.0.255"
INTERFACE_STATE[1]="up"
DHCP_ENABLE[1]=0

Lanscan sees it as skge0 and I can ping it from the system locally.

lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/0/20/0 0x0060B0D0E39C 0 UP lan0 snap0 1 ETHER Yes 119
10/0/2/0 0x00005A9F0464 0 UP skge0 3 ETHER No *

ifconfig skge0
skge0: flags=843
inet 192.168.0.3 netmask ffffff00 broadcast 192.168.0.255

########################################
The problem: Communication to other hosts in subnet 192.168.0.X is not working.

What I notice is skge0 interface is not present in the lanadmin. Lanadmin only shows lan0 which is the first interface.

Another redflag within SAM | Network Interface Cards is the hardware path. Although, 10/0/2/0 is skge0 (as shown above by lanscan), its interface name is lan0.

Card Interface Hardware Internet x
Type Name Path Status Address x

Ethernet lan0 10/0/2/0 Enabled 172.16.11.97
Fast Ethernet lan0 8/0/20/0 Enabled 172.16.1.97



One more item confused me is the result of ioscan. It shows the second NIC not as lan but pseudo.

8/0/20/0 lan HP PCI 10/100Base-TX Core
10/0/2/0 pseudo PCI Ethernet (11484320)


I wonder what else I need to do something to get it working. Any inputs is greatly appreciated.

Thank you very much
--nguy--

[D Block 2]

nguy,

it might help if you post a:

$ netstat -rn
$ netstat -in

also, from another system, there might be a Routing problem from your server. thinking, your Default-Gateway should be updated to know how to Route to the 192.168.0. subnet..

so, can you post a 'traceroute' command from your other server trying to hit your local server ?

[Vinh Nguyen_2]

Hi Tom,
Thanks for replying. I doubt it's a routing issue since the hosts I try to reach are on the same subnet, no router involved.

netstat -in
Name Mtu Network Address Ipkts Opkts
skge0 1500 192.168.0.0 192.168.0.3 6355 6355
lan0 1500 172.16.1.0 172.16.1.97 476910 546090
lo0 4136 127.0.0.0 127.0.0.1 593108 593108

netstat -rn
Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 593108 lo0 4136
172.16.1.97 172.16.1.97 UH 0 363108 lan0 4136
192.168.0.3 192.168.0.3 UH 0 6355 skge0 4136
172.16.1.0 172.16.1.97 U 2 0 lan0 1500
192.168.0.0 192.168.0.3 U 2 0 skge0 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
default 172.16.1.99 UG 0 0 lan0 1500

[Mel Burslan]

I have never worked with this kind of NIC before, as a mater of fact I do not remember a time when we put in a non-hp NIC into a hpux server ever, but for some reason, I think your drivers did not get installed properly, because you said your system sees this instance as a pseudo interface.

Just to make sure that the drivers are safe and sound, try running this command:

linkloop -i 3

the number 3 came from your lanscan output. I am assuming (due to formatting of text copied from termianl to here gets broken badly) that number is the one under "ppa number" column. If not, please change it to correct ppa value.

What do you see as the output of this command ? It totally disregards, tcp or udp and works with link level frames. So, by running this, we are eliminating if the culprit is the network communication layer possibility.

Let us know the results.

[Vinh Nguyen_2]

Hi Mel,
Thanks for checking into this. Your suspicion of the drivers make sense, but this same NIC works fine on another L200 system. It's strange that on this C240 system, both NICs have the same PPA number (0). The 3 you saw is the num ID. Is there anyway we can assign a different PPA number for skge?

Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/0/20/0 0x0060B0D0E39C 0 UP lan0 snap0 1 ETHER Yes 119
10/0/2/0 0x00005A9F0464 0 UP skge0 3 ETHER No *

I used PPA 0 to run linkloop, there's err.

Link connectivity to LAN station: 0x000c293cf090
error: get_msg2 getmsg failed, errno = 4
-- FAILED
frames sent : 1
frames received correctly : 0
reads that timed out : 1

Thank you much.
--nguy--

[Devender Khatana]

Hi,

I too never had any opportunity to have a hands on non-HP cards with HP systems. I rather do not have a 11.00 system to check configs at present. But in any case your cards should have different PPA ID for different cards. Can you try putting it in some other slot and then give it a try to have a different PPA ID.

Pseudo part can also be a reason for the non functioning of the card.
Can you check which driver is binded to this card by
mydv101:>>lssf /dev/lan0
btlan card instance 0 ieee at address 0/0/0/0 /dev/lan0

HTH,
Devender

[Vinh Nguyen_2]

Thanks Davender,
Unfortunately there's only 1 slot that I can fit this Syskonnect NIC in. The driver that binds to this NIC is skge. Result from the lssf:

lssf /dev/skge
pseudo driver clone minor 0x0000f1 /dev/skge

lssf /dev/lan
streams cloneable pseudo driver dlpi /dev/lan

This is the info generated by ioscan for this NIC:

pseudo 0 10/0/2/0 skge CLAIMED INTERFACE PCI Ethernet (11484320)

Is there any way we can force the class from pseudo to lan?

Thanks

[Devender Khatana]

Hi,

I think this is not going to work here now. A would like to know if some one can suggest some work around for this.

So far as there is the question of this working in L2000 and not here then this is quite possible. Compatibility is a big deal and it is quite possible that one card is not supported for L1000 itself and works fine in D Class. Here allthough you are even moving card from server to workstation. I would suggest to look for some used cards which are cheaply available.

HTH,
Devender

[Florian Heigl (new acc)]

Hey,

I still wait for HP-UX drivers for my PCI-X syskonnect adapter, but from my experience syskonnect has a really, really good support, so You might want to let them know of these issues...

the address is
support@syskonnect.com

it would be great if You could post some performance numbers after it's working if time allows. I'm quite interested if the HP-UX drivers are as fast as the linux drivers.


good luck,
florian

[Vinh Nguyen_2]

Thanks Florian and Davender,
I emailed Syskonnect support for help. I'll post the workaround if they provide me one.
--nguy--

[rick jones]

As you have noticed, pinging the system locally is rather meaningless. By default, traffic to one's local IP addresses never even gets to a NIC driver, let alone NIC hardware.

I'm not sure if lanadmin "knows" about opening anything other than /dev/dlpi - it would have to know to open /dev/skge. PPA's are not unique across the system (IIRC, but could be wrong), only across the base device file.

I suspect the same would be true of linkloop, which is a very good tool to test link-level connectivity - no working IP required.

Anyway, the suggestion to get in touch with SysKonnect is definitely the correct path.

[D Block 2]

Vinh,

just my 2-cents here, have you tryed running some Kernel Debugging on your system ?

There is a way to instrument your kernel with a low-level trace program..

Also, you can start with the Streams Trace program (strace), if you know the kernel Module#, your just run: strace ALL ALL

[Vinh Nguyen_2]

Thanks all,
The response I got from SysKonnec:

The NIC is not supported on HP-UX 11.0.

The suggestion:
Upgrade to HP-UX 11.11 (64 bit) and install driver v6.17.1.3