topic Re: What does it mean 802.11(Mobile)? in Wireless

What does it mean 802.11(Mobile)?

theophile — Sun, 04 Jul 2021 03:46:41 GMT

Hello,

I've two wlc4402 in the same mobility group and since yesterday, when I take a look at the client's page, I see some strange clients. Have a look at the attached document... The AP name is the IP address of the management interface of the other controller, the protocol is neither 802.11b or g or a, but it's displayed as 802.11(Mobile). I've never seen that in the past, does someone have an explanation? Thanks in advance

What does it mean 802.11(Mobile)?

theophile — Thu, 15 Sep 2011 07:40:42 GMT

And the client has got an ip address in the same network than the management interface ogf the wlc (10.233.1.*). On the SSID I do not authorize client with static IP, and there is no DHCP scope for the 10.233.1.* network. How can the client have an IP address in 10.233.1.*?

What does it mean 802.11(Mobile)?

theophile — Thu, 15 Sep 2011 07:47:26 GMT

On the log file, I've this strange entry

What does it mean 802.11(Mobile)?

theophile — Thu, 15 Sep 2011 07:49:55 GMT

Another strange log

What does it mean 802.11(Mobile)?

Nicolas Darchis — Thu, 15 Sep 2011 09:05:34 GMT

Strange. You mentioned you have 2 WLCs. Is it possible that you configured auto-anchor ? (and possibly wrongly)

Please post the "Show run-config" of both your WLCs.

Re: What does it mean 802.11(Mobile)?

theophile — Thu, 15 Sep 2011 09:18:31 GMT

Hi Nicolas, here it is

Re: What does it mean 802.11(Mobile)?

Stephen Rodriguez — Thu, 15 Sep 2011 11:42:35 GMT

Generally when you see mobile it means the client did a layer 3 roam to the other controller. Check the client entry on the other WLC and se what it's status and address are

Sent from Cisco Technical Support iPad App

Re: What does it mean 802.11(Mobile)?

theophile — Thu, 15 Sep 2011 12:14:46 GMT

but if I look at the Uptime, the value seems to be very long for just a roaming.

Re: What does it mean 802.11(Mobile)?

theophile — Thu, 15 Sep 2011 12:35:51 GMT

Found it!

it was one of the access point which was misconfigured, was in the default-group under the AP Group settings. I placed it onto the correct AP group and now all is correct.

Cheers