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

IPsec Performance Considerations, IPsec Configuration Limitations, CLI Commands IPsec

Page 92 highlights

CLI Commands (IPsec) Enter the following CLI commands on the PS Series group to implement the configuration shown in Figure 13. Tunnel Mode (Hostto-Gateway) Using PSK: > ipsec security-params create RemGW_PSK_Auth_Tunnel pre-shared-key key tunnel type v4 tun-ip-addr 10.125.56.1 > ipsec policy create ToRemGW_IPv4_PSK_Ikev1 type v4 ip-addr 10.125.56.0 netmask 255.255.255.0 protocol any action protect RemGW_PSK_Auth_Tunnel IPsec Performance Considerations The performance impact of IPsec varies by host and network configuration, and increases with the number of IPsec-protected iSCSI connections to the group. Even if IPsec is used only to protect traffic between group members, I/O performance is still affected. Based on these factors, you can expect that using IPsec might degrade I/O performance. Although PS Series group members use hardware to accelerate cryptographic operations, many initiators perform these operations in software, which can cause a further reduction in the speed of communications between iSCSI initiators and the group. IPsec Host Connectivity Considerations • Enabling or disabling IPsec for the group using the ipsec enable and ipsec disable commands might disrupt host connectivity to the group for several minutes. To prevent unplanned outages, Dell recommends that IPsec be enabled or disabled during a planned maintenance window when volumes do not have any active iSCSI connections. • Consult the documentation for your host operating systems, HBAs, and iSCSI initiators to verify that they support IPsec. The initiators' IPsec support might have known issues and idiosyncrasies that require additional planning or configuration. When configuring IPsec with Windows hosts, note the following limitations: - IPsec traffic is not always handled correctly if the IPsec policy is configured to protect only a subset of traffic between the host and the group. For example, if the IPsec policy protects only iSCSI traffic on port 3260, the Windows host might not perform reliably when connecting to the group. As a workaround, IPsec policies should apply to all traffic passing between the group and Windows systems. Microsoft KB article 2665206 discusses this workaround in greater detail. - IPsec must be configured using the Windows Firewall with Advanced Security. Do not use the IPsec option in the Microsoft iSCSI initiator, which does not have the capability to fully configure an IPsec configuration between the host and the group. Further, if you attempt to configure an IPsec connection using the iSCSI initiator, the system might not allow you to remove the partial configuration and replace it with a complete configuration created with Windows Firewall. - IPsec policies defined using the Local Security Policy Manager are not supported. strongSWAN Limitations with IPsec If you are using strongSWAN, the following limitations apply: • If you are using certificates, the uniqueids keyword must be disabled (uniqueids=no). • In rare cases, strongSWAN might negotiate standard frames in IPv6 environments even though jumbo frames are configured. • If you are using IKEv2 and the certificate IDs are mismatched, the PSA might behave as if the security association (SA) has been established when it has not. • strongSWAN does not create exceptions for IPv6 neighbor discovery in its Allow All IPsec policy. Consequently, neighbor discovery will fail and security associations (SA) will not be established. As a workaround, use an IPsec policy that uses ports and protocols to manage neighbor discovery. IPsec Configuration Limitations The following limitations apply when implementing IPsec: • IPsec is supported only for certain PS Series array models, and can be enabled for a group only if all members support IPsec. See the Dell EqualLogic PS Series Storage Arrays Release Notes for more information. • IPsec can be enabled and configured only with the Group Manager CLI. The Group Manager GUI provides no facility for configuring or monitoring IPsec. 92 About Group-Level Security

  • 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

CLI Commands (IPsec)
Enter the following CLI commands on the PS Series group to implement the
configuration
shown in
Figure 13. Tunnel Mode (Host-
to-Gateway) Using PSK
:
> ipsec security-params create RemGW_PSK_Auth_Tunnel pre-shared-key key <password> tunnel
type v4 tun-ip-addr 10.125.56.1
> ipsec policy create ToRemGW_IPv4_PSK_Ikev1 type v4 ip-addr 10.125.56.0 netmask
255.255.255.0 protocol any action protect RemGW_PSK_Auth_Tunnel
IPsec Performance Considerations
The performance impact of IPsec varies by host and network
configuration,
and increases with the number of IPsec-protected iSCSI
connections to the group. Even if IPsec is used only to protect
traffic
between group members, I/O performance is still
affected.
Based on these factors, you can expect that using IPsec might degrade I/O performance.
Although PS Series group members use hardware to accelerate cryptographic operations, many initiators perform these operations in
software, which can cause a further reduction in the speed of communications between iSCSI initiators and the group.
IPsec Host Connectivity Considerations
Enabling or disabling IPsec for the group using the
ipsec enable
and
ipsec disable
commands might disrupt host connectivity to
the group for several minutes. To prevent unplanned outages, Dell recommends that IPsec be enabled or disabled during a
planned maintenance window when volumes do not have any active iSCSI connections.
Consult the documentation for your host operating systems, HBAs, and iSCSI initiators to verify that they support IPsec. The
initiators' IPsec support might have known issues and idiosyncrasies that require additional planning or
configuration.
When
configuring
IPsec with Windows hosts, note the following limitations:
IPsec
traffic
is not always handled correctly if the IPsec policy is
configured
to protect only a subset of
traffic
between the
host and the group. For example, if the IPsec policy protects only iSCSI
traffic
on port 3260, the Windows host might not
perform reliably when connecting to the group. As a workaround, IPsec policies should apply to all
traffic
passing between the
group and Windows systems.
Microsoft KB article 2665206
discusses this workaround in greater detail.
IPsec must be
configured
using the Windows Firewall with Advanced Security. Do not use the IPsec option in the Microsoft
iSCSI initiator, which does not have the capability to fully
configure
an IPsec
configuration
between the host and the group.
Further, if you attempt to
configure
an IPsec connection using the iSCSI initiator, the system might not allow you to remove
the partial
configuration
and replace it with a complete
configuration
created with Windows Firewall.
IPsec policies
defined
using the Local Security Policy Manager are not supported.
strongSWAN Limitations with IPsec
If you are using strongSWAN, the following limitations apply:
If you are using
certificates,
the
uniqueids
keyword must be disabled (
uniqueids=no
).
In rare cases, strongSWAN might negotiate standard frames in IPv6 environments even though jumbo frames are
configured.
If you are using IKEv2 and the
certificate
IDs are mismatched, the PSA might behave as if the security association (SA) has been
established when it has not.
strongSWAN does not create exceptions for IPv6 neighbor discovery in its Allow All IPsec policy. Consequently, neighbor
discovery will fail and security associations (SA) will not be established. As a workaround, use an IPsec policy that uses ports and
protocols to manage neighbor discovery.
IPsec
Configuration
Limitations
The following limitations apply when implementing IPsec:
IPsec is supported only for certain PS Series array models, and can be enabled for a group only if all members support IPsec. See
the
Dell EqualLogic PS Series Storage Arrays Release Notes
for more information.
IPsec can be enabled and
configured
only with the Group Manager CLI. The Group Manager GUI provides no facility for
configuring
or monitoring IPsec.
92
About Group-Level Security