Cisco Catalyst 9130AX invalid configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2021 01:50 AM
Hello everyone,
I'm trying to configure a Cisco Catalyst 9130AX but I'm running into this error when I validate the configuration.
Any idea of what I can try to solve this?
Thanks.
AP216>wireless config validate AP216>
*Sep 15 09:53:34.769: %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:Mandatory.crypto_pki_vwlc_ssc_config) AP216> *Sep 15 09:53:36.103: %CONFIG_VALIDATOR_MESSAGE-5-EWLC_GEN_ERR: Chassis 1 R0/0: wncd: Error in AP: APA488.73D6.1B68 with address b811.4b3b.fa00Radio state down for slot 0, Unknown reason
*Sep 15 09:53:36.103: %CONFIG_VALIDATOR_MESSAGE-5-EWLC_GEN_ERR: Chassis 1 R0/0: wncd: Error in AP: APA488.73D6.1B68 with address b811.4b3b.fa00Radio state down for slot 1, Unknown reason
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2021 04:44 AM
Look at the cursor. The AP is not even in "enable" mode.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2021 04:47 AM
Sorry, I wasn't aware that made a difference. In any case in "enable" mode the result is the same.
AP216#wireless config validate AP216# *Sep 15 09:46:29.330: %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:Mandatory.crypto_pki_vwlc_ssc_config) *Sep 15 09:46:30.221: %CONFIG_VALIDATOR_MESSAGE-5-EWLC_GEN_ERR: Chassis 1 R0/0: wncd: Error in AP: APA488.73D6.1B68 with address b811.4b3b.fa00Radio state down for slot 0, Unknown reason *Sep 15 09:46:30.221: %CONFIG_VALIDATOR_MESSAGE-5-EWLC_GEN_ERR: Chassis 1 R0/0: wncd: Error in AP: APA488.73D6.1B68 with address b811.4b3b.fa00Radio state down for slot 1, Unknown reason AP216#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2021 04:01 PM - edited 09-16-2021 04:01 PM
Did you assign the site, policy and RF tag to the AP and try this again. If possible paste a sanitized configuration to check and confirm.
TAC recommended codes for AireOS WLC's
Best Practices for AireOS WLC's
TAC recommended codes for 9800 WLC's
Best Practices for 9800 WLC's
Cisco Wireless compatibility matrix
___________________________________________
Arshad Safrulla
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2021 06:14 AM
and what version of code are you running?
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2021 02:50 AM
I've found out it might be an issue with the external antenna. I'm getting a new one and trying again as soon as I get it.
