Cfs Merge Process; Islb Cfs Merge Status Conflicts - HP Cisco MDS 9216 - Fabric Switch Configuration Manual

Chapter 50 Configuring iSCSI
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
Tip The pending changes are only available in the volatile directory and are discarded if the switch is
restarted.
To release a fabric lock c using Device Manager, follow these steps:
Choose Admin > CFS.
Step 1
You see the CFS Configuration dialog box (see
Set the Command field to clear for the iSLB feature.
Step 2
Click Apply to save this change.
Step 3

CFS Merge Process

When two fabrics merge, CFS attempts to merge the iSLB configuration from both the fabrics. A
designated switch (called the dominant switch) in one fabric sends its iSLB configuration to a designated
switch (called the subordinate switch) in the other fabric. The subordinate switch compares its running
configuration to the received configuration for any conflicts. If no conflicts are detected, it merges the
two configurations and sends it to all the switches in both the fabrics. Each switch then validates the
configuration. This check ensures the following:
•
•
•
If this check completes successfully, the subordinate switch directs all the switches to commit the
merged configuration to running configuration. If any check fails, the merge fails.

iSLB CFS Merge Status Conflicts

Merge conflicts may occur. User intervention is required for the following merge conflicts:
•
•
•
•
•
Check the syslog for details on merge conflicts.
Tip
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.
OL-16184-01, Cisco MDS SAN-OS Release 3.x
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 have no conflicts with iSCSI initiators on all the switches.
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.
Figure 50-35).
Cisco MDS 9000 Family CLI Configuration Guide
Configuring iSLB
50-49