HP StorageWorks MSA1510i HP StorageWorks 1510i Modular Smart Array installatio - Page 70

Configuring the VMware iSCSI software initiator, Naming requirements, Discovery methods

Page 70 highlights

Configuring the VMware iSCSI software initiator NOTE: Only iSCSI software initiators are supported by MSA1510i. This section describes how to configure the VMware iSCSI initiator to connect to a dual-controller MSA1510i in a multipathing environment. (For single-controller configurations, omit all steps shown for multipath or dual-controller configurations.) The initiator is native to ESX. While configuring the iSCSI software initiator, you enable your initiator and set up the initiator's target addresses and CHAP parameters. See the following sections for more information. After configuring the iSCSI software initiator, perform a rescan, so that all LUNs to which the initiator has access display on the list of storage devices available to your ESX Server. For more information, see"Performing a Rescan" on page 74. Naming requirements Because storage area networks can become large and complex, all iSCSI initiators and targets that use the network have unique and permanent iSCSI names and are assigned addresses for access. The iSCSI name provides a correct identification of a particular iSCSI device, an initiator or a target, regardless of its physical location. When configuring your iSCSI initiators, make sure they have properly formatted names. The initiators can use one of the following formats: • IQN (iSCSI qualified name)-Can be up to 255 characters long and has the following format: iqn..: where represents the year and month your domain name was registered, is the official domain name, reversed, and is any name you want to use, for example, the name of your server. Example: iqn.1998-01.com.mycompany:myserver. • EUI (extended unique identifier) -Represents the eui. prefix followed by the 16-character name. The name includes 24 bits for company name assigned by the IEEE and 40 bits for a unique ID such as a serial number. Discovery methods To determine which storage resource on the network is available for access, the iSCSI initiators ESX Server system uses these discovery methods: • Dynamic Discovery -The initiator discovers iSCSI targets by sending a SendTargets request to a specified target address. To use this method, enter the address of the target device so that the initiator can establish a discovery session with this target. The target device responds by forwarding a list of additional targets that the initiator is allowed to access. • Static Discovery- After the target device used in the SendTargets session sends you the list of available targets, they appear on the Static Discovery list. To this list, you can manually add any additional targets, or remove targets you don't need. The static discovery method is available only with the hardware-initiated storage. iSCSI security Because iSCSI technology uses the IP networks to connect to remote targets, it is necessary to ensure security of the connection. The IP protocol itself doesn't protect the data it transports, and it doesn't have the capability to verify the legitimacy of initiators that access targets on the network. You need to take specific measures to guarantee security across IP networks. 70 Configuration

  • 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
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

Con
guring the VMware iSCSI software initiator
NOTE:
Only iSCSI software initiators are supported by MSA1510i.
This section describes how to con
gure the VMware iSCSI initiator to connect to a dual-controller
MSA1510i in a multipathing environment. (For single-controller con
gurations, omit all steps shown for
multipath or dual-controller con
gurations.) The initiator is native to ESX.
While con
guring the iSCSI software initiator, you enable your initiator and set up the initiator’s target
addresses and CHAP parameters. See the following sections for more information.
After con
guring the iSCSI software initiator, perform a rescan, so that all LUNs to which the initiator
has access display on the list of storage devices available to your ESX Server. For more information,
see“
Performing a Rescan
” on page 74.
Naming requirements
Because storage area networks can become large and complex, all iSCSI initiators and targets that use
the network have unique and permanent iSCSI names and are assigned addresses for access. The iSCSI
name provides a correct identi
cation of a particular iSCSI device, an initiator or a target, regardless
of its physical location.
When con
guring your iSCSI initiators, make sure they have properly formatted names. The initiators
can use one of the following formats:
IQN (iSCSI quali
ed name)
—Can be up to 255 characters long and has the following format:
iqn.<year-mo>.<reversed_domain_name>:<unique_name>
where <
year-mo
> represents the year and month your domain name was registered,
<
reversed_domain_name
> is the of
cial domain name, reversed, and <
unique name
> is
any name you want to use, for example, the name of your server.
Example:
iqn.1998-01.com.mycompany:myserver
.
EUI (extended unique identi
er)
—Represents the eui. pre
x followed by the 16-character name.
The name includes 24 bits for company name assigned by the IEEE and 40 bits for a unique
ID such as a serial number.
Discovery methods
To determine which storage resource on the network is available for access, the iSCSI initiators ESX Server
system uses these discovery methods:
Dynamic Discovery
—The initiator discovers iSCSI targets by sending a SendTargets request to
a speci
ed target address. To use this method, enter the address of the target device so that
the initiator can establish a discovery session with this target. The target device responds by
forwarding a list of additional targets that the initiator is allowed to access.
Static Discovery
— After the target device used in the SendTargets session sends you the list of
available targets, they appear on the Static Discovery list. To this list, you can manually add any
additional targets, or remove targets you don’t need.
The static discovery method is available only with the hardware-initiated storage.
iSCSI security
Because iSCSI technology uses the IP networks to connect to remote targets, it is necessary to ensure
security of the connection. The IP protocol itself doesn’t protect the data it transports, and it doesn’t have
the capability to verify the legitimacy of initiators that access targets on the network. You need to take
speci
c measures to guarantee security across IP networks.
70
Con
guration