Campus Switching and Routing

Reply
Occasional Contributor I

Issues with Aruba AP-205 on HP ProCurve 2910al

I am having issues with Aruba access points on HP ProCurve 2910al-48G-POE+ switches.  I am not sure if this is a power issue or what..

 

Here's the scenario... I have many 2910al's floating around and all of my AP-105's work perfect on them.  We recently did some network upgrades in other areas to 5406R ZL2 and 5412R ZL2 switches. I have installed multiple variations of access points on those switches (AP-115's, AP-105's, AP-205's) and everything works great.  

 

Using the same config on my 2910al's everything works fine except the AP-205's.  They get stuck with the power light flashing and the network light flashing. Looking at the LED paterns it seems it is stuck in bootloop. If plug the same access points in 5400 series switch they work great.

 

I noticed that they run about 8.9W on the 5400 series chasis, but only around 6W on the 2910al's.  I tried adjusting the power settings, but have had no luck. I also notice the radios never come on so that could be why they aren't drawing as much.

 

I have also noticed that the AP's never even hit our DHCP server while all of the AP-105's do, it's so strange.  

 

I have tried this on multilpe switches and the outcome is always the same. Oh and they work perfectly fine on 2920al switches..  

 

I do have a ticket in with Aruba and HP.. But any help would be greatly appreciated.

 

 

Aruba Employee

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

Greetings!

 

My first two recommendations would be to check the event log on the switch ('show log -r') for any unusual entries related to the AP port and PoE status, and verifying that you are running the latest available switch software; this would be W.15.14.0013 (downloadable from the My Networking portal).

 

The 2910al is capable of providing up to 30W per port, so it shouldn't be a power availability issue (the 205 has a worst-case draw of 12.5W).  It would be helpful to see if the switch is logging anything unusual when an AP is connected, so we can determine where to troubleshoot from there.

 



Matthew Fern | Technical Marketing Engineer, Campus Networking
Aruba, a Hewlett Packard Enterprise Company
Occasional Contributor I

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

Here is the log information you requested.  It appears I am getting the same LLDP error on 5406R ZL2 as well. 

 

Ports 6,7,8 are the AP-205's.  Ports 1-5 are the working AP-105's.

 

Does it use LLDP to determine the power requirements?


