Dell EqualLogic PS6210XS EqualLogic Group Manager Administrator s Guide PS Ser - Page 95

Protect Network Traffic with IPsec, Traffic

Page 95 highlights

Algorithm Type IKE (Diffie-Hellman) Key Exchange IPsec Integrity IPsec Encryption Supported Algorithms • AES-CBC-256 • 2 (if legacy support is not disabled) • 14 • 24 • HMAC-SHA1-96 • HMAC-SHA2-224 • HMAC-SHA2-256 • HMAC-SHA2-384 • HMAC-SHA2-512 • NULL • 3DES-CBC • AES-CBC • AES-CBC-192 • AES-CBC-256 NOTE: IKE (Diffie-Hellman) Key Exchange Group 2 algorithm is supported only if legacy support is not disabled. Requirements for Pre-Shared Keys Pre-shared keys that are used with the group must meet the following requirements: • A text string of 6 to 64 printable ASCII characters, meeting these specifications: - Letters and numbers are allowed, but letters with accent marks, such as or ü, are not. - Spaces are not allowed. - ASCII keys cannot begin with "0x" or "0X"; that prefix is reserved for hexadecimal keys. - You can use the following nonalphanumeric characters: ! " # $ percent An even number of hexadecimal digits, meeting these specifications: - The string must be 12 to 128 ASCII characters long. - The string must be preceded by either 0x or 0X. The prefix does not count toward the number of characters and is not part of the pre-shared key. The system will interpret any pre-shared key that does not begin with 0x or 0X as a text string, even if it contains only hexadecimal characters. Protect Network Traffic with IPsec To enable IPsec protection for traffic between the group and iSCSI initiators, use the following basic process: NOTE: This process is not required for protecting communications between group members. After IPsec is enabled, all network traffic between group members is automatically protected, without need for further configuration. 1. A group administrator creates security parameters to specify how traffic should be authenticated. 2. A group administrator creates policies to identify traffic and determine what action to take for it: • Traffic is dropped. • Traffic is allowed to pass directly through to the array in the clear. • Traffic is protected using certificates or pre-shared keys. NOTE: IPsec configurations cannot be modified. They must be removed and then recreated using the new configuration. About Group-Level Security 95

  • 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
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355

Algorithm Type
Supported Algorithms
AES-CBC–256
IKE
(Diffie-Hellman)
Key Exchange
2 (if legacy support is not disabled)
14
24
IPsec Integrity
HMAC-SHA1–96
HMAC-SHA2–224
HMAC-SHA2-256
HMAC-SHA2-384
HMAC-SHA2-512
IPsec Encryption
NULL
3DES-CBC
AES-CBC
AES-CBC–192
AES-CBC–256
NOTE: IKE
(Diffie-Hellman)
Key Exchange Group 2 algorithm is supported only if legacy support is not disabled.
Requirements for Pre-Shared Keys
Pre-shared keys that are used with the group must meet the following requirements:
A text string of 6 to 64 printable ASCII characters, meeting these
specifications:
Letters and numbers are allowed, but letters with accent marks, such as é, ç, ñ, or ü, are not.
Spaces are not allowed.
ASCII keys cannot begin with “0x” or “0X”; that
prefix
is reserved for hexadecimal keys.
You can use the following nonalphanumeric characters: ! " # $ percent & ` ( ) * + , - / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ .
An even number of hexadecimal digits, meeting these
specifications:
The string must be 12 to 128 ASCII characters long.
The string must be preceded by either
0x
or
0X
. The
prefix
does not count toward the number of characters and is not part
of the pre-shared key. The system will interpret any pre-shared key that does not begin with
0x
or
0X
as a text string, even if
it contains only hexadecimal characters.
Protect Network
Traffic
with IPsec
To enable IPsec protection for
traffic
between the group and iSCSI initiators, use the following basic process:
NOTE: This process is not required for protecting communications between group members. After IPsec is enabled, all
network
traffic
between group members is automatically protected, without need for further
configuration.
1.
A group administrator creates security parameters to specify how
traffic
should be authenticated.
2.
A group administrator creates policies to identify
traffic
and determine what action to take for it:
Traffic
is dropped.
Traffic
is allowed to pass directly through to the array in the clear.
Traffic
is protected using
certificates
or pre-shared keys.
NOTE: IPsec
configurations
cannot be
modified.
They must be removed and then recreated using the new
configuration.
About Group-Level Security
95