Aruba Instant APs and AOS 10
This page configures an Aruba Instant cluster (virtual controller, VC) or AOS 10 APs managed by Aruba Central to authenticate Wi-Fi users and devices against Airgate, accept CoA, and send guests to the Airgate portal. At the end you have an 802.1X SSID, a MAC-authenticated guest SSID with an external captive portal, and roles assigned with Aruba-User-Role.
Before you begin
Section titled “Before you begin”- An Instant cluster with a virtual controller IP (
virtual-controller-ip), or AOS 10 APs in Aruba Central. - The Airgate RADIUS address (
203.0.113.10in the examples) and a shared secret. - For guests: the Airgate portal host name (for example
airgate.contoso.com) reachable from the guest VLAN over DNS and TCP 443, and a guest portal created on Guests › Guest portal. - An administrator with
policy:writein Airgate (Tenant Administrator or Network Administrator).
Step 1: Decide where RADIUS comes from
Section titled “Step 1: Decide where RADIUS comes from”| Mode | RADIUS source | CoA target | Add to Airgate |
|---|---|---|---|
| Dynamic RADIUS proxy on | The virtual controller IP | The VC IP | One device with the VC IP, for example 10.0.10.5. |
| Dynamic RADIUS proxy off (default) | Each AP’s own IP | The AP that holds the session | The AP subnet, for example 10.0.10.0/24. |
With the proxy on, every AP’s request arrives from the VC IP and Airgate sends CoA there. If the device entry is a subnet and you want CoA to go to the VC, add the custom attribute CoA-Address = the VC IP on the device entry.
To turn the proxy on (CLI, Instant 8.x):
dynamic-radius-proxyStep 2: Add the APs in Airgate
Section titled “Step 2: Add the APs in Airgate”- Go to Network › Switches and APs › Add device.
- Name
branch-iap, IP address or subnet10.0.10.5(proxy on) or10.0.10.0/24(proxy off). - Vendor profile: Aruba Instant / AOS 10 APs (Central). 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) with CoA port
3799. - Select Save.
Step 3: Add Airgate as RADIUS server
Section titled “Step 3: Add Airgate as RADIUS server”wlan auth-server Airgate ip 203.0.113.10 port 1812 acctport 1813 key <shared-secret> rfc3576 nas-ip 10.0.10.5rfc3576lets the cluster accept CoA and Disconnect from this server on UDP 3799.nas-ipsets NAS-IP-Address; use the VC IP when the dynamic RADIUS proxy is on.
Step 4: 802.1X SSID
Section titled “Step 4: 802.1X SSID”wlan ssid-profile Corp-WiFi enable type employee essid Corp-WiFi opmode wpa2-aes vlan 20 auth-server Airgate radius-accounting radius-accounting-mode user-authentication radius-interim-accounting-interval 10Airgate can return a role with Aruba-User-Role or a VLAN with the RFC 3580 attributes (Tunnel-Type, Tunnel-Medium-Type, Tunnel-Private-Group-Id) or Aruba-User-Vlan. Create the roles you return as wlan access-rule <role-name> on the cluster. Build the matching enforcement profile on Access › Enforcement profiles from the Aruba RADIUS Enforcement or VLAN Enforcement template.
To add MAC authentication on the same SSID (for devices without a supplicant), add mac-authentication and l2-auth-failthrough to the SSID profile.
Step 5: Guest SSID with the Airgate captive portal
Section titled “Step 5: Guest SSID with the Airgate captive portal”The guest flow: the AP MAC-authenticates the device, Airgate answers with a captive-portal role, the role redirects web traffic to the Airgate portal, the guest signs in, the portal posts the credentials to the AP (https://<switchip>/cgi-bin/login), and the AP sends a RADIUS PAP request that Airgate answers with the guest role. Airgate can also cache the MAC and re-authenticate it with CoA.
wlan external-captive-portal Airgate-CP server airgate.contoso.com port 443 url "/portal/<tenant>/<portal>" auth-text "Authenticated" server-offline-action block-user switch-ip!wlan access-rule Airgate-Guest-Portal captive-portal external profile Airgate-CP rule any any match udp 67 68 permit rule any any match udp 53 53 permit rule 203.0.113.20 255.255.255.255 match tcp 443 443 permit rule any any match any any any deny!wlan access-rule Guest-Internet rule 10.0.0.0 255.0.0.0 match any any any deny rule 172.16.0.0 255.240.0.0 match any any any deny rule 192.168.0.0 255.255.0.0 match any any any deny rule any any match any any any permit!wlan ssid-profile Corp-Guest enable type guest essid Corp-Guest opmode opensystem vlan 30 mac-authentication auth-server Airgate radius-accounting radius-interim-accounting-interval 10 set-role-mac-auth Airgate-Guest-Portal captive-portal disable- Replace
203.0.113.20with the address of the Airgate portal host, and<tenant>/<portal>with the path shown in the portal editor. switch-ipmakes the redirect include the AP’s address (switchip), which Airgate needs to post the login. The redirect also carriesmac,ip,essid,apname,vcnameandurl.
In Airgate, open the portal on Guests › Guest portal, section Login & network:
| Field | Value |
|---|---|
| Vendor handling | Aruba (AOS 8 / Instant / AOS 10) or Auto-detect |
| Login model | Web login (or MAC caching + CoA to re-authenticate the MAC instead) |
| Post-login CoA | Reauthenticate (when you use MAC caching) |
Then create two enforcement profiles from the Aruba RADIUS Enforcement template, Aruba-User-Role = Airgate-Guest-Portal and Aruba-User-Role = Guest-Internet, and an access policy for the guest SSID that sends the internet role to known guests and the portal role to everyone else. See Guest portal for the full policy.
Verify
Section titled “Verify”- Connect to
Corp-WiFi. In Monitor › Sign-in log the record shows the AP or VC under Switch / AP and theAruba-User-Rolesent on the Output tab. - Connect to
Corp-Guest. The browser opens the Airgate portal. After sign-in, a second record shows the guest role. - In Monitor › Connected now, choose Reauthenticate on the session. The result is
CoA-ACK. - On the cluster,
show clientsshows the client with the expected role.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| No requests in the Sign-in log from some APs | Proxy off and only the VC IP is registered | Register the AP subnet, or turn on dynamic-radius-proxy. |
CoA timeout |
CoA goes to an AP while the proxy is on, or rfc3576 is missing |
Add rfc3576 to the auth server; set CoA-Address to the VC IP. |
| Portal shows “the controller did not send its login host (switchip)” | switch-ip is missing in the external captive-portal profile |
Add switch-ip. |
| Portal page does not load | The portal host is blocked by the captive-portal role | Allow DNS and TCP 443 to the portal host in the role. |
| Role not applied | The returned role name does not exist on the cluster | Create the wlan access-rule with the exact name sent in Aruba-User-Role. |