1834908 Members
2853 Online
110071 Solutions
New Discussion

lanadmin

 
martin wells_1
Advisor

lanadmin

One of our lancards is showing as down when using lanadmin -x lan1. The system is running HPUX 11i

This was working fine earlier today but I tried to connect via our ignite server and this didn't work and since then I can't get the lan up. Its showing as enablled in sam and up with ifconfig.

Is there a way to bring it up with lanadmin?

Thanks
9 REPLIES 9
Stephen Keane
Honored Contributor

Re: lanadmin

You could try

lanadmin -> lan -> reset

martin wells_1
Advisor

Re: lanadmin

I have tried reseting it but it still shows as down?

I can't get to the machine to check the cable but it was fine earlier today
Stephen Keane
Honored Contributor

Re: lanadmin

You could try linkloop to try the basic connectivity if you know/can determine the MAC address of the problem card.

martin wells_1
Advisor

Re: lanadmin

I'm getting to output below

Link connectivity to LAN station: 0x00306EF4CD9B
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message


I have never used linkloop before. Is it linkloop "macaddress"?
Stephen Keane
Honored Contributor

Re: lanadmin

Yes, as in ...

# linkloop 0x1083f9a4b2
Link connectivity to LAN station: 0x1083f9a4b2
-- OK


martin wells_1
Advisor

Re: lanadmin

I think there is a problem, if even linkloop is not working.

Thanks for your help
Stephen Keane
Honored Contributor

Re: lanadmin

Can you run linkloop on the same server as has the lan card, if that works, it indicates a cabling problem. If it doesn't it indicates more of a card problem.
Bharat Katkar
Honored Contributor

Re: lanadmin

Hi,
What does "lanscan" command report. What H/w State it is showing.

I doubt about the NIC failure...

Regards,
You need to know a lot to actually know how little you know
martin wells_1
Advisor

Re: lanadmin

Linkloop is not working on the server with the lancards and lanscan is showing all up. I think its a cable issue.

Thanks for the help!