Logs fpc0 ppcfpc-multi-svcs.elf: FDB :: Ipv4 route operation 2 failed. Rt_index 1799, As_index #####, gateway 0

-PTX devices.
-Ipv4 route operation 2 failed. Rt_index 1799, As_index ##, gateway 0 logs.

Rt_index seems to be Route table Index.

FBD: Forwarding database.

• Search for the RT index in the RSI:

 Logical interface .local..1799 (Index 76) (SNMP ifIndex 0) (HW Token 11) (Generation 128)

  Flags: Point-To-Point Encapsulation: Unspecified

  Bandwidth: 0

  Protocol inet, MTU: Unlimited

  Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0

  Generation: 175, Route table: 1799

   Flags: None

   Addresses, Flags: Is-Primary

    Destination: Unspecified, Local: 1.1.1.1, Broadcast: Unspecified, Generation: 155

  Protocol iso, MTU: Unlimited, Generation: 177, Route table: 1799

• Find to what interface that IP belongs:

  lo0 {

    unit 100 {

      family inet {

        address 1.1.1.1/32;

      }

• The lo0.100 was assigned to a routing-instance running BGP:

routing-instances {

  Internet {

  protocols {

      bgp {

    group MonitorBGP {

          type internal;

          log-updown;

          neighbor 1.1.1.1 {

            family inet {

              unicast;

            }

            export monitorbgp_out;

          }

        }

      }

    }

• The peer was in Active state:

Peer           AS   InPkt   OutPkt  OutQ  Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...

1.1.1.1     7167     0     0    0    0 1w1d 4:12:38 Active

• For this case the neighbor was for testing; so, the logs were cosmetic and could be ignored or filtered using the example on KB9382 - How to prevent certain syslog messages from being written to the log file [juniper.net]

2024-02-06 : Article Created

2024-10-17 : dconejomora - Changing KB Visible To value for "Internal, Partner and Customer"