Tagged and untagged VLAN ports
Overview
The NFM-P supports tagged and untagged ports as VLAN access ports. The following table describes the behavior when ingress tagged or untagged traffic enters and then exits a VLAN.
Table 16-1: Tagged and untagged traffic behavior
|
Ingress traffic configuration |
Ingress VLAN port configuration |
Action |
Egress VLAN port configuration and action |
|
Untagged |
Untagged |
The VLAN allows the traffic and passes it based on the default VLAN ID.
The MAC address of the destination is learned. |
If the egress VLAN port is untagged, the traffic remains untagged. |
|
If the egress VLAN port is tagged, a tag is added to the traffic. |
|
Tagged |
If the egress VLAN port is untagged, the traffic remains untagged. |
|
If the egress VLAN port is tagged, a tag is added to the traffic. |
|
Tagged |
Untagged |
The VLAN allows the traffic if the tag matches the default VLAN ID.
The MAC address of the destination is learned.
If the tag does not match the default VLAN ID, the traffic is dropped. |
If the egress VLAN port is untagged, the tag of the traffic is removed. |
|
If the egress VLAN port is tagged, the traffic remains tagged. |
|
Tagged |
The VLAN allows the traffic:
The MAC address of the destination is learned.
If the tag does not meet either condition, the traffic is dropped. |
If the egress VLAN port is untagged, the tag of the traffic is removed. |
|
If the egress VLAN port is tagged, the traffic remains tagged. |
The following figures show how tagged and untagged traffic is handled on the devices, based on the VLAN ID.
