Aruba CX switches
This page configures an Aruba AOS-CX switch (CX 6000, 6100, 6200, 6300, 6400 and later) for port-based 802.1X and MAC authentication against Airgate, dynamic authorization (CoA) from Airgate, and wired guest access through the Airgate portal. Roles are assigned with Aruba-User-Role, VLANs with the RFC 3580 attributes.
Before you begin
Section titled “Before you begin”- AOS-CX 10.08 or later is recommended (local user roles, captive-portal profiles).
- The Airgate RADIUS address (
203.0.113.10in the examples) and a shared secret. - The switch management address, for example
10.0.0.2, reachable from Airgate on UDP 3799 for CoA (or a site connector on the LAN). - NTP configured on the switch.
Step 1: Add the switch in Airgate
Section titled “Step 1: Add the switch in Airgate”- Go to Network › Switches and APs › Add device.
- Name
access-sw1, IP address or subnet10.0.0.2. - Vendor profile: Aruba AOS-CX switch. The dictionary becomes
Aruba, the CoA port3799. - 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 and accounting
Section titled “Step 2: RADIUS server and accounting”radius-server host 203.0.113.10 key plaintext <shared-secret>radius-server host 203.0.113.10 tracking enableip source-interface radius interface vlan10!aaa group server radius AIRGATE server 203.0.113.10!aaa accounting port-access start-stop interim 10 group AIRGATEUse vrf mgmt on the radius-server host line when the switch reaches Airgate through the management port.
Step 3: 802.1X and MAC authentication
Section titled “Step 3: 802.1X and MAC authentication”aaa authentication port-access dot1x authenticator radius server-group AIRGATE enableaaa authentication port-access mac-auth radius server-group AIRGATE enable!client track ip!interface 1/1/10 no shutdown no routing vlan access 10 aaa authentication port-access client-limit 4 aaa authentication port-access dot1x authenticator enable aaa authentication port-access mac-auth enableclient track iplets the switch learn client IP addresses and report them in accounting.- Airgate returns
Aruba-User-Role(a local role on the switch, or a downloadable role),Aruba-NAS-Filter-Rule, or a VLAN withTunnel-Type,Tunnel-Medium-TypeandTunnel-Private-Group-Id. Create local roles withport-access role <name>.
Step 4: CoA (dynamic authorization)
Section titled “Step 4: CoA (dynamic authorization)”radius dyn-authorization enableradius dyn-authorization client 203.0.113.10 secret-key plaintext <shared-secret>The switch listens on UDP 3799. Airgate’s CoA actions for this profile are Disconnect, Bounce port (Aruba-Port-Bounce-Host) and changing attributes (for example a new Aruba-User-Role).
Step 5: Guest captive portal (optional)
Section titled “Step 5: Guest captive portal (optional)”For wired guests, Airgate uses MAC caching + CoA: MAC authentication returns a role bound to a captive-portal profile; after sign-in, Airgate caches the MAC and sends CoA, and the next MAC authentication returns the guest role.
aaa authentication port-access captive-portal-profile Airgate-CP url https://airgate.contoso.com/portal/<tenant>/<portal> url-hash-key plaintext <hash-key>!class ip Portal-Allow 10 match udp any any eq 53 20 match udp any any eq 67 30 match tcp any 203.0.113.20 eq 443class ip Portal-Redirect 10 match tcp any any eq 80 20 match tcp any any eq 443!port-access policy Airgate-Guest-Portal 10 class ip Portal-Allow action permit 20 class ip Portal-Redirect action redirect captive-portal!port-access role Airgate-Guest-Portal associate captive-portal-profile Airgate-CP associate policy Airgate-Guest-Portal vlan access 30!port-access role Guest-Internet vlan access 30Replace 203.0.113.20 with the address of the Airgate portal host.
In Airgate, on the portal’s Login & network section (Guests › Guest portal):
| Field | Value |
|---|---|
| Vendor handling | Aruba switch (AOS-CX / AOS-S) |
| Login model | MAC caching + CoA |
| Post-login CoA | Reauthenticate, or Bounce port when the guest VLAN changes |
| Redirect MAC trust | Signed, with URL hash key = the url-hash-key above (recommended) |
Create the enforcement profiles Aruba-User-Role = Airgate-Guest-Portal and Aruba-User-Role = Guest-Internet from the Aruba RADIUS Enforcement template on Access › Enforcement profiles.
Verify
Section titled “Verify”- Connect a client to
1/1/10.show port-access clientsshows it authenticated bydot1xormac-authwith the expected role. - Monitor › Sign-in log shows the record with Switch / AP =
access-sw1. - On Monitor › Connected now, choose Bounce port for the session. The result is
CoA-ACKand the port flaps.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| No request in the Sign-in log | Wrong RADIUS source address | Set ip source-interface radius to the address registered in Airgate. |
| Client authorized but in the wrong role | The role named in Aruba-User-Role does not exist on the switch |
Create the port-access role with that exact name. |
CoA timeout |
radius dyn-authorization not enabled, or the client entry has another secret |
Enable it and use the same secret as in Airgate. |
| Guest portal refuses the device as untrusted | The redirect MAC had no recent RADIUS activity, or the hash key differs | Check Redirect MAC trust and the URL hash key. |