J-Insight Device Monitor Basic Configuration
Before you Begin
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. To use J-Insight, you must first complete the following steps:
Use the
show agent sensorscommand to verify whether or not J-Insight has successfully subscribed to sensors on which it is dependent.user@host> show agent sensors . . . Sensor Information : Name : sensor_1000 Resource : /junos/events/event[id='CHASSISD_SNMP_TRAP7']/ Version : 1.0 Sensor-id : 539528115 Subscription-ID : 1000 Parent-Sensor-Name : Not applicable Component(s) : eventd Profile Information : Name : export_1000 Reporting-interval : 0 Payload-size : 5000 Format : GPB Sensor Information : Name : sensor_1001 Resource : /junos/system/cmerror/configuration/ Version : 1.0 Sensor-id : 539528114 Subscription-ID : 1001 Parent-Sensor-Name : Not applicable Component(s) : PFE Profile Information : Name : export_1001 Reporting-interval : 6 Payload-size : 5000 Format : GPB Sensor Information : Name : sensor_1002 Resource : /junos/system/cmerror/counters/ Version : 1.0 Sensor-id : 539528113 Subscription-ID : 1002 Parent-Sensor-Name : Not applicable Component(s) : PFE Profile Information : Name : export_1002 Reporting-interval : 6 Payload-size : 5000 Format : GPB Sensor Information : Name : sensor_1003 Resource : /components/ Version : 1.0 Sensor-id : 539528112 Subscription-ID : 1003 Parent-Sensor-Name : Not applicable Component(s) : chassisd Profile Information : Name : export_1003 Reporting-interval : 6 Payload-size : 5000 Format : GPB Sensor Information : Name : sensor_1004 Resource : /junos/services/health-monitor/config/ Version : 1.0 Sensor-id : 539528119 Subscription-ID : 1004 Parent-Sensor-Name : Not applicable Component(s) : PFE Profile Information : Name : export_1004 Reporting-interval : 7 Payload-size : 5000 Format : GPB Sensor Information : Name : sensor_1005 Resource : /junos/services/health-monitor/data/ Version : 1.0 Sensor-id : 539528118 Subscription-ID : 1005 Parent-Sensor-Name : Not applicable Component(s) : PFE Profile Information : Name : export_1005 Reporting-interval : 7 Payload-size : 5000 Format : GPB
J-Insight Health Monitoring
To enable the J-Insight health monitor:
user@host# set services jinsightd subscribe health-monitor
To disable the J-Insight health monitor:
user@host# delete services jinsightd subscribe health-monitor
To display the J-Insight health monitor results:
user@host> show system health-monitor [fpc fpc-slot slot-number]
J-Insight Fault Monitoring
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:
user@host# set services jinsightd traceoptions flag trace-option
(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:
user@host> clear chassis fpc errors fpc-slot slot-number [ all | error-id error-id- uri]
To display information on alarms that have been triggered by faults:
user@host> show chassis alarms
To display summary or detailed information about the active errors based on FRU, error scope, or error category:
user@host> show system errors active [[fru slot-number] | [detail [fru slot-number [scope error-scope ] [category error-category ]]]
To display a summary of the number of detected errors and recovery actions taken based on severity level:
user@host> show system errors count
To display information about a detected error based on its error ID URI:
user@host> show system errors error-id error-id-uri
To display detailed information about the detected errors based on the FRU:
user@host> show system errors fru detail [fru slot-number]