Connectivity Guide

CLI Basics
The OS10 CLI is the software interface you use to access a device running the software — from the console or through a network
connection. The CLI is an OS10-specic command shell that runs on top of a Linux-based OS kernel. By leveraging industry-standard tools
and utilities, the CLI provides a powerful set of commands that you can use to monitor and congure devices running OS10.
User accounts
OS10 denes two categories of user accounts — use admin for both the username and password to log into the CLI, or use
linuxadmin to log into the Linux shell.
NOTE: You cannot delete the default admin and linuxadmin usernames.
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 identies 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 conguration statements.
CLI command modes
The OS10 CLI has two top-level modes:
• EXEC mode — Monitor, troubleshoot, check status, and network connectivity.
• CONFIGURATION mode — Congure network devices.
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 Transaction-Based
Conguration mode, enter the start transaction command. When you switch to the Transaction-Based Conguration mode, you
update 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 Conguration 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 mode session and
continue with the remaining conguration changes.
Getting Started
39