The easy way to do it could be:
On your WLC home page you should have something like:
You can reset the stat through the gear icon on the top right corner, selecting "Clear Dashboard Data"
Then the machine should quickly appear in the "Top Client Devices" list, you can click on it and you will get the IP address and the mac address of the device.
According to Cisco release notes for the Cisco 2504 Wireless LAN Controller, the last software, that supported the Cisco 1140 Series AP and Cisco 1250 Series AP is Releases 188.8.131.52 (31-Aug-2017) and 184.108.40.206 (21-Oct-2017).
From Cisco documentation:
Supported Access Point Platforms
The following access point platforms are supported in this release:...
I see you put the tag of aironet, so that I assume you are using Cisco WLC.
I used to manage this kind of WLC HA and I can be sure that both WLCs share the same IP address (here is 220.127.116.11) as long as you configured them properly.
Cisco also states this in their Cisco WLC Configuration Guide:
Information About High Availability
You may try turning off 802.11r in the AP and make sure your IOS is 10 or higher in case it's conflicting. IOS 10 and up have adaptive 801.11r and do not need it turned on in the AP. Reference link to Apple doc...
Quote from Apple...
When your iOS device roams from one AP to another on the same network, 802.11r uses a feature called Fast Basic ...
Is there a way to display on a WLC a list of commands used for configuration of a given AP?
For a given AP? No. But you can list all the commands from the running configuration with the following:
show run-config commands
Depending on your configuration this can be a very long output, so two pieces of advice.
Enable logging of the output in your SSH ...
The software version that you are running on your WLC is not compatible with the 3700 series access points. You need to upgrade your code to at least 18.104.22.168 which is what Cisco indicates is the first version of code to support that AP platform.
You can find the compatibility matrix from Cisco here.
Looking through the configuration I now see the problem. It was also hinted at in the screenshots you provided, but I missed it until I saw it in your configuration.
WLAN 1, your normal production WLAN is not configured as a FlexConnect WLAN. WLAN 4, your -Test WLAN is configured as a FlexConnect WLAN as indicated below:
wlan flexconnect local-switching 1 ...
Well, @Ron Trunk got it. Well, at least got me in thinking in a slightly different direction, which is good enough for me.
I did have the HA config mostly correct on the AP, BUT (because there's always a but), I had the name incompletely punched in.
To clarify: Each WLC's sysname is 'wlc-01.FQDN'. When I entered the HA name I only added the hostname, in this ...
Unlike IP addresses, that are often dynamically allocated, MAC addresses are unique identifiers that can be used to reliably identify hosts in your network. Flexible NetFlow allows collecting VLAN IDs or MAC addresses. https://www.noction.com/blog/finding-mac-addresses-using-flexible-netflow
Try the following command.
WLC version should be after v7.5
grep include 'Time\.' "show time"
I didn't have the device.
I'm not unclear what kind of regex option can be used.
Check the following filter example.
grep include '20[0-9][0-9]' "show time"
grep include 'Time' "show time"
grep include 'Timezone delta' "show time"
grep exclude 'Timezone' "show ...
The error is a standard "warning" message you get when making this configuration. I don't believe this has any relation to your problem.
Instead, you said you entered this:
config wlan dhcp_server 1 0.0.0.0 required 1
This is not correct syntax for the CLI command. This is the correct syntax:
config wlan dhcp_server <WLAN_ID> 0.0.0.0 required
If your question is to get the following AP configs ..
AP#capwap ap ip address
AP#capwap ap ip default-gateway
AP#capwap ap primary-base
AP#capwap ap secondary-base
AP#capwap ap hostname
You can check the configuration of the AP with show capwap ip config, and after joining the WLC, you can check the details with show capwap client ...
PEAP-MSCHAPv2 does need to to validate server side certificate. I see you have disabled the need to validate certs (for testing purposes). It wont work without validating server side cert.
This looks like mis-configuration issue. You need to make sure same authentication type is used at both ends (client and server). Wireless profiles at client must be ...
Option 43 is different from others DHCP options, you can re-define internal length or sub options. In INFOBLOX (as you can read on the admin guide pag 803) you have to put hexadecimal value divided by colon ":"
Most of what you are looking for is explained here :
There is no HW difference that I'm aware of, however if you buy an -HA version of the controller, it can only ever be an HA controller, you can't convert it to be a primary controller, whereas the reverse ...
The controller just bridges the the Wi-Fi traffic; you get DHCP from a DHCP server, either on the LAN or on a different LAN with the aid of a helper address in the router port for the LAN.
You normally want to trunk multiple VLANs to a WLC: one for management, and one or more for Wi-Fi clients. These VLANs use one or more DHCP servers for any DHCP clients.