Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

J-Insight Device Monitor Basic Configuration

 

Before you Begin

Note

If you’re running Junos OS Evolved software, you do not need to perform the procedures in this “Before you Begin” section.

J-Insight requires that your Junos OS device supports the Junos Telemetry Interface (JTI). For information about JTI, see the Junos Telemetry Interface User Guide. To use J-Insight, you must first complete the following steps:

  1. Install the Junos OS Release 18.2R1 or later Junos Network Agent software package. For information on how to install Junos Network Agent, see Installing the Network Agent Package (Junos Telemetry Interface).
  2. Use the show version | grep "na telemetry" command to verify that the Network Agent package was successfully installed.
    user@host> show version | grep "na telemetry"
  3. Install the Junos OS Release 18.2R1 or later OpenConfig for Junos OS software package. For information on how to install OpenConfig for Junos OS, see Installing the OpenConfig Package.
  4. Use the show version | grep "opencpnfig" command to verify that the OpenConfig package was successfully installed.
    user@host> show version | grep "opencpnfig"
  5. Use the show agent sensors command to verify whether or not J-Insight has successfully subscribed to sensors on which it is dependent.
    user@host> show agent sensors

J-Insight Health Monitoring

Starting with Junos OS Release 18.2R1, J-Insight supports health monitoring for FPC FRUs on the MX Series routers. The J-Insight health monitor is disabled by default.

  • To enable the J-Insight health monitor:

  • To disable the J-Insight health monitor:

  • To display the J-Insight health monitor results:

J-Insight Fault Monitoring

Starting with Junos OS Release 18.2R1, J-Insight supports fault monitoring for FPC FRUs on MX Series and PTX Series. Starting with Junos OS Evolved Release 19.1R1, J-Insight fault monitoring support is added for CB, chassis, fan, FPC, FPM, PDU, PIC, PSM, RE and SIB FRUs.

Chassis-level Configuration Commands

The Junos OS resiliency feature provides debugging capabilities in the case of device component failure. You can configure Packet Forwarding Engine (PFE)-related error levels on FRUs such as FPCs. Using the error configuration statement, you can set an automatic recovery action for each severity and configure the actions to perform when a specified threshold is reached.

For more information, see the Chassis-Level User Guide.

Trace Commands

  • (Junos OS only) To enable J-Insight trace options for debugging:

  • (Junos OS Evolved only) You can view collected J-Insight traces with the show trace application jinsightd command, and remove inactive J-Insight tracing sessions with the clear trace application jinsightd command.

Clear & Show Commands

  • To clear all system errors or a specific error denoted by the error ID Uniform Resource Identifier (URI) for a specific FPC:

  • To display information on alarms that have been triggered by faults:

  • To display summary or detailed information about the active errors based on FRU, error scope, or error category:

  • To display a summary of the number of detected errors and recovery actions taken based on severity level:

  • To display information about a detected error based on its error ID URI:

  • To display detailed information about the detected errors based on the FRU: