Abstract: Migrating a network service that is currently being performed by a first device to be performed by a second device includes: instructing the second device to notify an upstream network device to forward traffic that is to be serviced by the network service to the second device instead of to the first device, the network service being associated with an Internet Protocol (IP) address; and instructing the first device to migrate the network service to the second device, wherein the migration includes moving or copying state information associated with an existing flow currently serviced by the first device to the second device; the existing flow being an existing flow between a client application and a network application.

Abstract: Providing high availability in a distributed networking platform includes detecting that an original primary service engine is unavailable, wherein: the original primary service engine and a plurality of secondary service engines are configured to provide one or more network applications associated with a virtual Internet Protocol (VIP) address; the original primary service engine and the plurality of secondary service engines are in active-active configuration mode; and the original primary service engine is configured to respond to Address Resolution Protocol (ARP) requests designating the VIP address. Additionally, providing high availability in a distributed networking platform further includes determining that a controller is unavailable; and configuring a selected secondary service engine as the next primary service engine.

Abstract: Migrating a network service that is currently being performed by a first device to be performed by a second device includes: instructing the second device to notify an upstream network device to forward traffic that is to be serviced by the network service to the second device instead of to the first device, the network service being associated with an Internet Protocol (IP) address; and instructing the first device to migrate the network service to the second device, wherein the migration includes moving or copying state information associated with an existing flow currently serviced by the first device to the second device; the existing flow being an existing flow between a client application and a network application.

Abstract: Providing high availability in a distributed networking platform includes detecting that an original primary service engine is unavailable, wherein: the original primary service engine and a plurality of secondary service engines are configured to provide one or more network applications associated with a virtual Internet Protocol (VIP) address; the original primary service engine and the plurality of secondary service engines are in active-active configuration mode; and the original primary service engine is configured to respond to Address Resolution Protocol (ARP) requests designating the VIP address. Additionally, providing high availability in a distributed networking platform further includes determining that a controller is unavailable; and configuring a selected secondary service engine as the next primary service engine.

Abstract: Migrating a network service that is currently being performed by a first device to be performed by a second device includes: instructing the second device to notify an upstream network device to forward traffic that is to be serviced by the network service to the second device instead of to the first device, the network service being associated with an Internet Protocol (IP) address; and instructing the first device to migrate the network service to the second device, wherein the migration includes moving or copying state information associated with an existing flow currently serviced by the first device to the second device; the existing flow being an existing flow between a client application and a network application.

Abstract: Providing high availability in a distributed networking platform includes detecting that an original primary service engine is unavailable, wherein: the original primary service engine and a plurality of secondary service engines are configured to provide one or more network applications associated with a virtual Internet Protocol (VIP) address; the original primary service engine and the plurality of secondary service engines are in active-active configuration mode; and the original primary service engine is configured to respond to Address Resolution Protocol (ARP) requests designating the VIP address. Additionally, providing high availability in a distributed networking platform further includes determining that a controller is unavailable; and configuring a selected secondary service engine as the next primary service engine.

Abstract: Network session identification information is received. The network session identification information is associated with a destination IP address and a destination network port. An available source network port for a new session to be established for a source IP address is determined based on the destination IP address and the destination network port.

Abstract: In a network with at least a first device already configured to provide a network service to a network application, scaling service capacity includes: configuring one or more second devices to provide the network service to the network application. In embodiments where an upstream network device supports Equal-Cost Multi-Path (ECMP) routing, the upstream network device is configured, including storing a plurality of paths to reach an address associated with a network application, wherein the plurality of paths are equal in cost. In embodiments where the upstream network device does not support ECMP routing, the second device is configured not to respond to an Address Resolution Protocol (ARP) request associated with an Internet Protocol (IP) address of the network application, and the first device is instructed to perform load balancing on network traffic destined for the network application among the first device and the one or more second devices.

Abstract: Network session identification information is received. The network session identification information is associated with a destination IP address and a destination network port. An available source network port for a new session to be established for a source IP address is determined based on the destination IP address and the destination network port.

Abstract: Managing network ports is disclosed. Network session identification information is received. The network session identification information is associated with a destination IP address and a destination network port. An available source network port is determined using a data structure that is based on the destination IP address and the destination network port.

