[j-nsp] Ingress QoS Marking Now Fully Supported on MX Routers - Junos 14.2R3.8 Release

[Masood Ahmad Shah]

On Mon, May 18, 2015 at 12:39 AM, Chuck Anderson <cra at wpi.edu> wrote:

> Scroll down to the 4th top-level bullet:
>
> "Support for packet marking schemes on a per-customer basis (MX Series
> only)"
>

[Masood] I would say that this is incorrect and misleading. It should be MX
Series Trio based only and not an MX that runs with DPC's etc.



>
> On Sun, May 17, 2015 at 09:23:37PM +1000, Masood Ahmad Shah wrote:
> > Thanks for sharing, Mark!
> > Are you sure that it supports all Trio-bsaed cards and afterwards...
> > Juniper documentation confirm it for the Type-5 FPC (T4K) only though.
> >
> > On Sun, May 17, 2015 at 7:02 AM, Mark Tinka <mark.tinka at seacom.mu>
> wrote:
> >
> > > Hi all.
> > >
> > > Gosh, what a road this has been!
> > >
> > > Some of you may recall I started moaning and chasing Juniper about this
> > > way back in 2008. Well, finally, we have reached the promised land.
> > >
> > > Junos 14.2R3.8 for the MX was released last night. Prior to its
> release,
> > > we have been testing an engineering version of 14.2R1, where Juniper
> > > developed support for ingress marking/re-marking of QoS values on
> > > traffic entering an MX router.
> > >
> > > As you know, Juniper have traditionally done marking/re-marking on
> > > egress, which did not provide sufficient granularity for us, and I am
> > > sure several others on this list. With 14.2R3.8, Juniper now support
> > > ingress marking/re-marking of QoS values, negating the need for egress
> > > marking if what you're looking for is fine-grained marking/re-marking.
> > >
> > > Juniper are calling the feature Policy Map. I can get into more details
> > > of how this would work if anyone is interested, but below are some key
> > > features you might find useful:
> > >
> > >     a) Policy Map is currently supported only on the MX routers.
> > >     b) Requires a minimum of Trio-based line cards.
> > >     c) First shipping in Junos 14.2R3.8.
> > >     d) Supported for IPP, DSCP, MPLS EXP, 802.1p and 802.1ad.
> > >     e) Supported for the inet, inet6, ccc, vpls, mpls and any address
> > > families.
> > >     f) Application can be either via the [class-of-service] hierarchy
> or
> > > via a firewall filter.
> > >     g) Supersedes traditional Junos CoS Rewrite actions.
> > >
> > > You can find some basic details on the feature here:
> > >
> > >
> > >
> > >
> http://www.juniper.net/techpubs/en_US/junos14.2/information-products/topic-collections/release-notes/14.2/topic-83366.html#jd0e3370
> > >
> > > It's been a long time coming.
> > >
> > > I'm very pleased to see this feature, and hope the rest of you find it
> > > as useful as we do.
> > >
> > > Mark.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>