New Training: Understand Junos Configuration Datastores
In this 11-video skill, CBT Nuggets trainer Knox Hutchinson explores the Junos architecture of configuration datastores and rollback capabilities. Watch this new Juniper training.
Learn Juniper with one of these courses:
This training includes:
- 11 videos
- 57 minutes of training
You’ll learn these topics in this skill:
- Understand Junos Configuration Datastores
- Introducing the Candidate Datastore (and Commit)
- Configure Private
- Configure Exclusive
- Other commit mechanisms
- Comparing Candidate and Active Configurations
- Rescue Configurations
- Archiving Configurations to Remote Servers
- Encrypting Configuration Files
- Summarizing Junos Candidate Datastores
Your Old Configurations Are Waiting for You When You Need Them in Junos
If you work on a network that uses Juniper devices, you’re probably familiar with committing configurations. For plenty of network administrators, the most time isn’t spent writing a configuration, but in amping yourself up to type the ‘commit’ command and assuring yourself you won’t screw the network up. Juniper devices are polite enough to check your configuration for syntax errors before committing, but they can’t possibly anticipate what’ll happen if something goes catastrophically wrong and the log shows it was your name that issued the command.
Hopefully it puts your heart at ease to learn that Junos also comes fully equipped with a ‘rollback’ command. Now, it can’t anticipate catastrophe either, but in the event that something goes wrong, it’s possible to return to a previously committed configuration so you have time to figure out what went wrong with your new config. And you don’t just have to return to the most recent config. By default, Junos stores the last 50 committed configurations, including its number, and the date and time it was committed.
Commit with a bit more confidence knowing that ‘rollback’ has your back.