Enabling Cfs For An Application; Verifying Application Registration Status - Cisco nexus 5000 series Cli Configuration Manual

Chapter 1 Using Cisco Fabric Services
S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
CFS has the following requirements:
•
•
•
•

Enabling CFS for an Application

All CFS-based applications provide an option to enable or disable the distribution capabilities.
Applications have the distribution enabled by default.
The application configuration is not distributed by CFS unless distribution is explicitly enabled for that
application.

Verifying Application Registration Status

The show cfs application command displays the applications that are currently registered with CFS. The
first column displays the application name. The second column indicates whether the application is
enabled or disabled for distribution (enabled or disabled). The last column indicates the scope of
distribution for the application (logical, physical, or both).
Note The show cfs application command only displays applications registered with CFS. Conditional
services that use CFS do not appear in the output unless these services are running.
switch# show cfs application
----------------------------------------------
Application
----------------------------------------------
ntp
fscm
rscn
fctimer
syslogd
callhome
fcdomain
device-alias
Total number of entries = 8
OL-16597-01
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 network.
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 network. 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 network.
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 network,
and to release the network lock. The changes in the temporary buffer are not applied if you do not
perform the commit operation.
Enabled Scope
No Physical-all
Yes Physical-fc
No Logical
No Physical-fc
No Physical-all
No Physical-all
Yes Logical
Yes Physical-fc
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
CFS Support for Applications
1-7