Hi Chuck ! Followed with interest the problem and especially your solution and I have looked into the docu BUT:
DOCU says: " Before you begin: Configure the device interfaces. Configure OSPF or any other IGP protocol. Configure MPLS and LDP. <---------------------------------- REALLY ???????????????? Configure BGP. " Why do you need to enable MPLS and LDP for PIC ????? IMHO this is a documentation error , or do I miss something ? Regarding you suggestion of using it in a routing instance with version <15.1 I am not sure if that works as documentation says that it only works for vpnv4-BGP routes DOCU says "Before you begin: Configure LDP. Configure an IGP, either OSPF or IS-IS. Configure a Layer 3 VPN. Configure multiprotocol BGP for either an IPv4 VPN or an IPv6 VPN. <---------------- nthis seems to be a restriction regarding your proposed solution " Any more info on that available ? Regards alexander -----Ursprüngliche Nachricht----- Von: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] Im Auftrag von Chuck Anderson Gesendet: Mittwoch, 17. Februar 2016 21:19 An: juniper-nsp@puck.nether.net Betreff: Re: [j-nsp] Optimizing the FIB on MX On Wed, Feb 17, 2016 at 08:51:23PM +0100, Vincent Bernat wrote: > Being a bit unsatisfied with a pair of MX104 turning themselves as a > blackhole during BGP convergence, I am trying to reduce the size of > the FIB. > > I am in a simple situation: one upstream on each router, an iBGP > session between the two routers. I am also receiving a default route > along the full feed. Can you use Junos 15.1? Try this: http://www.juniper.net/techpubs/en_US/junos15.1/topics/concept/use-case-for- bgp-pic-for-inet-inet6-lu.html _______________________________________________ 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