Operational Status goes down for Radio Interface

Unanswered Question
Oct 13th, 2008

Hi All,

Need your help in understanding why the operational status of many LWAPP is showing down. Even i tried to enable admin status to enable but it gives a pop up Error in enabling Admin Status & again it goes to down.

The logs which i got is pasted below:

Oct 14 12:53:44.067 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:28:90 due to radio policy.

Oct 14 12:53:41.691 1x_auth_pae.c:2470 DOT1X-1-MAX_EAP_IE_RETRIES_REACHED: Reached Max EAP-Identity Request retries (21) for STA00:22:5f:1d:93:db

Oct 14 12:53:41.466 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:2d:b0 due to radio policy.

Oct 14 12:53:38.615 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:16:a0 due to radio policy.

Oct 14 12:53:33.834 spam_lrad.c:1287 LWAPP-0-MSGTAG095: Discarding Discovery Request Packet from AP 00:22:0d:e1:28:90

Oct 14 12:53:33.834 spam_lrad.c:4589 LWAPP-0-MSGTAG094: Received Discovery Request from AP 00:22:0d:e1:28:90 requesting OTAP but OTAP is disabled

Oct 14 12:53:32.058 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:28:c0 due to radio policy.

Oct 14 12:53:31.234 spam_lrad.c:1287 LWAPP-0-MSGTAG095: Discarding Discovery Request Packet from AP 00:22:0d:e1:2d:b0

Oct 14 12:53:31.233 spam_lrad.c:4589 LWAPP-0-MSGTAG094: Received Discovery Request from AP 00:22:0d:e1:2d:b0 requesting OTAP but OTAP is disabled

Oct 14 12:53:30.401 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:2c:d0 due to radio policy.

Oct 14 12:53:30.400 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:2d:80 due to radio policy.

Oct 14 12:53:28.430 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:2d:90 due to radio policy.

Oct 14 12:53:25.000 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:2f:b0 due to radio policy.

Oct 14 12:53:21.870 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e0:c1:30 due to radio policy.

Oct 14 12:53:20.033 spam_lrad.c:1287 LWAPP-0-MSGTAG095: Discarding Discovery Request Packet from AP 00:22:0d:e1:2c:d0

Oct 14 12:53:20.032 spam_lrad.c:4589 LWAPP-0-MSGTAG094: Received Discovery Request from AP 00:22:0d:e1:2c:d0 requesting OTAP but OTAP is disabled

Oct 14 12:53:19.782 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:26:00 due to radio policy.

Oct 14 12:53:19.020 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:05:c0 due to radio policy.

Oct 14 12:53:18.197 spam_lrad.c:1287 LWAPP-0-MSGTAG095: Discarding Discovery Request Packet from AP 00:22:0d:e1:2d:90

Oct 14 12:53:18.197 spam_lrad.c:4589 LWAPP-0-MSGTAG094: Received Discovery Request from AP 00:22:0d:e1:2d:90 requesting OTAP but OTAP is disabled

Oct 14 12:53:15.710 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:35:f0 due to radio policy.

Oct 14 12:37:09.324 hwutils.c:2159 INIT-0-MSGTAG007: Security Module not found.

Oct 14 12:37:08.554 bootos.c:874 INIT-0-MSGTAG001: Starting code...

Thanks in advance....

Regards,

Piyush

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (5 ratings)
Loading.
piyush_singh Mon, 10/13/2008 - 23:52

I had even tried to Set AP to Factory Defaults & configured it again, also checked for the countory code on WLC & in wireless ap settings it shows me same.

Cisco Wireless Access Point details are:

AP PID - AIR-LAP1242AG-N-K9

S/W Version - 4.1.185.0

IOS Version - 12.4(3g)JA2

For WLC:

Model No. - AIR-WLC4402-25-K9

Software Version 4.1.185.0

Regards,

Piyush

piyush_singh Tue, 10/14/2008 - 01:49

I had rebooted the LAP which were showing there radio interfaces down & got this in log:

Oct 14 15:15:57.650 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:05:c0 due to radio policy.

