295
Step Command
Remarks
mask-length
] |
ipv6
ipv6-address
[
prefix-length
] } |
hostname host-name
}
key
[
cipher cipher-key
]
4.
(Optional.) Specify a local
interface or IP address to
which the IKE keychain can
be applied.
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 end.
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 to which the IPsec policy or
IPsec policy template is applied 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.
If the aggressive IKE SA negotiation
mode and signature authentication
are used, configure this command on
the local device when the device
interconnects with a Comware
5-based peer device. Comware 5
supports only DN for signature
authentication.
Configuring the IKE keepalive feature
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 on the local device. 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 feature:
