This chapter covers the following subjects:
• Plan the deployment of Cisco IOS Software site-to-site IPsec VPN high-availability features: Covers methods for providing redundancy to site-to-site VPNs.
• Use routing protocols for VPN failover: Covers deploying routing protocols to provide path redundancy.
• Choose the most optimal method of mitigating failure in a VTI-based VPN: Covers path and device redundancy in single- and multiple-transport networks.
• Choose the most optimal method of mitigating failure in a DMVPN: Covers providing redundancy in a DMVPN.
IPsec Virtual Private Networks (VPN) have become a method of providing primary connections between sites. In the recent past, IPsec site-to-site VPNs were used as a backup path between sites that was enabled when a traditional WAN circuit went down. The IPsec VPN, in this case, was the secondary, backup means of communication. With the IPsec VPN becoming the primary communication path, network designers must understand the different types of failures that can occur and put in place a high-availability solution that will protect an organization from outages.
The “Do I Know This Already?” helps you decide whether you really need to read the entire chapter. If you already intend to read the entire chapter, you do not necessarily need to answer these questions now.
The eight-question quiz, derived from the major sections in the “Foundation Topics” portion of this chapter, helps you determine how to spend your limited study time.
Table 18-1 outlines the major topics discussed in this chapter and the “Do I Know This Already?” quiz questions that correspond to those topics.
Table 18-1. “Do I Know This Already?” Foundation Topics Section-to-Question Mapping

The goal of self-assessment is to gauge your mastery of the topics in this chapter. If you do not know the answer to a question or are only partially sure of the answer, you should mark this question wrong for purposes of the self-assessment. Giving yourself credit for an answer that you correctly guess skews your self-assessment results and might provide you with a false sense of security.
1. What can be used to mitigate device failure?
a. Single ISP transport networks
b. Multiple ISP transport networks
c. Multiple devices at a site
d. Redundant interfaces on a VPN device
2. What can be done to provide high availability when the cost of redundant devices cannot be justified?
a. Use single ISP transport networks
b. Use multiple ISP transport networks
c. Use redundant interfaces
d. Use multiple devices at a site
3. When a transport network is not under organizational control, it might be necessary to choose which of the following?
a. A different VPN technology
b. Traditional WAN circuits
c. Point-to-multipoint topology
d. Redundant routers
e. Multiple independent transport networks
4. Which interface command can be used to choose the best path when deploying the dynamic routing protocol OSPF?
a. ip ospf cost
b. ip ospf tuning
c. ip ospf path
d. ip ospf router
e. None of these answers are correct.
5. In a VTI-based IPsec VPN, traffic that should be protected by the VPN tunnel should be routed how?
a. Carefully
b. Redundantly
c. Dynamically
d. Statically
6. What should be used to provide a virtual gateway for clients at the spoke site?
a. IPsec
b. DHCP
c. HSRP
d. AAA
e. None of these answers are correct.
7. IPsec shared SAs are enabled with what command?
a. tunnel protection ipsec profile shared
b. ipsec dual SA
c. ip split sa
d. crypto ipsec sa redundant
e. None of these answers are correct.
8. Which high-availability scenario provides the highest level of redundancy because it mitigates failures of devices, interfaces, access links, and transport networks?
a. Static VTI-based VPN
b. Single DMVPN
c. Dual DMVPN
d. Dual ISPs
The answers to the “Do I Know This Already?” quiz are found in Appendix A. The suggested choices for your next step are as follows:
• 6 or less overall score: Read the entire chapter. This includes the “Foundation Topics” and the “Exam Preparation” sections.
• 7 or 8 overall score: If you want more review on these topics, skip to the “Exam Preparation” section. Otherwise, move on to Chapter 19, “Deploying GET VPNs.”
Providing high availability in a VPN network means protecting it from expected failures and enabling mechanisms that allow it to heal itself. This chapter provides information necessary for choosing recommended high-availability architectures and configuring a highly available IPsec VPN tunnel solution.
Site-to-site IPsec VPNs are becoming increasingly more popular solutions for connecting sites. Compared to the traditional WAN connections, they are more cost-effective. In fact, the IPsec VPN was, in some environments, the backup path that was used in the event that the primary WAN connection went down.
Now that the IPsec VPN is the primary connection, it needs to be highly available and be able to “heal” itself in the event of a failure. The network designer must be aware of the types of possible failures and the ways to recover from them.

