Wireless Access

Reply
Regular Contributor I

6.2.1.0

I had a client upgrade his controller to 6.2.1.0 (from 6.1.3.4). They stated they experienced a large signal strength drop after upgrade. Those that never had wireless trouble in the past went from having 3-4 bars were now at 1-2 bars and were loosing pings to the network. They then reverted back to the 6.1.3.4 software and signal strength went back to normal levels.

 

I did not experience this problem myself and am only relaying on what the customer told me. That being said has anyone else noticed this type of problem in the 6.2. upgrade?

Regular Contributor I

Re: 6.2.1.0

3800 controller

MVP

Re: 6.2.1.0

We had the same experience and after a fair amount of fiddling with it, fell back to 6.1.3.4 (our prior known-good version) while we await a fix. The last I heard was that there is a fix going in to 6.1.3.8 which may relate to our problem (it sounded imminent but hasn't come out yet)

 

I presume that the same fix will enter the 6.2.x.x chain as well.

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
Guru Elite

Re: 6.2.1.0

Msabin, Would you care to mention the details of the fix to help the community?



Colin Joseph
Aruba Customer Engineering

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

MVP

Re: 6.2.1.0

I'm still waiting for the fixed code.

 

Quoting my TAC engineer:

6.1.3.8  has a fix for a Low RSSI threshold issue ... Our best bet would be to upgrade to 6.1.3.8 once it available and take things from there.

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
Guru Elite

Re: 6.2.1.0

I don't even know what that means.



Colin Joseph
Aruba Customer Engineering

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

MVP

Re: 6.2.1.0

After much arguing over what was a problem with our client configs and what was a problem with our controller configs and what was due specifically to the code upgrade, we agreed that the primary evidence of the problem we were seeing was that clients appeared to the controller at somewhat lower RSSI than the client thought. Thus the client would keep talking and the controller would de-auth.

 

Apparently there's an identified issue where the controller mis-perceives the RSSI as low and there's a possibility that that issue is getting addressed.

 

Just got word from support that 6.1.3.8 may be out by 4/19.

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
Guru Elite

Re: 6.2.1.0

If you have a bug number or a case number we can track it down and see what is being done about it.

 



Colin Joseph
Aruba Customer Engineering

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

MVP

Re: 6.2.1.0

My case number is 1380609 -- I let them close it while I wait for 6.1.3.8 and then a chance to upgrade and test.

--Matthew

if I've helped, please give kudos
if I've provided a solution, please mark the solution so others can find it
Guru Elite

Re: 6.2.1.0


msabin wrote:

After much arguing over what was a problem with our client configs and what was a problem with our controller configs and what was due specifically to the code upgrade, we agreed that the primary evidence of the problem we were seeing was that clients appeared to the controller at somewhat lower RSSI than the client thought. Thus the client would keep talking and the controller would de-auth.

 

Apparently there's an identified issue where the controller mis-perceives the RSSI as low and there's a possibility that that issue is getting addressed.

 

Just got word from support that 6.1.3.8 may be out by 4/19.


In the case, I do not see anywhere that support replicated your specific issue.  Replication of the issue is the first step.  Unless support could replicate your issue in-house, there would be no bug filed, no issue identified, and coincidentally, no fix.

 

I would not upgrade to 6.1.3.8 expecting a fix unless support has confirmed that they replicated it in-house first.

 

Quite frankly, there could be something specific to your environment that is causing the issue.  That would have to be identified, first.

 

 

 



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: