lan1/lan2 is in UNCLAIMED state.

[Narendra Thapa]

Hi,
I have March 09 11.31 in one of my hp node was it was hard rebooted and there after lan1 and lan2 are in UNCLAIMED state.

(# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/2/0 0x0014C21063A6 0 UP lan0 snap0 1 ETHER Yes 119


# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/1/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core
lan 1 0/4/1/0 iether UNCLAIMED UNKNOWN PCI-X Ethernet (80861079)
lan 2 0/4/1/1 iether UNCLAIMED UNKNOWN PCI-X Ethernet (80861079)


What shall I try to get it back in claimed state so that I can start using lan1/lan2 again.

It seems to be some driver issue but still I want some concrete steps to get it back.

Thanks in advance.

[Suraj K Sankari]

Hi,

>>What shall I try to get it back in claimed state so that I can start using lan1/lan2 again

Did you tried "insf -e" ?

if not try it and check with "ioscan -fnC lan"

Suraj

[Narendra Thapa]

I already tried insf -e and ioscan -fnC lan.
Still I am not getting my lan1/lan2 in claimed state.
I feel that there may not be a driver issue.
as driver is in configured state.
SNIP:

# what /stand/vmunix |grep ietherkwdbdev_iether.c $Date: 2008/11/24 05:09:11 $Revision: r11.31/9 PATCH_11.31 (B11.31.0903LR)

[likid0]

You can allways check:
swlist -l fileset -a state IEther-00

Your actual version:
swlist -l bundle | grep -i IEther-00

And look for a newer version of the IETther-00 driver, just in case you cards are not supported by the current driver you have installed and need a new one

[likid0 · Accepted solution]

Looking at your version, looks like your iether driver version is up to date.

check if the filesets are in configured state, if they are you should be ready to go on the software side.

maybe a HDW issue ?

you could try with stm and check the HDW status.
remove the devices, poweroff with olrad the nic, poweron, re-scan and insf .

[Steven E. Protter]

Shalom,

Unclaimed almost always points to a hardware problem.

I would run cstm mstm or xstm try to test the hardware.

If that fails I would remove and reinstall the igelan software.

This is a certified LAN card is it not?

SEP

[TTr]

> it was hard rebooted...

Was anything removed from the kernel and was a new kernel built before the rebooting? Check the date of /stand/vmunix and /stand/vmunix.prev. It is possible that a driver was removed from the kernel and a new kernel was built but the server was never rebooted until the "hard reboot" time. Then of course the new kernel does not have the lan driver it needs.
Also what kind of LAN card is it? The part number should be on the card's slot cover. You need to have the card's part number so that you can check which LAN fileset is needed to support it.

[Narendra Thapa]

Hi All,
thanks for your time and your valuable comments, I was able to solve the issue as this was a hardware issue (LAN card was faulty) I changed the LAN card and I am able to see lan1 and lan2 now.

Thanks again for all your valuable comments.

[Narendra Thapa]

Closing the thread as this issue is resolved now.

Solution: changed the LAN card.


Thanks again for all your comments, its really helped me a lot.

[Steven E. Protter]

Shalom,

If the answers were helpful ( I think mine was right on) please assign points to your responses. That is how people who find the thread six months or a year down the road rate the answers.

SEP