The VPN has the following failure modes:
• Failure of the path between the VPN peers: This path can fail without affecting the status of a local interface, which makes it difficult to recognize. For VPNs that traverse the public Internet, this could be a failure at an Internet service provider (ISP), link congestion, or anything else that would prevent the two VPN peers from communicating with one another. This kind of failure is typically overcome by using redundant paths and/or devices and having dynamic routing protocols that route around the failed device or network segment.
• Failure of a device: Traditionally, redundant devices in combination with routing protocols and/or Hot Standby Router Protocol (HSRP) to provide high availability are used to provide high availability in the event of this type of failure.
• Failure of a network interface of the link adjacent to one of the VPN devices that prevents one VPN peer from reaching the other: This is similar to the failure of a physical WAN interface in traditional WAN networks. This can be resolved with redundant interfaces or redundant devices with a secondary circuit.
The first type of outage occurs when a VPN fails that traverses a transport network that is under control of the local network administrator (not an ISP connection). In this scenario, the VPN tunnel will fail to establish when a segment or device in the path between the two VPN peers fails. Mitigating this type of failure involves using a mechanism that detects failures in the transport network and automatically reroutes around the failure. This type of solution requires no high-availability features on the VPN devices themselves.
This type of outage occurs when the ISP transport network that provides connectivity between the two VPN peers fails. In this scenario, the local network administrator has no control over the routing protocols in the ISP network and cannot have any knowledge of how much, if any, redundancy exists in the ISP transport network. A possible solution to this type of failure would be to have two VPN tunnels that used different ISP transport networks. This provides a complete redundant solution to the failure of an ISP; however, it requires a mechanism to detect path failures (one ISP fails) and to automatically reroute traffic to the other ISP. This solution has the downside of high costs because of using multiple service providers.
The last of the three general types of failures is where the failure occurs on or close to the VPN device. This would include the total failure of the VPN device, failure of the access link directly connected to the VPN device, or failure of the VPN device’s network interface.
A reliable option for mitigating this kind of failure is to have a second VPN device at a VPN site where there are two VPN devices connected to the transport network. Failure of the VPN device could automatically fail over to the secondary VPN device if using HSRP or a similar protocol. Another option would be to have a redundant network interface in the same VPN device. This would protect against network interface failure, but not total device failure.
Cisco IOS Software supports the use of HSRP on untrusted interfaces facing the transport network and terminating the VPN tunnel on the HSRP virtual address. This feature also provides stateful IPsec failover, but it only works with classic IPsec configuration using crypto maps. It does not work with Virtual Tunnel Interface (VTI) or Dynamic Multipoint VPN (DMVPN) tunnels.

