Switch and router logins with TACACS+
Network engineers log in to switches, routers and firewalls with their own directory accounts instead of shared local passwords. Airgate checks the password, picks the privilege level from the engineer’s group, and records every login and, with command accounting, every command.
How it works
Section titled “How it works”The network device sends TACACS+ (TCP port 49) to Airgate. Airgate:
- finds the device by its source address and checks the TACACS+ shared secret;
- checks the user name and password in Local users and the directories you tick (ASCII, PAP and CHAP logins);
- runs the Switch and router logins rules: the first matching rule sets the privilege level;
- answers the device with
priv-lvl(Cisco-style devices) andAruba-Admin-Role(Aruba controllers and Instant:rootfor level 15,network-operationsfor 7,read-onlyfor 1); - records the login in Monitor › Admin login log.
Before you begin
Section titled “Before you begin”- The directory with the engineers’ accounts is set up under Access › Directories (for example Active Directory or Entra ID), or the engineers exist under Access › Local users.
- The network devices reach the Airgate TACACS+ address (here
203.0.113.10) on TCP 49, directly or through a site connector. - An administrator role with
policy:write. - A local emergency account on every device, in case Airgate cannot be reached.
Step 1: Add the devices with a TACACS+ secret
Section titled “Step 1: Add the devices with a TACACS+ secret”- Open Network › Switches and APs and add or edit the device (or a subnet of devices).
- On the RADIUS, CoA & RadSec tab, fill in TACACS+ shared secret. Use a long random secret.
- Save.
To give core switches different rules, put them in a group under Network › Device groups.
Step 2: Point the devices at Airgate
Section titled “Step 2: Point the devices at Airgate”Cisco IOS / IOS-XE (replace the address and secret):
aaa new-modeltacacs server AIRGATE address ipv4 203.0.113.10 key 0 <TACACS+ shared secret>aaa group server tacacs+ AIRGATE-GRP server name AIRGATEaaa authentication login default group AIRGATE-GRP localaaa authorization exec default group AIRGATE-GRP local if-authenticatedaaa accounting exec default start-stop group AIRGATE-GRPaaa accounting commands 15 default start-stop group AIRGATE-GRPline vty 0 15 login authentication defaultAruba AOS-CX:
tacacs-server host 203.0.113.10 key plaintext <TACACS+ shared secret>aaa group server tacacs AIRGATE server 203.0.113.10aaa authentication login ssh group AIRGATE localaaa authorization commands ssh group AIRGATE noneaaa accounting all-mgmt ssh start-stop group AIRGATEKeep local at the end of the login lines, so the local account still works
when Airgate cannot be reached. Other vendors (Juniper, Fortinet, Edgecore…)
have equivalent “TACACS+ server, authentication, authorization, accounting”
settings.
Step 3: Create the login rules
Section titled “Step 3: Create the login rules”-
Open Access › Access policies and select the Switch and router logins tab.
-
Under Accounts are checked in, tick the directories with your engineers’ accounts. Local users is always checked.
-
Add a rule for each group:
Order Rule When Then 1 Network adminsUser is in group Corp AD/Network-AdminsAllow, Full admin (level 15) 2 HelpdeskUser is in group Corp AD/HelpdeskAllow, Read-only (level 1) Default Deny Operator (level 7) is the third level. Add Network device group is to limit a rule to a group of devices, for example core switches only.
-
Select Save changes.
Verify
Section titled “Verify”- Log in to a switch over SSH with your directory account.
- Run
show privilege(Cisco): the level matches the rule. - Monitor › Admin login log: the authentication (Pass / permit), the authorization with the rule and privilege level, and with command accounting every command that was run, with the Administrator and Device.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
Admin login log: error undecodable TACACS+ packet (shared secret mismatch?); the device falls back to its local account |
The secrets on the device and in Airgate differ. | Re-enter the TACACS+ shared secret on both sides. An alert is also raised in Monitor › Alerts and events. |
| Nothing in the Admin login log | The device’s source address is not a network device in Airgate, or TCP 49 is blocked. | Add the device (its management or loopback address) under Switches and APs; check the firewall. |
| Admin login log: No account named “…” | The account is not in Local users or a ticked directory. | Tick the directory under Accounts are checked in. |
| Admin login log: Wrong password | Wrong password. | Check the account; for Entra ID, password logins fail for accounts that need MFA. |
| Admin login log: Denied: member of group check failed | The user is not in the rule’s group. | Add the user to the group in the directory, or change the rule. |
Admin login log: reason no TACACS+ service matched |
The Switch and router logins rules were never saved. | Open the tab and select Save changes. |
Authorization fails with no cached TACACS+ login for this user |
The device authorizes without logging in through Airgate. | Use aaa authentication login … group <Airgate>. |