# US 2020/0287967 A1 · Mirroring Dropped Packets

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

- Number: US 2020/0287967 A1
- Document ID: US20200287967A1
- Status: Published application
- Kind: A1
- Application number: 16/297,666
- Filed: 2019-03-10
- Published: 2020-09-10
- Earliest claimed: 2019-03-10
- Assignees: Mellanox Technologies Tlv Ltd.
- Applicants: Mellanox Technologies Tlv Ltd.
- Inventors: Barak Gafni; Aviv Kfir
- Web page: https://patentgrep.com/patent/US20200287967A1

## CPC

- H04L 49/208: {Port mirroring}
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 43/062: related to network traffic
- H04L 43/12: Network monitoring probes
- H04L 47/30: in combination with information about buffer occupancy at either end or at transit nodes
- H04L 47/32: by discarding or delaying data units, e.g. packets or frames
- H04L 49/25: Routing or path finding in a switch fabric
- H04L 49/3009: {Header conversion, routing tables or routing tags}
- H04L 49/3027: {Output queuing}
- H04L 49/555: {Error detection}
- H04L 69/22: Parsing or analysis of headers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, a network device, includes ports to serve as ingress ports and egress ports, a memory to store received network packets, a switch fabric, a controller to monitor queues of the egress ports and make a decision to drop at least a network packet of the received network packets, the network packet having a first destination address associated with a first network node, and mirroring circuitry to encapsulate the network packet with an encapsulation header including a second destination address different from the first destination address, and feedback the encapsulated network packet into a processing pipeline of the received network packets within the network device at a point in the processing pipeline that is prior to egress port assignment, wherein the switch fabric is configured to forward the encapsulated network packet to the packet analyzer responsively to the second destination address in the encapsulation header.

## Claims

### Claim 1

A network device, comprising:
a plurality of ports configured to serve as ingress ports for receiving network packets from a network and as egress ports for forwarding at least some of the network packets;
a switch fabric configured to selectively connect the ingress ports with the egress ports according to at least destination addresses of the received network packets;
a controller configured to monitor queues of the egress ports and make a decision to drop at least a network packet of the received network packets, the network packet having a first destination address associated with a first network node; and
mirroring circuitry configured to:
encapsulate the network packet yielding an encapsulated network packet with an encapsulation header which includes a second destination address different from the first destination address; and
feedback the encapsulated network packet into a processing pipeline of the received network packets within the network device at a point in the processing pipeline that is prior to egress port assignment, wherein the switch fabric is configured to forward the encapsulated network packet to a packet analyzer based on at least the second destination address in the encapsulation header.

### Claim 2 (depends on 1)

The device according to claim 1, wherein the mirroring circuitry is configured to encapsulate the network packet after the network packet has been assigned to one of the egress ports assigned for forwarding traffic to the first network node.

### Claim 3 (depends on 1)

The device according to claim 1, further comprising a memory, wherein the mirroring circuitry is configured to encapsulate the network packet after at least some data of the network packet has been read from the memory to one of the egress ports assigned for forwarding traffic to the first network node.

### Claim 4 (depends on 1)

The device according to claim 1, wherein the controller is configured to make a decision to drain one of the queues comprising multiple ones of the network packets resulting in dropping the multiple network packets including the network packet.

### Claim 5 (depends on 1)

The device according to claim 1, wherein the packet analyzer is disposed externally to the network device, the switch fabric being configured to assign the encapsulated network packet to one of the egress ports, the assigned egress port being configured to forward the encapsulated network packet to the packet analyzer via the network.

### Claim 6 (depends on 1)

The device according to claim 1, wherein the packet analyzer is disposed externally to the network device, the switch fabric being configured to assign the encapsulated network packet to one of the egress ports, the assigned egress port being configured to forward the encapsulated network packet to the packet analyzer, which is directly connected to the network device.

### Claim 7 (depends on 1)

