counter-profiles
Syntax
custom-profiles {
counter-profiles <counter-profile-name> {
app {
<app-name> {
counter-4k <num-of-counter-engines>
counter-8k <num-of-counter-engines>
counter-16k <num-of-counter-engines>
}
}
}
Hierarchy Level
[edit system packet-forwarding-options]
Description
The custom profile infrastructure allows you to create and manage custom profiles for hardware resources such as counters. It provides a controlled and flexible mechanism for reserving and managing hardware resources, allowing you to specify application-specific counter usage and which applications are permitted to reserve hardware resources, thereby improving scalability and resource efficiency.
The custom profile infrastructure enables you to create hardware-resource specific templates such as custom profiles for counter resources. You can group custom counter profiles to create a custom hardware profile. You can create multiple custom hardware profiles, and choose one custom hardware profile as the active hardware profile.
Options
-
counter-profiles counter-profile-name—Specify the name of the counter profile
-
app app-name—In a counter profile, specify the application name that will utilize the counter resources. The following applications are supported:
Table 1: Supported applications that utilize custom profiles Application Name
Description
storm-control
Storm control support
voq
HQoS statistics
tcam-ingress
TCAM related statistics support for ingress direction - used by firewall filters
perf-mon-ingress
Twamp, inline sFlow functionality related support for ingress direction
ifl-ingress
IFL statistics support for ingress direction
policer-ingress
Policer support for ingress direction
tcam-egress
TCAM related statistics support for egress direction - used by firewall filters
perf-mon-egress
Inline Sflow functionality related support
ifl-egress
IFL statistics support for egress direction
policer-egress
TCAM policer support for egress direction
multicast
Multicast route statistics support
-
counter-4k/counter-8k/counter-16k counter-engines—Specify the number of counter engines to assign for each counter resource. In the system, counter resources are provided through various counter engines. There are three types of counter engines based on the number of counters they support. 4k counter engines support 4K counters. Similarly, 8K and 16K counter engines support 8K and 16K counters. Counter engines are also used by policers. Number of counter engines vary depending on platform. Hence applications using policers should reserve counter engines accordingly. Default counter profile will remain the same as the one currently statically allocated on each platform. Some counter engines will be reserved for internal use. Hence number of available counter engines for the user to configure will be as below:
Table 2: Platform Support for Counter Engines Platform
4K Counter engines
8K Counter Engines
16K Counter Engines
ACX7100-48L
6
6
5
ACX7100-32C
6
6
5
ACX7024
3
4
4
ACX7024X
3
4
4
ACX7020
3
4
4
ACX7509
8
7
16
ACX7348
7
8
16
ACX7332
7
8
16
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Evolved Release 25.3R1 on ACX7100-32C, ACX7100-48L,ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X