MPLS

Unanswered Question
Sep 14th, 2009
User Badges:

I want to know the answers for the following failure scenario



1.FIB to LFIB Mismatch ( Aggregate entry has mismatched between FIB and LFIB table )


2.BGP to LFIB Mismatch ( Untagged entry has mismatched between BGP and LFIB )


3.LFIB and Ingress FIB inconsistency ( Egress LFIB and Ingress FIB inconsistency )


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
shivlu jain Mon, 09/14/2009 - 01:49
User Badges:
  • Silver, 250 points or more

1.FIB to LFIB Mismatch ( Aggregate entry has mismatched between FIB and LFIB table )

Answer:- RIB known as routing tables, FIBs are optimized for fast lookup of destination addresses. Earlier implementations cached only a subset of the routes most frequently used in actual forwarding, and this worked reasonably well for enterprises where there is a meaningful most-frequently-used subset. LFIB is the table which consists the information routes with label. During the table conersion if the label L1 should mapped with Dest D1 and instead of this it is D2. Then the problem of mismatch will occur.


2.BGP to LFIB Mismatch ( Untagged entry has mismatched between BGP and LFIB )

Ans:- Labels are in BGP but not in LFIB.


3.LFIB and Ingress FIB inconsistency

LFIB is having another label than FIB.


regards

shivlu jain



Actions

This Discussion