How to change operational status of a WLC-connected AP?

[Flavio Boniforti]

Hello everybody.

I'm noticing two of my 30+ APs having the 802.11a radio with "Operational Status = DOWN". The Admin Status is ENABLED, but I don't know where to act to put the op. stat. UP!

WLC is running 7.5.102.0, as well as the APs. The affected ones are 3502 models.

Any help will be much appreciated.

Thanks and regards,

Flavio.

[Sandeep Choudhary]

Hi

Paste the output from :

WLC: sh sysinfo

AP: sh inventory

Regards

[Flavio Boniforti]

Hello Sandeep.

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version.................................. 7.5.102.0

Bootloader Version............................... 1.0.16

Field Recovery Image Version..................... 7.0.112.21

Firmware Version................................. FPGA 1.7, Env 1.8, USB console                                               2.2

Build Type....................................... DATA + WPS

System Name...................................... VXWLC1

System Location.................................. Ibach, Serverraum 2

System Contact...................................

System ObjectID.................................. 1.3.6.1.4.1.9.1.1069

Redundancy Mode.................................. Disabled

IP Address....................................... 172.30.0.100

Last Reset....................................... Software reset

System Up Time................................... 36 days 21 hrs 46 mins 1 secs

System Timezone Location......................... (GMT +1:00) Amsterdam, Berlin,                                               Rome, Vienna

System Stats Realtime Interval................... 5

System Stats Normal Interval..................... 180

Configured Country............................... Multiple Countries:CH,US

Operating Environment............................ Commercial (0 to 40 C)

--More-- or (q)uit

Internal Temp Alarm Limits....................... 0 to 65 C

Internal Temperature............................. +44 C

External Temperature............................. +24 C

Fan Status....................................... OK

State of 802.11b Network......................... Enabled

State of 802.11a Network......................... Enabled

Number of WLANs.................................. 9

Number of Active Clients......................... 144

Burned-in MAC Address............................ 50:3D:E5:AE:92:A0

Power Supply 1................................... Present, OK

Power Supply 2................................... Present, OK

Maximum number of APs supported.................. 37

ap52#sh inv

NAME: "AP3500", DESCR: "Cisco Aironet 3500 Series (IEEE 802.11n) Access Point"

PID: AIR-CAP3502I-E-K9 , VID: V01, SN: FCZ1553W027

[Sandeep Choudhary]

Hi,

F
Configured Country............................... Multiple Countries:CH,US
ap52#sh inv
NAME: "AP3500", DESCR: "Cisco Aironet 3500 Series (IEEE 802.11n) Access Point"
PID: AIR-CAP3502I-E-K9 , VID: V01, SN: FCZ1553W027

Can you remove country code US from controlelr and then try again.

You have configured CH and US code on wlc.

Go to WIreless>Country and select only CH.

Your AP suggest it can only be usable in Europe.

Grüsse

Sandeep

[Flavio Boniforti]

Hello again.

I cannot remove US country code, as I also have APs in the US.

[Sandeep Choudhary]

okkkk then u dont need to remove.

Just check power injector state ...

If still failes then please console the AO and put the entire bootup process here.

Regards

[Leo Laohoo]

I cannot remove US country code, as I also have APs in the US.

You need to make a choice.  802.11a is disabled by the WLC because you have two CONFLICTING regulatory domain. 

You have but the following choices:

1.  Operate some of the APs in different countries as autonomous;

2.  Get another WLC and bunch your APs by regulatory domains

[Flavio Boniforti]

Hy Leo.

Are you sure I can't run this like I'm already doing? I mean, actually I have US and CH as regulatory domains. I have 30+ APs and they're distributed over european countries and US/Canada. The only ones showing the a-radio being down, are two 3502 located in the UK and having -E hardware...

I don't see why this is not working ONLY for those two...

Can you explain any further details?

Thanks,

Flavio.

[Leo Laohoo]

Are you sure I can't run this like I'm already doing? I mean, actually I have US and CH as regulatory domains. I have 30+ APs and they're distributed over european countries and US/Canada. The only ones showing the a-radio being down, are two 3502 located in the UK and having -E hardware...

Let me put it this way ...

US rules (from wireless to data communications) and European rules ALWAYS are not the same.  As long as you have the US regulatory domain enabled, only APs with the same regulatory domain as the US will join.  If you enable both US and European regulatory domain common sense dictates that only COMMON rules will be allowed.  In your case, only 802.11 b/g radios will be enabled and 802.11a/n radios will be disabled.

Don't believe me?  Disable US and see what happens.

[Flavio Boniforti]

Hi Leo.

I do believe you, but then my WLC is acting weird or playing tricks on me.

I have many -E hardware APs which have the a/n radios up and working, since years! As from your explanation, this shouldn't be working, right? AFAIU from your explanation, I shouldn't be seeing any of the APs with a/n radios UP, right?

So, what's wrong here?

F.

[Leo Laohoo]

As from your explanation, this shouldn't be working, right? AFAIU from your explanation, I shouldn't be seeing any of the APs with a/n radios UP, right?

You are running 7.5.102.0.  So this means that you've upgraded your firmware recently.  There was a bunch of new regulatory domain changes in 3Q2013. 

Could it be that when the WLC upgraded the firmware someone was not able to verify that all of your APs recovered with all radios up?

[Flavio Boniforti]

Hy Leo... that might as well be the case: I did the upgrade myself. I first of all pushed the images on the APs, then upgraded/rebooted the WLC and in fact I didn't care of checking for which radios were up or not.

Thus, we might agree on regulatory changes allowing now to use US and CH on the same WLC...

Still, I don't know how to get the a-radios UP again on those two APs: what do you suggest?

Regards,

F.

[Leo Laohoo]

Still, I don't know how to get the a-radios UP again on those two APs: what do you suggest?

Tell you what, prove me wrong.    Remove "US" from the country list and see what happens.  If 802.11a goes up then the same recommendations stands:

1.  Get another WLC and bunch all the same regulatory domain together; or

2.  Run the APs in autonomous

[Flavio Boniforti]

Hy Leo,

I would try this, but I think I might run into troubles: the US APs are -A hardware, thus I believe they wouldn't be able to join the WLC if I remove the US country code, right?

F.

[Leo Laohoo]

I would try this, but I think I might run into troubles: the US APs are -A hardware, thus I believe they wouldn't be able to join the WLC if I remove the US country code, right?

1.  This is just a test.  Once you see the effect then you can put it back.

2.  If the APs are already joined, then the worst you'll see are the radios go down.  But they won't get "kicked out" of the WLC.