We help IT Professionals succeed at work.
Get Started

Site to Site to Site VPN with McAfee Enterprise Firewalls

240 Views
Last Modified: 2015-09-16
I have a client with multiple locations and a primary hub we'll call that MAIN. They would like to implement a solution that if their primary location (MAIN) were to have some type of natural disaster they want to be able to reroute all traffic to their offsite DR location which hosts copies of their VMs/Servers/Apps/Etc...

They have their own DR (MAIN DR) site that all sites will route traffic through to the OFFSITE DR so instead of creating a VPN connection from all separate sites to the OFFSITE DR they want to have all sites route traffic through their MAIN DR to the OFFSITE DR. We tried to test this last week but ran into a snag.

SECONDARY SITE (10.0.10.0) <===VPN IPSEC===> MAIN DR (10.0.11.0) <====VPN IPSEC===> OFFSITE DR (10.0.12.0)

The VPN from MAIN DR to OFFSITE DR worked flawlessly, we could get to the backup servers and all services/apps worked without issues. Where we ran into trouble was getting the secondary site up and running. We could communicate back and forth from SECONDARY SITE to MAIN DR but no further.

My question is does the OFFSITE DR need to have the SECONDARY SITE subnet listed in the presented VPNs for traffic to flow properly? Or do I need to setup static routes from SECONDARY SITE to OFFSITE DR? I'm sure this is pretty basic but unfortunately it sort of got dropped in my lap last minute.

Just to be clear IF the MAIN went down. They want to then be able to enable a VPN from the MAIN DR to OFFSITE DR and from the separate sites enable a VPN to the MAIN DR that will give them access to the resources at the OFFSITE DR.

In case I have not explained it well I tried to give a better explanation/diagram below.

Currently 13 locations connect into the MAIN for resources. Every night the servers get copied to the OFFSITE DR site (in another state). The idea is that IF the main site were to burn down, lose power, or any other natural disaster, the 13 locations could enable their VPN to the MAIN DR firewall which is connected to the OFFSITE DR site and continue to work normally. What we do to test is disconnect the VPN from one location to the MAIN and enable to VPN from that location to the MAIN DR. The VPNs come up fine, but from that location you cannot access any resources at the OFFSITE DR. So the path of data should be like this

SECONDARY SITE =====> MAIN DR =====> OFFSITE DR

and

OFFSITE DR =====> MAIN DR =====> SECONDARY SITE

Currently when testing I get this

SECONDARY SITE <====> MAIN DR <=====> OFFSITE DR

SECONDARY SITE <xxxx> OFFSITE DR

Sorry for the poor diagram, but basically I can't get to any of the resources at the OFFSITE DR from the SECONDARY SITE.

I also realize I could just create a tunnel from SECONDARY SITE directly to OFFSITE DR and have it work, but for auditing purposes all traffic needs to run through the MAIN DR to get to the OFFSITE DR.
Comment
Watch Question
This problem has been solved!
Unlock 3 Answers and 5 Comments.
See Answers
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE