China-CCIE→Cisco经典文档→无线 LAN 控制器 (WLC) 配置最佳实践

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Best Practices
      Wireless/RF
      Network Connectivity
      Network Design
      Mobility
      Security
      General Administration
      How to Transfer the WLC Crash File from the WLC CLI to the TFTP Server
      Upload core dump file to an FTP server

Introduction

This document offers short configuration tips that cover several Wireless Unified Infrastructure issues commonly seen in the Technical Assistance Center (TAC).

The objective is to provide important notes that you can apply on most network implementations in order to minimize possible problems.

Note: Not all networks are equal, therefore some tips might not be applicable on your installation. Always verify them before you perform any changes on a live network.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

Knowledge of how to configure the Wireless LAN Controller (WLC) and Lightweight Access Point (LAP) for basic operation
Basic knowledge of Lightweight Access Point Protocol (LWAPP) and wireless security methods

Components Used

The information in this document is based on these software and hardware versions:

Cisco 2000 / 2100 / 4400 Series WLC that runs firmware 4.2 or 5.0
LWAPP based Access Points, series 1230, 1240, 1130, 10x0 and 1510

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Best Practices

Wireless/RF

These are the best practices for wireless/radio frequency (RF):

For any wireless deployment, always do a proper site survey to insure proper quality of service for your wireless clients. The requirements for voice or location deployments are more strict than for data services. Auto RF might help on channel and power settings management, but it cannot correct a bad RF design.
The site survey must be done with devices that match the power and propagation behavior of the devices to be used on the real network. For example, do not use a 350 802.11B radio with omni antenna to study coverage if the final network uses 1240 dual radios for 802.11A and G.
In the same related idea, limit the number of service set identifiers (SSIDs) configured at the controller. Based on your access point model, you can have configured 8 or 16 simultaneous SSIDs, but as each WLAN/SSID needs separated probe responses, and beaconing, the RF pollution increases as more SSIDs are added. The results are that some smaller wireless stations like PDA, WiFi Phones and barcode scanners cannot cope with a high number of basic SSID (BSSID) information. This results in lockups, reloads or association failures. Also the more SSIDs, the more beaconing needed, so less RF space is available for real data transmits.
For RF environments that are clear spaces, like factories where there are access points in a large space without walls, it might be necessary to adjust the Transmit Power Threshold from the default of -65 dBm, to a lower value like -76 dBm. This allows you to lower the co-channel interference (number of BSSID heard from a wireless client in a given moment). The best value is dependant on each site environmental characteristics, so it should be evaluated carefully with a site survey.

Power Transmit Threshold—This value, expressed in dBm, is the cut-off signal level at which the Transmit Power Control (TPC) algorithm adjusts the power levels downward, such that this value is the strength at which the third strongest neighbor of an AP is heard.
Some 802.11 client software might encounter difficulties if it hears more than a certain fixed number of BSSIDs (for example, 24 or 32 BSSIDs.) When you reduce the transmit power threshold and hence the average AP transmit level, you can reduce the number of BSSIDs that such clients hear.
Do not enable aggressive load balancing unless the network has available a high density of access points in the area, and never if there is voice over wireless. If you enable this feature with access points spaced to far away from each other, it might confuse the roaming algorithm of some clients, and induce coverage holes in some cases. In the latest software versions, this feature is disabled by default. Bear in mind that it must not be used for voice networks, and that some older clients can have problems understanding the load balancing response from the AP.

Network Connectivity

These are the best practices for network connectivity:

Do not use spanning tree on controllers.

For most topologies, Spanning Tree Protocol (STP) that runs in the controller is not needed. STP is disabled by default.

For non-Cisco switches, it is also recommended that you also disable STP on a per port basis.

Use this command in order to verify:

Cisco Controller) >show spanningtree switch 

STP Specification...................... IEEE 802.1D
STP Base MAC Address................... 00:18:B9:EA:5E:60
Spanning Tree Algorithm................ Disable 
STP Bridge Priority.................... 32768
STP Bridge Max. Age (seconds).......... 20
STP Bridge Hello Time (seconds)........ 2
STP Bridge Forward Delay (seconds)..... 15

