Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

NPU Utilization Properties

The following sections contain NPU utilization and memory sensor information.

NPU Utilization for PTX10000 and QFX1000 Series

The following section contains NPU utilization information for PTX10000 and QFX10000 series.

Table 1: NPU Utilization sensor (resource path /junos/system/linecard/npu/utilization/)

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

  • Name

Memory load

  • Name

Load on a memory subsystem of the NPU

Memory load

Memory load

Load on a memory subsystem of the NPU

Memory load

  • Name

Memory load

  • Name

string

A name string to identify the particular memory subsystems (such as hmc)

Memory load

  • Average_util

  • Highest_util

  • Lowest_util

Memory load

  • Average_util

  • Highest_util

  • Lowest_util

32-bit

Various memory utilization metrics

Memory load

  • Average_cache_hit_rate

  • Highest_cache_hit_rate

  • Lowest_cache_hit_rate

Memory load

  • Average_cache_hit_rate

  • Highest_cache_hit_rate

  • Lowest_cache_hit_rate

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:

  • loopback_pps

  • recirculation_pps

  • wan_and_host_inject_pps

  • asic_to_host_pps

Packet Load:

  • Identifier

Packet Load:

  • Identifier

string

Each internal subsystem of the NPU has a name

Packet Load:

  • rate

Packet Load:

  • rate

64-bit

Rate of packets received

Packet Load:

  • average_instructions_per_packet

  • average_wait_cycles_per_packet

  • average_cycles_per_packet

Packet Load:

  • average_instructions_per_packet

  • average_wait_cycles_per_packet

  • average_cycles_per_packet

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.

Table 2: NPU memory sensor (resource path /junos/system/linecard/npu/memory/)

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

  • Resource_name

Memory Summary

  • Resource_name

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:

  • size

Memory Summary:

  • size

64-bit

%

Size memory utilization metrics

Memory Summary:

  • allocated

Memory Summary:

  • allocated

64-bit

%

Allocated memory utilization metrics

Memory Summary:

  • utilization

Memory Summary:

  • utilization

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_name

Application memory partition summary

  • Application_name

string

Name of the application for which NPU memory is allocated.

Application memory partition summary:

  • Bytes_allocated

  • Allocation_count

  • Free_count

Application memory partition summary:

  • Bytes_allocated

  • Allocation_count

  • Free_count

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.

Table 3: NPU memory sensor (resource path /junos/system/linecard/npu/memory/)

Native Sensor Property Name

gRPC Sensor Property Name

Unit Type

Range

Description

NPU Memory

  • L2 domain

Exported property names:

  • mem-util-kht-l2domain-allocated

  • mem-util-kht-l2domain-size

  • mem-util-kht-l2domain-utilization

32768 (size in your table)

An equivalent of a logical interface index. Logical interfaces is a contributor.

NPU Memory

  • SLU MY-MAC

Exported property names:

  • mem-util-kht-slu-my-mac-size

  • mem-util-kht-slu-my-mac-allocated

  • mem-util-kht-slu-my-mac-utilization

entry

3072

Used for both VRRP MAC and MYMAC indentification. Populated during FPC intitialization

NPU Memory

  • Forwarding table: edb0

Exported property names:

  • mem-util-kht-dlu-edb0-allocated

  • mem-util-kht-dlu-edb0-size

  • mem-util-kht-dlu-edb0-utilization

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

  • Forwarding table: edb1

Exported property names:

  • mem-util-kht-dlu-edb1-allocated

  • mem-util-kht-dlu-edb1-size

  • mem-util-kht-dlu-edb1-utilization

entry

4194304

Used by flow table. Populated only when IPFIX is enabled.

Firewall / Filter

  • Filter instances

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

  • Filter terms

Exported property names:

  • mem-util-flt-action-entries-utilization

  • mem-util-flt-action-entries-allocated

  • mem-util-flt-action-entries-size

65536

Reflects the number of filter terms. Regular filters, interface-specific filter creates a new instance. There is no program sharing

Firewall / Filter

  • Filter alpha block [0]

Exported property names:

  • mem-util-kht-flt0-size

  • mem-util-kht-flt0-allocated

  • mem-util-kht-flt0-utilization

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

  • Filter alpha block [1]

