topic Re: Failed to dot11 ie validate aironet ipaddr. in Wireless

Failed to dot11 ie validate aironet ipaddr.

jsjsj — Fri, 06 Oct 2023 12:42:09 GMT

I have Cisco Catalyst 9800-CL Wireless Controller and Five 1702I APs that are connected and have DNA Essentials licenses.

Clients have been unable to authenticate. Have DHCP setup and have confirmed that clients are get IP address on the network. Suggestions would be greatly appreciated.

Radioactive Trace indicates the following:

2023/10/06 08:11:39.649300 {wncd_x_R0-0}{1}: [client-orch-sm] [19103]: (note): MAC: 9cfc.e893.9d79 Association received. BSSID a023.9f19.3c3e, WLAN SCX-COLA-WLC-02, Slot 1 AP a023.9f19.3c30, AP_Name

2023/10/06 08:11:39.649412 {wncd_x_R0-0}{1}: [client-orch-state] [19103]: (note): MAC: 9cfc.e893.9d79 Client state transition: S_CO_INIT -> S_CO_ASSOCIATING

2023/10/06 08:11:39.649552 {wncd_x_R0-0}{1}: [dot11-validate] [19103]: (ERR): MAC: 9cfc.e893.9d79 Failed to dot11 ie validate aironet ipaddr. Aironet ipaddr IE is not present in Assoc Request

2023/10/06 08:11:39.649771 {wncd_x_R0-0}{1}: [dot11] [19103]: (note): MAC: 9cfc.e893.9d79 Association success. AID 16, Roaming = False, WGB = False, 11r = False, 11w = False

2023/10/06 08:11:39.649865 {wncd_x_R0-0}{1}: [client-orch-state] [19103]: (note): MAC: 9cfc.e893.9d79 Client state transition: S_CO_ASSOCIATING -> S_CO_L2_AUTH_IN_PROGRESS

2023/10/06 08:11:39.650306 {wncd_x_R0-0}{1}: [client-auth] [19103]: (note): MAC: 9cfc.e893.9d79 ADD MOBILE sent. Client state flags: 0x31 BSSID: MAC: a023.9f19.3c3e capwap IFID: 0x9000000a, Add mobiles sent: 1

2023/10/06 08:11:39.653190 {wncd_x_R0-0}{1}: [sanet-shim-translate] [19103]: (ERR): 9cfc.e893.9d79 wlan_profile Not Found : Device information attributes not populated

2023/10/06 08:11:39.653249 {wncd_x_R0-0}{1}: [client-auth] [19103]: (note): MAC: 9cfc.e893.9d79 L2 Authentication initiated. method DOT1X, Policy VLAN 0, AAA override = 1 , NAC = 0

2023/10/06 08:11:39.653879 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [19103]: (note): Authentication Success. Resolved Policy bitmap:11 for client 9cfc.e893.9d79

Re: Failed to dot11 ie validate aironet ipaddr.

DanielP211 — Fri, 06 Oct 2023 12:43:16 GMT

Hello,

Could you share the aaa configuration (WLC and ISE)?

BR

Re: Failed to dot11 ie validate aironet ipaddr.

jsjsj — Fri, 06 Oct 2023 13:38:39 GMT

Hope this is what you want to see.

WLC

Authentication List = Authetication_dot1x = Type dotlx Group Type = Group Assigned Server Group = Radius Server Group

ISE

Name = Profile Name

Server Address = "Assigned Radius Server IP Address."

PAC Key = unchecked

Key Type = Clear Text

Key = "Same Key for Radius Server"

Confirm Key = Same as above

Auth Port = 1812

Acct Port -1813

Server Time Out: 1000

Retry Count : 3

Support for CoA = Enabled

Re: Failed to dot11 ie validate aironet ipaddr.

Ambuj M — Fri, 06 Oct 2023 14:01:03 GMT

problem description is incorrect "Clients have been unable to authenticate. Have DHCP setup and have confirmed that clients are get IP address on the network." if you have authentication setup then clients wont get IP unless authenticated L3 can't work without L2 working properly. Anyways I see a successful L2 authentication for client 9cfc.e893.9d79 in trace but it seems like your policy or authorization on radius is not setup correctly.

to start with share output for

show wlan name <wlan name>

show wireless profile policy detailed <policy name attached to WLAN>

Re: Failed to dot11 ie validate aironet ipaddr.

jsjsj — Fri, 06 Oct 2023 16:12:06 GMT

Okay I will get the information you requested, and you see no issue with it indicating:(ERR): MAC: 9cfc.e893.9d79 Failed to dot11 ie validate aironet ipaddr. Aironet ipaddr IE is not present in Assoc Request

Re: Failed to dot11 ie validate aironet ipaddr.

jsjsj — Fri, 06 Oct 2023 17:36:07 GMT

WLAN Name: SCX-COLA-WLC-02

General

Profile Name: S11-GRNV-WLC-02

SSID: S11-GRNV-WLC-02

WLAN ID: 1

Status: Enable

Radio Policy: All

Broadcast SSID: Enable

Re: Failed to dot11 ie validate aironet ipaddr.

Rich R — Sat, 07 Oct 2023 13:21:14 GMT

Agreed with @Ambuj M to provide the output of the suggested commands - not a word doc with your summary of GUI checkboxes etc!

No, not worried about Aironet IE log - there are lots of things in debugs that don't matter as client and AP negotiate options and settings.

You stated "Clients have been unable to authenticate. Have DHCP setup and have confirmed that clients are get IP address on the network"
But as @Ambuj M pointed out - the logs show that authentication DID succeed and DHCP is the next step after authentication so the fact that the client gets an IP address means that the authentication must have succeeded. So your problem comes after that and is more likely a routing or bridging issue or maybe even an ACL somewhere.

Also provide "show wireless client mac-address <client-mac> detail" for one of the clients when connected.

Re: Failed to dot11 ie validate aironet ipaddr.

jsjsj — Tue, 10 Oct 2023 12:11:42 GMT

See requested information attached.

Re: Failed to dot11 ie validate aironet ipaddr.

jsjsj — Tue, 10 Oct 2023 12:23:55 GMT

Client Mac Address: 9cfc.e893.9d79

Client Mac Type: Universally Administered Address

Client Ipv4 Address:

Client Username: N/A

AP Name: Columbia_AP

AP Slot: 1

Client State: Associated

Policy Profile: default-policy-profile

Flex Profile: N/A

Wireless LAN Id: 1

WLAN Profile Name: SCX-COLA-WLC-02

BSSID: a023.9f19.3c3f

Connected For: 4 seconds

Protocol: 802.11ac

Channel: 60

Client IIF Id: Unknown

Association Id: 1

Authentication Algorithm: Open System

Idle State timeout: N/A

Re-Authentication Timeout: 1800 sec (Timer not running)

Re: Failed to dot11 ie validate aironet ipaddr.

jsjsj — Fri, 13 Oct 2023 13:12:51 GMT

Any thoughts on a solution to this?

Re: Failed to dot11 ie validate aironet ipaddr.

jsjsj — Fri, 13 Oct 2023 13:14:05 GMT

Rich any thoughts on the additional information provided.

Re: Failed to dot11 ie validate aironet ipaddr.

Rich R — Sun, 15 Oct 2023 11:45:29 GMT

You did not provide "show wireless client mac-address <client-mac> detail" for one of the clients when connected.