Glossary
The words tacctl and this documentation use, in one list · Checked against tacctl 0.2.22
Terms are in alphabetical order. Each entry points to the page that explains it in full.
| Term | Meaning | More |
|---|---|---|
| Accounting | The server’s record of commands run on devices. tacctl log accounting shows it. |
Audit and Compliance |
| Apply | Junos only: tacctl commits a plan under commit confirmed, proves it with a fresh login as you, then confirms. |
Engineer Guide §5.1 |
| Audit line | A syslog line (tags tacctl, tacctl-console) that tacctl writes for every change and refusal: who, what, result, snapshot. |
Audit and Compliance |
| Back-out | The lines that undo a plan’s paste. tacctl device config plan <name> --backout prints them. |
Engineer Guide §7 |
| Break-glass account | A local emergency account on a device, recorded per scope with tacctl scope breakglass; on Junos it may be root. tacctl never stores its password. |
Break Glass §1 |
| Break-glass hold | The server stops answering one device or host on purpose, so its local accounts work. Never expires. | Break Glass |
| Canary | During a Junos apply, the first device of each new shape goes alone before the others. | Engineer Guide §5.1 |
| Client config | An ssh configuration file (tacctl device client-config) that gives plain ssh and scp the registry’s pinned host keys. |
Connecting to Devices §3 |
| Configured / unconfigured | A registered device is configured when a scope’s prefixes cover its address. Only configured devices authenticate users. | Concepts §4 |
| Console (login console) | The login shell of every tacctl user on the tacctl server: tacctl commands and ssh to devices, nothing else. | Getting Started §1 |
| Converge | device config plan --converge: after the first paste is verified, also remove statements outside the standard (old servers and similar). |
Engineer Guide §4 |
| Diff | What differs between a device’s last pull and what tacctl renders, section by section. | Engineer Guide §3 |
| Drift | Two uses: a device whose configuration differs from the standard (device config list --differs), and a rendered server file edited by hand (DRIFT, exit status 3). |
Exit Codes |
| Emergency lockdown | The server refuses the logins of chosen groups on a scope. Superusers keep access. Never expires. | Emergency Lockdown |
| Enroll (device) | tacctl device enroll: one attended run from a new address to its plan: key, vendor, registration, pull, plan. |
Engineer Guide §2.2 |
| Enroll (host) | tacctl host enroll: install TACACS+ or RADIUS login on a Linux host and register it. |
Linux Host Operations §3 |
| Extras | Statements in a managed section that tacctl does not render. Reported, left alone until --converge. |
Engineer Guide §4 |
| Group | Decides what a user can do: device privilege and tacctl tier. | Concepts §2 |
| Host key / pin | The device’s ssh host key. tacctl pins it at registration, and ssh accepts only the pinned key. | Connecting to Devices §5 |
| Host sync | tacctl host sync: push user changes to enrolled Linux hosts. Nothing reaches a host without it. |
Linux Host Operations §2 |
| Legacy ssh | A device setting for old IOS that offers only SHA-1 key exchange, CBC ciphers and ssh-rsa. Separate from the configuration syntax. |
Vendor Notes §2.4 |
| Managed sections | The parts of a device’s configuration tacctl compares: aaa, roles, mgmt-acl, snmp, netconf, breakglass, and in some scopes system. |
Concepts §6 |
| Managed server login | The login of every user to the tacctl server and its console: the reserved scope tacctl, this server’s registry entry, the PAM client and sshd’s drop-in. install and upgrade set it up; host enroll --local rebuilds or repairs it. |
Superuser Daily Operations §11.1 |
| Notice | A flag on a device or host that needs attention, with the command that fixes it. tacctl device notice list. |
Concepts §5 |
| Onboard | tacctl device onboard: bring a blank Junos device in through one of its local accounts. |
Engineer Guide §2.3 |
| Password cache | Keeps your network password in locked memory for the session. A superuser allows it per tier; each user turns it on with console password-cache on. With it on, ssh asks for the password the first time and keeps it. |
Getting Started §1.3 |
PENDING |
A Junos apply whose state could not be read after the commit. Type nothing on the device until the time shown (the device’s own clock) passes. | Vendor Notes §3.2 |
| Plan | The exact fix for a device: report, the region between PASTE FROM HERE and PASTE TO HERE, checks and back-out. |
Engineer Guide §4 |
| Pull | Log in to a device as you and read its managed sections. Read only. | Engineer Guide §3 |
| Reason | Free text given with --reason on lockdowns and holds. Logged as typed: never put a secret in it. |
Audit and Compliance §6 |
| Registry | The list of devices (and hosts) by name, with address, vendor and pinned keys. | Concepts §4 |
| Required password change | A user must change the password before logging in to anything but the tacctl server. Set by user add and a superuser’s user passwd by default; never binds a superuser. |
Access Lifecycle §5.1 |
| Restore point | Cisco: a copy of the configuration on flash, added before a plan’s region with --restore-point=flash:. |
Vendor Notes §2.5 |
| Scope | Client address prefixes plus a shared secret. Decides where a user can log in. | Concepts §3 |
| Secret (shared secret) | The TACACS+ or RADIUS key between a scope’s devices and the server. Every print writes a secret-read audit line. |
Concepts §3 |
| Server address | The address devices and hosts reach this server at: the setting server.addresses, shown and changed by tacctl server addresses. It is the default of --server. |
Superuser Daily Operations §11.2 |
| Severity | A plan’s rating of each problem: ACCESS, MONITORING or COSMETIC. |
Engineer Guide §4 |
| Shape | A set of devices that need the same change. A Junos apply groups its review by shape. | Engineer Guide §5.1 |
sid |
The session id that ends every audit line of one command run, so grep sid=<id> finds them all. |
Audit and Compliance §2 |
| Snapshot | A copy of tacctl’s configuration taken before every change. tacctl backup list. |
Backups and Undo |
| Status (user) | Enabled or disabled: decides whether a user can log in. | Access Lifecycle |
| System shell | A user’s own shell on the tacctl server, started with the console word system-shell. Superusers always; read-only and operator users when a superuser opens it; engineers never. |
Superuser Daily Operations §10.1 |
| Template user | Junos: the local account a TACACS+ user logs in through. Must exist before TACACS+ logins work. | Vendor Notes §3.1 |
| Tier | The level of tacctl access a group gives: read-only < operator < engineer < superuser. | Concepts §2 |
| Timing scale | A whole number from 1 to 10 that multiplies the network timings tacctl uses to reach a device, for a slow or distant one. Set for a device, a scope or the server; 1 changes nothing. | Connecting to Devices §7 |
See also: Concepts · Command Reference Map ·
man tacctl