Target Storage Device Requiring Lun Mapping - HP Cisco MDS 9020 - Fabric Switch Configuration Manual

Chapter 42 Configuring iSCSI
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
Verify the detailed output of the iSCSI initiator nodes in the Fibre Channel name server.
Step 18
switch# show fcns database fcid 0x6d0300 detail vsan 1
------------------------
VSAN:1
------------------------
port-wwn (vendor)
node-wwn
class
node-ip-addr
ipa
fc4-types:fc4_features:scsi-fcp:init iscsi-gw
symbolic-port-name
symbolic-node-name
:iqn.1987-05.com.cisco:01.25589167f74c
port-type
port-ip-addr
fabric-port-wwn
hard-addr
Total number of entries = 1
switch# show fcns database fcid 0x6d0301 detail vsan 1
------------------------
VSAN:1
------------------------
port-wwn (vendor)
node-wwn
class
node-ip-addr
ipa
fc4-types:fc4_features:scsi-fcp:init iscsi-gw
symbolic-port-name
symbolic-node-name
port-type
port-ip-addr
fabric-port-wwn
hard-addr

Target Storage Device Requiring LUN Mapping

Sample scenario 2 assumes the following configuration (see
•
•
•
•
OL-16184-01, Cisco MDS SAN-OS Release 3.x
FCID:0x6d0300
:20:03:00:0b:fd:44:68:c2 (Cisco)
:20:02:00:0b:fd:44:68:c2
:2,3
:10.15.1.11
:ff ff ff ff ff ff ff ff
:
:N
:0.0.0.0
:21:91:00:0b:fd:44:68:c0
:0x000000
FCID:0x6d0301
:20:05:00:0b:fd:44:68:c2 (Cisco)
:20:04:00:0b:fd:44:68:c2
:2,3
:10.11.1.10
:ff ff ff ff ff ff ff ff
:
:10.11.1.10
:N
:0.0.0.0
:21:81:00:0b:fd:44:68:c0
:0x000000
Access control is based on Fibre Channel zoning.
There is target-based LUN mapping or LUN masking.
There is no iSCSI authentication (none).
The iSCSI initiator is assigned to different VSANs.
iSCSI Authentication Setup Guidelines and Scenarios
<----------------------
<------
<--------------------
<------
<---------------------
Figure
Cisco MDS 9000 Family CLI Configuration Guide
IPv4 address of the
iSCSI host
iSCSI gateway node
iSCSI initiator ID is
based on the registered
node name
iSCSI gateway node
iSCSI initiator ID is
based on the IPv4
address registered in
symbolic-node-name
field
42-22):
42-73