DMVPN With Internet In A Separate VRF

Jump to navigation Jump to search

This is the complementary to Hosting Multiple DMVPNs and DMVPN With Multiple VRFs.

Let's say you want to have your Internet connection isolated in a VRF. A couple scenarios why:

  • You want to use the global table for your private traffic.
  • You're using certain Cisco features that don't work in VRF's. For example, TACACS in some code versions
  • You want the added security of having your inside and outside traffic separated by a VRF boundary.
  • You want to prevent the local users from using the local internet feed, and force them through some firewalls and content filters at your head office.
  • You're an ISP and want to keep everything isolated by VRFs, including Internet. That allows you to use your global table just for MPLS.


First, set up your Internet VRF:

 rd 1:1
interface FastEthernet0
 ip vrf forwarding INTERNET
 ip address
ip route vrf INTERNET name DEFAULT_ROUTE

Everything else is configured like any of my other DMVPN examples, with the exception of two things.

Firstly, instead of defining a standard ISAKMP crypto key with the crypto isakmp key ... command, you'll create a keyring and associate it with a VRF:

 pre-shared-key address key aw3s0m3crypt0k3y

Secondly, you need to associate the encapsulated tunnel traffic with the VRF. This command tells the router which VRF to use for sending the packets out after they have been given a GRE header and encrypted. This is not the same as the ip vrf forwarding <VRF> command, which tells the router which VRF the packets should go in to after they have been received from the internet, decrypted, and have had the GRE header removed. Both commands can be applied to the interface if there are VRFs for the internet and private side.

interface Tunnel0
 tunnel vrf INTERNET