3-2
Using the Command Line Interface (CLI)
Using the CLI
U
si
n
g t
h
e Co
m
m
a
n
d
Li
ne
In
te
rf
ac
e (
C
LI
)
When you use the CLI to make a configuration change, the switch writes the
change to the Running-Config file in volatile memory. This allows you to test
your configuration changes before making them permanent. To make changes
permanent, you must use the
write memory
command to save them to the
Startup Config file in non-volatile memory. If you reboot the switch without
first using
write memory
, all changes made since the last reboot or
write memory
(whichever is later) will be lost. For more on switch memory and saving
configuration changes, see appendix C, “Switch Memory and Configuration.”
N o t e
CLI configuration changes are not saved from the Menu interface to the
startup-config file unless you make a configuration change in the Menu
interface before using the
Save
command. That is, if you use the CLI to make
a change to the running-config file and then go to the Menu interface and
execute a
Save
command without making a configuration change in the Menu
interface, the CLI change made to the running-config file is not saved to the
startup-config file. (You can still save the change by returning to the global
configuration level in the CLI and executing
write memory
).
Privilege Levels at Logon
Privilege levels control the type of access to the CLI. To implement this
control, you must set at least a Manager password.
Without a Manager
password configured, anyone having serial port, Telnet, or web browser
access to the switch can reach all CLI levels
. (For more on setting passwords,
see “Using Password Security” on page 7-2.)
When you use the CLI to log on to the switch, and passwords are set, you will
be prompted to enter a password. For example:
Figure 3-1. Example of CLI Log-On Screen with Password(s) Set
SMC 6624M TigerStack II 10/100
Firmware revision F.02.07
Password:
Password Prompt
