Virtual Target Access Control; Useful Show Commands To Debug Static Iscsi Configuration - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Chapter 20 Troubleshooting IP Storage Services
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
show iscsi local-node Command Output
switch# show iscsi local-node
target: iqn.com.domainname.IPS-TEST.02-07.gw.202300a0b80b14da
show fcns data vsan 1 Command Output
switch# show fcns data vsan 1
VSAN 1:
-----------------------------------------------------------------------
FCID
-----------------------------------------------------------------------
0x750000
0x750102
0x750105
0x750201
0x750301
0x750400
show flogi database vsan 1 Command Output
switch# show flogi database vsan 1
-----------------------------------------------------------
INTERFACE
-----------------------------------------------------------
fc1/1
fc1/6
fc1/8
fc1/9
fc1/10
iscsi2/7

Virtual Target Access Control

Use the following guidelines when creating a virtual target:
•
•
•
•

Useful Show Commands to Debug Static iSCSI Configuration

The show commands in this section are used to debug static iSCSI configuration. The following
command output indicates correctly established iSCSI sessions. Run these commands on your switch
and compare the output with these samples to help identify possible issues.
OL-9285-05
VSAN ID 1, FCID 0x750105
Port WWN 20:23:00:a0:b8:0b:14:da , VSAN 1
Auto-created node
TYPE PWWN
N 20:23:00:a0:b8:0b:14:da (SymBios)
N 10:00:00:00:c9:30:ba:06 (Emulex)
N 20:0d:00:0b:be:77:72:42
N 50:08:05:f3:00:04:96:71
N 50:08:05:f3:00:04:96:79
N 20:00:00:02:3d:07:05:c0 (NuSpeed)
VSAN FCID
1 0x750400
1 0x750000
1 0x750102
1 0x750201
1 0x750301
1 0x750105
Did you specify the correct pWWN?
If you are creating a virtual target from a subset of LUN(s) of a physical device, did you specify the
correct Fibre Channel (physical) LUN(s) and iSCSI (virtual) LUN(s)?
If using an access list to control access to the virtual target, did you specify the correct initiator(s)?
If you are not using an access list to restrict access, did you choose End Devices > iSCSI, select the
Targets tab and check the Initiator Access All check box in Fabric Manager or use the
all-initiator-permit CLI option to insure all initiators have access?
If restricting access to a particular interface(s), did you specify the correct Gigabit Ethernet
interface(s)?
(VENDOR)
PORT NAME
20:00:00:02:3d:07:05:c0
20:23:00:a0:b8:0b:14:da
10:00:00:00:c9:30:ba:06
50:08:05:f3:00:04:96:71
50:08:05:f3:00:04:96:79
20:0d:00:0b:be:77:72:42
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
FC4-TYPE:FEATURE
scsi-fcp:target
scsi-fcp:init
scsi-fcp:init isc..w
scsi-fcp
scsi-fcp
scsi-fcp:init
NODE NAME
10:00:00:02:3d:07:05:c0
20:22:00:a0:b8:0b:14:d9
20:00:00:00:c9:30:ba:06
50:08:05:f3:00:04:96:70
50:08:05:f3:00:04:96:70
20:0c:00:0b:be:77:72:42
iSCSI Issues
20-43