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

Configuring the global identity information, Configuring the IKE keepalive function

Page 238 highlights

Step 4. (Optional.) Specify a local interface or IP address that the IKE keychain can be applied to. 5. (Optional.) Specify a priority for the IKE keychain. Command match local address { interface-type interface-number | { ipv4-address | ipv6 ipv6-address } [ vpn-instance vpn-name ] } priority number Remarks By default, an IKE keychain can be applied to any local interface or IP address. The default priority is 100. Configuring the global identity information Follow these guidelines when you configure the global identity information for the local IKE. • The global identity can be used by the device for all IKE SA negotiations, and the local identity (set by the local-identity command) can be used only by the device that uses the IKE profile. • When signature authentication is used, you can set any type of the identity information. • When pre-shared key authentication is used, you cannot set the DN as the identity. To configure the global identity information: Step 1. Enter system view. 2. Configure the global identity to be used by the local. Command system-view ike identity { address { ipv4-address | ipv6 ipv6-address } | dn | fqdn [ fqdn-name ] | user-fqdn [ user-fqdn-name ] } 3. (Optional.) Configure the local device to always obtain the identity information from the local certificate for ike signature-identity from-certificate signature authentication. Remarks N/A By default, the IP address of the interface where the IPsec policy or IPsec policy template applies is used as the IKE identity. By default, the local end uses the identity information specified by local-identity or ike identity for signature authentication. Configure the command on the local device that initiates aggressive IKE SA negotiations that use signature authentication for compatibility with the peer device running a Comware V5-based release. Such release supports only DN for signature authentication. Configuring the IKE keepalive function IKE sends keepalive packets to query the liveness of the peer. If the peer is configured with the keepalive timeout time, you must configure the keepalive interval at the local. If the peer receives no keepalive packets during the timeout time, the IKE SA is deleted along with the IPsec SAs it negotiated. Follow these guidelines when you configure the IKE keepalive function: 229

  • 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

229
Step
Command
Remarks
4.
(Optional.) Specify a local
interface or IP address that
the IKE keychain can be
applied to.
match local address
{
interface-type
interface-number
| {
ipv4-address
|
ipv6
ipv6-address
} [
vpn-instance
vpn-name
] }
By default, an IKE keychain can
be applied to any local interface
or IP address.
5.
(Optional.) Specify a
priority for the IKE keychain.
priority
number
The default priority is 100.
Configuring the global identity information
Follow these guidelines when you configure the global identity information for the local IKE.
The global identity can be used by the device for all IKE SA negotiations, and the local identity (set
by the
local-identity
command) can be used only by the device that uses the IKE profile.
When signature authentication is used, you can set any type of the identity information.
When pre-shared key authentication is used, you cannot set the DN as the identity.
To configure the global identity information:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure the global identity
to be used by the local.
ike identity
{
address
{
ipv4-address
|
ipv6
ipv6-address
} |
dn
|
fqdn
[
fqdn-name
]
|
user-fqdn
[
user-fqdn-name
] }
By default, the IP address of the
interface where the IPsec policy or
IPsec policy template applies is used
as the IKE identity.
3.
(Optional.) Configure the
local device to always obtain
the identity information from
the local certificate for
signature authentication.
ike signature-identity
from-certificate
By default, the local end uses the
identity information specified by
local-identity
or
ike identity
for
signature authentication.
Configure the command on the local
device that initiates aggressive IKE SA
negotiations that use signature
authentication for compatibility with
the peer device running a Comware
V5-based release. Such release
supports only DN for signature
authentication.
Configuring the IKE keepalive function
IKE sends keepalive packets to query the liveness of the peer. If the peer is configured with the keepalive
timeout time, you must configure the keepalive interval at the local. If the peer receives no keepalive
packets during the timeout time, the IKE SA is deleted along with the IPsec SAs it negotiated.
Follow these guidelines when you configure the IKE keepalive function: