Disabling Cfs Distribution On A Switch; Cfs Application Requirements; Enabling Cfs For An Application - Cisco DS-X9530-SF1-K9 - Supervisor-1 Module - Control Processor Configuration Manual

Chapter 5 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 .

Disabling CFS Distribution on a Switch

By default, CFS distribution is enabled. Applications can distribute data and configuration information
to all CFS-capable switches in the fabric where the applications exist. This is the normal mode of
operation.
As of Cisco MDS SAN-OS 2.1(1a), you can globally disable CFS on a switch to isolate the applications
using CFS from fabric-wide distributions while maintaining physical connectivity. When CFS is
globally disabled on a switch, CFS operations are restricted to the switch and all CFS commands
continue to function as if the switch were physically isolated.
To globally disable CFS distribution on a switch, follow these steps:
Command
Step 1
switch# config t
switch(config)#
Step 2
switch(config)# no cfs distribution
switch(config)# cfs distribution

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:
•
•
•
•

Enabling CFS for an Application

All CFS based applications provide an option to enable or disable the distribution capabilities. Features
that existed prior to Cisco SAN-OS Release 2.0(1b) have the distribution capability disabled by default
and must have distribution capabilities enabled explicitly.
OL-6973-03, Cisco MDS SAN-OS Release 2.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 know as 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 and distributes the new database to the fabric and
releases the fabric lock. The changes in the temporary buffer are not applied if you do not perform
the commit operation.
Disabling CFS Distribution on a Switch
Purpose
Enters configuration mode.
Globally disables CFS distribution for all
applications on the switch.
Enables (default) CFS distribution on the switch.
Cisco MDS 9000 Family Configuration Guide
5-5