Wired Intelligent Edge

 View Only
last person joined: yesterday 

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

2540G-POE PD error message for Access point

This thread has been viewed 88 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
    ------------------------------



  • 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
    ------------------------------



  • 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



  • 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
    ------------------------------



  • 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: