Cisco Nexus 5600 Series - Discarding Changes; Saving the Configuration; Clearing a Locked Session

You can commit changes for a specified feature by entering the commit command for that feature.
Discarding Changes
If you discard configuration changes, the application flushes the pending database and releases locks in the
network. Both the abort and commit functions are supported only from the switch from which the network
lock is acquired.
You can discard changes for a specified feature by using the abort command for that feature.
Saving the Configuration
Configuration changes that have not been applied yet (still in the pending database) are not shown in the
running configuration. The configuration changes in the pending database overwrite the configuration in the
effective database when you commit the changes.
If you do not commit the changes, they are not saved to the running configuration.Caution
Clearing a Locked Session
You can clear a lock held by an application from any device in the fabric.
When you clear a lock in the fabric, any pending configurations in any device in the fabric are discarded.Caution
Before You Begin
You must have administrator permissions to release a lock.
Procedure
PurposeCommand or Action
(Optional)
Shows the current application state.
switch# show application-name status
Step 1
Clears the application configuration session and
releases the lock on the fabric. All pending changes
are discarded.
switch# clear application-name session
Step 2
(Optional)
Shows the current application state.
switch# show application-name status
Step 3
switch# show ntp status
Distribution : Enabled
Last operational state: Fabric Locked
switch# clear ntp session
Cisco Nexus 5600 Series NX-OS System Management Configuration Guide, Release 7.x
OL-31641-01 43
Using Cisco Fabric Services
Discarding Changes