Connectivity Guide
Key CLI features
Consistent
command names
Commands that provide the same type of function have the same name, regardless of the portion of the system
on which they are operating. For example, all show commands display software information and statistics, and all
clear commands erase various types of system information.
Available commands Information about available commands is provided at each level of the CLI command hierarchy. You can enter a
question mark (?) at any level and view a list of the available commands, along with a short description of each
command.
Command
completion
Command completion for command names (keywords) and for command options is available at each level of the
hierarchy. To complete a command or option that you have partially entered, click the Tab key or the Spacebar. If
the partially entered letters are a string that uniquely identies a command, the complete command name appears.
A beep indicates that you have entered an ambiguous command, and the possible completions display. Completion
also applies to other strings, such as interface names and conguration statements.
CLI command modes
The OS10 CLI has two top-level modes:
• EXEC mode — Monitor, troubleshoot, check status, and network connectivity.
• CONFIGURATION mode — Congure network devices.
When you enter CONFIGURATION mode, you are changing the current operating conguration, called the running conguration. By
default, all conguration changes are automatically saved to the running conguration.
You can change this default behavior by switching to the Transaction-Based Conguration mode. To switch to Transaction-Based
Conguration mode, enter the start transaction command. When you switch to the Transaction-Based Conguration mode, you
update the candidate conguration. Changes to the candidate conguration are not added to the running conguration until you commit
them, which activates the conguration. The
start transaction command applies only to the current session. Changing the
conguration mode of the current session to the Transaction-Based Conguration mode does not aect the conguration mode of other
CLI sessions.
• After you explicitly enter the commit command to save changes to the candidate conguration, the session switches back to the
default behavior of automatically saving the conguration changes to the running conguration.
• When a session terminates while in the Transaction-Based Conguration mode, and you have not entered the commit command, the
changes are maintained in the candidate conguration. You can start a new Transaction-Based Conguration mode session and
continue with the remaining conguration changes.
• All sessions in Transaction-Based Conguration mode update the same candidate conguration. When you enter the commit
command on any session in Transaction-Based Conguration mode or you make conguration changes on any session in Non-
Transaction-Based mode, you also commit the changes made to the candidate conguration in all other sessions running in the
transaction-based conguration mode. This implies that inconsistent conguration changes may be applied to the running conguration.
Dell EMC recommends only making conguration changes on a single CLI session at a time.
• When you enter the lock command in a CLI session, conguration changes are disabled on all other sessions, whether they are in
Transaction-Based Conguration mode or Non-Transaction-Based Conguration mode. For more information, see Candidate
conguration.
Getting Started
45