HP Cisco MDS 9020 HP StorageWorks C-Series iSCSI Configuration Guide (AA-RW7PE - Page 21

Creating an iSCSI host, Configuring iSCSI storage on the EVA controller

Page 21 highlights

You can use either Fabric Manager or the switch CLI to create and modify SAN zones. As a best practice of SAN management, HP recommends that you create separate iSCSI zones that contain the iSCSI WWPNs and the storage WWPNs it will access. Refer to the Cisco configuration documentation to create, modify, or activate SAN zones. NOTE: HP does not support multi-pathing software installed on non-Windows iSCSI initiators connected to the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), or MDS 9216i switch. iSCSI initiators can be zoned with only a single WWPN from the HP storage controller. Figure 9 shows an example of an iSCSI initiator, W2KX03 (33.33.33.143), zoned with a single port from an EVA named HSV04, in a zone named iSCSI-HSV04-ONE-PORT. When the new zone is activated, the iSCSI Initiator can log in to the storage controller. Figure 9 C-Series Zone containing iSCSI Initiator with single HSV port Creating an iSCSI host Configuring iSCSI storage on the EVA controller During initial setup, the iSCSI Initiator must log in to the storage controller before the EVA can recognize the iSCSI initiator's WWPN. You can set the controller port as a Persistent Target which will permit the iSCSI Initiator to reconnect to the storage controller after a power cycle or reboot. CAUTION: Failure to enable Persistent Target during controller login prohibits the iSCSI Initiator from accessing storage automatically after a power cycle or reboot, requiring another login to the storage controller. Initial iSCSI Initiator EVA login 1. From the the Microsoft iSCSI Initiator Properties window's Available Targets tab, click Refresh. C-Series iSCSI 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49

You can use either Fabric Manager or the switch CLI to create and modify SAN zones. As a best practice
of SAN management, HP recommends that you create separate iSCSI zones that contain the iSCSI
WWPNs and the storage WWPNs it will access. Refer to the Cisco con
guration documentation to
create, modify, or activate SAN zones.
NOTE:
HP does not support multi-pathing software installed on non-Windows iSCSI initiators connected to the
C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), or MDS
9216i switch. iSCSI initiators can be zoned with only a single WWPN from the HP storage controller.
Figure 9
shows an example of an iSCSI initiator,
W2KX03 (33.33.33.143)
, zoned with a single port
from an EVA named
HSV04
, in a zone named
iSCSI-HSV04-ONE-PORT
.
When the new zone is activated, the iSCSI Initiator can log in to the storage controller.
Figure 9 C-Series Zone containing iSCSI Initiator with single HSV port
Creating an iSCSI host
Con
guring iSCSI storage on the EVA controller
During initial setup, the iSCSI Initiator must log in to the storage controller before the EVA can recognize
the iSCSI initiator’s WWPN. You can set the controller port as a Persistent Target which will permit the
iSCSI Initiator to reconnect to the storage controller after a power cycle or reboot.
CAUTION:
Failure to enable Persistent Target during controller login prohibits the iSCSI Initiator from accessing
storage automatically after a power cycle or reboot, requiring another login to the storage controller.
Initial iSCSI Initiator EVA login
1.
From the the Microsoft iSCSI Initiator Properties window's Available Targets tab, click
Refresh
.
C-Series iSCSI
21