Cisco WIRELESS LAN CONTROLLER OL-17037-01 - Manual (Page 26)

7-26
Cisco Wireless LAN Controller Configuration Guide
OL-17037-01
Chapter 7 Controlling Lightweight Access Points
Autonomous Access Points Converted to Lightweight Mode
You can view join-related information for the following numbers of access points:
• Up to 300 access points for 4400 series controllers, the Cisco WiSM, and the Catalyst 3750G
Integrated Wireless LAN Controller Switch
• Up to three times the maximum number of access points supported by the platform for the 2100
series controllers and the Controller Network Module within the Cisco 28/37/38xx Series Integrated
Services Routers
When the controller is maintaining join-related information for the maximum number of access points,
it does not collect information for any more access points.
An access point sends all syslog messages to IP address 255.255.255.255 by default when any of the
following conditions are met:
• An access point running software release 4.2 or later has been newly deployed.
• An existing access point running a software release prior to 4.2 has been upgraded to 4.2 or a later
release.
• An existing access point running software release 4.2 or later has been reset after clearing the
configuration.
If any of these conditions are met and the access point has not yet joined a controller, you can also
configure a DHCP server to return a syslog server IP address to the access point using option 7 on the
server. The access point then starts sending all syslog messages to this IP address.
You can also configure the syslog server IP address through the access point CLI, provided the access
point is currently not connected to the controller. The relevant command is lwapp ap log-server
syslog_server_IP_address.
When the access point joins a controller for the first time, the controller pushes the global syslog server
IP address (the default is 255.255.255.255) to the access point. After that, the access point sends all
syslog messages to this IP address, until it is overridden by one of the following scenarios:
• The access point is still connected to the same controller, and the global syslog server IP address
configuration on the controller has been changed using the config ap syslog host global
syslog_server_IP_address command. In this case, the controller pushes the new global syslog server
IP address to the access point.
• The access point is still connected to the same controller, and a specific syslog server IP address has
been configured for the access point on the controller using the config ap syslog host specific
Cisco_AP syslog_server_IP_address command. In this case, the controller pushes the new specific
syslog server IP address to the access point.
• The access point gets disconnected from the controller, and the syslog server IP address has been
configured from the access point CLI using the lwapp ap log-server syslog_server_IP_address
command. This command works only if the access point is not connected to any controller.
• The access point gets disconnected from the controller and joins another controller. In this case, the
new controller pushes its global syslog server IP address to the access point.
Whenever a new syslog server IP address overrides the existing syslog server IP address, the old address
is erased from persistent storage, and the new address is stored in its place. The access point also starts
sending all syslog messages to the new IP address, provided the access point can reach the syslog server
IP address.
You can configure the syslog server for access points and view the access point join information only
from the controller CLI.