Although most of controller configuration is applied "on the fly", it is good idea to reload controllers after you change the following configuration settings:
- Management address
- SNMP configuration—This is very important if you use older software.
Generally, management interface of the WLC is left untagged. In this case, the packet sent to and from the management interface assumes the Native VLAN of the trunk port to which the WLC is connected. However, if you want management interface to be on a different VLAN, tag it to the appropriate VLAN using the <Cisco Controller> config interface vlan management <vlan-id> command. Make sure that corresponding VLAN is allowed on the port.
For all trunk ports that connect to the controllers, filter out the VLANs that are not in use.

For example in Cisco IOS® switches, if the management interface is on VLAN 20, plus VLAN 40 and 50 are used for two different WLANs, use this configuration command at the switch side:
```
switchport trunk allowed vlans 20,40,50
```

Do not leave an interface with a 0.0.0.0 address, for example an unconfigured service port. It might affect DHCP handling in the controller.

This is how you verify:

(Cisco Controller) >show interface summary             
Interface Name        Port  Vlan Id   IP Address       Type     Ap Mgr
--------------------  ----  --------  ---------------  -------  ------
ap-manager            LAG   15        192.168.15.66    Static   Yes 
example               LAG   30        0.0.0.0          Dynamic  No    
management            LAG   15        192.168.15.65    Static   No    
service-port          N/A   N/A       10.48.76.65      Static   No    
test                  LAG   50        192.168.50.65    Dynamic  No    
virtual               N/A   N/A       1.1.1.1          Static   No

Do not use LAG unless all ports of the controller have the same Layer 2 configuration on the switch side. For example, avoid filtering some VLANs in one port, and not the others.
When you use LAG, the controller relies on the switch for the load balancing decisions on traffic that comes from the network. It expects that traffic that belongs to an AP (LWAPP or network to wireless user) always enters on the same port. Use only ip-src or ip-src ip-dst load balancing options in the switch EtherChannel configuration. Some switch models might use unsupported load balancing mechanisms by default, so it is important to verify.

This is how to verify the EtherChannel load balancing mechanism:
```
switch#show etherchannel load-balance 
EtherChannel Load-Balancing Configuration:
src-dst-ip

EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address
IPv6: Source XOR Destination IP address
```
This is how to change the switch configuration (IOS):
```
switch(config)#port-channel load-balance src-dst-ip 
```
With the Cisco IOS Software Release 12.2(33)SXH6, there is an option for PFC3C mode chassis to exclude VLAN in the Load-distribution . Use the port-channel load-balance src-dst-ip exclude vlan command in order to implement this feature. This feature ensures that traffic that belongs to a LAP that enters on the same port.
LAG while using VSS, or stacked switch (3750/2960), should work, as long as the fragments of an IP packet are sent to the same port. The idea is that if you go to multiple switches, the ports must belong to the same L2 “entity” with regards of load balancing decisions.
If you want to connect the WLC to more than one switch, you must create an AP-manager for each physical port. This provides redundancy and scalability.

Note: On Cisco 4400-100 model WLCs , you need atleast three active physical ports in order to utilize the maximum capacity of 100 access points for each WLC. For Cisco 4400-50 model WLCs, you need two physical ports in order to utilize the maximum capacity of 50 access points for each WLC.
Whenever possible, do not create a backup port for an AP-manager interface, even if it is allowed in older software versions. The redundancy is provided by the multiple AP-manager interfaces as mentioned earlier in this document.

For multicast forwarding, the best performance and less bandwidth utilization is achieved through multicast mode.

This is how to verify the multicast mode on the controller:

(WiSM-slot1-1) >show network summary

