High Availability Network Address Translation

The described system ensures continuous network and application sessions by synchronizing NAT and TCP states between active and standby nodes, addressing the issue of session disruptions and data loss in cloud computing environments.

KR103047226B1Active Publication Date: 2026-11-10ALKUS GMBH
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
KR1020237009415
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-08-21
Filing Date
2021-08-18
Publication Date
2026-11-10
Estimated Expiration
2041-08-18

AI Technical Summary

Technical Problem

Existing network address translation (NAT) systems in cloud computing environments experience long timeouts and data loss during node failures, leading to interruptions in network sessions and application sessions.

Method used

Implementing a system where an active node maintains NAT tables and TCP states with a standby node, ensuring seamless failover by maintaining consistent data structures and sub-interfaces, allowing the standby node to take over without disrupting ongoing sessions.

Benefits of technology

Enables continuous network and application sessions by minimizing latency and data loss during node failures, as the standby node takes over with synchronized NAT and TCP state information, maintaining session integrity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure R1020237009415_ABST
    Figure R1020237009415_ABST
Patent Text Reader

Abstract

A computing environment, such as a cloud computing environment, may include nodes that perform NAT for multiple workloads. The active node performs NAT for workloads and maintains a NAT table. The active node can create sub-interfaces for workloads and function as a DHCP server. The NAT table and sub-interfaces can be recreated on a standby node. When a failure is detected, the routing table is updated to instruct workloads to connect to the standby node, and traffic can continue to be processed by the standby node without interrupting network or application sessions.
Need to check novelty before this filing date? Find Prior Art

Description

Background Technology

[0001] In many situations, it is advantageous to have a public address used for an entity different from the private address used for the entity. The public address can be used as the source and destination addresses for packets transmitted and received over an external network. The private address can be used as the source and destination addresses for packets transmitted and received over an internal network. The conversion between public and private addresses, known as NAT (Network Address Translation), can be performed by networking elements such as routers, switches, network gateways, or other computing devices.

[0002] Network address translation is particularly useful for applications running in cloud computing environments, as long as the network environment in which the application runs is virtualized. Applications running on on-premise equipment can also benefit from address translation. Brief explanation of the drawing

[0003] To facilitate a better understanding of the advantages of the present invention, a more specific description of the invention, as briefly described above, will be provided with reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings illustrate only typical embodiments of the invention and are therefore not to be construed as limiting its scope, the invention will be described and explained with additional specificities and details through the use of the accompanying drawings, wherein, FIG. 1 is a schematic block diagram of a network environment for implementing low-latency NAT according to an embodiment of the present invention. FIG. 2 is a schematic block diagram illustrating the performance of NAT failover between an active node and a standby node according to an embodiment of the present invention. FIG. 3 is a process flowchart of a method for performing NAT failover between an active node and a standby node according to an embodiment of the present invention. FIG. 4 is a schematic block diagram of components implementing an alternative approach for NAT failover between an active node and a standby node according to one embodiment of the present invention. FIG. 5 is a process flowchart of an alternative method for performing NAT failover between an active node and a standby node performing NAT according to an embodiment of the present invention. FIG. 6 is a process flowchart of another alternative method for performing NAT failover between an active node and a standby node performing NAT according to one embodiment of the present invention. FIG. 7 is a schematic block diagram of a computer system suitable for implementing methods according to embodiments of the present invention. Specific details for implementing the invention

[0004] It will be readily understood that the components of the present invention, as outlined and illustrated in the drawings herein, can be arranged and designed in a wide variety of different configurations. Accordingly, the following more detailed description of the embodiments of the present invention shown in the drawings is not intended to limit the scope of the present invention as claimed, but merely illustrates specific examples of embodiments currently being considered according to the present invention. The embodiments currently described will be best understood by reference to the drawings, in which similar parts are designated by similar numbers throughout.

[0005] Embodiments according to the present invention may be implemented as devices, methods, or computer program products. Accordingly, the present invention may take the form of an embodiment that is entirely hardware-based, entirely software-based (including firmware, resident software, microcode, etc.), or a combination of software and hardware aspects that may all be broadly referred to herein as a "module" or "system." Additionally, the present invention may take the form of a computer program product implemented on any type of representation medium having computer-usable program code implemented within the medium.

