Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Error TPAs for Route Installation

If you configure this feature, during route installations the consumer of a state update notifies the producing application when there are errors in processing the state update sent by the producer. The producer then attaches a third-party attachment (TPA) object on top of the errored object, with details of the error, and publishes it.

Overview of Error Third-Party Attachments (TPAs) on Errored Objects During Route Installations

In a distributed system, states can be produced anywhere and consumed anywhere, making it difficult for a producer (for example, a PFE) to determine whether the system is in the correct state for the consumer (for example, an rpdagent). If you configure this feature, during route installations the consumer notifies the producing application when there are errors in processing the state update sent by the producer. The producer then attaches a TPA object on top of the errored object with details of the error and publishes it.

Details of errors include:

  • errorID

  • severity

  • obj_guid

  • error_description

  • error_module

  • error_object_name

  • error_timestamp

  • error_producer_name

  • natural_name

The errors generated have standard error numbers.

The forwarding information base (FIB) telemetry daemon (FIBtd) also receives error notifications. You use the Junos telemetry interface (JTI) and remote procedure calls (gRPC) services to stream or export ON_CHANGE FIB statistics to an outside SDN collector. Set the collector to subscribe to xpath /state/system/anomalies/fib/ to get both the IPv4 and IPv6 error routes.

You can use the CLI to query errored objects and related information. To avoid flooding the system with error objects, the number of published error objects from a producer is set to a threshold limit of 20,000. Once the threshold is reached, no more error objects are published. However, errored objects and related information is still saved, you can query it using CLI

The consumer is notified when the errors are cleared and the route installation is successful.

Set Up the System for Error TPAs

  1. Configure FIP streaming on the client device.
  2. On the collector, subscribe to the xpath /state/system/anomalies/fib/ to get both the IPv4 and IPv6 error routes.

CLI Commands for Viewing Error Details

Use the following CLI commands to view details of error TPAs that are generated during route installations:

Table 1: CLI Commands to View Error TPA Information
Command Example Link
show system applications show system applications error app rpdagent node re0 show system applications (Junos OS Evolved)

show fib-streaming

show fib-streaming native-model route-errors inet

 show fib-streaming
show agent sensors – show agent sensors