Abstract: A method of controlling a packet flow in a distributed network system comprising a plurality of network nodes having the same destination address is disclosed. Network nodes each having an application running that waits for connections on a given destination port are registered in a flow table. This registration information is distributed to each of the plurality of network nodes. When a packet indicating an initiation of a connection is received and it is determined that the received packet indicates the initiation of the connection on the given destination port, a network node is selected from the network nodes registered in the flow table, to which the received packet is to be forwarded. The received packet is forwarded to the selected network node and a corresponding entry is inserted into the flow table. This entry information is distributed to each of the plurality of network nodes.

Abstract: A system and method is directed to synchronizing a standby route distributor in a distributed routing platform. A route distributor is configured to operate as an active route distributor. Another route distributor is configured to operate as a standby route distributor. The standby and active route distributor may reside in the same or a different distributed routing platform. A slave route distributor communicates a route to the active route distributor. The active route distributor may update its routing tables with the route. The active route distributor forwards the route to the standby route distributor to enable their routing tables to be substantially synchronized. The standby route distributor distributes the route to the slave route distributors, where the route enables an update to another routing table. In the event of a switchover, the standby route distributor resynchronizes its routing tables and may distribute route information to each slave route distributor.

Abstract: A standard socket interface is provided to implement socket redundancy. The interface includes socket options to create redundant sockets, obtain the status of redundant sockets, as well as providing error information relating to redundant sockets. A redundant socket may be created on a standby side that becomes active should the active side fail. The standby socket is associated with the active side socket. When an active side fails that has a redundant socket created, the standby side socket seamlessly takes over the sockets operations.

Abstract: A system and method is directed to synchronizing a standby route distributor in a distributed routing platform. A route distributor is configured to operate as an active route distributor. Another route distributor is configured to operate as a standby route distributor. The standby and active route distributor may reside in the same or a different distributed routing platform. A slave route distributor communicates a route to the active route distributor. The active route distributor may update its routing tables with the route. The active route distributor forwards the route to the standby route distributor to enable their routing tables to be substantially synchronized. The standby route distributor distributes the route to the slave route distributors, where the route enables an update to another routing table. In the event of a switchover, the standby route distributor resynchronizes its routing tables and may distribute route information to each slave route distributor.

Abstract: A standard socket interface is provided to implement socket redundancy. The interface includes socket options to create redundant sockets, obtain the status of redundant sockets, as well as providing error information relating to redundant sockets. A redundant socket may be created on a standby side that becomes active should the active side fail. The standby socket is associated with the active side socket. When an active side fails that has a redundant socket created, the standby side socket seamlessly takes over the sockets operations.