cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jbp573
New Contributor

Adtran VLAN configuration as compared to Nortel/Avaya

Jump to solution

Coming from the Nortel World, I am used to 4 options with VLAN tagging options: Untag/Access, Tagged/Trunk,   UntagPVIDOnly (Native Vlan is untagged), and TagPVIDOnly (Tag the Native, Untag the Rest)

I think I'm correct in my thinking, but correct me if I'm wrong:

If I set a Native VLAN in AOS, that is essentially UntagPVIDOnly  option, if not, does it just tag everything?

Labels (1)
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
jayh
Honored Contributor
Honored Contributor

Re: Adtran VLAN configuration as compared to Nortel/Avaya

Jump to solution

jbp573 wrote:



Coming from the Nortel World, I am used to 4 options with VLAN tagging options: Untag/Access, Tagged/Trunk,   UntagPVIDOnly (Native Vlan is untagged), and TagPVIDOnly (Tag the Native, Untag the Rest)


"TagPVIDOnly (Tag the Native, Untag the Rest)" makes no sense as described. There can only be one untagged VLAN on an interface. This is true regardless of the manufacturer of the device.

If you were to able have multiple untagged VLANs, the device on the other end of the wire wouldn't be able to identify to which VLAN a frame belonged.

On an access port, the PVID (Port VLAN ID) is the only VLAN appearing there and is not tagged. By default, this is VLAN 1 but you can change it in configuration.

On a trunked port, the "Native" VLAN is untagged and all others are tagged. By default, the native VLAN is also VLAN 1 and it can also be changed in configuration.


If I set a Native VLAN in AOS, that is essentially UntagPVIDOnly  option, if not, does it just tag everything?


By default, VLAN 1 will be untagged and all else tagged. If you configure a VLAN other than 1 as native, then that configured VLAN will be untagged and all others tagged.

View solution in original post

0 Kudos
3 Replies
michael56
New Contributor III

Re: Adtran VLAN configuration as compared to Nortel/Avaya

Jump to solution

If your description of "TagPVIDOnly (Tag the Native, Untag the Rest)" is correct the tagging a VLAN interface in AOS would be the same. You can only have ONE native VLAN in AOS (default is vlan1).

jayh
Honored Contributor
Honored Contributor

Re: Adtran VLAN configuration as compared to Nortel/Avaya

Jump to solution

jbp573 wrote:



Coming from the Nortel World, I am used to 4 options with VLAN tagging options: Untag/Access, Tagged/Trunk,   UntagPVIDOnly (Native Vlan is untagged), and TagPVIDOnly (Tag the Native, Untag the Rest)


"TagPVIDOnly (Tag the Native, Untag the Rest)" makes no sense as described. There can only be one untagged VLAN on an interface. This is true regardless of the manufacturer of the device.

If you were to able have multiple untagged VLANs, the device on the other end of the wire wouldn't be able to identify to which VLAN a frame belonged.

On an access port, the PVID (Port VLAN ID) is the only VLAN appearing there and is not tagged. By default, this is VLAN 1 but you can change it in configuration.

On a trunked port, the "Native" VLAN is untagged and all others are tagged. By default, the native VLAN is also VLAN 1 and it can also be changed in configuration.


If I set a Native VLAN in AOS, that is essentially UntagPVIDOnly  option, if not, does it just tag everything?


By default, VLAN 1 will be untagged and all else tagged. If you configure a VLAN other than 1 as native, then that configured VLAN will be untagged and all others tagged.

View solution in original post

0 Kudos
jbp573
New Contributor

Re: Adtran VLAN configuration as compared to Nortel/Avaya

Jump to solution

Thank you all