Procurve 2610-24-PWR no power to PD

[HGIS]

We have an Procurve 2610-24-PWR switch where Mitel IP Phone's are connected to.
It happend twice that the switch stopt providing power to the Phone's. In logging i see "port 1 is now off-line" and "port 1 PD Removed." Nothing more nothing less. I can connect to the switch using telnet, but using the webbrowser it gets stuck on loading Java.
I have the firware release: R.11.25 loaded.
After a reboot the switch works normal again!

Who has some advice? Is the switch defect or is something else wrong??

Thanks in advance for the answers!!

Maarten

P.S. This thread has been moved from Switches, Hubs, Modems (Legacy ITRC forum) to ProCurve / ProVision-Based. -HP Forum Moderator

[Mohammed Faiz]

Hi,

We're using a 2610-PWR with Mitel phones and haven't had any issues like this (although we are on R.11.30 at the moment).
It looks like you're just losing the link to the phones (rather than a specific PoE problem).
Does it happen to all of the phones at the same time?

[Shadow13]

Can you post your network topology, aslo how many PDs are connected to the switch ?

Also are you connecting directly or through patch panel ? if through patch panel try connecting the phone directly and monitor the status.

Does this happen to all the phones or only to this one ?

can you post the show loggin -a command output.

[HGIS]

Sorry for the late reaction!!

We have 12 Mitel phone's connected to this switch! When the error happens they al go down at the same time!! Only the power LED is ON from the switch.

The topoly is very straight forward. We have a seperate IP-Subnet for the Mitel VoIP environment. There are 4 HP Procurve switches in that network. 3 2610-24-PWR and 1 2610-48-PWR. The switches are uplinked via copper and fiber (another building).

I will post the log info here, but i think it is flushed since the crash / reboot:

