Background info:
Windows initiator - iqn.hella.net.win7
FC Disk pwwn - 22:00:00:14:c3:1b:9c:da
Zoning is pre-configured:
zone name ISCSI vsan 10
member pwwn 22:00:00:14:c3:1b:9c:da
member pwwn 22:05:00:0d:ec:1f:bc:02
zoneset name VSAN10 vsan 10
member ISCSI
Static Target example
This is pretty simple and straight forward. I've done this enough times that I don't need to refer to any documents
islb virtual-target name iqn.hella.disk1.com
pWWN 22:00:00:14:c3:1b:9c:da
initiator iqn.hella.net.win7.com permit
islb initiator name iqn.hella.net.win7.com
static pWWN 22:05:00:0d:ec:1f:bc:02
vsan 10
MDS-2# sh islb initiator
iSCSI Node name is iqn.hella.net.win7.com
Initiator ip addr (s): 10.10.209.250
iSCSI alias name:
Configured node (iSLB)
Node WWN is 23:01:00:0d:ec:0e:96:c2 (dynamic)
Member of vsans: 10
Number of Initiator Targets: 0
Number of Virtual n_ports: 1
Virtual Port WWN is 22:05:00:0d:ec:1f:bc:02 (configured)
Interface iSCSI 2/1, Portal group tag: 0x3080
VSAN ID 10, FCID 0x700100
Dynamic Target example
For this example, we will import the FC targets and use the automatic zoning feature. Note that a zoneset must exist for the MDS to add the 'auto-zone' to. There must be a zone member with a least one target in the zoneset. Here is an example of how the zoning looks:
zone name ISCSI vsan 10
member device-alias J2D1-10
zoneset name ISCSI-ZS vsan 10
member ISCSI
zoneset activate name ISCSI-ZS vsan 10
MDS-1(config)# do sh zone active
zone name ISCSI vsan 10
device-alias J2D1-10
zone name ips_zone_dynamic vsan 10
symbolic-nodename iqn.hella.net:windows7
* fcid 0x0b00e0 [pwwn 22:00:00:14:c3:1b:a2:ba] [J1D1-10]
On to the configuration:
iscsi import target fc
islb initiator name iqn.hella.net.win7.com
static pWWN 22:05:00:0d:ec:1f:bc:02
vsan 10
zonename helladynamic
target pwwn 22:00:00:14:c3:1b:9c:da vsan 10
! [J1D4]
After the commit, the automatic zone has been created:
MDS-1# sh zone active
zone name ips_zone_helladynamic vsan 10
* fcid 0x700100 [symbolic-nodename iqn.hella.net.win7.com]
* fcid 0x0b00e4 [pwwn 22:00:00:14:c3:1b:9c:da] [J1D4]
You end up with a really long initiator IQN related to VRRP and the pWWN :
MDS-2# sh islb session
Initiator iqn.hella.net.win7.com
Initiator ip addr (s): 10.10.209.250
Session #1
Target iqn.1987-05.com.cisco:05.558c3d5bf791e6d342b5c6e215cab181.22000014c31b9cda
VSAN 10, ISID 400001370000, Status active, no reservation
Authentication
MDS
aaa authentication iscsi default local
! note that the Windows 7 initiator that I'm using uses it's initiator IQN as the CHAP username
username iqn.hella.net:windows7 password Cisco123Cisco123 iscsi
iscsi authentication chap
Windows
The trick I used was using the 'properties' tab using the discovered target. The under 'connect to target' enter the CHAP secret:
A terminal monitor should show something like this
2014 Jan 19 17:49:50 MDS-2 %IPS-SLOT2-5-ISCSI_CONN_UP: %$VSAN 10%$ GigabitEthernet2/1: iSCSI session up from initiator iqn.hella.net:windows7 alias ip 10.10.209.250 to target iqn.1987-05.com.cisco:05.309693e8105133a716831dbdbb9a33a2.22000014c31b9cda
