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-62
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 20 Troubleshooting IP Storage Services
iSLB Issues
Session Down—”pWWN in Use At Remote Switch”
Symptom
Session down with error
pWWN in use at remote switch
.
Redirected Session Does Not Come Up
Symptom
Redirected session does not come up.
Table 20-10
Session Down—”pWWN in Use At Remote Switch”
Symptom
Possible Cause
Solution
Session down with
error
pWWN in use at
remote switch
.
An initiator pWWN can be used only
once in the fabric.
If the same initiator tries to log in to two iSCSI ports at the
same time, both ports will initially allow the sessions to
come up and then try to reserve the pWWN in the fabric. If
it is detected that this pWWN is already in use, the session
will be destroyed.
To fix the problem, use another WWN or allow the system
to assign one for the initiator using the
static [nWWN |
pWWN] system-assign
CLI
command.
Table 20-11
Redirected Session Does Not Come Up
Symptom
Possible Cause
Solution
Redirected session
does not come up.
Connection may be down, or initiator to
interface mapping may be missing.
Use the
ping
CLI command to verify that the connection
between the redirected port and initiator is up.
Use the
show logging logfile
CLI command to check the
system messages to determine what the session creation
failure reason is if any.
Use the
show interface brief
CLI command to verify that
iSCSI and Gigabit Ethernet interfaces are up.
Bring down and then bring up the initiator and try again to
see if the error is persistent. There are times initiators do
not attempt to make connections to the redirected interface.
Use the
debug ips islb vrrp flow
CLI command to check
if the redirection is performing correctly.
Use the
show islb vrrp summary
CLI command to see if
the initiator to the interface mapping is set up.
