Operational Mode:
The operational mode CLI commands are used to monitor and control the operation of a device running the Junos OS. The operational mode commands exist in a hierarchical structure, as shown in the graphic. Eg. the show command displays various types of information about the system and its environment. One of the possible options for the show command is ospf, which displays information about the Open Shortest Path First (OSPF) protocol. Specifying the interface option, as in the show ospf interface command, outputs information on OSPF interfaces.
Another flexibility of Junos OS is issuing operational mode commands while in configuration mode. It is done with the help of 'run' command. Will be discussed later.
Batch Configuration:
Configuration changes made in Junos OS does not take effect immediately. This design feature allows you to group together and supply multiple configuration changes to the running configuration as a single unit.
Active Configuration:
The active configuration is the configuration currently operational on the system and is the configuration the system loads during the boot sequence. It is also known as running configuration and startup configuration in other software vendors.
Candidate Configuration:
The candidate configuration is a temporary configuration that might possibly become the active configuration. When you configure a device running the Junos OS, the software creates a candidate configuration and initially populates it with the active configuration running on the device. We then modify the candidate configuration, once satisfied with modifications we can commit the changes. This action causes the candidate configuration to become the active configuration.
The 'configure' command is used to make some changes on active configuration and populated with the contents of the active configuration. After the change is made, 'commit' command is used to save the configuration and make it active. You can easily recover previous configurations by using a 'rollback n' command. The Junos OS maintains a configuration history by storing previously active configurations. The software saves a maximum of 50 configurations. this number indicates the current active configuration, which is also known as rollback 0, and upto 49 previously active configurations.
The operational mode CLI commands are used to monitor and control the operation of a device running the Junos OS. The operational mode commands exist in a hierarchical structure, as shown in the graphic. Eg. the show command displays various types of information about the system and its environment. One of the possible options for the show command is ospf, which displays information about the Open Shortest Path First (OSPF) protocol. Specifying the interface option, as in the show ospf interface command, outputs information on OSPF interfaces.
Another flexibility of Junos OS is issuing operational mode commands while in configuration mode. It is done with the help of 'run' command. Will be discussed later.
Batch Configuration:
Configuration changes made in Junos OS does not take effect immediately. This design feature allows you to group together and supply multiple configuration changes to the running configuration as a single unit.
Active Configuration:
The active configuration is the configuration currently operational on the system and is the configuration the system loads during the boot sequence. It is also known as running configuration and startup configuration in other software vendors.
Candidate Configuration:
The candidate configuration is a temporary configuration that might possibly become the active configuration. When you configure a device running the Junos OS, the software creates a candidate configuration and initially populates it with the active configuration running on the device. We then modify the candidate configuration, once satisfied with modifications we can commit the changes. This action causes the candidate configuration to become the active configuration.
The 'configure' command is used to make some changes on active configuration and populated with the contents of the active configuration. After the change is made, 'commit' command is used to save the configuration and make it active. You can easily recover previous configurations by using a 'rollback n' command. The Junos OS maintains a configuration history by storing previously active configurations. The software saves a maximum of 50 configurations. this number indicates the current active configuration, which is also known as rollback 0, and upto 49 previously active configurations.
No comments:
Post a Comment