Table of Contents
Advertisement
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 .
Saving the Configuration
Configuration changes that have not been applied yet (still in the pending database) are not shown in the
running configuration. The configuration changes in the pending database overwrites the configuration
in the effective database when you commit the changes.
If you do not commit the changes, they are not saved to the running configuration.
Caution
The CISCO-CFS-MIB contains SNMP configuration information for any CFS-related functions. Refer
to the Cisco MDS 9000 Family MIB Quick Reference for more information on this MIB.
Clearing a Locked Session
You can clear locks held by an application from any switch in the fabric. This option is provided to rescue
you from situations where locks are acquired and not released. This function requires ADMIN
permissions.
Exercise caution when using this function to clear locks in the fabric. Any pending configurations in any
Caution
switch in the fabric is flushed and lost.
CFS Merge Support
An application keeps the configuration synchronized in a fabric through CFS. Two such fabrics might
merge as a result of an ISL coming up between them. 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 two fabrics with M and N application peers merge and if
a application triggers a merge action on every such notification, a link up event results in M*N 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 switch in a fabric as the merge manager for that fabric. The other switches do not play any
role in the merge process.
During a merge, the merge manager in the two fabrics exchange their configuration databases with each
other. The application on one of them merges the information, decides if the merge is successful and
informs all switches in the combined fabric of the status of the merge.
In case of a successful merge, the merged database is distributed to all switches in the combined fabric
and the entire new fabric remains in a consistent state. You can recover from a merge failure by starting
a distribution from any of the switches in the new fabric. This distribution restores all peers in the fabric
to the same configuration database.
OL-6973-03, Cisco MDS SAN-OS Release 2.x
Saving the Configuration
Cisco MDS 9000 Family Configuration Guide
5-7
Advertisement
Table of Contents
