Dear All,

Virtual controller solution of 42 IAPs model 103. One IAP as a virtualc controller for WLAN network services.

 

Client match help for the sticky clients. After enabling the client match feature what is the recommended settings for client match?

 

 CM calculating interval=400sec     (default value was 30 sec)
 CM neigbouring matching=75% default value
CM threshold= 2 default value
 

If I set all to the default values users are experiencing disconnectivity./connectivity after every 1min. So I set the CM calculating interval to 400 sec now disconnectivity/connectivity issue has been reduced but sometimes occuring.

 

Minimum transmit power=12

Maxumim transmit power= max (18)

 

what is the recommended settings ?

Do not use CM on IAP 103 at this time.

What is an issue at this stage ?

It does not work as expected. It is being optimized. You should be able to run your network without it.

But how could i resolved sticky clients issue ?

The correct power for your environment should mitigate the issue. High power creates sticky client issues. Match your power to the output power of your clients.

How should I check the power of the user devices, since there are 350 users ????????

You currently have 12/18 has min/max power settings, do you experience sticky clients with those power levels?
Are they (clients) all different devices or mostly IOS or Android or Windows, etc.. devices? If a strong majority of devices are of a certain vendor and/or mobile devices, this will help you choose the correct power levels. Mobile devices have a weaker antenna than laptops for example
Have you tried reducing to 9/15 to see if it helps? Have you done a site survey?
When you reduce the power can you do another walk through with your site survey tool?

I will look into it and will update you.

Yes most of them are different vendor devices such as tablets, latptops and mostly mobile phone of different vendors....

 

 

I suggest looking at your power levels and how close your APS are together. by close I mean you need to run some ARM commands to see how many aps another ap can see, if a particular ap can see 3, 4 even 5 others APS with an rssi that's not very high, reduce your power levels and try again.

I also suggest taking a look at what basic rates are configured...for 2.4 and 5ghz maybe change it to a min of 6 instead of having 1, 2 or 5 selected for 2.4.

if you have airwave, load the floor plans on visualRF and let it gather some data if you dont have a site survey tool.

also like CJoseph said disable CM.

Is Client Match still not recommended for IAP-103 for 6.4.2.6-4.1.1.11_52666?

Only enable Client Match in 4.2.X.X and above.

---

@cjoseph wrote:
Only enable Client Match in 4.2.X.X and above.

Thanks for your fast replay.

Another question. Isn't the 6.4.2.6-4.1.1.11_52666 the latest firmware for the IAP-103?

 

 

It is the latest GA code. 4.2 is early access code.

 

---

@cjoseph wrote:
It is the latest GA code. 4.2 is early access code.

---

Pardon my ignorance since I'm new to Aruba. When you refer to 4.2 are you talking as on 6.4.2.x or to the number after the dash?

Number after the dash

I apologize.  6.4.2.6-4.1.1.11 is the latest GA code.  6.4.3.4-4.2.1.1 is the latest Early Access Code.

 

I hope that helps.

 

 

 

---

cjoseph wrote:

I apologize.  6.4.2.6-4.1.1.11 is the latest GA code.  6.4.3.4-4.2.1.1 is the latest Early Access Code.

 

I hope that helps.

 

Thanks a lot.

 So GA stands for something like the latest stable version and Early Access Code like a new Beta Version, correct?

Yes.