Cfs Merge Support; Locking The Network; Cfs Regions - Cisco Nexus 7000 Series Configuration Manual

CFS Merge Support

For more information on CFS for the Cisco Nexus 7000 Series, Cisco Nexus 5000 Series, and Cisco MDS
9000 switches, see the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Cisco
Nexus 5000 Series NX-OS System Management Configuration Guide, and Cisco MDS 9000 Family NX-OS
System Management Configuration Guide, respectively.
CFS Merge Support
An application keeps the configuration synchronized in the fabric through CFS. When two such fabrics become
reachable to one another, CFS triggers a merge. These two fabrics could have two different sets of configuration
information that need to be reconciled in the event of a merge. CFS provides notification each time an
application peer comes online. If a fabric with M application peers merges with another fabric with N application
peers and if an application triggers a merge action on every notification, a link-up event results in MxN merges
in the fabric.
CFS supports a protocol that reduces the number of merges required to one by handling the complexity of the
merge at the CFS layer. This protocol runs per application per scope. The protocol involves selecting one
device in a fabric as the merge manager for that fabric. The other devices do not have a role in the merge
process.
During a merger of two networks, their designated managers exchange configuration databases. The application
on one of them merges the databases, decides if the merge is successful, and notifies all other devices.
In the merge is successful, the merged database is distributed to all devices in the combined fabric, and the
entire new fabric remains in a consistent state.

Locking the Network

When you configure an application that uses the CFS infrastructure, that application starts a CFS session and
locks the network. When a network is locked, the device software allows configuration changes to this
application only from the device holding the lock. If you make configuration changes to the application from
another device, the device issues a message to inform the user about the locked status. The configuration
changes are held in a pending database by that application.
If you start a CFS session that requires a network lock but forget to end the session, an administrator can clear
the session. If you lock a network at any time, your username is remembered across restarts and switchovers.
If another user (on the same machine) tries to perform configuration tasks, that user's attempts are rejected.

CFS Regions

A CFS region is a user-defined subset of devices for a given feature or application. You usually define regions
to localize or restrict distribution based on devices that are close to one another. When a network covers many
geographies with many different administrators who are responsible for subsets of devices, you can manage
the scope of an application by setting up a CFS region.
CFS regions are identified by numbers ranging from 0 through 200. Region 0 is reserved as the default region
and contains every device in the network. You can configure regions from 1 through 200.
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
22
Configuring CFS