NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
VLAN tagging and PVID
Hi, I am new to Netgear switches so apologies if I have missed something basic, I have a HP switching background. I have come across a port configuration which has the same VLAN as tagged as ...
- The untagged config for 300 does make the switch removing the tags on outgoing frames, the PVID 300 config does add the tag for VLAN 300 assigning the untagged traffic to the VLAN 300.
Show the related Web UI VLAN configs - the Web UI is the only supported way to manage these devices.
In brief, the PVID config (a feature coming from the ability of overloading VLANs [mostly not supported on Netgear switches]) does define the VLAN incoming untagged frames are associated to - so if VLAN ID 300 is intended to be untagged (access port, or on a trunk port) the PIVD must be set to 300, too. Said that, only one VLAN should must be configured as [U]ntagged - lack of support for 802.1q asymetric VLANs.
Hi,
Thanks for the reply.
Unfortunately I only have CLI outputs for this switch. From what I gather from the reply it would appear the PVID takes precedence over the VLAN tagging statement and therefore the VLAN 300 traffic would be seen as untagged in this instance.
It was more so for me to understand to behaviour of such a port config where historically from what I have seen if you had a PVID set and then added it also the same VLAN ID as tagged you would only have one or the other.
- The untagged config for 300 does make the switch removing the tags on outgoing frames, the PVID 300 config does add the tag for VLAN 300 assigning the untagged traffic to the VLAN 300.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
