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-61
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 20 Troubleshooting IP Storage Services
iSLB Issues
iSLB Configuration Failed—”Pending iSLB CFS Config Has Reached Its Limit...”
Symptom
iSLB configuration failed with error
Pending iSLB CFS config has reached its limit.
.
iSCSI Disable Failed—”Cannot Disable Iscsi - Large Iscsi Config Present...”
Symptom
iSCSI disable failed with error
Cannot disable iSCSI - large iSCSI config present.
iSLB Commit Timeout
Symptom
iSLB commit timeout.
Table 20-7
iSLB Configuration Failed—”Pending iSLB CFS Config Has Reached Its Limit...”
Symptom
Possible Cause
Solution
iSLB configuration
failed with error
Pending iSLB CFS
config has reached
its limit.
The limit of 200 initiators in the
pending database has been reached, so
no more configuration is allowed
Use the
islb commit
CLI command to commit the
outstanding changes.
Table 20-8
iSCSI Disable Failed—”Cannot Disable Iscsi - Large Iscsi Config Present...”
Symptom
Possible Cause
Solution
iSCSI disable failed
with error
Cannot
disable iSCSI -
large iSCSI config
present
..
There are more than 200 initiators in
the running config, so iSCSI disable is
not allowed.
Delete initiators from the configuration until you have less
than 200 initiators. Then use the
no iscsi enable
CLI
command to disable iSCSI.
Table 20-9
iSLB Commit Timeout
Symptom
Possible Cause
Solution
iSLB commit
timeout.
When a large configuration is present,
it is possible for the iSLB commit to
take a long time.
Check the output of the
show islb cfs-session status
CLI
command to get the status of the commit.
