juniper:how_many_packets_per_second_per_port_are_needed_to_achieve_wire-speed
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
juniper:how_many_packets_per_second_per_port_are_needed_to_achieve_wire-speed [2024/02/18 09:30] – aperez | juniper:how_many_packets_per_second_per_port_are_needed_to_achieve_wire-speed [2024/02/18 09:38] – aperez | ||
---|---|---|---|
Line 19: | Line 19: | ||
- | {{ : | + | {{ : |
Line 52: | Line 52: | ||
- | {{ :juniper:jupiter3.jpeg?400 |}} | + | |
+ | |||
+ | {{ :juniper:juniper0.1.png?600 |}} | ||
+ | |||
+ | |||
**Figure 2: 802.1Q tagged minimum frame** | **Figure 2: 802.1Q tagged minimum frame** | ||
Line 76: | 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: | 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** | **Figure 3: 802.1ad tagged frame** |
juniper/how_many_packets_per_second_per_port_are_needed_to_achieve_wire-speed.txt · Last modified: 2024/02/18 09:41 by aperez