HP 6125XLG R2306-HP 6125XLG Blade Switch Security Configuration Guide - Page 237

Configuring an IKE keychain

Page 237 highlights

Step 5. Specify an authentication algorithm for the IKE proposal. 6. Specify a DH group for key negotiation in phase 1. 7. Set the IKE SA lifetime for the IKE proposal. Command • In non-FIPS mode: authentication-algorithm { md5 | sha } • In FIPS mode: authentication-algorithm sha • In non-FIPS mode: dh { group1 | group14 | group2 | group24 | group5 } • In FIPS mode: dh group14 sa duration seconds Remarks By default, an IKE proposal uses the HMAC-SHA1 authentication algorithm. By default, DH group1 (the 768-bit DH group) is used in non-FIPS mode, and DH group 14 (2048-bit DH group) is used in FIPS mode. By default, the IKE SA lifetime is 86400 seconds. Configuring an IKE keychain Perform this task when you configure the IKE to use the pre-shared key for authentication. Follow these guidelines when you configure an IKE keychain: 1. Two peers must be configured with the same pre-shared key to pass pre-shared key authentication. 2. You can specify the local address configured in IPsec policy or IPsec policy template view (using the local-address command) for the IKE keychain to be applied. If no local address is configured, specify the IP address of the interface referencing the IPsec policy. 3. You can specify a priority number for the IKE keychain. To determine the priority of an IKE keychain: a. The device examines the existence of the match local address command. An IKE keychain with the match local address command configured has a higher priority. b. If a tie exists, the device compares the priority numbers. An IKE keychain with a smaller priority number has a higher priority. c. If a tie still exists, the device prefers an IKE keychain configured earlier. To configure the IKE keychain: Step Command Remarks 1. Enter system view. system-view N/A 2. Create an IKE keychain and ike keychain keychain-name enter its view. [ vpn-instance vpn-name ] By default, no IKE keychain exists. By default, no pre-shared key is pre-shared-key { address configured. { ipv4-address [ mask | mask-length ] | For security purposes, all 3. Configure a pre-shared key. ipv6 ipv6-address [ prefix-length ] } | pre-shared keys, including those hostname host-name } key { cipher configured in plain text, are cipher-key | simple simple-key } saved in cipher text to the configuration file. 228

  • 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

228
Step
Command
Remarks
5.
Specify an authentication
algorithm for the IKE
proposal.
In non-FIPS mode:
authentication-algorithm
{
md5
|
sha
}
In FIPS mode:
authentication-algorithm sha
By default, an IKE proposal uses
the HMAC-SHA1 authentication
algorithm.
6.
Specify a DH group for key
negotiation in phase 1.
In non-FIPS mode:
dh
{
group1
|
group14
|
group2
|
group24
|
group5
}
In FIPS mode:
dh group14
By default, DH group1 (the
768-bit DH group) is used in
non-FIPS mode, and DH group
14 (2048-bit DH group) is used
in FIPS mode.
7.
Set the IKE SA lifetime for
the IKE proposal.
sa
duration
seconds
By default, the IKE SA lifetime is
86400 seconds.
Configuring an IKE keychain
Perform this task when you configure the IKE to use the pre-shared key for authentication.
Follow these guidelines when you configure an IKE keychain:
1.
Two peers must be configured with the same pre-shared key to pass pre-shared key authentication.
2.
You can specify the local address configured in IPsec policy or IPsec policy template view (using
the
local-address
command) for the IKE keychain to be applied. If no local address is configured,
specify the IP address of the interface referencing the IPsec policy.
3.
You can specify a priority number for the IKE keychain. To determine the priority of an IKE
keychain:
a.
The device examines the existence of the
match local address
command. An IKE keychain with
the
match local address
command configured has a higher priority.
b.
If a tie exists, the device compares the priority numbers. An IKE keychain with a smaller priority
number has a higher priority.
c.
If a tie still exists, the device prefers an IKE keychain configured earlier.
To configure the IKE keychain:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create an IKE keychain and
enter its view.
ike keychain
keychain-name
[
vpn-instance
vpn-name
]
By default, no IKE keychain
exists.
3.
Configure a pre-shared key.
pre-shared-key
{
address
{
ipv4-address
[
mask
|
mask-length
] |
ipv6
ipv6-address
[
prefix-length
] } |
hostname
host-name
}
key
{
cipher
cipher-key
|
simple
simple-key
}
By default, no pre-shared key is
configured.
For security purposes, all
pre-shared keys, including those
configured in plain text, are
saved in cipher text to the
configuration file.