topic Re: error with the network in Operating System - HP-UX

error with the network

Wael_4 — Sat, 14 May 2005 15:05:02 GMT

I have a problem in sam when trying to access the networking and communication > interface cards.
I got the following error:
"laninfo: Current: not found."
and then when I press ok
I got the following error
There are currently no network interface cards installed on thissystem. To add a network interface card you should refer to theinstallation manual for the applicable card and ensure that bothhardware and software installation procedures are followed. For more information, choose "Overview" from the "Help" pulldown menu."
on the other hand when I run lanscan I get the three network cards available as well when I run ioscan -funClan

what is wrong with my system, kindly help.

Regards;

Re: error with the network

Wael_4 — Sat, 14 May 2005 15:10:43 GMT

also when I run sam from /sbin and access the networking and communications > interface cards. I did not get any error messages and I can access the three network cards available on the system.
also I can connect to the system fom my workstation.

kindly help

appreciate your cooperation.
Regards;

Re: error with the network

Colin Topliss — Sat, 14 May 2005 15:11:02 GMT

Please post the output from your ioscan and lanscan.

Thanks

Col.

Re: error with the network

Wael_4 — Sat, 14 May 2005 15:14:00 GMT

the output from ioscan -funClan
"Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0
lan 2 0/4/0/0 gelan CLAIMED INTERFACE HP A4926A PCI 1000Base-Sr
/dev/gelan2
lan 1 1/0/0/0 gelan CLAIMED INTERFACE HP A4926A PCI 1000Base-Sr
/dev/gelan1"

and the output from lanscan is
"Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x001083FF6BB4 0 UP lan0 snap0 1 ETHER Yes 119
1/0/0/0 0x001083FCC3E4 1 UP lan1 snap1 2 ETHER Yes 119
0/4/0/0 0x001083FCC3D6 2 UP lan2 snap2 3 ETHER Yes 119"

Re: error with the network

Tony Scully_2 — Sat, 14 May 2005 15:18:13 GMT

Sounds like the problme is something in the environment when you sun SAM.

Are all filesystems mounted and have free space? can you post the output of the env command.

Tony

Re: error with the network

Colin Topliss — Sat, 14 May 2005 15:27:17 GMT

Odd. It should at the very least see the core I/O interface, if nothing else.

Sounds like there is a problem with SAM.

Was there anything mentioned in the SAM log?

Col

Re: error with the network

Tony Scully_2 — Sat, 14 May 2005 15:46:11 GMT

But it works OK when SAM is run form /sbin?

Something not right with the shell, session or environment maybe?

I'd like to see the output of an env cmd.

Tony

Re: error with the network

Wael_4 — Sun, 15 May 2005 01:49:28 GMT

here is the output of the env command
_=/usr/bin/env
MANPATH=/usr/share/man/%L:/usr/share/man:/usr/contrib/man/%L:/usr/contrib/man:/n
LIBRARY=/dev/scsi/c10t13d0
PATH=/usr/sbin:/opt/perl_64/bin:/usr/bin:/opt/ansic/bin:/usr/ccs/bin:/usr/contrt
COLUMNS=80
EDITOR=vi
LOGNAME=root
MAIL=/var/mail/root
ERASE=^H
SHELL=/sbin/sh
HOME=/
VA=00SG146G0066
TERM=vt100
PWD=/
TZ=WAT-3
LINES=24

Re: error with the network

Devender Khatana — Sun, 15 May 2005 03:25:44 GMT

Hi,

Yes, it is a path issue as when you do it from /sbin directory it works fine. Just add /sbin to your current path and it should be OK. It apparently appears that it can not find some commands of /sbin which are executed by SAM in background as your PATH does not include /sbin.

HTH,
Devender

Re: error with the network

Wael_4 — Sun, 15 May 2005 03:40:02 GMT

I have already add the /sbin to the PATH and actualy I got the same error after logout and login to activate the new path.

Re: error with the network

Ermin Borovac — Sun, 15 May 2005 04:20:22 GMT

Any errors in /var/sam/log/samlog?

SAM runs the following command to get the info. What happens when you run it from command line?

# /usr/sam/lbin/laninfo

Re: error with the network

Ermin Borovac — Sun, 15 May 2005 04:27:24 GMT

Also please post the output of

# netstat -ni
# ifconfig lan0
# ifconfig lan1
# ifconfig lan2

Re: error with the network

Wael_4 — Sun, 15 May 2005 04:41:03 GMT

this is the output in samlog
"Executing the following command:\Claninfo -i\C
@!@2@1116100341@0
Command completed with exit status 127.
@!@16@1116100341@0
Task: "Get ifconfig(1M) network interfaces." failed. The return code was 127.
Standard error contains "laninfo: Current: not found.^A".
@!@8@1116100341@0"
***************
the output for ifconfig
"ifconfig lan0
lan0: flags=843
inet 172.16.3.22 netmask ffffff00 broadcast 172.16.3.255
ifconfig lan1
lan1: flags=1843
inet 172.16.2.22 netmask ffffff00 broadcast 172.16.2.255

ifconfig lan2
lan2: flags=1843
inet 172.16.1.22 netmask ffffff00 broadcast 172.16.1.255
********************

netstat -ni
"netstat -ni
Name Mtu Network Address Ipkts Opkts
lan2 1500 172.16.1.0 172.16.1.22 2 2
lan1 1500 172.16.2.0 172.16.2.22 1933 1607
lan0 1500 172.16.3.0 172.16.3.22 2501 2264
lo0 4136 127.0.0.0 127.0.0.1 4987 4987"

*************

Regards;

Re: error with the network

Wael_4 — Sun, 15 May 2005 04:44:54 GMT

I discovered something that the problem happens only when I run sam from "/" and when I run it from any other folder or directory it's working without any problem

Re: error with the network

Tony Scully_2 — Sun, 15 May 2005 07:15:50 GMT

That seems to suggest that SAM has an issue with / directory. Maybe sam is trying to write some temp files there, and is unable to -- surprised that there is nothing logged in the sam logs though.

Do you have a $TMPDIR defined?

Maybe try export TMPDIR=/var/tmp and then re-run sam from /

Tony

Re: error with the network

Ermin Borovac — Sun, 15 May 2005 08:02:05 GMT

For some reason /usr/sam/lbin/laninfo is failing.

I suggest that you trace it with 'tusc'. You can get tusc from

ftp://ftp.cup.hp.com/dist/networking/tools/tusc..shar

Then run it as

# tusc -fv -o tusc.log /usr/sam/lbin/laninfo

Examine tusc.log for possible clues.