UCS Technology Labs UCS B-Series Service

Profiles

Service Profile Instantiation - ESXiVMFEX

Last updated: April 11, 2013

Task
Spawn a single instance of the Service Profile Template ESXi-VMFEX-iSCSI and be sure that the
service profile is named ESXi-VMFEX-iSCSI-1.
As stated in a previous task, the iSCSI vNIC should boot from a target that is at IP address
10.0.117.25:3260, is at the target name of iqn.2013-01.com.ine:storage:esxi-vmfex:1, and uses
LUN 1.
Provision MDS1 (only) to be a gateway for iSCSI traffic with the above IP address and target IQN,
to connect on the back end to actual FC target at the pWWN of 21:01:00:1b:32:24:37:dc and
LUN 1.
Configure the MDS1 to spoof an FC initiator with the pWWN of 20:aa:00:05:05:00:00:01.
Configure MDS1 to use FC zoning to allow communication strictly between the FC initiator and
disk target in this task.
Boot the blade and ensure that you see the target disk.

Configuration
On the Servers tab in the left navigation pane, filter or navigate to Servers >> Service Profile
Templates >> root org >> Sub-Organizations >> CUST2, right-click Service Template
ESXi-VMFEX-iSCSI, and click Create Service Profiles From Template.

FEEDBACK

For the Naming Prefix, enter ESXi-VMFEX-iSCSI-, and enter 1 instance to be created. Click
OK.

Click OK.

On MDS1:

feature iscsi
iscsi enable module 1
vsan database
vsan 101 interface iscsi1/1
iscsi virtual-target name iqn.2013-01.com.ine:storage:esxi-vmfex:1
pWWN 21:01:00:1b:32:24:37:dc fc-lun 0x0000 iscsi-lun 0x0000
pWWN 21:01:00:1b:32:24:37:dc fc-lun 0x0001 iscsi-lun 0x0001
advertise interface gigabitethernet 1/1
all-initiator-permit
iscsi initiator name iqn.2013-01.com.ine:ucs:esxi-vmfex:9
static nWWN 20:01:00:05:9b:1e:5b:42
static pWWN 20:aa:00:05:05:00:00:01
vsan 101
interface GigabitEthernet1/1
ip address 10.0.117.25 255.255.255.0
no shutdown
interface iscsi1/1
no shutdown

zone mode enhanced vsan 101

zone name ESXi-VMFEX-Boot vsan 101
member pwwn 20:aa:00:05:05:00:00:01
member pwwn 21:01:00:1b:32:24:37:dc
zoneset name VSAN101 vsan 101
member ESXi-12-boot-datastore
member ESXi-VMFEX-Boot
zoneset activate name VSAN101 vsan 101
zone commit vsan 101

Verification
The only way to test this is to temporarily disassociate one of the existing ESXi service profiles
from a blade and associate this ESXi-VMFEX-iSCSI service profile to the blade.

Click ESXi1 in the left navigation pane and click Disassociate Service Profile in the right pane.

Notice that when the ESXi1 service profile completes disassociation (which may take a while),
that the ESXi-VMFEX-iSCSI service profile begins association.

When that process completes, click Boot Server, and then click KVM Console in the right
pane.

Back on MDS1, as the Cisco VIC iSCSI boot driver finally gets to its stage, we begin to see
some action, such as the iSCSI interface FLOGI to the FC Fabric and an iSCSI session setup.

MDS1# sh int br
-----------------------------------------------------------------------------Interface

Status

Oper Mode

Oper Speed
(Gbps)

-----------------------------------------------------------------------------iscsi1/1

up

ISCSI

------------------------------------------------------------------------------Interface

Status

IP Address

Speed

MTU

Port
Chann

el
------------------------------------------------------------------------------GigabitEthernet1/1

up

10.0.117.25/24

1 Gbps

MDS1(config)# sh iscsi initiator configured

iSCSI Node name is iqn.2013-01.com.ine:ucs:esxi-vmfex:9
Member of vsans: 101
Node WWN is 20:01:00:05:9b:1e:5b:42
No. of PWWN: 1
Port WWN is 20:aa:00:05:05:00:00:01
Configured node (iSCSI)
MDS1(config)# sh iscsi virtual-target

