Header
Home | Set as homepage | Add to favorites
  Search the Site     » Advanced Search
Sections
Syndication


Blogroll:

||||| ALL Cisco-Network ARTICLES |||||  
CCIE Journey,
The CCIE Journey,


Phase Two Features-Manual Tunnel Control

Oct 18,2009 by alperen

image

Phase Two Features

Cisco Easy VPN Remote Phase Two provides automatic management of the following features:

Manual Tunnel Control

With the original Cisco Easy VPN Remote, the VPN tunnel connects automatically on configuration. If the tunnel times out or fails, it automatically reconnects or retries indefinitely. Phase Two implements manual control over IPSec VPN tunnels, making it possible to establish and terminate the tunnel on demand. The manual feature is implemented with a new subcommand under the crypto ipsec client ezvpn command. The syntax is as follows:

Rtr1(config)#crypto ipsec client ezvpn name
Rtr1(config-crypto-ezvpn)#connect [auto | manual]

Automatic is the default setting, compatible with Phase One functionality. As such, the subcommand with the autoparameter is only needed to reverse the manual option.

With the manual option, the Easy VPN Client waits for the following command to attempt to establish the connection or to reestablish a timed out or failed session:

Rtr1#crypto ipsec client ezvpn connect name

Use the following clear command to disconnect an established tunnel.

Rtr1#clear crypto ipsec client ezvpn [name]

Multiple Outside Interfaces Support

Phase One supports only one outside interface on the remote client router. The crypto ipsec client ezvpn name outside command option allows designating up to four outside interfaces. The default option is outside. The syntax is as follows:

Rtr1(config-if)#interface interface-id
Rtr1(config-if)#crypto ipsec client ezvpn name [outside | inside]

This feature is applicable only to platforms, such as the Cisco 1700 series routers, that support multiple outside interfaces.

While each inside or outside interface supports only one tunnel, multiple inside interfaces can be mapped to one outside interface.

The following example shows configuring an outside interface using the designation outside. As the default, the outside didn’t need to be included:

Rtr1(config)#interface serial 0/0
Rtr1(config-if)#crypto ipsec client ezvpn vpn1 outside


515 times read

Related news

» NAT Interoperability Support
by alperen posted on Oct 18,2009
» Peer Host Name Enhancement
by alperen posted on Oct 18,2009
» Simultaneous Easy VPN Client and Server Support
by alperen posted on Oct 18,2009
» Step 3-5 Apply the Crypto Maps to the Interface
by alperen posted on Sep 27,2009
» Easy VPN Remote Phase Two
by alperen posted on Oct 18,2009
Did you enjoy this article?
(total 0 votes)

comment Comments (0 posted) 

More Top News
CCSP-Cisco Certified Security Professional
Most Popular
Most Commented
Featured Author