# US 2020/0403882 A1 · Network health checker

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

- Number: US 2020/0403882 A1
- Document ID: US20200403882A1
- Status: Published application
- Kind: A1
- Application number: 16/920,407
- Filed: 2020-07-02
- Published: 2020-12-24
- Earliest claimed: 2016-10-31
- Assignees: Nicira, Inc.
- Applicants: Nicira, Inc.
- Inventors: Aditya G. Holla; Ramya Bolla; Manoj Tammali; Vaibhav Kumar; Nithya Vijayaraghavan
- Web page: https://patentgrep.com/patent/US20200403882A1

## CPC

- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 41/12: Discovery or management of network topologies
- H04L 45/02: Topology update or discovery
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/34: Signalling channels for network management communication
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 43/12: Network monitoring probes
- H04L 47/36: by determining packet size, e.g. maximum transfer unit [MTU]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method of generating a network topology map in a datacenter comprising a network manager server and a set of host machines is provided. Each host machine hosts a set of data compute nodes (DCNs). The method receives information regarding the configuration of each of a set of logical networks from the network manager server. Each logical network is connected to several DCNs. The method identifies logical connections configured between the DCNs using the configuration of the overlay networks. The method generates a network topology map based on the identified logical configuration. The network topology identifies the DCNs that are connected to each overlay network. The method displays the network topology map on a graphical user interface.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method of generating a network topology diagram in a datacenter comprising a network manager server and a set of host machines, each host machine hosting a set of data compute nodes (DCNs), the method comprising:
receiving information regarding a configuration of each of a set of logical networks from the network manager server, each logical network connected to a plurality of DCNs;
identifying logical connections configured between the DCNs using the configuration of the overlay networks;
generating a network topology diagram based on the identified logical configuration, the network topology identifying the DCNs that are connected to each logical network;
displaying the network topology diagram on a graphical user interface, said displaying comprising displaying at least one particular logical connection to one DCN differently than a plurality of other logical connections to other DCNs in order to identify the health of the particular logical connection.

### Claim 22 (depends on 21)

The method of claim 21, wherein the data center further comprises a compute manager, the method further comprising:
receiving information regarding the DCNs that are hosted on each host machine from the compute manager server;
wherein generating the network topology diagram further comprises using the information regarding the DCNs that are hosted on each host machine.

### Claim 23 (depends on 22)

The method of claim 22 further comprising:
receiving information regarding changes to the configuration of each logical network from the compute manager;
updating the network topology based on the changes, and
displaying the updated network topology on the graphical user interface.

### Claim 24 (depends on 22)

The method of claim 22 further comprising:
receiving information regarding a change in the DCNs that are hosted on a host machine from the compute manager server;
updating the network topology based on the changes, and
displaying the updated network topology on the graphical user interface.

### Claim 25 (depends on 21)

The method of claim 21, wherein receiving information regarding the configuration of each logical network comprises receiving an identification of each DCN, each logical forwarding element, each virtual logical router, and each edge gateway connected to the logical network.

### Claim 26 (depends on 21)

The method of claim 21, wherein each logical network is an overlay network configured by a tenant of the datacenter.

### Claim 27 (depends on 21)

The method of claim 21 further comprising:
utilizing the determined health of each configured logical connection to visually identify a health status of each configured logical connection as one of healthy, having latency issues, having maximum transmission unit (MTU) issues, and failed.

### Claim 28 (depends on 21)

The method of claim 21, wherein the spoof ICMP packets comprise spoof ICMP packets sent to determine latency issues of each configured logical connection, the method further comprising:
starting a first timer and a second timer at a time of sending each spoof ICMP packet, the second timer having a longer expiration time than the first timer;
marking each logical connection for which a response to the spoof ICM packet is received before an expiration of the first timer as a health logical connection;
marking each logical connection for which a response to the spoof ICM packet is received after the expiration of the first timer and before an expiration of the second timer as a connection having latency issues; and
marking each logical connection for which no response is received to the spoof ICM packet before the expiration of the second timer as a failed logical connection.

### Claim 29 (depends on 21)