[0006] Any combination of one or more computer-usable or computer-readable media may be used. For example, a computer-readable medium may include one or more of a portable computer diskette, a hard disk, a random access memory (RAM) device, a read-only memory (ROM) device, an erasable programmable read-only memory (EPROM or flash memory) device, a portable compact disc read-only memory (CDROM), an optical storage device, and a magnetic storage device. In selected embodiments, a computer-readable medium may include any non-transient medium capable of containing, storing, communicating, propagating, or transmitting a program for use by or in connection with an instruction execution system, device, or device.

[0007] Computer program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages, and may also use descriptive or markup languages ​​such as HTML, XML, JSON, etc. The program code may be executed entirely as a standalone software package on a computer system, on a standalone hardware unit, partially on a remote computer located at a certain distance from the computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the computer through any type of network including a local area network (LAN) or a wide area network (WAN), or a connection to an external computer may be made (e.g., over the Internet using an Internet Service Provider).

[0008] The present invention is described below with reference to flowchart examples and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart examples and / or block diagrams, and combinations of blocks in the flowchart examples and / or block diagrams, may be implemented by computer program instructions or code. These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to create a machine, and instructions executed through the processor of the computer or other programmable data processing device create means for implementing specific functions / actions in the blocks of the flowchart and / or block diagram.

[0009] These computer program instructions may also be stored in a non-transient computer-readable medium capable of instructing a computer or other programmable data processing device to function in a specific manner, so that the instructions stored in the computer-readable medium produce a manufactured article comprising instruction means for implementing a specific function / operation in a flowchart and / or block diagram block or in blocks.

[0010] Computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to create a computer-implemented process, thereby providing processes for implementing specific functions / operations in blocks or blocks of a flowchart and / or block diagram for instructions executed on the computer or other programmable device.

[0011] FIG. 1 illustrates an example of a network environment (100) in which low-latency network address translation (NAT) can be performed. The network environment (100) may include a plurality of virtual private clouds (VPCs) (102) running on a cloud computing platform (104). The cloud computing platform (104) may be any cloud computing platform known in the art, such as Amazon Web Services (AWS), Microsoft Azure, Google Cloud, or other cloud computing platforms. As known in the art, the cloud computing platform (104) provides virtualized computing and storage resources that can be accessed by customers via a network (106). A VPC (102) can function as a logically isolated section of a cloud computing platform (104) that includes internet protocol (IP) addresses, subnets, routing tables, network gateways, and other networking elements, which is isolated from other parts of the cloud computing platform and therefore does not need to be globally unique.

[0012] Each VPC (102) can run one or more nodes (108, 110, 112). Each of the nodes (108, 110, 112) may be a virtual machine, a container, or an application running within the VPC (102), as well as another execution environment running within the VPC (102). Each node (108, 110, 112) may function as a networking element and may provide a gateway between the VPC (102) and another VPC (102), as well as to an external network (106) connected to the cloud computing platform (104).

[0013] In the illustrated embodiment, one or more nodes are hub nodes (108) connected to an external network (106), and other spoke nodes (110, 112) can send and receive traffic to and from the external network (106) through the hub node (108). In the illustrated embodiment, the hub node (108) is located in a different VPC from the spoke nodes (110, 112). In some embodiments, the spoke nodes (110, 112) each have an established virtual private network (VPN) session with the hub node (108). For example, the VPN sessions may follow the layer two tunneling protocol (L2TP).

[0014] Each VPC (102) may additionally run one or more workloads (114). Each workload (114) may communicate with workloads of other VPCs (102) and an external network (106) by a node (110, 112) within the VPC hosting the workload (114). Thus, each workload (114) may have a network connection, such as a virtualized local area network (VLAN) connection to the node (110, 112) of the VPC. Each workload (114) may be an application, a daemon, a network service, an operating system, a container, or any computing process that can be executed by a computer.

[0015] In the illustrated embodiments, one node (110) may be active for one or more workloads (114), while another node (112) is a backup or standby node (112) for the node (110). The active node (110) and the standby node (112) may be located within the same VPC (102) so that workloads can be connected to either of the nodes (110, 112) through the internal virtual network of the VPC (102).

[0016] As discussed in this specification, the active node (110) may maintain network sessions with components located outside the VPC (102) and possibly outside the cloud computing platform (104). The network session may be a Transmission Control Protocol (TCP) session with a TCP server (116) connected to an external network (106). The network session may additionally or alternatively be an application session established between an external application and a workload (114) connected to the TCP server (116).

