[c-nsp] cisco-nsp Digest, Vol 156, Issue 3

Methsri Wickramarathna mmethw2003 at gmail.com
Mon Nov 2 12:32:25 EST 2015


Thanks Lukas,
I can do the marking on the physical interface if needed. Can you guide me
through this because my ISP is requested to set priority according to
802.1P standard in order to priorities our traffic over their backbone.

On Mon, Nov 2, 2015 at 10:30 PM, <cisco-nsp-request at puck.nether.net> wrote:

> Send cisco-nsp mailing list submissions to
>         cisco-nsp at puck.nether.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://puck.nether.net/mailman/listinfo/cisco-nsp
> or, via email, send a message with subject or body 'help' to
>         cisco-nsp-request at puck.nether.net
>
> You can reach the person managing the list at
>         cisco-nsp-owner at puck.nether.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of cisco-nsp digest..."
>
>
> Today's Topics:
>
>    1. Re: IEEE 802.1P QoS Issue........ (Lukas Tribus)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 2 Nov 2015 16:29:16 +0100
> From: Lukas Tribus <luky-37 at hotmail.com>
> To: Peter Rathlev <peter at rathlev.dk>, Methsri Wickramarathna
>         <mmethw2003 at gmail.com>
> Cc: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] IEEE 802.1P QoS Issue........
> Message-ID: <DUB123-W40BF266E709677301F50FDED2C0 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
> > The 802.1p bits are carried in the 802.1Q tag
>
> Yes, but ...
>
>
>
> > , so you would have to mark??on the physical interface,
> > not the subinterface.
>
> Not so true. Just because you are on a subinterface, doesn't mean
> you can't set cos values.
>
> Yes, the COS field isn't?theoretically "visible" if you strip the
> dot1q header from the packet?on the wire, however that
> doesn't mean the information can't?propagate through the
> stack anyway.
>
> "qos-groups" are available on a lot of platforms, which is
> an internal/local QoS?parameter that you can't see on the wire,
> yet you still can set it on ingress and match on egress.
> Because it propagates through the stack/fabric, just as COS
> does.
>
>
> Of course, certain platforms may be unable to set COS in
> this situation, but?thats?a specific limitation then.
>
>
> (setting COS on a subif works just fine on a ISR G2 for example).
>
>
> Lukas
>
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> cisco-nsp mailing list
> cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
>
> ------------------------------
>
> End of cisco-nsp Digest, Vol 156, Issue 3
> *****************************************
>



-- 
-- 
________´$$$$`_____________________________,,,_
_______´$$$$$$$`_________________________´$$$`
________`$$$$$$$`______,,________,,_______´$$$$´
_________`$$$$$$$`____´$$`_____´$$`____´$$$$$´
__________`$$$$$$$`_´$$$$$`_´$$$$$`__´$$$$$$$´
___________`$$$$$$$_$$$$$$$_$$$$$$$_´$$$$$$$´_
____________`$$$$$$_$$$$$$$_$$$$$$$`´$$$$$$´_
___,,,,,,______`$$$$$$_$$$$$$$_$$$$$$$_$$$$$$´_
_´$$$$$`____`$$$$$$_$$$$$$$_$$$$$$$_$$$$$$´_
´$$$$$$$$$`´$$$$$$$_$$$$$$$_$$$$$$$_$$$$$´_
´$$$$$$$$$$$$$$$$$$_$$$$$$$_$$$$$$$_$$$$$´_
___`$$$$$$$$$$$$$$$_$$$$$$$_$$$$$$_$$$$$$´_
______`$$$$$$$$$$$$$_$$$$$__$$_$$$$$$_$$´_
_______`$$$$$$$$$$$$,___,$$$$,_____,$$$$$´_
_________`$$$$$$$$$$$$$$$$$$$$$$$$$$$$$´_
__________`$$$$$$$$$$$$$$$$$$$$$$$$$$$´_
____________`$$$$$$$$$$$$$$$$$$$$$$$$´_
_______________`$$$$$$$$$$$$$$$$$$$$´_

~~( ŊëŌ )~~


More information about the cisco-nsp mailing list