Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

resiliency

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
resiliency {
   exceptions {
      forwarding;
      os;
      routing;
   }
   store {
      database;
      file name {
         files number;
         (no-world-readable | world-readable);
         size size;
      }
      fwding-file name{
         files number;
         (no-world-readable | world-readable);
         size size;
      }
   }
   traceoptions {
      file name {
         files number;
         match;
         (no-world-readable | world-readable);
         size size;
      }
      flag flag;
      no-remote-trace;
   }
}

Hierarchy Level

content_copy zoom_out_map
[edit system]

Description

Configure the Juniper Resiliency Interface (JRI) on-box collector to detect exceptions from multiple modules and collect those exceptions in a file or a database. If you want to store exceptions data in a file, you need to configure a filename for the file and the size for the file.

Default

The on-box collector is disabled.

Options

The statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.

Additional information

To fully configure JRI for forwarding exceptions, you must also:

  • Configure inline-monitoring services as you normally would, and configure the Juniper-specific IEs with the primary-data-record-fields statement at the [edit services inline-monitoring templates template-name] hierarchy level.
  • Configure the Observation Cloud identifier with the observation-cloud-id statement at the [edit services inline-monitoring] hierarchy level.
  • Configure exception reporting for a particular inline-monitoring instance with the exception-reporting statement at the [edit chassis fpc name pfe name] hierarchy level.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 21.2R1 for MX Series routers.

Statement introduced in Junos Evolved OS Release 22.2R1 for PTX Series routers.

footer-navigation