[0017] The approach described herein enables the workload (114) to maintain a session even if the active node (110) fails. In some cases, a failure of a TCP session can result in a long timeout period before the parties to the session can perform a handshaking to re-establish the session. Similarly, an application session can have a long timeout period before applications attempt to re-establish a new application session. The process of re-establishing a new application session is time-consuming and can result in data loss. Therefore, the ability to handle the failure of the node (110, 112) without interrupting network sessions is a significant benefit.

[0018] Referring to FIG. 2, the active node (110) may maintain various data structures describing the status of network interfaces managed by the active node (110). This may include a NAT table (200a) containing a mapping between the private IP address (located within the VPC (102)) and the public IP address (address used outside the VPC (102)) of each workload (114). The allocations of one or both of the public and private IP addresses may be dynamic so that allocations can be made and released by workloads according to communication requirements.

[0019] For example, the hub node (108) can operate as a dynamic host configuration protocol (DHCP) server. The active node (110) can operate as a dynamic NAT server. Thus, a public IP address leased to the active node (110) by the DHCP server can be dynamically mapped by the active node (110) to a private IP address of a workload (114). The active node (110) can map the public IP address to a different workload (114), for example, when the first workload completes transmission or expiration of a predefined time period. The public IP allocation made by the hub node (108) can be stored in the NAT table (200a) of the active node (110) for each allocation of the public IP address, so that the public IP address is mapped to the private IP address of the workload (114) to which the public IP address was allocated by the active node (110) when dynamic NAT is performed on behalf of the workload (114).

[0020] In some embodiments, a private IP address may be assigned to a sub-interface of a VPN session connecting the active node (110) to the hub node (108). For example, the hub node (108) may create a sub-interface for a workload (114) that includes the workload's MAC (Media Access Control) address. The sub-interface may also be assigned one or both of the public IP address and the private IP address assigned to the workload (114). For each sub-interface created on the active node (110), the hub node (108) may create another sub-interface on the VPN connection between the hub node (108) and the standby node (112) having the same MAC address and the same public IP address and private IP address. In some embodiments, a sub-interface having the same MAC address is created on the standby node (112), which then attempts to acquire one or both of the public and private IP addresses for the interface. Then, the hub node (108) will assign the same public and private IP addresses as the active node (110) to the sub-interfaces according to DHCP because the MAC address of the standby node (112) is the same as the interface on the active node (110).

[0021] The active node (110) updates the routing table (204) so ​​that the default route for the workloads (114) points to the network interface of the active node (110). The routing table (204) can likewise refer to the active node (110) as the network gateway for the VPC (102).

[0022] The active node (110) may also maintain a TCP state (202a). The TCP state (202a) may maintain the state of TCP connections to the public IP addresses of the workload (114). As is known in the art, a TCP connection may implement a state machine that changes according to the interactions between the components connected by the TCP connection. Thus, the TCP state (202a) may be this state machine for each TCP connection of each workload (114).

[0023] The standby node (112) may maintain its own copies of the NAT table (200a) and TCP states (202b). The active node (110) may communicate these changes to the standby node (112) when changes to the TCP states (202a) occur, and the standby node (112) may update the TCP states (202b) with these updates. In some embodiments, the communication of updates to the TCP states is performed by the active node (110) and transmitted through the hub node (108). In other embodiments, the updates are performed by direct communication between the nodes (110, 112).

[0024] In addition to sharing updates for the NAT table (200a) and TCP state (202a), the nodes (110, 112) may communicate with each other to enable the detection of failure of the active node (110). This communication may be performed using the same connection used to share updates for the NAT table (200a) and TCP state (202a), and may be a direct connection within the VPC (102) or through a hub node (108). This communication may include "still alive" messages transmitted from the active node (110) to the standby node (112) at predefined intervals (e.g., 100 ms to 2 seconds). Thus, the standby node (112) may detect a failure of the active node (110) in response to not receiving a still alive message within a threshold time period from the last received still alive message. In other embodiments, the standby node (112) will periodically (e.g., every 100 ms to 2 seconds) send a query to the active node (110) and detect a failure of the active node (110) in response to not receiving a response to the query within a threshold time period from when the query was sent.

