> # About iSLB Configuration Distribution Using CFS

> You can distribute the configuration for iSLB initiators and initiator targets on an MDS switch. This feature lets you synchronize the iSLB configuration across the fabric from the console of a single MDS switch. The iSCSI initiator idle timeout, global authentication, and iSCSI dynamic initiator mode parameters are also distributed. CFS distribution is disabled by default.

> 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 (see the System Management Configuration Guide, Cisco DCNM for SAN for more information).

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

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

> After the check completes successfully, all the switches commit the pending configuration to the running configuration. If any check fails, the entire commit fails.

> Note 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.

> Note CFS does not distribute non-iSLB initiator configurations or import Fibre Channel target settings.

> Non-iSLB virtual targets will continue to support advertised interfaces option.

> Tip The pending changes are only available in the volatile directory and are discarded if the switch is restarted.

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.