[rbak-nsp] Internal QoS markings

[Mariano Juliá]

Dave,

The "propagate qos from" only works on the inbound direction (from the
network to the SmartEdge) and "propagate qos to" in the outbound direction.

I don't know your setup but assuming that you are trying to mark the packets
on LNS->LAC direction, there are a couple of possible scenarios.

The interface from the LNS to the core is IP only.

Apply "propagate qos from ip" to the interface facing the core and
"propagate qos to l2tp" on your L2TP peer configuration

If the interface from the LNS to the core is MPLS enabled, use the following
config;

router mpls
 propagate qos from mpls

If you want to use the short pipe model then also use "egress prefer
dscp-qos" under router mpls

Hope this helps.

Regards,

Mariano

On 17 March 2010 14:58, David Freedman <david.freedman at uk.clara.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Apparently it doesn't, this is the response I've had after trying to
> make it work (and it failing):
>
> ‘Using "propagate qos from ip" is not the right way to achieve what
> you want since subscriber is terminating on this box so with
> "propagate qos from ip", it will actually try to copy dscp in subscriber
> IP header from LAC direction and potentially put dscp back to ip header
> outbound toward core network. So basically, this will not work
>
> So this is apparently only relevant when we are acting as LAC?
>
> They suggested putting a metering policy on the sub, but we've already
> got a pwfq on there (it was the only way we found to get policing)
> wondering if the policer on the metering policy (rate xxx) actually
> works now..
>
> Dave.
>
>
> Ian Calderbank wrote:
> > It works :-)
> > Ian
> >
> > -----Original Message-----
> >
> >
> > Message: 1
> > Date: Thu, 18 Feb 2010 12:23:43 -0000
> > From: "David Freedman" <david.freedman at uk.clara.net>
> > To: <redback-nsp at puck.nether.net>
> > Subject: [rbak-nsp] Internal QoS markings
> > Message-ID:
> >       <7B8B0D6F623C3A40A0D0A80A66756E2B2C3552 at EXVS01.claranet.local>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> >
> > Was thinking of using the internal QoS markings to copy DSCP from
> subscriber
> > payload to the tunnel header but the tunnels originate in another
> context,
> > should be able to do this with "propagate qos from ip" and "propagate qos
> to
> > l2tp" in sub profile and l2tp peer respectively but concerned that these
> > markings may get lost when user's packet has to travel between PPAs.
> Perhaps
> > I'm just confusing this with the "not being able to do per-sub qos when
> > using an lns card group" issue (see earlier posts from me) so anybody
> doing
> > this and it working between multiple linecards, a simple "it works" would
> be
> > much appreciated!
> >
> > Dave.
> >
> > ---
> >
> >
> > _______________________________________________
> > redback-nsp mailing list
> > redback-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/redback-nsp
> >
>
>
>
>
> - --
>
> - ------------------------------------------------
> David Freedman
> Group Network Engineering
> Claranet Limited
> http://www.clara.net
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkug7g0ACgkQtFWeqpgEZrIt9gCfY20QBfA+u3fOka0n+lODXEmo
> DfoAnRATguwleFdZpSsC1HP7fqAP09K6
> =v+Gl
> -----END PGP SIGNATURE-----
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20100318/9f1a87aa/attachment.html>