[0025] Referring to FIG. 3, and continuing to refer to FIG. 2, the active node (110) and the standby node (112) may implement the illustrated method (300). The method (300) may include the step (302) of maintaining consistency between NAT tables (200a, 200b) and between TCP states (202a, 202b). As previously described, this may include sending updates from the active node (110) to the standby node (112) when the NAT table (200a) and the TCP state (202a) change. These updates may be sent directly or through a hub node (108). The updates may include adding and deleting entries in the NAT table (200b) when corresponding entries are created and deleted in the NAT table (200a). Updates may also include creating and deleting state machines for TCP connections when TCP connections are created and terminated on the active node (110). Step (302) may further include creating and deleting sub-interfaces for workloads (114) on the standby node (112) as described above when the corresponding sub-interface on the active node is created and deleted.

[0026] The method (300) may include a step (304) of monitoring the status of the active node (110) by a standby node (112). This may include a step of monitoring still-alive messages transmitted by the active node (110). This may additionally or alternatively include a step of monitoring responses to queries transmitted by the standby node (112).

[0027] The method (300) may include the step (306) of a standby node (112) detecting a failure of the active node (110). As mentioned above, this may include failing to receive a still-alive message within a threshold time period from a previous still-alive message, or failing to receive a response to a query within a threshold time period from when the query was sent.

[0028] When a failure is detected (306), the method (300) may include the step (308) of updating the routing table (204) to replace the reference to the active node (110) with a reference to the standby node (112). In particular, this may include the step of referencing the standby node (112), for example, the private IP address of the standby node (112), as the default gateway for the VPC (102).

[0029] Now, the standby node (112), which is the active node for the VPC (102), will then process traffic received from the workload (114) and from the external network (106) according to a copy of the NAT table (200b) and TCP states (202b) (310). In particular, the standby node (112) may perform the functions described herein for the active node (110) in functioning as a network gateway, including performing NAT, managing TCP state machines, and any of the other functions described herein for the active node (110).

[0030] Note that some dropped packets may occur during the transition from the active node (110) to the standby node (112). However, the TCP protocol provides retransmission of the dropped packets. Therefore, the TCP session remains active and does not need to be re-established. Likewise, since the same sub-interfaces are available for each workload (114) on the standby node (112), any application sessions can continue to operate uninterrupted. The lack of interruption is also due to the NAT table (200b) remaining the same, so applications configured to communicate with the workload's public IP address do not need to acquire new addresses and establish new application and TCP sessions for the new addresses. In some embodiments, after the standby node (112) becomes the active node, it can also function as a NAT server for the workloads of the VPC (102).

[0031] As mentioned above, sub-interfaces for VPN connections between nodes (110, 112) and the hub node (108) can be created for each workflow (114), so that for each sub-interface created on the VPN connection between the active node (110) and the hub node (108), a corresponding sub-interface having the same public and private IP addresses and MAC addresses is created on the VPN connection between the standby node (112) and the hub node (108). Accordingly, step (310) may include, for each workload (114), transmitting traffic (e.g., TCP packets) through the sub-interface of the standby node (112) having the same public and private IP addresses and MAC addresses as the sub-interface of the active node (110) previously used by each workload. Thus, the delay caused by creating a new sub-interface when a failure occurs is avoided.

[0032] Changes in the routing of traffic to and from the workload (114) may occur because the standby node (112) becomes the new default gateway and the MAC address and private IP address of the workload (114) remain the same: traffic received by the standby node (112) that references the MAC address or private IP address of the workload (114) will be routed through the appropriate sub-interface associated with the said MAC address and private IP address.

[0033] In some embodiments, when the active node (110) resumes operation after a failure, the active node (110) may function as a standby node, that is, receive redundant information regarding NAT tables (200b), TCP states (202b), and / or redundant sub-interfaces based on the VPN connection to the hub node (108) described above in relation to the standby node (112). If this information is up to date for the standby node (112), the active node (110) may be reactivated and the standby node (112) will function as a standby node again.

[0034] The embodiments of FIGS. 1 through 3 are illustrated as being implemented in a cloud computing platform (104). This approach can also be implemented by any computing nodes including connected on-premises equipment, so that one computing node can act as a hub node for spoke nodes as described above.

[0035] FIG. 4 illustrates a configuration in which the active node (110) and standby node (112) are not connected by a hub node (108). The nodes (110, 112) may run within a VPC (102) or on individual computing devices of a premises network. In the illustrated configuration, a static pool of IP addresses is assigned to the active node (110) and standby node (112), and the active node (110) functions as a DHCP server and a NAT server for workloads (114).

