[j-nsp] RES: Juniper MX VPLS S-Tag pop/push with QoS
alexandre.guimaraes at ascenty.com
Fri Nov 13 11:23:29 EST 2015
Could you please share some config? Ihad tried that with no results.
De: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] Em nome de Marcin Wojcik
Enviada em: quarta-feira, 11 de novembro de 2015 09:01
Para: Nealon, Mike
Cc: juniper-nsp at puck.nether.net
Assunto: Re: [j-nsp] Juniper MX VPLS S-Tag pop/push with QoS
I'd use 'learn-vlan-1p-priority X' in your filter in order to make sure the QoS classification is based on the S-tag.
'user-vlan-1p-priority X' is useful if you want to base the classification on the C-Tag.
On Fri, Nov 6, 2015 at 5:57 PM, Nealon, Mike <mnealon at lightower.com> wrote:
> Hello, does anybody have knowledge of the order of operations relative to QoS classification of a packet when using a pop/push mechanism in a VPLS instance? I'm trying to make sure packets are classified based on the S-Tag that I am "popping", but I fear the pop may happen before the classification. I need the QoS/P-Bit information in the S-Tag to persist across the network. So I guess the actual question is: How is QoS information persistence achieved when you need to also provide VLAN ambiguity?
> Thanks all,
> juniper-nsp mailing list juniper-nsp at puck.nether.net
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp