Wired Intelligent Edge

 View Only
last person joined: yesterday 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Back to discussions
Expand all | Collapse all

2540G-POE PD error message for Access point

This thread has been viewed 131 times

  • 1.  2540G-POE PD error message for Access point

    Posted Jun 15, 2020 03:30 AM

    I faced the issue that access point went down with this message.

    I am not sure where is the root cause to make this error.

     

    PD stopped responding to LLDP PoE TLVs from PSE.
    Previous LLDP negotiated power values will be retained.

    port 1 is now on-line.

    port 1 is now off-line.

    port 1 is now on-line.

     

    Switch 2540G-POE

    Access Point 515(RW)


    Please help



  • 2.  RE: 2540G-POE PD error message for Access point

    MVP EXPERT
    Posted Jun 15, 2020 11:02 AM

    Did you see anything in the logs from the AP side when the issue occurred? Any warnings or similar mentioning LLDP or PoE?



  • 3.  RE: 2540G-POE PD error message for Access point

    Posted Feb 01, 2022 07:38 AM
    Hello Craig,
    I have same issue and getting error on switch port " PD stopped responding to LLDP PoE TLVs from PSE" 
    What should I do ?

    ------------------------------
    Shivam Ojha
    ------------------------------

    Original Message


  • 4.  RE: 2540G-POE PD error message for Access point

    MVP GURU
    Posted Jun 16, 2020 02:49 AM

    What firmware on IAP and switch ?



  • 5.  RE: 2540G-POE PD error message for Access point

    EMPLOYEE
    Posted Jul 02, 2020 05:48 AM

    I'm seeing this log message on a 3810M with 315 and 535. I don't believe the AP is actually going down in my case.



  • 6.  RE: 2540G-POE PD error message for Access point

    MVP GURU
    Posted Jul 07, 2020 02:38 PM

    What sw firmware ?



  • 7.  RE: 2540G-POE PD error message for Access point

    Posted Aug 20, 2020 06:28 AM

    Hi,

     

    I am getting this issue too

     

    The switch im using is aruba 2930F WC.16.10.0009

     

     



  • 8.  RE: 2540G-POE PD error message for Access point

    Posted Aug 26, 2020 05:22 AM

    Hi i am getting the same massages:

     

    PD stopped responding to LLDP PoE TLVs from PSE. Previous LLDP negotiated power values will be retained.

     

    Using iAP305 with 2930F WC.16.10.0010



  • 9.  RE: 2540G-POE PD error message for Access point

    MVP GURU
    Posted Aug 31, 2020 02:34 AM

    I think, need to open issue on TAC



  • 10.  RE: 2540G-POE PD error message for Access point

    Posted Sep 01, 2020 06:04 PM

    Guess this is also a "me too" as well. 

     

    I've been getting complaints for about a week. I think it actually started though after the last Aruba maintenance cycle. Though, I just replaced 2 of our cisco switches with Aruba 2930M's and now I can actually see it. 

     

    Seeing a drop on the switch side and the following on one of our ap's

     
    ap drop.jpg

     We have 21 515's currently deployed.

     

    I should add, out of the access points we have, only a handful of them are having this issue. 

     

    switch firmware WC.16.10.0009

    ap firmware        8.6.0.4_74969  



  • 11.  RE: 2540G-POE PD error message for Access point

    Posted Feb 01, 2021 07:29 AM
    Another 'me too'.
    AP showing down in AirWave - IAP 375 running 8.6.0.6
    Interface showing up on switch.  PoE delivering on switch, however looks different to other ports with same APs.
    "Status and Configuration Information for port 1/1
    Power Enable : Yes PoE Port Status : Delivering
    PLC Class/Type : 4/2 Priority Config : high
    DLC Class/Type : 0/- Pre-std Detect : off"
    as opposed to:
    Status and Configuration Information for port 1/2
    Power Enable : Yes PoE Port Status : Delivering
    PLC Class/Type : 4/2 Priority Config : high
    DLC Class/Type : 4/2 Pre-std Detect : off

    Message in logs about PoE:
    "ports: ST2-CMDR: Port 1/1: PD stopped responding to LLDP PoE TLVs from PSE. Previous LLDP negotiated power values will be retained."

    Switch is a stack of 2930M-40G-8SR-PoE-Class6 Switch (R0M67A) on WC.16.10.0010.  APs are all connected to the 802.3bz 100M, 1/2.5/5/10GBaseT PoE Class 6 ports.

    I turned off PoE to the affected AP and re-enabled it (always worth a go ;-)) - the AP rebooted and all was fine again.


    ------------------------------
    Toby Setchfield
    ------------------------------

    Original Message


  • 12.  RE: 2540G-POE PD error message for Access point

    Posted Oct 22, 2021 03:55 AM
    Hi all 

    Another with same issues. However only seen it once so far. 

    AP down, no ping response, interfaces up, poe+ being provided, same logs as above. 

    Aruba 555 2 Interfaces LACP. Aruba 2530-48G-PoEP YA.16.10.0015

    Original Message


  • 13.  RE: 2540G-POE PD error message for Access point

    Posted Dec 09, 2021 11:00 AM
    We are also facing this issue. We get random complaints from these areas, but nothing consistent. I'm not 100% sure the APs are booting, or not. 

    515 APs with the POE TLV messages on 2930M switches. Airwave shows the AP booting and constantly jumping controllers.

    I 12/09/21 10:45:33 05824 ports: Port 9: PD stopped responding to LLDP PoE TLVs
    from PSE. Previous LLDP negotiated power values will be retained.
    I 12/09/21 10:45:33 05747 DFP: device_fingerPrinting: Hardware Rules updated
    successfully for port:9, protocol:80, client:D0:D3:E0:C6:86:58
    I 12/09/21 10:45:33 00076 ports: port 9 is now on-line
    I 12/09/21 10:45:33 05824 ports: Port 3: PD stopped responding to LLDP PoE TLVs
    from PSE. Previous LLDP negotiated power values will be retained.
    I 12/09/21 10:45:33 05747 DFP: device_fingerPrinting: Hardware Rules updated
    successfully for port:3, protocol:80, client:D0:D3:E0:C6:79:04
    I 12/09/21 10:45:33 00076 ports: port 3 is now on-line
    W 12/09/21 10:45:33 00328 FFI: port 5-Excessive jabbering/fragments. See Help
    W 12/09/21 10:45:33 00328 FFI: port 4-Excessive jabbering/fragments. See Help
    I 12/09/21 10:45:32 05824 ports: Port 15: PD stopped responding to LLDP PoE TLVs
    from PSE. Previous LLDP negotiated power values will be retained.
    I 12/09/21 10:45:32 05747 DFP: device_fingerPrinting: Hardware Rules updated
    successfully for port:15, protocol:80, client:D0:D3:E0:C6:7C:6E
    I 12/09/21 10:45:32 00076 ports: port 15 is now on-line
    I 12/09/21 10:45:32 05745 DFP: device_fingerPrinting: policy
    <Device>_Fingerprint applied to port 15
    I 12/09/21 10:45:32 05745 DFP: device_fingerPrinting: policy
    <Device>_Fingerprint applied to port 9
    I 12/09/21 10:45:32 05745 DFP: device_fingerPrinting: policy
    <Device>_Fingerprint applied to port 3
    I 12/09/21 10:45:32 00435 ports: port 15 is Blocked by AAA
    I 12/09/21 10:45:32 00435 ports: port 9 is Blocked by AAA
    I 12/09/21 10:45:32 00435 ports: port 3 is Blocked by AAA
    I 12/09/21 10:45:27 05746 DFP: device_fingerPrinting: policy
    <Device>_Fingerprint removed from port 15
    I 12/09/21 10:45:27 05746 DFP: device_fingerPrinting: policy
    <Device>_Fingerprint removed from port 9
    I 12/09/21 10:45:27 05746 DFP: device_fingerPrinting: policy
    <Device>_Fingerprint removed from port 3
    I 12/09/21 10:45:27 00077 ports: port 15 is now off-line
    I 12/09/21 10:45:27 00077 ports: port 9 is now off-line
    I 12/09/21 10:45:27 00077 ports: port 3 is now off-line

    Running 8.6.0.14 on the MDs, 16.08.0018 on the 2930Ms.

    Could be as simple as repunching the jack ends?

    ------------------------------
    Brian Simpson
    ------------------------------

    Original Message


  • 14.  RE: 2540G-POE PD error message for Access point

    Posted Feb 11, 2022 08:07 AM
    Hi

    Any further updates on this issue?
    I'm seeing very similar symptoms at one site. AP-305s seem to suddenly be affected within the last two weeks. We've had no absolutely zero complaints from locations with AP-315s. All APs connected to 2930F switches. The switch is running WC.16.10.0012 and the AP 8.6.0.16_83052 (the recommended version, according to Central). 

    Here's an example of behaviour we've seen today:

    Central claims that this particular AP has been up for 19 hours (since I rebooted the switch, last night), but the 'health status' graph shows it as offline from 5:30 (when I rebooted the switch) to midnight!
    The switch has logged:

    I 02/11/22 07:43:03 05824 ports: Port 7: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 02/11/22 07:43:03 00435 ports: port 7 is Blocked by STP
