Send documentation comments to mdsfeedback-doc@cisco.com
50-49
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
Chapter 50 Configuring iSCSI
Configuring iSLB
Clearing a Fabric Lock
If you have performed an iSLB configuration task and have not released the lock by either committing
or discarding the changes, an administrator can release the lock from any switch in the fabric. If the
administrator performs this task, your pending changes are discarded and the fabric lock is released.
Tip The pending changes are only available in the volatile directory and are discarded if the switch is
restarted.
To release a fabric lock using Device Manager, follow these steps:
Step 1 Choose Admin > CFS.
You see the CFS Configuration dialog box (see Figure 50-35).
Step 2 Set the Command field to clear for the iSLB feature.
Step 3 Click Apply to save this change.
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:
• 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.
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:
• 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.
To Next Page
Loading...
Need help?
General
