Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configure Local Accounting as a Fallback Solution

Learn how to configure the Local Accounting on a MX204, MX301, MX304, MX10004, or MX10008 router.

Use on-box accounting as a fallback to collect key statistics when external monitoring systems are unavailable. Although protocols such as gRPC and gNMI provide reliable telemetry, local data collection supports post‑event analysis when management connectivity is lost.

Use the following example templates to capture local statistics:

  • Routing Engine KPIs
  • Interface statistics (primarily error counters)

Routing Engine Profile

Configure a routing‑engine accounting profile to store periodic statistics locally. First, define a local file, then specify the fields to collect in CSV format.

The following example saves key counters from the master Routing Engine at 1‑minute intervals:

Interface Profile

To enable local statistics collection for each interface, apply the following configuration:

Enable accounting on each physical interface where you need to collect statistics. Configure this feature only on critical paths to limit resource usage.

Use local interface accounting as a fallback when external data collection is unavailable during an outage.

For each interface, enable local statistics collection as shown below:

Display the statistics by viewing the local file contents. For example, use the file generated by the interface accounting profile:

Use a dedicated CLI command to provide filtering capabilities: