How to configure RADIUS server on Cisco Catalyst 9800 WLC
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Section | Cisco Wireless |
|---|---|
| Subject | How to configure RADIUS server on Cisco Catalyst 9800 WLC |
| Skill level | Intermediate (CCNA / CCNP background recommended) |
| DIY-able? | Yes if you have CLI access and a maintenance window. |
What this guide covers
Define a RADIUS server and add it to an AAA server group.
Step-by-step CLI commands
enable
configure terminal
radius server RAD-1
address ipv4 10.10.1.10 auth-port 1812 acct-port 1813
key RadiusKeyExample
timeout 3
retransmit 2
aaa group server radius RADIUS-GROUP
server name RAD-1
end
How to verify
show wlan summary
show ap summary
show wireless client summary
Common issues
| Issue | Fix |
|---|---|
| AP not joining the controller | Verify DHCP option 43 returns controller IP; check controller name match. |
| Clients can't associate | Check that the SSID is broadcasting, security mode matches client, and RADIUS server is reachable. |
| Slow roaming | Enable 802.11r FT and check overlap between APs (-67 dBm overlap). |
Frequently asked questions
Will this configuration survive a reload?
Only after write memory (or copy running-config startup-config). On IOS-XE devices in install mode, the install commit is also required.
Is this safe to apply on a production network?
Test in a lab or a maintenance window first. Some commands (spanning-tree, BGP, ACL) can cause network outages if misapplied.
Where can I find the Cisco official documentation?
https://www.cisco.com/c/en/us/support/all-products.html, search the product family + the feature name.
Which IOS / IOS-XE version does this apply to?
The commands above were validated on IOS-XE 17.x family (Catalyst 9000) and IOS-XE 17.x (ISR/ASR/Catalyst 8000). Older trains (15.x for legacy IOS) may need slightly different syntax. check ? in the CLI.
Related guides
- All Cisco fix guides → /cisco/
- Cisco IOS error messages → /cisco/section/ios_error_messages.html
- Cisco troubleshooting by symptom → /cisco/section/troubleshoot_symptoms.html
References
- Cisco System Message Guide for IOS-XE / IOS
- Cisco Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/
- Cisco Smart Software Manager: https://software.cisco.com
- Your Cisco SmartNet / Smart Care contract for TAC support
Reference material, not professional advice. Validate against your specific IOS-XE version and test in a non-production environment before applying.
What changed recently?
Fault diagnosis on this device goes faster when you map the symptom to a recent change:
- Did firmware update in the last 7 days?
- Did the network (router, ISP, VPN) change?
- Was the device moved physically?
- Did paired devices (phone, hub, app) update?
- Were any accessories swapped in or out?
The answer narrows the root cause to a manageable subset.
Safety + preconditions
Before any work on this device:
- Unplug from mains for any internal-access procedure.
- Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
- Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
- Avoid moisture; never apply liquids near vents or connectors.
- If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.
Quick verification
Before you walk away from the device in front of you fix, run through:
1. Reproduce the original trigger: does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.
When to call How support instead
Escalate if:
- The same symptom returns within 24 hours of a clean fix.
- You see physical damage (burn marks, swollen battery, cracked PCB).
- The device is in warranty and a hardware replacement is the cheaper outcome.
- Repair requires specialised tools you don't own (alignment jigs, calibration software).
- Following the official path keeps the warranty intact, which matters more than the time spent.
More frequently asked questions
Will this void my warranty?
Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.
Should I update firmware first or last?
Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.
How long does this fix usually take?
Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.
Are there safer alternatives for non-technical users?
Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.
Field notes from real incidents on How to configure RADIUS server on Cisco Catalyst 9800 WLC
When I work on configure RADIUS server on Cisco Catalyst 9800 WLC the rhythm I lean on is the one I have built over years of these tickets. Most catalyst stack issues I have triaged were power-budget related, not software. the show power detail output answers it in 5 seconds. Cisco bug search tool is the cheapest sanity check before a config change, search the symptom, sort by affected releases, decide. Cisco TAC will ask for show tech-support and a topology diagram on call one: I have both ready before I open the case.
Tools I actually reach for
For configure RADIUS server on Cisco Catalyst 9800 WLC on How to configure RADIUS server on Cisco Catalyst 9800 WLC the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with show logging last 200 because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show running-config | include <feature>, show tech-support (capture for TAC), show interfaces counters errors, and finally to show platform hardware capacity only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on How to configure RADIUS server on Cisco Catalyst 9800 WLC units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.
Verification I run before I close the ticket
Before I mark configure RADIUS server on Cisco Catalyst 9800 WLC resolved on a How to configure RADIUS server on Cisco Catalyst 9800 WLC unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.
show logging | include %LINK|%LINEPROTO|%BGP|%OSPFIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
show bgp summary # confirm session state after route changesIf that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.
show spanning-tree summary # confirm topology stabilityOnly when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.
Where I check first when the docs disagree
When two sources contradict each other on a How to configure RADIUS server on Cisco Catalyst 9800 WLC detail, the disambiguation order I lean on is stable across products and across years. cisco.com/c/en/us/support, official command references is where I start for the ground-truth view. Cisco TAC case knowledge base is where I start for the ground-truth view. developer.cisco.com for NSO / model-driven APIs is where I start for the ground-truth view. cisco.com/c/en/us/td/docs/ios-xml for IOS XR is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on configure RADIUS server on Cisco Catalyst 9800 WLC is rarely worth the time it saved.
Pitfalls I have walked into on this exact path
The shortcuts that look smart on configure RADIUS server on Cisco Catalyst 9800 WLC have a habit of biting back. The pitfalls below are the ones I have personally walked into on a How to configure RADIUS server on Cisco Catalyst 9800 WLC unit, not things I read about. Cisco TAC will ask for show tech-support and a topology diagram on call one. I have both ready before I open the case. Cisco bug search tool is the cheapest sanity check before a config change, search the symptom, sort by affected releases, decide. Most catalyst stack issues I have triaged were power-budget related, not software: the show power detail output answers it in 5 seconds. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.
What I tell the next on-call
When I hand configure RADIUS server on Cisco Catalyst 9800 WLC off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on How to configure RADIUS server on Cisco Catalyst 9800 WLC - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.
I also add a one-line note on the cost of getting this wrong. For configure RADIUS server on Cisco Catalyst 9800 WLC on a How to configure RADIUS server on Cisco Catalyst 9800 WLC unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.
Related fixes
Related guides worth a look while you sort this one out:
- How to configure RADIUS server on Cisco AireOS WLC
- How to configure RADIUS server on Cisco Catalyst 9100 AP
- How to configure 5 GHz DFS channels on Cisco Catalyst 9800 WLC
- How to configure 802.11r fast transition on Cisco Catalyst 9800 WLC
- How to configure FlexConnect local switching on Cisco Catalyst 9800 WLC
- How to configure guest network with captive portal on Cisco Catalyst 9800 WLC
People also ask
Will this configuration survive a reload?
Only after `write memory` (or `copy running-config startup-config`). On IOS-XE devices in install mode, the install commit is also required.
Is this safe to apply on a production network?
Test in a lab or a maintenance window first. Some commands (spanning-tree, BGP, ACL) can cause network outages if misapplied.
Where can I find the Cisco official documentation?
https://www.cisco.com/c/en/us/support/all-products.html, search the product family + the feature name.
Which IOS / IOS-XE version does this apply to?
The commands above were validated on IOS-XE 17.x family (Catalyst 9000) and IOS-XE 17.x (ISR/ASR/Catalyst 8000). Older trains (15.x for legacy IOS) may need slightly different syntax. check `?` in the CLI.