Send documentation comments to mdsfeedback-doc@cisco.com
20-60
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 20 Troubleshooting IP Storage Services
iSLB Issues
iSLB Configuration, Commit, or Merge Failed—”Failed to Allocate WWN”
Symptom iSLB configuration, commit, or merge failed with error Failed to allocate WWN.
iSLB Configuration, Commit, or Merge Failed—”Duplicate WWN Found as...”
Symptom iSLB configuration, commit, or merge failed with error Duplicate WWN found as ..
iSLB Configuration, Commit, or Merge Failed—”Duplicate Node Name”
Symptom iSLB configuration, commit, or merge failed with error Duplicate node name.
Table 20-4 iSLB Configuration, Commit, or Merge Failed—”Failed to Allocate WWN”
Symptom Possible Cause Solution
iSLB configuration,
commit, or merge
failed with error
Failed to allocate
WWN.
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.
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.
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.
Table 20-6 iSLB Configuration, Commit, or Merge Failed—”Duplicate Node Name”
Symptom Possible Cause Solution
iSLB configuration,
commit, or merge
failed with error
Duplicate node
name
.
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.
To Next Page
Loading...
Need help?
General