Failover from HQ to Branch

Unanswered Question
Apr 27th, 2009
User Badges:

Dear All,


Please help me to show how can i design diagram for fail over from HQ to Branch.

I mean which equipment that i need to buy .and at my branch i have fiber optic and other VPN connection.the primary connection is fiber optic when the fiber down the VPN connection will be up automatically...

Please help me to let me know ......how can i do on this ?


Best Regards,

Join

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
johnaceti Mon, 04/27/2009 - 08:10
User Badges:

I too am looking assistance in a similar situation.

VPN via DSL in the event of MPLS failure.

stephenshaw Mon, 04/27/2009 - 09:44
User Badges:

Hi,


we setup a VPN tunnel that is now a "backup" to the main MPLS link. MPLS routes are advertised using OSPF and we simply use a floating static route to send traffic to the VPN tunnel when the MPLS fails. In our case the VPN tunnel terminates on a separate firewall from the device terminating the MPLS connection.


Regards,


Steve


johnaceti Mon, 04/27/2009 - 12:27
User Badges:

I would like to see how you tagged the interesting traffic within your config and route map. Could you provide me with an example please?


johnaceti Tue, 04/28/2009 - 05:12
User Badges:

I do not see a router in your design, mine looks similar but instead of the Switches I have 2811 routers with security set.

I was looking at the new command used by the Enzo wireless card "Backup interface" and thought that might be way to do failover but not sure. Mine needs to switch to vpn backup upon Layer3 failure not just sync.

Marwan ALshawi Tue, 04/28/2009 - 05:22
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, December 2015

the easy way based on your requirment is using HSRP

make the lease line router the active router nthe HSRP group and the VPN router the standby

users will use the virtuall IP addrees of that HSRP


regarding whihc router of cisco to use

hte answer depend on the size of the network and required functionalities


HTH

Actions

This Discussion