Operating System - HP-UX
1827589 Members
3807 Online
109965 Solutions
New Discussion

ifconfig: plumb error: No such file or directory

 
SOLVED
Go to solution
dm74
New Member

ifconfig: plumb error: No such file or directory

hi,
I physically reinstall NIC from one PCI-X slot in other slot.
then start server.
# ioscan -funC lan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 2 0/1/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
lan 3 0/1/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core
#
Drivers claimed, but
# ifconfig lan2 inet 192.168.200.200 netmask \
> 255.255.255.0 broadcast 192.168.200.255 up

plumb error: No such file or directory
ifconfig: #

How change name from lan2 to lan0 and why 'plumb error', when i try up interface ?
1 REPLY 1
Ramesh S
Esteemed Contributor
Solution

Re: ifconfig: plumb error: No such file or directory

Hi

1) "plumb error: "/dev/lan" No such file or directory" is due to

The symbolic link between /dev/lan and /dev/dlpi has been lost or /dev/dlpi is
missing.

This problem can be solved by symbolically linking /dev/lan to /dev/dlpi
with the commands:

insf -e -d dlpi # recreates the /dev/dlip* file if needed
ln -s /dev/dlpi /dev/lan # recreates the missing synlink

Now run the ifconfig command...


2) To change the name from lan2 to lan0, you need to change the instance number.

Perform the following steps to change your instance numbers:

1. Create the '/usr/sbin/infile' file to contain the following
information:

path type_of_device name_reference

10/12/6 lan 2
10/4/16 lan 0

Note: This information changes the name of lan0 to lan2 and
lan2 to lan0.

2. Execute the following command:

/usr/sbin/ioinit -f /usr/sbin/infile -r

Note: At this point, your system automatically reboots. When
the system boots, it is possible that your LAN card
configuration will fail.

To resolve a LAN card failure:

Modify the '/etc/rc.config.d/netconf' file by changing
the INTERFACE_NAME[x] to reflect the new LAN interface
name. For example:

INTERFACE_NAME[2]=lan0 and INTERFACE_NAME[0]=lan2

If 'ionit' returns an error, continue with Step 3.

3. Rename the '/etc/ioconfig' and '/stand/ioconfig' files:

mv /etc/ioconfig /etc/ioconfig.old
mv /stand/ioconfig /stand/ioconfig.old

Renaming these files allows you to boot into single-user mode
and recover from your original files.

4. Reboot the system.

Your system will come up to 'ioinitrc' and prompt you with the
following message:

/etc/ioconfig is missing.
Restore it from backup or invoke '/sbin/ioinit -c' to re-create
it from the kernel.

Issue a Ctrl-D to continue your boot sequence.

5. Restore or re-create the '/etc/ioconfig' file per the
instructions in Step 4.

Execute the 'ioscan' command to view the contents of the new
'ioconfig' file.

6. Execute the following sequence of commands:

(in ioinitrc)# /sbin/ioinit -c
(in ioinitrc)# ^d

7. Use the 'infile' to make the desired changes:

(in ioinitrc)# /sbin/ioinit -f infile -r

You will receive several messages, all of which you can ignore.

Ensure that you have tested your infile before executing the
'ioinit' command.

If necessary, you can perform the following steps:

- Restore the original ioconfig.old files.
- Reboot your system.
- Re-start this process.

Thanks & Regards

Ramesh