This article outlines the procedural steps necessary to accurately pinpoint the specific route table that corresponds to Rt-index.
In certain scenarios, delays in writing route changes (additions/deletions) to the forwarding database may occur, typically due to extensive route modifications. The following logs may be observed:
ppcfpc-multi-svcs.elf: FDB :: Ipv4 route operation 2 failed. Rt_index 1801, As_index 620360, gateway 1747774317
To troubleshoot and pinpoint the specific instance or table responsible for these route changes, thereby isolating the problematic instance, it is necessary to identify the relevant route table. This can be achieved from the FPC shell.
labroot@Device-re0> start shell pfe network fpc1
Routing platform (1600 Mhz QorIQ P5020 processor, 3072MB memory, 8192KB flash)
FPC1(Device-re0 vty)# show route table
Protocol: IPv4
Table Name Table Index (lrid ) # of Routes Bytes LOCAL FRRP TID
-------------------------------------------------------------------------------------------------------
ITEpremium.1799 1799 (0 ) 5 876 LOCAL low ----
ITEvrf.1800 1800 (0 ) 55 9676 LOCAL low ----
__juniper_private1__.1 1 (0 ) 11 1932 LOCAL low ----
__juniper_private2__.2 2 (0 ) 8 1404 LOCAL low ----
__juniper_private3__.36735 36735 (0 ) 5 876 LOCAL low ----
__juniper_private4__.36736 36736 (0 ) 5 876 LOCAL low ----
__juniper_private5__.36737 36737 (0 ) 5 876 LOCAL low ----
__juniper_services__.1795 1795 (0 ) 9 1580 LOCAL low ----
__master.anon__.1797 1797 (0 ) 5 876 LOCAL low ----
__pfe_private__.1803 1803 (0 ) 5 876 LOCAL low ----
__srm6__.1798 1798 (0 ) 5 876 LOCAL low ----
default.0 0 (0 ) 4000665 704117036 LOCAL low ----
XYZ-vrf.1801 1801 (0 ) 5 876 LOCAL low ---- >>>>>>>>>>>>>>>>>>