[0036] In the illustrated embodiment, each node (110, 112) includes a control plane (400) capable of implementing logic to perform the functions of each node (110, 112) as the active node (110) and standby node (112) as described herein. Regardless of which node (110, 112) is active, the control plane can operate as a DHCP and NAT server for a workload (114) connecting to an external network (106) through the active node (110).

[0037] Each node (110, 112) may contain or access a database (402). The database (402) may be synchronized so that the database (402) of the standby node (112) is updated identically to the database (402) of the active node (110). For example, the database (402) may be a REDIS database configured to be synchronized with each other.

[0038] The active node (110) may create a NAT table, such as a secure NAT (SNAT) table, that maps private addresses to MAC addresses of workloads (114) and maps private addresses assigned to workloads (114) to public addresses assigned to said workloads (114). The SNAT mappings may also be recorded in the kernel IP table of the device (actual or virtual) running the active node (110). As mentioned above, there may exist a static pool (408) of IP addresses managed by the active node (110) such that public and / or private IP addresses are returned to the pool (408) and later assigned to a second workload (114) after the first workload assigned to the public and / or private IP addresses completes its tasks or the lease for the public and / or private IP addresses expires.

[0039] Nodes (110, 112) may further include a forwarding information base (FIB) (406) or other data structure that defines the routing of packets received by the nodes (110, 112). Thus, the FIB (406) may be configured to route packets addressed to external IP addresses to an external network (106) and to route received packets addressed to public IP addresses to private IP addresses of workloads (114) to which public IP addresses are assigned in the SNAT table (404).

[0040] Other information, such as the SNAT table (404), the FIB (406) of the active node (110), and TCP status information, can be recorded in the database (402) of the active node (110). Then, the database (402) can be synchronized with the database (402) of the standby node (112). Then, the standby node (112) can populate its own SNAT table (404) and FIB (406) according to the database (402) to prepare for a failure of the active node (110).

[0041] When a specific node (110, 112) is an active node, ingress traffic (410) is received, converted according to the SNAT table, and then output as output traffic (412) to the egress port or kernel of a computing device (real or virtual) running the node (110, 112) defined in the FIB (406).

[0042] Referring to FIG. 5, the illustrated method (500) can be performed using the system illustrated in FIG. 4. The method (500) can be executed by the active node (110), except when operations are assigned to the standby node (112).

[0043] The method (500) may include a step (502) of assigning IP addresses to each workload (114) from a static IP pool. This may be performed according to DHCP or other IP configuration protocols. The step (502) may further include a step of creating entries in an SNAT table (404). The method (500) further includes a step (504) of writing entries in an SNAT table (404) within a synchronized database (402). As a result, data within the database (402) will be replicated to the database (402) of the standby node (112).

[0044] For each workload (114) to which an IP address is assigned in step (502), the active node may additionally create a sub-interface for the workload (114) to which a static IP (e.g., a static public IP address) is assigned and which references the MAC address of the workload (114) (506). Traffic to and from the workload (114) may thus be routed by the active node (110) through the sub-interface. A corresponding sub-interface referencing the public IP address assigned to the workload (114) and the MAC address of the workload (114) may also be created on the standby node (112). The private IP address of the workload (114) may also be associated with the sub-interface of the node (110, 112).

[0045] The reverse of steps (504 and 506) is also performed: when workloads (114) give up private and / or public IP addresses, the corresponding entries in the SNAT table (404) may be deleted, and sub-interfaces for the workloads (114) may likewise be deleted. The corresponding SNAT table entries and sub-interfaces on the standby node (112) may likewise be deleted to maintain consistency. These updates may be communicated by updating the database (402) of the active node (110), and consequently, updating the database (402) of the standby node (112) to display the deleted information.

[0046] The method (500) may further include a step (508) of monitoring the status of the active node (110) and a step (510) of detecting a failure of the active node (110). This can be performed as described above in relation to steps (304 and 306) of the method (300) using periodic still-alive messages or queries.

[0047] When a failure is detected (510), traffic may be routed to a standby node (112) instead of the active node (110) (512). The change in routing may be implemented by changing the routing table (204) in the VPC (102) containing the nodes (110, 112). The change in routing may include configuring workloads (114) to use the standby node (112) as the default gateway.

