# US 2020/0403960 A1 · System and method of persistent address resolution synchronization

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

- Number: US 2020/0403960 A1
- Document ID: US20200403960A1
- Status: Published application
- Kind: A1
- Application number: 16/897,933
- Filed: 2020-06-10
- Published: 2020-12-24
- Earliest claimed: 2015-02-27
- Assignees: Arista Networks, Inc.
- Applicants: Arista Networks, Inc.
- Inventors: Vijay Mahadevan; Dileep Honsoge Ramesh; Adam James Sweeney
- Web page: https://patentgrep.com/patent/US20200403960A1

## CPC

- H04L 61/10: of different types
- H04L 61/103: across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
- H04L 61/45: Network directories; Name-to-address mapping
- H04L 61/5046: Resolving address allocation conflicts; Testing of addresses (testing when self-assigning an address H04L61/5092)
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 2101/622: Layer-2 addresses, e.g. medium access control [MAC] addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method and apparatus of a device that starts an address resolution service on a network element after a boot-up of this network element is described. In an exemplary embodiment, the network element sends an indication of the boot-up. The network element further sends a request for an address resolution table and receives a reply with the requested address resolution table. In addition, the network element starts the address resolution service using the requested address resolution table.

## Claims

### Claim at position 1

-8. (canceled)

### Claim 9

A non-transitory machine-readable medium having executable instructions to cause one or more processing units perform a method to boot-up of a first processing unit in a network element, the method comprising:
periodically synchronizing software address resolution information between the first and a second processing unit of the network element;
receiving an indication of the boot-up of the first processing unit;
determining differences between a hardware address resolution information and the software address resolution information;
reconciling the differences so that the hardware and the software address information includes the same address resolution entries; and
starting the address resolution service on the first processing unit.

### Claim 10 (depends on 9)

The non-transitory machine-readable medium of claim 9, wherein the address resolution information is Address Resolution Protocol information.

### Claim 11 (depends on 9)

The non-transitory machine-readable medium of claim 9, wherein the synchronizing software address resolution information comprises:
receiving the address resolution information; and
installing the address resolution information.

### Claim 12 (depends on 9)

The non-transitory machine-readable medium of claim 9, wherein reconciling the differences comprises:
retrieving the hardware and software address information; and
fixing differences between the hardware and software address information.

### Claim at position 6

13-20. (canceled)

### Claim 21 (depends on 9)

The non-transitory machine-readable medium of claim 9, wherein the network element is implemented as a first hop gateway.

### Claim 22 (depends on 9)

The non-transitory machine-readable medium of claim 9, wherein the network element provides access to a network layer for the first and second processing units from a different network layer.

### Claim 23 (depends on 22)

The non-transitory machine-readable medium of claim 22, wherein the network element provides access to a layer 3 network layer for the first and second processing units from a layer 2 network layer.

### Claim 24 (depends on 9)

The non-transitory machine-readable medium of claim 9, wherein the resolution table is a serialized table.

### Claim 25 (depends on 9)

The non-transitory machine-readable medium of claim 9, wherein the network element is a network element peer of another network element in a multi-chassis link aggregation topology.

### Claim 26

A network element comprising:
first and second processing units;
one or more processors programmed and configured to perform:
periodically synchronizing software address resolution information between the first and a second processing unit of the network element;
receiving an indication of the boot-up of the first processing unit;
determining differences between a hardware address resolution information and the software address resolution information;
reconciling the differences so that the hardware and the software address information includes the same address resolution entries; and
starting the address resolution service on the first processing unit.

### Claim 27 (depends on 26)

The network element of claim 26 wherein the address resolution information is Address Resolution Protocol information.

### Claim 28 (depends on 26)

The network element of claim 26, wherein the synchronizing software address resolution information comprises:
receiving the address resolution information; and
installing the address resolution information.

### Claim 29 (depends on 26)

The network element of claim 26, wherein reconciling the differences comprises:
retrieving the hardware and software address information; and
fixing differences between the hardware and software address information.

### Claim 30 (depends on 26)

The network element of claim 26, wherein the network element is implemented as a first hop gateway.

### Claim 31 (depends on 26)

The network element of claim 26, wherein the network element provides access to a network layer for the first and second processing units from a different network layer.

### Claim 32 (depends on 26)

The network element of claim 26, wherein the network element provides access to a layer 3 network layer for the first and second processing units from a layer 2 network layer.

### Claim 33 (depends on 26)

The network element of claim 26, wherein the resolution table is a serialized table.

### Claim 34 (depends on 26)

The network element of claim 26, wherein the network element is a network element peer of another network element in a multi-chassis link aggregation topology.

### Claim 35

A method of starting an address resolution service, the method comprising:
periodically synchronizing software address resolution information between a first and a second processing unit of a network element;
receiving an indication of the boot-up of the first processing unit;
determining differences between a hardware address resolution information and the software address resolution information;
reconciling the differences so that the hardware and the software address information includes the same address resolution entries; and
starting the address resolution service on the first processing unit.

### Claim 36 (depends on 35)

The method of claim 35, wherein the address resolution information is Address Resolution Protocol information.

### Claim 37 (depends on 35)

The method of claim 35, wherein the synchronizing software address resolution information comprises:
receiving the address resolution information; and
installing the address resolution information.

### Claim 38 (depends on 35)

The method of claim 35, wherein reconciling the differences comprises:
retrieving the hardware and software address information; and
fixing differences between the hardware and software address information.

### Claim 39 (depends on 35)

The method of claim 35, wherein the network element is implemented as a first hop gateway.

### Claim 40 (depends on 35)

The method of claim 35, wherein the network element provides access to a network layer for the first and second processing units from a different network layer.

### Claim 41 (depends on 40)

The method of claim 40, wherein the network element provides access to a layer 3 network layer for the first and second processing units from a layer 2 network layer.

### Claim 42 (depends on 35)

The method of claim 35, wherein the resolution table is a serialized table.

### Claim 43 (depends on 35)

The method of claim 35, wherein the network element is a network element peer of another network element in a multi-chassis link aggregation topology.

### Claim 44

A method of starting an address resolution service, the method comprising:
periodically synchronizing software address resolution information between an first processing unit and a second processing unit of a network element, the first processing unit actively processing an address resolution service;
receiving an indication of the failure of the active processing unit;
determining differences between a hardware address resolution information and the software address resolution information;
reconciling the differences so that the hardware and the software address information includes the same address resolution entries; and
resuming the address resolution service on the second processing unit.

### Claim 45 (depends on 44)

The method of claim 44, wherein the network element is a network element peer of another network element in a multi-chassis link aggregation topology.
