Re: [j-nsp] 6PE RR & next-hop resolution best practices
Hi James > James Jun > Sent: 16 May 2015 16:20 > > The problem however is that I'm using the P's also as route-reflectors for > distributing BGP throughout the network. So, I need the RR's to make > correct BGP best-path decisions, but they can't do that on 6PE routes without > having inet6.3 table to reference the ipv4-mapped-in-v6 next-hops against. > I'm sorry I misunderstood the problem so the problem isn't that the P's are trying to do IPv6 lookup instead of label-switch the packets between PEs but the problem is that RRs are not advertising the IPv6 prefixes because they can't select the best paths so the IPv6 prefixes are not being exchanged between the PEs right? To resolve the NHs you can do: set routing-options rib-groups 0-to-6 import-rib inet.0 set routing-options rib-groups 0-to-6 import-rib inet6.0 set routing-options rib-groups 0-to-6 import-policy loopbacks set protocols isis/ospf rib-group inet 0-to-6 This should create the ipv4-mapped-in-v6 (::ipv4) addresses in inet6 And then you tell BGP to resolve the NHs in inet.6: set routing-options resolution rib bgp.inet6.0 resolution-ribs inet6.0 adam --- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] interoperation between MSTP and old STP
Hi Victor, On 15 May 2015, at 6:06 pm, Victor Sudakov wrote: > Colleagues, > > I have several EX4200 switches with redundant links, all are running > MSTP with a couple of MSTIs. > > If I include an older switch which can only run old-fashioned STP, > will they interoperate and still keep the topology loop-free? What if > it can run STP and RSTP, but not MSTP? They will interoperate, however there are key differences to be aware of: - STP/RSTP forms topology with STP bridges regardless of whether correct VLANs are trunked on ports - this can mean that topologies may form that isolate VLAN segments if you haven't configured trunked ports correctly on all links - STP/RSTP bridges will treat an MSTP network (regardless of how many switches it contains) as single contiguous bridge, so you may find that the ports that block in your RSTP network aren't quite where you expected them to be when simply counting the radius from the root bridge. > > A link to some good documentation is also appreciated. > > TIA for any input. I highly recommend Petr Lapukhov's work here: http://blog.internetworkexpert.com/2010/02/22/understanding-mstp/ The configuration and outputs are IOS-based and there are a few PVST+ interop discussions, but the supporting protocol description and break-down is truly excellent. Cheers, Ben ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Ingress QoS Marking Now Fully Supported on MX Routers - Junos 14.2R3.8 Release
On Mon, May 18, 2015 at 12:39 AM, Chuck Anderson 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 > 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@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Ingress QoS Marking Now Fully Supported on MX Routers - Junos 14.2R3.8 Release
On 17/May/15 16:39, Chuck Anderson wrote: > Scroll down to the 4th top-level bullet: > > "Support for packet marking schemes on a per-customer basis (MX Series > only)" That one. And yes, I confirm it's on the Trio cards for the MX (included MX80, of course). Mark. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Ingress QoS Marking Now Fully Supported on MX Routers - Junos 14.2R3.8 Release
Scroll down to the 4th top-level bullet: "Support for packet marking schemes on a per-customer basis (MX Series only)" 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 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Ingress QoS Marking Now Fully Supported on MX Routers - Junos 14.2R3.8 Release
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 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@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
