-
null
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The pages that you access by selecting Site-To-Site VPN Manager from the Tools menu, or clicking the Site-To-Site VPN Manager button on the toolbar, help you configure site-to-site VPNs.
Note You can also configure site-to-site VPNs in Device view (View > Device View) and Policy view (View > Policy View). For more information, see:
Managing VPN Devices in Device View, page 9-42
Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44
These topics describe the pages that help you create VPN topologies, and the policies that will be assigned to them:
•Site-to-Site VPN Manager Window
•VPN Topologies Device View Page
•Rediscover VPN Policies Wizard
Use the Site-to-Site VPN Manager window to:
•Create, edit, and delete VPN topologies.
•View detailed information about each VPN topology.
•View the endpoints defined for a VPN topology.
•View and edit the policies assigned to a VPN topology.
The VPNs selector, in the upper left pane of the window, lists all available VPN topologies, and enables you to select topologies for viewing or editing. The lower left pane of the page lists the policies that are assigned to the VPN topology selected in the upper pane.
Navigation Path
Click the Site-To-Site VPN Manager button on the toolbar or select Tools > Site-To-Site VPN Manager.
Related Topics
•Understanding VPN Topologies, page 9-2
•Working with VPN Topologies, page 9-14
•Using the Policy Banner, page 6-25
Field Reference
|
|
---|---|
Create VPN Topology button |
Click to create a VPN topology, then select the type of topology you want to create from the options that are displayed. The Create VPN wizard opens. |
Edit VPN Topology button |
Opens the Edit VPN dialog box for editing a selected VPN topology. Note You can also edit a VPN topology by right-clicking it in the VPNs selector, and selecting the Edit option. |
Delete VPN Topology button |
Deletes a selected VPN topology. Note You can also delete a selected VPN topology by right-clicking it and selecting the Delete option. A confirmation dialog box opens asking you to confirm the deletion. |
VPNs selector |
Lists each VPN topology, represented by its name and an icon indicating its VPN type (hub and spoke, point to point, or full mesh). |
Policies selector |
Lists each individually named policy that is already assigned to, or can be configured on, devices in the selected VPN topology. Select a policy to open a page on which you can view or edit the parameters for the selected policy. See Site to Site VPN Policies. |
Security Manager supports three basic types of topologies with which you can create a site-to-site VPN. Use the Create VPN wizard to create a hub-and-spoke, point-to-point, or full mesh VPN topology across multiple device types. For more information, see Understanding VPN Topologies, page 9-2.
Note You can deploy to your devices immediately after creating a VPN topology, using the default policy configurations provided by Security Manager. All you need to do is complete the steps of the Create VPN wizard.
Editing a VPN topology is done using the Edit VPN dialog box, which comprises tabs whose elements are identical (except for the buttons) to the pages of the Create VPN wizard. You can click a tab to go directly to the page that contains the fields you want to edit, without having to go through each step of the wizard. Clicking OK on any tab in the dialog box saves your definitions on all the tabs. For more information, see Editing a VPN Topology, page 9-27.
The pages that appear and their sequence depend on the type of VPN topology you are creating.
|
|
|
|
Step 1 |
Step 1 |
Step 1 |
|
Step 2 |
Step 2 |
Step 2 |
|
Step 3 |
Step 3 |
— |
|
Step 4 |
— |
— |
|
— |
— |
Step 3 |
|
— |
— |
Step 4 |
|
Step 5 |
Step 4 |
Step 5 |
Navigation Path
1. In the Site-to-Site VPN Manager Window, click the Create VPN Topology button above the VPNs selector.
2. Select the type of VPN topology you want to create from the options that are displayed—Hub and Spoke, Point to Point, or Full Mesh.
Related Topics
•Understanding VPN Topologies, page 9-2
•Understanding IPsec Technologies and Policies, page 9-5
•Using the Create VPN Wizard, page 9-14
Use the Name and Technology page of the Create VPN wizard to define a name and description for the VPN topology and to select the IPsec technology that will be assigned to it.
Navigation Path
•When creating a VPN topology, open the Create VPN Wizard.
•When editing a VPN topology, open the Site-to-Site VPN Manager Window, then right-click a VPN topology in the VPNs selector, or click the Name and Technology tab in the Edit VPN dialog box.
Related Topics
•Editing a VPN Topology, page 9-27
•Understanding IPsec Technologies and Policies, page 9-5
•Defining a Name and IPsec Technology, page 9-16
Field Reference
|
|
---|---|
Name |
A unique name that identifies the VPN topology. |
Description |
Information about the VPN topology. |
IPsec Technology |
IPsec technology associated with the VPN topology: Regular IPsec, IPsec/GRE, DMVPN, Easy VPN, or GET VPN. Note If you are editing an existing VPN, the assigned IPsec technology is displayed, but unavailable for editing. To edit the technology, you must delete the VPN topology and create a new one. |
Type |
Available if the selected IPsec technology is IPsec/GRE or DMVPN. •IPsec/GRE—Select either Standard (for IPsec/GRE) or Spokes with Dynamic IP (for GRE Dynamic IP). For more information, see Configuring GRE or GRE Dynamic IP Policies, page 9-65. •DMVPN—Select either Standard (for regular DMVPN) or Large Scale with IPsec Terminator (for a large scale DMVPN). For more information, see Configuring Large Scale DMVPNs, page 9-70. |
Use the Device Selection page of the Create VPN wizard to select the devices that will be included in the VPN topology. The devices that are available for selection include only those that can be used for the selected VPN topology type, that support the IPsec technology type, and which you are authorized to view.
Navigation Path
•When creating a VPN topology, open the Create VPN Wizard, then click Next on the Name and Technology page.
•When editing a VPN topology, click the Device Selection tab in the Edit VPN dialog box.
•In the VPN Topologies Device View Page, click the Edit VPN Topology button.
Related Topics
•Editing a VPN Topology, page 9-27
•About Selecting Devices in a VPN Topology, page 9-17
•Selecting Devices for Your VPN Topology, page 9-18
•About Selecting Devices in a VPN Topology, page 9-17
•About Editing a VPN Topology, page 9-25
Field Reference
|
|
---|---|
Available Devices |
Lists all devices that can be included in your selected VPN topology, that support the IPsec technology type, and which you are authorized to view. Note Clicking a device group selects all its devices. |
IPsec Terminators |
Available only if you selected Large Scale with IPsec Terminator as the DMVPN technology type in the Name and Technology page. Catalyst 6500/7600 devices defined as IPsec Terminators in your Large Scale DMVPN configuration. To add devices to the list, select them and click >>. To remove devices from the list, select them and click <<. Note You can use the Up and Down buttons to change the order of the devices in the list. For more information, see Configuring Large Scale DMVPNs, page 9-70. |
Hubs |
Devices defined as hubs in your hub-and-spoke topology. In an Easy VPN topology, the selected devices are servers. Note If you selected only one device, it becomes the primary hub. If multiple devices are selected, you must make sure that the required primary hub device appears first in the list. You can use the Up and Down buttons to change the order of the Hubs in the list. |
Spokes |
Devices defined as spokes in your hub-and-spoke topology. In an Easy VPN topology, the selected devices are clients. |
Peer One/Peer Two |
Devices defined as peers in your point-to-point topology. |
Key Servers |
Devices defined as key servers in your GET VPN topology. |
Group Members |
Devices defined as group members in your GET VPN topology. |
>> button |
To add devices to the list, select them and click >> |
>>button |
To remove devices from the list, select them and click <<. |
Use the GET VPN Group Encryption page to define the group encryption policy to be used by the VPN topology.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select Group Encryption in the Policies selector.
•You can also open the Group Encryption Policy page from Policy view.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
|
|
---|---|
Group Name |
Name of the Group Domain of Interpretation (GDOI) group. This name is the same as a VPN name. |
Group Identity |
Parameter that is used to identify the group. All key servers and group members use this parameter to identify the group. The identity can be either a number or any IP address. |
Receive Only |
If enabled, group members decrypt traffic and forward it in clear text. This feature is useful for testing the VPN. |
Security Policy |
ACL Policy object to be used as the security policy. Note The ACL policy object must contain a deny ACE statement as its first deny statement. This statement allows the group members to receive rekey packets sent using multicast protocol. |
Authorization Type |
Type of association mechanism used by the group: None, Certificates, or Preshared Key. If you select Certificates, you must define a certificates filter (either dn or fqdn). This filter, located on the key server, specifies the attributes and values used to validate whether the group member is authorized to join the GDIO or not. |
Key Distribution |
Address method used to distribute keys to each group member: •Unicast or Multicast—If unicast is selected, the key server sends a rekey message to each registered group member and waits for an acknowledgment. If multicast is selected, the key server sends a rekey message to all group members at once. Note If you select multicast, make sure that the router used as the key server is multicast enabled. •Group IP Address—IP Address to be used for key distribution. •Use Static IGMP Joins on Group Members—This checkbox is applicable only when key servers use multicast to distribute keys to group members. If you select this option, the static Source Specific Multicast (SSM) mappings are enabled, which reveal the source of multicast traffic to the group member. In the case of GET VPN, the group member learns the key server address. |
RSA Key Label |
(Optional) Label that key servers use to sign rekey messages with. If rekeying is not required, you do not need to assign an RSA key label. Note Security Manager does not manage RSA keys and therefore appropriate keys need to be manually generated on the key server before deployment. FlexConfig can be used. See Creating FlexConfig Policy Objects, page 18-26. |
Lifetime (KEK) |
Number of seconds that the key encryption key (KEK) is valid. Note If you are encrypting high packet rates for count-based anti-replay, ensure that you do not make the lifetime too long or it can take several hours for the sequence number to wrap. For example, if the packet rate is 100 kilopackets per second, the lifetime should be configured as less than 11.93 hours so that the SA is used before the sequence number wraps. |
Encryption Algorithm |
Algorithm that the key server uses to encrypt the rekey messages sent to group members. |
Retransmits |
Number of times the rekey message can be sent. |
Interval |
Number of seconds between retries. |
Use the Endpoints page of the Create VPN wizard to view the devices in your VPN topology, and define or edit their external or internal interfaces and protected networks.
Note The internal and external interfaces that appear on the Endpoints page are the default interfaces that are defined in the Administration tool's VPN Defaults page. For more information, see VPN Policy Defaults Page, page A-41.
The Endpoints page displays a scrollable table listing the VPN interfaces and protected networks for all selected devices. By clicking on the arrow displayed alongside any table heading, you can switch the order of the list to display from ascending to descending order, and vice versa. You can also filter the table contents using the filter controls above it to display only rows that match the criteria that you specify (see Filtering Tables, page 2-16).
Note When editing a VPN topology, the Endpoints tab is used. The elements of the tab (except for the buttons) are identical to those that appear on the Endpoints page. For more information, see Editing a VPN Topology, page 9-27.
Navigation Path
•When creating a VPN topology, open the Create VPN Wizard, then click Next on the Device Selection page.
•When editing a VPN topology, click the Endpoints tab in the Edit VPN dialog box.
Related Topics
•Editing a VPN Topology, page 9-27
•About Defining and Editing the Endpoints and Protected Networks, page 9-19
•Defining the Endpoints and Protected Networks, page 9-20
Field Reference
|
|
---|---|
Role |
The role of the device—hub, spoke, peer, or IPsec Terminator. |
Device |
The name of the device. |
VPN Interface |
The primary or backup VPN interface that is defined for the selected device. Depending on the selection in the Show list, the interface roles, or the interfaces that match each interface role, for the VPN interface may also be displayed. Select a row and click Edit to change the device's VPN interfaces. The Edit Endpoints dialog box opens, from which you can select the required VPN interface. See VPN Interface Tab. Note You can select more than one device at a time for editing. The changes you make in the VPN Interface tab are applied to all the selected devices. |
Protected Networks |
The protected networks that are defined for the selected device. Depending on the selection in the Show list, the interface roles, or the interfaces that match each interface role, for the protected networks may also be displayed. Select a row and click Edit to change the device's protected networks. The Edit Endpoints dialog box opens, from which you can select the required protected networks. See Protected Networks Tab. Note You can select more than one device at a time for editing. The changes you make in the Protected Networks tab are applied to all selected devices. |
Show |
Select to display either the interface roles or matching interfaces, for the VPN interfaces and protected networks in the table, as follows: •Interface Roles Only (default)—To display only the interface roles assigned to the VPN interfaces and protected networks. •Matching Interfaces—To display the interfaces that match the pattern of each interface role. If there are no matching interfaces "No Match" will be displayed. |
Edit button |
Opens the Edit Endpoints dialog box so you can edit the VPN interface and/or protected networks for a selected device in the table. See Edit Endpoints Dialog Box. |
Use the Edit Endpoints dialog box to:
•Edit the VPN interfaces and protected networks defined for devices.
•Edit a hub interface that is connected to an IPsec Terminator in a large scale DMVPN.
•Configure a dial backup interface to use as a fallback link for a primary VPN interface.
•Define VPN Services Module (VPNSM) settings for a Catalyst 6500/7600 device.
•Define VPN SPA settings for a Catalyst 6500/7600 device (which may be an IPsec Terminator in a Large Scale DMVPN topology).
•Configure FWSM on a Catalyst 6500/7600 device.
•Configure a VRF-Aware-IPsec policy on a hub device.
The following tabs may be available on the Edit Endpoints dialog box:
•VPN Interface Tab—VPNSM/VPN SPA Settings
Navigation Path
From the Endpoints Page (or tab), select a device in the Endpoints table, and click Edit.
Related Topics
•Defining the Endpoints and Protected Networks, page 9-20
•Configuring Dial Backup, page 9-29
•Procedure for Configuring a VPNSM or VPN SPA/VSPA, page 9-31
•Configuring a Firewall Services Module (FWSM) Interface with VPNSM or VPNSPA/VSPA, page 9-33
•Configuring VRF-Aware IPsec Settings, page 9-38
Note If the device you selected for editing in the Endpoints table is a hub in a large scale DMVPN, the Hub Interface tab opens, enabling you to specify the interface that is connected to the IPsec Terminator, in the field provided. For more information, see Configuring Large Scale DMVPNs, page 9-70.
Note If you selected a Catalyst 6500/7600 device in the Endpoints table for editing, the VPN Interface tab provides settings that enable you to configure a VPN Services Module (VPNSM) or a VPNSPA/VSPA blade on the device. For a description of the elements that appear on the VPN Interface tab for a Catalyst 6500/7600 device, see Table G-7.
Use the VPN Interface tab in the Edit Endpoints dialog box to edit the VPN interfaces defined for devices in the Endpoints table. When defining a primary VPN interface for a router device, you can also configure a backup interface to use as a fallback link for the primary route VPN interface, if its connection link becomes unavailable. You can configure a backup interface on a Cisco IOS security router, that is in a point-to-point or full mesh topology, or that is a spoke in a hub-and-spoke topology, or is a remote client in an Easy VPN topology. For more information, see Understanding Dial Backup, page 9-29.
Navigation Path
The VPN Interface tab is displayed when you open the Edit Endpoints Dialog Box. You can also open it by clicking the VPN Interface tab from any other tab in the Edit Endpoints dialog box.
Related Topics
•Defining the Endpoints and Protected Networks, page 9-20
•Configuring Dial Backup, page 9-29
•Procedure for Configuring a VPNSM or VPN SPA/VSPA, page 9-31
•Creating Interface Role Objects, page 8-34
Field Reference
Table G-6 describes the elements on the VPN Interface tab when a device other than a Catalyst 6500/7600 is selected. For a description of the elements that appear on the VPN Interface tab for a Catalyst 6500/7600 device, see Table G-7.
|
|
---|---|
Enable the VPN Interface Changes on All Selected Peers |
Available if you selected more than one device on the Endpoints page for editing. When selected, applies any changes you make in the VPN interface tab to all the selected devices. |
VPN Interface |
The VPN interface defined for the selected device. The default is External. VPN interfaces are predefined interface role objects. If required, click Select to open a dialog box that lists all available interfaces, and sets of interfaces defined by interface roles, in which you can make your selection, or create interface role objects. If the device is an ASA 5505 version 7.2(1) or later, it must have two interfaces defined with different security levels. For more information, see Managing Device Interfaces, page 14-5. |
Connection Type |
Only available in a hub-and-spoke VPN topology, if the selected device is an ASA or PIX 7.0 hub, and the selected technology is Regular IPsec. Select the type of connection that the ASA hub will use during an SA negotiation: •Answer Only—To configure the hub to only respond to an SA negotiation, but not initiate it. •Originate Only—To configure the hub to only initiate an SA negotiation, but not respond to one. •Bidirectional—To configure the hub to both initiate and respond to an SA negotiation. |
Local Peer IPSec Termination |
Unavailable if the selected technology is Easy VPN. Specifies the IP address of the VPN interface of the local router. You can select one of the following options: •VPN Interface IP Address—This is the default. Uses the configured IP address on the selected VPN interface. Only one VPN interface can match the interface role. •IP Address—To enter manually the IP address of the VPN interface of the local router. Enter the IP address in the field provided. Note If you select a tunnel source as the VPN interface, it is likely that the VPN interface has a dynamically assigned IP address. •IP Address of Another Existing Interface to be Used as Local Address (unavailable if IPsec technology is DMVPN)—To use the configured IP address on any interface as a local address, not necessarily a VPN interface. Enter the interface in the field provided. You can choose the required interface by clicking Select. A dialog box opens that lists all available predefined interface roles, and in which you can create an interface role object. |
Tunnel Source |
Available only for a hub when the selected technology is IPsec/GRE or DMVPN. If you have enabled the setting to use a unique tunnel source per tunnel interface in the GRE Modes > Tunnel Parameters tab, the Override Unique Tunnel Source per Tunnel Interface check box is available. Click this check box to specify a different tunnel source for the selected device. Specifies the tunnel source address to be used by the GRE or DMVPN tunnel on the spoke side. You can select one of the following options: •Inside VLAN—Uses the inside VLAN VPN interface as the tunnel source address. •Outside VLAN/External Port (When CCA/VRF is Enabled)—Uses the outside VLAN VPN interface as the tunnel source address (available only when CCA/VRF is enabled). •Interface—To use any interface as the tunnel source address, not necessarily a VPN interface. Enter the interface in the field provided. |
|
|
Enable Backup |
Available if the selected device is an IOS router that is in a point-to-point or full mesh topology, or that is a spoke in a hub-and-spoke topology, or is a remote client in an Easy VPN topology. When selected, enables you to configure a backup interface to use as a fallback link for the primary route VPN interface, if its connection link becomes unavailable. Note Before configuring a backup interface, you must first configure the dialer interface settings on the device. For more information, see Dialer Interfaces on Cisco IOS Routers, page 13-22. |
Dialer Interface |
The logical interface through which the secondary route traffic is directed when the dialer interface is activated. This can be a Serial, Async, or BRI interface. You can choose the required interface by clicking Select. A dialog box opens that lists all available interfaces and predefined interface roles, and in which you can create an interface role object. |
Primary Next Hop IP Address |
Available only if the selected technology is Regular IPsec, IPsec/GRE, GRE Dynamic IP, or Easy VPN. The IP address to which the primary interface connects when it is active. This is known as the next hop IP address. If you do not specify the next hop IP address, Security Manager configures a static route using the VPN interface name. The VPN interface must be point-to-point or deployment fails. You can choose the required IP address by clicking Select. The Network/Hosts selector opens, in which you can select a network from which the IP address will be allocated. |
Tracking IP Address |
The IP address of the destination device to which connectivity must be maintained from the primary VPN interface connection. This is the device that is pinged by the Service Assurance agent through the primary route to track connectivity. The backup connection is triggered if connectivity to this device is lost. Note If you do not specify an IP address, the primary hub VPN interface is used in a hub-and-spoke or Easy VPN topology. In a point-to-point or full mesh VPN topology, the peer VPN interface is used. You can choose the required IP address by clicking Select. The Network/Hosts selector opens, in which you can select a network from which the IP address will be allocated. |
Advanced button |
Available if the selected technology is Regular IPsec, IPsec/GRE, GRE Dynamic IP, or Easy VPN. Opens the Dial Backup Settings dialog box for configuring additional (optional) settings. See Dial Backup Settings Dialog Box. |
When you select a Catalyst 6500/7600 device in the Endpoints table for editing, the VPN Interface tab of the Edit Endpoints dialog box provides settings for configuring a VPN Services Module (VPNSM) or VPNSPA/VSPA on the device. You can select more than one Catalyst 6500/7600 device at the same time. Your changes are applied to all the selected devices.
Note These settings must also be configured if the selected device is an IPsec Terminator in a large scale DMVPN. See Configuring Large Scale DMVPNs, page 9-70.
If you are configuring a VPNSM or VPNSPA/VSPA with VRF-Aware IPsec on a device, verify that the device does not belong to a different VPN topology in which VRF-Aware IPsec is not configured. Similarly, if you are configuring a VPNSM or VPNSPA/VSPA without VRF-Aware IPsec, make sure that the device belongs to a different VPN topology in which VRF-Aware IPsec is configured.
Navigation Path
•From the Endpoints Page, select a Catalyst 6500/7600 device and click the Edit button.
Field Reference
|
|
---|---|
Enable the VPN Interface Changes on All Selected Peers |
Note Available if you selected more than one Catalyst 6500/7600 device for editing in the Endpoints page. When selected, applies any changes you make in the VPN interface tab to all the selected devices. |
VPNSM/VPN SPA Settings |
•Use Crypto Connect Alternate—When selected, only encrypted traffic entering the VPNSM/VPN SPA on the Catalyst 6500/7600 is passed through. Cleartext traffic does not go through (bypasses) the adapters. •Inside VLAN—VLAN that serves as the inside interface to the VPN Services Module or VPN SPA. It is also the hub endpoint of the VPN tunnel (unless VRF-Aware IPsec is configured on the device). Enter the name of the interface or click Select to display an Object Selectors, page F-205. •Slot and Subslot—Number designating the slot location of the VPNSM or VPNSPA/VSPA. If you are configuring a VPNSPA/VSPA, the subslot number is also required. •Outside VLAN/Extern—External port or VLAN that connects to the inside VLAN. Enter the name of the interface or click Select to display an Object Selectors, page F-205. Note If VRF-Aware IPsec is configured on the device, the external port or VLAN must have an IP address. Note You must select an interface or interface role that differs from the one selected for the inside VLAN. |
Tunnel Source |
Note Available only for a hub when the selected technology is IPsec/GRE or DMVPN. Specifies the tunnel source address to be used by the GRE or DMVPN tunnel on the spoke side. You can select one of the following options: •Override Unique Tunnel Source per Tunnel Interface—If you have enabled the setting to use a unique tunnel source per tunnel interface in the GRE Modes > Tunnel Parameters tab, this check box is available. Click this check box to specify a different tunnel source for the selected device. •Outside VLAN/External Port (When CCA/VRF is Enabled)—When the Use Crypto Connect Alternate check box is selected, this radio button is available. When selected, specifies the outside VLAN/external port as the tunnel source. •Inside VLAN—When selected, uses the interface configured for the inside VLAN as the tunnel source. •VPN Interface—When selected, uses the selected VPN interface as the tunnel source address. •Interface—To use any interface as the tunnel source address, not necessarily a VPN interface, enter the interface in the field provided or click Select to display an Object Selectors, page F-205. |
Local Peer IPSec Termination |
Define the IPSec termination point of the VPN interface on the local router: •Inside VLAN—Click this radio button to use interface configured as the inside VLAN. •IP Address—Click this radio button and enter the IP address of the VPN interface on the local router. Note If you select a tunnel source as the VPN interface, it is likely that the VPN interface has a dynamically assigned IP address. |
Enable Failover Blade |
When selected, enables you to configure a failover VPNSM or VPNSPA/VSPA blade for intra-chassis high availability. Note A VPNSM and VPNSPA/VSPA blade cannot be used on the same device as primary and failover blades. Specify the failover blade, as follows: •Slot—From the list of available slots, select the number that identifies where the VPNSM blade or VPNSPA/VSPA blade is located. •Subslot—If you are configuring a VPNSPA/VSPA, select the number of the subslot (0 or 1) on which the failover VPN SPA blade is installed. Note If you are configuring a VPNSM, select the blank option. |
Use the Protected Networks tab on the Edit Endpoints dialog box to edit the protected networks that are defined on a selected device in the Endpoints table.
You can specify the protected networks as interface roles whose naming patterns match the internal VPN interface type of the device, as network objects containing one or more network or host IP addresses, interfaces, or other network objects, or as access control lists (if Regular IPsec is the assigned technology).
For more information, see:
•Understanding Interface Role Objects, page 8-33
•Understanding Network/Host Objects, page 8-65
•Creating Access Control List Objects, page 8-23
Navigation Path
You can access the Protected Networks tab from the Edit Endpoints dialog box. Open the Edit Endpoints Dialog Box, then click the Protected Networks tab.
Related Topics
•Defining the Endpoints and Protected Networks, page 9-20
Field Reference
|
|
---|---|
Enable the Protected Networks Changes on All Selected Peers |
Available if you selected more than one device for editing in the Endpoints page. When selected, applies any changes you make in the Protected Networks tab to all the selected devices. |
Available Protected Networks |
A hierarchy of all available protected networks, including the interface roles whose naming pattern may match the internal VPN interface type of the device. If Regular IPsec is the assigned technology, access control lists (ACLs) are also included in the list of available protected networks. Note In a hub-and-spoke VPN topology in which Regular IPsec is the assigned technology, when an ACL object is used to define the protected network on a spoke, Security Manager mirrors the spoke's ACL object on the hub to the matching crypto map entry. Select the interface role(s), protected networks, and/or access control lists that you want to define for the selected device, then click >>. |
Selected Protected Networks |
The protected networks and interface roles you selected for the device. Note You can reorder the selected protected networks/interface roles in the list by selecting them (one at a time), then clicking the Move Up or Move Down button, as required. |
>> button |
Moves protected networks from the available networks list to the selected networks list. |
<< button |
Removes protected networks from the selected list. |
Create button |
If the required interface roles, protected networks, or access control lists do not appear in the Available Protected Networks list, click Create and select the required option to create an interface role, protected network, or access control list. Note The Access Control List option is only available if the assigned technology is Regular IPsec. If you select the Interface Role option, the Interface Role Editor page opens in which you can create an interface role object. For more information, see Creating Interface Role Objects, page 8-34. If you select the Protected Network option, the Network Editor page opens in which you can create a network object. For more information, see Creating Network/Host Objects, page 8-66. If you select the Access Control List option, the Access Lists Editor page opens in which you can create an access control list object. For more information, see Creating Access Control List Objects, page 8-23. |
Note The FWSM tab is only available in a hub-and-spoke VPN topology, when the selected hub is a Catalyst 6500/7600 device.
Use the FWSM tab on the Edit Endpoints dialog box to define the settings that enable you to connect between a Firewall Services Module (FWSM) and an IPsec VPN Services Module (VPNSM) or VPNSPA/VSPA, that is already configured on a Catalyst 6500/7600 device.
Note Before defining the FWSM settings, you must import your Catalyst 6500/7600 device to the Security Manager inventory. Then open Cisco Catalyst Device Manager (Cisco CDM), and discover the FWSM configurations on the device, and assign a VLAN that will serve as the inside interface to the FWSM. For details, see Configuring a Firewall Services Module (FWSM) Interface with VPNSM or VPNSPA/VSPA, page 9-33.
Navigation Path
Open the Edit Endpoints Dialog Box in the Create VPN wizard, then click the FWSM tab.
Note Make sure you selected a Catalyst 6500/7600 device in the table on the Endpoints Page (or tab), before opening the Edit Endpoints dialog box.
Related Topics
•Using the Create VPN Wizard, page 9-14
Field Reference
|
|
---|---|
Enable FWSM Settings |
When selected, enables you to configure the connection between the Firewall Services Module (FWSM) and the VPN Services Module (VPNSM) or VPN SPA on the selected Catalyst 6500/7600 device. |
FWSM Inside VLAN |
The VLAN which serves as the inside interface to the Firewall Services Module (FWSM). If required, click Select to open a dialog box that lists all available interfaces, and sets of interfaces defined by interface roles, and in which you can make your selection, or create interface role objects. |
FWSM Blade |
From the list of available blades, select the blade number to which the selected FWSM inside VLAN interface is connected. |
Security Context |
If the selected FWSM inside VLAN is part of a security context, specify its name in this field. The name is case-sensitive. You can partition an FWSM into multiple virtual firewalls, known as security contexts. A security context is an independent virtual firewall that has its own security policy, interfaces, and administrators. You can define security contexts when you import a Catalyst 6500/7600 device into the Security Manager inventory. For more information, see Security Contexts Page, page K-198. |
Use the VRF-Aware IPsec tab on the Edit Endpoints dialog box to configure a VRF-Aware IPsec policy on a hub in your hub-and-spoke VPN topology. When you select the row in the Endpoints table that contains the required hub device (the IPsec Aggregator), and click Edit, the VRF Aware IPsec tab opens. You can configure VRF-Aware IPsec as a one-box or two-box solution.
Note In a VPN topology with two hubs, you must configure VRF-Aware IPsec on both devices.
You cannot configure VRF-Aware IPsec on a device that belongs to another VPN topology in which VRF-Aware IPsec is not configured.
Deployment may fail if the IPsec Aggregator is configured with the same keyring CLI command as the existing preshared key (keyring) command, and is not referenced by any other command. In this case, Security Manager does not use the VRF keyring CLI, but generates the keyring with a different name, causing deployment to fail. You must manually remove the preshared key keyring command through the CLI, before you can deploy the configuration.
For more information about creating or editing a VRF-Aware IPsec policy, see Understanding VRF-Aware IPsec, page 9-34.
Navigation Path
You can access the VRF-Aware IPsec tab from the Edit Endpoints dialog box. Open the Edit Endpoints Dialog Box, then click the VRF-Aware IPsec tab.
Note Make sure you selected a hub device in the table on the Endpoints Page (or tab), before opening the Edit Endpoints dialog box.
Related Topics
•Configuring VRF-Aware IPsec Settings, page 9-38
•Defining the Endpoints and Protected Networks, page 9-20
Field Reference
|
|
---|---|
Enable the VRF Settings Changes on All Selected Peers |
Available if you selected more than one device for editing in the Endpoints page. When selected, applies any changes you make in the VRF Settings tab to all the selected devices. |
Enable VRF Settings |
When selected, enables the configuration of VRF settings on the selected hub for the selected hub-and-spoke topology. Note To remove VRF settings that were defined for the VPN topology, deselect this check box. |
1-Box (IPsec Aggregator + MPLS PE) |
When selected, enables you to configure a one-box VRF solution. In the one-box solution, one device serves as the Provider Edge (PE) router that does the MPLS tagging of the packets in addition to IPsec encryption and decryption from the Customer Edge (CE) devices. For more information, see VRF-Aware IPsec One-Box Solution, page 9-35. |
2-Box (IPsec Aggregator Only) |
When selected (the default), enables you to configure a two-box VRF solution. In the two-box solution, the PE device does just the MPLS tagging, while the IPsec Aggregator device does the IPsec encryption and decryption from the CEs. For more information, see VRF-Aware IPsec Two-Box Solution, page 9-36. |
VRF Name |
The name of the VRF routing table on the IPsec Aggregator. The VRF name is case-sensitive. |
Route Distinguisher |
The unique identifier of the VRF routing table on the IPsec Aggregator. This unique route distinguisher maintains the routing separation for each VPN across the MPLS core to the other PE routers. The identifier can be in either of the following formats: •IP address:X (where X is in the range 0- 2147483647). •N:X (where N is in the range 0-65535, and X is in the range 0- 2147483647). Note You cannot override the RD identifier after deploying the VRF configuration to your device. To modify the RD identifier after deployment, you must manually remove it using the device CLI, and then deploy again. |
Interface Towards Provider Edge |
Available only when a 2-Box solution is selected. Specify the VRF forwarding interface on the IPsec Aggregator towards the PE device. Note If the IPsec Aggregator (hub) is a Catalyst VPN service module, you must specify a VLAN. Interfaces and VLANs are predefined interface role objects. If required, you can click Select to open a dialog box that lists all available interfaces, and sets of interfaces defined by interface roles, in which you can make your selection, or create interface role objects. |
Routing Protocol |
Available only when a 2-Box solution is selected. Select the routing protocol to be used between the IPsec Aggregator and the PE. If the routing protocol used for the secured IGP differs from the routing protocol between the IPsec Aggregator and the PE, select the routing protocol to use for redistributing the routing to the secured IGP. The options are BGP, EIGRP, OSPF, RIPv2, or Static route. The default is BGP. For information about protocols, see Chapter 13, "Managing Routers". |
AS Number |
Available only when a 2-Box solution is selected. Enter the number that will be used to identify the autonomous system (AS) area between the IPsec Aggregator and the PE. If the routing protocol used for the secured IGP differs from the routing protocol between the IPsec Aggregator and the PE, enter an AS number that will be used to identify the secured IGP into which the routing will be redistributed from the IPsec Aggregator and the PE. This is relevant only when IPsec/GRE or DMVPN are applied. The AS number must be within the range 1-65535. |
Process Number |
Available only if the 2-Box radio button is selected, and if the selected routing protocol is OSPF. The routing process ID number that will be used to identify the secured IGP. The range is 1-65535. |
OSPF Area ID |
Available only if the 2-Box radio button is selected, and if the selected routing protocol is OSPF. The ID number of the area in which the packet belongs. You can enter any number from 0-4294967295. Note All OSPF packets are associated with a single area, so all devices must have the same area ID number. |
Next Hop IP Address |
Available only when a 2-Box solution is selected with static routing. Specify the IP address of the interface that is connected to the IPsec Aggregator. |
Redistribute Static Route |
Available only when a 2-Box solution is selected with any routing protocol other than Static route. When selected, enables static routes to be advertised in the routing protocol configured on the IPsec Aggregator towards the PE device. |
Use the Dial Backup Settings dialog box to define optional settings for configuring a dial backup policy for your site-to-site VPN. These settings are available for Regular IPsec, IPsec/GRE, GRE Dynamic IP, or Easy VPN technologies.
Mandatory settings for dial backup are configured in the VPN Interface tab on the Edit Endpoints dialog box. See VPN Interface Tab.
Note You must configure the dialer interface settings before dial backup can work properly. For more information, see Dialer Interfaces on Cisco IOS Routers, page 13-22.
Navigation Path
Open the VPN Interface Tab from the Edit Endpoints dialog box, select the Enable check box in the Backup area, and click Advanced.
Related Topics
•Defining the Endpoints and Protected Networks, page 9-20
•Configuring Dial Backup, page 9-29
•Understanding Easy VPN, page 9-71
Field Reference
Use the High Availability page to define a group of hubs as an HA group.
Note When editing a VPN topology, the High Availability tab is used. The elements of the tab (except for the buttons) are identical to those that appear on the High Availability page. For more information, see Editing a VPN Topology, page 9-27.
High Availability may be configured in a hub-and-spoke VPN topology when Regular IPsec or Easy VPN is the assigned technology.
For more information about the prerequisites for configuring high availability, see the section on Prerequisites for Successful High Availability Configuration in Understanding High Availability, page 9-39.
Navigation Path
•When creating a hub-and-spoke VPN topology, open the Create VPN Wizard, then click Next on the Endpoints page.
•When editing a hub-and-spoke or Easy VPN topology, click the High Availability tab in the Edit VPN dialog box.
Related Topics
•Understanding High Availability, page 9-39
•Configuring High Availability in Your VPN Topology, page 9-41
•Understanding Easy VPN, page 9-71
Field Reference
|
|
---|---|
Enable |
When selected, enables you to configure high availability on a group of hubs. When deselected, enables you to remove an HA group that was defined for the VPN topology. |
Inside Virtual IP |
The IP address that is shared by the hubs in the HA group and represents the inside interface of the HA group. The virtual IP address must be on the same subnet as the inside interfaces of the hubs in the HA group, but must not be identical to the IP address of any of these interfaces. You can choose the required IP address by clicking Select. The Network/Hosts selector opens, in which you can select a network from which the IP address is allocated. Note If there is an existing standby group on the device, make sure that the IP address you provide is different to the virtual IP address already configured on the device. |
Inside Mask |
The subnet mask for the inside virtual IP address. |
VPN Virtual IP |
The IP address that is shared by the hubs in the HA group and represents the VPN interface of the HA group. This IP address serves as the hub endpoint of the VPN tunnel. You can choose the required IP address by clicking Select. The Network/Hosts selector opens, in which you can select a host from which the IP address is allocated. Note If there is an existing standby group on the device, make sure that the IP address you provide is different to the virtual IP address already configured on the device. |
VPN Mask |
The subnet mask for the VPN virtual IP address. |
Hello Interval |
The duration in seconds (within the range of 1-254) between each hello message sent by a hub to the other hubs in the group to indicate status and priority. The default is 5 seconds. |
Hold Time |
The duration in seconds (within the range of 2-255) that a standby hub will wait to receive a hello message from the active hub before concluding that the hub is down. The default is 15 seconds. |
Standby Group Number (Inside) |
The standby number of the inside hub interface that matches the internal virtual IP subnet for the hubs in the HA group. The number must be within the range of 0-255. The default is 1. |
Standby Group Number (Outside) |
The standby number of the outside hub interface that matches the external virtual IP subnet for the hubs in the HA group. The number must be within the range of 0-255. The default is 2. Note The outside standby group number must be different to the inside standby group number. |
Stateful Failover |
When selected, enables SSO for stateful failover. Note In an Easy VPN topology, this check box appears selected and disabled, as stateful failover must always be configured. You can only configure stateful failover on an HA group that contains two hubs that are Cisco IOS routers. This check box is disabled if the HA group contains more than two hubs. Note When deselected in a Regular IPsec topology, stateless failover is configured on the HA group. Stateless failover will also be configured if the HA group contains more than two hubs. Stateless failover can be configured on Cisco IOS routers or Catalyst 6500/7600 devices. For more information, see Understanding High Availability, page 9-39. |
Use the GET VPN Peers page to define the peers to be used by the VPN topology.
Navigation Path
•When creating a VPN topology, open the Create VPN Wizard.
•When editing a VPN topology, open the Site-to-Site VPN Manager Window, then right-click a VPN topology in the VPNs selector, or click the GET VPN Peers tab in the Edit VPN dialog box.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
|
|
---|---|
Key Servers Table |
The device name, identity, priority, and registration interface are shown. For detailed information about these attributes, see Edit Key Server Dialog Box. •To add a key server to the table, click the Add button. •To edit a key server, select it and click the Edit button. •To delete a key server, select it and click the Delete button. •To move a key server, select it and click the up or down arrow button. Using the arrow keys, you can establish the order of cooperative key servers (configured for redundancy). Group members register with the first key server in the list. If the first key server cannot be reached, they will register with the second key server, and so on. For more information about key server redundancy, see Redundancy Using Cooperative Key Servers, page 9-85. •To show specific device identity information, select Interface Roles Only or Matching Interfaces in the Show field. |
Group Members Table |
The device name, GET-enabled interface, and local security policy are shown. For detailed information about these attributes, see Edit Group Member Dialog Box. •To add a group member to the table, click the Add button. •To edit a group member, select it and click the Edit button. •To delete a group member, select it and click the Delete button. •To show specific device identity information, select Interface Roles Only or Matching Interfaces in the Show field. |
Use the Add Key Server and Add Group Member dialog boxes to select key servers or group members to be used in the VPN topology. Navigate to the desired device and click the check box next to it. Then, click OK.
Navigation Path
•Go to the GET VPN Peers Page, then click the Add button beneath the Key Server or Group Member table.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Use the Edit Key Servers dialog box to change the attributes defined for a key server.
Navigation Path
•From the Key Servers Page, click the Add button.
•Go to the GET VPN Peers Page, select a key server and click the Edit button.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
Use the Edit Group Members dialog box to change the attributes defined for a group member.
Navigation Path
•Go to the GET VPN Peers Page, select a group member and click the Edit button.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
|
|
---|---|
GET-Enabled Interface |
VPN-enabled outside interface to the provider edge (PE). Traffic originating or terminating on this interface is evaluated for encryption or decryption, as appropriate. You can configure multiple interfaces. |
Interface to be used as local address |
Local address interface. If there are more than one GET-enabled interface, you must define a local address interface. Enter an interface name or click Select to display an Object Selectors, page F-205. |
Security Policy |
Local group member security ACL used to deny some group member-specific traffic over and above the security ACL downloaded from the key server. |
Override Key Servers |
Click the check box to specify key servers to be used by the selected group member instead of the key servers designated for the GET VPN topology. This setting can be used to select a subset of the key servers defined at the GET VPN topology level to be used by the selected group member. It can also be used to change the order of the overridden key servers for the selected group member. |
Use the VPN Defaults page of the Create VPN wizard to view and select the default site-to-site VPN policies that will be assigned to the VPN topology you are creating. The page displays all the available mandatory and optional policies that can be assigned to your VPN topology, according to the selected IPsec technology.
Note When you click Finish on this page, the default policies are assigned to the new VPN topology. The policies you select will be applied only to the specific VPN topology you are creating. If you want the selected policies to be applied to all future VPN topologies that are created, you must change the policy defaults selection on the Administration tool's VPN Policy Defaults page.
For more information, see Understanding VPN Default Policies, page 9-8.
Navigation Path
•Open the Create VPN Wizard, then click Next on the Endpoints page, or High Availability page (if you are configuring a hub-and-spoke VPN topology).
Related Topics
•Understanding IPsec Technologies and Policies, page 9-5
•Understanding VPN Default Policies, page 9-8
•Assigning Default Policies to Your VPN Topology, page 9-24
Field Reference
|
|
---|---|
Policy type |
Lists the VPN policy types that can be assigned to your VPN topology. For each policy type, select the default VPN policy you want to assign to your VPN topology. You can accept the Factory Default policy (available for a mandatory policy only) or select a shared VPN policy that was created (and submitted or approved, depending on the workflow mode) using Security Manager. Note If you want to assign a default policy that is not provided in the list, you can change the policy defaults selection in the Administration tool's VPN Policy Defaults page. The policy will then be available for assignment to all future VPN topologies that are created. For more information, see VPN Policy Defaults Page, page A-41. Note If you try to select a default policy that is currently locked by another user, a message is displayed warning you of a lock problem. To bypass the lock, select a different policy or cancel the VPN topology creation until the lock is approved. For more information, see Understanding Locking, page 6-7. |
View Content button |
Opens a page that displays the contents of the selected VPN policy. Note If you make any changes on this page, you cannot save them. |
You can access site-to-site VPN policies by selecting Tools > Site-To-Site VPN Manager, or clicking the Site-To-Site VPN Manager button on the toolbar, and then selecting the required policy in the Policies selector of the Site-to-Site VPN window.
You can also access site-to-site VPN policies from Device view or Policy view.
In Device view, you can see the VPN topology (topologies) to which each device in the CSM inventory belongs, and if necessary, change its assignment to or from a VPN topology. For more information, see VPN Topologies Device View Page.
For more information about accessing site-to-site VPN policies from Policy view, see Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
These topics describe the pages of the policies that you can assign to your VPN topologies:
•Client Connection Characteristics Page
•Tunnel Group Policy (PIX 7.0/ASA) Page
•IKE Proposal Page for GET VPN
•Public Key Infrastructure Page
•Global Settings for GET VPN Page
Use the Client Connection Characteristics page to specify how traffic will be routed in the VPN and how the VPN tunnel will be established. You configure these characteristics on a remote client, which may be a PIX Firewall, a Cisco 800-3800 Series router, or an ASA 5505 running OS version 7.2(1) or later.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select an Easy VPN topology in the VPNs selector, then select Client Connection Characteristics in the Policies selector.
•You can also open the Client Connection Characteristics page from Policy view. For more information, see Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Understanding Easy VPN, page 9-71
•Configuring Client Connection Characteristics for Easy VPN, page 9-79
•Creating Access Control List Objects, page 8-23
Field Reference
|
|
---|---|
Mode |
Select the required configuration mode for your remote device, as follows: •Client—Specifies that all traffic from the remote client's inside network will undergo Port Address Translation (PAT) to a single IP address which was assigned for the device by the head end server at connect time. •Network Extension—Specifies that PCs and other hosts at the client end of the VPN tunnel should be given IP addresses that are fully routable and reachable by destination network. PAT is not used, allowing the client PCs and hosts to have direct access to the PCs and hosts at the destination network. •Network Extension Plus—An enhancement to Network Extension mode, that enables an IP address that is received via mode configuration to be automatically assigned to an available loopback interface. The IPsec SAs for this IP address are automatically created by the Easy VPN client. The IP address is typically used for troubleshooting (using ping, Telnet, and Secure Shell). Note Network Extension Plus mode can be configured only on IOS routers. If the selected client device is a PIX 6.3 or ASA 5505 running OS version 7.2(1), Network Extension mode will be configured. For more information, see Configuring Client Connection Characteristics for Easy VPN, page 9-79. |
Xauth Credentials Source |
Select how you want to enter the Xauth credentials for user authentication when you establish a VPN connection with the server, as follows: •Device Stored Credentials (default)—The username and password are saved on the device itself in the device's configuration file to be used each time the tunnel is established. •Interactive Entered Credentials—Enables you to manually enter the username and password each time Xauth is requested, in a web browser window or from the command line interface. For more information, see Configuring Client Connection Characteristics for Easy VPN, page 9-79. |
Xauth Credentials |
Available only if you selected Device Stored Credentials as the Xauth Credentials Source. Displays the default Xauth credentials. Xauth Credentials are predefined objects. If required, click Select to open the Credentials Selector in which you can select different Xauth credentials, and from which you can create or edit Credential objects. Note If you want to configure different Xauth credentials on your remote client, you must override the default one by clicking the Allow Value Override per Device check box in the Add/Edit Xauth Credentials dialog box. For more information, see Creating Credential Objects, page 8-30. |
User Authentication Method (IOS) |
Available only if the remote device is an IOS router, and if you selected the Interactive Entered Credentials option for the Xauth credentials source. Select one of these ways to enter the Xauth username and password interactively each time Xauth authentication is requested: •Web Browser (default)—Manually in a web browser window (http page). •Router Console—Manually from the command line interface (CLI). |
Tunnel Activation (IOS) |
If the remote device is an IOS router, and if you selected the Device Stored Credentials option for the Xauth password source, you must select a tunnel activation method, as follows: •Auto (default)—The Easy VPN tunnel is established automatically when the Easy VPN configuration is delivered to the device configuration file. If the tunnel times out or fails, the tunnel automatically reconnects and retries indefinitely. •Traffic Triggered Activation—The Easy VPN tunnel is established whenever outbound local (LAN side) traffic is detected. When using this option, you must specify the Access Control List (ACL) that defines the "interesting" traffic. Traffic Triggered Activation is recommended for use when Easy VPN dial backup is configured so that backup is activated only when there is traffic to send across the tunnel. Note Manual tunnel activation is configured implicitly when you select to configure the Xauth password interactively. |
ACL (IOS) |
If you selected the Traffic Triggered Activation option for Tunnel Activation, you must configure an ACL-triggered tunnel by specifying the Access Control List (ACL) that defines the "interesting" traffic. Click Select to open the Access Control Lists Selector from which you can select the required ACL, or create or edit an ACL object. |
Use the Tunnel Group Policy (PIX 7.0/ASA) page to create or edit tunnel group policies on your Easy VPN server. An Easy VPN tunnel group policy can be configured only on PIX Firewalls running version 7.0, and ASA devices.
Note You can also configure tunnel group policies in remote access VPNs.
The following tabs are available on the Tunnel Group Policy (PIX 7.0/ASA) page:
•Tunnel Group Policy > General Tab
•Tunnel Group Policy > IPsec Tab
•Tunnel Group Policy > Advanced Tab
•Tunnel Group Policy > Client VPN Software Update Tab
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select Tunnel Group Policy (PIX 7.0/ASA) in the Policies selector.
•You can also open the Tunnel Group Policy (PIX 7.0/ASA) page from Policy view. For more information, see Working with Site-to-Site VPN Policies, page 9-43.
Related Topics
•Configuring a Tunnel Group Policy for Easy VPN, page 9-78
•Understanding Easy VPN, page 9-71
Use the General tab of the Tunnel Group Policy (PIX 7.0/ASA) page to specify the global AAA settings for your tunnel group. On this tab you can also select the method (or methods) of address assignment to use.
Navigation Path
The General tab appears when you open the Tunnel Group Policy (PIX 7.0/ASA) Page. You can also open it by clicking the General tab from any other tab on the Tunnel Group Policy (PIX 7.0/ASA) page.
Related Topics
•Tunnel Group Policy (PIX 7.0/ASA) Page
•Configuring a Tunnel Group Policy for Easy VPN, page 9-78
•Creating ASA User Group Objects, page 8-28
•Understanding AAA Server and Server Group Objects, page 8-15
•Creating Network/Host Objects, page 8-66
Field Reference
|
|
---|---|
Tunnel Group Name |
The name of the tunnel group that contains the policies for this IPsec connection. |
Group Policy |
The group policy to be applied to the tunnel group. A group policy is a collection of user-oriented attribute/value pairs stored either internally on the device or externally on a RADIUS/LDAP server. Click Select to open a dialog box that lists all available ASA group policies, and in which you can create an ASA group policy object. |
AAA |
|
Authentication Server Group |
The name of the authentication server group (LOCAL if the tunnel group is configured on the local device). You can click Select to open a dialog box that lists all available AAA server groups, and in which you can create AAA server group objects. Note If you want to set the authentication server group per interface, click the Advanced tab. |
User LOCAL if Server Group fails |
Available if you selected LOCAL for the authentication server group. When selected, enables fallback to the local database for authentication if the selected authentication server group fails. |
Authorization Server Group |
The name of the authorization server group (LOCAL if the tunnel group is configured on the local device). You can click Select to open a dialog box that lists all available AAA server groups, and in which you can create AAA server group objects. |
User must exist in the authorization database to connect |
When selected, specifies that the username of the remote client must exist in the database so a successful connection can be established. If the username does not exist in the authorization database, then the connection is denied. |
Accounting Server Group |
The name of the accounting server group (LOCAL if the tunnel group is configured on the local device). You can click Select to open a dialog box that lists all available AAA server groups, and in which you can create AAA server group objects. |
Strip Realm from Username |
When selected, removes the realm from the username before passing the username on to the AAA server. A realm is an administrative domain. Enabling this option allows the authentication to be based on the username alone. You must select this check box if your server cannot parse delimiters. |
Strip Group from Username |
When selected, removes the group name from the username before passing the username on to the AAA server. Enabling this option allows the authentication to be based on the username alone. You must select this check box if your server cannot parse delimiters. |
Client Address Assignment |
|
DHCP Server |
The DHCP servers to be used for client address assignments. The server uses the DHCP servers in the order listed. You can add up to 10 servers. A default DHCP server is displayed. DHCP servers are predefined network objects. If you want to use a different DHCP server, or select additional DHCP servers, click Select to open the Network/Hosts selector that lists all available network hosts, and in which you can create network host objects. |
Address Pools |
The address pools from which IP addresses will be assigned. The server uses these pools in the order listed. If all addresses in the first pool have been assigned, it uses the next pool, and so on. You can specify up to 6 pools. A default address pool is displayed. Address pools are predefined network objects. If you want to use a different address pool, or select additional address pools, click Select to open the Network/Hosts selector that lists all available network hosts, and in which you can create network host objects. |
Use the IPsec tab of the Tunnel Group Policy (PIX 7.0/ASA) page to specify IPsec and IKE parameters for the tunnel group policy.
Navigation Path
Open the Tunnel Group Policy (PIX 7.0/ASA) Page, then click the IPsec tab. You can also open the IPsec tab by clicking it from any other tab on the Tunnel Group Policy (PIX 7.0/ASA) page.
Related Topics
•Tunnel Group Policy (PIX 7.0/ASA) Page
•Configuring a Tunnel Group Policy for Easy VPN, page 9-78
Field Reference
|
|
---|---|
Preshared Key |
The value of the preshared key for the tunnel group. The maximum length of a preshared key is 127 characters. |
Trustpoint Name |
The trustpoint name if any trustpoints are configured. A trustpoint represents a CA/identity pair and contains the identity of the CA, CA-specific configuration parameters, and an association with one enrolled identity certificate. |
IKE Peer ID Validation |
Select whether IKE peer ID validation is ignored, required, or checked only if supported by a certificate. During IKE negotiations, peers must identify themselves to one another. |
Enable Sending Certificate Chain |
When selected, enables the sending of the certificate chain for authorization. A certificate chain includes the root CA certificate, identity certificate, and key pair. |
Enable Password Update with RADIUS Authentication |
When selected, enables passwords to be updated with the RADIUS authentication protocol. For more information, see Supported AAA Server Types, page 8-16. |
|
|
Monitor Keepalive |
When selected, enables you to configure IKE keepalive as the default failover and routing mechanism. For more information, see Understanding ISAKMP/IPsec Settings, page 9-52. |
Confidence Interval |
The number of seconds that a device waits between sending IKE keepalive packets. |
Retry Interval |
The number of seconds a device waits between attempts to establish an IKE connection with the remote peer. The default is 2 seconds. |
|
|
Use Entire DN as the Username |
Select to use the entire Distinguished Name (DN) as the identifier for the username. A distinguished name (DN) is a unique identification, made up of individual fields, that can be used as the identifier when matching users to a tunnel group. DN rules are used for enhanced certificate authentication on PIX Firewalls and ASA devices. |
Specify Individual DN fields as the Username |
Select to use individual DN fields as the username when matching users to the tunnel group. A DN certificate is made up of different field identifiers to match users to tunnel groups. |
Primary DN field |
Available if you selected to use individual DN fields as the username. Select the primary DN field identifier to be used for identification from the list. |
Secondary DN field |
Available if you selected to use individual DN fields as the username. Select the secondary DN field identifier to be used for identification. Select None if no secondary field identifier is required. |
Use the Advanced tab of the PIX7.0/ASA Tunnel Group Policy page to specify interface-specific information for your tunnel group.
Navigation Path
Open the Tunnel Group Policy (PIX 7.0/ASA) Page, then click the Advanced tab. You can also open the Advanced tab by clicking it from any other tab on the Tunnel Group Policy (PIX 7.0/ASA) page.
Related Topics
•Tunnel Group Policy (PIX 7.0/ASA) Page
•Configuring a Tunnel Group Policy for Easy VPN, page 9-78
•Creating Interface Role Objects, page 8-34
•Creating AAA Server Group Objects, page 8-22
•Creating Network/Host Objects, page 8-66
Field Reference
Use the Client VPN Software Update tab of the PIX7.0/ASA Tunnel Group Policy page to view or edit the client type, VPN Client revisions, and image URL for each client VPN software package installed.
Navigation Path
Open the Tunnel Group Policy (PIX 7.0/ASA) Page, then click the Client VPN Software Update tab. You can also open the Client VPN Software Update tab by clicking it from any other tab on the Tunnel Group Policy (PIX 7.0/ASA) page.
Related Topics
•Tunnel Group Policy (PIX 7.0/ASA) Page
•Configuring a Tunnel Group Policy for Easy VPN, page 9-78
Field Reference
Use the Easy VPN IPsec Proposal page to create or edit the IPsec policy definitions for your Easy VPN server, including the configuration of Dynamic VTI. For more information, see Configuring an IPsec Proposal for Easy VPN, page 9-75.
Note This topic describes the IPsec Proposal page when the assigned technology is Easy VPN. For a description of the IPsec Proposal page when the assigned technology is Regular IPsec, IPsec/GRE, GRE Dynamic IP, or DMVPN, see IPsec Proposal Page.
The following tabs are available on the Easy VPN IPsec Proposal page:
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select Easy VPN IPsec Proposal in the Policies selector.
•You can also open the Easy VPN IPsec Proposal page from Policy view. For more information, see Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Use the Easy VPN IPsec Proposal tab to create or edit the IPsec policy definitions for your Easy VPN server.
Navigation Path
The Easy VPN IPsec Proposal tab appears when you open the Easy VPN IPsec Proposal Page.
Related Topics
•Understanding Easy VPN, page 9-71
•Configuring an IPsec Proposal for Easy VPN, page 9-75
•Understanding AAA Server and Server Group Objects, page 8-15
Field Reference
|
|
---|---|
Transform Sets |
The transform set(s) to be used for your tunnel policy. Transform sets specify which authentication and encryption algorithms will be used to secure the traffic in the tunnel. You can select up to six transform sets. Transform sets may use only tunnel mode IPsec operation. Note If more than one of your selected transform sets is supported by both peers, the transform set that provides the highest security will be used. A default transform set is displayed. If you want to use a different transform set, or select additional transform sets, click Select to open a dialog box that lists all available transform sets, and in which you can create transform set objects. For more information, see Creating IPSec Transform Set Objects, page 8-36. For more information, see About Transform Sets, page 9-49. |
Reverse Route |
Supported on ASA devices, PIX 7.0 devices, and Cisco IOS routers except 7600 devices. Reverse Route Injection (RRI) enables static routes to be automatically inserted into the routing process for those networks and hosts protected by a remote tunnel endpoint. For more information, see About Reverse Route Injection, page 9-50. Select one of the following options to configure RRI on the crypto map: •None—To disable the configuration of RRI on the crypto map. •Standard—To create routes based on the destination information defined in the crypto map access control list (ACL). This is the default option. •Remote Peer—To create two routes, one for the remote endpoint and one for route recursion to the remote endpoint via the interface to which the crypto map is applied. •Remote Peer IP—To specify an interface or address as the explicit next hop to the remote VPN device. Then, click Select to open the Network/Hosts Selector, from which you can select the IP address of the remote peer to be used as the next hop. Note You can select the Allow Value Override per Device check box to override the default route, if required. |
Enable Network Address Translation |
Supported on PIX 7.0 and ASA devices. When selected, enables you to configure Network Address Translation (NAT) on a device. NAT enables devices that use internal IP addresses to send and receive data through the Internet. Private NAT addresses are converted to globally routable IP addresses when they try to access data on the Internet. For more information, see Understanding NAT, page 9-53. |
Group Policy Lookup/AAA Authorization Method |
Supported on Cisco IOS routers only. The AAA authorization method list that will be used to define the order in which the group policies are searched. Group policies can be configured on both the local server or on an external AAA server. You can click Select to open a dialog box that lists all available AAA group servers, and in which you can create AAA group server objects. |
User Authentication (Xauth)/AAA Authentication Method |
Supported on Cisco IOS routers only. The AAA or Xauth user authentication method used to define the order in which user accounts are searched. Xauth allows all Cisco IOS software AAA authentication methods to perform user authentication in a separate phase after the IKE authentication phase 1 exchange. The AAA configuration list-name must match the Xauth configuration list-name for user authentication to occur. For more information about defining user accounts, see Defining Accounts and Credential Policies, page 13-48. You can click Select to open a dialog box that lists all available AAA group servers from which you can make your selection, and in which you can create additional AAA group server objects. |
Use the Dynamic VTI tab to configure a dynamic virtual interface on a device in a hub-and-spoke Easy VPN topology. For more information, see the section on Easy VPN with Dynamic Virtual Tunnel Interfaces.
Note Dynamic VTI can be configured only on IOS routers running IOS version 12.4(2)T and later, except 7600 devices.
Navigation Path
Open the Easy VPN IPsec Proposal Page, then click the Dynamic VTI tab.
Related Topics
•Understanding Easy VPN, page 9-71
•Configuring an IPsec Proposal for Easy VPN, page 9-75
Field Reference
Use the GRE Modes page to define the routing and tunnel parameters, that enable you to configure IPsec tunneling with GRE, GRE Dynamic IP, and DMVPN policies.
Table G-24 describes the elements on the GRE Modes page for configuring IPsec tunneling with GRE or GRE Dynamic IP.
Table G-25 describes the elements on the GRE Modes page for configuring DMVPN.
Note When configuring an IPsec/GRE, GRE Dynamic IP, or DMVPN routing policy, Security Manager adds a routing protocol to all the devices in the secured IGP, on deployment. If you want to maintain this secured IGP, you must create a router platform policy using the same routing protocol and autonomous system (or process ID) number as defined in the GRE Modes policy.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select GRE Modes in the Policies selector.
•You can also open the GRE Modes page from Policy view. For more information, see Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Understanding GRE Configuration for Dynamically Addressed Spokes, page 9-64
•Configuring GRE or GRE Dynamic IP Policies, page 9-65
•Understanding DMVPN, page 9-67
•Configuring DMVPN Policies, page 9-68
•Understanding IPsec Technologies and Policies, page 9-5
Table G-24 describes the elements on the GRE Modes page for configuring IPsec tunneling with GRE or GRE Dynamic IP.
|
|
---|---|
|
|
Routing Protocol |
Select the required dynamic routing protocol (EIGRP, OSPF, or RIPv2,) or static route to be used for GRE or GRE Dynamic IP. The default routing protocol is EIGRP. |
AS Number |
Available only if you selected the EIGRP routing protocol. The number that is used to identify the autonomous system (AS) area to which the EIGRP packet belongs. The range is 1-65535. The default is 110. An autonomous system (AS) is a collection of networks that share a common routing strategy. An AS can be divided into a number of areas, which are groups of contiguous networks and attached hosts. Routers with multiple interfaces can participate in multiple areas. An AS ID identifies the area to which the packet belongs. All EIGRP packets are associated with a single area, so all devices must have the same AS number. |
Process Number |
Available only if you selected the OSPF routing protocol. The routing process ID number that will be used to identify the secured IGP that Security Manager adds when configuring GRE. The range is between 1 and 65535. The default is 110. Security Manager adds an additional Interior Gateway Protocol (IGP) that is dedicated for IPsec and GRE secured communication. An IGP refers to a group of devices that receive routing updates from one another by means of a routing protocol. Each "routing group" is identified by the process number. For more information, see Understanding GRE, page 9-62. |
Hello Interval |
Available only if you selected the EIGRP routing protocol. The interval between hello packets sent on the interface, between 1 and 65535 seconds. The default is 5 seconds. |
Hold Time |
Available only if you selected the EIGRP routing protocol. The number of seconds the router will wait to receive a hello message before invalidating the connection. The range is between 1 and 65535. The default hold time is 15 seconds (three times the hello interval). |
Delay |
Available only if you selected the EIGRP routing protocol. The throughput delay for the primary route interface, in microseconds. The range of the tunnel delay time is 1-16777215. The default is 1000. |
Failover Delay |
Available only if you selected the EIGRP routing protocol. The throughput delay for the failover route interface, in microseconds. The range of the tunnel delay time is 1-16777215. The default is 1500. |
Bandwidth |
Available only if you selected the EIGRP routing protocol. The amount of bandwidth available to the primary route interface for the EIGRP packets. You should enter a value that gives priority to the primary route over other routes. You can enter a value in the range 1 to 10000000 kb. The default is 1000 kb. The amount of bandwidth available to the primary route interface for the EIGRP packets. You can enter a value in the range 1 to 10000000 kb. The default is 1000 kb. Note By default, the cost of sending a packet on an interface is calculated based on the bandwidth—the higher the bandwidth, the lower the cost. |
Failover Bandwidth |
Available only if you selected the EIGRP routing protocol. The amount of bandwidth available to the failover route interface for the EIGRP packets. Enter a value in the range 1 to 10000000 kb. The default is 1000 kb. |
Hub Network Area ID |
Available only if you selected the OSPF routing protocol. The ID number of the area in which the hub's protected networks will be advertised, including the tunnel subnet. You can specify any number. The default is 0. |
Spoke Protected Network Area ID |
Available only if you selected the OSPF routing protocol. The ID number of the area in which the remote protected networks will be advertised, including the tunnel subnet. You can specify any number. The default is 1. |
Authentication |
Available if you selected the OSPF or RIPv2 routing protocol. A string that specifies the OSPF or RIPv2 authentication key. The string can be up to eight characters long. |
Cost |
Available if you selected the OSPF or RIPv2 routing protocol. The cost of sending a packet on the primary route interface. If the selected protocol is OSPF, enter a value in the range 1-65535; the default is 100. If the selected protocol is RIPv2, enter a value in the range 1-15; the default is 1. |
Failover Cost |
Available if you selected the OSPF or RIPv2 routing protocol. The cost of sending a packet on the secondary (failover) route interface. You can enter a value in the range 1-65535 for OSPF (the default is 125), or in the range 1-15 for RIPv2 (the default is 2). |
Filter Dynamic Updates on Spokes |
When selected, enables the creation of a redistribution list that filters all dynamic routing updates on the spokes. This forces the spoke devices to advertise (populate on the hub device) only their own protected subnets and not other IP addresses. |
Tunnel Parameters Tab |
|
Tunnel IP |
Select the required option to specify the GRE or GRE Dynamic IP tunnel interface IP address. Note To view the new GRE tunnel and/or loopback interfaces in the Router Interfaces page, you must rediscover the device inventory details after successfully deploying the VPN to the device. For more information, see Basic Interface Settings on Cisco IOS Routers, page 13-13. •Use Physical Interface—When selected, uses the private IP address of the tunnel taken from the protected network. •Use Subnet—When selected, uses the tunnel IP address taken from an IP range. This is the default. Note In most cases, when you use a subnet to specify a GRE tunnel interface IP address, Security Manager creates a loopback interface on the device which is used for the tunnel IP address. If the device belongs to a VPN topology whose configurations were discovered by Security Manager, and you configure an IP address directly on the device's GRE tunnel, Security Manager keeps that configuration and does not create a loopback interface on the device. However, a loopback is always configured on a hub in a VPN topology; in a hub-and-spoke VPN topology with multiple hubs, a loopback interface is also configured on the spokes. •Use Loopback Interface—When selected, uses the tunnel IP address taken from an existing loopback interface. |
Configure Unique Tunnel Source for each Tunnel |
Available only if the assigned IPsec technology is GRE Standard. When enabled, each GRE tunnel interface in the VPN is assigned a unique tunnel source. In the Tunnel Source IP Range field, enter a subnet IP to be used as tunnel sources. Note When enabled, this feature is set for all GRE tunnel interfaces in the VPN. If you want to assign a specific tunnel source for an interface, use the Peers page (see Peers Page). |
Tunnel Source IP Range |
Available only if the assigned IPsec technology is GRE Dynamic IP. The private IP address including the unique subnet mask that supports the loopback for GRE. The GRE tunnel interface has an IP address (inside tunnel IP address) which is taken from a loopback interface that Security Manager creates specifically for this purpose. When a spoke has a dynamic IP address, there is no fixed GRE tunnel source address (to be used by the GRE tunnel on the spoke side) or destination address (to be used by the GRE tunnel on the hub side). Therefore, Security Manager creates additional loopback interfaces on the hub and the spoke to use as the GRE tunnel endpoints. You must specify a subnet from which Security Manager can allocate an IP address for the loopback interfaces. |
Enable IP Multicast |
When selected, enables multicast transmissions across your GRE tunnels. IP multicast delivers application source traffic to multiple receivers without burdening the source or the receivers, while using a minimum of network bandwidth. |
Rendezvous Point |
Only available if you selected the Enable IP Multicast check box. If required, you can enter the IP address of the interface that will serve as the rendezvous point (RP) for multicast transmission. Sources send their traffic to the RP. This traffic is then forwarded to receivers down a shared distribution tree. |
Table G-25 describes the elements on the GRE Modes page for configuring a DMVPN policy.
|
|
---|---|
|
|
Routing Protocol |
Select the required dynamic routing protocol, or static route, to be used in the DMVPN tunnel. Options include the EIGRP, OSPF, and RIPv2 dynamic routing protocols, and GRE static routes. On-Demand Routing (ODR) is also supported. On-Demand Routing is not a routing protocol. It can be used in a hub-and-spoke VPN topology when the spoke routers connect to no other router other than the hub. If you are running dynamic protocols, On-Demand Routing is not suitable for your network environment. For more information, see Understanding GRE, page 9-62. |
AS Number |
Available only if you selected the EIGRP routing protocol. The number that is used to identify the autonomous system (AS) area to which the EIGRP packet belongs. The range is 1-65535. The default is 110. An autonomous system (AS) is a collection of networks that share a common routing strategy. An AS can be divided into a number of areas, which are groups of contiguous networks and attached hosts. Routers with multiple interfaces can participate in multiple areas. An AS ID identifies the area to which the packet belongs. All EIGRP packets are associated with a single area, so all devices must have the same AS number. |
Process Number |
Available only if you selected the OSPF routing protocol. The routing process ID number that will be used to identify the secured IGP that Security Manager adds when configuring DMVPN. The valid range for either protocol is 1-65535. The default is 110. |
Hello Interval |
Available only if you selected the EIGRP routing protocol. The interval between hello packets sent on the interface, from 1 to 65535 seconds. The default is 5 seconds. |
Hold Time |
Available only if you selected the EIGRP routing protocol. The number of seconds the router will wait to receive a hello message before invalidating the connection. The range is 1-65535. The default hold time is 15 seconds (three times the hello interval) |
Delay |
Available only if you selected the EIGRP routing protocol. The throughput delay for the primary route interface, in microseconds. The range of the tunnel delay time is 1-16777215. The default is 1000. |
Hub Network Area ID |
Available only if you selected the OSPF routing protocol. The ID number of the area in which the hub's protected networks will be advertised, including the tunnel subnet. You can enter any number. The default is 0. |
Spoke Protected Network Area ID |
Available only if you selected the OSPF routing protocol. The ID number of the area in which the remote protected networks will be advertised, including the tunnel subnet. You can enter any number. The default is 1. |
Authentication |
A string that indicates the OSPF authentication key. The string can be up to eight characters long. |
Cost |
Available if you selected the OSPF or RIPv2 routing protocol. The cost of sending a packet on the primary route interface. If the selected protocol is OSPF, enter a value in the range 1-65535; the default is 100. If the selected protocol is RIPv2, enter a value in the range 1-15; the default is 1. |
Allow Direct Spoke to Spoke Connectivity |
When selected, enables direct communication between spokes, without going through the hub. Note With direct spoke-to-spoke communication, you must use the Main Mode Address option for preshared key negotiation. For more information, see Understanding Preshared Key Policies, page 9-56. |
Filter Dynamic Updates On Spokes |
Unavailable if you are using On-Demand Routing or a static route for your DMVPN tunnel. When selected, enables the creation of a redistribution list that filters all dynamic routing updates (EIGRP, OSPF, and RIPv2) on spokes. This forces the spoke devices to advertise (populate on the hub device) only their own protected subnets and not other IP addresses. |
|
|
Tunnel IP Range |
The IP range of the inside tunnel interface IP address, including the unique subnet mask. Note If CSM detects that a tunnel interface IP address already exists on the device, and its IP address matches the tunnel's IP subnet field, it will use that interface as the GRE tunnel. |
Dial Backup Tunnel IP Range |
If you are configuring a dial backup interface, enter its inside tunnel interface IP address, including the unique subnet mask. |
Server Load Balance |
When selected, enables the configuration of load balancing on a Cisco IOS router that serves as a hub in a multiple hubs configuration. Server load balancing optimizes performance in a multiple hubs configuration, by sharing the workload. In this configuration, the DMVPN server hubs share the same tunnel IP and source IP addresses, presenting the appearance of a single device to the spokes in a VPN topology. |
Enable IP Multicast |
When selected, enables multicast transmissions across your GRE tunnels. IP multicast delivers application source traffic to multiple receivers without burdening the source or the receivers, while using a minimum of network bandwidth. |
Rendezvous Point |
Only available if you selected the Enable IP Multicast check box. If required, you can enter the IP address of the interface that will serve as the rendezvous point (RP) for multicast transmission. Sources send their traffic to the RP. This traffic is then forwarded to receivers down a shared distribution tree. |
Tunnel Key |
A number that identifies the tunnel key. The default is 1. The tunnel key differentiates between different multipoint GRE (mGRE) tunnel Non Broadcast Multiple Access (NBMA) networks. All mGRE interfaces in the same NBMA network must use the same tunnel key value. If there are two mGRE interfaces on the same router, they must have different tunnel key values. Note To view the newly created tunnel interfaces in the Router Interfaces page, you must rediscover the device inventory details after successfully deploying the VPN to the device. For more information, see Basic Interface Settings on Cisco IOS Routers, page 13-13. |
|
|
Network ID |
All Next Hop Resolution Protocol (NHRP) stations within one logical Non-Broadcast Multi-Access (NBMA) network must be configured with the same network identifier. Enter a globally unique, 32-bit network identifier within the range of 1 to 4294967295. |
Hold time |
The time, in seconds, that routers will keep information provided in authoritative NHRP responses. The cached IP-to-NBMA address mapping entries are discarded after the hold time expires. The default is 300 seconds. |
Authentication |
An authentication string that controls whether the source and destination NHRP stations allow intercommunication. All routers within the same network using NHRP must share the same authentication string. The string can be up to eight characters long. |
Use this page to define the group settings and security associations.
Navigation Path
•(Device view) From the Create a VPN Topology wizard, create or edit a GET VPN topology and click Next until you reach this page.
•(Device view) From the Site-to-Site VPN Manager Window, select a VPN topology in the VPN selector, then select Group Encryption Policy in the Policies selector.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
|
|
---|---|
|
|
Group Name |
Name of the Group Name of Interpretation (GDOI) group. This name is the same as a VPN name. |
Group Identity |
Parameter that is used to identify the group. All key servers and group members use this parameter to identify with the group. The identity can be either a number or any IP address. |
Security Policy |
Note This field appears only if you are using the Create a VPN Topology wizard. ACL Policy object to be used as the security policy. Note The ACL policy object must contain a deny ACE statement as its first deny statement. This statement allows the group members to receive rekey packets sent using multicast protocol. |
Authorization Type |
Type of authorization mechanism used by the group: None, Certificates, or Preshared Key. Selecting Certificates or Preshared Key provides additional security in allowing only authorized group members to register with the key server. This type of additional security is required when a key server serves multiple GDIO groups. If you select Certificates, you must define a certificates filter (either dn or fqdn). This filter, located on the key server, specifies the attributes and values used to validate whether the group member is authorized to join the GDIO or not. |
Key Distribution |
Transport method used to distribute keys to each group member: •Unicast or Multicast—If unicast is selected, the key server sends a rekey message to each registered group member and waits for an acknowledgment. If multicast is selected, the key server sends a rekey message to all group members at once. Note If you select multicast, make sure that the router used as the key server is multicast enabled. •Group IP Address—If multicast is selected as the transport method, specify the group IP address to be used for key distribution. •Use Static IGMP Joins on Group Members—If multicast is selected as the transport method, this option is available. If you select this option, the static Source Specific Multicast (SSM) mappings are enabled, which reveal the source of multicast traffic to the group member. In the case of GET VPN, the group member learns the key server address. |
RSA Key Label |
Label used by key servers to sign rekey messages with. Note Security Manager does not manage RSA keys and therefore appropriate keys need to be manually generated on the key server before deployment. FlexConfig can be used. See Creating FlexConfig Policy Objects, page 18-26. |
Lifetime (KEK) |
Number of seconds that the key used for encrypting traffic keys is valid. |
Encryption Algorithm |
Algorithm used to encrypt the rekey message from the key server to the group member. |
Retransmits |
Number of times the rekey message can be sent if one or more group members do not receive it. |
Interval |
Number of seconds between retries. |
|
|
Use the Security Associations tab to define security associations for the selected VPN topology. The columns in the table summarize the settings for an entry and are explained in Add New Security Association Dialog Box. To configure security associations: •Click the Add button to add an entry to the table, and fill in the Add New Security Association dialog box. •Select an entry and click the Edit button to edit an existing entry. •Select an entry and click the Delete button to delete it. |
Use the Add Certificate Filter dialog box to define a certificate filter for the group encryption policy. This filter, located on the key server, specifies the attributes and values used to validate whether the group member is authorized to join the group or not.
Navigation Path
•From the Group Encryption Policy Page, in the authorization filter table, click the create button or select a authorization filter and click the Edit button.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
Use the Add New Security Association dialog box to define an IPSec profile (name and transform set only) and security policy used by the selected VPN topology.
Navigation Path
From the Group Encryption Policy Page, click the Add button.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
Use the Group Members page to define the group members to be used by the GET VPN topology.
The device name, GET-enabled interface, and local security policy are shown. For detailed information about these attributes, see Edit Group Member Dialog Box.
•To add a group member to the table, click the Add button.
•To edit a group member, select it and click the Edit button.
•To delete a group member, select it and click the Delete button.
•To show specific device identity information, select Interface Roles Only or Matching Interfaces in the Show field.
Navigation Path
Open the Site-to-Site VPN Manager Window, select a GET VPN topology in the VPNs selector, then select Group Members in the Policies selector.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Use the IKE Proposal page to select the IKE proposal that will be used to secure the IKE negotiation between two peers. An IKE proposal is a mandatory policy that is already configured in your VPN topology with predefined default values. On the IKE Proposal page, you can view the parameters of the selected IKE proposal, select a different one from a list of predefined IKE proposals, or create a new one.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select IKE Proposal in the Policies selector.
•You can also open the IKE Proposal page from Policy view. See Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Configuring an IKE Proposal, page 9-47
•Understanding Preshared Key Policies, page 9-56
•VPN Topologies Device View Page
•Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44
Field Reference
|
|
---|---|
Available IKE Proposals |
Lists the predefined IKE proposals available for selection. Select the required IKE proposal in the list. The IKE proposal replaces the one in the Selected IKE Proposal field. IKE proposals are predefined objects. If the required IKE proposal is not included in the list, click Add to open the IKE Editor dialog box that enables you to create or edit an IKE proposal object. For more information, see Add or Edit IKE Proposal Dialog Box, page F-53. |
Selected |
The selected IKE proposal with its predefined default values. The default is preshared_sha_3des_dh5_5. Note You cannot edit the selected IKE proposal because it is a predefined object. You can only edit the properties of an IKE proposal object you create. To remove the IKE proposal from this field, select a different one. |
Create button |
Opens the IKE Editor dialog box for creating an IKE proposal object. For more information, see Add or Edit IKE Proposal Dialog Box, page F-53. |
Edit button |
Opens the IKE Editor dialog box for editing the selected IKE proposal. For more information, see Add or Edit IKE Proposal Dialog Box, page F-53. |
Use the IKE Proposal for GET VPN page to define the IKE proposal to be used by the GET VPN topology.
Navigation Path
•From Policy View, select IKE Proposal for GET from the Policies selector.
Related Topics
•Understanding Preshared Key Policies, page 9-56
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
|
|
---|---|
IKE Proposal |
IKE proposal policy object. Click Select to open a list of predefined IKE proposal policy objects from which to choose. |
IKE Proposal Settings |
Settings defined for the selected IKE proposal policy object. For descriptions of these fields, see Add or Edit IKE Proposal Dialog Box, page F-53. |
IKE Proposal Overrides |
Number of seconds that the ISAKMP SA for key servers and group members is valid. When the lifetime is exceeded, the SA expires and must be renegotiated between the peers. Note If a cooperative key server is configured, key servers should have long lifetimes to keep the ISAKMP SA active for cooperative key server communications. Note We recommend that you set the group member lifetime low as compared to the key server lifetime, especially when cooperative key servers are configured. |
Use the IPsec Proposal page to edit the IPsec policy definitions for your VPN topology.
Note When configuring IPsec policy definitions on an Easy VPN server, the IPsec Proposal page contains different elements. See Easy VPN IPsec Proposal Page.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select IPsec Proposal in the Policies selector.
•You can also open the IPsec Proposal page from Policy view. See Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Understanding IPsec Tunnel Policies, page 9-48
•Configuring IPsec Proposals, page 9-51
Field Reference
|
|
---|---|
Crypto Map Type |
A crypto map combines all the components required to set up IPsec security associations. When two peers try to establish an SA, they must each have at least one compatible crypto map entry. Select the type of crypto map you want to generate: •Static—Use a static crypto map in a point-to-point or full mesh VPN topology. •Dynamic—Dynamic crypto maps can only be used in a hub-and-spoke VPN topology. Dynamic crypto map policies allow remote peers to exchange IPsec traffic with a local hub, even if the hub does not know the remote peer's identity. For more information, see About Crypto Maps, page 9-49. |
Transform Sets |
The transform set(s) to use for your tunnel policy. Transform sets specify which authentication and encryption algorithms will be used to secure the traffic in the tunnel. You can select up to six transform sets. Note Transform sets may use tunnel mode or transport mode of IPsec operation. When IPsec or Easy VPN is the assigned technology, you cannot use transport mode. A default transform set is displayed (tunnel_3des_sha). If you want to use a different transform set, or select additional transform sets, click Select to open a dialog box that lists all available transform sets, and in which you can create transform set objects. For more information, see Creating IPSec Transform Set Objects, page 8-36. If more than one of your selected transform sets is supported by both peers, the transform set that provides the highest security will be used. For more information, see About Transform Sets, page 9-49. |
Enable Perfect Forward Secrecy |
When selected, enables the use of Perfect Forward Secrecy (PFS) to generate and use a unique session key for each encrypted exchange. The unique session key protects the exchange from subsequent decryption, even if the entire exchange was recorded and the attacker has obtained the preshared and/or private keys used by the endpoint devices. Note To enable PFS, you must also select a Diffie-Hellman group for generating the PFS session key. |
Modulus Group |
Available if Enable Perfect Forward Secrecy is selected. Select the required Diffie-Hellman key derivation algorithm from the Modulus Group list box. Security Manager supports Diffie-Hellman group 1, group 2, group 5, and group 7 key derivation algorithms. Each group has a different size modulus: •Group 1 (the default): 768-bit modulus. •Group 2: 1024-bit modulus. •Group 5: 1536-bit modulus. •Group 7: Use when the elliptical curve field size is 163 characters. For more information, see Deciding Which Diffie-Hellman Group to Use, page 9-46. |
Lifetime (sec) |
The number of seconds an SA will exist before expiring. The default is 3600 seconds (one hour). Lifetime refers to the global lifetime settings for the crypto IPsec security association (SA). The IPsec lifetime can be specified in seconds, in kilobytes, or both. |
Lifetime (kbytes) |
The volume of traffic (in kilobytes) that can pass between IPsec peers using a given SA before it expires. Valid values depend on the device type. Enter a value within the range 10-2147483647 for an IOS router, and 2560-536870912 for a PIX7.0/ASA device. The default value is 4,608,000 kilobytes. |
QoS Preclassify |
Supported on Cisco IOS routers, except 7600 devices. When selected, enables the classification of packets before tunneling and encryption occur. The Quality of Service (QoS) for VPNs feature enables Cisco IOS QoS services to operate with tunneling and encryption on an interface. The QoS features on the output interface classify packets and apply the appropriate QoS service before the data is encrypted and tunneled, enabling traffic flows to be adjusted in congested environments, and resulting in more effective packet tunneling. |
Reverse Route |
Supported on ASA devices, PIX 7.0 devices, and Cisco IOS routers except 7600 devices. Reverse Route Injection (RRI) enables static routes to be automatically inserted into the routing process for those networks and hosts protected by a remote tunnel endpoint. For more information, see About Reverse Route Injection, page 9-50. Select one of the following options to configure RRI on the crypto map: •None—Disables the configuration of RRI on the crypto map. •Standard—It creates routes based on the destination information defined in the crypto map access control list (ACL). This is the default option. •Remote Peer—Creates two routes, one for the remote endpoint and one for route recursion to the remote endpoint via the interface to which the crypto map is applied. •Remote Peer IP—Specifies an interface or address as the explicit next hop to the remote VPN device. Then, click Select to open the Network/Hosts Selector, from which you can select the IP address of the remote peer to be used as the next hop. Note You can select the Allow Value Override per Device check box to override the default route, if required. |
Use the Key Servers page to define key servers to be used by the GET VPN topology.
The device name, identity, priority, and registration interface are shown. For detailed information about these attributes, see Edit Key Server Dialog Box.
•To add a key server to the table, click the Add button.
•To edit a key server, select it and click the Edit button.
•To delete a key server, select it and click the Delete button.
•To move a key server, select it and click the up or down arrow button.
Using the arrow keys, you can establish the order of cooperative key servers (configured for redundancy). Group members register with the first key server in the list. If the first key server cannot be reached, they will register with the second key server, and so on. For more information about key server redundancy, see Redundancy Using Cooperative Key Servers, page 9-85.
•To show specific device identity information, select Interface Roles Only or Matching Interfaces in the Show field.
Navigation Path
Open the Site-to-Site VPN Manager Window, select a GET VPN topology in the VPNs selector, then select Key Servers in the Policies selector.
Related Topics
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Use the Peers page to view the endpoints defined for a VPN topology, including the internal and external VPN interfaces and protected networks assigned to the devices in the topology. The interface roles, or interfaces that match each interface role, may also be displayed for the VPN interfaces and protected networks.
The Peers page contains a scrollable table displaying the device roles, VPN interfaces and protected networks for all selected devices.You can filter the table contents using the filter controls above it to display only rows that match the criteria that you specify (see Filtering Tables, page 2-16).
To configure peers:
•Select an entry and click the Edit button to edit an existing entry.
•Select an entry and click the Delete button to delete it.
For more information, see Edit Endpoints Dialog Box.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select Peers in the Policies selector.
•You can also open the Peers page from Device view. For more information, see Managing VPN Devices in Device View, page 9-42.
Related Topics
•Site-to-Site VPN Manager Window
•VPN Topologies Device View Page
Use the Preshared Key page to view or edit the parameters for a preshared key policy.
Note A preshared key policy is not available when configuring Easy VPN.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select Preshared Key in the Policies selector.
•You can also open the Preshared Key page from Policy view. For more information, see Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Understanding Preshared Key Policies, page 9-56
•Configuring Preshared Key Policies, page 9-57
Field Reference
Use the Public Key Infrastructure page to select the CA server that will be used to create a Public Key Infrastructure (PKI) policy, for generating enrollment requests for CA certificates.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select Public Key Infrastructure in the Policies selector.
•You can also open the Public Key Infrastructure page from Policy view. For more information, see Working with Site-to-Site VPN Policies, page 9-43.
Related Topics
•Understanding Public Key Infrastructure Policies, page 9-57
•Configuring Public Key Infrastructure Policies, page 9-61
•Creating PKI Enrollment Objects, page 8-69
Field Reference
|
|
---|---|
Available CA Servers |
Lists the predefined CA servers available for selection. CA servers are predefined PKI enrollment objects that contain server information and enrollment parameters that are required for creating enrollment requests for CA certificates. Select the required CA server if you want to replace the default one in the Selected field. If the required CA server is not included in the list, click Create to open a dialog box that enables you to create or edit a PKI enrollment object. For more information, see PKI Enrollment Dialog Box, page F-142. Note If you are making a PKI enrollment request on an Easy VPN remote access system, you must configure each remote component (spoke) with the name of the user group to which it connects. You specify this information in the Organization Unit (OU) field in the Certificate Subject Name tab of the PKI Enrollment Editor dialog box. You do not need to configure the name of the user group on the hub (Easy VPN Server). For more information, see PKI Enrollment Dialog Box—Certificate Subject Name Tab, page F-150. |
Selected |
The selected CA server. Note You cannot edit the selected CA server because it is a predefined object. You can only edit the properties of an object you define. To remove the selected CA server, select a different one. |
Save button |
Saves your changes to the server but keeps them private. To publish your changes, click the Submit button on the toolbar. Note To save the RSA key pairs and the CA certificates between reloads permanently to Flash memory on a PIX firewall version 6.3, you must configure the "ca save all" command. You can do this manually on the device or using a FlexConfig (see Chapter 18, "Managing FlexConfigs"). |
Use the Server Load Balance page to view or edit the server load balance policy configured on the IPsec Terminators in a large scale DMVPN. Server load balancing optimizes performance in multiple hub-and-spoke VPN topologies, by sharing the workload. In large scale DMVPN configurations, the IPsec Terminators perform the traffic load balancing.
For more information, see Configuring Large Scale DMVPNs, page 9-70.
The Server Load Balance page contains a scrollable table displaying the server load balance parameters for each hub that is connected to an IPsec Terminator. By clicking the arrow displayed alongside any table heading, you can switch the order of the list to display from ascending to descending order, and vice versa. You can also filter the table contents using the filter controls above it to display only rows that match the criteria that you specify (see Filtering Tables, page 2-16).
Navigation Path
•Open the Site-to-Site VPN Manager Window, in the VPNs selector select a hub-and-spoke topology on which large scale DMVPN is configured, then select Server Load Balance in the Policies selector.
•You can also open the Server Load Balance page from Policy view. For more information, see Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Configuring Large Scale DMVPNs, page 9-70
Field Reference
|
|
---|---|
Hub |
The name of the hub connected to the IPsec Terminator. |
Weight |
The capacity of the hub relative to other hubs connected to the IPsec Terminator. A weighted round robin (WRR) scheduling algorithm is used to control the bandwidth allocated to output transmission queues. Weighting is based on the amount of bandwidth used by each transmit queue on an interface. Packets from queues with higher capacity are transmitted more often than those from queues with less capacity. |
Max Connections |
The maximum number of active connections to the IPsec Terminator permitted to the hub. |
Edit button |
Click to open the Edit Load Balancing Parameters Dialog Box, in which you can modify the parameters of a selected load balancing policy. |
In the Edit Load Balancing Parameters dialog box, you can edit the server load balance parameters configured on a hub that is connected to an IPsec Terminator in a large scale DMVPN.
Navigation Path
Open the Server Load Balance Page, select an entry in the table and click Edit.
Related Topics
•Configuring Large Scale DMVPNs, page 9-70
Field Reference
Use the User Group Policy page to create or edit a user group policy on your Easy VPN server. An Easy VPN user group policy can be configured on a Cisco IOS security router, PIX 6.3 Firewall, or Catalyst 6500 /7600 device.
Note You can also configure user group policies in remote access VPNs.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select User Group Policy in the Policies selector.
•You can also open the User Group Policy page from Policy view. For more information, see Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Understanding Easy VPN, page 9-71
•Configuring a User Group Policy for Easy VPN, page 9-77
•Creating User Group Objects, page 8-94
Field Reference
Use the VPN Global Settings page to define global settings for IKE, IPsec, NAT, and fragmentation, that apply to devices in your VPN topology.
The following tabs are available on the VPN Global Settings page:
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select VPN Global Settings in the Policies selector.
•You can also open the VPN Global Settings page from Policy view. See Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Use the ISAKMP/IPsec Settings tab of the VPN Global Settings page to specify global settings for Internet Key Exchange (IKE) and IPsec.
Internet Key Exchange (IKE), also called Internet Security Association and Key Management Protocol (ISAKMP), is the negotiation protocol that lets two hosts agree on how to build an IPsec security association.
Navigation Path
The ISAKMP/IPsec Settings tab appears when you open the VPN Global Settings Page. You can also open it by clicking the ISAKMP/IPsec Settings tab from any other tab in the VPN Global Settings page.
Related Topics
•Understanding IPsec Tunnel Policies, page 9-48
•Understanding ISAKMP/IPsec Settings, page 9-52
•Configuring VPN Global Settings, page 9-55
Field Reference
|
|
---|---|
ISAKMP Settings |
|
Enable Keepalive |
When selected, enables you to configure IKE keepalive as the default failover and routing mechanism. IKE keepalive is defined on the spokes in a hub-and-spoke VPN topology, or on both devices in a point-to-point VPN topology. |
Interval |
The number of seconds that a device waits between sending IKE keepalive packets. The default is 10 seconds. |
Retry |
The number of seconds a device waits between attempts to establish an IKE connection with the remote peer. The default is 2 seconds. |
Periodic |
Available only if Enable Keepalive is selected, and supported on routers running IOS version 12.3(7)T and later, except 7600 devices. When selected, enables you to send dead-peer detection (DPD) keepalive messages even if there is no outbound traffic to be sent. Usually, DPD keepalive messages are sent between peer devices only when no incoming traffic is received but outbound traffic needs to be sent. For more information, see Understanding ISAKMP/IPsec Settings, page 9-52. |
Identity |
During Phase I IKE negotiations, peers must identify themselves to each other. When selected, enables you to use the (IP) address or the hostname of the device that it will use to identify itself in IKE negotiations. You can also select to use a Distinguished Name (DN) to identify a user group name. The default is Address. |
SA Requests System Limit |
Supported on routers running IOS version 12.3(8)T and later, except 7600 routers. The maximum number of SA requests allowed before IKE starts rejecting them. The specified value must equal or exceed the number of peers, or the VPN tunnels may be disconnected. You can enter a value in the range of 0-99999. |
SA Requests System Threshold |
Supported on Cisco IOS routers and Catalyst 6500 /7600 devices. The percentage of system resources that can be used before IKE starts rejecting new SA requests. The default is 75 percent. |
Enable Aggressive Mode |
Supported on ASA devices and PIX 7.0 devices. When selected, enables you to use aggressive mode in ISAKMP negotiations, for an ASA device. Aggressive mode is enabled by default. Deselect this check box to disable the use of aggressive mode in ISAKMP negotiations, for an ASA device. |
|
|
Enable Lifetime |
When selected, enables you to configure the global lifetime settings for the crypto IPsec security associations (SAs) on the devices in your VPN topology. |
Lifetime (secs) |
The number of seconds a security association will exist before expiring. The default is 3,600 seconds (one hour). |
Lifetime (kbytes) |
The volume of traffic (in kilobytes) that can pass between IPsec peers using a given security association before it expires. The default is 4,608,000 kilobytes. |
Xauth Timeout |
Available when Easy VPN is the selected technology, and the selected device is a Cisco IOS router or Catalyst 6500 /7600 device. The number of seconds the device waits for a response from the end user after an IKE SA has been established. When negotiating tunnel parameters for establishing IPsec tunnels in an Easy VPN configuration, Xauth adds another level of authentication that identifies the user who requests the IPsec connection. Using the Xauth feature, the client waits for a "username/password" challenge after the IKE SA has been established. When the end user responds to the challenge, the response is forwarded to the IPsec peers for an additional level of authentication. |
Max Sessions |
Supported on ASA devices and PIX 7.0 devices. The maximum number of SAs that can be enabled simultaneously on the device. |
Enable IPsec via Sysopt |
Supported on ASA devices and PIX Firewalls versions 6.3 or 7.0. When selected (the default), specifies that any packet that comes from an IPsec tunnel is implicitly trusted (permitted). |
Enable SPI Recovery |
Supported on routers running IOS version 12.3(2)T and later, in addition to Catalyst 6500/7600 devices running version 12.2(18)SXE and later. When selected, enables the SPI recovery feature to configure your device so that if an invalid SPI (Security Parameter Index) occurs, an IKE SA will be initiated. SPI (Security Parameter Index) is a number which, together with a destination IP address and security protocol, uniquely identifies a particular security association. When using IKE to establish security associations, the SPI for each security association is a pseudo-randomly derived number. Without IKE, the SPI is manually specified for each security association. When an invalid SPI occurs during IPsec packet processing, the SPI recovery feature enables an IKE SA to be established. |
Use the NAT Settings tab of the VPN Global Settings page to define the NAT settings that will be configured on the devices in your VPN topology.
Note If you want to bypass NAT configuration on IOS routers, make sure the Do Not Translate VPN Traffic check box is selected in the NAT Dynamic Rule platform policy (see NAT Dynamic Rule Dialog Box, page J-8). To exclude NAT on PIX Firewalls or ASA devices, make sure this check box is selected in the NAT Translation Options platform policy (see Translation Options Page, page K-6).
Navigation Path
Open the VPN Global Settings Page, then click the NAT Settings tab.
Related Topics
Field Reference
|
|
---|---|
Enable Traversal Keepalive |
When selected, enables you to configure NAT traversal keepalive on a device. NAT traversal keepalive is used for the transmission of keepalive messages when there is a device (middle device) located between a VPN-connected hub and spoke, and that device performs NAT on the IPsec flow. Note On Cisco IOS routers, NAT traversal is enabled by default. If you want to disable the NAT traversal feature, you must do this manually on the device or using a FlexConfig (see Chapter 18, "Managing FlexConfigs"). For more information, see Understanding NAT, page 9-53. |
Interval |
Available when NAT Traversal Keepalive is enabled. The interval, in seconds, between the keepalive signals sent between the spoke and the middle device to indicate that the session is active. The NAT keepalive value can be from 5 to 3600 seconds. The default is 10 seconds. |
Enable PAT (Port Address Translation) on Split Tunneling for Spokes |
Supported on Cisco IOS routers and Catalyst 6500 /7600 devices. When selected, enables Port Address Translation (PAT) to be used for split-tunneled traffic on spokes in your VPN topology. PAT can associate thousands of private NAT addresses with a small group of public IP address, through the use of port addressing. PAT is used if the addressing requirements of your network exceed the available addresses in your dynamic NAT pool. See Understanding NAT, page 9-53. Note When this check box is enabled, Security Manager implicitly creates an additional NAT rule for split-tunneled traffic, on deployment. This NAT rule, which denies VPN-tunneled traffic and permits all other traffic (using the external interface as the IP address pool), is not reflected as a router platform policy. For information on creating or editing a dynamic NAT rule as a router platform policy, see Defining Dynamic NAT Rules, page 13-10. |
Use the General Settings tab of the VPN Global Settings page to define fragmentation settings including maximum transmission unit (MTU) handling parameters.
Navigation Path
Open the VPN Global Settings Page, then click the General Settings tab.
Related Topics
•Understanding Fragmentation, page 9-54
Field Reference
Use the Global Settings for GET VPN page to define global settings for ISAKMP and IPsec that apply to devices in your GET VPN topology.
Note Global settings do not apply to the group and key server lifetime settings. To configure these settings, see IKE Proposal Page for GET VPN.
Navigation Path
•Open the Site-to-Site VPN Manager Window, select a GET VPN topology in the VPNs selector, then select Global Settings for GET VPN in the Policies selector.
•You can also open the Global Settings for GET VPN page from Policy view. See Managing Shared Site-to-Site VPN Policies in Policy View, page 9-44.
Related Topics
•Understanding IPsec Tunnel Policies, page 9-48
•Understanding ISAKMP/IPsec Settings, page 9-52
•Understanding Group Encrypted Transport (GET) VPNs, page 9-82
•Configuring GET VPN, page 9-88
Field Reference
|
|
---|---|
ISAKMP Settings |
|
Enable Keepalive |
When selected, enables you to configure IKE keepalive as the default failover and routing mechanism. IKE keepalive is defined on the spokes in a hub-and-spoke VPN topology, or on both devices in a point-to-point VPN topology. |
Interval |
The number of seconds that a device waits between sending IKE keepalive packets. The default is 10 seconds. |
Retry |
The number of seconds a device waits between attempts to establish an IKE connection with the remote peer. The default is 2 seconds. |
Periodic |
Available only if Enable Keepalive is selected, and supported on routers running IOS version 12.3(7)T and later, except 7600 devices. Periodic ISAKMP keep-alives should be configured for cooperative key servers. When selected, enables you to send dead-peer detection (DPD) keepalive messages even if there is no outbound traffic to be sent. Usually, DPD keepalive messages are sent between peer devices only when no incoming traffic is received but outbound traffic needs to be sent. For more information, see Understanding ISAKMP/IPsec Settings, page 9-52. |
Identity |
During Phase I IKE negotiations, peers must identify themselves to each other. When selected, enables you to use the (IP) address or the hostname of the device that it will use to identify itself in IKE negotiations. You can also select to use a Distinguished Name (DN) to identify a user group name. The default is Address. |
SA Requests System Limit |
Supported on routers running IOS version 12.3(8)T and later, except 7600 routers. The maximum number of SA requests allowed before IKE starts rejecting them. The specified value must equal or exceed the number of peers, or the VPN tunnels may be disconnected. You can enter a value in the range of 0-99999. |
SA Requests System Threshold |
Supported on Cisco IOS routers and Catalyst 6500 /7600 devices. The percentage of system resources that can be used before IKE starts rejecting new SA requests. The default is 75 percent. |
IPsec Settings |
|
Enable Lifetime |
When selected, enables you to configure the global lifetime settings for the crypto IPsec security associations (SAs) on the devices in your VPN topology. |
Lifetime (secs) |
The number of seconds a security association will exist before expiring. The default is 3,600 seconds (one hour). |
Lifetime (kbytes) |
The volume of traffic (in kilobytes) that can pass between IPsec peers using a given security association before it expires. The default is 4,608,000 kilobytes. |
Use the VPN Summary page to view information about a selected VPN topology. This includes information about the type of VPN topology, its devices, the assigned technology, and specific policies that are configured in it.
Navigation Path
Open the Site-to-Site VPN Manager Window, select a topology in the VPNs selector, then select VPN Summary in the Policies selector.
Note The VPN Summary page automatically opens when you finish creating a VPN topology and is accessible from both Device and Policy views. For more information, see Managing VPN Devices in Device View, page 9-42 and Working with Site-to-Site VPN Policies, page 9-43.
Related Topics
•Site-to-Site VPN Manager Window
•Configuring High Availability in Your VPN Topology, page 9-41
•Configuring VRF-Aware IPsec Settings, page 9-38
•Configuring an IKE Proposal, page 9-47
•Configuring IPsec Proposals, page 9-51
•Configuring Preshared Key Policies, page 9-57
•Configuring Public Key Infrastructure Policies, page 9-61
•Configuring GRE or GRE Dynamic IP Policies, page 9-65
•Configuring DMVPN Policies, page 9-68
•Configuring Large Scale DMVPNs, page 9-70
•Configuring an IPsec Proposal for Easy VPN, page 9-75
•Configuring a User Group Policy for Easy VPN, page 9-77
•Configuring a Tunnel Group Policy for Easy VPN, page 9-78
Field Reference
|
|
---|---|
Type |
The VPN topology type: Hub-and-Spoke, Point-to-Point, or Full Mesh. |
Description |
A description of the VPN topology. |
IPsec Terminator |
Available if the VPN topology is large scale DMVPN. The name of the IPsec Terminator(s) used to load balance GRE traffic to the hubs in the large scale DMVPN. |
Primary Hub |
Available if the VPN topology type is hub-and-spoke. The name of the primary hub in the hub-and-spoke topology. |
Failover Hubs |
Available if the VPN topology type is hub-and-spoke. The name of any secondary backup hubs that are configured in the hub-and-spoke topology. |
Number of Spokes |
Available if the VPN topology type is hub-and-spoke. The number of spokes that are included in the hub-and-spoke topology. |
Peer 1 |
Available if the VPN topology type is point-to-point. The name of the device that is defined as Peer One in the point-to-point VPN topology. |
Peer 2 |
Available if the VPN topology type is point-to-point. The name of the device that is defined as Peer Two in the point-to-point VPN topology. |
Number of Peers |
Available if the VPN topology type is full mesh. The number of devices included in the full mesh VPN topology. |
IPsec Technology |
The IPsec technology assigned to the VPN topology. See Understanding IPsec Technologies and Policies, page 9-5. |
IKE Proposal |
The security parameters of the IKE proposal configured in the VPN topology. See IKE Proposal Page. |
Dynamic VTI |
Available in an Easy VPN topology. Displays if a dynamic virtual template interface is configured on a device in an Easy VPN topology. See Dynamic VTI Tab. |
Transform Sets |
The transform sets that specify the authentication and encryption algorithms that will be used to secure the traffic in the VPN tunnel. See IPsec Proposal Page. |
Preshared Key |
Unavailable if the selected technology is Easy VPN. Specifies whether the shared key to use in the preshared key policy is user defined or auto-generated. See Preshared Key Page. |
Public Key Infrastructure |
If a Public Key Infrastructure policy is configured in the VPN topology, specifies the CA server. See Public Key Infrastructure Page. |
Routing Protocol |
Available only if the selected technology is IPsec/GRE, GRE Dynamic IP, or DMVPN. The routing protocol and autonomous system (or process ID) number used in the secured IGP for configuring a GRE, GRE Dynamic IP, or DMVPN routing policy. Note Security Manager adds a routing protocol to all the devices in the secured IGP on deployment. If you want to maintain this secured IGP, you must create a router platform policy using this routing protocol and autonomous system (or process ID) number. See GRE Modes Page. |
Tunnel Subnet IP |
Available only if the selected technology is IPsec/GRE, GRE Dynamic IP, or DMVPN. If a tunnel subnet is defined, displays the inside tunnel interface IP address, including the unique subnet mask. See GRE Modes Page. |
User Group |
Available for an Easy VPN topology. If a User Group policy is configured on a device in the Easy VPN topology, displays the details of the policy. See User Group Policy Page. |
PIX7.0/ASA Tunnel Group |
Available for an Easy VPN topology. If a Tunnel Group policy is configured on a PIX Firewall version 7.0, or ASA appliance in the Easy VPN topology, displays the details of the policy. See Tunnel Group Policy (PIX 7.0/ASA) Page. |
High Availability |
Available if the VPN topology type is hub-and-spoke. If a High Availability policy is configured on a device in your hub-and-spoke VPN topology, displays the details of the policy. See Map Settings Dialog Box, page B-10. |
VRF-Aware IPsec |
Available if the VPN topology type is hub-and-spoke. If a VRF-Aware IPsec policy is configured on a hub in your hub-and-spoke VPN topology, displays the type of VRF solution (1-Box or 2-Box) and the name of the VRF policy. See VRF Aware IPsec Tab. |
Device view provides an easy way to view and edit the structure of your VPN topologies at the device level. Use this page to view the VPN topology (topologies) to which each device in the CSM inventory belongs, and if necessary, change its assignment to or from a VPN topology. From this page, you can also create and delete VPN topologies, edit the properties of a VPN topology, including its device selection, and edit its policies.
Navigation Path
1. Click the Device View button on the toolbar.
2. Select the device from the Device selector.
3. Select Site-to-Site VPN from the Policy selector.
Related Topics
•Working with VPN Topologies, page 9-14
•Using the Create VPN Wizard, page 9-14
•Editing a VPN Topology, page 9-27
•About Editing a VPN Topology, page 9-25
•Managing VPN Devices in Device View, page 9-42
•Working with Site-to-Site VPN Policies, page 9-43
Field Reference
|
|
---|---|
Type |
An icon that depicts the topology type. |
Name |
The unique name that identifies the VPN topology. |
IPsec Technology |
The IPsec technology assigned to the VPN topology. |
Description |
Any description defined for the VPN topology. |
Edit VPN Policies button |
Click to edit the VPN policies defined for a selected VPN topology. The Site-to-Site VPN Policies window opens, displaying information about the VPN topology. To edit a policy, select it in the Policies selector. A page opens on which you can view or edit the parameters for the selected policy. See Site to Site VPN Policies. |
Create VPN Topology button |
Opens the Create VPN wizard to create a VPN topology. See Create VPN Wizard. Note You can also create a VPN topology by right-clicking in the table and selecting the Create VPN Topology option. |
Edit VPN Topology button |
Click to edit the properties of a selected VPN topology. The Edit VPN dialog box opens, displaying the Device Selection tab. See Device Selection Page. Note You can also edit the properties of a VPN topology by double-clicking its row in the table, or right-clicking it and selecting the Edit VPN Topology option. For more information, see About Editing a VPN Topology, page 9-25. |
Delete VPN Topology button |
Deletes a selected VPN topology. A dialog box opens asking you to confirm the deletion. Note You can also delete a VPN topology by right-clicking it in the table and selecting the Delete VPN Topology option. For more information, see Deleting a VPN Topology, page 9-28. |
Security Manager allows you to import your existing VPN configurations so that they can be managed by Security Manager, without you having to recreate them. You can do this using the Discover VPN Policies wizard.
The following pages describe the steps in the Discover VPN Policies wizard:
•Discover VPN Policies Wizard—Name and Technology Page
•Discover VPN Policies Wizard—Device Selection Page
Navigation Path
Select Policy > Discover VPN Policies in Device view.
Related Topics
•Site-To-Site VPN Discovery, page 9-8
•Prerequisites for VPN Discovery, page 9-10
•VPN Discovery Rules, page 9-10
•Discovering Site-to-Site VPNs, page 9-12
•Rediscovering Site-to-Site VPNs, page 9-13
Use the Name and Technology page of the Discover VPN Policies wizard to provide a name and description for the VPN, specify the topology type and IPsec technology of the VPN to be discovered, and whether you want to discover the VPN directly from the live devices in your network or from the Config Archive.
Navigation Path
Select Policy > Discover VPN Policies in Device view. The Discover VPN Policies wizard opens, displaying the Name and Technology page.
Related Topics
•Discover VPN Policies Wizard—Device Selection Page
•Site-To-Site VPN Discovery, page 9-8
•Discovering Site-to-Site VPNs, page 9-12
•Rediscovering Site-to-Site VPNs, page 9-13
Field Reference
Use the Device Selection page of the Discover VPN Policies wizard to specify the devices participating in the VPN being discovered, and their role in the VPN topology. The devices that are available for selection include only those that can be used for the selected VPN topology type, that support the IPsec technology type, and which you are authorized to view.
The contents of this page differ depending on the VPN topology type. For example, if the topology type is hub and spoke, the page allows you to specify the devices as hubs or spokes.
Navigation Path
Open the Discover VPN Policies Wizard—Name and Technology Page, then click Next.
Related Topics
•Discover VPN Policies Wizard—Name and Technology Page
•Site-To-Site VPN Discovery, page 9-8
•Discovering Site-to-Site VPNs, page 9-12
•Rediscovering Site-to-Site VPNs, page 9-13
•About Selecting Devices in a VPN Topology, page 9-17
Field Reference
|
|
---|---|
Available Devices |
Lists all devices that can be included in your selected VPN topology, that support the IPsec technology type, and which you are authorized to view. Note Clicking a device group selects all its devices. |
>> button |
Select devices and click this button to add them to the list. |
<< button |
Select devices and click this button to remove them from the list. |
Hubs |
Devices that are hubs in your hub-and-spoke topology. In an Easy VPN topology, the selected devices are servers. Note If multiple devices are selected, you must make sure that the required primary hub device appears first in the list. You can use the Up and Down buttons to change the order of the hubs in the list. |
Spokes |
Devices that are spokes in your hub-and-spoke topology. In an Easy VPN topology, the selected devices are clients. |
Peer One/Peer Two |
Devices that are peers in your point-to-point topology. |
Selected Devices |
Devices that participate in your full mesh topology. |
Key Servers |
Devices defined as key servers in your GET VPN topology. |
Group Members |
Devices defined as group members in your GET VPN topology. |
Finish button |
Saves your wizard definitions and closes the wizard. The Discovery Status dialog box opens, allowing you to monitor the status of the VPN discovery task and view any relevant error or warning messages. See Viewing Policy Discovery Task Status, page 6-16. Note When the process is complete, the Site-to-Site VPN Manager window opens, displaying summary information for the VPN that was discovered. |
Security Manager allows you to rediscover the configurations of existing VPN topologies that are already managed with Security Manager, without having to recreate them. You can do this in the Rediscover VPN Policies wizard.
Note Only the configurations of device specific policies, such as VPN interfaces and protected networks, and any High Availability (HA) policies that are configured on hubs, can be rediscovered. VPN global policies, such as IKE proposals or PKI enrollments cannot be rediscovered.
In addition, Easy VPN topologies with Dynamic VTI cannot be rediscovered.
The following pages describe the steps in the Rediscover VPN Policies wizard:
•Rediscover VPN Policies Wizard—Name and Technology Page
•Rediscover VPN Policies Wizard—Device Selection Page
Navigation Path
In the Site-to-Site VPN Manager window, right-click the VPN topology whose configurations you want to rediscover, and click Rediscover Peers.
Related Topics
•Rediscovering Site-to-Site VPNs, page 9-13
•Site-To-Site VPN Discovery, page 9-8
•Prerequisites for VPN Discovery, page 9-10
•VPN Discovery Rules, page 9-10
•Discovering Site-to-Site VPNs, page 9-12
Use the Name and Technology page of the Rediscover VPN Policies wizard to specify whether you want to rediscover the VPN directly from the live devices in your network or from the Config Archive.
Note You cannot change the topology type or IPsec technology.
Navigation Path
In the Site-to-Site VPN Manager window, right-click the VPN topology whose configurations you want to rediscover, and click Rediscover Peers. The Rediscover VPN Policies wizard opens, displaying the Name and Technology page.
Related Topics
•Rediscover VPN Policies Wizard
•Rediscover VPN Policies Wizard—Device Selection Page
•Rediscovering Site-to-Site VPNs, page 9-13
•Site-To-Site VPN Discovery, page 9-8
•Discovering Site-to-Site VPNs, page 9-12
Field Reference
Use the Device Selection page of the Rediscover VPN Policies wizard to specify the devices whose peer-level policies need to be rediscovered, and their roles in the VPN topology.
The contents of this page differ depending on the VPN topology type. For example, if the topology type is hub and spoke, the page enables you to specify the devices as hubs or spokes.
Navigation Path
Open the Rediscover VPN Policies Wizard—Name and Technology Page, then click Next.
Related Topics
•Rediscover VPN Policies Wizard
•Rediscovering Site-to-Site VPNs, page 9-13
•Site-To-Site VPN Discovery, page 9-8
•Discovering Site-to-Site VPNs, page 9-12
Field Reference
|
|
---|---|
Available Devices |
Lists all devices that can be included in your selected VPN topology, that support the IPsec technology type, and which you are authorized to view. Note Clicking a device group selects all its devices. |
>> button |
Select devices and click this button to add them to the list. |
<< button |
Select devices and click this button to remove them from the list. |
Hubs |
The devices that are hubs in your hub-and-spoke topology. In an Easy VPN topology, the selected devices are servers. Note If you selected only one device, it becomes the primary hub. If multiple devices are selected, you must make sure that the required primary hub device appears first in the list. You can use the Up and Down buttons to change the order of the hubs in the list. |
Spokes |
The devices that are spokes in your hub-and-spoke topology. In an Easy VPN topology, the selected devices are clients. |
Peer One/Peer Two |
The devices that are peers in your point-to-point topology. |
Key Servers |
Devices defined as key servers in your GET VPN topology. |
Group Members |
Devices defined as group members in your GET VPN topology. |
Selected Devices |
The devices that participate in your full mesh topology. |
Finish button |
Saves your wizard definitions and closes the wizard. The Discovery Status dialog box opens, allowing you to monitor the status of the VPN rediscovery task and view any relevant error or warning messages. See Viewing Policy Discovery Task Status, page 6-16. Note When the process is complete, the Site-to-Site VPN Manager window opens, displaying summary information for the VPN that was rediscovered. |