RF-Network Name............................. 705
Web Mode.................................... Enable
Secure Web Mode............................. Enable
Secure Web Mode Cipher-Option High.......... Disable
Secure Shell (ssh).......................... Enable
Telnet...................................... Enable
Ethernet Multicast Mode..................... Enable   Mode: Mcast  239.0.1.1
Ethernet Broadcast Mode..................... Disable
IGMP snooping............................... Disabled
IGMP timeout................................ 60 seconds
User Idle Timeout........................... 300 seconds
ARP Idle Timeout............................ 300 seconds
ARP Unicast Mode............................ Disabled
Cisco AP Default Master..................... Disable
Mgmt Via Wireless Interface................. Disable
Mgmt Via Dynamic Interface.................. Disable
Bridge MAC filter Config.................... Enable
Bridge Security Mode........................ EAP
Over The Air Provisioning of AP's........... Enable
Apple Talk ................................. Disable
AP Fallback ................................ Enable

This is how to change the switch configuration (IOS):

config network multicast mode multicast 239.0.1.1
config network multicast global enable

The multicast address is used by the controller in order to forward traffic to access points. It is important that it does not match another address in use on your network by other protocols. For example, if you use 224.0.0.251, it breaks mDNS used by some third party applications. It is recommended that the address be on the private range (239.0.0.0-239.255.255.255, which does not include 239.0.0.x and 239.128.0.x.)
If the access points are on a different subnetwork than the one used on the management interface, your network infrastructure must provide multicast routing between the management interface subnet, and the AP subnetwork.

Network Design

These are the best practices for network design:

Limit the number of access points per VLAN. A good number is around 60 to 100 if you use a later code version. This helps to minimize reassociation problems in case of network failure. Cisco IOS based APs can be deployed on higher densities subnetworks. Always make sure that the underlying layer 2 and layer 3 topology is properly configured (spanning tree, loadbalancing, and so forth).
For APs in local mode, configure the switch port with portfast. In order to do this, set the port to be connected as a “host” port (switchport host command), or directly with the portfast command. This allows faster join process for AP. There is no risk of loops, as the LWAPP AP never bridge between VLANs.
In relation to the first tip, do not put more than 20 access points in the same VLAN with the management interface of the controller, unless you use 4.2.112.0 or later code. It is possible that due to a high number of broadcast messages generated by the access points, some discovery messages are dropped and this results in a slower access point joining processes.
Per design, most of the CPU initiated traffic is sent from the management address in the controller. For example, SNMP traps, RADIUS authentication requests, multicast forwarding, and so forth.

The exception to this rule is DHCP related traffic, which is sent from the interface related to the WLAN settings, for controller software version 4.0 and later. For example, if a WLAN uses a dynamic interface, the DHCP request is forwarded using this Layer 3 address.

This is important to take into account when you configure firewall policies or design the network topology. It is important to avoid configuring a dynamic interface in the same sub network as a server that has to be reachable by the controller CPU, for example a RADIUS server, as it might cause asymmetric routing issues.

Mobility

These are the best practices for mobility:

All controllers in a mobility group should have the same IP address for a virtual interface, for example 1.1.1.1. This is important for roaming. If all the controllers within a mobility group do not use the same virtual interface, inter-controller roaming can appear to work, but the hand-off does not complete, and the client loses connectivity for a period of time.

This is how to verify:

(Cisco Controller) >show interface summary             

Interface Name      Port   Vlan Id   IP Address       Type     Ap Mgr
-----------------   -----  --------  ---------------  -------  ------
ap-manager           LAG   15        192.168.15.66    Static   Yes 
management           LAG   15        192.168.15.65    Static   No    
service-port         N/A   N/A       10.48.76.65      Static   No    
test                 LAG   50        192.168.50.65    Dynamic  No    
virtual              N/A   N/A       1.1.1.1          Static   No

