![]() |
![]() |
Table�45 shows the relationship between Port VLAN / Trunk Mode / VLAN Binding parameters when using the VLAN Operational Rules.
VLAN Binding |
Trunk Mode |
Description |
---|---|---|
Static |
Clear |
Ingress: Untagged frames are classified to the VLAN associated with the port on which the frame is received. Tagged frames are classified to the VLAN identified by the VLAN tag in the tag header of the frame. Forwarding: Only forward frames to the port for the assigned VLAN. Egress: All frames transmitted will be sent with no tagging. |
Static |
802.1Q Multi-layer |
Ingress: Untagged frames are classified to the VLAN associated with the port on which the frame is received. Tagged frames are classified to the VLAN identified by the VLAN tag in the tag header of the frame. Forwarding: Only forward frames to the port for the assigned VLAN. Egress: All frames transmitted out of the port will be tagged using the IEEE 802.1Q/Multi-Layer tag header format. The tag used will be that assigned to the port. |
Bind to All |
Clear |
NOT RECOMMENDED Ingress: Untagged frames are classified to the VLAN associated with the port on which the frame is received. Tagged frames are classified to the VLAN identified by the VLAN tag in the tag header of the frame. Forwarding: All broadcast frames from all VLANs will be forwarded to the port. Egress: All frames transmitted will be sent with no tagging. |
Bind to All |
802.1Q Multi-layer |
Ingress: Untagged frames are classified to the VLAN associated with the port on which the frame is received. Tagged frames are classified to the VLAN identified by the VLAN tag in the frame's tag header. Note: For 802.1q mode: if a tagged frame is received, but the VLAN for that tagged frame does not exist on the switch, that frame will be placed onto the port VLAN assigned to the port. This may cause unicast and broadcast VLAN traffic from other VLANs to be seen on the port VLAN. To avoid this behavior, you can set the port VLAN into the "discard" VLAN which will drop all untagged frames and tagged frames with unknown VLAN IDs. For Multi-layer: if a tagged frame is received, but the VLAN for that tagged frame does not exists on the switch, that frame will be dropped. Forwarding: All broadcast frames from all VLANs will be forwarded to the port. Egress: All frames transmitted out of the port to be tagged using the IEEE 802.1Q/Multi-Layer tag header format. The tagged used will be that of the VLAN in which the frame was received. |
Bind to Received |
Clear |
NOT RECOMMENDED Ingress: Untagged frames are classified to the VLAN associated with the port on which the frame is received. Tagged frames are classified to the VLAN identified by the VLAN tag in the tag header of the frame. Forwarding: All broadcast frames from all VLANs learned on the port will be forwarded. Egress: All frames transmitted will be sent with no tagging. |
Bind to Received |
802.1Q Multi-layer |
Ingress: Untagged frames are classified to the VLAN associated with the port on which the frame is received. Tagged frames are classified to the VLAN identified by the VLAN tag in the frame's tag header.
Note: For 802.1q mode: if a tagged frame is received, but the VLAN for that tagged frame does not exist on the switch, that frame will be placed onto the port VLAN assigned to the port. This may cause unicast and broadcast VLAN traffic from other VLANs to be seen on the port VLAN. To avoid this behavior, you can set the port VLAN into the "discard" VLAN which will drop all untagged frames and tagged frames with unknown VLAN IDs. Forwarding: All broadcast frames from all VLANs learned on the port will be forwarded. Egress: All frames transmitted out of the port to be tagged using the IEEE 802.1Q/Multi-Layer tag header format. The tagged used will be that of the VLAN in which the frame was received. |
![]() |
![]() |