Cisco Cisco 2106 Wireless LAN Controller

New 1250 series access points shipped from the factory contain new bootloader images, which fixes the 
flash file system after it is corrupted during a crash (without losing files). This new bootloader 
automatically sets a new CRASH_LOG environment variable to “yes,” which enables a crash log to be 
generated following a crash but only on controllers running software release 4.2.112.0 or later. 
Therefore, no user configuration is needed to enable a crash log on new 1250 series access points shipped 
from the factory.

These examples show the output from the CLI commands (in bold) that you use to check the bootloader 
version on LWAPP and autonomous 1250 series access points:

LWAPP (commands entered on the controller CLI):

(wlc) >debug ap enable AP001b.d513.1754

(wlc) >debug ap command "show version | include BOOTLDR" AP001b.d513.1754

(wlc) >Thu Apr 23 09:31:38 2009: AP001b.d513.1754: BOOTLDR: C1250 Boot Loader 

(C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)

Autonomous (command entered on the access point CLI):

ap# show version | include BOOTLDR

BOOTLDR: C1250 Boot Loader (C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)

The controller Port Mirroring feature is not supported on 2100 series controllers, 4400 series controllers, 
Cisco WiSM controllers, and Wireless LAN Controller Network Modules.

Rogue Location Discovery Protocol (RLDP) is a controller feature that detects the presence of rogue 
access points that are connected to your wired network. In this software release, RLDP operates with 
these limitations:

RLDP detects rogue access points that are configured for open authentication.

RLDP detects rogue AP which use a broadcast BSSID--that is, the access point broadcasts its SSID 
in beacons.

RLDP detects only rogue AP that are on the same the network. In other words, if an access list in 
the network prevents the sending of RLDP traffic from the rogue AP to the controller, RLDP will 
not work.

RLDP does not work on 5-GHz DFS channels.

RLDP is a best-effort protocol. For each rogue, the controller initiates RLDP only once. If the 
controller does not detect a rogue (due to a noisy RF environment, for example), the controller does 
not retry. However, you can initiate RLDP manually on a rogue at any time.

In controller software 4.2, the controller’s bootup configuration file is stored in an Extensible Markup 
Language (XML) format rather than in binary format. Therefore, you cannot download a binary 
configuration file onto a controller running software release 4.2. However, when you upgrade a 
controller from a previous software release to 4.2, the configuration file is migrated and converted to 
XML.