The virtual gateway address must be not routable inside your network infrastructure. It is only intended to be reachable for a wireless client when connected to a controller, never from a wired connection.
All controllers must be configured for the same LWAPP transport mode (Layer 2 or Layer 3).
IP connectivity must exist between the management interfaces of all controllers.
In most situations, all controllers must be configured with the same mobility group name. For example, in the Cisco WiSM, both controllers must be configured with the same mobility group name for seamless routing among 300 access points. Exceptions to this rule are deployments on controllers for the Guest Access feature, typically on DMZ.
All controllers must run the same version of controller software. The only accepted exception for this rule is a controller that currently runs a 4.2.112.0 as anchor in a Guest Access DMZ controller scenario to controllers that run at least 4.1.185.0
You must have gathered the MAC address and IP address of every controller that is to be included in the mobility group. This information is necessary because you configure all controllers with the MAC address and IP address of all the other mobility group members. You can find the MAC and IP addresses of the other controllers to be included in the mobility group on the Controller > Mobility Groups page of the GUI of each controller.
Do not create unnecessarily large mobility groups. A mobility group should only have all controllers that have access points in the area where a client can physically roam, for example all controllers with access points in a building. If you have a scenario where several buildings are separated, they should be broken into several mobility groups. This saves memory and CPU, as controllers do not need to keep large lists of valid clients, rogues and access points inside the group, which would not interact anyway.

Also, try to accommodate the AP distribution across controllers in the mobility group so that there are APs for example, per floor, per controller, and not a salt and pepper distribution. This reduces inter-controller roaming, which has less impact on the mobility group activity.

Also, if using the 5.x version, you can add the multicast mobility feature in order to reduce the traffic needed to do client announce during roaming/association. For more information, refer to the Messaging among Mobility Groups section of the Cisco Wireless LAN Controller Configuration Guide, Release 5.2.

Keep in mind that WLC redundancy is achieved through the mobility groups. So it might be necessary in some situations to increase the mobility group size, including additional controllers for redundancy (N+1 topology for example).
In scenarios where there is more than one controller in a mobility group, it is normal to see some rogue access point alerts about our own access points in the network after a controller reload. This happens due to the time it takes to update the access point, client and rogue lists between mobility group members.

The DHCP Required option in WLAN settings allows you to force clients to do a DHCP address request/renew every time they associate to the WLAN before they are allowed to send or receive other traffic to the network. From a security standpoint, this allows for a more strict control of IP addresses in use, but also might have affects in the total time for roaming before traffic is allowed to pass again.

Additionally, this might affect some client implementations which do not do a DHCP renew until the lease time expires. For example, Cisco 7920 or 7921 phones might have voice problems while they roam if this option is enabled, as the controller does not allow voice or signaling traffic to pass until the DHCP phase is completed. Some third-party printer servers might also be affected. In general, it is a good idea not to use this option if the WLAN has non-Windows clients. This is because the more strict controls might induce connectivity issues, based on how the DHCP client side is implemented. This is how you verify:

(Cisco Controller) >show wlan 1                  


WLAN Identifier.................................. 1
Profile Name..................................... 4400
Network Name (SSID).............................. 4400
Status........................................... Enabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Number of Active Clients......................... 0
Exclusionlist Timeout............................ 60 seconds
Session Timeout.................................. 1800 seconds
Interface........................................ management
WLAN ACL......................................... unconfigured
DHCP Server...................................... Default
DHCP Address Assignment Required................. Disabled 
Quality of Service............................... Silver (best effort)
WMM.............................................. Disabled
CCX - AironetIe Support.......................... Enabled
CCX - Gratuitous ProbeResponse (GPR)............. Disabled
Dot11-Phone Mode (7920).......................... Disabled
Wired Protocol................................... None

If you use Layer 3 roaming, for example a subnet for one WLAN on one controller does not match the subnet on another controller, or AP-Groups, it is recommended that symmetric mobility is enabled on all controllers in order to avoid issues with asymmetrical routing. This is very important if your network has firewalls with state control, as they disrupt the traffic flow. This setting must be the same across all controllers in the same mobility group.

This is how to verify:

(Cisco Controller) >show mobility summary 

Symmetric Mobility Tunneling (current) .......... Disabled
Symmetric Mobility Tunneling (after reboot) ..... Disabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... 100
Mobility Keepalive interval...................... 10
Mobility Keepalive count......................... 3
Mobility Group members configured................ 1

Controllers configured in the Mobility Group

 MAC Address        IP Address       Group Name         Status

 00:16:9d:ca:e4:a0    192.168.100.28   100              Up

This is how to configure:

config mobility symmetric-tunneling enable

Note: You must reboot the controller in order for this to take effect.

If you use 5.0 code or later, it is advisable to configure multicast-mode for mobility. This allows client announce messages to be sent on multicast between mobility peers, instead of unicast sent to each controller, with benefits on time, CPU usage and network utilization.

This is how to verify:

(WiSM-slot1-1) >show mobility summary 

Symmetric Mobility Tunneling (current) .......... Disabled
Symmetric Mobility Tunneling (after reboot) ..... Disabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... 705
Multicast Mode .................................. Enabled
Mobility Domain ID for 802.11r................... 0x8e5e
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 2
Mobility Control Message DSCP Value.............. 0

Controllers configured in the Mobility Group

 MAC Address        IP Address       Group Name         Multicast IP         Status

 00:14:a9:bd:da:a0    192.168.100.22   705              239.0.1.1        Up

 00:19:06:33:71:60    192.168.100.67   705              239.0.1.1        Up

Security

These are the best practices for security:

It is good idea to change the RADIUS timeout to 5 seconds. The default of 2 seconds is acceptable for a fast RADIUS failover, but probably not enough for Extensible Authentication Protocol-Transport Layer Security (EAP-TLS) authentication, or if the RADIUS server has to contact external databases (Active Directory, NAC, SQL, and so forth).

This is how to verify:

(Cisco Controller) >show radius summary 
Vendor Id Backward Compatibility............ Disabled
Credentials Caching......................... Disabled
Call Station Id Type........................ IP Address
Administrative Authentication via RADIUS.... Enabled
Aggressive Failover......................... Disabled
Keywrap..................................... DisabledAuthentication Servers


!--- This portion of code has been wrapped to several lines due to spatial
!--- concerns.

Idx  Type  Server Address    Port    State    Tout RFC3576
---  ----  ----------------  ------  --------  ----  -------
1    N     10.48.76.50       1812    Enabled   2    Enabled

IPSec -AuthMode/Phase1/Group/Lifetime/Auth/Encr
------------------------------------------------
Disabled - none/unknown/group-0/0 none/none

This is how to configure:

config radius auth retransmit-timeout 1 5

Check on the SNMPv3 default user. By default, the controller comes with a username that should be disabled or changed.

This is how to verify:
```
(Cisco Controller) >show snmpv3user 

SNMP v3 User SNMP v3 User Name AccessMode Authentication Encryption 
-------------------- ----------- -------------- ---------- 
default Read/Write HMAC-MD5 CBC-DES 
```
This is how to configure:
```
config snmp v3user delete default
config snmp v3user create nondefault rw hmacsha des authkey encrkey
```
Keep in mind that your SNMP settings must match between the controller and the Wireless Control System (WCS). Also, you should use an encryption and hash keys that match your security policies.
When you perform web authentication with an external authentication page, do not use a server which has a web server and a proxy server at the same time to host the login page. The controller allows HTTP traffic from the wireless client to the server before authentication is complete. This allows the client to navigate using the proxy service present on the server.
In the controllers, the default timeout for the EAP Identity request is 1 second, which is not enough for some situations like One Time Passwords, or Smart Card implementations, where the user is prompted to write a PIN or password before the wireless client can answer the identity request. In autonomous access points, the default is 30 seconds, so this should be taken into account while you migrate autonomous to infrastructure wireless networks.

This is how to change:
```
config advanced eap identity-request-timeout 30
```
On aggressive environments, a helpful feature is to enable access point authentication with a threshold of 2. This permits both to detect possible impersonation and minimize false positive detections.

This is how to configure:
```
config wps ap-authentication enable
config wps ap-authentication threshold 2
```
In relation to the previous tip, Management Frame Protection (MFP) can also be used to authenticate all 802.11 management traffic detected between nearby access points in the wireless infrastructure. Take into consideration that some common third party wireless cards have problems in their driver implementation that do not handle correctly the extra information elements added by MFP. Make sure you use the latest drivers from your card manufacturer before you test and use MFP.
NTP is very important for several features. It is mandatory to use NTP synchronization on controllers if you use any of these features: Location, SNMPv3, access point authentication, or MFP.