[0048] Then, the standby node (112) can process traffic received according to SNAT tables (404), sub-interfaces, FIB (406), TCP states, or other data received from the active node (110) prior to failure (514). In particular, the standby node (112) can perform the functions described herein for the active node (110) in functioning as a network gateway, including performing NAT, managing TCP state machines, routing according to FIB (406), and any of the other functions described herein for the active node (110).

[0049] With respect to the embodiments of FIGS. 1 to 3, the standby node (112) is already configured with some or all of the SNAT tables (404), FIB (406), and sub-interfaces for the workloads (114) before failure occurs, and thus can route traffic to and from the workloads (114) without interfering with higher-level network sessions such as TCP sessions and application sessions.

[0050] With respect to the embodiments of FIGS. 1 through 3, the approach of FIGS. 4 and 5 may be implemented on a cloud computing platform (104) or on-premises equipment so that each node (110, 112) runs on a different computing device. Workloads (114) may run on the same on-premises equipment as the nodes (110, 112) or on different on-premises equipment.

[0051] With respect to the embodiments of FIGS. 1 to 3, when the active node (110) resumes operation after a failure, the active node (110) can function as a standby node, that is, receive replication information regarding the SNAT table (404), FIB, and / or sub-interfaces from the standby node (112). When this information is up to date for the standby node (112) and corresponding sub-interfaces are created on the active node (110), the active node (110) can be activated again and the standby node (112) will function as a standby node again.

[0052] FIG. 6 illustrates a method (600) that can be used to perform failover between an active node (110) and a standby node (112) in the absence of a synchronized database (402) at each node (110, 112).

[0053] In method (600), the active node (110) and the standby node (112) establish a connection between them (602). In the illustrated embodiment, this is a user datagram protocol (UDP) connection. The active node (110) will then notify the standby node (112) through this connection (604). The notification may include a notification of information sufficient to enable the standby node (112) to recreate sub-interfaces for the workloads (114) created on the active node (110). The notification may include information such as a private IP address, a public IP address mapped to a public IP address in the SNAT table, and the MAC address of the workload (114). Thus, the standby node (112) will create a sub-interface having the private IP address, public IP address, and MAC address indicated in the notification.

[0054] The notifications may also include notifications that an interface has been dropped or an SNAT table entry has been dropped, for example, due to a workload terminating a network session or otherwise due to the abandonment of a private and / or public IP address. Accordingly, the standby node (112) will update its SNAT table to drop the interface referenced in the notification and / or drop the entry referenced in the notification.

[0055] The method (600) may further include a step (606) of monitoring the status of the active node (110) and a step (608) of detecting a failure of the active node (110). This can be performed as previously described for the steps (304 and 306) of the method (300) using periodic still-alive messages or queries.

[0056] When a failure is detected (608), traffic may be routed to a standby node (112) instead of the active node (610). Changing the routing may be implemented by changing the routing table (204) in the VPC (102) containing the nodes (110, 112). Changing the routing may include configuring the workload (114) to use the standby node (112) as the default gateway.

[0057] The standby node (112) can then process traffic (612) according to the SNAT table (404), FIB (406), TCP states, and / or sub-interfaces received from the active node (110). In particular, the standby node (112) can perform the functions described herein for the active node (110) which functions as a network gateway, including performing NAT, managing TCP state machines, routing according to the FIB (406), and any other functions assigned to the active node (110) in this specification.

[0058] For the embodiments of FIGS. 1 through 3, the approach of FIG. 6 may be implemented on a cloud computing platform (104) or on-premise equipment so that each node (110, 112) runs on a different computing device. Workloads (114) may run on the same on-premise equipment as the nodes (110, 112) or on different on-premise equipment.

[0059] For the embodiments of FIGS. 1 to 3, when the active node (110) resumes operation after a failure, the active node (110) can function as a standby node, that is, receive replication information regarding the SNAT table (404), FIB, and / or sub-interfaces from the standby node (112). When this information is up to date for the standby node (112) and corresponding sub-interfaces are created on the active node (110), the active node (110) can be reactivated and the standby node (112) will function as a standby node again.

[0060] FIG. 7 is a block diagram illustrating an exemplary computing device (700) that can be used to implement the system and method disclosed herein. In particular, a node (108, 110, 112) according to any of the embodiments described above may have some or all of the attributes of the computing device (700). Likewise, a cloud computing platform may be composed of a device having some or all of the attributes of the computing device (709).

