Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

per-route-accounting

date_range 25-Jun-24

Syntax

content_copy zoom_out_map
per-route-accounting

Hierarchy Level

content_copy zoom_out_map
[edit routing-options flow],
[edit routing-instances flow],
[edit routing-options-rib-inet6.0 flow],
[edit routing-instance-rib-inet6.0 flow]

Description

Earlier to Junos OS Evolved Release 21.1R1, by default, in the usual BGP FlowSpec filter, an individual counter was added for each FlowSpec term configured. As part of optimization of FlowSpec, starting from Junos OS Evolved Release 21.1R1 this behavior is changed, and counter action is not added by default. This will create more room for filter terms compression. When the term counters are not programmed, the traffic matching against a specific flow term is not accounted. You can use the new configuration statement per-route-accounting under the [edit routing-options flow] hierarchy level to enable creation of term counters for flowspec at global level on PTX10001-36MR, PTX10004, and PTX10008.

Default

The term counters are disabled by default.

Required Privilege Level

routing-options flow-To enable the new configuration statement.

footer-navigation