This is how to configure:
```
config time ntp server 1 10.1.1.1
```
In order to verify, check for entries like this in your traplog:
```
30 Tue Feb 6 08:12:03 2007 Controller time base status - 
Controller is in sync with the central timebase. 
```
When using Protected EAP-Microsoft Challenge Handshake Authentication Protocol version 2 (PEAP-MSCHAPv2), with Microsoft XP SP2, and the wireless card is managed by the Microsoft Wireless Zero Configuration (WZC), you should apply the Microsoft hotfix KB885453 . This prevents several issues on authentication related with PEAP Fast Resume.
If, for security reasons, the wireless clients should be separated in several sub networks, each one with different security policies, it is good idea to use one or two WLANs (for example, each one has a different Layer 2 encryption policy), together with the AAA-Override feature. This feature allows you to assign per user settings. For example, move the user to either a specific dynamic interface in a separated VLAN, or apply a per user Access Control List.
Although the controller and access points do support WLAN with SSID using Wi-Fi Protected Access (WPA) and WPA2 simultaneously, it is very common that some wireless client drivers cannot handle complex SSID settings. In general, it is a good idea to keep the security policies simple for any SSID, for example, using one WLAN/SSID with WPA and Temporal Key Integrity Protocol (TKIP), plus a separated one with WPA2 and Advanced Encryption Standard (AES).

General Administration

These are the best practices for General Administration:

In general, before any upgrade it is a good idea to do a binary backup of the configuration. WLCs support the conversion of older configuration information into new versions, but there is no support for the reverse process. This applies both to major or minor version changes.
The use of a newer configuration into an older release might lead to missing settings (access lists, interfaces, and so forth), or on incorrectly working features. If you need to downgrade a controller, it is advisable that after the downgrade, you clear the configuration, configure back the management interface address, and load the binary backup file by TFTP.
If you downgrade from a version with an XML configuration file (for example 4.2, 5.0) to a binary configuration file (4.0, 4.1), the controller erases the configuration, and you are presented with the setup wizard after the first boot. This is intentional.

It is advisable to always configure controller names into the AP settings, so you can control the controllers that are selected to join first by the AP. You can this verify with:

(WiSM-slot1-1) >show ap config general AP1130-9064

Cisco AP Identifier.............................. 164
Cisco AP Name.................................... AP1130-9064
Country code..................................... BE  - Belgium
Regulatory Domain allowed by Country............. 802.11bg:-E     802.11a:-E
AP Country code.................................. BE  - Belgium
AP Regulatory Domain............................. 802.11bg:-E    802.11a:-E 
Switch Port Number .............................. 29
MAC Address...................................... 00:16:46:f2:90:64
IP Address Configuration......................... DHCP
IP Address....................................... 192.168.100.200
IP NetMask....................................... 255.255.255.0
Gateway IP Addr.................................. 192.168.100.1
Telnet State..................................... Disabled
Ssh State........................................ Disabled
Cisco AP Location................................ default location
Cisco AP Group Name.............................. default-group
Primary Cisco Switch Name........................ Cisco_ea:5e:63
Primary Cisco Switch IP Address.................. Not Configured
Secondary Cisco Switch Name...................... 
Secondary Cisco Switch IP Address................ Not Configured
Tertiary Cisco Switch Name.......................

In order to set this value (remember it is the system name, not the DNS name):

config ap primary-base Cisco_ea:5e:63

In versions later than 4.2, the AP can use a syslog server to send troubleshooting information. By default, it is sent as local broadcast. If the AP is not on same subnet as the syslog server, it is advisable to change to a unicast address in order to be able to collect this information and to reduce the possibility of a broadcast storm caused by syslog messages sent to the local broadcast, in case there is an incidence that affects all APs in the same subnetwork. In order to check this setting:

(WiSM-slot1-1) >show ap config general AP1130-9064    