---- Reverse event Log listing: Events Since Boot ----
I 06/27/16 11:51:00 00828 lldp: AM1: PVID mismatch on port A8(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:59 00828 lldp: AM1: PVID mismatch on port A7(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:59 00828 lldp: AM1: PVID mismatch on port A10(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:59 00828 lldp: AM1: PVID mismatch on port A9(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:35 00828 lldp: AM1: PVID mismatch on port A4(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:33 00828 lldp: AM1: PVID mismatch on port A1(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:32 00828 lldp: AM1: PVID mismatch on port A5(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:32 00828 lldp: AM1: PVID mismatch on port A2(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:32 00828 lldp: AM1: PVID mismatch on port A3(VID 225)with peer
device port XXXXX (VID unknown)(1)
I 06/27/16 11:50:32 00828 lldp: AM1: PVID mismatch on port A6(VID 225)with peer
device port XXXXX VID unknown)(1)
I 06/27/16 11:50:13 00076 ports: AM1: port A8 is now on-line
I 06/27/16 11:50:12 00076 ports: AM1: port A9 is now on-line
I 06/27/16 11:50:12 00076 ports: AM1: port A10 is now on-line
I 06/27/16 11:50:11 00076 ports: AM1: port A7 is now on-line
I 06/27/16 11:50:10 00077 ports: AM1: port A8 is now off-line
I 06/27/16 11:50:09 00077 ports: AM1: port A9 is now off-line
I 06/27/16 11:50:09 00077 ports: AM1: port A10 is now off-line
I 06/27/16 11:50:08 00077 ports: AM1: port A7 is now off-line
I 06/27/16 11:49:47 00076 ports: AM1: port A2 is now on-line
I 06/27/16 11:49:47 00076 ports: AM1: port A1 is now on-line
I 06/27/16 11:49:47 00076 ports: AM1: port A5 is now on-line
I 06/27/16 11:49:47 00076 ports: AM1: port A3 is now on-line
I 06/27/16 11:49:46 00076 ports: AM1: port A4 is now on-line
I 06/27/16 11:49:46 00076 ports: AM1: port A6 is now on-line
I 06/27/16 11:49:45 00077 ports: AM1: port A1 is now off-line
I 06/27/16 11:49:44 00077 ports: AM1: port A2 is now off-line
I 06/27/16 11:49:44 00077 ports: AM1: port A5 is now off-line
I 06/27/16 11:49:44 00077 ports: AM1: port A3 is now off-line
I 06/27/16 11:49:44 00077 ports: AM1: port A6 is now off-line
I 06/27/16 11:49:44 00077 ports: AM1: port A4 is now off-line
I 06/27/16 11:49:16 00076 ports: AM1: port A1 is now on-line
I 06/27/16 11:49:15 00076 ports: AM1: port A6 is now on-line
I 06/27/16 11:49:15 00076 ports: AM1: port A5 is now on-line
I 06/27/16 11:49:15 00076 ports: AM1: port A3 is now on-line
I 06/27/16 11:49:15 00076 ports: AM1: port A2 is now on-line
I 06/27/16 11:49:15 00076 ports: AM1: port A4 is now on-line
I 06/27/16 11:49:00 00076 ports: AM1: port A8 is now on-line
I 06/27/16 11:49:00 00076 ports: AM1: port A10 is now on-line
I 06/27/16 11:49:00 00076 ports: AM1: port A9 is now on-line
I 06/27/16 11:49:00 00076 ports: AM1: port A7 is now on-line
I 06/27/16 11:48:58 00561 ports: AM1: port A1 Applying Power to PD.
I 06/27/16 11:48:58 00560 ports: AM1: port A1 PD Detected.
I 06/27/16 11:48:57 00561 ports: AM1: port A10 Applying Power to PD.
I 06/27/16 11:48:57 00560 ports: AM1: port A10 PD Detected.
I 06/27/16 11:48:57 00561 ports: AM1: port A8 Applying Power to PD.
I 06/27/16 11:48:57 00560 ports: AM1: port A8 PD Detected.
I 06/27/16 11:48:57 00561 ports: AM1: port A5 Applying Power to PD.
I 06/27/16 11:48:57 00560 ports: AM1: port A5 PD Detected.
I 06/27/16 11:48:57 00561 ports: AM1: port A3 Applying Power to PD.
I 06/27/16 11:48:57 00560 ports: AM1: port A3 PD Detected.
I 06/27/16 11:48:57 00561 ports: AM1: port A2 Applying Power to PD.
I 06/27/16 11:48:57 00560 ports: AM1: port A2 PD Detected.
I 06/27/16 11:48:56 00561 ports: AM1: port A9 Applying Power to PD.
I 06/27/16 11:48:56 00560 ports: AM1: port A9 PD Detected.
I 06/27/16 11:48:56 00561 ports: AM1: port A7 Applying Power to PD.
I 06/27/16 11:48:56 00560 ports: AM1: port A7 PD Detected.
I 06/27/16 11:48:56 00561 ports: AM1: port A6 Applying Power to PD.
I 06/27/16 11:48:56 00560 ports: AM1: port A6 PD Detected.
I 06/27/16 11:48:56 00561 ports: AM1: port A4 Applying Power to PD.
I 06/27/16 11:48:56 00560 ports: AM1: port A4 PD Detected.
I 06/27/16 11:48:48 00076 ports: AM1: port A20 is now on-line
I 06/27/16 11:48:48 00803 usb: AM1: port enabled.
I 06/27/16 11:48:47 00001 vlan: AM1: XXXX virtual LAN enabled
I 06/27/16 11:48:47 00001 vlan: AM1: XXXX virtual LAN enabled
I 06/27/16 11:48:47 00001 vlan: AM1: XXXX virtual LAN enabled
I 06/27/16 11:48:47 00001 vlan: AM1: XXXX virtual LAN enabled
I 06/27/16 11:48:47 00001 vlan: AM1: XXXX virtual LAN enabled
I 06/27/16 11:48:47 00001 vlan: AM1: XXXX virtual LAN enabled
I 06/27/16 11:48:47 00001 vlan: AM1: XXXX virtual LAN enabled
I 06/27/16 11:48:47 00076 ports: AM1: port A22 is now on-line
I 06/27/16 11:48:44 00422 chassis: AM1: Slot A Ready
I 06/27/16 11:48:30 00376 chassis: AM1: Slot A Download Complete
I 06/27/16 11:48:29 00375 chassis: AM1: Slot A Downloading
I 06/27/16 11:48:21 00928 chassis: AM1: Fabric 1 active
I 06/27/16 11:48:19 03401 crypto: AM1: Function POWER UP passed selftest.
I 06/27/16 11:48:19 03803 chassis: AM1: System Self test completed on Master
I 06/27/16 11:48:18 00068 chassis: AM1: Slot A Inserted
I 06/27/16 11:48:18 03802 chassis: AM1: System Self test started on Master
I 06/27/16 11:48:18 00260 system: AM1: Mgmt Module 1 Active
I 06/27/16 11:48:18 00066 system: AM1: Mgmt Module 1 Booted
I 06/27/16 11:48:18 04260 dhcp-server: AM1: Conflict-logging is disabled
I 06/27/16 11:48:18 04257 dhcp-server: AM1: Ping-check configured with retry
count = 2, timeout = 1
I 06/27/16 11:48:18 02012 mtm: AM1: A non-multicast client: Non-Mcast client Op,
is registered with client ID: 3
I 06/27/16 11:48:18 00410 SNTP: AM1: Client is enabled.
I 06/27/16 11:48:18 02633 SNTP: AM1: Client authentication is disabled.
I 06/27/16 11:48:18 00688 lldp: AM1: LLDP - enabled
I 06/27/16 11:48:18 00417 cdp: AM1: CDP enabled
I 06/27/16 11:48:18 04695 auth: AM1: Command authorization method set to none.
I 06/27/16 11:48:17 00433 ssh: AM1: Ssh server enabled
I 06/27/16 11:48:17 02604 dhcpv6r: AM1: Inclusion of client link-layer address
in DHCPv6 relay message is disabled.
I 06/27/16 11:48:17 02638 srcip: AM1: RADIUS oper policy for IPv6 is 'outgoing
interface'
I 06/27/16 11:48:17 02637 srcip: AM1: RADIUS admin policy for IPv6 is 'outgoing
interface'
I 06/27/16 11:48:17 02638 srcip: AM1: SFLOW oper policy is 'outgoing interface'
I 06/27/16 11:48:17 02637 srcip: AM1: SFLOW admin policy is 'outgoing interface'
I 06/27/16 11:48:17 02638 srcip: AM1: SNTP oper policy is 'outgoing interface'
I 06/27/16 11:48:17 02637 srcip: AM1: SNTP admin policy is 'outgoing interface'
I 06/27/16 11:48:17 02638 srcip: AM1: TFTP oper policy is 'outgoing interface'
I 06/27/16 11:48:17 02637 srcip: AM1: TFTP admin policy is 'outgoing interface'
I 06/27/16 11:48:17 02638 srcip: AM1: TELNET oper policy is 'outgoing interface'
I 06/27/16 11:48:17 02637 srcip: AM1: TELNET admin policy is 'outgoing
interface'
I 06/27/16 11:48:17 02638 srcip: AM1: SYSLOG oper policy is 'outgoing interface'
I 06/27/16 11:48:17 02637 srcip: AM1: SYSLOG admin policy is 'outgoing
interface'
I 06/27/16 11:48:17 02638 srcip: AM1: RADIUS oper policy is 'outgoing interface'
I 06/27/16 11:48:17 02637 srcip: AM1: RADIUS admin policy is 'outgoing
interface'
I 06/27/16 11:48:17 02638 srcip: AM1: TACACS oper policy is 'outgoing interface'
I 06/27/16 11:48:17 02637 srcip: AM1: TACACS admin policy is 'outgoing
interface'
I 06/27/16 11:48:17 00690 udpf: AM1: DHCP relay agent feature enabled
I 06/27/16 11:48:17 05177 ip: AM1: Setting IP address 10.225.0.1 as default
gateway.
I 06/27/16 11:48:16 02682 OOBM: AM1: OOBM - Enabled globally.
I 06/27/16 11:48:16 02012 mtm: AM1: A non-multicast client: Non-Mcast client DT,
is registered with client ID: 1
M 06/27/16 11:48:16 02798 chassis: AM1: Internal power supply 1 main PoE power
OK. Total fault count: 0
M 06/27/16 11:48:16 02797 chassis: AM1: Internal power supply 1 is OK. Total
fault count: 0.
M 06/27/16 11:48:16 02796 chassis: AM1: Internal power supply 1 inserted. Total
fault count: 0.
I 06/27/16 11:48:16 02759 chassis: AM1: Savepower LED timer is OFF.
I 06/27/16 11:48:16 02712 console: AM1: USB console cable disconnected
I 06/27/16 11:48:16 02712 console: AM1: USB console cable disconnected
I 06/27/16 11:48:16 03006 system: AM1: Reason for system reboot: Cold boot
I 06/27/16 11:48:16 00062 system: AM1: System went down without saving crash
information
I 06/27/16 11:48:16 00061 system: AM1: -----------------------------------------
I 06/27/16 11:48:14 03803 chassis: xM1: System Self test completed on Master
I 06/27/16 11:48:13 03802 chassis: xM1: System Self test started on Master
---- Top of Log : Events Listed = 123 ----

Aruba Employee

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

The LLDP events being logged are just informing you that there is a different untagged VLAN (PVID) on the other end of the link; since they're both untagged, traffic should not be affected.

 

PoE negotiation via LLDP is supported, but not enabled by default.  To enable, enter the command 'interface <list> poe-lldp-detect enable'.  Try this on the ports assigned to the AP-205s and see if they boot successfully.



Matthew Fern | Technical Marketing Engineer, Campus Networking
Aruba, a Hewlett Packard Enterprise Company
Occasional Contributor I

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

Thanks for the suggestion. I have already tried that on one of the interfaces and the issue persists. 

Aruba Employee

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

I'm following up with our AP and switch teams to figure out what may be going on here.  There are a few bits of info we may be able to use to get to the bottom of this issue:

 

  • Version of software running on the 2910al ('show version')
  • Port power status for one of the AP-205 ports during the AP boot process ('show power <port>')
  • LLDP info while the AP is booting, ideally as late in the boot process as possible before it reboots ('show lldp info remote <port>')

You can PM me the output if you'd rather not post it on the board.



Matthew Fern | Technical Marketing Engineer, Campus Networking
Aruba, a Hewlett Packard Enterprise Company
Occasional Contributor I

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

Thanks for your help on this issue. Here is the information you requested.

 

2910al Software Version: W.15.14.0013

 

Power on bootup outputs:

XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 84 mA
Power : 17.0 W Pre-std Detect : on

 

XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 84 mA
Power : 11.3 W Pre-std Detect : on

 

XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 90 mA
Power : 9.9 W Pre-std Detect : on

 

XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 90 mA
Power : 8.7 W Pre-std Detect : on

 

XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 90 mA
Power : 8.7 W Pre-std Detect : on

 

XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 90 mA
Power : 7.6 W Pre-std Detect : on


XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 90 mA
Power : 6.6 W Pre-std Detect : on

 

XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 91 mA
Power : 5.8 W Pre-std Detect : on


XXX-SW-IDFC-01(config)# show power-over-ethernet 8
Status and Counters - Port Power Status for port 8
Power Enable : Yes
LLDP Detect : enabled
Priority : low Configured Type :
AllocateBy : usage Value : 17 W
Power Class : 3 Detection Status : Delivering
Over Current Cnt : 0 MPS Absent Cnt : 2
Power Denied Cnt : 0 Short Cnt : 0
Voltage : 55.4 V Current : 92 mA
Power : 5.0 W Pre-std Detect : on

 

Show lldp info remote 8 output:

 

LLDP Remote Device Information Detail

Local Port : 8
ChassisType : mac-address
ChassisId : xx xx xx xx xx xx
PortType : mac-...
PortId : xx xx xx xx xx xx
SysName : xx:xx:xx:xx:xx:xx
System Descr : ArubaOS (MODEL: 205), Version 6.4.1.0 (43850)
PortDescr : bond0

System Capabilities Supported : bridge, wlan-access-point
System Capabilities Enabled :

Remote Management Address
Type : ipv6
Address : xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx

Aruba Employee

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

Based on this info, and after discussions with our teams, I have three steps we recommend to try (one at a time -- let me know if you've already tried any/all of these):

 

  1. Disable PoE pre-standard detection on the AP-205 ports ('no power-over-ethernet pre-std-detect ports <portlist>')
  2. Test a working AP-105 on a port currently assigned to an AP-205
  3. Update the firmware on an AP-205 to a newer build (you'll need to move it to a switch where it boots successfully), then reconnect it to the 2910.

Our AP team noted that the AP-205 seems to be running fairly old firmware based on the LLDP neighbor report, so making sure it's running the latest build (or at least something more recent than 6.4.1.0) may eliminate firmware issues as a potential cause.



Matthew Fern | Technical Marketing Engineer, Campus Networking
Aruba, a Hewlett Packard Enterprise Company
Occasional Contributor I

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

Thanks for the tips.

 

  1. I have removed the pre standard POE support off of the two (of the three) ports that had it enabled.  
  2. I have tested AP-105's in the same 3 ports and they work fine.
  3. The firmware on two of the non-working AP-205's is 6.4.4.5, which is what our controller is currently on.  The AP's on ports 6 and 7 are 6.4.4.5 and AP on port 8 is 6.4.1.0.

Unfortunantely it is still not working.  

Aruba Employee

Re: Issues with Aruba AP-205 on HP ProCurve 2910al

At this point, our support teams are going to need diagnostic info from both the switch and AP itself to troubleshoot the issue; if you haven't already been contacted by your support rep, let me know via PM with your case number, and I'll make sure it gets to the right people.



Matthew Fern | Technical Marketing Engineer, Campus Networking
Aruba, a Hewlett Packard Enterprise Company
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: