How to unclaim a claimed lancard

[prashantm]

I have three lancards on my system and i wish to unclaim one of them can anyone tell me how can i unclaim a claimed lancard ..
here is the ouput of `ioscan -fnC lan`
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/1/2/0 iether CLAIMED INTERFACE HP PCI-X 1000Base-T Dual-port Built-in
lan 1 0/1/2/1 iether CLAIMED INTERFACE HP PCI-X 1000Base-T Dual-port Built-in
lan 2 0/2/1/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Base-T Adapter

here is the output of lanscan command
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/2/0 0x0011855F198A 0 UP lan0 snap0 1 ETHER Yes 119
0/1/2/1 0x0011855F198B 1 UP lan1 snap1 2 ETHER Yes 119
0/2/1/0 0x001321AFD6D9 2 UP lan2 snap2 3 ETHER Yes 119

[Duncan Edmonstone · Accepted solution]

>> I have three lancards on my system and i wish to unclaim one of them can anyone tell me how can i unclaim a claimed lancard ..

Why on earth would you want to do that? A 'claimed' LAN card isn't actually active in any way unless you set up a protocol stack on it in some way (such as using ifconfig for TCP/IP). Can you explain why you would want to do this?

As to *how* you would do it:

- Take the LAN card out of the system ;o)

- or in your case I guess you could remove the igelan driver from your kernel to 'unclaim' lan2 (but then you can't use it for *anything*)


HTH

Duncan

[Berd]

If you are just looking to make sure it is not usable, you could use ifconfig to take the card down or unplumb any i.p. addresses.

Berd

[Torsten.]

Hi,

once again: Why?

Looks like this is an rp4440 or rx4640 - you cannot take out the built-in card (lan0 and lan1).

Of course you can uninstall the card in slot 7 - but again, why?

An unconfigured card is not on the network ...

[rick jones]

Strictly speaking, a CLAIMED but not ifconfig'd interface can still be used to communicate over the link via link-level APIs - eg DLPI. And in fact, an unplumbed interface can have an appliction bind the IP and ARP SAPs and run its own IP stack if it so chooses.

The only way _I_ know of to cause a card to not be claimed is to remove the driver. That of course means that none of the cards driven by that driver will be claimed, which may be akin to tossing the baby out with the bathwater.

[prashantm]

Thanks all of you . . now the answer to the `Why ?`
I have to use one of the lancards for remote debugging using kwdb which requires one UNCLAIMED card so that the kwdb drivers can be installed on the target and can be used for the commincation between the kwdb host and kwdb target machine.
neways thanks again,

[Torsten.]

I read only in the docs:

"This method requires that a LAN card be installed on the target
system that can be used exclusively by KWDB."

There is nothing about "unclaimed".

[prashantm]

Please read the following from the kwdb manual

Lan kwdbctl -i lan Cell/Non cell IPF/PA â ¢ No known issues with speed of
communication.
â ¢ Requires at least one LAN card
of the system to be in
UNCLAIMED state for remote
debugging.
â ¢ Target and host if in different
subnets. Requires the comm
server to be in the same subnet as
target.

[Torsten.]

Please post your link.

[prashantm]

http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,5669,00.html

[prashantm]

http://h21007.www2.hp.com/dspp/files/unprotected/ddk/KWDB_all.pdf

[Jim Keeble]

Hi Prashantm,

First, I'm not an expert in this area, so I'm sorry if I'm off base.

I looked at the manual link you sent, and I think that what they want you to do is run the "olrad -d " . When I tried it on my system, it didn't really make the card show up as "UNCLAIMED" in ioscan, rather it powered off the slot and made the card disappear from ioscan altogether. I'm hoping the the kwdbctl command in the later steps powers up the slot as it adds the kwdb driver. I think that adding it back with olrad would simply power up the slot and allow the default driver to claim it.

Good luck! Let us know how it turns out.

[prashantm]

what you are sayin is only applicable for
kernels starting 11.31 not prior to that
kwdbctl doesnt work on 11.23