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-18
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 7 Using Cisco Fabric Services
CFS Example Using Device Manager
To configure the master or seed switch for distribution for each feature using Fabric Manager, perform
this task:
Step 1 Choose the feature that needs a merge master for CFS.
For example, expand Switches > Events, and then choose CallHome from the Physical Attributes pane.
The Information pane shows that feature including 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 Check the Master column check box for the switch to act as the merge master for this feature.
Step 4 Click the Apply Changes icon to select this switch as master for future CFS distributions.
.
CFS Example Using Device Manager
This procedure is an example of what you see when you use Device Manager to configure a feature that
uses CFS. For specific procedures for features that use CFS, refer to that feature’s documentation.
To configure a feature that uses CFS using Device Manager, perform this task:
Step 1 Open the dialog box for any CFS-capable feature.
Device Manager checks to see whether CFS is enabled. It also checks to see if there is a lock on the
feature by checking for at least one entry in the Owner table. If CFS is enabled and there is a lock, Device
Manager sets the status to pending for that feature. You see a dialog box displaying the lock information.
Step 2 Click Continue or Cancel when prompted. If you continue, Device Manager remembers the CFS status.
Step 3 Choose Admin > CFS (Cisco Fabric Services) to view the user name of the CFS lock holder.
Step 4 Click the locked feature and click Details.
Step 5 Click the Owners tab and look in the UserName column.
Note Device Manager does not monitor the status of the feature across the network until you click
Refresh. If a user on another CFS-enabled switch attempts to configure the same feature, they
do not see the pending status. However, their configuration changes are rejected by your switch.
Step 6 If CFS is enabled and there is no lock, Device Manager sets the status to running for that feature.
You then see a dialog box for the feature. As soon as you perform a creation, deletion, or modification,
Device Manager changes the status to pending and displays the updated information from the pending
database.
Step 7 View the CFS table for a feature. Device Manager only changes the status to running when commit,
clear, or abort is selected and applied. Device Manager will not change the status to pending if enable
is selected, because the pending status does not apply until the first actual change is made.
The Last Command and Result fields are blank if the last command is noOp.