Unable to stop the event logs on access point console

[Vikas Gundu]

Hi team,

I have an AIR-LAP1131AG-E-K9 access point having ios c1130-k9w8-mx.124-21a.JHB1.

When I am trying to take the console of it there are many logs generated like LWAPP ...Go join the controller, Discover controller etc. and the ap is unable to register to the controller(2112 with ios version 6.0.199.4). I'm trying to enter the command but there are many event msg generated....How do i stop this event log. I tried entering the command no debug all. but still there are many logs...

I want to enter the the following commands

#lwapp ap  ip address <ip addr>.

#lwapp a pip default-gateway <gateway ip addr>

#lwapp ap controller ip addr <controller ip>

#wr me

Revert me back on urgent basis

Thanks in advance..

[Rasika Nayanajith]

I do not think you can stop these log messages on console in LAP.

Try put the AP on same vlan as WLC management. If it is not DHCP subnet, then try to add a static IP & see.

HTH

Rasika

**** Pls rate all useful responses ***

[Scott Fella]

Just to add, there is no write mem on a lightweight access point. If you are trying to enter those commands or any other, write it on a notepad and copy and paste your commands. The commands will still enter even if the logs are being generated. 

Like Rasika mentioned, it's probably be best to put the access points on the same calm as the WLC management and make sure that their is a dhcp scope on that subnet. This way the APs get a dhcp address and will join and download the image. One this happens and the ap is in a run state, you can set a static if you want and move the ap to a different Vlan. Your better off to not set a static until you have put the ap in the Vlan you want. 

Scott

[Vikas Gundu]

Thanks Scott,

Now the access point got registered to the controller..This happened because of country Code..

I have changed the country code to UK, Belgium it started working fine.

Initially when it was IN the access point was not getting register..

But now the problem which arised is that the user is unable to get authenticated to the radius server.

Radius server is reachable and we have done every changes required for radius server authentication.

Users are getting rejected.

Customer is saying that the radius server is in IN domain and the WLC/access point is in UK,BE and hence the users are unable to connect..

Is it so??

Rply

Thanks in advance...

[Vikas Gundu]

Thanks Rashika,

Now the access point got registered to the controller..This happened becuse of country Code..

I have changed the country code to UK, Belgium it started working fine.

Initially when it was IN the access point was not getting register..

But now the problem which arised is that the user is unable to get authenticated to the radius server.

Radius server is reachable and we have done every changes required for radius server authentication.

Users are getting rejected.

Customer is saying that the radius server is in IN domain and the WLC/access point is in UK,BE and hence the users are unable to connect..

Is it so??

Rply

Thanks in advance...

[Rasika Nayanajith]

What does RADIUS logs say about client failure ? that is the best place to start troubleshooting

HTH

Rasika

[robert.reho]

Hi

If you connected via console cable to the AP, then:

logging console disable

I hope it's help.

[cfraguio]

This worked for me in an Cisco AP connected through consle cable with putty, thank you

[sbhadrav@cisco.com]

Cisco IOS Lightweight Access Point Protocol (LWAPP) access points have a default password of Cisco, and the pre-stage configuration for LWAPP access points is disabled by default. To enable it, you must configure the access point with a new username and password when it joins the controller. Enter this command using the controller CLI to push a new username and password to the access point:

config ap mgmtuser add user_id password password {Cisco_AP | all}

The Cisco_AP parameter configures the username and password on the specified access point.
The all parameter configures the username and password on all the access points registered to the controller.
The password pushed from the controller is configured as “enable password” on the access point.

There are some cases where the pre-stage configuration for LWAPP access points is disabled and the access point displays the following error message when the CLI commands are applied:

“ERROR!!! Command is disabled.”

For more information, see the Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode.