Adaptec 5325301507 Administration Guide - Page 107

Creating iSCSI Disks, To use CHAP authentication, GuardianOS Support for CHAP Security Target Only

Page 107 highlights

Creating iSCSI Disks iqn.[servername].[iscsidiskname] • The format of IQN names for VSS-based iSCSI disks on the SnapServer is: iqn.1997-10.com.snapserver:[servername]:[diskname].[nnn] where [servername] is the name of the SnapServer, [diskname] is the name of the iSCSI disk on the target SnapServer, and [nnn] is a sequential number starting from 000. For example: iqn.1997-10.com.snapserver:snap123456:iscsi0.000 • The format of IQN names for VDS-based iSCSI disks on the SnapServer is: iqn.1997-10.com.snapserver:[servername]:[diskname]-snap[n] where [servername] is the name of the SnapServer, [diskname] is the name of the iSCSI disk on the target SnapServer, and [n] is a sequential number starting from 0. For example: iqn.1997-10.com.snapserver:snap123456:iscsi0-snap0 Creating iSCSI Disks Navigate to Storage > iSCSI to to create, edit, or delete iSCSI Disks on the SnapServer. Be sure to read "iSCSI Configuration on the SnapServer" on page 88 before you begin creating iSCSI Disks. Note You cannot delete or edit an iSCSI disk until all clients have been disconnected from that disk. Click VSS/VDS Access to add VSS/VDS clients to the SnapServer. See "Configuring VSS/VDS for iSCSI Disks" on page 93 for more information. To use CHAP authentication 1 Click to put a check in the Enable CHAP Logon box. 2 Enter a user name and target secret (password). Both are case sensitive. • The user name range is 1 to 223 alphanumeric characters. • The target secret must be a minimum of 12 and a maximum of 16 characters. GuardianOS Support for CHAP Security (Target Only) CHAP is a network login protocol that uses a challenge-response mechanism to control iSCSI initiator access to an iSCSI target. GuardianOS supports target authentication, in which the initiator must provide the same CHAP user name and password (or "target secret") that was configured on the target SnapServer iSCSI disk. Other forms of CHAP authentication are not currently supported. 91

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

Creating iSCSI Disks
91
iqn.[servername].[iscsidiskname]
The format of IQN names for VSS-based iSCSI disks on the SnapServer is:
iqn.1997-10.com.snapserver:[servername]:[diskname].[nnn]
where
[servername]
is the name of the SnapServer,
[diskname]
is the name of the
iSCSI disk on the target SnapServer, and
[nnn]
is a sequential number starting
from 000. For example:
iqn.1997-10.com.snapserver:snap123456:iscsi0.000
The format of IQN names for VDS-based iSCSI disks on the SnapServer is:
iqn.1997-10.com.snapserver:[servername]:[diskname]-snap[
n]
where
[servername]
is the name of the SnapServer,
[diskname]
is the name of the
iSCSI disk on the target SnapServer, and
[n]
is a sequential number starting from
0. For example:
iqn.1997-10.com.snapserver:snap123456:iscsi0-snap0
Creating iSCSI Disks
Navigate to
Storage > iSCSI
to to create, edit, or delete iSCSI Disks on the
SnapServer. Be sure to read “iSCSI Configuration on the SnapServer” on page 88
before you begin creating iSCSI Disks.
Note
You cannot delete or edit an iSCSI disk until all clients have been
disconnected from that disk.
Click
VSS/VDS Access
to add VSS/VDS clients to the SnapServer. See “Configuring
VSS/VDS for iSCSI Disks” on page 93 for more information.
To use CHAP authentication
1
Click to put a check in the
Enable CHAP Logon
box.
2
Enter a user name and target secret (password). Both are case sensitive.
The user name range is 1 to 223 alphanumeric characters.
The target secret must be a minimum of 12 and a maximum of 16 characters.
GuardianOS Support for CHAP Security (Target Only)
CHAP is a network login protocol that uses a challenge-response mechanism to
control iSCSI initiator access to an iSCSI target. GuardianOS supports target
authentication, in which the initiator must provide the same CHAP user name and
password (or "target secret") that was configured on the target SnapServer iSCSI
disk. Other forms of CHAP authentication are not currently supported.