Thank you I have managed to find a nice document over the weekend that shed some light on the use of COMPOSITE NHs so then the documentation on Juniper web page finally made sense
I think it is preferable to have this feature enabled in an case as it speeds up convergence since it breaks up the VPN Label-->Transport Label relation. So with this feature enabled all the VPN Labels(prefixes) can have the NH information updated at once. Well how much time is saved depends on the VPN label allocation mode (per-prefix/per-NH/per-VPN) and the number of prefixes/NHs/VPNs. adam -----Original Message----- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Amarjeet Singh Sent: 19 January 2015 08:39 To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Juniper MX FIB hierarchy Hello - I believe it's like INDIRECT NEXT-HOP Prefix -->INDIRECT NH --> Actual NH COMPOSITE NH: used in case n/w has routers from vendors who don't have default controlled label allocation mechanism i.e cisco Prefix -->VPN LABEL --->INDIRECT NH --> Outer/Transport LABEL Br, Amarjeet > Message: 3 > Date: Sun, 18 Jan 2015 12:40:41 +0000 > From: Adam Vitkovsky <avitkov...@gammatelecom.com> > To: "juniper-nsp@puck.nether.net" <juniper-nsp@puck.nether.net> > Subject: [j-nsp] Juniper MX FIB hierarchy > Message-ID: > < > 627266b72b856946bcd625d4b34b1916a29...@inf-exch-mb-02.gammatelecom.com> > > Content-Type: text/plain; charset=UTF-8 > > Hi folks, > > I just came across an interesting info about Juniper's implementation of > hierarchical forwarding table i.e. indirect next hops. > But then I also found chained-composite next hops. > So now I'm not sure how are these two related. > I think the relation between them is: > prefix-->indirect next hop-->chained-composite next hop-->forwarding next > hop. > > Is my assumption correct please? > > Oh and also is anybody using indirect-next-hop-change-acknowledgements > please? > > Thanks > > 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 --------------------------------------------------------------------------------------- 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