Exported property names:

  • mem-util-kht-flt1-size

  • mem-util-kht-flt1-allocated

  • mem-util-kht-flt1-utilization

  • mem-util-flt-alpha-1-kht-size

  • mem-util-flt-alpha-1-kht-allocated

  • mem-util-flt-alpha-1-kht-utilization

  • mem-util-flt-alpha-1-bft-0-size

  • mem-util-flt-alpha-1-bft-0-allocated

  • mem-util-flt-alpha-1-bft-0-utilization

  • mem-util-flt-alpha-1-plt-size

  • mem-util-flt-alpha-1-plt-allocated

  • mem-util-flt-alpha-1-plt-utilization

131072

Used for longest prefix matches (source, destination addresses). Contributors are source or destination prefix lists.

Firewall / Filter

  • Filter beta block [0]

Exported property names:

  • mem-util-beta-0-bank-0-size

  • mem-util-beta-0-bank-0-allocated

  • mem-util-beta-0-bank-0-utilization

  • mem-util-beta-0-bank-1-size

  • mem-util-beta-0-bank-1-allocated

  • mem-util-beta-0-bank-1-utilization

  • mem-util-beta-0-bank-2-size

  • mem-util-beta-0-bank-2-allocated

  • mem-util-beta-0-bank-2-utilization

  • mem-util-beta-0-bank-3-size

  • mem-util-beta-0-bank-3-allocated

  • mem-util-beta-0-bank-3-utilization

  • mem-util-beta-0-bank-4-size

  • mem-util-beta-0-bank-4-allocated

  • mem-util-beta-0-bank-4-utilization

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

  • Filter beta block [1]

Exported property names:

  • mem-util-beta-1-bank-0-size

  • mem-util-beta-1-bank-0-allocated

  • mem-util-beta-1-bank-0-utilization

  • mem-util-beta-1-bank-1-size

  • mem-util-beta-1-bank-1-allocated

  • mem-util-beta-1-bank-1-utilization

  • mem-util-beta-1-bank-2-size

  • mem-util-beta-1-bank-2-allocated

  • mem-util-beta-1-bank-2-utilization

  • mem-util-beta-1-bank-3-size

  • mem-util-beta-1-bank-3-allocated

  • mem-util-beta-1-bank-3-utilization

  • mem-util-beta-1-bank-4-size

  • mem-util-beta-1-bank-4-allocated

  • mem-util-beta-1-bank-4-utilization

  • mem-util-flt-beta-1-bank-5-size

  • mem-util-flt-beta-1-bank-5-allocated

  • mem-util-flt-beta-1-bank-5-utilization

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

  • Secondary Facet Match

Exported property names:

  • mem-util-sfm-entries-size

  • mem-util-sfm-entries-allocated

  • mem-util-sfm-entries-utilization

8192

Used by other match conditions, such as tcp-flags.

Firewall / Filter

  • Special Cover Vector

Exported property names:

  • mem-util-flt-scv-size

  • mem-util-flt-scv-allocated

  • mem-util-flt-scv-utilization

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

  • FCV block [1]

Exported property names:

  • mem-util-fcv-blk-1-size

  • mem-util-fcv-blk-1-allocated

  • mem-util-fcv-blk-1-utilization

B

65536

Cover vector FCV block 1.

Firewall / Filter

  • FCV block [2]

Exported property names:

  • mem-util-fcv-blk-2-size

  • mem-util-fcv-blk-21allocated

  • mem-util-fcv-blk-2-utilization

B

65536

Cover vector FCV block 2.

Firewall / Filter

  • FCV block [3]

Exported property names:

  • mem-util-fcv-blk-3-size

  • mem-util-fcv-blk-3-allocated

  • mem-util-fcv-blk-3-utilization

B

65536

Special cover vector FCV block 3.

NPU Memory

  • Forwarding table: edb0

Exported property names:

  • mem-util-kht-dlu-edb0-allocated

  • mem-util-kht-dlu-edb0-size

  • mem-util-kht-dlu-edb0-utilization

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

  • Forwarding table: edb1

