263
To do…
Command…
Remarks
3.
Enable IPsec RRI.
reverse-route
[
remote-peer
ip-
address
[
gateway
|
static
] |
static
]
Required.
Disabled by default.
To enable static IPsec RRI,
specify the
static
keyword. If the
keyword is not specified,
dynamic IPsec RRI is enabled.
4.
Change the preference of
the static routes created by
IPsec RRI.
reverse-route
preference
preference-
value
Optional.
60 by default.
5.
Set a tag for the static
routes created by IPsec RRI.
reverse-route
tag
tag-value
Optional.
0 by default.
NOTE:
•
IPsec RRI can work in both tunnel mode and transport mode.
•
When you change the route attributes, static IPsec RRI deletes all static routes it has created and
creates new static routes. In contrast, dynamic IPsec RRI applies the new attributes only to subsequent
static routes. It does not delete or modify static routes it has created.
Implementing tunnel interface-based IPsec
Configuration task list
This is the generic configuration procedure for implementing tunnel interface-based IPsec:
1.
Configure an IPsec proposal to specify the security protocols, authentication and encryption
algorithms, and encapsulation mode.
2.
Configure an IPsec profile to associate data flows with the IPsec proposal and to specify the IKE
peer parameters and the SA lifetime.
3.
Configure an IPsec tunnel interface, and apply the IPsec profile to the interface. To enhance the
encryption and decryption speed of the IPsec tunnel, bind the IPsec profile to one or more
encryption cards.
NOTE:
Because packets routed to the IPsec tunnel interface are all protected, the data protection scope, which
is required for IPsec policy configuration, is not needed in the IPsec profile.
Complete the following tasks to configure tunnel interface-based IPsec:
Task Remarks
Required
An IPsec proposal for the IPsec
tunnel interface to reference
supports tunnel mode only.
Required
Configuring an IPsec tunnel interface
Required