I have a T1 leased line to a partner location. The leased line is terminated on a router outside my firewall. Now as a backup ican i configure an IPsec VPN to the same partner site and have a floating static route so that traffic gets routed via the IPsec VPN in case the T1 link fails.
Is there any potential bottleneck in doing this? Please advice.
If the VPN is provided by an external devices, such as a firewall or another router, there is no problem doing this. However, if the VPN is implemented on the same router as the path through the leased line, I found that the access list used to define the VPN also tried to VPNize the leased line, which was not desired. Maybe someone else can point out a way around this restriction?
In the meantime, you may find the points brought out in the redundant VPN whitepaper on my web site useful, even though what you are trying to do is slightly different, and consequently the specific examples given can't be used directly.
Thanks for your response. If I statically route the remote branch traffic to a GRE tunnel Tunnel with a higher administrative distance call the crypto map at this tunnel then will i overcome the bottleneck mentioned by you?
The basic idea is OK the problems might come in the detail, the best method I have used is the same floatinf static routes but use ipsec through GRE tunnels then you can point the routes for the VPN'd networks into the tunnel i.e.
'ip route x.x.x.x mask int tunel (number of tunnel int.) if you have configured your crypto maps correctly (a hair pulling process) the theory is that the traffic you point down the tunnel is VPN'd and the T1 traffic is not, this is assuming you are wanting this on the same router.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...