When implementing high-availability mechanisms to overcome failures in a tunnel-based VPN, consider the following general guidelines:
• Design the VPN to meet an organization’s requirements for availability. The design should provide a level of high availability that is commensurate with the cost of meeting availability needs.
• For locations that have continuous operation requirements, use redundant VPN devices to mitigate the risk of device failure.
• On sites that have a likelihood of an access link failure and where the cost of redundant devices cannot be justified, use redundant interfaces on the same device to provide connectivity to either a secondary access link or as a standby interface for the primary access link.
• If complete redundant paths are needed, either deploy a completely redundant network path that is under the control of local administration or use multiple-transport networks (two ISPs) and connect them to either redundant interfaces or redundant VPN devices.
• Remember that not all VPN sites require the same level of high availability. A hub-and-spoke network would have high-availability features for the hub routers and for the most critical spoke sites.
When using site-to-site VPNs as an alternative to traditional WAN connectivity, it is important to use dynamic routing protocols to provide automatic failover. The following sections provide detailed information about using dynamic routing with VPN tunnels.
Dynamic routing protocols are one of the best ways to provide high availability to site-to-site IPsec VPNs. Because tunnel-based IPsec VPNs use Cisco IOS Software tunnel interfaces, configuring the high-availability features is similar to when they are configured on classic routed WAN interfaces.
Dynamic routing protocols will automatically detect peer failures and path failures and then automatically reroute around the failure if redundant paths and devices are in place.
One of the most common uses of routing protocols to ensure VPN high availability is where dynamic routing protocols are used in the transport network between two VPN peers. The tunnel endpoints should be included in the routing process so that, in the event of a device or path failure in the transport network, the routing protocol will automatically route around the failure and the connectivity between the two VPN peers will not be lost.
When the transport network is not under the network administrator’s control, choosing to use multiple independent transport networks (two ISPs) at each VPN location can provide high availability to site-to-site IPsec VPN tunnels.
In this situation, each VPN device (one at each site) connects to both transport networks and two VPN tunnels, one over each transport network. With direct peering between the VPN devices, the interior gateway protocols (IGP) will see each of them as a single-hop point-to-point link, and keepalive packets can be exchanged directly between the two VPN devices over the tunnels. This setup will provide detection of both path and remote device failures because both instances will cause the loss of keepalive packets. This setup will be able to reroute around a path failure by sending traffic over the working path (VPN tunnel), but it will not mitigate a VPN device failure because each VPN site has a single VPN device.
You must take precautions when configuring dynamic routing protocols to ensure that there is a device that participates in the same routing protocol both outside the VPN tunnel (the transport network) and inside the tunnel (directly with VPN peers).
This could be a possibility if an organization is in control of the transport network and wants to provide high availability through dynamic routing, both inside the transport network and inside the VPN to ensure continuous connectivity.
This kind of routing requires that VPN devices be prevented from learning the paths to their remote peer tunnel destination IP addresses over the VPN tunnel itself. The single-hop path over the VPN will always be a better route than the path over the transport network. This situation will break the tunnel because it causes the VPN-encapsulated packet to be routed into its own tunnel interface instead of being routed out the correct physical interface that is used to reach the remote VPN peer. Cisco IOS Software will react to this behavior by flapping the tunnel interface.
Use either route filtering or a different routing protocol for the transport network and the VPN network to avoid this recursive routing issue.
Routing protocols are ideal technologies to use with tunnel-based IPsec VPNs because the IPsec tunnels are routable interfaces to Cisco IOS Software. Two of the prominent technologies that support this functionality are IPsec Virtual Tunnel Interfaces (VTI) and the Dynamic Multipoint VPN (DMVPN) architecture.
In a VTI-based IPsec VPN topology, an interior routing protocol will see the VTI-based VPN tunnel as a point-to-point link, similar to a point-to-point leased WAN link. This means that redundant primary/secondary or load-balanced VTI tunnels can be deployed over two transport networks between two sites to provide path redundancy. These two tunnels can be terminated on two VPN devices to provide device redundancy as well. The configuration of this kind of high availability is exactly the same as it would be for a classic point-to-point WAN.
A DMVPN can look like either a point-to-multipoint (for strict hub-and-spoke DMVPNs) or a broadcast network (partial or full mesh DMVPNs). Routing protocol adjacencies are always established between spoke routers and the hub router. There is no spoke-to-spoke routing protocol peering. The hub will replicate all received route information to all other spokes. Configuring redundancy is similar to a classic nonbroadcast multiaccess (NBMA) network, and hub redundancy is especially important to maintaining routing propagation among the spokes.
Whichever tunneling IPsec VPN technology or topology is deployed, tuning the dynamic routing protocol to control best-path selection might be necessary.
Tuning routing protocols for path selection usually means choosing between two options:
• Two site-to-site VPN tunnels, with one being the primary data path and the second tunnel being the secondary path: In this option, the secondary path is used only if the primary fails. This option is configured simply by tuning the routing protocol cost so that the primary tunnel always appears as the best path.
• Two site-to-site VPN tunnels, with load sharing between the two tunnels to increase available bandwidth: This option is configured by setting equal costs on the two tunnels.
To improve convergence time, tune the timers used by routing protocols to check for peer availability. By tuning (shortening) these timers, peer and path failures can be detected (and routed around) much quicker.

