diff --git a/images/693_OpenShift_QinQ_SR-IOV_CNI_0624.png b/images/693_OpenShift_QinQ_SR-IOV_CNI_0624.png
new file mode 100644
index 0000000000..7fd62b6f38
Binary files /dev/null and b/images/693_OpenShift_QinQ_SR-IOV_CNI_0624.png differ
diff --git a/modules/nw-sriov-about-qinq.adoc b/modules/nw-sriov-about-qinq.adoc
index 59fe851ec0..d753934394 100644
--- a/modules/nw-sriov-about-qinq.adoc
+++ b/modules/nw-sriov-about-qinq.adoc
@@ -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.