Committing Changes; Discarding Changes; Saving The Configuration; Clearing A Locked Session - Cisco AP776A - Nexus Converged Network Switch 5020 Configuration Manual

Committing Changes

S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Committing Changes
A commit operation saves the pending database for all application peers and releases the lock for all
switches.
In general, the commit function does not start a session; only a lock function starts a session. However,
an empty commit is allowed if configuration changes are not previously made. In this case, a commit
operation results in a session that acquires locks and distributes the current database.
When you commit configuration changes to a feature using the CFS infrastructure, you receive a
notification about one of the following responses:
•
•
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 fabric. Both the abort and commit functions are only supported from the switch from which the fabric
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
The CISCO-CFS-MIB contains SNMP configuration information for any CFS-related functions. Refer
to the Cisco MDS 9000 Family MIB Quick Reference for more information on this MIB.

Clearing a Locked Session

You can clear locks held by an application from any switch in the fabric. This option is provided to rescue
you from situations where locks are acquired and not released. This function requires Admin
permissions.
The CFS locks can be cleared by using the following methods in the CLI:
•
Cisco MDS 9000 Family CLI Configuration Guide
7-8
One or more external switches report a successful status—The application applies the changes
locally and releases the fabric lock.
None of the external switches report a successful state—The application considers this state a failure
and does not apply the changes to any switch in the fabric. The fabric lock is not released.
Abort the configuration from the switch where the configuration lock was acquired previously. This
method clears the CFS locks in the entire fabric.
This example shows how to clear the CFS locks for the DPVM application in the entire fabric:
Chapter 7 Using the CFS Infrastructure
OL-18084-01, Cisco MDS NX-OS Release 4.x