Abstract: Migrating a network service that is currently being performed by a first device to be performed by a second device includes: instructing the second device to notify an upstream network device to forward traffic that is to be serviced by the network service to the second device instead of to the first device, the network service being associated with an Internet Protocol (IP) address; and instructing the first device to migrate the network service to the second device, wherein the migration includes moving or copying state information associated with an existing flow currently serviced by the first device to the second device; the existing flow being an existing flow between a client application and a network application.

Abstract: Migrating a network service that is currently being performed by a first device to be performed by a second device includes: instructing the second device to notify an upstream network device to forward traffic that is to be serviced by the network service to the second device instead of to the first device, the network service being associated with an Internet Protocol (IP) address; and instructing the first device to migrate the network service to the second device, wherein the migration includes moving or copying state information associated with an existing flow currently serviced by the first device to the second device; the existing flow being an existing flow between a client application and a network application.

Abstract: Load balancing includes receiving, from a client, a connection request to establish a connection with a server; determining load balancing state information based at least in part on the connection request; synchronizing the load balancing state information across a plurality of service engines using a distributed data store service, the distributed data store service being configured to: determine whether in a distributed data store there is an existing entry that corresponds to the load balancing state information; in the event that it is determined that in the distributed data store there is no existing entry that corresponds to the load balancing state information, atomically create a new entry based on the load balancing state information; and distributing the connection to a selected server among a plurality of servers, the selected server being selected based at least in part on the load balancing state information.

Abstract: In a network with at least a first device already configured to provide a network service to a network application, scaling service capacity includes: configuring one or more second devices to provide the network service to the network application. In embodiments where an upstream network device supports Equal-Cost Multi-Path (ECMP) routing, the upstream network device is configured, including storing a plurality of paths to reach an address associated with a network application, wherein the plurality of paths are equal in cost. In embodiments where the upstream network device does not support ECMP routing, the second device is configured not to respond to an Address Resolution Protocol (ARP) request associated with an Internet Protocol (IP) address of the network application, and the first device is instructed to perform load balancing on network traffic destined for the network application among the first device and the one or more second devices.

Abstract: Managing network ports is disclosed. Network session identification information is received. The network session identification information is associated with a destination IP address and a destination network port. An available source network port is determined using a data structure that is based on the destination IP address and the destination network port.

Abstract: In a network with at least a first device already configured to provide a network service to a network application, scaling service capacity includes: configuring one or more second devices to provide the network service to the network application. In embodiments where an upstream network device supports Equal-Cost Multi-Path (ECMP) routing, the upstream network device is configured, including storing a plurality of paths to reach an address associated with a network application, wherein the plurality of paths are equal in cost. In embodiments where the upstream network device does not support ECMP routing, the second device is configured not to respond to an Address Resolution Protocol (ARP) request associated with an Internet Protocol (IP) address of the network application, and the first device is instructed to perform load balancing on network traffic destined for the network application among the first device and the one or more second devices.

Abstract: Managing network ports is disclosed. Network session identification information is received. The network session identification information is associated with a destination IP address and a destination network port. An available source network port is determined using a data structure that is based on the destination IP address and the destination network port.

Abstract: Load balancing includes receiving, from a client, a connection request to establish a connection with a server; determining load balancing state information based at least in part on the connection request; synchronizing the load balancing state information across a plurality of service engines using a distributed data store service, the distributed data store service being configured to: determine whether in a distributed data store there is an existing entry that corresponds to the load balancing state information; in the event that it is determined that in the distributed data store there is no existing entry that corresponds to the load balancing state information, atomically create a new entry based on the load balancing state information; and distributing the connection to a selected server among a plurality of servers, the selected server being selected based at least in part on the load balancing state information.

Abstract: Load balancing includes receiving, from a client, a connection request to establish a connection with a server; determining load balancing state information based at least in part on the connection request; synchronizing the determined load balancing state information across a plurality of service engines, including to invoke an atomic read-miss-create (RMC) function on a distributed data store service; and distributing the connection to a selected server among a plurality of servers according to a result of the RMC function.

Abstract: Load balancing includes receiving, from a client, a connection request to establish a connection with a server; determining load balancing state information based at least in part on the connection request; synchronizing the determined load balancing state information across a plurality of service engines, including to invoke an atomic read-miss-create (RMC) function on a distributed data store service; and distributing the connection to a selected server among a plurality of servers according to a result of the RMC function.