Cisco AP Identifier.............................. 164
Cisco AP Name.................................... AP1130-9064
Country code..................................... BE  - Belgium
Regulatory Domain allowed by Country............. 802.11bg:-E     802.11a:-E
AP Country code.................................. BE  - Belgium
AP Regulatory Domain............................. 802.11bg:-E    802.11a:-E 
Switch Port Number .............................. 29
MAC Address...................................... 00:16:46:f2:90:64
IP Address Configuration......................... DHCP
IP Address....................................... 192.168.100.200
IP NetMask....................................... 255.255.255.0
Gateway IP Addr.................................. 192.168.100.1
Telnet State..................................... Disabled
Ssh State........................................ Disabled
Cisco AP Location................................ default location
Cisco AP Group Name.............................. default-group
Primary Cisco Switch Name........................ Cisco_ea:5e:63
Primary Cisco Switch IP Address.................. Not Configured
Secondary Cisco Switch Name...................... 
Secondary Cisco Switch IP Address................ Not Configured
Tertiary Cisco Switch Name....................... 
Tertiary Cisco Switch IP Address................. Not Configured
Administrative State ............................ ADMIN_ENABLED
Operation State ................................. REGISTERED
Mirroring Mode .................................. Disabled
AP Mode ......................................... Local
Public Safety ................................... Global: Disabled, Local:
 Disabled
Remote AP Debug ................................. Disabled
S/W  Version .................................... 5.0.152.0
Boot  Version ................................... 12.3.7.1
Mini IOS Version ................................ 3.0.51.0
Stats Reporting Period .......................... 180
LED State........................................ Enabled
PoE Pre-Standard Switch.......................... Enabled
PoE Power Injector MAC Addr...................... Disabled
Power Type/Mode.................................. Power injector / Normal mode
Number Of Slots.................................. 2 
AP Model......................................... AIR-LAP1131AG-E-K9  
IOS Version...................................... 12.4(20080324:062820)
Reset Button..................................... Enabled
AP Serial Number................................. FHK0952C0FC
AP Certificate Type.............................. Manufacture Installed
Management Frame Protection Validation........... Enabled (Global MFP Disabled)
AP User Mode..................................... AUTOMATIC
AP User Name..................................... cisco
Cisco AP system logging host..................... 255.255.255.255

In order to change it to a known available server for all APs in the controller:

config ap syslog host global 10.48.76.33

In versions later than 4.2, the AP can have a local credential for console access (physical access to the AP). It is good security practice to set a username/password to all APs . In order to check this setting:

(WiSM-slot1-1) >show ap config general AP1130-9064    

Cisco AP Identifier.............................. 164
Cisco AP Name.................................... AP1130-9064
Country code..................................... BE  - Belgium
Regulatory Domain allowed by Country............. 802.11bg:-E     802.11a:-E
AP Country code.................................. BE  - Belgium
AP Regulatory Domain............................. 802.11bg:-E    802.11a:-E 
Switch Port Number .............................. 29
MAC Address...................................... 00:16:46:f2:90:64
IP Address Configuration......................... DHCP
IP Address....................................... 192.168.100.200
IP NetMask....................................... 255.255.255.0
Gateway IP Addr.................................. 192.168.100.1
Telnet State..................................... Disabled
Ssh State........................................ Disabled
Cisco AP Location................................ default location
Cisco AP Group Name.............................. default-group
Primary Cisco Switch Name........................ Cisco_ea:5e:63
Primary Cisco Switch IP Address.................. Not Configured
Secondary Cisco Switch Name...................... 
Secondary Cisco Switch IP Address................ Not Configured
Tertiary Cisco Switch Name....................... 
Tertiary Cisco Switch IP Address................. Not Configured
Administrative State ............................ ADMIN_ENABLED
Operation State ................................. REGISTERED
Mirroring Mode .................................. Disabled
AP Mode ......................................... Local
Public Safety ................................... Global: Disabled, Local:
 Disabled
