Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide, NX-OS 4.0 (OL-16598-01, June 2008)

Send comments to [e-mail]
7-8
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 7 Using Cisco Fabric Services
CFS Support for Applications
To enable CFS for a feature using Device Manager, perform this task:
Step 1 Choose Admin > CFS (Cisco Fabric Services).
You see the CFS dialog box with the CFS status for all features on that switch.
Step 2 Decide which features need CFS. Set the Command column to either enable to enable CFS or disable
to disable CFS.
Note Enable or disable CFS for all switches in the network or VSAN for the feature that uses CFS.
Step 3 Click Pending Differences to compare the configuration of this feature on this switch to other switches
in the network or VSAN that have CFS enabled for this feature. Close the Show Pending Diff dialog box.
Step 4 Click Apply to apply the CFS configuration change.
Device Manager retrieves the status of the CFS change and updates the Last Command and Result
columns.
Locking the Network
When you configure (first time configuration) a feature (or application) that uses the CFS infrastructure,
that feature starts a CFS session and locks the network. When a network is locked, the switch software
allows configuration changes to this feature only from the switch holding the lock. If you make
configuration changes to the feature from another switch, the switch issues a message to inform the user
about the locked status. The configuration changes are held in a pending database by that application.
If you start a CFS session that requires a network lock but forget to end the session, an administrator can
clear the session. If you lock a network at any time, your user name is remembered across restarts and
switchovers. If another user (on the same machine) tries to perform configuration tasks, that user’s
attempts are rejected.
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:
• One or more external switches report a successful status—The application applies the changes
locally and releases the network 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 network. The network lock is not released.
You can commit changes for a specified feature by for that feature.