Just a few items I’ve found useful. I’ve noted them here for future reference/reminder.
Commit Confirm
Nothing is more comforting than the commit confirm feature, especially when working remotely. I make a habit of using this feature when working with distant devices.
The feature is simple – a commit is applied to the running config for a period of time (10min default) – then automatically rolled back after this period has elapsed. You apply a second commit during the rollback phase to commit the changes permanently. In other words – apply some changes, if you goofed – your changes will be reverted for you.
commit confirmed 15 <em>configuration check succeeds commit confirmed will be automatically rolled back in 15 minutes unless confirmed commit complete # commit confirmed will be rolled back in 15 minutes</em>
You can view how much time is remaining on a confirmation
show system commit # commit confirmed will be rolled back in 9 minutes</em>
Lock in the config.
commit check
Disable management link monitoring
In some scenarios it doesn’t make sense to have the management port connected.
This triggers the angry little amber light of doom.
set chassis alarm management-ethernet link-down ignore
All is good in the world again.
Output the configuration as input
Using the following, you can dump the configuration as a means for input.
show configuration |no-more | display set
Version Control
You can add some configuration, to upload a copy of the configuration each time it is commited.
configuration {
transfer-on-commit;
archive-sites {
"scp://switch-configs@backuphost:/home/switch-configs" password "123456789";
}
}
Renaming a VLAN
You can use the ‘replace’ command to alter the configuration – however be cautious as it will replace any matching values throughout the configuration, not just vlans.
replace pattern "old-vlan" with "new-vlan"
A safer option is to use the rename command.
rename [path to-the-area required] [value1] to [value2]