Replication of VPN configuration
Some embodiments provide a method for automatically configuring VPN gateways. The method receives a first configuration for a first VPN gateway located at a first datacenter. The configuration includes configuration data for a first set of VPNs connecting a first set of networks at the first datacenter to other networks at other datacenters. The method automatically modifies the configuration data to generate a second configuration for a second VPN gateway. The method configures the second VPN gateway using the second configuration to setup a second set of VPNs connecting a second set of networks to the other networks at the other datacenters.
1. A method comprising:
receiving a first configuration for a first virtual private network (VPN) gateway located at a first datacenter, the first configuration comprising configuration data for a first plurality of VPNs connecting a first set of networks at the first datacenter to a plurality of other networks at a plurality of other datacenters;
automatically modifying the configuration data to generate a second configuration for a second VPN gateway; and
configuring the second VPN gateway using the second configuration to setup a second plurality of VPNs connecting a second set of networks to the plurality of other networks at the plurality of other datacenters;
wherein the method is performed by a management application that manages the first datacenter; and
wherein automatically modifying the configuration data comprises:
determining whether the first VPN gateway uses a set of digital certificates for authentication; and
when the first VPN gateway uses the set of digital certificates for authentication, generating a set of new certificates for the second VPN gateway.
2. The method of claim 1 , wherein the second VPN gateway and the second set of networks are located at a second, different datacenter.
3. The method of claim 2 , wherein the first and second datacenters are a first virtual datacenter and a second virtual datacenter operating in one or more public cloud datacenters.
4. The method of claim 3 , wherein the second virtual datacenter replaces the first virtual datacenter, wherein the first virtual datacenter is removed from the one or more public cloud datacenters after the second virtual datacenter becomes operational.
5. The method of claim 3 , wherein the second virtual datacenter replicates the first virtual datacenter as a backup to the first virtual datacenter.
6. The method of claim 1 , wherein the second VPN gateway and the second set of networks are also located at the first datacenter.
7. The method of claim 1 , wherein automatically modifying the configuration data comprises modifying a local network address for a plurality of VPN configurations to match a network address associated with the second VPN gateway.
8. The method of claim 1 , wherein automatically modifying the configuration data comprises determining whether each VPN in the configuration data is a policy-based VPN or a route-based VPN.
9. The method of claim 8 , wherein automatically modifying the configuration data comprises further comprises, for each policy-based VPN, modifying a set of local networks that the policy-based VPN connects to another datacenter based on network addresses associated with the second set of networks.
10. The method of claim 8 , wherein automatically modifying the configuration data further comprises, for each of a set of route-based VPNs, modifying routing protocol session settings to match information associated with the second VPN gateway.
11. The method of claim 1 , wherein automatically modifying the configuration data comprises, for each VPN of a set of the first plurality of VPNs:
determining a vendor identifier for a remote VPN gateway for the VPN; and
when the vendor identifier indicates that the remote VPN gateway will need to be manually configured to connect to the second VPN gateway, using a dummy value for a network address of the remote VPN gateway in the modified configuration data for the VPN and disabling the VPN.
12. A non-transitory machine-readable medium storing a program for execution by at least one processing unit, the program comprising sets of instructions to be performed by a management application for:
receiving a first configuration for a first virtual private network (VPN) gateway located at a first datacenter, the first configuration comprising configuration data for a first plurality of VPNs connecting a first set of networks at the first datacenter to a plurality of other networks at a plurality of other datacenters;
automatically modifying the configuration data to generate a second configuration for a second VPN gateway; and
configuring the second VPN gateway using the second configuration to setup a second plurality of VPNs connecting a second set of networks to the plurality of other networks at the plurality of other datacenters;
wherein the set of instructions for automatically modifying the configuration data comprises sets of instructions for:
determining whether the first VPN gateway uses a set of digital certificates for authentication; and
when the first VPN gateway uses the set of digital certificates for authentication, generating a set of new certificates for the second VPN gateway.
13. The non-transitory machine-readable medium of claim 12 , wherein:
the second VPN gateway and the second set of networks are located at a second, different datacenter; and
the first and second datacenters are a first virtual datacenter and a second virtual datacenter operating in one or more public cloud datacenters.
14. The non-transitory machine-readable medium of claim 13 , wherein the second virtual datacenter replaces the first virtual datacenter, wherein the first virtual datacenter is removed from the one or more public cloud datacenters after the second virtual datacenter becomes operational.
15. The non-transitory machine-readable medium of claim 13 , wherein the second virtual datacenter replicates the first virtual datacenter as a backup to the first virtual datacenter.
16. The non-transitory machine-readable medium of claim 12 , wherein the set of instructions for automatically modifying the configuration data comprises a set of instructions for modifying a local network address for a plurality of VPN configurations to match a network address associated with the second VPN gateway.
17. The non-transitory machine-readable medium of claim 12 , wherein the set of instructions for automatically modifying the configuration data comprises a set of instructions for determining whether each VPN in the configuration data is a policy-based VPN or a route-based VPN.
18. The non-transitory machine-readable medium of claim 17 , wherein the set of instructions for automatically modifying the configuration data comprises further comprises a set of instructions for modifying, for each policy-based VPN, a set of local networks that the policy-based VPN connects to another datacenter based on network addresses associated with the second set of networks.
19. The non-transitory machine-readable medium of claim 17 , wherein the set of instructions for automatically modifying the configuration data further comprises a set of instructions for modifying, for each of a set of route-based VPNs, routing protocol session settings to match information associated with the second VPN gateway.
20. The non-transitory machine-readable medium of claim 12 , wherein the set of instructions for automatically modifying the configuration data comprises sets of instructions for, for each VPN of a set of the first plurality of VPNs:
determining a vendor identifier for a remote VPN gateway for the VPN; and
when the vendor identifier indicates that the remote VPN gateway will need to be manually configured to connect to the second VPN gateway, using a dummy value for a network address of the remote VPN gateway in the modified configuration data for the VPN and disabling the VPN.