Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configure the Local Syslog to Track a Specific Pattern

Learn about how to configure the local syslog on a MX204, MX301, MX304, MX10004, or MX10008 router.

Use on-box syslog to track specific events for troubleshooting. The default messages file can become too verbose during incidents. Although match conditions provide basic filtering, configure additional syslog files for specific purposes.

Use these templates as a reference to create custom syslog files:

Common use cases:

  • Track control plane events
  • Track data plane errors

Control Plane Event Tracking

Track RPD (routing daemon) and BFD state‑change events (up and down). Filter physical and logical interface events, selected BGP events (such as session state changes and prefix‑limit violations), and LACP state changes. Modify the event list as needed.

Show or monitor all protocols events:

Data Plane Monitoring

The second syslog file tracks only hardware-related syslog matching the patterns: CMERROR, LUSS, MQSS and XQSS.

Note:
  1. CMERROR—Hardware error handler that manages errors at the FPC level.
  2. LUSS—Lookup engine within the Trio ASIC.
  3. MQSS—WAN and fabric processing block within the Trio ASIC.
  4. XQSS—Queuing (QoS) processing block within the Trio ASIC.

Show or monitor all Trio-related events: