Cfs Application Requirements - HP Cisco MDS 9216 - Fabric Switch Configuration Manual

Chapter 13 Using the CFS Infrastructure
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
Choose any CFS feature. For example, expand Switches > Events then select CallHome in the Physical
Step 1
Attributes pane.
The Information pane shows that feature, with a CFS tab.
Click the CFS tab to display the CFS state for each switch in the fabric for that feature.
Step 2
Click a value in the Global column—the value changes to a drop-down menu.
Step 3
From the drop-down menu choose disable or enable.
Step 4
Repeat steps 3 and 4 for all switches that you want to disable or enable CFS.
Step 5
Set the Config Action column to commit.
Step 6
Step 7 Click the Apply Changes icon to commit the configuration changes for that feature and distribute the
changes through CFS.
To globally disable or enable CFS distribution on a switch using Device Manager, follow these steps:
Choose Admin > CFS (Cisco Fabric Services).
Step 1
You see the CFS dialog box with the CFS status for all features on that switch.
Uncheck or check the Globally Enabled check box to disable or enable CFS distribution on this switch.
Step 2
Step 3 Click Apply to disable CFS on this switch.

CFS Application Requirements

All switches in the fabric must be CFS capable. A Cisco MDS 9000 Family switch is CFS capable if it
is running Cisco SAN-OS Release 2.0(1b) or later. Switches that are not CFS capable do not receive
distributions and result in part of the fabric not receiving the intended distribution.
CFS has the following requirements:
•
•
•
•
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Implicit CFS usage—The first time you issue a CFS task for a CFS-enabled application, the
configuration modification process begins and the application locks the fabric.
Pending database—The pending database is a temporary buffer to hold uncommitted information.
The uncommitted changes are not applied immediately to ensure that the database is synchronized
with the database in the other switches in the fabric. When you commit the changes, the pending
database overwrites the configuration database (also known as the active database or the effective
database).
CFS distribution enabled or disabled on a per-application basis—The default (enable or disable) for
CFS distribution state differs between applications. If CFS distribution is disabled for an
application, then that application does not distribute any configuration nor does it accept a
distribution from other switches in the fabric.
Explicit CFS commit—Most applications require an explicit commit operation to copy the changes
in the temporary buffer to the application database, to distribute the new database to the fabric, and
to release the fabric lock. The changes in the temporary buffer are not applied if you do not perform
the commit operation.
CFS Application Requirements
Cisco MDS 9000 Family CLI Configuration Guide
13-5