1500 --

target: iqn.2013-01.com.ine:storage:esxi-vmfex:1
Port WWN 21:01:00:1b:32:24:37:dc
Configured node (iSCSI)
No. of LU mapping: 2
iSCSI LUN: 0x0000, FC LUN: 0x0000
iSCSI LUN: 0x0001, FC LUN: 0x0001
No. of advertised interface: 1
GigabitEthernet 1/1
All initiator permit is enabled
Trespass support is disabled
Revert to primary support is disabled

MDS1(config)# sh iscsi initiator iscsi-session

iSCSI Node name is iqn.2013-01.com.ine:ucs:esxi-vmfex:9
Initiator ip addr (s): 10.0.117.19
iSCSI alias name: INE-UCS-01
Configured node (iSCSI)
Node WWN is 20:01:00:05:9b:1e:5b:42 (configured)
Member of vsans: 101
Number of Virtual n_ports: 1

MDS1(config)# sh flog d
------------------------------------------------------------------------------INTERFACE

VSAN

FCID

PORT NAME

NODE NAME

------------------------------------------------------------------------------fc1/3

101

0x280200 21:00:00:1b:32:04:37:dc 20:00:00:1b:32:04

:37:dc
[SAN_ARRAY1_FabA_FC0-P0]
fc1/4

101

0x280500 21:01:00:1b:32:24:37:dc 20:01:00:1b:32:24

:37:dc
[SAN_ARRAY1_FabA_FC0-P1]
port-channel 1

101

0x280040 24:02:54:7f:ee:c5:7d:40 20:65:54:7f:ee:c5

101

0x280080 20:aa:00:05:05:00:00:01 20:01:00:05:9b:1

:7d:41
iscsi1/1
e:5b:42
Total number of flogi = 6.
MDS1(config)#

MDS1(config-iscsi-tgt)# sh iscsi session

Initiator iqn.2013-01.com.ine:ucs:esxi-vmfex:9
Initiator ip addr (s): 10.0.117.19
Session #1
Target iqn.2013-01.com.ine:storage:esxi-vmfex

VSAN 101, ISID 00023d010000, Status active, no reservation

MDS1# sh iscsi session detail

Initiator iqn.2013-01.com.ine:ucs:esxi-vmfex:9 (INE-UCS-01)
Initiator ip addr (s): 10.0.117.19
Session #1 (index 15)
Target iqn.2013-01.com.ine:storage:esxi-vmfex:1
VSAN 101, ISID 00023d010000, TSIH 12288, Status active, no reservation
Type Normal, ExpCmdSN 8, MaxCmdSN 135, Barrier 0
MaxBurstSize 262144, MaxConn 1, DataPDUInOrder Yes
DataSeqInOrder Yes, InitialR2T No, ImmediateData Yes
Registered LUN 0, Mapped LUN 2
Stats:
PDU: Command: 8, Response: 8
Bytes: TX: 200, RX: 0
Number of connection: 1
Connection #1 (index 1)
Local IP address: 10.0.117.25, Peer IP address: 10.0.117.19
CID 0, State: Full-Feature
StatSN 11, ExpStatSN 0
MaxRecvDSLength 262144, our_MaxRecvDSLength 262144
CSG 3, NSG 3, min_pdu_size 48 (w/ data 48)
AuthMethod none, HeaderDigest None (len 0), DataDigest None (len 0)
Version Min: 0, Max: 0
FC target: Up, Reorder PDU: No, Marker send: No (int 0)
Received MaxRecvDSLen key: Yes
Stats:
Bytes: TX: 200, RX: 0
MDS1#

And finally, back in our UCSM KVM session, we see the iSCSI disk and LUN.

^ back to top

Disclaimer (http://www.ine.com/feedback.htm) | Privacy Policy (http://www.ine.com/resources/)

Inc., All Rights Reserved (http://www.ine.com/about-us.htm)

2013 INE