Learning paths › JNCIA-Junos › The CLI, the candidate configuration and initial setup
The CLI, the candidate configuration and initial setup
Operational and configuration mode, moving around the configuration tree, piping show output, editing the candidate privately or exclusively, commit confirmed and rollback — then the same series carries straight on into first-day setup: hostname and management reachability, named accounts and login classes, RADIUS or TACACS+ with a local fallback, interface addressing, NTP and syslog.
Lessons
- Move between operational and configuration mode
- Move around the configuration tree with edit, up and top
- Discover valid syntax without guessing keywords
- Choose terse, detail or extensive for the question asked
- Pipe show output down to the lines you need
- Change the candidate without touching the running system
- Edit privately or share a candidate with other engineers
- Validate and activate a change, or confirm it first
- Get back to a known configuration in one command
- Save and load configuration in the matching format
- Do the same work from the web interface
- Run the whole change cycle: edit, diff, commit, verify
- Decide what a device needs beyond an address
- Recognise an unconfigured box and its platform baseline
- Give a new device identity and a reachable path
- Create named accounts so activity is attributable
- Grant a role only the permissions it needs
- Authenticate against RADIUS or TACACS+ with a local fallback
- Read an interface name down to its logical unit
- Put an IPv4 address on a logical unit
- Add an IPv6 address under family inet6
- Apply one block of settings to many interfaces
- Synchronise the clock so timestamps can be correlated
- Choose the facilities and severities worth recording