Operating System - HP-UX
1855081 Members
4294 Online
104109 Solutions
New Discussion

Re: Interface State =DOWN, Probable Cause for State = Cable disconnect

 
Taurian
Valued Contributor

Interface State =DOWN, Probable Cause for State = Cable disconnect

 

Hi All,

 

I am getting the message when I run the command for lan1:

 

*-*---------------------------------------------------

# nwmgr -g -v -c lan1
lan1:
   Interface State =DOWN
   Probable Cause for State = Cable disconnect
   MAC Address = <MAC>
   Subsystem = iexgbe
   Interface Type = 10GBASE-KR
   Hardware Path = 0/0/0/3/0/0/1
   NMID = 2
   Feature Capabilities = Physical Interface
                          IPV4 Recv CKO
                          IPV4 Send CKO
                          VLAN Tag Offload
                          64Bit MIB Support
                          IPV4 TCP Segmentation Offload
                          UDP Multifrag CKO
   Feature Settings = Physical Interface
                      IPV4 Recv CKO
                      IPV4 Send CKO
                      VLAN Tag Offload
                      64Bit MIB Support
                      IPV4 TCP Segmentation Offload
                      UDP Multifrag CKO
   MTU = 1500
   Speed = 0 Mbps Full Duplex
      The link is down. Speed and other link state information are undefined.
      Only the configured speed is shown.

 

*-*---------------------------------------------------

 

 

The strange thing is that this is a blade enclosure with Virtual Connect cards. I can't seem to bring the lan1 up. On the adjecant blade server, the lan1 is up and working fine!

 

Please help!

 

 

Regards,

Taurian.

 

 

 

3 REPLIES 3
Torsten.
Acclaimed Contributor

Re: Interface State =DOWN, Probable Cause for State = Cable disconnect

You should double-check the vc settings, if the ports are not configured correctly, you won't get a link.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Taurian
Valued Contributor

Re: Interface State =DOWN, Probable Cause for State = Cable disconnect

 

Hi Torsten,

 

Thanks for the reply.

 

As this is a 870c server, the VC shows the port for lan1 to be "Bay 2, LOM 1". I don't understand why the port of the auxilary blade server is mapping in the VC server profile. How do I work around this?

 

 

Regards,

Taurian.

Torsten.
Acclaimed Contributor

Re: Interface State =DOWN, Probable Cause for State = Cable disconnect

>>  I don't understand why the port of the auxilary blade server is mapping in the VC server profile

 

 

Why not?

 

From the OA/VC point of view this is a single server.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!