Filter
Top Products
70 Appendix—Manual Configuration of iSCSI
•
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 MD36
x
0i configuration, then LUNs should also be
balanced between the controllers.
The
Status
field on the
Ta rget s
tab should now display as
Connected
.
8
Click
OK
to close the Microsoft iSCSI initiator.
NOTE: PowerVault MD36
x
0i supports only round-robin load-balancing
policies.
If you are using Windows Server 2008 Core Version:
1
Set the iSCSI initiator services to start automatically (if not already set):
sc \\<server_name> config msiscsi start=auto
2
Start the iSCSI service (if necessary):
sc start msiscsi
3
Log on to the target:
iscsicli PersistentLoginTarget <Target_Name>
<Report_To_PNP> <Target_Portal_Address>
<TCP_Port_Number_Of_Target_Portal> * * *
<Login_Flags> * * * * * <Username> <Password>
<Authtype> * <Mapping_Count>
book.book Page 70 Thursday, July 18, 2013 5:56 PM