Exported property names:

  • mem-util-kht-dlu-edb1-allocated

  • mem-util-kht-dlu-edb1-size

  • mem-util-kht-dlu-edb1-utilization

entry

4194304

Used by flow table. Populated only when IPFIX is enabled.

NPU Memory

  • Forwarding table: edb0

Exported property names:

  • mem-util-kht-dlu-edb0-allocated

  • mem-util-kht-dlu-edb0-size

  • mem-util-kht-dlu-edb0-utilization

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

  • Forwarding table: edb1

Exported property names:

  • mem-util-kht-dlu-edb1-allocated

  • mem-util-kht-dlu-edb1-size

  • mem-util-kht-dlu-edb1-utilization

entry

4194304

Used by flow table. Populated only when IPFIX is enabled.

Firewall / Filter

  • Policer IDs

Exported property names:

  • mem-util-policer-id-size

  • mem-util-policer-id-allocated

  • mem-util-policer-id-utilization

B

16384

Contributors are firewall policers, and interface policers

Firewall / Filter

  • Policer/Counter space

Exported property names:

  • mem-util-plct-size

  • mem-util-plct-allocated

  • mem-util-plct-utilization

  • mem-util-plct-filter-bytes-allocated

  • mem-util-plct-filter-allocation-count

  • mem-util-plct-filter-free-count

  • mem-util-plct-ing-nh-bytes-allocated

  • mem-util-plct-ing-nh-allocation-count

  • mem-util-plct-ing-nh-free-count

  • mem-util-plct-egr-nh-bytes-allocated

  • mem-util-plct-egr-nh-allocation-count

  • mem-util-plct-egr-nh-free-count

  • mem-util-plct-misc-bytes-allocated

  • mem-util-plct-misc-allocation-count

  • mem-util-plct-misc-free-count

  • mem-util-plct-memory-size

  • mem-util-plct-memory-allocated

  • mem-util-plct-memory-utilization

B

131072

Issues 1 word per counter, 3 words per single rate policer, and 5 words for tricolor policers.

Next-hops and encapsulation

  • IRP Memory: Load-balancing partition

Exported property names:

  • mem-util-jnh-loadbal-allocated

  • mem-util-jnh-loadbal-size

  • mem-util-jnh-loadbal-utilization

KWords

128

Load-balancing data structures. Contributors are aggregated Ethernet and multipath.

Next-hops and encapsulation

  • IRP Memory: Next-hop partition

Exported property names:

  • mem-util-jnh-loadbal-allocated

  • mem-util-jnh-loadbal-size

  • mem-util-jnh-loadbal-utilization

  • mem-util-jnh-loadbal-utilization

KWords

256

Used for next-hops. Contributors are next-hops.

Next-hops and encapsulation

  • IRP Memory: EDF partition

Exported property names:

  • mem-util-edf-public-words-allocated

  • mem-util-edf-public-words-size

  • mem-util-edf-public-words-utilization

KWords

320

Encapsulation data structures. Contributors are forwarding next-hops.

Next-hops and encapsulation

  • IRP Memory: MPLS label memory

Exported property names:

  • mem-util-jnh-mpls-allocated

  • mem-util-jnh-mpls-size

  • mem-util-jnh-mpls-utilization

KWords

128

MPLS Label structures. Contributors are MPLS Labels.

Table 4: NPU utilization sensor (resource path /junos/system/linecard/npu/utilization/)

Native Sensor Property Name

gRPC Sensor Property Name

Unit Type

Range

Description

NPU Utilization

  • Utilization

Exported property names:

  • util-metric

percent

Current PE chip utilization. Contributor is traffic stream.

NPU Utilization

  • Packet Load

Exported property names:

  • util-loopback-pps-rate

  • util-recirculation-pps-rate

  • util-asic-to-host-pps-rate

  • util-wan-and-host-inject-pps-rate

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

  • Memory Load

Exported property names:

  • util-hmc-average-util

  • util-hmc-highest-util

  • util-hmc-lowest-util

  • util-hmc-average-cache-hit-rate

  • util-hmc-highest-cache-hit-rate

  • util-hmc-lowest-cache-hit-rate

percent/per-sec

HMC memory utilization and memory cache hit rate