Oct 14 15:15:49.246 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:35:f0 due to radio policy.

Oct 14 15:15:43.189 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e0:c1:30 due to radio policy.

Oct 14 15:15:35.380 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:28:c0 due to radio policy.

Oct 14 15:15:01.991 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:16:a0 due to radio policy.

Oct 14 15:14:43.580 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:2d:80 due to radio policy.

Oct 14 15:14:00.150 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:05:c0 due to radio policy.

Oct 14 15:13:48.282 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:35:f0 due to radio policy.

Oct 14 14:21:16.732 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e0:c1:30 due to radio policy.

Oct 14 14:19:14.646 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:28:c0 due to radio policy.

Oct 14 12:53:44.067 apf_spam.c:930 APF-1-NOT_ADV_SSID_ON_AP: Not advertising SSID Behr_User on AP 00:22:0d:e1:28:90 due to radio policy.

May be this can help u..

jeff.kish Tue, 10/14/2008 - 11:29

Unfortunately, these obscure errors are, well, obscure :) I've never seen anything like it, and if no one has replied then I guess that most people are the same way.

I would open a TAC case with Cisco and see what they say. Otherwise, try updating the firmware on the APs, or maybe try reverting one back to autonomous, then reupgrade it to lightweight. Looks like you've already tried rebooting it and returning it to factory defaults. Have you tried using these access points with a different controller? Maybe it's a controller issue.

Sorry I don't have a better answer. Best of luck!

piyush_singh Wed, 10/15/2008 - 02:00

Hi All,

The problem is resolved. I dont know what was the case but it resolved after i selected the Power injecters setting in LAP & in that already installed & the rebooted the LAP. After it came up all the radio interfaces were up.

Regards,

Piyush

jeff.kish Wed, 10/15/2008 - 05:30

Thanks for letting us know! It's strange that power was the problem since usually the errors will state something about being in low-power mode.

George Stefanick Fri, 02/12/2010 - 08:23

Another indicator if it a power issue. The AP interface is UP. Meaning you can access the AP. However the RADIOs are DOWN. and when you

try to enable them. They just wont come up. Good call on the power ...

jbonaccidp Wed, 09/08/2010 - 10:53

I had the same prolem and Uncheck “Power Injector State” and click apply then reboot AP (Under Wireless > Access Points > All AP’s > Advanced) The switched it back to Installed and clicked apply and the AP came back up. Not sure of this reason as well since there are three other AP's on this controller.

jezzbird69 Fri, 08/14/2015 - 09:50

I had the same problem but with APs drawing power using POE from Cat 3850s. I solved it by doing the following:

(1) Enable SSH and username/password on APs. (using cat 3850 cli)

(2) SSH to AP and run debug capwap console cli command.

(3) Type conf t in the usual way

(4) Go into each radio interface and type no shut

 

I tried enabling the interfaces form the webui but it didn't work. Also changing the power injector settings for the webui did not work. :(

Isuru Manikkage Mon, 11/30/2015 - 18:43

Hi All,

I am facing this issue on WLC 5508 on firmware 8.0.120.0 for AIR-LAP1242AG-P-K9 APs. At least once a week I notice few APs have 802.11a radio operational status is down. But radio admin status is enabled.
So what I do it disable and enable back the admin status, then the operational status will come back to UP.
But issue is repeating around once a week. Any idea please?

Thank you.

loudguitars Fri, 02/12/2010 - 06:35

Thanks for posting your solution. I ran into the exact same problem and, since we let the SmartNet contract expire (Oops!) I couldn't open a TAC case. Your solution saved me hours of troubleshooting.

Cheers!

Dan

diego porez Wed, 01/23/2013 - 13:22

HI man..

it was really helpful, i had the same problem and it was solved with the power injector state check box. (override).

1. enable the box (power injector - override).

2. reload the AP.

3. enable the admin status check box.-- wireless-- radios-- configure--- admin status

rsmit1508 Thu, 03/06/2014 - 13:32

The Power Injector check still works. Just worked for me after upgrading the software on our WLAN Controller, some of the APs didn't come up. The aformentioned solution worked for me.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode