09-30-2007 06:40 PM - edited 03-03-2019 06:58 PM
Hi!
I attached a simple network drawing for our network. We are using MPLS/VPN. We have a Central Facility router (CF router) which facilitates our servers. All our remote network (Remote Routers) connects to this router to access our servers. I want to configure the DRC router to be a stand-by if the central router or network will go down, all the routes will be redirected to the DRC network. The DRC network facilitates all the DR servers. This servers replicates all the servers inside Central Facility network. Can you please suggest what is the best solution for this one? Does static route can solve this one? Please help!
Thank you very much!
10-01-2007 09:04 AM
I dont know about others, but I cannot open your drawing. Anyone else open it?
10-01-2007 06:10 PM
10-01-2007 06:42 PM
This may help in your back up design, reliable static routing using object-tracking.
http://www.cisco.com/en/US/products/sw/iosswrel/ps5413/products_feature_guide09186a00801d862d.html
HTH - rate helpfull posts
Jorge
10-01-2007 08:30 PM
tnx for the reply. is it possible to use this guide even we only have one connection?
tnx!
10-02-2007 03:55 AM
you could use this guide, or simply use at each remote site floating static routes with diferent admin distance, routes pointing to most critical servers in CF being primary site with lower admin dist and higher admin dist for DR servers.
10-03-2007 11:14 PM
tnx jorgemcse! i will use the floating static route. just one more question, do i need to setup one more dns server on the DR network so that if the failure will happen on the CF, all the pc that connecting on the CF servers can connect onto servers on the DR automatically. I will just put the server list on the remote routers. is that correct?
10-04-2007 09:37 AM
I don't have a lot of dns architecture experience, most DR sites do differ from one another depending on requirements and how much architecture investment companies are willing to mirror, but I would use an example in our company whereby each remote site do have their own AD/DCHP/DNS including the disaster recovery site. Our DR site do have its own internet vpn, firewalling architecture beside internal links so that access to DR is also accessible from the outside.
HTH - Please rate helpfull posts
Jorge
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide