> # iSLB CFS Merge Status Conflicts

> Merge conflicts may occur. User intervention is required for the following merge conflicts:

> - The iSCSI global authentication or iSCSI initiator idle timeout parameters are not configured the same in the two fabrics.
> - The same iSLB initiator is configured differently in the two fabrics.
> - An iSLB initiator in one fabric has the same name as an iSCSI initiator in the other fabric.
> - Duplicate pWWN/nWWN configuration is detected in the two fabric. For example, a pWWN/nWWN configured for an iSLB initiator on one fabric is configured for an iSCSI initiator or a different iSLB initiator in the other fabric.
> - A VSAN configured for an iSLB initiator in one fabric does not exist in the other fabric.

> Tip Check the syslog for details on merge conflicts.

> User intervention is not required when the same iSLB initiator has a different set of non-conflicting initiator targets. The merged configuration is the union of all the initiator targets.

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