Default timers depend on the dynamic routing protocol in use:
• Open Shortest Path First (OSPF): The default hello interval is 10 seconds, and the hold time is 40 seconds. Use the ip ospf hello-interval interface command to modify the hello timer and the ip ospf dead-interval interface command to modify the hold time. OSPF fast hellos can be used but only after adequate performance testing. This is configured by using the ip ospf dead-interval minimal hello-multiplier command.
• Enhanced IGRP (EIGRP): The default hello interval is 5 seconds, and the hold time is 15 seconds or higher on low-speed links (hello timer of 60 seconds and hold timer of 180 seconds). Use the ip hello-interval eigrp AS interval interface command to change the hello timer and the ip hold-time eigrp AS holdtime interface command to modify the hold timer.
• Routing Information Protocol version 2 (RIPv2): The default update timer is 30 seconds, and the default holddown timer is 180 seconds. Use the timers basic router configuration command to modify the RIP timers.
An additional amount of time is added to the overall convergence that is due to the specifics of each routing protocol that can prevent immediate recalculations of the best-path algorithm:
• OSPF: SPF (shortest path first) timer is 5 seconds. Use the timers spf OSPF router command to modify the SPF timer.
• EIGRP: A route could become active that can last for several seconds. If the backup route is reachable through a feasible successor, the recalculation is immediate.
There are several methods that you can use to provide continuity in the event of a failure. The following sections describe the different types of mitigation techniques that are available for Cisco IOS Software VTI-based VPNs.
For a VTI-based site-to-site IPsec VPN running over a single-transport network that is under the organization’s control where only path redundancy is required, the following redundancy architecture is recommended:
• Include only the physical interfaces that terminate VPN tunnels in the dynamic routing protocol. Do not include the inside VTIs in the routing process. Instead, use static routing to protect anything that requires IPsec protection.
• Make sure to include all interfaces of devices in the transit network that the VPN tunnel will traverse in the routing protocol. This will allow automatic rerouting around failures in the transit network should one occur.

For a VTI-based site-to-site IPsec VPN running over two transport networks that are not under the organization’s control (typically two ISPs) with only path redundancy required, the following redundancy architecture is recommended:
• On the VPN routers, use one routed network interface to connect to the first ISP and another routed network interface to connect to the second ISP.
• On the VPN routers, configure two permanent VTI tunnels, one over the first ISP network and one over the second ISP network. Configure static routes that point to the remote peer’s tunnel destination IP addresses.
• On the VPN routers, configure that same dynamic routing protocol over both VTI tunnels and tune the cost of the tunnel interfaces to route over the preferred path.

For a VTI-based site-to-site IPsec VPN with a single ISP, device redundancy and path protection are required. The solution to meeting this requirement is to add an additional VPN device (router) at each location. In this case, all routers are running HSRP and running the same OSPF process with tuning configured to set up a primary and secondary tunnel.

To increase the high availability of this scenario by adding device redundancy, there are two options:
• Add a redundant device to critical sites and configure one VTI tunnel per device (one for each different ISP transport network). HSRP is used on the LAN side of the spoke routers to ensure that clients have a seamless failover to the redundant router.
• Use redundant interfaces in branch offices that do not have the redundant devices mentioned in the previous option. The single router still will have two tunnels (again, one over each ISP network). HSRP will be used on the LAN to provide a virtual gateway to the users. If one of the ISP transport networks fails, OSPF will route traffic over the secondary tunnel.
The following sections present the mitigation techniques that you can use to provide redundancy in a DMVPN.
To provide redundancy for a DMVPN topology, it is recommended to create two separate DMVPNs by using two hub routers and one or two spoke routers at remote sites.
Remote sites with a single spoke router on-site will become a member of both DMVPNs by registering with both hub routers. Remote sites with two spoke routers will have one spoke router registered with one hub router, and the other spoke router will register with the other hub router. HSRP will be configured on the two spoke routers to provide the virtual gateway for LAN users. Both scenarios will have a dynamic routing protocol running over both DMVPNs that will provide path and device redundancy. Tuning the routing protocol provides the capability to engineer traffic to take desired paths.

Configuring redundant DMVPNs is the same as configuring two independent DMVPNs with different tunnel keys and Next Hop Resolution Protocol (NHRP) network IDs. Figure 18-1 depicts a dual DMVPN topology and shows primary and secondary paths. Keep the following points in mind:
• The configuration of the dynamic routing protocol determines traffic patterns over the redundant tunnels (primary/secondary versus load sharing).
• Shared IPsec security associations (SA) must be configured on the spoke routers because dynamic spoke-to-spoke tunnels are being used in the DMVPN (meaning partial or full mesh DMVPN).

