mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
TELCODOCS-1683-image adding images
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
e580b8191d
commit
09952eced7
BIN
images/693_OpenShift_QinQ_SR-IOV_CNI_0624.png
Normal file
BIN
images/693_OpenShift_QinQ_SR-IOV_CNI_0624.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
@@ -11,7 +11,7 @@ In traditional VLAN setups, frames typically contain a single VLAN tag, such as
|
||||
|
||||
QinQ facilitates the creation of nested VLANs by using double VLAN tagging, enabling finer segmentation and isolation of traffic within a network environment. This approach is particularly valuable in service provider networks where you need to deliver VLAN-based services to multiple customers over a common infrastructure, while ensuring separation and isolation of traffic.
|
||||
|
||||
When two VLAN tags are present in a packet, the outer VLAN tag can be either 802.1Q or 802.1ad. The inner VLAN tag must always be 802.1Q.
|
||||
image::693_OpenShift_QinQ_SR-IOV_CNI_0624.png[QinQ]
|
||||
|
||||
The {product-title} SR-IOV solution already supports setting the VLAN protocol on the `SriovNetwork` custom resource (CR). The virtual function (VF) can use this protocol to set the VLAN tag, also known as the outer tag. Pods can then use the VLAN CNI plugin to configure the inner tag.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user