Dell PowerVault MD3200i Deployment Guide - Page 69

Data Digest and Header Digest, Microsoft iSCSI Initiator

Page 69 highlights

3 Click Log On. 4 Select Automatically restore this connection when the system boots. 5 Select Enable multi-path. 6 Click Advanced and configure the following settings under the General tab: • Local Adapter-Must be set to Microsoft iSCSI Initiator. • Source IP-The source IP address of the host server you want to connect from. • Target Portal-Select the iSCSI port on the storage array controller that you want to connect to. • Data Digest and Header Digest-Optionally, you can specify that a digest of data or header information be compiled during transmission to assist in troubleshooting. • CHAP logon information-If CHAP authentication is required, select this option and enter the Target secret. • Perform mutual authentication-If mutual CHAP authentication is configured, select this option. NOTE: IPSec is not supported. 7 Click OK. To support storage array controller failover, the host server must be connected to at least one iSCSI port on each controller. Repeat step 3 through step 8 for each iSCSI port on the storage array that you want to establish as failover targets. The Target Portal address is different for each port you connected to. NOTE: To enable the higher throughput of multipathing I/O, the host server must connect to both iSCSI ports on each controller, ideally from separate host-side NICs. Repeat step 3 through step 7 for each iSCSI port on each controller. If using a duplex MD32xxi configuration, then LUNs should also be balanced between the controllers. The Status field on the Targets tab should now display as Connected. 8 Click OK to close the Microsoft iSCSI initiator. NOTE: PowerVault MD32xxi supports only round robin load-balancing policies. Appendix-Manual Configuration 69

  • 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
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82

Appendix—Manual Configuration
69
3
Click
Log On
.
4
Select
Automatically restore this connection when the system boots
.
5
Select
Enable multi-path
.
6
Click
Advanced
and configure the following settings under the
General
tab:
Local Adapter
—Must be set to
Microsoft iSCSI Initiator
.
Source IP
—The source IP address of the host server you want to
connect from.
Target Portal
—Select the iSCSI port on the storage array controller
that you want to connect to.
Data Digest and Header Digest
—Optionally, you can specify that a
digest of data or header information be compiled during transmission
to assist in troubleshooting.
CHAP logon information
—If CHAP authentication is required,
select this option and enter the Target secret.
Perform mutual authentication
—If mutual CHAP authentication is
configured, select this option.
NOTE:
IPSec is not supported.
7
Click
OK
.
To support storage array controller failover, the host server must be
connected to at least one iSCSI port on each controller. Repeat step 3
through step 8 for each iSCSI port on the storage array that you want to
establish as failover targets. The
Target Portal
address is different for each
port you connected to.
NOTE:
To enable the higher throughput of multipathing I/O, the host server
must connect to both iSCSI ports on each controller, ideally from separate
host-side NICs. Repeat step 3 through step 7 for each iSCSI port on each
controller. If using a duplex MD32
xx
i configuration, then LUNs should also be
balanced between the controllers.
The
Status
field on the
Targets
tab should now display as
Connected
.
8
Click
OK
to close the Microsoft iSCSI initiator.
NOTE:
PowerVault MD32
xx
i supports only round robin load-balancing
policies.