Figure 18-1. Redundancy with Dual DMVPNs

In environments running a redundant solution using two DMVPNs with dynamic spoke-to-spoke tunnels, it is possible to have two or more generic routing encapsulation (GRE) tunnel sessions between the same two spokes. In this case, there are multiple tunnels between the same two endpoints, but they have different tunnel keys.
This situation requires that the two GRE tunnels be secured using a single IPsec SA because the IPsec Quick Mode request comprises two tunnels with the same tunnel source.
The tunnel protection ipsec profile shared command creates a single IPsec Security Association Database (SADB) for all tunnel interfaces that use the same profile and tunnel source interface. This allows the same IPsec SA to secure all GRE tunnels (same source and destination but different tunnel key).
In this situation, configuring dual DMVPN environments to provide path and device redundancy means creating two separate DMVPNs on the spoke router that use different NHRP network IDs and tunnel keys. The primary DMVPN uses a lower cost for its tunnel by configuring the ip ospf cost interface command under the tunnel interface. The secondary DMVPN will have a higher cost configured with the ip ospf cost interface command. This should be configured on the tunnel interfaces on both the hub and spoke routers. Ensure that the shared command option is included in the tunnel protection ipsec profile command to allow IPsec SA negotiation to work properly. Examples 18-1 through 18-3 show the similarities and differences in the configurations. Note that the DMVPN configurations on the hubs create two DMVPNs with different NHRP network IDs and tunnel keys, and the spoke router is configured for both of these independent DMVPNs.

Example 18-1. Primary Hub Router Configuration for a DMVPN with a Single-Transport Network
router(config)# interface FastEthernet 0/0
router(config-if)# standby 1 ip 192.168.0.1
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# interface tunnel0
router(config-if)# ip address 172.16.0.1 255.255.255.0
router(config-if)# ip nhrp map multicast dynamic
router(config-if)# ip nhrp network-id 100
router(config-if)# tunnel source FastEthernet 1/0
router(config-if)# yunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1
router(config-if)# tunnel key 100
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf priority 10
router(config-if)# ip ospf cost 10

Example 18-2. Secondary Hub Router Configuration for a DMVPN with a Single-Transport Network
router(config)# interface FastEthernet 0/0
router(config-if)# standby 1 ip 192.168.0.1
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# interface tunnel0
router(config-if)# ip address 172.16.1.1 255.255.255.0
router(config-if)# ip nhrp map multicast dynamic
router(config-if)# ip nhrp network-id 200
router(config-if)# tunnel source FastEthernet 1/0
router(config-if)# tunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1
router(config-if)# tunnel key 100
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf priority 10
router(config-if)# ip ospf cost 20

Example 18-3. Spoke Router Configuration for a DMVPN with a Single-Transport Network
router(config)# interface FastEthernet 0/0
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# interface tunnel0
router(config-if)# ip address 172.16.0.10 255.255.255.0
router(config-if)# ip nhrp map 172.16.0.1 172.17.0.1
router(config-if)# ip nhrp network-id 100
router(config-if)# ip nhrp nhs 172.16.0.1
router(config-if)# tunnel source FastEthernet1/0
router(config-if)# tunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1 shared
router(config-if)# tunnel key 100
router(config-if)# ip ospf network broadcast
router(config-if)# ip ospf priority 0
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf cost 10
!
router(config)# interface tunnel1
router(config-if)# ip address 172.16.1.10 255.255.255.0
router(config-if)# ip nhrp map 172.16.1.1 172.17.0.2
router(config-if)# ip nhrp network-id 200
router(config-if)# ip nhrp nhs 172.16.1.1
router(config-if)# tunnel source FastEthernet1/0
router(config-if)# tunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1 shared
router(config-if)# tunnel key 200
router(config-if)# ip ospf network broadcast
router(config-if)# ip ospf priority 0
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf cost 20
Two independent DMVPNs can also be configured to use two ISP transport networks. The primary DMVPN will use one ISP transport network, and the secondary DMVPN will use the other ISP transport network. This provides the highest level of redundancy in that it mitigates failures of devices, interfaces, and the transport network. Refer to Examples 18-4 through 18-6. As with the case of a DMVPN over a single-transport network, the hub routers are configured with two distinct DMVPNs that have different NHRP IDs and tunnel keys. The spoke router is configured to peer with both of these DMVPNs and uses ip ospf cost to dictate which is the primary and which is the backup DMVPN.

