Cisco MDS-9124 Troubleshooting Guide - Page 439

Chapter 20 Troubleshooting IP Storage Services iSLB Issues Send documentation comments to [email protected] iSLB CFS Commit Fails Symptom iSLB CFS commit fails. Table 20-16 iSLB CFS Commit Fails Symptom iSLB CFS commit fails. Possible Cause Zone set activation is not from the switch with IVR and iSLB enabled. Another zone set activation is n progress. Zoning database is locked because a configuration is pending. 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. Resolving an iSLB Merge Failure To resolve an iSLB merge failure using the CLI, follow these steps: Step 1 Step 2 Step 3 Determine the cause of merge failure using the output of the show islb merge status and the show ips internal event-history error commands. If the reason for the merge failure is the VSAN configuration, configure the VSAN on all the switches. Log in to the switch in the fabric whose running configuration you want to keep and issue the islb commit command. Note 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. OL-9285-05 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x 20-65