HPE Aruba Networking & ProVision-based
1833309 Members
2848 Online
110051 Solutions
New Discussion

Re: Procurve 5412zl disabled port

 
freezstyle
Occasional Visitor

Procurve 5412zl disabled port

Hello everybody! I have some mysterious problem with my switch 5412zl, everything works fine and there is no any serious problems, BUT there is one port which is disabled and it doesn't want to enable. It is down and that is all, nothing helps me:

1. interface c6

          enable

2. Firstly I thought the problem is in my server that is connected to this port, but it works in other ports

3. I have connected my laptop to this port but the port is down

4. There was an old software K.14.41, I upgrade it till K.15.13.0003. During reboot self-test said nothing to me, nothing in logs and nothing during reboot.

5. During self-test LED lighted on this port, but than it went down

6. speed-duplex, mdi/mdix is auto and I dont change anything

 

Can anyboby help me to resolve this problem

2 REPLIES 2
Richard Litchfield
Respected Contributor

Re: Procurve 5412zl disabled port

Do a "sh logging -r" to show a list of log entries with the latest on top. That will possibly tell you what the switch is doing on that port.

 

Also do a "sh run int <port>" to show all the details of a specific port config. You may have some security settings blocking the port.

 

interface B20
   unknown-vlans disable
   no power-over-ethernet
   untagged vlan 1
   filter connection-rate throttle
   port-security learn-mode static action send-alarm mac-address 4c72b9-e64c89
   no snmp-server enable traps link-change
   spanning-tree admin-edge-port
   exit

 

John Gelten
Regular Advisor

Re: Procurve 5412zl disabled port

If this is still an issue...

That sounds like a hardware-defect to me. If  you did an SW-upgrade with reboot, and there is nothing in the logs, it is not a configuration or software issue. It's like the switch is just not aware you connected a cable to this interface.

It happened to me once, on careful examination we noticed one of the eight pins in the RJ45 connector was just missing; probably broken off at some point. The symptoms were like in your case.