# US 2019/0245783 A1 · Systems and methods for dynamic routing on a shared ip address

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0245783 A1
- Document ID: US20190245783A1
- Status: Published application
- Kind: A1
- Application number: 16/389,338
- Filed: 2019-04-19
- Published: 2019-08-08
- Earliest claimed: 2015-09-07
- Assignees: Citrix Systems, Inc.
- Applicants: Citrix Systems, Inc.
- Inventors: Sharvari Mithyantha
- Web page: https://patentgrep.com/patent/US20190245783A1

## CPC

- H04L 45/46: {Cluster building}
- H04L 45/02: Topology update or discovery
- H04L 45/42: Centralised routing
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 43/00: Arrangements for monitoring or testing data switching networks
- H04L 43/0823: Errors, e.g. transmission errors
- H04L 43/0852: Delays
- H04L 43/0864: Round trip delays
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 45/74: Address processing for routing
- H04L 61/2514: between local and global IP addresses
- H04L 61/4511: using domain name system [DNS]
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 67/00: Network arrangements or protocols for supporting network services or applications (user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present disclosure is directed towards systems and methods for dynamic routing on an IP address shared by a cluster of nodes. In an implementation, a first node of a cluster of nodes can receive a unicast routing protocol packet from a peer router. The unicast routing protocol packet can be addressed to a shared IP address established across the cluster of nodes. The cluster of nodes can be intermediary to a plurality of clients and a plurality of servers. The first node can identify a second node identified as a routing leader. The first node can steer the packet to the second node in response to determining that the routing protocol packet is a unicast routing protocol packet. The second node can be configured to advertise virtual IP address routes to the network over the routing adjacency and maintain routing adjacencies.

## Claims

### Claim 1

A method, comprising:
identifying, by a first device of a cluster of devices having a shared Internet protocol (IP) address, a routing leader among devices of the cluster, the routing leader configured to maintain routing adjacencies for the cluster of devices;
receiving, by the first device, a packet addressed to the shared IP address;
determining, by the first device, that the packet is a IP routing protocol packet; and
forwarding, by the first device response to the determination, the IP routing protocol packet to the routing leader of the cluster of devices to update routing adjacencies responsive to the IP routing protocol packet.

### Claim 2 (depends on 1)

The method of claim 1, further comprising advertising, by the routing leader, the shared IP address as a next hop.

### Claim 3 (depends on 1)

The method of claim 1, wherein the routing leader communicates with other devices of the cluster of devices to update respective routing tables to include information in the IP routing protocol packet.

### Claim 4 (depends on 1)

The method of claim 1, further comprising receiving, by the first device, a response generated by the routing leader responsive to the IP routing protocol packet and communicating, by the first device, the response to a sender of the IP routing protocol packet.

### Claim 5 (depends on 1)

The method of claim 1, further comprising receiving the IP routing protocol packet from a peer router.

### Claim 6 (depends on 5)

The method of claim 5, further comprising determining that the IP routing protocol is a multicast IP routing protocol packet and that at least the routing leader is not connected to the peer router.

### Claim 7 (depends on 1)

The method of claim 1, further comprising determining that the IP routing protocol is a unicast IP routing protocol packet.

### Claim 8 (depends on 1)

The method of claim 1, further comprising selecting a second device of the cluster of devices as the routing leader based at least on a number of linksets to which the second device is a member.

### Claim 9 (depends on 1)

The method of claim 1, wherein the cluster of devices is configured to appear as a single routing entity on a network.

### Claim 10 (depends on 1)

The method of claim 1, wherein the routing leader is configured to advertise routing information of the cluster to a peer router.

### Claim 11

A system, comprising:
a first device of a cluster of devices having a shared Internet protocol (IP) address, wherein the first device is configured to:
identify a routing leader among devices of the cluster, the routing leader configured to maintain routing adjacencies for the cluster of devices;
receive a packet addressed to the shared IP address;
determine that the packet is a IP routing protocol packet; and
forward, responsive to the determination, the IP routing protocol packet to the routing leader of the cluster of devices to update routing adjacencies responsive to the IP routing protocol packet.

### Claim 12 (depends on 11)

The system of claim 11, wherein the routing leader is further configured to advertise the shared IP address as a next hop.

### Claim 13 (depends on 11)

The system of claim 11, wherein the routing leader is further configured to communicate with other devices of the cluster of devices to update respective routing tables to include information in the IP routing protocol packet.

### Claim 14 (depends on 11)

The system of claim 11, wherein the first device is further configured to receive a response generated by the routing leader responsive to the IP routing protocol packet and communicate the response to a sender of the IP routing protocol packet.

### Claim 15 (depends on 11)

The system of claim 11, wherein the first device is further configured to receive the IP routing protocol packet from a peer router.

### Claim 16 (depends on 15)

The system of claim 15, wherein the first device is further configured to determine that the IP routing protocol is a multicast IP routing protocol packet and that at least the routing leader is not connected to the peer router.

### Claim 17 (depends on 11)

The system of claim 11, wherein the first device is further configured to determine that the IP routing protocol is a unicast IP routing protocol packet.

### Claim 18 (depends on 11)

The system of claim 11, wherein the first device is further configured to select a second device of the cluster of devices as the routing leader based at least on a number of linksets to which the second device is a member.

### Claim 19 (depends on 11)

The system of claim 11, wherein the cluster of devices is further configured to appear as a single routing entity on a network.

### Claim 20 (depends on 11)

The system of claim 11, wherein the routing leader is further configured to advertise routing information of the cluster to a peer router.
