NPU and Resource Utilization Sensor Properties
NPU and resource utilization sensors provide visibility into the internal operations of Juniper devices and the state of resource consumption on each device. You can use this information to improve network design and to optimize traffic engineering. This data can also be used for early detection of problems in individual devices as well as in the overall network and the traffic carried by it.
NPU Utilization for PTX10000 and QFX1000 Series
The following section contains NPU utilization information for PTX10000 and QFX10000 series.
Native Sensor Property Name |
gRPC Sensor Property Name |
Unit Type |
Range |
Description |
---|---|---|---|---|
NPU Utilization |
NPU Utilization |
32-bit |
1-100 |
Number on a scale of 0-100 that indicates the busyness of an NPU. |
Memory load
|
Memory load
|
— |
— |
Load on a memory subsystem of the NPU |
Memory load |
Memory load |
— |
— |
Load on a memory subsystem of the NPU |
Memory load
|
Memory load
|
string |
— |
A name string to identify the particular memory subsystems (such as hmc) |
Memory load
|
Memory load
|
32-bit |
— |
Various memory utilization metrics |
Memory load
|
Memory load
|
— |
Each memory is front ended by a cache. The following metrics indicate how these caches are working |
|
Packet Load |
Packet Load |
— |
— |
Offered packet load on an internal subsystem of the NPU, like the following:
|
Packet Load:
|
Packet Load:
|
string |
— |
Each internal subsystem of the NPU has a name |
Packet Load:
|
Packet Load:
|
64-bit |
— |
Rate of packets received |
Packet Load:
|
Packet Load:
|
32-bit |
— |
Indicate the compute load on the NPU. These metrics are not valid for the PF chip on the PTX10000 routers or QFX10000 switches. |
Native Sensor Property Name |
gRPC Sensor Property Name |
Unit Type |
Range |
Description |
---|---|---|---|---|
Memory Summary |
Memory Summary |
— |
— |
NPU memory utilization summary per memory type |
Memory Summary
|
Memory Summary
|
— |
string |
A name string to identify the particular memory blocks such as KHT (cuckoo hash tables), edf, flt, sfm, fcv. Beta-0, beta-1, policer, and pclt |
Memory Summary:
|
Memory Summary:
|
64-bit |
% |
Size memory utilization metrics |
Memory Summary:
|
Memory Summary:
|
64-bit |
% |
Allocated memory utilization metrics |
Memory Summary:
|
Memory Summary:
|
32-bit |
% |
Memory utilization metrics |
Application memory partition summary |
— |
— |
Detailed statistics for NPU memory partitions per application; examples include plct-filter, plct-ingr-nh, plct-egr-nh, plct-rt, and plct-misc. |
|
Application memory partition summary:
|
Application memory partition summary
|
string |
— |
Name of the application for which NPU memory is allocated. |
Application memory partition summary:
|
Application memory partition summary:
|
32-bit |
— |
Various memory values for allocation and free count. |
NPU Utilization for PTX Series
The following Section contains NPU utilization sensor information PTX series routers.
Native Sensor Property Name |
gRPC Sensor Property Name |
Unit Type |
Range |
Description |
---|---|---|---|---|
NPU Memory
|
Exported property names:
|
— |
32768 (size in your table) |
An equivalent of a logical interface index. Logical interfaces is a contributor. |
NPU Memory
|
Exported property names:
|
entry |
3072 |
Used for both VRRP MAC and MYMAC indentification. Populated during FPC intitialization |
NPU Memory
|
Exported property names:
|
entry |
16777216 |
Used by L3 / L2 forwarding table entries, including IPv4, IPv6, MPLS. Only route entries are located in this database. Entries size vary and depends on the entry type. |
NPU Memory
|
Exported property names:
|
entry |
4194304 |
Used by flow table. Populated only when IPFIX is enabled. |
Firewall / Filter
|
Exported property names: not available |
entry |
8192 |
Reflects the number of filter instances (and not the number of configured filters) Regular filters, interface-specific filter creates a new instance, there is no program sharing |
Firewall / Filter
|
Exported property names:
|
— |
65536 |
Reflects the number of filter terms. Regular filters, interface-specific filter creates a new instance. There is no program sharing |
Firewall / Filter
|
Exported property names:
|
— |
131072 |
Used for longest prefix matches (source, destination addresses). Contributors are source or destination prefix lists. IPv6 prefixes with matches longer than /64 occupy two entries. |
Firewall / Filter
|
Exported property names:
|
— |
131072 |
Used for longest prefix matches (source, destination addresses). Contributors are source or destination prefix lists. |
Firewall / Filter
|
Exported property names:
|
— |
65536 |
Used for range matches (source and destination ports). Contributors are ports, port ranges, and other match conditions. This is a tree structure. Each match condition may translate into 1 or more entries, depending on the number of ranges. |
Firewall / Filter
|
Exported property names:
|
— |
65536 |
Used for range matches (source and destination ports). Contributors are ports, port ranges, and other match conditions. This is a tree structure. Each match condition may translate into 1 or more entries, depending on the number of ranges. |
Firewall / Filter
|
Exported property names:
|
— |
8192 |
Used by other match conditions, such as tcp-flags. |
Firewall / Filter
|
Exported property names:
|
— |
256 rows 4 pages each |
An auxiliary data structure used to optimize for direction indifference matches (source or destination addresses ports), excepts and ranges (plus wildcards). Contributors are filters with irregular patterns (direction indifference matches, excepts, ranges, wildcards) will contribute to the utilization. |
Firewall / Filter
|
Exported property names:
|
B |
65536 |
Cover vector FCV block 1. |
Firewall / Filter
|
Exported property names:
|
B |
65536 |
Cover vector FCV block 2. |
Firewall / Filter
|
Exported property names:
|
B |
65536 |
Special cover vector FCV block 3. |
NPU Memory
|
Exported property names:
|
entry |
16777216 |
Used by L3 / L2 forwarding table entries, including IPv4, IPv6, MPLS. Only route entries are located in this database. Entries size vary and depends on the entry type. |
NPU Memory
|
Exported property names:
|
entry |
4194304 |
Used by flow table. Populated only when IPFIX is enabled. |
NPU Memory
|
Exported property names:
|
entry |
16777216 |
Used by L3 / L2 forwarding table entries, including IPv4, IPv6, MPLS. Only route entries are located in this database. Entries size vary and depends on the entry type. |
NPU Memory
|
Exported property names:
|
entry |
4194304 |
Used by flow table. Populated only when IPFIX is enabled. |
Firewall / Filter
|
Exported property names:
|
B |
16384 |
Contributors are firewall policers, and interface policers |
Firewall / Filter
|
Exported property names:
|
B |
131072 |
Issues 1 word per counter, 3 words per single rate policer, and 5 words for tricolor policers. |
Next-hops and encapsulation
|
Exported property names:
|
KWords |
128 |
Load-balancing data structures. Contributors are aggregated Ethernet and multipath. |
Next-hops and encapsulation
|
Exported property names:
|
KWords |
256 |
Used for next-hops. Contributors are next-hops. |
Next-hops and encapsulation
|
Exported property names:
|
KWords |
320 |
Encapsulation data structures. Contributors are forwarding next-hops. |
Next-hops and encapsulation
|
Exported property names:
|
KWords |
128 |
MPLS Label structures. Contributors are MPLS Labels. |
Native Sensor Property Name |
gRPC Sensor Property Name |
Unit Type |
Range |
Description |
---|---|---|---|---|
NPU Utilization
|
Exported property names:
|
percent |
— |
Current PE chip utilization. Contributor is traffic stream. |
NPU Utilization
|
Exported property names:
|
pps |
— |
Traffic load on the chip which includes loopback, recirculated, WAN, and host-injected and ASIC-to-host traffic. Contributors are traffic stream pps. |
NPU Utilization
|
Exported property names:
|
percent/per-sec |
— |
HMC memory utilization and memory cache hit rate |
Firewall Resource Utilization
You can export statistics on firewall resource utilization by subscribing to the OpenConfig
resource path /components/component/integrated-circuit/pipeline-counters/
.
The operational state sensors display the total supported filter entries and used entries in
terms of count and bytes.
State sensors for firewall resource utilization are:
-
/components/component/integrated-circuit/pipeline-counters/packet/lookup-block/state/acl-memory-used-entries
-
/components/component/integrated-circuit/pipeline-counters/packet/lookup-block/state/acl-memory-total-entries
-
/components/component/integrated-circuit/pipeline-counters/packet/lookup-block/state/acl-memory-used-bytes
-
/components/component/integrated-circuit/pipeline-counters/packet/lookup-block/state/acl-memory-total-bytes
The values of the sensors use the following calculations:
- acl-memory-used-entries = round ( UtilizationOfTables [a number from 0
to 100] / 100 * 64000)
The value of UtilizationOfTables is the maximum value of the following NPU memory statistics, which are leaves under the native sensor
/junos/system/linecard/npu/memory/
:mem-util-flt-vfilter-utilization
mem-util-flt-phyfilter-utilization
mem-util-flt-action-entries-utilization
mem-util-fcv-blk-1-utilization
mem-util-fcv-blk-2-utilization
mem-util-fcv-blk-3-utilization
mem-util-flt-scv-utilization
mem-util-beta-0-bank-0-utilization
mem-util-beta-0-bank-1-utilization
mem-util-beta-0-bank-2-utilization
mem-util-beta-0-bank-3-utilization
mem-util-beta-0-bank-4-utilization
mem-util-beta-1-bank-1-utilization
mem-util-beta-1-bank-2-utilization
mem-util-beta-1-bank-3-utilization
mem-util-beta-1-bank-4-utilization
mem-util-beta-1-bank-5-utilization
mem-util-flt-alpha-1-kht-utilization
mem-util-flt-alpha-1-plt-utilization
mem-util-policer-id-utilization
mem-util-plct-utilization
-
acl-memory-total-entries = 64K
-
acl-memory-used-bytes = acl-memory-used-entries * 8
-
acl-memory-total-bytes = acl-memory-total-entries * 8 = 64k *8