Failed to dot11 ie validate aironet ipaddr

[Timothy M Patrick]

We are having reports of our clients loosing connectivity to the network. 

Controller is a Cisco 9800-L APs are 9120AXE-B's

Client is a Zebra MC93 hand scanner

Client auth is local WPA2-PSK connection

I have attempted to replicate the behaviour unsuccessfully I pulled the debug trace from the client and did see something odd as the client roams between APs we get this message each time they connect to a new AP. 

2024/11/11 15:06:16.601489 {wncd_x_R0-0}{1}: [dot11-validate] [17366]: (ERR): MAC: 94fb.29bc.f14a Failed to dot11 ie validate aironet ipaddr. Aironet ipaddr IE is not present in Assoc Request

[marce1000]

  - Check if this can work for you : https://community.cisco.com/t5/wireless/solved-9800-cl-sonos-can-t-associate/m-p/4682453/highlight/true#M245793 

  M.

[Timothy M Patrick]

Thanks this did help partially I used the tool and it appears this message
is not something to worry about in my case but the tool did show me an
interesting issue we are looking into


SessionStateAuth MethodAPWLANMobility RoleIP AddressOnboarding TimeStart/Run
TimeDelete ReasonDelete Time


23 RUN UNKNOWN AP043 s-3 Local-None 5 ms 16:06:51:721 /
16:06:51:726
24 RUN UNKNOWN AP055 s-3 Local-None 5 ms 16:08:00:294 /
16:08:00:299
25 INIT UNKNOWN AP105 s-3 NONE-NONE 0 ms 16:09:18:371 /
ROAM_ACROSS_POLICY_PROFILE_DENY 16:09:18:000
26 L2AUTH PSK 889c.ade4.c300 s-3 NONE-NONE 0 ms 16:09:18:373 /
27 RUN UNKNOWN AP105 s-3 Local-None 172.1.1.114 915 ms 16:09:20:122 /
16:09:21:037
28 INIT UNKNOWN AP259 s-3 NONE-NONE 0 ms 16:11:01:630 /
ROAM_ACROSS_POLICY_PROFILE_DENY 16:11:01:000
29 L2AUTH PSK 5c64.f18d.f700 s-3 NONE-NONE 0 ms 16:11:01:634 /
30 RUN UNKNOWN AP259 s-3 Local-None 172.1.1.114 1033 ms 16:11:03:462 /
16:11:04:495
31 RUN UNKNOWN AP249 s-3 Local-None 5 ms 16:11:41:466 /
16:11:41:471

[Scott Fella]

There are a lot of messages that seem to be bad or the possible cause, and most of the time its nothing.  Replicating the issue and being to also perform the test in a good know location allows you to compare logs and that can tell you what might be the problem.  If you run a debug, then use the debug analyzer to help deciphering the logs.

[Scott Fella]

So, when you try to replicate the issue, are you on-site at the location that folks are complaining? Are you also using device(s) that are problematic. They key thing is being able to replicate the issue and then capture debugs, isolating issues for one site to another, an area or from certain ap's to others.  

Look at the link @marce1000 posted.  Not really knowing how many sites, if the issue is only with one site or with on wlan, makes it hard to start troubleshooting.

[Timothy M Patrick]

I am on site with the same client device and unable to replicate the error

[Scott Fella]

Well maybe its an issue with the device that the users has been using.  If you are onsite, let the user let you know so you can actually possbily replicate it or identify something different with that devices versus others. I have seen some issues with scanners that are on the trucks vs handheld and specific to areas.

**Edit**

Also reach out to the vendor as they can help with debugs on their end.

[Rich R]

Make sure your software is up to date as per TAC recommended (link below).

And read the section of the config guide relating to roaming across policy profiles:
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/config-guide/b_wl_17_12_cg/m_client_roaming_policy_profile.html

And check your WLC setup/config with the Config Analyzer (link below).