Network Management

 View Only
last person joined: 2 days ago 

Keep an informative eye on your network with IMC and AirWave network management solutions.
Expand all | Collapse all

Old school 5406ZL, recommended power 802.3 at

This thread has been viewed 16 times
  • 1.  Old school 5406ZL, recommended power 802.3 at

    Posted Jan 05, 2022 08:38 AM
    Hello, (Appologies if this question is in the wrong community)

    I'm trying to deliver 802.3 at power to my Aruba AP-515 (Instant Access Points)

    My old school switch, 5406ZL switch delivers 802.3 af

    I upgraded one of the PoE modules which now supports 802.3 at. Then changed the port 'AllocateBy: usage' 'set value to 33 W' and bingo! it works.

    I then upgraded the firmware on the 5406ZL switch from v15 to v16. In doing so the power negotiation has reverted back to 'af' for said port, WIFI access points are now offline...

    Whatever I try, GUI or CLI I cannot change the AllocateBy from LLDP to Usage. (assuming 'Usage' would fix it)

    If I physically remove the access point from the switch the port changes back to usage. When I plug the device back in again it changes to LLDP.

    I'm totally stuck, I don't know what to do. 
    Thanks for any help with this.



    ------------------------------
    Leo Pickford
    ------------------------------


  • 2.  RE: Old school 5406ZL, recommended power 802.3 at

    MVP GURU
    Posted Jan 05, 2022 09:37 AM
    Hi Leo, this thread should have been started on the Wired Intelligent Edge community or in the Wireless Access community for better visibility.

    Does your Switch's running configuration contain a section like:

    device-profile name "aruba-ap"
      poe-allocate-by lldp
    exit
    device-profile type "aruba-ap"
      associate "aruba-ap"
      enable
    exit

    or something similar?

    Have you tried to force this on the port where the AP-515 is currently connected (just to see if it works):

    (config)# lldp admin-status <port-id> disable

    then inside the <port-id> (say it is "eth-x") context issue a:

    (eth-x)# poe-allocate-by usage

    Useful commands (before/after the change): show lldp info remote-device <port-id> and show power-over-ethernet <port-id>

    ------------------------------
    Davide Poletto
    ------------------------------



  • 3.  RE: Old school 5406ZL, recommended power 802.3 at

    Posted Jan 05, 2022 10:09 AM
      |   view attached
    Hello Davide,

    Thank you so much for your reply. Noted on the community category. 

    Running config shows this for said port D23:

    interface D23
    power-over-ethernet high
    poe-allocate-by value
    poe-value 30
    poe-lldp-detect enabled
    exit

    I entered the lldp disable command you suggested. It how shows this. 

    interface D23
    power-over-ethernet high
    poe-value 30
    poe-lldp-detect enabled
    exit

    I have added a screen grab for the PoE status.

    Kindest regards,
    Leo.

    ------------------------------
    Leo Pickford
    ------------------------------



  • 4.  RE: Old school 5406ZL, recommended power 802.3 at

    MVP GURU
    Posted Jan 10, 2022 09:30 AM
    Was the poe-allocate-by usage command then issued within the context of port D23 or not? it looks like it wasn't.

    ------------------------------
    Davide Poletto
    ------------------------------



  • 5.  RE: Old school 5406ZL, recommended power 802.3 at

    Posted Jan 10, 2022 10:13 AM
    Hello Davide,

    Thanks for your message. 

    I'm issuing the commands but it's not taking. See screen shots. Before issuing commands I physically removed the device from the port. It makes no difference. I am missing something here...

    ------------------------------
    Leo Pickford
    ------------------------------



  • 6.  RE: Old school 5406ZL, recommended power 802.3 at

    Posted Jan 10, 2022 11:12 AM
    Hello Davide,

    As per your suggestion, I raised a discussion over in Wired Networking and it's looking like I need compatible PoE+ power supplies (300W) to drive the PoE+ module which may explain the problem.

    https://community.arubanetworks.com/community-home/digestviewer/viewthread?MessageKey=c1b80301-a15a-498c-8c7e-4484ba097d63&CommunityKey=22dc38ea-a1e1-4059-b55e-a622fedecf32&tab=digestviewer&bm=c1b80301-a15a-498c-8c7e-4484ba097d63#bmc1b80301-a15a-498c-8c7e-4484ba097d63

    ------------------------------
    Leo Pickford
    ------------------------------