Wireless Access

Reply

AOS 6.4 change in allowed-channels for AP125 in MX domain

We had a customer in Mexico who previously we had to exclude Ch 149-165 cause some of the clients did not connect to those channels.

Having just upgraded them to 6.4.2.5 I happen to notice that 75% of their APs, being AP125s were all in air monitor mode.

Now I see in the allowed-channels for the AP125 in MX that support for ch 36-48 is no longer included.

Why would that change between versions?  I understand this is a regulatory thing, but I can't find any mention of this in the release notes.


If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com
Guru Elite

Re: AOS 6.4 change in allowed-channels for AP125 in MX domain

I am on 6.4.4.1 and I get this output:

 

(Aruba7005-US) #show ap allowed-channels country-code mx ap-type AP-125

Allowed Channels for AP Type AP-125 Country Code "MX" Country "Mexico"
----------------------------------------------------------------------
PHY Type                 Allowed Channels
--------                 ----------------
802.11g (indoor)         1 2 3 4 5 6 7 8 9 10 11 12 13
802.11a (indoor)         149 153 157 161 165
802.11g (outdoor)        1 2 3 4 5 6 7 8 9 10 11 12 13
802.11a (outdoor)        149 153 157 161 165
802.11g 40MHz (indoor)   1-5 2-6 3-7 4-8 5-9 6-10 7-11 8-12 9-13
802.11a 40MHz (indoor)    149-153 157-161
802.11g 40MHz (outdoor)  1-5 2-6 3-7 4-8 5-9 6-10 7-11 8-12 9-13
802.11a 40MHz (outdoor)   149-153 157-161
802.11a (DFS)            None

I would type "show ap database long" and see if there is another issue.



Colin Joseph
Aruba Customer Engineering

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

Re: AOS 6.4 change in allowed-channels for AP125 in MX domain

In 6.3 I see this for the supported channels.

 

Allowed Channels for AP Type 125 Country Code "MX" Country "Mexico"
-------------------------------------------------------------------
PHY Type                 Allowed Channels
--------                 ----------------
802.11g (indoor)         1 2 3 4 5 6 7 8 9 10 11 12 13
802.11a (indoor)         36 40 44 48 52 56 60 64 149 153 157 161 165
802.11g (outdoor)        1 2 3 4 5 6 7 8 9 10 11 12 13
802.11a (outdoor)        36 40 44 48 52 56 60 64 149 153 157 161 165
802.11g 40MHz (indoor)   1-5 2-6 3-7 4-8 5-9 6-10 7-11
802.11a 40MHz (indoor)   36-40 44-48 52-56 60-64 149-153 157-161
802.11g 40MHz (outdoor)  1-5 2-6 3-7 4-8 5-9 6-10 7-11
802.11a 40MHz (outdoor)  36-40 44-48 52-56 60-64 149-153 157-161
802.11a (DFS)            52 56 60 64

No issues really, just that for about 6 weeks the site was essentially turned into a 2.4GHz only deployment.


If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com
Guru Elite

Re: AOS 6.4 change in allowed-channels for AP125 in MX domain

What is the exact version of 6.3?

 



Colin Joseph
Aruba Customer Engineering

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

Re: AOS 6.4 change in allowed-channels for AP125 in MX domain

I just checked now on 6.3.1.18. 

It was the same channel list in 6.1.3.4 which we upgraded from for the customer.


If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com
Guru Elite

Re: AOS 6.4 change in allowed-channels for AP125 in MX domain

Please open a TAC case so that they can look at your situation specifically.  Even if we identify an issue, your only choice may be to downgrade in the short term to restore those channels until it makes it into a DRT.  Looking at the difference between your output and my input, indicates there is a discrepancy somewhere.



Colin Joseph
Aruba Customer Engineering

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

Re: AOS 6.4 change in allowed-channels for AP125 in MX domain

Downgrading not really an option.  Have raised a case for TAC to look into it.

 


If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com

Re: AOS 6.4 change in allowed-channels for AP125 in MX domain

Turns out was a bug and those channels should never have been allowed in the first place.  It was corrected in 6.4.


If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: