Differences

This shows you the differences between two versions of the page.

--- juniper:how_many_packets_per_second_per_port_are_needed_to_achieve_wire-speed [2024/02/18 09:27] – aperez
+++ juniper:how_many_packets_per_second_per_port_are_needed_to_achieve_wire-speed [2024/02/18 09:41] (current) – aperez
@@ Line 17: / Line 17: @@
 We need to see how much ‘space’ each packet will occupy so we will look at the frame size in which the smallest packet will be encapsulated, as well as the inter-frame gap, and the preamble since they occupy ‘space’ in between frames.
-{{ :juniper:renditiondownload.jpg?400 |}}
+{{ :juniper:juniper0.png?800 |}}
 **Figure 1: ‘Space’ Occupied by the smallest packet**
@@ Line 44: / Line 52: @@
-{{ :juniper:jupiter3.jpeg?400 |}}
+{{ :juniper:juniper0.1.png?600 |}}
 **Figure 2: 802.1Q tagged minimum frame**
@@ Line 68: / Line 81: @@
 An amendment to the 802.1Q standard is the 802.1ad or otherwise known as Q-in-Q. The purpose of this amendment was to create a method for users to run their own VLANs inside the VLANs offered by a Metro Ethernet Service Provider. To achieve this goal a second tag is inserted in the Ethernet frame to distinguish the customer VLANs as shown below:
-{{ :juniper:jupiter5.jpeg?400 |}}
+{{ :juniper:juniper10.jpg?600 |}}
 **Figure 3: 802.1ad tagged frame**
@@ Line 88: / Line 105: @@
 For our example we will look at a packet with 3 labels placed in it:
-{{ :juniper:juniper7.jpg?400 |}}
+{{ :juniper:juniper11.jpg?600 |}}
+{{ :juniper:juniper12.gif?600 |}}
 **Figure 4: MPLS tagged frame**