[0061] The computing device (700) may be used to perform various procedures such as those discussed in this specification. The computing device (700) may function as a server, a client, or any other computing entity. The computing device may perform various monitoring functions discussed in this specification and may execute one or more application programs, such as the application programs described in this specification, on a computer, a laptop computer, a server computer, a portable computer, a tablet computer, etc.

[0062] The computing device (700) includes one or more processor(s) (702), one or more memory device(s) (704), one or more interface(s) (706), one or more mass storage device(s) (708), one or more input / output (I / O) device(s) (710), and a display device (730), all of which are coupled to a bus (712). The processor(s) (702) include one or more processors or controllers that execute instructions stored in the memory device(s) (704) and / or mass storage device(s) (708). The processor(s) (702) may also include various types of computer-readable media, such as cache memory.

[0063] The memory device(s) (704) include various computer-readable media such as volatile memory (e.g., random access memory (RAM) (714)) and / or non-volatile memory (e.g., read-only memory (ROM) (716)). The memory device(s) (704) may also include rewritable ROM such as flash memory.

[0064] Mass storage device(s) (708) include various computer-readable media such as magnetic tape, magnetic disk, optical disk, solid-state memory (e.g., flash memory). As illustrated in FIG. 7, a specific mass storage device is a hard disk drive (724). Various drives may also be included in the mass storage device(s) (708) to enable reading from and / or writing to various computer-readable media. The mass storage device(s) (708) include removable media (726) and / or non-removable media.

[0065] I / O device(s) (710) include various devices that enable data and / or other information to be input into or retrieved from the computing device (700). Exemplary I / O device(s) (710) include a cursor control device, a keyboard, a keypad, a microphone, a monitor or other display device, a speaker, a printer, a network interface card, a modem, a lens, a CCD or other image capture device, etc.

[0066] The display device (730) includes any type of device capable of displaying information to one or more users of the computing device (700). Examples of the display device (730) include a monitor, a display terminal, a video projection device, etc.

[0067] Interface(s) (706) include various interfaces that enable the computing device (700) to interact with other systems, devices, or computing environments. An exemplary interface(s) (706) includes any number of different network interfaces (720), such as interfaces for a local area network (LAN), a wide area network (WAN), a wireless network, and the Internet. Other interface(s) include a user interface (718) and a peripheral device interface (722). Interface(s) (706) may also include one or more user interface elements (718). Interface(s) (706) may also include one or more peripheral interfaces, such as interfaces for a printer, a pointing device (mouse, trackpad, etc.), a keyboard, etc.

[0068] The bus (712) enables the processor(s) (702), memory device(s) (704), interface(s) (706), mass storage device(s) (708), and I / O device(s) (710) to communicate with each other, as well as with other devices or components coupled to the bus (712). The bus (712) represents one or more of several types of bus structures, such as a system bus, PCI bus, IEEE 1394 bus, USB bus, etc.

[0069] For the purposes of illustration, programs and other executable program components are illustrated herein as individual blocks, but it is understood that such programs and components may reside in different storage components of the computing device (700) at various times and are executed by the processor(s) (702). Alternatively, the systems and procedures described herein may be implemented in hardware, or a combination of hardware, software, and / or firmware. For example, one or more application-specific integrated circuits (ASICs) may be programmed to perform one or more of the systems and procedures described herein.

Claims

