Technical information

IPSec VPN Acceleration Services Module Installation and Configuration Note

78-14459-03 Rev C0

Configuring a VPN Using the VPN Module

Using Dead-Peer-Detection

Note This section applies to VPN modules running Cisco IOS Release 12.2(14)SY or later releases.

For complete configuration information for Cisco IOS Dead-Peer-Detection (DPD) support, refer to

this URL:

http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_user_guide_chapter09186a00800ecb3d.html

Using WAN Interfaces

Note This section applies to VPN modules running Cisco IOS Release 12.2(14)SY or later releases.

Follow these guidelines when configuring WAN interfaces:

• Configuring WAN interfaces is the same as configuring Ethernet routed interfaces. From the WAN

subinterface, make a crypto connection to the interface VLAN as follows:

interface Vlan101

ip address 192.168.101.1 255.255.255.0

no mop enabled

crypto map cwan

interface ATM6/0/0.101 point-to-point

pvc 0/101

crypto connect vlan 101

• You must configure a crypto connection on subinterfaces for ATM and Frame Relay. For example,

the following configuration will not work:

interface ATM6/0/0

pvc 0/101

crypto connect vlan 101

• For ATM and Frame Relay, there is no SVC support, no RFC-1483/1490 bridging, and no

point-to-multipoint support.

• For Point-to-Point Protocol (PPP) and Multilink PPP (MLPPP), you must make the physical

interface passive for routing protocols, as follows:

router ospf 10

passive-interface multilink1

• For PPP and MLPPP, there is no Bridging Control Protocol (BCP) support.

WAN interface configuration examples are as follows:

• Crypto Connection for a Channelized T3 Port Adapter in the FlexWAN Module, page 46

• Crypto Connection for an ATM Port Adapter in the FlexWAN Module, page 47

• Crypto Connection for a POS Port Adapter in the FlexWAN Module, page 48