i dont believe that is supported on CX switches. perhaps others can chime in.
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
------------------------------
Original Message:
Sent: Jul 05, 2023 09:28 AM
From: tommyd
Subject: Priority tagged vlan
It is not a challenge, I am just curious. I do not use this kind of configuration, however I might have some place where tagging of the native vlan would be useful because it allows to carry CoS bits. But, on the other hand, it is to exotic and probably unsupported on most end systems.
I already know that following syntax is possible and valid.
interface 1/1/2
no shutdown
vlan trunk native 1 tag
vlan trunk allowed 1
The resulting frame looks like this
However when the priority tagging is used the ID field would be 0000 0000 0000.
Original Message:
Sent: Jul 05, 2023 09:11 AM
From: Thomas Siegenthaler
Subject: Priority tagged vlan
Hi Tommyd
Are we talking of edge-ports here (e.g. where end systems like a server or clients are connected) or network ports (connections to other switches etc.)?
I could imaging that tagging the native VLAN to the link could solve your challenge even though I don't know for sure.
Regards,
Thomas
Original Message:
Sent: Jul 05, 2023 08:10 AM
From: tommyd
Subject: Priority tagged vlan
I am digging into QoS stuff and have a question. Does AOS-CX support (or plan to) Priority Tagged Vlans? I mean frames with a 802.1Q header where VLAN-ID field is all zeroes? I just learnt that Cisco supports encapsulation priority-tagged or encapsulation dot1Q 0 syntax . Does AOS-CX have something like this?