Wireless Access

Reply
Occasional Contributor II

Mobility controller 3000 / AP 125 bizzare behavior

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!

 

Guru Elite

Re: Mobility controller 3000 / AP 125 bizzare behavior

What is the max TX power in your ARM profile? It sounds like the power is too high..


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: Mobility controller 3000 / AP 125 bizzare behavior

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

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

 

Guru Elite

Re: Mobility controller 3000 / AP 125 bizzare behavior

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



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: Mobility controller 3000 / AP 125 bizzare behavior

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.

 

Guru Elite

Re: Mobility controller 3000 / AP 125 bizzare behavior

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.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: Mobility controller 3000 / AP 125 bizzare behavior

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"...

Guru Elite

Re: Mobility controller 3000 / AP 125 bizzare behavior

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



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: Mobility controller 3000 / AP 125 bizzare behavior

how would one influence it?

Guru Elite

Re: Mobility controller 3000 / AP 125 bizzare behavior

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.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: