Reference Guide

Prevent conguration changes
You can prevent conguration changes on sessions other than the current CLI session using the lock command. Use the lock and
unlock commands in EXEC mode to respectively prevent and allow conguration changes on other sessions. When you enter the lock
command on a CLI session, users cannot make conguration changes across any other active CLI sessions. When you close the CLI session
on which you entered the lock command, conguration changes are automatically allowed on all other sessions.
Lock conguration changes
OS10# lock
Unlock conguration changes
OS10# unlock
Change to transaction-based conguration
To change to transaction-based conguration mode for a session, enter the start transaction command
1 Change to transaction-based conguration in EXEC mode.
start transaction
2 Enable, for example, an interface from INTERFACE mode.
interface ethernet 1/1/1/
no shutdown
3 Save the conguration.
do commit
NOTE
: After you enter the do commit command, the current session switches back to the default behavior of
committing all conguration changes automatically.
Save conguration changes manually
OS10# start transaction
OS10# configure terminal
OS10(config)#
OS10(config)# interface ethernet 1/1/1
OS10(config-if-eth1/1/1)# no shutdown
OS10(config-if-eth1/1/1)# do commit
Back up or restore conguration
The running conguration contains the current system conguration which you can copy to and from a server for backup and restore
purposes. You can also copy the running conguration locally to and from the home: and cong: directories on the switch.
The startup conguration le is maintained in the cong system folder and is called system.xml. When you make changes to conguration
les, use the reload command to reboot OS10 with the updated conguration.
Copy the running conguration to the startup conguration
OS10# copy running-configuration startup-configuration
View /cong directory
OS10# dir config
Directory contents for folder: config
Getting Started
35