[j-nsp] Juniper MX FIB hierarchy

[Amarjeet Singh]

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 <avitkovsky at gammatelecom.com>
> To: "juniper-nsp at puck.nether.net" <juniper-nsp at puck.nether.net>
> Subject: [j-nsp] Juniper MX FIB hierarchy
> Message-ID:
>         <
> 627266B72B856946BCD625D4B34B1916A2961A at 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
>
> ---------------------------------------------------------------------------------------
>
>
>
>
>