Figure 1 0 shows a typical scenario below this scenario is common amongst service providers and geographic separation is normally sold as part of the solution.
Front door vrf.
Under the geographic separation scenario eompls would normally be used to link the two ip networks.
When you are using a front door vrf you can t define the key using the old crypto isakmp key command.
Router ospf 100 vrf pipe router id 13 13 13 13 4.
Modify the tunnel interface to stitch the tunnel to the front door vrf.
All we did is stitch them together.
The ivrf of these tunnels can be different and.
Create front door vrf named fvrf on r1 and r4.
The crypto isakmp key command doesn t support vrfs.
As you can see we did not move the tunnel11 interface from the global routing table to the routing table for vrf pipe.
Sets the destination address of a tunnel.
Configuring physical interface on r1 and r4 to be vrf aware.
The fvrf of all these tunnels is the same and is set to the vrf that is confi gured on that interface.
Optional associates a vpn routing and forwarding instance vrf with a specific tunnel destination interface or subinterface.
If you don t use a keyring you won t be able to apply the key to the isakmp profile so the ipsec configuration won t have access to a.
The key must be defined in a keyring.
Router config if tunnel destination ip address.
There are other benefits of this design and it s quite commonly used in the sp enterprise world.
Vrf name name assigned to the vrf.
This step is only required when configuring a front door vrf fvrf.
If no vrf aware config is used everything is done in the global vrf and all interfaces are in the global vrf.
By using front door vrf we are isolating transport network usually internet facing and this allows us to configure default route that won t interfere with routing in our global table.
The routing instance that is used if no specific vrf is defined.
R1 sh runn int fa0 0.
Front door vrf or outside vrf the vrf that contain the encrypted traffic.
Note front door vrf fvrf is only supported as of cisco ios release 12 2 33 sxh and later.