Datapath resource monitoring

On 7215 IXS, 7220 IXR, 7250 IXR, and 7730 SXR devices, SR Linux exposes utilization information about the following datapath resources, which are limited in number and potentially can be exhausted:

  • ACL-related resources

  • TCAM-related resources

  • MTU-related resources (only applicable to 7250 IXR devices)

  • QoS profile-related resources

  • Buffer memory

  • XDP forwarding-related resources

  • ASIC-specific forwarding-related resources

For each of these resources, you can specify a rising-threshold-log value (in percentage, 0 to 100) and a falling-threshold-log value (in percentage, 0 to 100). These values apply system-wide.

The falling-threshold-log value sets the threshold that triggers the generation of a log message of warning severity whenever the utilization of the datapath resource in any linecard (if applicable), forwarding-complex, or pipeline (if applicable) reaches this value in a rising direction. The log message captures the following information:

  • Linecard slot number (if applicable)
  • Forwarding-complex name, for example “0”
  • Pipeline number (if applicable)
  • Resource name, for example ip-lpm-routes

The falling-threshold-log value sets the threshold that triggers the generation of a log message of notice severity whenever the utilization of the datapath resource reaches this value in a falling direction. This log message captures the same information as the rising-threshold-log message.

Configuring thresholds for datapath resources

To configure monitoring for datapath resources, use the platform resource-monitoring command to set values for the rising-threshold-log and falling-threshold-log parameters for the resource you want to monitor.

Set thresholds for resource usage by input IPv4 filter instances

The following example sets thresholds for resource usage by input IPv4 filter instances. If the resource usage percentage falls below the falling-threshold-log value, a log message of severity notice is generated. If the resource usage percentage falls below the rising-threshold-log value, a log message of severity warning is generated.

--{ * candidate shared default }--[  ]--
# info with-context platform resource-monitoring
    platform {
        resource-monitoring {
            acl {
                resource input-ipv4-filter-instances {
                    rising-threshold-log 90
                    falling-threshold-log 75
                }
            }
        }
    }

Set thresholds for TCAM resource usage by IPv4 CPM filters

The following example sets thresholds for TCAM resource usage by IPv4 CPM filters. If the resource usage percentage falls below the falling-threshold-log value, a log message of severity notice is generated. If the resource usage percentage falls below the rising-threshold-log value, a log message of severity warning is generated.

--{ * candidate shared default }--[  ]--
# info with-context platform resource-monitoring
    platform {
        resource-monitoring {
            tcam {
                resource cpm-capture-ipv4 {
                    rising-threshold-log 90
                    falling-threshold-log 75
                }
            }
        }
    }