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
About iSLB Configuration Distribution Using CFS
Configuration for iSLB initiators and initiator targets on an MDS switch can be distributed using the
Cisco Fabric Services (CFS). This feature allows you to synchronize the iSLB configuration across the
fabric from the console of a single MDS switch. The iSCSI initiator idle timeout, iSCSI dynamic initiator
mode, and global authentication parameters are also distributed. CFS distribution is disabled by default
After enabling the distribution, the first configuration starts an implicit session. All server configuration
changes entered thereafter are stored in a temporary database and applied to all switches in the fabric
(including the originating one) when you explicitly commit the database.
When CFS is enabled for iSLB, the first iSLB configuration operation starts a CFS session and locks the
iSLB configuration in the fabric. The configuration changes are applied to the pending configuration
database. When you make the changes to the fabric, the pending configuration is distributed to all the
switches in the fabric. Each switch then validates the configuration. This check ensures the following:
After the check completes successfully, all the switches commit the pending configuration to the running
configuration. If any check fails, the entire commit fails.
iSLB is only fully supported when CFS is enabled. Using iSLB auto-zoning without enabling CFS mode
may cause traffic disruption when any zone set is activated.
CFS does not distribute non-iSLB initiator configurations or import Fibre Channel target settings.
The pending changes are only available in the volatile directory and are discarded if the switch is
Distributing the iSLB Configuration Using CFS
This section contains the following:
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Chapter 5, "Using the CFS
The VSANs assigned to the iSLB initiators are configured on all the switches.
The static WWNs configured for the iSLB initiators are unique and available on all the switches.
The iSLB initiator node names do not conflict with the iSCSI initiators on all the switches.
Enabling iSLB Configuration Distribution, page 42-56
Locking the Fabric, page 42-56
Committing Changes to the Fabric, page 42-56
Discarding Pending Changes, page 42-56
Clearing a Fabric Lock, page 42-57
CFS Merge Process, page 42-57
Cisco MDS 9000 Family CLI Configuration Guide