Islb Cfs Commit Fails; Resolving An Islb Merge Failure - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Chapter 20 Troubleshooting IP Storage Services
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

iSLB CFS Commit Fails

Symptom
Table 20-16 iSLB CFS Commit Fails
Symptom Possible Cause
iSLB CFS commit Zone set activation is not from the
fails. switch with IVR and iSLB enabled.
Another zone set activation is n
progress.
Zoning database is locked because a
configuration is pending.

Resolving an iSLB Merge Failure

To resolve an iSLB merge failure using the CLI, follow these steps:
Determine the cause of merge failure using the output of the show islb merge status and the show ips
Step 1
internal event-history error commands.
If the reason for the merge failure is the VSAN configuration, configure the VSAN on all the switches.
Step 2
Log in to the switch in the fabric whose running configuration you want to keep and issue the islb
Step 3
commit command.
Note
OL-9285-05
iSLB CFS commit fails.
The iSLB configuration on other switches will be overwritten. A commit after a merge failure
synchronizes the fabric configuration to the running- config of the switch where the commit was
performed.
Solution
Activate the zone set from a switch that has IVR and iSLB
enabled.
Use the islb commit CLI command.
Wait until the zone set activation completes and then retry
the iSLB zone set activation.
Commit the existing configuration change or discard the
changes.
Use the show islb status, islb commit, or islb abort CLI
command to view the status, to commit the changes or use
islb abort to discard the changes.
Also, verify that no zone or IVR zone changes are pending.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
iSLB Issues
20-65