Remote AP Debug ................................. Disabled
S/W  Version .................................... 5.0.152.0
Boot  Version ................................... 12.3.7.1
Mini IOS Version ................................ 3.0.51.0
Stats Reporting Period .......................... 180
LED State........................................ Enabled
PoE Pre-Standard Switch.......................... Enabled
PoE Power Injector MAC Addr...................... Disabled
Power Type/Mode.................................. Power injector / Normal mode
Number Of Slots.................................. 2 
AP Model......................................... AIR-LAP1131AG-E-K9  
IOS Version...................................... 12.4(20080324:062820)
Reset Button..................................... Enabled
AP Serial Number................................. FHK0952C0FC
AP Certificate Type.............................. Manufacture Installed
Management Frame Protection Validation........... Enabled (Global MFP Disabled)
AP User Mode..................................... AUTOMATIC
AP User Name..................................... cisco

In order to change it to a known available server for all APs in controller, for version 4.2 and 4.1 Mesh:

config ap username Cisco password AnotherComplexPass all

In order to change it to a known available server for all APs in the controller, for version 5.0 and later:

config ap mgmtuser add username cisco password Cisco123 secret
	  AnotherComplexPass all

How to Transfer the WLC Crash File from the WLC CLI to the TFTP Server

Issue these commands in order to transfer the WLC crash file from the WLC CLI to the TFTP server.

transfer upload datatype crashfile
transfer upload serverip <IP address of the TFTP Server>

transfer upload path <Enter directory path>
 
transfer upload filename <Name of the Crash File>

transfer upload start<yes>

Note: When you enter the directory path, "/" usually means the default root directory onthe TFTP server.

Here is an example:

(Cisco Controller) >debug transfer tftp enable

(Cisco Controller) >debug transfer trace enable

(Cisco Controller) >transfer upload datatype crashfile

(Cisco Controller) >transfer upload filename aire2cra.txt

(Cisco Controller) >transfer upload path /

(Cisco Controller) >transfer upload serverip X.Y.Z.A

(Cisco Controller) >transfer upload start

Mode............................................. TFTP TFTP Server
IP................................... X.Y.Z.A TFTP
Path........................................ / TFTP
Filename.................................... aire2cra.txt Data
Type........................................ Crash File

Are you sure you want to start? (y/N) yes
Thu Dec 29 10:13:17 2005: RESULT_STRING: TFTP Crash File transfer starting.
Thu Dec 29 10:13:17 2005: RESULT_CODE:1

TFTP Crash File transfer starting.
Thu Dec 29 10:13:21 2005: Locking tftp semaphore, pHost=X.Y.Z.A 
pFilename=/aire2cra.txt Thu Dec 29 10:13:22 2005: 
Semaphore locked, now unlocking,
pHost=X.Y.Z.A pFilename=/aire2cra.txt Thu Dec 29 10:13:22 2005: 
Semaphore successfully unlocked,
pHost=X.Y.Z.A pFilename=/aire2cra.txt Thu Dec 29 10:13:22 2005: 
tftp rc=0, pHost=X.Y.Z.A pFilename=/aire2cra.txt
 

pLocalFilename=/mnt/application/bigcrash
Thu Dec 29 10:13:22 2005: RESULT_STRING: File transfer operation 
completed successfully.
Thu Dec 29 10:13:22 2005: RESULT_CODE:11 File transfer operation 
completed successfully.

Upload core dump file to an FTP server

In order to help troubleshoot controller crashes, you can now configure the controller to automatically upload its core dump file to an FTP server after experiencing a crash with these CLI commands:

config coredump {enable | disable}

config coredump ftp server_ip_address filename

config coredump username ftp_username password ftp_password

show coredump summary

You can now upload the console dump resulting from a software-watchdog-initiated reboot of the controller following a crash using the transfer upload datatype watchdog-crash-file controller CLI command. The software watchdog module periodically checks the integrity of the internal software and makes sure that the system does not stay in an inconsistent or non-operational state for a long period of time.

You can also upload the kernel panic information if a kernel panic occurs with the transfer upload datatype panic-crash-file controller CLI command.

With Wireless LAN Controller release 5.2, you can now upload the radio core dump file to a TFTP or FTP server using the controller GUI. Previously, radio core dump uploads could be configured only from the controller CLI.

Contents