# US 2014/0211639 A1 · Network Tracing for Data Centers

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

- Number: US 2014/0211639 A1
- Document ID: US20140211639A1
- Status: Published application
- Kind: A1
- Application number: 13/839,501
- Filed: 2013-03-15
- Published: 2014-07-31
- Earliest claimed: 2013-01-30
- Assignees: Broadcom Corporation
- Applicants: Broadcom Corporation
- Inventors: William Brad Matthews; Puneet Agarwal
- Web page: https://patentgrep.com/patent/US20140211639A1

## CPC

- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 43/12: Network monitoring probes
- H04L 43/50: Testing arrangements
- H04L 45/02: Topology update or discovery
- H04L 45/16: Multipoint routing
- H04L 45/24: Multipath
- H04L 45/72: {Routing based on the source address}
- H04L 49/555: {Error detection}
- H04L 43/0817: by checking functioning
- H04L 43/16: Threshold monitoring
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Network devices facilitate network tracing using tracing packets that travel through the network devices. The network devices may be switches, routers, bridges, hubs, or any other network device. The network tracing may include sending tracing packets down each of multiple routed paths between a source and a destination, at each hop through the network, or through a selected subset of the paths between a source and a destination. The network devices may add tracing information to the tracing packets, which an analysis system may review to determine characteristics of the network and the characteristics of the potentially many paths between a source and a destination.

## Claims

### Claim 1

A method comprising:
in a network device that connects a source device to a destination device through the network device:
determining whether to execute network tracing; and
when the network device determines to execute network tracing:
determining a set of network paths outgoing from the network device toward the destination device;
determining a selected set of network paths to trace from among the set of network paths; and
sending an outgoing network tracing packet down each network path in the selected set of network paths.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving an incoming network tracing packet at the network device; and
replicating the incoming network tracing packet to obtain the outgoing network tracing packets.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
adding tracing information to the outgoing network tracing packets prior to sending the outgoing network tracing packets down each network path.

### Claim 4 (depends on 2)

The method of claim 2, where the incoming network tracing packet comprises an injected tracing packet added into a network flow by a device other than the network device.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
receiving an outgoing network tracing packet at a different network device;
determining a new set of network paths outgoing from the different network device toward the destination device;
determining a newly selected set of network paths to trace from among the new set of network paths; and
sending an additional outgoing network tracing packet down each network path in the newly selected set of network paths.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
generating at least one of the outgoing network tracing packets within the network device itself, without replicating a received packet for use as the outgoing network tracing packet.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
reading tracing configuration information that specifies when to execute network tracing.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
reading tracing configuration information that constrains how many network paths may be present in the in the selected set of network paths.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
reading tracing configuration information that constrains how many consecutive hops an outgoing network tracing packet may take.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
reading tracing configuration information that specifies to execute network tracing after a specified number of hops have occurred in reaching the destination device.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
reading tracing configuration information that specifies to execute network tracing when a device condition has been met with respect to an operational parameter of the network device.

### Claim 12 (depends on 11)

The method of claim 11, where the device condition comprises: a buffer level has exceeded a buffer threshold, latency through the network device has exceeded a latency threshold, power consumption in the network device has exceeded a power consumption threshold, or any combination thereof.

### Claim 13

A network device comprising:
an input buffer operable to receive a packet from a source device;
an output buffer operable to hold an outgoing packet to a destination device;
tracing logic connected to the input buffer and the output buffer, the tracing logic configured to:
determine multiple paths along which a packet may travel from the network device to the destination device;
despite routing information in the network device specifying a particular path for the packet to the destination device, determine a selection of paths from among the multiple paths for tracing; and
send an outgoing network tracing packet down each path of the selection of paths.

### Claim 14 (depends on 13)

The device of claim 13, where the tracing logic is further configured to:
generate at least one of the outgoing network tracing packets internally in the network device, without replicating a received packet for use as an outgoing network tracing packet.

### Claim 15 (depends on 13)

The device of claim 13, where the tracing logic is further configured to:
generate at least one of the outgoing network tracing packets by replicating a received packet.

### Claim 16 (depends on 13)

The device of claim 13, where the tracing logic is further configured to:
recognize a received packet as a tracing packet received from a different network device; and
determine to continue tracing in response to receipt of the tracing packet.

### Claim 17 (depends on 16)

The device of claim 16, where the tracing logic is further configured to:
generate at least one of the outgoing network tracing packets by replicating the received packet.

### Claim 18

A device comprising:
a packet buffer in a network device, the packet buffer comprising a network packet received from a source network device and destined for a destination network device;
tracing logic connected to the packet buffer, the tracing logic configured to:
obtain tracing execution criteria;
evaluate the tracing execution criteria to determine whether to execute network tracing toward the destination network device;
when network tracing will proceed with respect to the destination network device for the network packet:
determine selected network paths to trace from among multiple network paths supported by the network device toward the destination network; and
sending an outgoing network tracing packet down each selected network path.

### Claim 19 (depends on 18)

The device of claim 18, where the tracing logic is further configured to:
generate the outgoing network tracing packets without replicating a received packet for use for the outgoing network tracing packets.

### Claim 20 (depends on 18)

The device of claim 18, where the tracing logic is further configured to:
generate the outgoing network tracing packets by replicating a received packet.
