# US 10,320,898 B2 · Automated multi-network failover for data centers > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,320,898 B2 - Document ID: US10320898B2 - Status: Granted - Kind: B2 - Application number: 15/174,710 - Filed: 2016-06-06 - Published: 2017-12-07 - Granted: 2019-06-11 - Earliest claimed: 2016-06-06 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Shailan Lala; Thomas B. Edgar; Kalanithi Srinivasan - Web page: https://patentgrep.com/patent/US10320898B2 ## CPC - H04L 67/1036: Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers - H04L 41/0654: using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) - H04L 43/0817: by checking functioning - H04L 43/0876: Network utilisation, e.g. volume of load or congestion level - H04L 45/28: using route fault recovery - H04L 67/1034: Reaction to server failures by a load balancer - H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) - H04L 47/125: by balancing the load, e.g. traffic engineering - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A device may monitor a status of a first data center of a group of data centers. The device may determine, based on the status of the first data center, to cause a failover from the first data center to a second data center. The device may cause a domain name server (DNS) configuration, associated with an external DNS, to be and a set of DNS entries, associated with an internal DNS, to be altered to cause a portion of the network traffic, respectively associated with a first network and a second network of the plurality of networks, to be routed the second data center. The device may cause a load balancer configuration to be altered to cause a portion of the network traffic associated with a third network of the plurality of networks to be redirected from the first data center to the second data center. ## Claims ### Claim 1 A device, comprising: a memory; and one or more processors to: monitor a status of a first data center of a group of data centers, the first data center, of the group of data centers, being associated with receiving network traffic from a plurality of networks; determine, based on the status of the first data center, to cause a failover from the first data center, of the group of data centers, to a second data center of the group of data centers; cause a domain name server (DNS) configuration, associated with an external DNS, to be altered to cause a first plurality of devices, of a first network of the plurality of networks, to route a first portion of the network traffic to the second data center of the group of data centers, the external DNS being external to the group of data centers; cause a set of DNS entries, associated with an internal DNS, to be altered to cause a second plurality of devices, of a second network of the plurality of networks, to route a second portion of the network traffic to the second data center of the group of data centers, the internal DNS being internal to the group of data centers; cause a load balancer configuration, associated with a load balancer of the first data center, to be altered to cause a third portion of the network traffic, associated with a third plurality of devices, of a third network of the plurality of networks, to be redirected from the first data center to the second data center; and determine whether the failover is successful based on testing the internal DNS and receiving a response from the internal DNS and based on determining whether the network traffic is being routed to the second data center. ### Claim 2 (depends on 1) The device of claim 1, where the one or more processors are further to: determine, based on monitoring the status of the first data center, a failure associated with a threshold quantity of persistent connections associated with a particular network of the plurality of networks; and where the one or more processors, when determining to cause the failover, are to: determine to cause the failover based on determining the failure associated with the threshold quantity of persistent connections. ### Claim 3 (depends on 1) The device of claim 1, where the one or more processors, when determining whether the failover is successful, are to: determine a failure associated with altering the set of DNS entries; and where the one or more processors are further to: roll back the set of DNS entries to cause subsequent network traffic to be routed to the first data center based on determining the failure. ### Claim 4 (depends on 1) The device of claim 1, where the one or more processors, when monitoring the status of the first data center, are to: cause information to be transmitted, via a particular network of the plurality of networks, toward the group of data centers; determine that the information failed to be routed to the first data center based on transmitting the information toward the group of data centers; and where the one or more processors, when determining to cause the failover, are to: determine to cause the failover based on determining that the information failed to be routed to the first data center. ### Claim 5 (depends on 1) The device of claim 1, where the one or more processors are to: determine that a threshold quantity of computing resources of the first data center are associated with a failure; and where the one or more processors, when determining to cause the failover, are to: determine to cause the failover based on determining that the threshold quantity of computing resources are associated with the failure. ### Claim 6 (depends on 1) The device of claim 1, where the one or more processors are further to: override another failover from the second data center to another data center, of the group of data centers, after altering the set of DNS entries. ### Claim 7 (depends on 1) The device of claim 1, where the plurality of networks includes at least one of: a wired customer network, a wireless customer network, or a control network. ### Claim 8 (depends on 1) The device of claim 1, where the internal DNS is a DNS service provided by a particular data center of the group of data centers; and where causing the set of DNS entries to be altered comprises: causing an updated DNS entry to be included in the set of DNS entries, of the DNS service, the updated DNS entry being associated with the second data center. ### Claim 9 A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors, cause the one or more processors to: determine, for a first data center of a group of data centers, that a condition associated with causing a failover from the first data center to a second data center, of the group of data centers, is satisfied, the first data center, of the group of data centers, being associated with receiving network traffic from a plurality of networks; cause a domain name server (DNS) configuration, associated with an external DNS, to be altered to cause a first plurality of devices, of a first network of the plurality of networks, to route a first portion of the network traffic to the second data center of the group of data centers, the external DNS being external to the group of data centers; cause a set of DNS entries, associated with an internal DNS, to be altered to cause a second plurality of devices, of a second network of the plurality of networks, to route a second portion of the network traffic to the second data center of the group of data centers, the internal DNS being internal to the group of data centers; cause a load balancer configuration, associated with a load balancer of the first data center, to be altered to cause a third portion of the network traffic, associated with a third plurality of devices, of a third network of the plurality of networks, to be redirected from the first data center to the second data center; and determine whether the failover is successful based on testing the internal DNS and receiving a response from the internal DNS and based on determining whether the network traffic is being routed to the second data center. ### Claim 10 (depends on 9) The non-transitory computer-readable medium of claim 9, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: transmit a particular quantity of network traffic to the group of data centers prior to determining that the condition associated with causing the failover is satisfied; determine, based on transmitting the particular quantity of network traffic to the group of data centers, that the first data center is associated with an unhealthy status; and where the one or more instructions, that cause the one or more processors to determine that the condition associated with causing the failover is satisfied, cause the one or more processors are to: determine that the condition associated with causing the failover is satisfied based on determining that the first data center is associated with the unhealthy status. ### Claim 11 (depends on 10) The non-transitory computer-readable medium of claim 10, where the one or more instructions, that cause the one or more processors to determine that the first data center is associated with the unhealthy status, cause the one or more processors to: determine that the particular quantity of network traffic failed to be received at the first data center; and determine that the first data center is associated with the unhealthy status based on determining that the particular quantity of network traffic failed to be received at the first data center. ### Claim 12 (depends on 10) The non-transitory computer-readable medium of claim 10, where the one or more instructions, that cause the one or more processors to determine that the first data center is associated with the unhealthy status, cause the one or more processors to: determine that a computing resource of the first data center failed to correctly respond to the particular quantity of network traffic; and determine that the first data center is associated with the unhealthy status based on determining that the computing resource of the first data center failed to correctly respond to the particular quantity of network traffic. ### Claim 13 (depends on 9) The non-transitory computer-readable medium of claim 9, where the first data center is associated with an active configuration and the second data center is associated with a standby configuration; and where the one or more instructions, when executed by the one or more processors, cause the one or more processors to: cause the second data center to be transferred to the active configuration. ### Claim 14 (depends on 9) The non-transitory computer-readable medium of claim 9, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: override a subsequent failover for a threshold period of time. ### Claim 15 A method, comprising: monitoring, by a device, a status of a first data center of a group of data centers, the first data center, of the group of data centers, being associated with receiving network traffic from a plurality of devices of a plurality of networks; determining, by the device and based on the status of the first data center, to cause a failover from the first data center, of the group of data centers, to a second data center of the group of data centers; causing, by the device, a domain name server (DNS) configuration, associated with an external DNS, to be altered to cause a first plurality of devices, of a first network of the plurality of networks, to route a first portion of the network traffic to the second data center of the group of data centers, the external DNS being external to the group of data centers; causing, by the device, a set of DNS entries, associated with an internal DNS, to be altered to cause a second plurality of devices, of a second network of the plurality of networks, to route a second portion of the network traffic to the second data center of the group of data centers, the internal DNS being internal to the group of data centers; causing, by the device, a load balancer configuration, associated with a load balancer of the first data center, to be altered to cause a third portion of the network traffic, associated with a third plurality of devices, of a third network of the plurality of networks, to be redirected from the first data center to the second data center; and determining, by the device, whether the failover is successful based on testing the internal DNS and receiving a response from the internal DNS and based on determining whether the network traffic is being routed to the second data center. ### Claim 16 (depends on 15) The method of claim 15, where monitoring the status of the first data center comprises: performing an application programming interface (API) call to an API associated with the first data center to determine the status of the first data center. ### Claim 17 (depends on 15) The method of claim 15, where monitoring the status of the first data center comprises: transmitting data toward the first data center via a particular network of the plurality of networks; and identifying the status of the first data center based on transmitting the data toward the first data center via the particular network. ### Claim 18 (depends on 15) The method of claim 15, further comprising: determining, after causing the DNS entries to be altered, that a threshold period of time has elapsed; determining that the first data center is associated with a healthy status after determining that the threshold period of time has elapsed; and causing another alteration to the DNS entries to cause network traffic to be directed toward the first data center based on determining that the first data center is associated with the healthy status. ### Claim 19 (depends on 9) The non-transitory computer-readable medium of claim 9, where the one or more instructions, that cause the one or more processors to determine whether the failover is successful, cause the one or more processors to: determine a failure associated with altering the set of DNS entries and where the one or more instructions, when executed by the one or more processors, cause the one or more processors to: roll back the set of DNS entries to cause subsequent network traffic to be routed to the first data center based on determining the failure. ### Claim 20 (depends on 15) The method of claim 15, where determining whether the failover is successful comprises: determining a failure associated with altering the set of DNS entries; and further comprising: rolling back the set of DNS entries to cause subsequent network traffic to be routed to the first data center based on determining the failure.