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
20-59
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 20 Troubleshooting IP Storage Services
iSLB Issues
iSCSI Initiator and Virtual Target Configuration Not Distributed
Symptom
iSCSI initiator and virtual target configuration is not distributed to the fabric.
iSLB Configuration, Commit, or Merge Failed—”VSAN ID is Not Yet
Configured”
Symptom
iSLB configuration, commit, or merge failed with error
VSAN ID is not yet configured
.
Table 20-2
iSCSI Initiator and Virtual Target Configuration Not Distributed
Symptom
Possible Cause
Solution
iSCSI initiator and
virtual target
configuration is not
distributed to the
fabric.
Normal operation.
Only the following iSCSI and iSLB configuration is
distributed:
•
iSLB initiator and iSLB initiator targets
•
iSLB VRRP load-balancing configuration
•
iSCSI global authentication parameters
(authentication algorithm and CHAP user name or
password)
•
iSCSI dynamic initiator mode (iSCSI, iSLB, or deny)
Table 20-3
iSLB Configuration, Commit, or Merge Failed—”VSAN ID is Not Yet Configured.”
Symptom
Possible Cause
Solution
iSLB configuration,
commit, or merge
failed with error
VSAN
ID is not yet
configured.
The VSAN ID for one of the initiators
is not configured on all switches in the
fabric.
Check the output of the
show islb cfs-session status,
s
how
islb merge status
, and
show ips internal event-history
error
CLI command
for details on which initiator VSAN
ID is not configured on a switch.
Use the
vsan database vsan
vsan-id
CLI command to add
the VSAN ID, or remove the VSAN ID from the initiator
configuration.
