Skip to content

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.

The network device sends TACACS+ (TCP port 49) to Airgate. Airgate:

  1. finds the device by its source address and checks the TACACS+ shared secret;
  2. checks the user name and password in Local users and the directories you tick (ASCII, PAP and CHAP logins);
  3. runs the Switch and router logins rules: the first matching rule sets the privilege level;
  4. answers the device with priv-lvl (Cisco-style devices) and Aruba-Admin-Role (Aruba controllers and Instant: root for level 15, network-operations for 7, read-only for 1);
  5. records the login in Monitor › Admin login log.
  • 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”
  1. Open Network › Switches and APs and add or edit the device (or a subnet of devices).
  2. On the RADIUS, CoA & RadSec tab, fill in TACACS+ shared secret. Use a long random secret.
  3. Save.

To give core switches different rules, put them in a group under Network › Device groups.

Cisco IOS / IOS-XE (replace the address and secret):

aaa new-model
tacacs server AIRGATE
address ipv4 203.0.113.10
key 0 <TACACS+ shared secret>
aaa group server tacacs+ AIRGATE-GRP
server name AIRGATE
aaa authentication login default group AIRGATE-GRP local
aaa authorization exec default group AIRGATE-GRP local if-authenticated
aaa accounting exec default start-stop group AIRGATE-GRP
aaa accounting commands 15 default start-stop group AIRGATE-GRP
line vty 0 15
login authentication default

Aruba AOS-CX:

tacacs-server host 203.0.113.10 key plaintext <TACACS+ shared secret>
aaa group server tacacs AIRGATE
server 203.0.113.10
aaa authentication login ssh group AIRGATE local
aaa authorization commands ssh group AIRGATE none
aaa accounting all-mgmt ssh start-stop group AIRGATE

Keep 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.

  1. Open Access › Access policies and select the Switch and router logins tab.

  2. Under Accounts are checked in, tick the directories with your engineers’ accounts. Local users is always checked.

  3. Add a rule for each group:

    Order Rule When Then
    1 Network admins User is in group Corp AD / Network-Admins Allow, Full admin (level 15)
    2 Helpdesk User is in group Corp AD / Helpdesk Allow, 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.

  4. Select Save changes.

  1. Log in to a switch over SSH with your directory account.
  2. Run show privilege (Cisco): the level matches the rule.
  3. 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.
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>.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security