Claim 1 A method comprising: providing a plurality of workloads executed in a computing environment comprising a plurality of computing devices, wherein each computing device comprises a processing device and a memory device, and each of the plurality of workloads is an application, a daemon, a network service, an operating system, a container, or a computing process executable by a computer; providing a first node executed in the computing environment, wherein the first node is programmed to operate as a first gateway between the computing environment and an external network by performing network address translation (NAT), and the computing environment is configured to allow the plurality of workloads to communicate with the external network through the first node; providing a second node executed in the computing environment programmed to operate as a second gateway between the computing environment and the external network by performing NAT; configuring the second node to mirror the NAT state of the first node; creating first interfaces for the plurality of workloads on the first node and creating second interfaces for the plurality of workloads identical to the first interfaces on the second node; wherein the second node is such that the first A step of detecting a failure of a node; and in response to detecting a failure of the first node, configuring the computing environment such that the second node allows the plurality of workloads to communicate with the external network through the second node using the second interface - the second interface is created prior to the failure of the first node -;A method comprising the step of executing the NAT according to the NAT state of the first node, wherein the first interfaces are sub-interfaces for a first VPN (Virtual Private Network) connection and the second interfaces are sub-interfaces for a second VPN connection. Claim 2 A method according to claim 1, wherein the computing environment defines a routing table; and the step of configuring the computing environment to be programmed so that the plurality of workloads communicate with the external network through the second node comprises the step of replacing a reference to the first node in the routing table with a reference to the second node. Claim 3 A method according to claim 1, wherein the NAT state is a NAT table comprising a mapping between the private IP addresses of the plurality of workloads and the public IP addresses of the plurality of workloads. Claim 4 delete Claim 5 A method according to claim 1, wherein the first interfaces reference the MAC (media access code) addresses of the plurality of workloads, and the second interfaces reference the MAC addresses. Claim 6 delete Claim 7 A method according to claim 1, wherein the first node is connected to a hub node by the first VPN connection, and the hub node provides a connection between the first node and the external network; and the second node is connected to a hub node by the second VPN connection, and the hub node provides a connection between the second node and the external network. Claim 8 In claim 7, the computing environment is a cloud computing environment, and the first node and the second node are executed within a Virtual Private Cloud (VPC) in the cloud computing environment, a method. Claim 9 A method according to claim 8, further comprising: maintaining protocol state machines on the first node for the plurality of workloads; copying the protocol state machines to the second node; and, in response to detecting a failure of the first node, the second node continues to route traffic for the plurality of workloads by the second node according to the protocol state machines. Claim 10 In paragraph 9, the method wherein the protocol state machines are each TCP (transport control protocol) state machines. Claim 11 A method according to claim 10, further comprising the step of configuring the computing environment so that the plurality of workloads communicate with the external network through the second node without invoking the creation of new TCP sessions by the plurality of workloads. Claim 12 A method according to claim 1, further comprising the step of configuring the computing environment so that the plurality of workloads communicate with the external network through the second node without calling the creation of new application sessions by the plurality of workloads. Claim 13 A method according to claim 1, further comprising: a step in which the first node maintains a first database including the NAT state; a step in which the second node maintains a second database; and a step in which the first node and the second node synchronize the first database with the second database. Claim 14 A method comprising: executing a plurality of workloads in a computing environment, wherein each of the plurality of workloads is an application, a daemon, a network service, an operating system, a container, or a computing process executable by a computer; executing a first node in the computing environment, wherein the first node is connected to the plurality of workloads and manages network communication between the plurality of workloads and an external network outside the computing environment; wherein the first node creates first network interfaces for the plurality of workloads for communication with the external network; wherein a second node executed in the computing environment creates second network interfaces having the same addresses as the first network interfaces for use by the plurality of workloads; and wherein the second node detects a failure of the first node. A method comprising the step of, in response to detecting a failure of the first node, configuring the computing environment such that the second node allows the plurality of workloads to communicate with the external network through the second network interfaces and the second node, wherein the second interface is created prior to the failure of the first node, the first interfaces are sub-interfaces for a first VPN (Virtual Private Network) connection, and the second interfaces are sub-interfaces for a second VPN connection. Claim 15 A method according to claim 14, further comprising: a step in which the first node performs NAT using a first NAT (network address translation) table that maps private addresses of the plurality of workloads used within the computing environment to public addresses used in the external network; a step in which the second node maintains a second NAT table identical to the first NAT table; and a step in which the second node performs NAT using the second NAT table in response to the detection of a failure of the first node. Claim 16 A method according to claim 14, wherein the first virtual private network (VPN) connection is a hub node connecting the first node to an external network; and the second VPN connection is a hub node connecting the second node to an external network. Claim 17 A method according to claim 16, further comprising the step of the hub node creating a first NAT table on the first node to manage NAT (network address translation), - the first NAT table maps private addresses of a plurality of workloads used within the computing environment and public addresses used in the external network -; and the step of the hub node creating a second NAT table identical to the first NAT table on the second node. Claim 18 In paragraph 14, the method wherein the computing environment is a cloud computing platform. Claim 19 In paragraph 18, the method wherein the first node and the second node are executed within a virtual private cloud (VPC) within the cloud computing platform. Claim 20 In paragraph 18, the method wherein the first node and the second node are executed on different computing devices connected to the same local network.

Citation Information

Patent Citations

  • Address conversion system, address conversion duplication method and program

    JP6579608B2

  • High availability and failover

    US20160210209A1