[j-nsp] Junos EVPN FIB structure?

[adamv0025 at netconsultings.com]

Hi folks,

Does anyone know why juniper decided to completely change the FIB structure
for EVPN Type 2 entries?
I mean what's wrong with the IP FIB entries format? 
Does anyone know what is the "chain" next-hop type please? - and no its not
chained composite next-hop those are marked as "comp"
The "chain" ID can't be even looked up with the request pfe execute target
fpc0 command "show nhdb id <ID> recursive"

L3VPN IP destination FIB structure: 
Each destination is referencing its own unique indr and ulist  Index IDs.
(the router unilist Index ID is what's pointing to forwarding NHs) 
Each unilist then lists a set of forwarding next-hops. 
- for each egress PE there's a unique Index ID for each of the forwarding
NHs (this is because of different label stack that needs to be applied to
get to each particular PE). 
(Route interface-index is always 0)
(if composite next hops are enabled then comp Index ID is at the top of the
hierarchy)

EVPN MAC destination FIB structure: 
Each destination is referencing its own unique chain Index ID. 
And then there's a list of per destination Route interface-indexes (lying
around at the bottom of the table like headless chickens). 
- the  route interface-index ID happens to match with the chain Index ID
-and that's how MAC destination is linked with its set of forwarding NHs. 
- and again for each egress PE there's a unique Index ID for each of the
forwarding NHs (this is because of different label stack that needs to be
applied to get to each particular PE).
(composite next-hop ingress enabled/disabled has no effect on the MAC
entries in the FIB)



Why I'm asking is because with CBTS:
IP destination FIB structure: 
Each destination is referencing its own unique indr and idxd  Index IDs.
(the indexed Index ID is what's pointing to unilist Index ID)
Each unilist then lists a set of forwarding next-hops. 
- for each egress PE there's a unique Index ID for each of the forwarding
NHs (this is because of different label stack that needs to be applied to
get to each particular PE).
(Route interface-index is always 0)
(if composite next hops are enabled then comp Index ID is at the top of the
hierarchy)

MAC destination FIB structure: 
Each destination is referencing its own unique chain Index ID. 
But the list of per destination Route interface-indexes disappears, and
forwarding ceases after a while


adam

netconsultings.com
::carrier-class solutions for the telecommunications industry::