Storing data associated with packet related metrics
Methods, systems, and computer readable media for storing data associated with packet related metrics are disclosed. According to one method, the method includes generating a test packet including a port tuple sequence number (PTSN), wherein the PTSN indicates a number of packets across multiple flows associated with a same port tuple, wherein the port tuple indicates an ingress port and an egress port that the test packet traverses at a device under test (DUT), and storing the PTSN in an entry of a data structure, wherein the entry is indexed by the port tuple.
1. A method for storing data associated with packet related metrics, the method comprising:
generating a test packet including a port tuple sequence number (PTSN), wherein the PTSN is generated using port or path awareness information and indicates a position of the test packet within a sequence of packets associated with a same port tuple, wherein the sequence of packets includes packets from different flows, wherein the port tuple indicates an ingress port and an egress port that the test packet traverses at a device under test (DUT);
storing the PTSN in an entry of a data structure, wherein the entry is indexed by the port tuple;
sending, to the ingress port of the DUT, the test packet;
receiving, from the egress port of the DUT, the test packet;
analyzing, using information in the test packet and information stored in the data structure, the test packet, wherein analyzing the test packet includes identifying, using the port tuple associated with the test packet, the entry associated with the test packet and determining, using a PTSN stored in the data structure entry and the PTSN in the test packet, whether the test packet is an expected packet in the sequence of packets associated with the same port tuple; and
generating one or more packet related metrics using the analyzing.
2. The method of claim 1 wherein the test packet includes a port tuple identifier (PTID) indicating the port tuple or a flow identifier (FLID) indicating an associated flow.
3. The method of claim 2 wherein the port tuple identifier indicates a traffic class or priority.
4. The method of claim 1 wherein generating the one or more packet related metrics includes generating a packet loss metric, a packet delay metric, a jitter metric, a packet count metric, a packet ordering metric, a session related metric, a port tuple related metric, or a DUT related metric.
5. The method of claim 1 wherein at least a portion of the data structure is stored in a static random-access memory (SRAM), a dynamic random-access memory (DRAM), a latch, a register, or a storage element.
6. The method of claim 1 wherein the DUT includes a network switch, a network router, or a network device.
7. The method of claim 1 wherein the PTSN is incremented for every original packet transmitted to the DUT that traverses the port tuple regardless of an FLID associated with the original packet.
8. The method of claim 1 wherein the port tuple is determined prior to generating the test packet.
9. A system for storing data associated with packet related metrics, the system comprising:
a memory; and
a processor;
wherein the system is implemented using the processor and the memory, wherein the system is configured to:
generate a test packet including a port tuple sequence number (PTSN), wherein the PTSN is generated using port or path awareness information and indicates a position of the test packet within a sequence of packets associated with a same port tuple, wherein the sequence of packets includes packets from different flows, wherein the port tuple indicates an ingress port and an egress port that the test packet traverses at a device under test (DUT);
store the PTSN in an entry of a data structure, wherein the entry is indexed by the port tuple;
send, to the ingress port of the DUT, the test packet;
receive, from the egress port of the DUT, the test packet;
analyze, using information in the test packet and information stored in the data structure, the test packet, wherein analyzing the test packet includes identifying, using the port tuple associated with the test packet, the entry associated with the test packet and determining, using a PTSN stored in the data structure entry and the PTSN in the test packet, whether the test packet is an expected packet in the sequence of packets associated with the same port tuple; and
generate one or more packet related metrics using the analyzing.
10. The system of claim 9 wherein the test packet includes a port tuple identifier (PTID) indicating the port tuple or a flow identifier (FLID) indicating an associated flow.
11. The system of claim 10 wherein the port tuple identifier indicates a traffic class or priority.
12. The system of claim 9 wherein the system is configured to generate a packet loss metric, a packet delay metric, a jitter metric, a packet count metric, a packet ordering metric, a session related metric, a port tuple related metric, or a DUT related metric.
13. The system of claim 9 wherein at least a portion of the data structure is stored in a static random-access memory (SRAM), a dynamic random-access memory (DRAM), a latch, a register, or a storage element.
14. The system of claim 9 wherein the DUT includes a network switch, a network router, or a network device.
15. The system of claim 9 wherein the system is configured to increment the PTSN for every original packet transmitted to the DUT that traverses the port tuple regardless of an FLID associated with the original packet.
16. The system of claim 9 wherein the system is configured to determine the port tuple prior to generating the test packet.
17. A non-transitory computer readable medium comprising computer executable instructions embodied in the non-transitory computer readable medium that when executed by a processor of a computer perform steps comprising:
generating a test packet including a port tuple sequence number (PTSN), wherein the PTSN is generated using port or path awareness information and indicates a position of the test packet within a sequence of packets associated with a same port tuple, wherein the sequence of packets includes packets from different flows, wherein the port tuple indicates an ingress port and an egress port that the test packet traverses at a device under test (DUT);
storing the PTSN in an entry of a data structure, wherein the entry is indexed by the port tuple;
sending, to the ingress port of the DUT, the test packet;
receiving, from the egress port of the DUT, the test packet;
analyzing, using information in the test packet and information stored in the data structure, the test packet, wherein analyzing the test packet includes identifying, using the port tuple associated with the test packet, the entry associated with the test packet and determining, using a PTSN stored in the data structure entry and the PTSN in the test packet, whether the test packet is an expected packet in the sequence of packets associated with the same port tuple; and
generating one or more packet related metrics using the analyzing.