---- Event Log listing: Events Since Boot ----
I 02/13/90 02:16:05 system: --------------------------------------------------
I 02/13/90 02:16:05 system: System went down: 02/13/90 02:15:44
I 02/13/90 02:16:05 system: Operator reboot from TELNET session.
I 02/13/90 02:16:14 udpf: DHCP relay agent feature enabled
I 02/13/90 02:16:14 stack: Stack Protocol enabled
I 02/13/90 02:16:14 tftp: Enable succeeded
I 02/13/90 02:16:14 system: System Booted.
I 02/13/90 02:16:14 cdp: CDP enabled
I 02/13/90 02:16:14 lldp: LLDP - enabled
I 02/13/90 02:16:17 vlan: VLAN1-(VoIP) virtual LAN enabled
I 02/13/90 02:16:17 ports: port 25 is now on-line
I 02/13/90 02:16:17 vlan: VLAN2-(DATA) virtual LAN enabled
I 02/13/90 02:16:17 ports: port 26 is now on-line
I 02/13/90 02:16:17 ip: VLAN1-(VoIP): network enabled on 10.31.40.4
I 02/13/90 02:16:24 ports: port 1 PD Detected.
I 02/13/90 02:16:24 ports: port 1 Applying Power to PD.
I 02/13/90 02:16:24 ports: port 2 PD Detected.
W 02/13/90 02:16:24 ports: port 2 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:25 ports: port 3 PD Detected.
W 02/13/90 02:16:25 ports: port 3 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:25 ports: port 4 PD Detected.
W 02/13/90 02:16:25 ports: port 4 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:25 ports: port 5 PD Detected.
W 02/13/90 02:16:25 ports: port 5 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:25 ports: port 6 PD Detected.
W 02/13/90 02:16:25 ports: port 6 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:25 ports: port 7 PD Detected.
W 02/13/90 02:16:25 ports: port 7 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:25 ports: port 8 PD Detected.
W 02/13/90 02:16:25 ports: port 8 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:25 ports: port 9 PD Detected.
W 02/13/90 02:16:25 ports: port 9 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:26 ports: port 10 PD Detected.
W 02/13/90 02:16:26 ports: port 10 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:26 ports: port 11 PD Detected.
W 02/13/90 02:16:26 ports: port 11 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:26 ports: port 12 PD Detected.
W 02/13/90 02:16:26 ports: port 12 PD Denied power due to insufficient power
allocation.
I 02/13/90 02:16:26 ports: port 2 PD Detected.
I 02/13/90 02:16:26 ports: port 2 Applying Power to PD.
I 02/13/90 02:16:27 ports: port 3 PD Detected.
I 02/13/90 02:16:27 ports: port 3 Applying Power to PD.
I 02/13/90 02:16:27 ports: port 4 PD Detected.
I 02/13/90 02:16:27 ports: port 4 Applying Power to PD.
I 02/13/90 02:16:27 ports: port 5 PD Detected.
I 02/13/90 02:16:27 ports: port 5 Applying Power to PD.
I 02/13/90 02:16:27 ports: port 6 PD Detected.
I 02/13/90 02:16:27 ports: port 6 Applying Power to PD.
I 02/13/90 02:16:27 ports: port 1 is now on-line
I 02/13/90 02:16:28 ports: port 2 is now on-line
I 02/13/90 02:16:28 ports: port 7 PD Detected.
I 02/13/90 02:16:28 ports: port 7 Applying Power to PD.
I 02/13/90 02:16:28 ports: port 8 PD Detected.
I 02/13/90 02:16:28 ports: port 8 Applying Power to PD.
I 02/13/90 02:16:28 ports: port 3 is now on-line
I 02/13/90 02:16:29 ports: port 9 PD Detected.
I 02/13/90 02:16:29 ports: port 9 Applying Power to PD.
I 02/13/90 02:16:29 ports: port 10 PD Detected.
I 02/13/90 02:16:29 ports: port 10 Applying Power to PD.
I 02/13/90 02:16:29 ports: port 4 is now on-line
I 02/13/90 02:16:29 ports: port 5 is now on-line
I 02/13/90 02:16:29 ports: port 6 is now on-line
I 02/13/90 02:16:30 ports: port 7 is now on-line
I 02/13/90 02:16:30 ports: port 11 PD Detected.
I 02/13/90 02:16:30 ports: port 11 Applying Power to PD.
I 02/13/90 02:16:30 ports: port 8 is now on-line
I 02/13/90 02:16:31 ports: port 12 PD Detected.
I 02/13/90 02:16:31 ports: port 12 Applying Power to PD.
I 02/13/90 02:16:31 ports: port 9 is now on-line
I 02/13/90 02:16:31 ports: port 10 is now on-line
I 02/13/90 02:16:31 ports: port 11 is now on-line
I 02/13/90 02:16:32 ports: port 12 is now on-line
I 02/13/90 02:30:14 mgr: SME TELNET from 10.31.31.130 - MANAGER Mode
I 02/13/90 02:35:40 mgr: SME TELNET from 10.31.31.130 - MANAGER Mode
I 02/18/90 01:44:05 mgr: SME TELNET from 10.31.31.130 - MANAGER Mode
I 02/18/90 01:52:58 mgr: SME TELNET from 10.31.31.130 - MANAGER Mode
I 02/18/90 01:53:35 mgr: SME TELNET from 10.31.31.130 - MANAGER Mode
---- Bottom of Log : Events Listed = 77 ----


ps: The date / time isn't set correct.... :-( I have to do this....

Maarten

[HGIS]

@Shadow13
The phone's are connected via a patch panel. Once the error happens again, i will try to connect a phone directly and will see if it works.

Can it be a short circuit somewhere in the wiring?

Maarten

[Mohammed Faiz]

Did you use a "show log -a" command (it may be able to pull out log entries that occurred prior to the reboot)?

[Shadow13]

try to test using direct cable to the switch maybe the issue is with the patch panel,

also try to upgrade to the latest firmware it will be better actully for you.

what about normal devices like pcs do they get disconnected or working normaly ?

[HGIS]

Oke, thanks for the replies....
The storie continues.
Yesterday the 2610-48-PWR had a the problem. But this time it wasn't the whole switch but only port 11 until 24. Port 25 till 52 where working normal!! What i did:
- Mitel phone direct on port 10, result no power!
- Notebook on port 9, result: connected
- Notebook on port 10, result: connected
- Removed patches from port 11 until 24, result: no change
- Mitel phone direct on port 12, result: no power
Conclusion, i can't restore the function on port 11 until 24 withour rebooting. So i toke also the chance to upgrade the firmware to version R.11.30.
I'm really puzzeld what is causing this and how i can prevent this from happening.
See in the attachement a "show log -a"

Thanks in advance form helping me!

Maarten

[Shadow13]

you said you only have 12 phones connected but from the logs i think they are more can you confirm.

