ifconfig

[ricky_8]

Hi ALL,

Iam getting a following error after reboot and server is not coming online after that

lo0 interface:ifconfig :check plumbing error: bad file number

ANy help

[Michael Tully]

Hi,

The first thing I would be checking is whether this symbolic link exists:
/dev/lan to /dev/dlpi

If it is not, then run:
# ln -s /dev/dlpi /dev/lan

Regards
Michael

[ricky_8]

Michael,

The link is already present.Iam getting errors in rc.log for net.link and net scripts.

Never seen Bad file number ? error


Rgds,
Sajesh.

[G. Vrijhoeven]

Hi,

check the numbers ( between brackets [] ) in the /etc/rc.config.d/netconf file.

Gideon

[Sunil Sharma_1]

Hi,

You check you /etc/rc.config.d/netconf file
the interface number specified inside [] may be wrong.

Sunil

[ricky_8]

Iam not ableto configure even the lookback address on it.Gives same error Bad file name.

[Michael Duthie]

Ricky,

Do you get any further errors when starting the networking manually ? # /sbin/init.t/net start

I found a similar problem relating to a missing /dev/sad.

Fix is insf -ev

[Dietmar Konermann]

Hi!

Check this...

# lsdev -d sad
Character Block Driver Class
74 -1 sad pseudo
# lsdev -d tcp
Character Block Driver Class
79 -1 tcp pseudo

# insf -ed sad
insf: Installing special files for pseudo driver sad

# insf -ed tcp
insf: Installing special files for pseudo driver tcp

Then try to run the net.init script and post the results, if it still fails:

# sh -x /sbin/init.d/net.init start

Best regards...
Dietmar.

[ricky_8]

Mike/Dietmark/ALL,

Even tried that, but i get same error "check plumbing error :Bad File name"

rgds

[Michael Duthie]

You have me beat Ricky.

What does SAM say when you try to configure a LAN card, it sometimes give you a better error.

[Sridhar Bhaskarla]

Hi,

Do you have a "real" script call /sbin/init.d/net.init?.

What does "sh -x /sbin/init.d/net.init" give?. It should printout the debugging output.

Make sure it is not of 0 bytes size. Compare it with another server.

-Sri

[Jon Finley]

From HP
---------------------
This problem is caused by not starting /sbin/init.d/net.init before
the /sbin/init.d/net script.

HP-UX versions prior to 10.30 did not have an /sbin/init.d/net.init
startup script.
----------------------

Jon

[ricky_8]

Guys,

Thanxs a lot , but i found that the kernel was corrupt and hence rebuilt the server. Now itis ok, but dont know what made it behave like that.

Rgds,