
Extranet VPN Business Scenario 4-11
Configuring IPSec and IPSec Tunnel Mode
Note Set an ISAKMP identity whenever you specify preshared keys. The address
keyword is typically used when there is only one interface (and therefore only one IP
address) that will be used by the peer for IKE negotiations, and the IP address is known.
Use the hostname keyword if there is more than one interface on the peer that might be
used for IKE negotiations, or if the interface’s IP address is unknown (such as with
dynamically-assigned IP addresses).
Configuring IPSec and IPSec Tunnel Mode
After you have configured a different shared key, configure IPSec at each participating
IPSec peer. This section contains basic steps to configure IPSec and includes the following
tasks:
1 Setting Global Lifetimes for IPSec Security Associations
2 Verifying Global Lifetimes for IPSec Security Associations
Note If you set global lifetimes for IPSec SAs while configuring IPSec in Chapter 3,
“Intranet VPN Business Scenario,” there is no need to set lifetimes again here. If you have
not configured global lifetimes for IPSec SAs on your Cisco 7100 series router, see the
“Setting Global Lifetimes for IPSec Security Associations” section on page 3-20 before
creating your crypto access lists.
3 Creating Crypto Access Lists
4 Verifying Crypto Access Lists
3
bus-ptnr(config)# crypto isakmp key
67890 address 172.17.2.4
At the remote peer: Specify the shared key to be
used with the local peer. This is the same key you
just specified at the local peer. This example
configures the shared key 67890 to be used with the
local peer 172.16.2.2 (serial interface 2/0 on the
headquarters router).
Step Command Purpose
Kommentare zu diesen Handbüchern