Logs are the best method to use for generating alerts when the system transitions from a stable steady state. In Cumulus Linux, rsyslog handles all logging, including local and remote logging. Triggered issues are normally sent to syslog, but can go to another log file depending on the feature. Metrics are more valuable when used for trend analysis. Examples of metrics include bytes on an interface, CPU utilization, and total number of routes. Critical log messages that you can monitor for triggered alertsĪ metric is a quantifiable measure that is used to track and assess the status of a specific infrastructure component.Metrics that you can poll from Cumulus Linux and use in trend analysis.In addition, several of the more common issues have been listed, with potential solutions included. The following monitoring processes are considered best practices for reviewing and troubleshooting potential issues with Cumulus Linux environments. If you are redirected to the main page of the user guide, then this page may have been renamed please search for it there. The current version of the documentation is available

If you are using the current version of Cumulus Linux, the content on this page may not be up to date. Resource Diagnostics Using cl-resource-query.Using Nutanix Prism as a Monitoring Tool.Simple Network Management Protocol - SNMP.Monitoring System Statistics and Network Traffic with sFlow.Using NCLU to Troubleshoot Your Network Configuration.Monitoring Interfaces and Transceivers Using ethtool.Understanding the cl-support Output File.Network Switch Port LED and Status LED Guidelines.Unequal Cost Multipath with BGP Link Bandwidth.

Equal Cost Multipath Load Sharing - Hardware ECMP.

Bidirectional Forwarding Detection - BFD.

Hybrid Cloud Connectivity with QinQ and VXLANs.

Ethernet Virtual Private Network - EVPN.

Virtual Router Redundancy - VRR and VRRP.

Default Cumulus Linux ACL Configuration.

Authentication, Authorization and Accounting.

Check resource usage linux