Reference Guide

When you enter CONFIGURATION mode, you are changing the current operating conguration, called the running conguration. By

default, all conguration changes are automatically saved to the running conguration.

You can change this default behavior by switching to the transaction-based conguration mode. To switch to the transaction-based

conguration mode, enter the start transaction command. When you switch to the transaction-based conguration mode, you are

updating the candidate conguration. Changes to the candidate conguration are not added to the running conguration until you commit

them, which activates the conguration. The

start transaction command applies only to the current session. Changing the

conguration mode of the current session to the transaction-based mode does not aect the conguration mode of other CLI sessions.

• After you explicitly enter the commit command to save changes to the candidate conguration, the session switches back to the

default behavior of automatically saving the conguration changes to the running conguration.

• When a session terminates while in the transaction-based conguration mode, and you have not entered the commit command, the

changes are maintained in the candidate conguration. You can start a new transaction-based conguration session and continue with

the remaining conguration changes.

• All sessions in the transaction-based conguration mode update the same candidate conguration. When you enter the commit

command on any session in the transaction-based conguration mode or you make conguration changes on any session in the non-

transaction-based mode, you also commit the changes made to the candidate conguration in all other sessions running in the

transaction-based conguration mode. This implies that inconsistent conguration changes may be applied to the running conguration.

Dell EMC recommends that you only make conguration changes on a single CLI session at a time.

• When you enter the lock command in a CLI session, conguration changes are disabled on all other sessions, whether they are in the

transaction-based conguration mode or the non-transaction-based conguration mode. For more information, see Candidate

conguration.

CLI command hierarchy

CLI commands are organized in a hierarchy. Commands that perform a similar function are grouped together under the same level of

hierarchy. For example, all commands that display information about the system and the system software are grouped under the show

system command, and all commands that display information about the routing table are grouped under the show route-map

command.

CLI command categories

There are several broad groups of CLI commands available:

set

Controls the CLI environment and congure the CLI screen.

ssh Connects to other network systems or to open secure shell connections.

copy Copies les from one location on a device to another, from a device to a remote system, or from a remote system

to a device.

congure Enters CONFIGURATION mode to congure routing protocols, interfaces, network management, and user access.

exit Moves up one command mode. Use the end command to go directly to EXEC mode.

quit Leaves or exits the CLI.

CONFIGURATION Mode

When you initially log in to OS10, you are automatically placed in EXEC mode by default. To access CONFIGURATION mode, enter the

configure terminal command. Use CONFIGURATION mode to manage interfaces, protocols, and features.

Interface mode is a sub-mode of CONFIGURATION mode. Interface mode is where you congure Layer 2 and Layer 3 protocols, and IPv4

and IPv6 services specic to an interface:

Getting Started