1847413 Members
2843 Online
110264 Solutions
New Discussion

Re: plumb error

 
SOLVED
Go to solution
mariusz grabowski
New Member

plumb error

Hello,
I have this strange problem:

I have a k380 with hp-ux 11.0 OS on it.
when I try to configure my LAN interface, I have a response like:

ifconfig: plumb error: no such file or directory

this problem is about lan2 (I have another lan interface, which reserved lan0 and lan1), the one on core I/O, which is my primary lan interface.

I cannot configure this interface, although linkloop, lanscan and ioscan show, that's everything's just fine.

I also checked /sbin/rc2.d/net and /sbin/rc2.d/net.init. The second one stops on ifconfig (the reason is like before - no such file or directory) , and the second one starts ok.

while the primary lan interface has 2nd number, I've changed infos in /etc/rc.config.d/netconf from 0 (which is default value) to 2.

what could be wrong?
thanks for your assitance!

Mariusz Grabowski
try until you're done
5 REPLIES 5
Alex Glennie
Honored Contributor
Solution

Re: plumb error

things to check :

Symbolically linked /dev/lan to /dev/dlpi:
ln -s /dev/dlpi /dev/lan

Kofi ARTHIABAH
Honored Contributor

Re: plumb error

Actually, you only need to plumb the first card! all other cards need not be plumbed. so make sure that lan0 is plumbed and you would not need to plumb lan2. However, I would suggest the following:

first, you might want to check that you have loaded any drivers you need for that card.

next try running:

insf -e

next do an ioscan -fnC lan and ensure that the SW state is CLAIMED... if it is not - that is an indication that the drivers have not been loaded.

nothing wrong with me that a few lines of code cannot fix!
Devbinder Singh Marway
Valued Contributor

Re: plumb error

Matthew Cherry
New Member

Re: plumb error

This problem may be caused by not starting /sbin/init.d/net.init before
the /sbin/init.d/net script
rick jones
Honored Contributor

Re: plumb error

kofi -

i'm not so sure about the only having to plumb the first interface. i suspect you are thinking about only having to plumb what the transport considers the physical interface - eg lan0:0, lan1:0, etc.

the additional logical (alias) interfaces do not need to be plumbed (lan0:1, lan0:2, etc)
there is no rest for the wicked yet the virtuous have no pillows