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-9
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 7 Using Cisco Fabric Services
CFS Support for Applications
To commit changes using Fabric Manager for CFS-enabled features, perform this task:
Step 1 Choose the feature you want to enable CFS for.
For example, expand Switches expand Events, and then choose CallHome from the Physical Attributes
pane.
The Information pane shows that feature with a CFS tab.
Step 2 Click the CFS tab to display the CFS state for each switch in the network for that feature.
Step 3 Right-click the value in the Config Action column for any switch and choose an option from the
drop-down menu (Copy, Paste, Export to File, Print Table, Detach Table).
Step 4 Click the Apply Changes icon to commit the configuration changes for that feature and distribute the
changes through CFS.
Fabric Manager retrieves the status of the CFS change and updates the Last Command and Last Result
columns for the feature or VSAN.
To commit changes using Device Manager for CFS-enabled features, 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 For each applicable feature, set the Command column to commit to commit the configuration changes
for that feature and distribute the changes through CFS, or set it to abort to discard the changes for that
feature and release the network lock for CFS for that feature.
Step 3 Optionally, provide a Type or VsanID as the basis for the CFS distribution for CFS features that require
this information.
Step 4 Click Pending Differences to check the configuration of this feature on this switch as compared to other
switches in the network or VSAN that have CFS enabled for this feature.
Step 5 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.
Caution If you do not commit the changes, they are not saved to the running configuration.
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 only supported from the switch from which the
network lock is acquired.
You can discard changes for a specified feature by setting the Command column value to disable for that
feature then clicking Apply.