High collisons on unconfigured built-in LAN card

[Penni Nussbaum]

This is a K400 11.0 system. The built in lan card is not configured (see below). However, Glance is showing a high rate of collsions on this interface. How is this possible? How do I stop it?




Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
10/16/8 0x100090CEDDE6 4 UP lan4 1 802.5 Yes 119
8/0/1/0 0x0010831856AE 5 UP lan5 2 FDDI Yes 119
10/12/6 0x080009ADEC90 3 UP lan3 snap3 3 ETHER Yes 119

ifconfig lan3
ifconfig: no such interface

[harry d brown jr]

Can you post the output from:

lanscan -v

and

ls -l /dev/lan*

thanks,


live free or die
harry

[Penni Nussbaum]

root@whdist [/] # lanscan -v
-------------------------------------------------------------------------------
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
10/16/8 0x100090CEDDE6 4 UP lan4 1 802.5 Yes 119

Extended Station LLC Encapsulation
Address Methods
0x100090CEDDE6 IEEE SNAP

Driver Specific Information
token2
-------------------------------------------------------------------------------
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/0/1/0 0x0010831856AE 5 UP lan5 2 FDDI Yes 119

Extended Station LLC Encapsulation
Address Methods
0x0010831856AE IEEE SNAP

Driver Specific Information
fddi3
-------------------------------------------------------------------------------
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
10/12/6 0x080009ADEC90 3 UP lan3 snap3 3 ETHER Yes 119

Extended Station LLC Encapsulation
Address Methods
0x080009ADEC90 IEEE HPEXTIEEE SNAP ETHER NOVELL

Driver Specific Information
lan2
-------------------------------------------------------------------------------
root@whdist [/] # ls -l /dev/lan*
lrwxr-xr-x 1 root sys 9 Jul 6 2001 /dev/lan@ -> /dev/dlpi
crw-rw-rw- 1 bin bin 52 0x030000 Jun 10 1996 /dev/lan3
crw-rw-rw- 1 bin bin 103 0x040000 Oct 13 01:38 /dev/lan4
crw-r--r-- 1 bin bin 115 0x050000 Dec 4 20:11 /dev/lan5

[Wim Rombauts]

It doesn't make a difference if your LAN card is configured or not. lanscan shows it is UP, and that's what matters.

As soon as the hardware is up, the system can detect traffic on that interface.

Is there a cable connected to thatinterface ?
Does "netstat -r" show a lot of coomunication on that lan card ?

[harry d brown jr]

Penni,

If you can reboot the machine rather painlessly, then what you can do is remove the "lan2" driver from the kernel via sam (turn it off).

live free or die
harry

[Penni Nussbaum]

Wim,
netstat -r does not show the interface since it is not configured.



William,
Are you saying until I can remove the lan2 drive from the kernel, OI have to live with these collissions. What if I wanted to use the interface in the future, would it still have collisions?

[harry d brown jr]

penni,

You can remove the driver from the kernel, but it requires a reboot.

later when you want to use it, just add it back to the kernel.

live free or die
harry

[Penni Nussbaum]

Harry,
O.K., I guess I'll have to remove the driver from the kernel, but it still doesn't explain why I have excessive collisions. Is excessive collisions normal for a lan card that is not configured?

[harry d brown jr]

Penni,

If it does not have a lan cable plugged into it, then yes it is unusual. You might want to have HP do some replacements.

live free or die
harry