We have two Cisco 2602E APs and one Cisco 3602E AP deployed at a location in China. They are connected to an HP ProCurve 2910al PoE switch.
The 3602E powers up fine when the switch is rebooted (i.e. power loss, they have rolling blackouts in this city) but the 2602E APs both require someone pressing the mode button on them before they power on.
Before the mode button is pressed, the HP switch shows no device on the ports and no power being pulled on them. The APs have no LED activity, they appear off. When someone presses the mode button they mysteriously power on. The HP switch now shows power draw and their LED turns on.
The cable runs to them are around 200'. The switch is PoE+ so it has plenty of wattage to cover any loss over the distance. The 3602 is on a shorter run and has no issues.
We have a second facility in China with the same setup and they do not have this issue. All APs have the same boot loader and IOS per model (i.e. the 2602Es in each site have the same boot loader and IOS rev).
This same issue occurs when using a Cisco 3560C PoE+ switch and the existing cabling setup.
As this is in China, my ability to troubleshoot is a bit limited right now. I am hoping someone has experienced a similar problem and can point me in the right direction. This wouldn't be such a big issue if the APs weren't mounted in a factory ceiling that requires a lift to get to them for pressing the mode button.
What could be causing the 2602Es to not power up with the switch?
Best Answer
We solved this with new cable runs using STP instead of UTP. No more issues with POE to the APs.
First time we've needed STP and we can't find anything that would cause the interference with the run.