NETWORK TRAFFIC DEBUGGER

• US 20140201354A1
• Filed: 01/17/2013
• Published: 07/17/2014
• Est. Priority Date: 01/17/2013
• Status: Abandoned Application

• Current Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Matthews, Brad, Agarwal, Puneet, Kwan, Bruce
• Application Number:
  US13/743,780
• Publication Number:
  US 20140201354A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 43/028 by filtering
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/28 in relation to timing considerations
• CPC Class Codes: H04L 47/32 by discarding or delaying data units, e.g. packets or frames

Abstract

Disclosed are various embodiments that relate to a network switch. The switch determines whether a network packet is associated with a packet processing context, the packet processing context specifying a condition of handling network packets processed in the switch. The switch determines debug metadata for the network packet in response to the network packet being associated with the packet processing context; and the debug metadata is stored in a capture buffer.

Claims

1. A system comprising:

processing circuitry implemented in a switch, the processing circuitry being configured to;

determine whether a network packet has been dropped by a queue associated with the switch;

determine whether the network packet is associated with a packet characteristic that is intrinsic to the network packet;

determine debug metadata for the network packet to facilitate a debugging of the switch; and

store the debug metadata in a memory associated with the switch.

2. The system of claim 1, wherein the packet characteristic is at least one of a packet length, a packet class, a packet priority, or a packet application type.

3. The system of claim 1, wherein the processing circuitry that is configured to determine whether the network packet is associated with a packet characteristic is further configured to determine whether the network packet is generated by a network application.

4. The system of claim 1, wherein the debug metadata is at least one of a local port associated with routing the network packet via the switch, a packet delay associated with routing the network packet via the switch, a class of service of the network packet, a portion of data contained by the network packet, or an event code that specifies a reason why the network packet was dropped by the queue.

5. The system of claim 4, wherein one of a plurality of event codes specifies a buffer full event.

6. A switch comprising:

an event detector configured to determine whether a network packet is associated with a packet processing event;

a filtering engine configured to determine whether the network packet is associated with a packet characteristic;

a data collector configured to determine debug metadata in response to the network packet being associated with the packet characteristic and being associated with the packet processing context; and

a capture buffer configured to store the debug metadata.

7. The switch of claim 6, wherein the packet processing event comprises a corresponding queue exceeding a predefined queue length.

8. The switch of claim 6, wherein the packet processing event comprises a power consumption level of the switch exceeding a predefined threshold level.

9. The switch of claim 6, wherein the packet processing event comprises a packet delay associated with the network packet exceeding a time based threshold.

10. The switch of claim 9, wherein the packet delay is based at least upon a time stamp associated with the network packet, wherein the time stamp is at least one of a local time stamp that is local with respect to the switch or a synchronized time stamp that is synchronized with respect to a plurality of switches.

11. The switch of claim 6, wherein the switch further comprises a sampler configured to select a predefined proportion of a plurality of network packets received by the switch, thereby causing a reduction in an amount of debug metadata stored by the capture buffer.

12. The switch of claim 6, wherein the debug metadata is at least one of a local port associated with routing the network packet via the switch, a packet delay associated with routing the network packet via the switch, a class of service of the network packet, a portion of data contained by the network packet, or an event code for the network packet.

13. The switch of claim 6, further comprising a packetization engine configured to aggregate at least a portion of the debug metadata stored in the capture buffer into a network status packet, the packetization engine being further configured to transmit the network status packet to a user.

14. The switch of claim 6, wherein the capture buffer is configured to respond to a read request by allowing a user to read at least a portion of the debug metadata from the capture buffer.

15. A method comprising:

determining whether a network packet is associated with a packet processing context, the packet processing context specifying a condition of handling the network packet processed in a switch;

determining debug metadata for the network packet in response to the network packet being associated with the packet processing context; and

storing the debug metadata in a capture buffer.

16. The method of claim 15, further comprising filtering the network packet according to a packet characteristic, thereby causing a reduction in an amount of debug metadata stored by the capture buffer.

17. The method of claim 15, wherein the packet processing context comprises a dropped packet event.

18. The method of claim 15, further comprising transmitting a network status message to a user, the network status message comprising the debug metadata.

19. The method of claim 18, wherein the network status message further comprises a network state metric, the network state metric being determined based at least upon a routing of a plurality of network packets via the switch.

20. The method of claim 15, wherein the debug metadata is at least one of a local port associated with routing the network packet via the switch, a packet delay associated with routing the network packet via the switch, a class of service of the network packet, a portion of data contained by the network packet, or an event code for the network packet.