I 02/11/22 07:43:01 00077 ports: port 7 is now off-line
I 02/11/22 07:35:35 00076 ports: port 7 is now on-line
I 02/11/22 07:35:32 05824 ports: Port 7: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 02/11/22 07:35:32 00435 ports: port 7 is Blocked by STP
I 02/11/22 07:35:30 00077 ports: port 7 is now off-line
    The AP has logged (show log system)
    Feb 11 07:55:58  cli[5642]: <341271> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  ethernet uplink bond0 link down.
Feb 11 07:55:58  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  stopping DHCP on bond0
Feb 11 07:55:58  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  ip address get failed
Feb 11 07:55:58  cli[5642]: <341185> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Retrieving ip address from uplink, ip 10.73.16.98, mask 255.255.248.0.
Feb 11 07:55:58  cli[5642]: <341274> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Update election ip from br0, election ip 10.73.16.98/255.255.248.0.
Feb 11 07:55:58  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  build_my_ip_address: old ip and new ip same; skipping
Feb 11 07:55:58  cli[5642]: <341167> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Uplink bond0 type Ethernet, state UP->DOWN.
Feb 11 07:55:58  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  uplink failure on slave
Feb 11 07:55:58  cli[5642]: <341263> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  enable uplink .
Feb 11 07:55:58  cli[5642]: <341167> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Uplink  type Dummy, state LOAD->PROBE.
Feb 11 07:55:58  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  enable dummy uplink
    Feb 11 07:55:58  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  disable SSID[ssid-wlan
Feb 11 07:55:58  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  disable SSID[ssid2 House
Feb 11 07:55:59  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  uplink failure on slave
Feb 11 07:56:01  cli[5642]: <341272> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  ethernet uplink bond0 link up.
Feb 11 07:56:01  cli[5642]: <341167> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Uplink bond0 type Ethernet, state DOWN->UP.
Feb 11 07:56:01  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  ip address get failed
Feb 11 07:56:01  cli[5642]: <341166> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Get interface br0 ip: 0.0.0.0/0.0.0.0.
Feb 11 07:56:01  cli[5642]: <341005> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  wired reset detected, setup ip now

:01  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  bring up dhcp client for ethernet uplink
Feb 11 07:56:02  stm[5674]: <304055> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 stm| |ap| Unexpected stm (Station management) runtime error at rap_asap_to_stm_handler, 16782, rap_asap_to_stm_handler: recv - Network is down
Feb 11 07:56:02  sapd[5662]: <311020> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 sapd|  An internal system error has occurred at file sapd_fw.c function sapd_dp_msg_handler line 2269 error sapd_dp_msg_handler: socket recv failure Network is down.
Feb 11 07:56:03  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  /etc/setup_ip_swarm Ethernet 1
Feb 11 07:56:03  cli[5642]: <341166> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Get interface br0 ip: 10.73.16.98/255.255.248.0.
Feb 11 07:56:03  cli[5642]: <341185> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Retrieving ip address from br0, ip 10.73.16.98, mask 255.255.248.0.
Feb 11 07:56:03  cli[5642]: <341274> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Update election ip from br0, election ip 10.73.16.98/255.255.248.0.
Feb 11 07:56:03  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  build_my_ip_address: old ip and new ip same; skipping
Feb 11 07:56:03  cli[5642]: <341006> <CRIT> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Sending uplink_up msg to sapd
Feb 11 07:56:03  cli[5642]: <341006> <CRIT> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  trap uplink info.
Feb 11 07:56:03  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  last uplink is null, it's the first uplink, ignore this trap.
Feb 11 07:56:03  cli[5642]: <341264> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  disable uplink .
Feb 11 07:56:03  cli[5642]: <341167> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  Uplink  type Dummy, state PROBE->DOWN.
Feb 11 07:56:03  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  disable dummy uplink
Feb 11 07:56:03  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  enable SSID[ssid-wlan
Feb 11 07:56:03  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  enable SSID[ssid2 House
Feb 11 07:56:05  cli[5642]: <341213> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  cli_papi_dp_msg_handler: ASAP to CLI socket recv failed 12 100.
Feb 11 07:56:05  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  cli_loop_protect_dp_msg_handler: recv failure.
Feb 11 07:56:05  cli[5642]: <341004> <WARN> |AP 90:4c:81:c9:09:be@10.73.16.98 cli|  recv non-3g setup_uplink finished from sapd
Feb 11 07:56:13  nanny[5542]: <303073> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 nanny|  Process /aruba/bin/aruba_ntpdate [pid 6827] died: got signal SIGTERM
Feb 11 07:56:13  nanny[5542]: <303079> <ERRS> |AP 90:4c:81:c9:09:be@10.73.16.98 nanny|  Restarted process /aruba/bin/aruba_ntpdate, new pid 7198
    Note the different times, but the clock on the AP and switch are in sync.

    In addition, the Central events log for the AP shows that the AP was clearly online last night at the times the graph states that it was offline:

    2022-02-10 18:33:27 GMT 86:17:c4:52:24:0e 90:4c:81:10:9b:f0 Client Association Success Client 86:17:c4:52:24:0e associated successfully to SSID chester-wlan on channel 36E

    2022-02-10 18:25:14 GMT Radio ARM Increased Power Radio output power increased to 10 dBm. Reason: Channel Assignment ARM Increase Power

    2022-02-10 18:15:25 GMT 86:17:c4:52:24:0e 90:4c:81:10:9b:f0 Client Roaming Success Client 86:17:c4:52:24:0e associated to BSSID 90:4c:81:10:9b:e0 on channel 6 of AP hostname 90:4c:81:c9:09:be roamed successfully to BSSID 90:4c:81:10:9b:f0 on channel 36E of AP hostname 90:4c:81:c9:09:be chester-wlan 90:4c:81:c9:09:be 36E 90:4c:81:c9:09:be 90:4c:81:10:9b:e0 6 7 802.11 44

    2022-02-10 18:15:25 GMT 86:17:c4:52:24:0e 90:4c:81:10:9b:e0 Client 802.11 De-authentication to Client De-authentication sent to client 86:17:c4:52:24:0e from BSSID 90:4c:81:10:9b:e0 on channel 6 of AP hostname 90:4c:81:c9:09:be. Reason: Station has roamed to another AP Station has roamed to another AP chester-wlan

    2022-02-10 17:56:43 GMT Radio ARM Increased Power Radio output power increased to 10 dBm. Reason: Channel Assignment ARM Increase Power

    2022-02-10 17:50:33 GMT Radio ARM Increased Power Radio output power increased to 10 dBm. Reason: Channel Assignment ARM Increase Power

    2022-02-10 17:43:57 GMT Radio ARM Increased Power Radio output power increased to 10 dBm. Reason: Channel Assignment ARM Increase Power

    2022-02-10 17:37:00 GMT Radio ARM Increased Power Radio output power increased to 10 dBm. Reason: Channel Assignment ARM Increase Power

    2022-02-10 17:33:05 GMT 86:17:c4:52:24:0e 90:4c:81:10:9b:e0 Client Association Success Client 86:17:c4:52:24:0e associated successfully to SSID chester-wlan on channel 6

    2022-02-10 17:29:22 GMT AP Reboot Access point 90:4c:81:c9:09:be rebooted

    2022-02-10 17:27:48 GMT AP Offline Access point 90:4c:81:c9:09:be is offline

    I'm a bit lost as to where to start troubleshooting. Ports on the switch show very few if any errors and I'm not sure if this is an AP, switch or Central issue?

    Thank you for any advice. 


    Original Message


  • 15.  RE: 2540G-POE PD error message for Access point

    Posted Jun 16, 2022 11:00 AM
    Hi sram, did you ever find out the solution to this?

    Seeing this exact issue on our AP-305s as well.
    Original Message


  • 16.  RE: 2540G-POE PD error message for Access point

    Posted Jun 17, 2022 05:17 PM
    Same issue here as well with AP-305s. Would love to know if this was ever resolved.
    Original Message


  • 17.  RE: 2540G-POE PD error message for Access point

    Posted Jun 21, 2022 11:01 AM
    Just for the sake if someone has encountered this issue in the future.

    So I have exactly the same (or very close) issue for my Aruba 3810M + AP-515. The Gigabits ports are doing well, but when I plugged my AP-515 to the 10Gbit ports (negotiated as 2.5Gb), the same annoying message flooded my switch:

       PD stopped responding to LLDP PoE TLVs from PSE. Previous LLDP negotiated power values will be retained.

    The AP would drop out from the connection, and there are also a lot of Link Down/Link Up messages together with this on both the switch and AP sides.

    I suspect the LLDP thing on my 10Gb ports is defective, but I can still see constant power has been supplied to the AP, which is a good sign. The workaround I used to overcome this was:

    1. Disable both "LLDP MED TLV (PoE)" and "LLDP DOT3 TLV (PoE+)" for the port
    2. Change "Power Allocation By" to "value"
    3. Give a value in Watt according to your device, in my case, 21

    Then everything went back to normal. One drawback is I am not sure if the device is running in full power mode, but at least all drop outs are gone.
    Original Message


  • 18.  RE: 2540G-POE PD error message for Access point

    Posted Jun 21, 2022 05:21 PM
    Hi Alex

    No, I never got to the bottom of it. After updating firmware on both switch and AP the users stopped reporting outages, but I still have the messages in the switch log. The last time this happened was 12 June and so in the last few days I've set up a basic repetitive ping test from a workstation plugged in to the same switch as the AP that is being flagged as going offline to see if it's actually going offline or is the entry in the switch log is perhaps not completely accurate. Of course, it may be a few days before I see the entry again and I can check the ping log to see if there's any correlation.
    Original Message


  • 19.  RE: 2540G-POE PD error message for Access point

    Posted Oct 31, 2022 06:50 AM
    The problem is back with a vengeance:

    I 10/30/22 13:01:10 00076 ports: port 1 is now on-line
I 10/30/22 13:01:07 05824 ports: Port 1: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 13:01:07 00435 ports: port 1 is Blocked by STP
I 10/30/22 13:00:57 00077 ports: port 1 is now off-line
I 10/30/22 13:00:57 00076 ports: port 4 is now on-line
I 10/30/22 13:00:54 00435 ports: port 4 is Blocked by STP
I 10/30/22 13:00:52 00077 ports: port 4 is now off-line
I 10/30/22 13:00:51 05824 ports: Port 4: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 13:00:51 00435 ports: port 4 is Blocked by STP
I 10/30/22 13:00:48 00077 ports: port 4 is now off-line
I 10/30/22 13:00:08 00076 ports: port 7 is now on-line
I 10/30/22 13:00:06 05824 ports: Port 7: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 13:00:06 00435 ports: port 7 is Blocked by STP
I 10/30/22 12:59:57 00076 ports: port 6 is now on-line
I 10/30/22 12:59:56 00077 ports: port 7 is now off-line
I 10/30/22 12:59:55 05824 ports: Port 6: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 12:59:55 00435 ports: port 6 is Blocked by STP
I 10/30/22 12:59:46 00076 ports: port 2 is now on-line
I 10/30/22 12:59:45 00076 ports: port 8 is now on-line
I 10/30/22 12:59:45 00077 ports: port 6 is now off-line
I 10/30/22 12:59:44 00435 ports: port 2 is Blocked by STP
I 10/30/22 12:59:43 05824 ports: Port 8: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 12:59:43 00435 ports: port 8 is Blocked by STP
I 10/30/22 12:59:41 00077 ports: port 2 is now off-line
I 10/30/22 12:59:41 05824 ports: Port 2: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 12:59:41 00435 ports: port 2 is Blocked by STP
I 10/30/22 12:59:37 00077 ports: port 2 is now off-line
I 10/30/22 12:59:36 00077 ports: port 8 is now off-line
I 10/30/22 12:58:13 00076 ports: port 3 is now on-line
I 10/30/22 12:58:11 00435 ports: port 3 is Blocked by STP
I 10/30/22 12:58:08 00077 ports: port 3 is now off-line
I 10/30/22 12:57:19 00076 ports: port 3 is now on-line
I 10/30/22 12:57:16 05824 ports: Port 3: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 12:57:16 00435 ports: port 3 is Blocked by STP
I 10/30/22 12:56:52 00077 ports: port 3 is now off-line
I 10/30/22 12:56:23 00076 ports: port 1 is now on-line
I 10/30/22 12:56:20 05824 ports: Port 1: PD stopped responding to LLDP PoE TLVs
            from PSE. Previous LLDP negotiated power values will be retained.
I 10/30/22 12:56:20 00435 ports: port 1 is Blocked by STP
I 10/30/22 12:56:10 00077 ports: port 1 is now off-line
I 10/30/22 12:56:10 00076 ports: port 4 is now on-line
​

    Ports 1-8 are AP-305s running 8.6.0.16.

    As per dracocephalum's suggestion I have just set the power value to 13 (13w is the worst case scenario without anything connected to the USB port, according to the 300 series spec sheet)

    interface 1
   poe-allocate-by value
   poe-value 13
   exit
interface 2
   poe-allocate-by value
   poe-value 13
   exit
​


    I believe that by hard coding the value like this, the switch will reserve more power for the ports and so potentially it may not be able to support as many APs plugged in? Please can someone with more experience chime in here? In this instance it won't be a problem as there are only 8 APs connected to this particular switch, but we have some 2030Fs elsewhere in the school with ~20 AP-305s connected and so it will be interesting to see what happens there...

    Thank you
    Original Message


  • 20.  RE: 2540G-POE PD error message for Access point

    Posted Oct 31, 2022 05:52 PM
    I've been looking at these log entries in more detail. I've noticed some patterns between APs connected to different switches - a lot of them appear to have rebooted within a couple of minutes of each other. Is there a known list of events that would cause an AP-305 to automatically reboot itself? The log entries of the interface going down and the PoE power being removed started to spike over the weekend (29-30 Oct). This also happens to coincide with when their DNS and DHCP server went down. So if an AP can't lease an IP or can't perform a DNS lookup, will it reboot? This may explain the log entries in this particular instance. 
    But that does make me wonder if the entry PD stopped responding to LLDP PoE TLVs from PSE is merely a resulting symptom and not necessarily the cause of any problem?
    Original Message


  • 21.  RE: 2540G-POE PD error message for Access point

    EMPLOYEE
    Posted Nov 01, 2022 09:20 AM
    That is quite likely.. the AP will only do LLDP when the firmware is loaded and running.

    You could check the reboot reason for the AP. If it is instant, use the show version command where the reason is in the last line, or on a controller show ap debug system-status ap-name name-of-your-AP.

    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------

    Original Message