Step 1.16

Move to the [edit protocols ospf] portion of the hierarchy. This step requires that you first visit the root of the hierarchy, as you cannot jump directly between branches. You can perform this step with a single command in the form of top edit protocols ospf, however.

[edit interfaces]

lab@srxA-1# top edit protocols ospf

[edit protocols ospf] lab@srxA-1#

Question: Which commands can you now enter to reposition yourself at the [edit] portion of the hierarchy? Return to the [edit] hierarchy level now.

Answer: You can issue an up command twice, or an up 2 command. You can also issue an exit command or a top command.

[edit protocols ospf] lab@srxA-1# top

[edit] lab@srxA-1#

Note

If you have not already done so, return to the [edit] hierarchy level using one of the available methods.

Step 1.17

Try to display the status of chassis hardware with a show chassis hardware operational command while in configuration mode.

[edit]

lab@srxA-1# show chassis hardware

^

syntax error.

Question: Why do you think you received an error? What can you do to execute operational mode commands while in configuration mode? Try that now.

Answer: The command issued is not valid in configuration mode. Precede operational mode commands with the keyword run to execute them while in configuration mode:

Power Supply 0

Step 1.18

Try to return to operational mode by entering an exit command.

[edit] lab@srxA-1# exit

The configuration has been changed but not committed Exit with uncommitted changes? [yes,no] (yes)

Question: What happens when you execute the exit command?

Answer: You should see a message indicating that uncommitted changes exist. This message results from the creation of an empty [edit protocols ospf] stanza. This empty stanza causes the configuration database to believe that the configuration actually changed.

Question: Which CLI command can you use to display differences between the candidate and active configuration file? Enter no at the current prompt and issue the required command to view the differences between the candidate and active configurations.

Answer: Use the show command with the results piped to compare rollback number. In this example, you should not see any actual configuration changes, as shown in the following sample capture:

The configuration has been changed but not committed

Exit with uncommitted changes? [yes,no] (yes) no

Exit aborted

[edit]

lab@srxA-1# show | compare rollback 0

[edit] lab@srxA-1#

Question: Considering that nothing changed, which command can you enter to allow an exit from configuration mode without being warned of uncommitted changes? Issue that command now.

Answer: Issue a rollback 0 command to replace the candidate configuration with a new copy of the active configuration. You can now exit configuration mode without being warned of uncommitted changes:

[edit]

lab@srxA-1# rollback 0 load complete

[edit] lab@srxA-1# exit

Exiting configuration mode

lab@srxA-1>

Step 1.19

Log out of your assigned device using the exit command.