The method of claim 21, wherein the spoof ICMP packets comprise spoof ICMP packets sent to determine maximum transmission unit (MTU) issues, the method further comprising:
sending a plurality of spoof ICMP packets with different sizes to each destination VM over each configured logical connection;
marking each logical connection as having an acceptable MTU when no response indicating a spoof ICMP packet is too big over the logical connection; and
marking each logical connection as having an MTU issue with a particular packet size when a response is received to an spoof ICMP packet with the particular size indicating the packet is too big.

### Claim 30

A non-transitory machine readable medium storing a program that when executed by at least one processing unit generates a network topology diagram in a datacenter comprising a network manager server and a set of host machines, each host machine hosting a set of data compute nodes (DCNs), the program comprising sets of instructions for:
receiving information regarding a configuration of each of a set of logical networks from the network manager server, each logical network connected to a plurality of DCNs;
identifying logical connections configured between the DCNs using the configuration of the logical networks;
generating a network topology diagram based on the identified logical configuration, the network topology identifying the DCNs that are connected to each overlay network;
displaying the network topology diagram on a graphical user interface, said displaying comprising displaying at least one particular logical connection to one DCN differently than a plurality of other logical connections connected to other DCNs in order to identify the health of the particular logical connection.

### Claim 31 (depends on 30)

The non-transitory machine readable medium of claim 30, wherein the data center further comprises a compute manager, the program further comprising a set of instructions for:
receiving an identification of the DCNs hosted by each host machine from the compute manager server;
wherein the set of instructions for generating the network topology diagram further comprises a set of instructions for using the identification of the DCNs to determine the DCNs that are hosted on each host machine.

### Claim 32 (depends on 31)

The non-transitory machine readable medium of claim 31, the program further comprising sets of instructions for:
receiving information regarding changes to the configuration of each logical network from the compute manager;
updating the network topology based on the changes, and
displaying the updated network topology on the graphical user interface.

### Claim 33 (depends on 31)

The non-transitory machine readable medium of claim 31, the program further comprising sets of instructions for:
receiving information regarding a change in the DCNs that are hosted on a host machine from the compute manager server;
updating the network topology based on the changes, and
displaying the updated network topology on the graphical user interface.

### Claim 34 (depends on 30)

The method of claim 30, wherein receiving information regarding the configuration of each logical network comprises receiving an identification of each DCN, each logical forwarding element, each virtual logical router, and each edge gateway connected to the logical network.

### Claim 35 (depends on 30)

The non-transitory machine readable medium of claim 30, wherein each logical network is an overlay network configured by a tenant of the datacenter.

### Claim 36 (depends on 30)

The non-transitory machine readable medium of claim 30, the program further comprising sets of instructions for:
utilizing the determined health of each configured logical connection to visually identify a health status of each configured logical connection as one of healthy, having latency issues, having maximum transmission unit (MTU) issues, and failed.

### Claim 37 (depends on 30)

The non-transitory machine readable medium of claim 30, wherein the spoof ICMP packets comprise spoof ICMP packets sent to determine latency issues of each configured logical connection, the program further comprising sets of instructions for:
starting a first timer and a second timer at a time of sending each spoof ICMP packet, the second timer having a longer expiration time than the first timer;
marking each logical connection for which a response to the spoof ICM packet is received before an expiration of the first timer as a health logical connection;
marking each logical connection for which a response to the spoof ICM packet is received after the expiration of the first timer and before an expiration of the second timer as a connection having latency issues; and
marking each logical connection for which no response is received to the spoof ICM packet before the expiration of the second timer as a failed logical connection.

### Claim 38 (depends on 30)

The non-transitory machine readable medium of claim 30, wherein the spoof ICMP packets comprise spoof ICMP packets sent to determine maximum transmission unit (MTU) issues, the program further comprising sets of instructions for:
sending a plurality of spoof ICMP packets with different sizes to each destination VM over each configured logical connection;
marking each logical connection as having an acceptable MTU when no response indicating a spoof ICMP packet is too big over the logical connection; and
marking each logical connection as having an MTU issue with a particular packet size when a response is received to an spoof ICMP packet with the particular size indicating the packet is too big.
