Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Mobility controller 3000 / AP 125 bizzare behavior

This thread has been viewed 0 times
  • 1.  Mobility controller 3000 / AP 125 bizzare behavior

    Posted Jan 21, 2017 05:16 PM

    I have one issue and one question:

     

    Issue: Mobile devices on my network just "drop" with no warning/reason and rejoin almost immediately. It's very strange. I did a 'debug' on one of them and saw the error "internal ageout". I looked around the rest of the config and found a timeout set to its default at 180 seconds, but this drop is something I can reproduce if I put the phone in the right place in my environment in just a few seconds. I'm not sure where to begin here.

     

    Question: Is there a way to force certain clients (security cameras) to associate to specific aps? For some reason these things are joining aps way too far away and the signal is horrible, when there are mesh nodes something like 5 feet away.

     

    Any advice would be fantastic, and thanks in advance!

     



  • 2.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 21, 2017 06:00 PM
    What is the max TX power in your ARM profile? It sounds like the power is too high..


  • 3.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    Posted Jan 22, 2017 04:13 PM

    It's cranked - as high as it can go. 

    I can try turning it down, and seeing what happens.

     



  • 4.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 22, 2017 06:51 PM

    What is it set at?   Max power creates issues with clients like random disconnects and roaming problems.



  • 5.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    Posted Jan 23, 2017 04:04 PM

    both the max and min EIRP was set to 127, so I've changed max to 33 and min to 3, but it appears to have not affected the issue. I still have mobile devices just dropping off the network.

     

    I'm also still trying to sort out how to get certain cameras to only associate with specific radios - I can't find a clear way to do that.

     



  • 6.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 23, 2017 04:50 PM

    Change the min to 9 and the max to 12 or 15 please.  Every 3 db results in a doubling of power (dbm is logarithmic).  Most mobile devices do not transmit much more than 17 so anything above that makes transmit power very asymetric and it will cause issues.  Most AP are not allowed to transmit more than 23 depending on channel, so changing from 127 to 33 did not make a difference.



  • 7.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    Posted Jan 23, 2017 06:02 PM

    Okiedokie. That change has been made.

    A and G radios are set to min 9, max 12.

     

    Any ideas on how to force association? I was hoping one could tell the controller something like "these mac addresses should be forced to talk to this radio, specifically"...



  • 8.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 23, 2017 08:16 PM

    That is not possible.  Only the client can make decisions on what access points it connects to.  We can only try to influence it.



  • 9.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    Posted Jan 23, 2017 08:17 PM

    how would one influence it?



  • 10.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 23, 2017 08:50 PM

    We are already influencing it by reducing the power.  You can turn it off, then turn it back on again, and it might select the closest access point, as a result.



  • 11.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    Posted Jan 24, 2017 09:08 PM

    So it turns out these cameras having the issue can only do 2.4ghz, not 5ghz, and the mesh AP closest to it is likely using the 2.4ghz radios to backhaul the traffic and using the 5ghz radios as the access radios. Is there a way to invert those to see if that helps?

    This is an ap125, by the way...

     



  • 12.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 24, 2017 09:23 PM

    By default backhaul is performed on the 5ghz band.  I would open a TAC case to get the details of your deployment reveiwed carefully and remediated.



  • 13.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    Posted Jan 24, 2017 09:27 PM

    Is that HPE now? or is there still aruba support?



  • 14.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 24, 2017 09:33 PM


  • 15.  RE: Mobility controller 3000 / AP 125 bizzare behavior

    EMPLOYEE
    Posted Jan 25, 2017 01:14 AM

    Only way to force cameras/clients to a specific AP is to have specific SSIDs created on each AP specific to each camera. Not sure that is a good direction to go, but it would force the issue.