A client of mine has about 30 LWAPs configured, one for each physical location. For each site, the AP is statically assigned an IP address of 10.x.10.30. We use ICMP to monitor the availability of each AP and three times, now, in the last 2 weeks the monitoring software has alarmed for an AP. When I go into the WLC and check on the status of the AP, I discover that the AP is using an IP address other than the one assigned to it. If I reset the AP, the AP reverts back to the originally assigned IP address and the monitoring software returns to normal for the AP. Has anybody else has this experience? The AP version is 12.4(18a)JA. The version of code on the WLC is 22.214.171.124 (model 4402).
Were these APs converted from Autonomous to LWAPP? If so read below:
If you configure an access point to use a static IP address that is not on the same subnet on which the access point's previous DHCP address was, the access point falls back to a DHCP address after the access point reboots. If the access point falls back to a DHCP address, the show ap config generalCisco_AP CLI command correctly shows that the access point is using a fallback IP address. However, the GUI shows both the static IP address and the DHCP address, but it does not identify the DHCP address as a fallback address.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...