The device according to claim 1, further comprising a processing unit, wherein the packet analyzer is comprised in the processing unit, the switch fabric being configured to transfer the encapsulated network packet to the packet analyzer in the processing unit responsively to reading at least the second destination address in the encapsulation header.

### Claim 8 (depends on 1)

The device according to claim 1, further comprising a processing unit, wherein the processing unit runs an agent connected to the packet analyzer, the switch fabric being configured to transfer the encapsulated network packet to the agent in the processing unit responsively to reading at least the second destination address in the encapsulation header.

### Claim 9 (depends on 1)

The device according to claim 1, wherein the mirroring circuitry is configured to include metadata in the encapsulation header of the encapsulated network packet.

### Claim 10 (depends on 9)

The device according to claim 9, wherein the metadata includes one or more of the following: an ingress port identification; an ingress priority; an ingress timestamp; an egress timestamp; a pad count of padding of the network packet; a packet switch network identification; an identification of an egress port of the first destination address; whether the network packet is a unicast or multicast packet; an egress queue; an ingress buffer fill level; an egress buffer fill level; flags; a mirror reason; and a mirror agent identification.

### Claim 11

A mirroring method, comprising:
receiving network packets in a network device from a network;
forwarding at least some of the network packets;
storing the received network packets;
selectively connecting ingress ports with egress ports according to at least destination addresses of the received network packets;
monitoring queues of the egress ports;
making a decision to drop at least a network packet of the received network packets, the network packet having a first destination address associated with a first network node;
encapsulating the network packet yielding an encapsulated network packet with an encapsulation header which includes a second destination address different from the first destination address;
feedbacking the encapsulated network packet into a processing pipeline of the received network packets within the network device at a point in the processing pipeline that is prior to egress port assignment; and
forwarding the encapsulated network packet to a packet analyzer based on at least the second destination address in the encapsulation header.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the encapsulating is performed after the network packet has been assigned to one of the egress ports assigned for forwarding traffic to the first network node.

### Claim 13 (depends on 11)

The method according to claim 11, wherein the encapsulating is performed after at least some data of the network packet has been read from a memory to one of the egress ports assigned for forwarding traffic to the first network node.

### Claim 14 (depends on 11)

The method according to claim 11, further comprising making a decision to drain one of the queues comprising multiple ones of the network packets resulting in dropping the multiple network packets including the network packet.

### Claim 15 (depends on 11)

The method according to claim 11, wherein the packet analyzer is disposed externally to the network device, the method further comprising: assigning the encapsulated network packet to one of the egress ports; and forwarding the encapsulated network packet to the packet analyzer via the network.

### Claim 16 (depends on 11)

The method according to claim 11, wherein the packet analyzer is disposed externally to the network device, the method further comprising: assigning the encapsulated network packet to one of the egress ports; and forwarding the encapsulated network packet to the packet analyzer, which is directly connected to the network device.

### Claim 17 (depends on 11)

The method according to claim 11, wherein the packet analyzer is comprised in a processing unit of the network device, further comprising transferring the encapsulated network packet to the packet analyzer in the processing unit responsively to reading at least the second destination address in the encapsulation header.

### Claim 18 (depends on 11)

The method according to claim 11, wherein a processing unit of the network device runs an agent connected to the packet analyzer, further comprising transferring the encapsulated network packet to the agent in the processing unit responsively to reading at least the second destination address in the encapsulation header.

### Claim 19 (depends on 11)

The method according to claim 11, further comprising including metadata in the encapsulation header of the encapsulated network packet.

### Claim 20 (depends on 19)

The method according to claim 19, wherein the metadata includes one or more of the following: an ingress port identification; an ingress priority; an ingress timestamp; an egress timestamp; a pad count of padding of the network packet; a packet switch network identification; an identification of an egress port of the first destination address; whether the network packet is a unicast or multicast packet; an egress queue; an ingress buffer fill level; an egress buffer fill level; flags; a mirror reason; and a mirror agent identification.