also issue the command #show power
and post the output here plz

[Shadow13]

also issue the command
#no interface all power

then

#interface all power

these steps will power cycle the poe option on the ports

[HGIS]

@shadow13
My previous post was another switch, an 48 port. On that one are more ports in use.

"show power" on the 2610-PWR-48:
Status and Counters - System Power Status

Pre-standard Detect : Off
Maximum Power : 406 W Operational Status : On
Power In Use : 119 W +/- 6 W Usage Threshold (%) : 80

"show power" on the 2610-PWR-24:
Status and Counters - System Power Status

Pre-standard Detect : Off
Maximum Power : 406 W Operational Status : On
Power In Use : 41 W +/- 6 W Usage Threshold (%) : 80


Thanks for the tip for shutdown the power and then re-enabeling it!!

Maarten

[Shadow13]

if the issue continue i would suggest contacting your region HP Support to get this sorted out, for now try to give the ports that are providing power a high priority use the below commands
#interface ... Power critical

Or something like that am not sure about the command

[hakancicekci]

Dear HGIS we have same problem.
Did you solve it?
We did try to upgrade latest firmware but it did not work

[Jay Cardin]

I can confirm the exact same problem has bit me several times.
I've replaced the switch (2610-48-PWR) twice and the problem continues. This lead me to think that the problem was environmental.
We aren't using Mitel but are using ShoreTel phones.

Procurve support had no idea because the logs didn't show anything and a reboot fixed it for a few days.
The tier-2 guys did say that the 2610-48-PWR has two PoE controllers and that it seems that something was causing one of the controllers to shutdown. Their only suggestion was to try to remove the phones one at a time to isolate a possible defective phone. Because the shutdowns seemed random, it didn't seem feasible.

We use the R.11.30 firmware and it's still an issue.

For us, the resolution was to split the load from a single 2610-48-PWR to two 2610's.

[RogerOval]

Hi.

I know this topic is a few months old, but i have also just experienced the same issue.

HP Procurve 48 port POE, running Avaya IP handsets powered over the POE. They draw 3W each.

The switch logs show it has stopped supplying power to 11 ports randomly, all at the same second this afternoon.

The other ports appear fine (not all 48 are in use anyway, so maybe 20 POE-active ones which are still working fine).

Very odd, and irritating that the logs don't give any clues.

We're running v11.30

[cenk sasmaztin]

hi

please test this command

config)#power pre-std-detect

[TSHERMAN]

I am experiencuing the same issue,  HP 2610-48-PoE Switch which shows the following:

Status and Counters - System Power Status

Pre-standard Detect : Off
Maximum Power : 406 W Operational Status : On
Power In Use : 93 W +/- 6 W Usage Threshold (%) : 80

The show tech is full of the following for a random selection of ports:

PD Denied power due to insufficient power

The denied count is up on said ports; it doesn't seem to be any particular phone model, we run Avaya 1608 and 1616.

All of my phones are Class 2, so based on the specs for each phone and quantities I have the worst case is 294.13w which is well short of the max 406w on my switch.

I am running firmware R.11.70 and the newest available is R.11.72 which doesn't have any power fixes according to the release notes.  

So far this has only happened once, but it is really irratating for users and results in dropped calls.  Anyone find any other info on this from HP or otherwise?

[Network-user]

We have the exact same issue with ramdom ports "Denied power due to insufficient power allocation" at a givin time. Class 2 phones

It is happening 2 to 3 times a month now.

Has anyone found the root cause.?

We do have some of the same switches not given errors with POE cables to RPS units.

Wondering if we need to supply RPS to all ..

[John Gelten]

A few years ago, there has been a firmware-release that included a wipe-and-flash routine for the PoE-controller(s) of these switches. During the first boot with this firmware, it did an extra boot-cycle to flash the firmware on the PoE-controller(s). Ports 1-24 are on one PoE-controller, and ports 25-48 (on te 48-port model obviously) are on the second PoE-controller.

After booting with this special version, you should load a recent one.

We had a lot of issues at one customer with a large installed-base of 2610-48-PWR switches, when they started implementing VoIP. After a one-time flash with this 'special version', we never had any PoE-issues again.

[ktaber]

Anyone get any further with this? I have a 2610-48-PWR running software 11.98 and my switch refuses to power access points that are 802.3af compliant. There are not that many PoE devices on this switch, so I know there is more than enough power.