IPSec is the next-generation network layer crypto
framework described in RFC2401-2411.
This MIB defines the IPsec configurations.
It may be used to view and provision IPsec-based
To create an IPsec tunnel, you need first configure
Internet Key Exchange (IKE). IKE negotiates Security
Associations with the peer for IPsec. To find out
how to configure IKE, please see
CISCO-IKE-CONFIGURATION-MIB for detail.
Once you setup IKE, you will have to configure IPsec.
To configure IPsec, you need perform following steps.
1. Create an IPsec transform set.
A transform set describes a security protocol
(AH or ESP) with its corresponding algorithms.
For example, ESP with the DES cipher algorithm
and HMAC-SHA for authentication.
2. Create a cryptomap and its peers.
This will a) select data flows that need security
processing and b) defines the policy for these flows
and the crypto peer that traffic needs to go to.
3. Apply cryptomap to an interface
A crypto map is applied to an egress interface.
Outgoing data flows are protected by this cryptomap.
The following acronyms are used in this document:
Static Cryptomap Template:
A static cryptomap template (or static cryptomap)
is a security template created for IPsec.
A static cryptomap pulls together various parts
to set up an IPsec security association
- which traffic should be protected by IPsec
- where IPsec protected traffic should be sent
- the local address used for the the IPsec traffic
- which transform sets should be applied to this
Dynamic Cryptomap Template:
A dynamic cryptomap template (or a dynamic cryptomap)
is essentially a crypto map entry without all the
parameters configured. It acts as a policy template
where the missing parameters are later dynamically
configured (as the result of an IPsec negotiation)
to match a peer's requirements.
A cryptomap set may contain multiple cryptomap
templates which specify an IPsec policy.
Tunnel Endpoint Discovery protocol
This MIB provides the operational information on
Cisco's IPsec implementation of IPsec. This MIB
delineates ISAKMP and IPsec configuration. This MIB
deals only with IPsec (Phase-2) configuration. The
following entities are managed:
a) IPsec Global Parameters
b) IPsec transform set definitions
c) Cryptomap Group
- Cryptomap Set Table
- Cryptomap Table
- CryptomapSet Transform Binding Table
- CryptomapSet Peer Binding Table
- CryptomapSet Interface Binding Table
d) Notification Control Group
e) Notifications Group