Cisco MDS-9124 Troubleshooting Guide - Page 434
iSLB Configuration, Commit, or Merge Failed-”Failed to Allocate WWN”, iSLB Configuration, Commit, or
View all Cisco MDS-9124 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 434 highlights
iSLB Issues Chapter 20 Troubleshooting IP Storage Services Send documentation comments to [email protected] iSLB Configuration, Commit, or Merge Failed-"Failed to Allocate WWN" Symptom iSLB configuration, commit, or merge failed with error Failed to allocate WWN. Table 20-4 iSLB Configuration, Commit, or Merge Failed-"Failed to Allocate WWN" Symptom iSLB configuration, commit, or merge failed with error Failed to allocate WWN. Possible Cause The pWWN or nWWN for one for the initiators could not be reserved from the WWN manager. This implies that the particular WWN is already in use. Solution Check the output of the show islb cfs-session status, show islb merge status and show ips internal event-history error CLI commands for details on the specific WWN and initiator in error. To fix the problem, use another WWN or allow the system to assign one for the initiator using the static [nWWN | pWWN] system-assign command. iSLB Configuration, Commit, or Merge Failed-"Duplicate WWN Found as..." Symptom iSLB configuration, commit, or merge failed with error Duplicate WWN found as .. Table 20-5 iSLB Configuration, Commit, or Merge Failed-"Duplicate WWN Found as ..." Symptom Possible Cause Solution iSLB configuration, commit, or merge failed with error Duplicate WWN found as .. The pWWN or nWWN for one for the initiators is already in use by another initiator. Check the output of the show islb cfs-session status, show islb merge status and show ips internal event-history error CLI commands for details on the specific WWN and initiator in error. To fix the problem, use another WWN or allow the system to assign one for the initiator using the static [nWWN | pWWN] system-assign command. iSLB Configuration, Commit, or Merge Failed-"Duplicate Node Name" Symptom iSLB configuration, commit, or merge failed with error Duplicate node name. Table 20-6 iSLB Configuration, Commit, or Merge Failed-"Duplicate Node Name" Symptom iSLB configuration, commit, or merge failed with error Duplicate node name. Possible Cause Solution Node name of one of the iSLB initiators is the same as an existing iSCSI initiator. Check the output of the show islb cfs-session status, show islb merge status and show ips internal event-history error CLI commands for details on the specific initiator in error. To fix the problem, use a different node name. 20-60 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05