Cisco Catalyst 9800 wireless controller
This page configures a Cisco Catalyst 9800 wireless LAN controller (IOS-XE) to authenticate Wi-Fi users and devices against Airgate, accept CoA, and send guests to the Airgate portal with central web authentication (CWA). AireOS controllers use the same Airgate vendor profile; their configuration follows the same RADIUS settings in the AireOS GUI.
Before you begin
Section titled “Before you begin”- The controller’s wireless management interface address, for example
10.0.0.2. - The Airgate RADIUS address (
203.0.113.10in the examples) and a shared secret. - For guests: the Airgate portal host address (
203.0.113.20in the examples) and a guest portal on Guests › Guest portal.
Step 1: Add the controller in Airgate
Section titled “Step 1: Add the controller in Airgate”- Go to Network › Switches and APs › Add device.
- Name
wlc1, IP address or subnet10.0.0.2. - Vendor profile: Cisco Catalyst 9800 WLC / AireOS. The dictionary becomes
Cisco, the CoA port1700(the 9800 default). - On RADIUS, CoA & RadSec: enter the RADIUS shared secret, keep Require Message-Authenticator in Access-Requests on, turn on RADIUS CoA / Disconnect (RFC 5176).
- Select Save.
Step 2: RADIUS server, method lists and CoA
Section titled “Step 2: RADIUS server, method lists and CoA”aaa new-model!radius server AIRGATE address ipv4 203.0.113.10 auth-port 1812 acct-port 1813 key <shared-secret>!aaa group server radius AIRGATE-GROUP server name AIRGATE!aaa authentication dot1x AIRGATE-DOT1X group AIRGATE-GROUPaaa authorization network AIRGATE-AUTHZ group AIRGATE-GROUPaaa accounting identity AIRGATE-ACCT start-stop group AIRGATE-GROUP!aaa server radius dynamic-author client 203.0.113.10 server-key <shared-secret>!radius-server attribute wireless authentication call-station-id ap-macaddress-ssidaaa server radius dynamic-authoraccepts CoA and Disconnect from Airgate on the default port 1700. Keep CoA port in Airgate at1700unless you change it on the controller.call-station-id ap-macaddress-ssidputs the SSID intoCalled-Station-Id, so access policies can match it.
Step 3: 802.1X WLAN and policy profile
Section titled “Step 3: 802.1X WLAN and policy profile”wlan Corp-WiFi 1 Corp-WiFi security dot1x authentication-list AIRGATE-DOT1X no shutdown!wireless profile policy Corp-Policy aaa-override accounting-list AIRGATE-ACCT nac vlan 20 no shutdown!wireless tag policy Corp-Tag wlan Corp-WiFi policy Corp-Policyaaa-overridelets Airgate assign the VLAN (Tunnel-Private-Group-IdorAirespace-Interface-Name) and ACL (Airespace-ACL-Name).nac(RADIUS NAC) is required for CoA and for CWA.- Assign the policy tag to the APs (
ap <ap-mac>›policy-tag Corp-Tag, or a tag rule).
Step 4: Guest WLAN with central web authentication (optional)
Section titled “Step 4: Guest WLAN with central web authentication (optional)”ip access-list extended ACL-REDIRECT deny udp any any eq domain deny udp any eq domain any deny udp any any eq bootps deny tcp any host 203.0.113.20 eq 443 deny tcp host 203.0.113.20 eq 443 any permit tcp any any eq www permit tcp any any eq 443!wlan Corp-Guest 2 Corp-Guest mac-filtering AIRGATE-AUTHZ no security wpa akm dot1x no security wpa wpa2 no security wpa no shutdown!wireless profile policy Guest-Policy aaa-override accounting-list AIRGATE-ACCT nac vlan 30 no shutdown!wireless tag policy Corp-Tag wlan Corp-Guest policy Guest-PolicyIn the redirect ACL, permit means “redirect” and deny means “let through”.
In Airgate:
-
Create an enforcement profile from the Cisco RADIUS Enforcement template with:
Cisco-AVPair=url-redirect-acl=ACL-REDIRECTCisco-AVPair=url-redirect=https://airgate.contoso.com/portal/<tenant>/<portal>?mac=%{Connection:Client-Mac-Address-Colon}
Airgate reads the client MAC from the
macparameter; the controller does not add it. -
On the portal’s Login & network section: Vendor handling = Cisco IOS-XE / C9800 CWA, Login model = MAC caching + CoA, Post-login CoA = Reauthenticate.
-
In the guest access policy, send the redirect profile to unknown devices and the guest profile to devices with a valid guest login.
For local web authentication (the controller hosts the login and the portal posts to its switch_url), use Vendor handling = Cisco WLC (EWA / LWA) and Login model = Web login instead, with a web-auth parameter map that points to the Airgate portal as external login page.
Verify
Section titled “Verify”show wireless client mac-address <mac> detailshows the client inRunstate with the VLAN and ACL Airgate sent.- Monitor › Sign-in log shows the request from
wlc1. - On Monitor › Connected now, choose Reauthenticate. The result is
CoA-ACK.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| VLAN or ACL from Airgate ignored | aaa-override missing in the policy profile |
Add aaa-override. |
CoA timeout |
CoA port in Airgate is not 1700, or no client entry under dynamic-author |
Match the port; add the client. |
| Guest not redirected | nac missing in the policy profile, or the redirect ACL name differs |
Add nac; use the same ACL name in the profile and the controller. |
| Access policies cannot match the SSID | Called-Station-Id carries only the AP MAC |
Set call-station-id ap-macaddress-ssid. |