Example 18-4. Primary Hub Router Configuration for a DMVPN over Multiple-Transport Networks
router(config)# interface FastEthernet 0/0
router(config-if)# standby 1 ip 192.168.0.1
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# interface tunnel0
router(config-if)# ip address 172.16.0.1 255.255.255.0
router(config-if)# ip nhrp map multicast dynamic
router(config-if)# ip nhrp network-id 100
router(config-if)# tunnel source FastEthernet 1/0
router(config-if)# tunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1
router(config-if)# tunnel key 100
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf priority 10
router(config-if)# ip ospf cost 10

Example 18-5. Secondary Hub Router Configuration for a DMVPN over Multiple-Transport Networks
router(config)# interface FastEthernet 0/0
router(config-if)# standby 1 ip 192.168.0.1
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# interface tunnel0
router(config-if)# ip address 172.16.1.1 255.255.255.0
router(config-if)# ip nhrp map multicast dynamic
router(config-if)# ip nhrp network-id 200
router(config-if)# tunnel source FastEthernet 1/0
router(config-if)# tunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1
router(config-if)# tunnel key 100
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf priority 10
router(config-if)# ip ospf cost 20

Example 18-6. Spoke Router Configuration for a DMVPN over Multiple-Transport Networks
router(config)# interface FastEthernet 0/0
router(config-if)# ip ospf 1 area 0.0.0.0
router(config)# interface tunnel0
router(config-if)# ip address 172.16.0.10 255.255.255.0
router(config-if)# ip nhrp map 172.16.0.1 172.17.0.1
router(config-if)# ip nhrp network-id 100
router(config-if)# ip nhrp nhs 172.16.0.1
router(config-if)# tunnel source FastEthernet1/0
router(config-if)# tunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1 shared
router(config-if)# tunnel key 100
router(config-if)# ip ospf network broadcast
router(config-if)# ip ospf priority 0
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf cost 10
!
router(config)# interface tunnel1
router(config-if)# ip address 172.16.1.10 255.255.255.0
router(config-if)# ip nhrp map 172.16.1.1 172.17.0.2
router(config-if)# ip nhrp network-id 200
router(config-if)# ip nhrp nhs 172.16.1.1
router(config-if)# tunnel source FastEthernet1/0
router(config-if)# tunnel mode gre multipoint
router(config-if)# tunnel protection ipsec profile VPN1 shared
router(config-if)# tunnel key 200
router(config-if)# ip ospf network broadcast
router(config-if)# ip ospf priority 0
router(config-if)# ip ospf 1 area 0.0.0.0
router(config-if)# ip ospf cost 20
As mentioned in the section, “How to Use This Book,” in the Introduction, you have several choices for exam preparation: the exercises here, the memory tables in Appendix C, the final exam preparation chapter, and the exam simulation questions on the CD-ROM. The following questions present a bigger challenge than the exam itself because they use an open-ended question format. By using this more difficult format, you exercise your memory better and prove your conceptual and factual knowledge of this chapter. You can find the answers to these questions in Appendix A, “Answers to the DIKTA Quizzes and Fill in the Blanks Questions.”
Review the most important topics in the chapter, noted with the Key Topics icon in the margin of the page. Table 18-2 lists a reference of these key topics and the page numbers on which each is found.

Print a copy of Appendix C, “Memory Tables” (found on the CD), or at least the section for this chapter, and complete the tables and lists from memory. Appendix D, “Memory Table Answers,” also on the CD, includes completed tables and lists to check your work. Although there are no memory tables in this chapter, you will find some memory tables for other chapters.
Define the following key terms from this chapter, and check your answers in the Glossary:
Security Association Database (SADB)
Sharing IPsec with Tunnel Protection, www.cisco.com/en/US/docs/ios/sec_secure_connectivity/configuration/guide/share_ipsec_w_tun_protect.html.