command stringlengths 2 75 | syntax stringlengths 0 289k | hierarchy_level stringlengths 0 6.91k | description stringlengths 0 45.2k | options listlengths 0 499 | required_privilege_level stringlengths 0 330k | release_information stringlengths 0 3.14k | related_documentation listlengths 0 22 |
|---|---|---|---|---|---|---|---|
filter-interfaces | [edit snmp] | Configure the options available for the filter-interfaces statement to specify the interfaces that you
want to exclude from the output of SNMP Get and GetNext requests performed on interface-related MIBs. | [
{
"name": "all-internal-interfaces",
"desc": "Filters out all the internal interfaces from the output of SNMP Get and GetNext"
},
{
"name": "interfaces interfaces",
"desc": "Specify the interfaces to filter them out from the output of SNMP Get and GetNext"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Filtering Interface Information Out of SNMP Get and GetNext Output"
] | |
filter-list-template | filter-list-template; | [edit firewall family (inet | inet6) filter filter-name],
[edit logical-systems logical-system-name firewall family (inet | inet6) filter filter-name] | (MX5, MX10, MX40, and MX80 routers, and routers that use MX Series MPC line cards only) Configure
all interfaces that use the same filter list to use a common template. This feature can be used to save
microkernel memory and DMEM memory.
If the same filter list cannot be used on all interfaces, consider merging the fil... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3R9. | [
"input-list",
"output-list",
"Firewall Filter Match Conditions for IPv6 Traffic"
] |
filter-profile | filter-profile profile-name {
counters {
counter-name;
}
file filename;
interval minutes;
start-time time;
} | [edit accounting-options] | Create a profile to filter and collect packet and byte count statistics and write them to a file in
the /var/log directory. To apply the profile to a firewall filter, you include the accounting-profile statement
at the [edit firewall filter filter-name] hierarchy level. For more information about firewall filters, see
... | [
{
"name": "profile-name",
"desc": "Name of the filter profile."
},
{
"name": "start-time",
"desc": ""
},
{
"name": "time",
"desc": "(Optional) Specify the start time in yyyy-mm-dd.hh:mm local time format for the accounting profile. Sometimes, if the time at which the records are writ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Firewall Filters Overview",
"Configuring the Filter Profile"
] |
filter-specific (QFX) | filter-specific; | [edit firewall policer policer-name] | Configure a policer to be filter-specific, which means that Junos OS creates only one policer instance
regardless of how many times the policer is referenced. If you use a filter-specific policer in multiple
terms, both of the following are true:
•
Traffic is policed at the aggregate rate. For example, if you create a ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration | Statement introduced in Junos OS Release 11.1. | [
"Configuring Two-Color and Three-Color Policers to Control Traffic Rates",
"Overview of Policers"
] |
filter-specific | filter-specific; | [edit dynamic-profiles profile-name firewall policer policer-name],
[edit firewall family inet prefix-action name],
[edit firewall policer policer-name],
[edit logical-systems logical-system-name firewall policer policer-name],
[edit logical-systems logical-system-name firewall family inet prefix-action name] | By default, a policer operates in term-specific mode, which means that for a given firewall filterthe
Junos OS creates a separate policer instance for every filter term that references the policer. You can,
however, use a common policer instance for all terms within the same firewall filter by setting the filter-
speci... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... policer policer-name] hierarchy level introduced in Junos OS
Release 11.4. | [
"Filter-Specific Policer Overview",
"Prefix-Specific Counting and Policing Overview",
"Filter-Specific Counter and Policer Set Overview"
] |
filtering-type (Source NAT Next Gen Services) | filtering-type {
endpoint-independent {
prefix-list [allowed-host] except [denied-host ];
}
} | [edit services nat source rule-set rule-set rule rule-name then source-nat] | Specify prefix lists that contain prefixes of hosts that are allowed to establish inbound connections using
endpoint-independent mapping, and prefix lists for hosts that are not allowed to establish inbound
connections. (Prefix lists are configured at the [edit policy-options] hierarchy level.) | [
{
"name": "[allowed-host ]",
"desc": "Names of the prefix lists for hosts that are allowed to establish connections."
},
{
"name": "except [ denied-host ]",
"desc": "Names of prefix lists for hosts that are not allowed to establish connections."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
filtering-type | filtering-type endpoint-independent; | [edit services nat rule (Services NAT) rule-name term (Services NAT) term-name then (Services NAT)
translated] | Specify the NAT filtering behavior for sessions initiated from outside to inside. | [
{
"name": "endpoint-independent",
"desc": "Currently, the only valid setting specifies endpoint-independent filtering"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.1. | [
"Network Address Translation Rules Overview"
] |
filters | filters {
age-of-attack
{
greater-than value;
less-than value;
}
category (Security Dynamic Attack Group) {
values [ values];
}
cvss-score
{
greater-than value;
less-than value;
}
direction {
... | [edit security idp dynamic-attack-group dynamic-attack-group-name] | To create a dynamic attack group, set the criteria using different types of filters. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. The expression option added in Junos OS Release 11.4.
Additional tags under filters of dynamic attack groups (CVSS score, age-of-attack, file-type, vulnerability-
type) are added in Junos OS Release 18.2R1 for dynamic attacks grouping of IDP signatures. The
Product and Vend... | [] |
fin-invalidate-session | fin-invalidate-session; | [edit security flow tcp-session] | Invalidates a TCP session after the 4-way or 3-way handshake completes, with each session endpoint
signalling conclusion of the session independently. New incoming SYN packets will need to establish a
new TCP session.
When either session endpoint wants to terminate the session, it sends a FIN(ish) message. When the
oth... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 10.4 R13. | [
"Understanding Traffic Processing on Security Devices"
] |
fin-no-ack (IDS Screen Next Gen Services) | fin-no-ack; | [edit services screen ids-option screen-name tcp] | Identify and drop any packet with a FIN flag set and without the ACK flag set. The TPC FIN No Ack
attack can allow the attacker to identify the operating system of the target or to identify open ports on
the target. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
fin-no-ack | fin-no-ack; | [edit security screen ids-option screen-name tcp] | Enable detection of an illegal combination of flags, and reject packets that have this combination. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
final-response-timeout (OCS Partition) | final-response-timeout seconds; | [edit access ocs partition partition-name] | Configure the amount of time in seconds before an Online Charging System (OCS) partition stops
attempting to send the final interrogation during the subscriber logout process. When a subscriber starts
to logs out, the OCS sends a final interrogation. If there is no response within 24 hours, then the system
continues an... | [
{
"name": "seconds",
"desc": "Number of seconds to wait before an OCS partition stops sending the final interrogation using a CCR-GY-T message. Default: 7200 Range: 0 through 86,400 seconds (24 hours)"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"3GPP Policy and Charging Control Overview for Wireline Provisioning and Accounting",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between t... |
finger | finger {
connection-limit limit;
rate-limit limit;
} | [edit system services] | Allow finger requests from remote systems to the local device. | [
{
"name": "connection-limit limit",
"desc": "Configure the maximum number of connection sessions for the finger service per protocol (either IPv4 or IPv6). NOTE: The actual number of maximum connections depends on the availability of system resources, and might be fewer than the configured connection-limit ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Finger Service for Remote Access to the Router"
] |
fip | fip {
fcoe-trusted;
fc-map fc-map-value;
fka-adv-period milliseconds;
interface {
interface-name {
fka-adv-period milliseconds;
priority priority;
}
}
max-sessions-per-enode max-sessions-per-enode;
priority priority;
traceoptions {
file f... | [edit fc-fabrics fc-fabric-name protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring FIP on an FCoE-FC Gateway",
"Overview of FIP"
] |
fip-security | fip-security {
examine-vn2vf;
examine-vn2vn {
beacon-period milliseconds;
}
fc-map fc-map-value;
interface interface-name {
(fcoe-trusted | no-fcoe-trusted;)
}
} | [edit vlans vlan-name forwarding-options] | NOTE: This statement supports the Enhanced Layer 2 Software (ELS) CLI. If your switch
runs the original (non-ELS) software, see examine-fip. For ELS details, see Using the
Enhanced Layer 2 Software CLI.
Configure FIP snooping and FCoE interface properties.
The remaining statements are explained separately. Also, see CL... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced for the ELS CLI in Junos OS Release 13.2 for the QFX Series. | [
"Understanding VN_Port to VF_Port FIP Snooping on an FCoE Transit Switch",
"Understanding VN_Port to VN_Port FIP Snooping on an FCoE Transit Switch",
"Understanding FCoE Transit Switch Functionality",
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch",
"Enabling VN2V... |
firewall (Dynamic Firewalls) | firewall {
family family {
fast-update-filter filter-name {
interface-specific;
match-order [match-order];
term term-name {
from {
match-conditions;
}
then {
action;
... | [edit dynamic-profiles profile-name] | Configure firewall filters and policers in a dynamic client profile or a dynamic service profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Methods for Regulating Traffic by Applying Hierarchical Policers",
"Configuring Fast Update Filters"
] |
firewall | firewall {
family family-name {
filter filter-name {
interface-specific;
micro-segmentation;
no-longest-prefix-match;
term term-name {
from {
match-conditions;
}
then {
act... | [edit] | Configure firewall filters and policers.
The remaining statements are explained separately. See CLI Explorer. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Option micro-segmentation introduced in Junos OS Release 22.4R1 for supported switches. | [
"Firewall Filter Match Conditions and Actions (QFX5100, QFX5110, QFX5120, QFX5200, EX4600,",
"EX4650)",
"Configuring Firewall Filters",
"Configuring Two-Color and Three-Color Policers to Control Traffic Rates",
"Overview of Firewall Filters (QFX Series)"
] |
firewall-authentication (Security Policies) | firewall-authentication {
pass-through {
access-profile profile-name;
client-match user-or-group-name;
ssl-termination-profile profile-name;
web-redirect;
web-redirect-to-https;
auth-only-browser
auth-user-agent
}
push-to-identity-management
us... | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit] | Configure firewall authentication methods.
On SRX Series Firewall, you must configure security policy with firewall-authentication at initial stage.
When ssl-termination-profile is engaged with firewall-authentication in security policy, you can’t
configure dynamic-application statement at [edit security policies from-... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Support added for the user-firewall option in Junos OS Release 12.1X45-D10.
Support for the ssl-termination-profile and web-redirect-to-https options added on SRX5600 and SRX5800
Services Gateways starting from Junos OS Release 12.1X44-D10, on SRX5400 devices starting from
... | [
"Understanding User Role Firewalls"
] |
firewall-authentication (Security) | firewall-authentication {
mtls-profile profile-name;
mtls-profile-fallback-password;
traceoptions (Security Firewall Authentication) {
flag (all | authentication | proxy) {
}
}
} | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "mtls-profile",
"desc": "Enable passwordless user authentication based on client/server certificate validation"
},
{
"name": "mtls-profile-fallback-password",
"desc": "Enable user authentication with mTLS and fallback to standard login"
},
{
"name": "flag",
"desc": "Trace o... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configure Mutual-TLS (mTLS) Authentication",
"SRX Firewall Users",
"Understanding Logical System Firewall Authentication"
] |
firewall-authentication (tenants) | firewall-authentication {
pass-through (Access Firewall-Authentication) {
default-profile default-profile;
ftp {
banner (Access FTP HTTP Telnet Authentication) {
fail fail;
login login;
success success;
}
}
ftp {... | [edit logical-systems name tenants name access],
[edit tenants name access] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | access | Statement introduced in Junos OS Release 18.3R1 | [
"Firewall Authentication for Tenant Systems"
] |
firewall-authentication | firewall-authentication {
pass-through {
default-profile profile-name;
ftp {
banner {
fail string;
login string;
success string;
}
}
http {
banner {
fail string;
... | [edit access] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"SRX Firewall Users",
"Configure Authentication Methods For SRX Firewall Users",
"Juniper Secure Connect"
] |
firewall-authentication-forced-timeout | firewall-authentication-forced-timeout minutes; | [edit services user-identification active-directory-access] | Configure the firewall authentication forced timeout setting to apply to entries for user who
authenticate through captive portal.
When a user authenticates through captive portal, an authentication table entry is generated for that
user based on the information that the SRX Series Firewall obtains from the firewall au... | [
{
"name": "minutes",
"desc": "The maximum duration for which the non-domain users who authenticate through captive portal remain authenticated. Default: 30 minutes Range: 10 through 1440 minutes"
}
] | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D100. | [
"Understanding the Forced Timeout Setting Assigned to Active Directory Authentication Entries for",
"Users Authenticated Through Captive Portal",
"invalid-authentication-entry-timeout",
"Understanding the Invalid Authentication Table Entry Timeout Setting"
] |
firewall-authentication-service | firewall-authentication-service (enable | disable); | [edit system processes] | Enable or disable the firewall authentication service process. | [
{
"name": "enable",
"desc": "Start the firewall authentication service process."
},
{
"name": "disable",
"desc": "Stop the firewall authentication service process."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Firewall User Authentication Overview"
] |
firewall-install-disable | firewall-install-disable; | [edit routing-options flow],
[edit logical-systems logical-system-name routing-options flow],
[edit routing-instances routing-instance-name routing-options flow],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options flow] | Disable installing flow-specification firewall filters in the firewall process (dfwd).
Default
For PTX Series routers, this statement appears in the default configuration, preventing installation of
flow-specification firewall filters into dfwd. For other models, this setting is omitted from the default
configuration, ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 12.1X48 and 12.3. | [
"Example: Enabling BGP to Carry Flow-Specification Routes",
"Understanding BGP Flow Routes for Traffic Filtering"
] |
firewall-user | firewall-user {
password password;
} | [edit access profile profile-name client client-name] | Specify a client as a firewall user and the associated password (encrypted). | [
{
"name": "password password",
"desc": "Password used by the firewall user during local authentication."
}
] | secret—To view this statement in the configuration.
secret-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Example: Configuring RADIUS and LDAP User Authentication"
] |
firmware-revision | firmware-revision firmware-revision; | [edit access diameter] | Configure the firmware revision that is advertised in the Capabilities-Exchange-Request or Capabilities-
Exchange-Answer message. | [
{
"name": "firmware-revision",
"desc": "Number of the firmware revision that is the advertised value of the Firmware-Revision AVP. Default: 0 Range: 0 through 4294967295"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
fiveqi-map | fiveqi-map identifier {
upstream-rewrite {
dscp dscp;
dscp-n3 dscp-n3;
forwarding-class forwarding-class;
loss-priority(high | low);
}
} | [edit services agf] | Configure the Quality of Service (QoS) attributes for a 5G QoS identifier (5QI) value in the 5QI table.
Customers send data packets across the access Y5 interface to the Access Gateway Function (AGF) in
clear IP text. AGF encapsulates the data packet using GPRS Tunnelling Protocol (GTP) and forwards the
encapsulated pa... | [
{
"name": "identifier",
"desc": ""
},
{
"name": "5QI number",
"desc": "Range: 0 through 63"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Command introduced in Junos OS Release 23.2R1. | [
"CoS for Subscriber Access Overview"
] |
fixed-stuff-bytes | (fixed-stuff-bytes | no-fixed-stuff-bytes); | [edit interfaces interface-name otn-options rate] | Enable or disable fixed stuff bytes.
Default
By default, no fixed stuff bytes are set. | [
{
"name": "fixed-stuff-bytes",
"desc": "Fixed stuff bytes 11.0957 Gbps."
},
{
"name": "no-fixed-stuff-bytes",
"desc": "No fixed stuff bytes 11.0491 Gbps."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
fka-adv-period | fka-adv-period milliseconds; | [edit fc-fabrics fc-fabric-name protocols fip],
[edit fc-fabrics fc-fabric-name protocols fip interface interface-name] | Set the global or interface-specific interval between periodic FIP keepalive advertisements. An interval
set at the interface level overrides the global setting. | [
{
"name": "milliseconds",
"desc": "Time in milliseconds between FIP keepalive advertisements."
}
] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Overview of FIP"
] |
flag (App Engine Virtual Machine Management Service) | flag (all |ccif | configuration | heartbeat | init | miscellaneous | platform | pxe | routing-
instances | snmp) | [edit system processes app-engine-virtual-machine-management-service traceoptions] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "all",
"desc": "Trace all events."
},
{
"name": "ccif",
"desc": "Trace compute node interface events. This is the default option."
},
{
"name": "configuration",
"desc": "Trace configuration events."
},
{
"name": "heartbeat",
"desc": "Trace compute node heartbeat... | system-control | Statement introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] |
flag (Interfaces) | flag | [edit interfaces interface-name traceoptions] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "all",
"desc": "Enable all interface trace flags."
},
{
"name": "event",
"desc": "Trace interface events."
},
{
"name": "cache",
"desc": "Enable interface flags for Web filtering cache maintained on the routing table."
},
{
"name": "enhanced",
"desc": "Enable in... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Understanding Interfaces"
] |
flag (Next Gen Services Global System Logging) | flag name; | [edit services rtlog traceoptions] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "name",
"desc": "Values:"
},
{
"name": "all",
"desc": "Enable all interface trace flags. event —Trace interface events."
},
{
"name": "cache",
"desc": "Enable interface flags for Web filtering cache maintained on the routing table."
},
{
"name": "enhanced",
"des... | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
flag (Services) | flag (all | cli-configuration | initiation | proxy | selected-profile | termination); | [edit services ssl traceoptions] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "all",
"desc": "Trace all the parameters."
},
{
"name": "cli-configuration",
"desc": "Trace CLI configuration events."
},
{
"name": "initiation",
"desc": "Trace initiation service events."
},
{
"name": "proxy",
"desc": "Trace proxy service events."
},
{
... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. This statement is supported. | [
"Configuring SSL Forward Proxy"
] |
flag (SMTP) | flag {
all;
configuration;
IPC;
protocol-exchange;
send-request;
} | [edit smtp traceoptions] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "IPC",
"desc": "Trace interprocesss communication."
},
{
"name": "all",
"desc": "Trace everything."
},
{
"name": "configuration",
"desc": "Trace configuration event."
},
{
"name": "protocol-exchange",
"desc": "Trace SMTP protocol exchanges."
},
{
"name":... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement added in Junos OS Release 10.0. | [] |
flag (Tracing for Origin AS Validation) | flag flag <flag-modifier> <disable>; | [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation traceoptions],
[edit logical-systems logical-system-name routing-instances instance-name routing-options
validation group group-name session address traceoptions],
[edit logical-systems logical-system-name routing-opt... | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "flag",
"desc": "Tracing operation to perform. To specify more than one RPKI BGP route validation tracing operation, include multiple flag statements. Values:"
},
{
"name": "all",
"desc": "Trace all events."
},
{
"name": "error",
"desc": "Trace errored packets."
},
{
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Use Case and Benefit of Origin Validation for BGP"
] |
flap-trap-monitor | flap-trap-monitor seconds; | [edit logical-systems name protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles],
[edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles],
[edit logical-systems name protocols oam ethernet connectivity-fault-management perfor... | Enables damping of jnxSoamPmThresholdCrossingAlarm traps sent to the network management system
(NMS) by summarizing the flap occurrences over a period of time and sends a single
jnxSoamPmThresholdFlapAlarm notification to the NMS. You can enable damping at the global level for
the iterator or you can enable damping at ... | [
{
"name": "seconds",
"desc": "Duration in seconds, for summarizing flap occurrences and send out a single jnxSoamPm"
}
] | routing | Statement introduced in Junos OS Release 17.2R1. | [
"Damping CFM performance Monitoring Traps and Notifications to Prevent Congestion of The NMS"
] |
flat-file-profile (Accounting Options) | flat-file-profile profile-name{
fields {
all-fields;
egress-stats {
all-fields;
input-bytes;
input-packets;
output-bytes;
output-packets;
queue-id;
red-drop-bytes;
red-drop-packets;
tail-drop-... | [edit accounting-options] | Configure a flat-file accounting profile that defines the contents of a flat file that records accounting
statistics collected from the Packet Forwarding Engine for an interface at regular intervals. To be used,
the profile is associated with a subscriber interface. The accounting flat file is archived by the
accountin... | [
{
"name": "profile-name",
"desc": "Name of the flat-file profile."
},
{
"name": "start-time time",
"desc": "(Optional) Specify the start time in yyyy-mm-dd.hh:mm local time format for the accounting profile. Sometimes, if the time at which the records are written to the accounting file is beyond... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4.
service-accounting option added in Junos OS Release 17.1.
Support for the service-accounting option removed in Junos OS Release 18.1R4.
use-fc-ingress-stats option added in Junos OS Release 21.2R1. | [
"Configuring Accounting-Data Log Files",
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Configuring Service Accounting in Local Flat Files",
"Flat-File Accounting Overview"
] |
flat-file-profile (Extensible Subscriber Services) | flat-file-profile profile-name | [edit system services extensible-subscriber-services] | Specify the name of an accounting flat file profile that applies to an ESSM subscriber. | [
{
"name": "profile name",
"desc": "Name of an accounting flat file profile configured at the [edit accounting-options] hierarchy level."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Flat-File Accounting for Extensible Subscriber Services Management"
] |
flex-algorithm (Protocols OSPF) | flex-algorithm name {
color color;
definition (Protocols OSPF) ;
} | [edit logical-systems name routing-instances name routing-options],
[edit logical-systems name routing-options],
[edit logical-systems name tenants name routing-instances name routing-options],
[edit routing-instances name routing-options],
[edit routing-options],
[edit tenants name routing-instances name routing-optio... | Define a flexible algorithm for OSPFv2 to compute a path based on specified parameters to thin slice a
network. We recommend configuring flexible algorithms on only a couple of routers to provide
redundancy and to avoid conflicts.
Configure participation of routers in a specific flexible algorithm in a network at the ... | [
{
"name": "name",
"desc": "Specify a flexible algorithm id to identify a flexible algorithm definition. Range: 128 through 255"
},
{
"name": "color",
"desc": "Specify a color to be associated with this flexible algorithm."
}
] | routing | Statement introduced in Junos OS Release 21.1R1. | [
"definition (Protocols OSPF)",
"How to Configure Flexible Algorithms in OSPF for Segment Routing Traffic Engineering"
] |
flex-algorithm | flex-algorithm name {
color color;
definition;
} | [edit logical-systems name routing-instances name routing-options],
[edit logical-systems name routing-options],
[edit logical-systems name tenants name routing-instances name routing-options],
[edit routing-instances name routing-options],
[edit routing-options],
[edit tenants name routing-instances name routing-optio... | Define a flexible algorithm for IS-IS to compute a path based on specified parameters to thin slice a
network. We recommend configuring flexible algorithms on only a couple of routers to provide
redundancy and to avoid conflicts.
Configure participation of routers in a specific flexible algorithm in a network at the [e... | [
{
"name": "name",
"desc": "Specify a flexible algorithm id to identify a flexible algorithm definition. Range: 128 through 255"
},
{
"name": "color",
"desc": "Specify a color to be associated with this flexible algorithm."
}
] | routing | Statement introduced in Junos OS Release 19.4R1. | [
"Configuring Flexible Algorithm for Segment Routing",
"Understanding IGP Flexible Algorithms for Segment Routing"
] |
flex-algorithm-preference | flex-algorithm-preference flex-algorithm-preference; | [edit logical-systems name protocols ospf],
[edit logical-systems name routing-instances name protocols ospf],
[edit logical-systems name tenants name routing-instances name protocols ospf],
[edit protocols ospf],
[edit routing-instances name protocols ospf],
[edit tenants name routing-instances name protocols ospf] | Preference of flexible algorithm L-OSPF routes. You can control path selection by configuring the
preference for L-OSPF Flexible Algorithm routes in inetcolor.0 and mpls.0 to prioritize desired routes and
improve traffic engineering across IP and MPLS domains. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | flex-algorithm-preference statement introduced in Junos OS and Junos OS Evolved Release 25.4R1. | [] |
flex-flow-sizing | flex-flow-sizing; | [edit chassis fpc slot-number inline-services] | Configure support for the service creation of flows for inline services sampling. This configuration results
in a first-come-first-serve creation of flows. Whichever flow comes first, that flow is allowed to occupy
the flow table if there is space in the table. Otherwise, the flow is dropped and an error count is creat... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F5.
NOTE: The flex-flow-sizing configuration statement is not supported on the MX204
router until Junos OS Release 17.4R2 or Junos OS Release 18R3. If you need to set the
flow size for a release prior to those releases for the MX204 router, configure the flow-
table-size sta... | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250",
"Including Fragmentation Identifier and IPv6 Extension Header Elements in IPFIX Templates on MX",
"Series Routers"
] |
flex-hashing | flex-hashing name {
ethtype {
inet {
conditional-match conditional-match;
hash-offset {
offset1 {
base-offset1 (start-of-L2Header | start-of-L3-InnerHeader | start-of-L3-
OuterHeader | start-of-L4-Header);
offset1-mask offset1-m... | [edit forwarding-options enhanced-hash-key] | Configure user-defined flex hashing to load balance MPLS traffic based on TCP or UDP source/
destination port information. | [
{
"name": "name",
"desc": "Name identifier"
}
] | interface | Statement introduced in Junos OS Release 20.4R1. | [] |
flexible-cross-connect-vlan-aware | flexible-cross-connect-vlan-aware; | [edit logical-systems name routing-instances name protocols evpn],
[edit routing-instances name protocols evpn] | Enable EVPN-VPWS flexible cross-connect (FXC) VLAN aware service. For FXC service, all point-to-
point Ethernet services under the same EVPN-VPWS instance share the same incoming MPLS label.
FXC allows you to aggregate attachment circuits in the same EVPN-VPWS instance into a single group.
For FXC VLAN aware services, ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Overview of Flexible Cross-Connect Support on VPWS with EVPN"
] |
flexible-cross-connect-vlan-unaware | flexible-cross-connect-vlan-unaware; | [edit logical-systems name routing-instances name protocols evpn],
[edit routing-instances name protocols evpn] | Enable EVPN-VPWS flexible cross-connect (FXC) VLAN unaware Service. For EVPN-VPWS FXC service,
all point-to-point Ethernet services under the same EVPN VPWS instance share the same incoming
MPLS label. FXC allows you to aggregate attachment circuits into a single group. When you enable
flexible-cross-connect-vlan-unawa... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Overview of Flexible Cross-Connect Support on VPWS with EVPN"
] |
flexible-match-ranges | flexible-match-ranges <flexible-ranges-name> | [edit firewall family <inet | inet6 | ethernet-switching> filter <filter-name> term <term-name>
from] | Configure multiple flex match ranges within the same term, allowing traffic to be filtered based on
several criteria simultaneously. Supported for family inet, inet6 and ethernet-switching.
NOTE: flexible-match-ranges and flexible-match-range cannot be configured in the same
term. | [
{
"name": "match-start",
"desc": "Start point to match in packet. payload match-start is not supported."
},
{
"name": "byte-offset",
"desc": "Byte offset after the match start point"
},
{
"name": "bit-offset",
"desc": "Bit offset after the (match-start + byte) offset. (0..7)"
},
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1 | [] |
flexible-queuing-mode | flexible-queuing-mode; | [edit chassis] | Enable flexible queuing on a non-HQoS MPCE that is installed in an MPC slot. A maximum of up to
32,000 queues are supported per port and per card, including queues on both ingress and egress
interfaces.
When flexible queuing is enabled, the non-HQoS MPC is restarted for the changes to take effect and is
brought online ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R1. | [
"Upgrading non-HQoS MPCs to Support Flexible Queuing",
"Flexible Queuing Mode Overview",
"Protocols and Applications Supported by the MPC5E for MX Series Routers"
] |
flexible-vlan-tagging | flexible-vlan-tagging; | [edit interfaces aex],
[edit interfaces ge-fpc/pic/port],
[edit interfaces et-fpc/pic/port],
[edit interfaces ps0],
[edit interfaces xe-fpc/pic/port] | Support simultaneous transmission of 802.1Q VLAN single-tag and dual-tag frames on logical interfaces
on the same Ethernet port, and on pseudowire logical interfaces.
NOTE: The flexible-vlan-tagging command is supported only with either no encapsulation
or VPLS VLAN encapsulation.
This statement is supported on M Serie... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
Support for aggregated Ethernet added in Junos OS Release 9.0.
For the list of products and applications that support this feature on Junos OS Evolved, see Flexible
VLAN Tagging. | [
"Enabling VLAN Tagging",
"Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers",
"Configuring Double-Tagged VLANs on Layer 3 Logical Interfaces"
] |
flood (Security ICMP) | flood {
threshold number;
} | [edit security screen ids-option screen-name icmp] | Configure the device to detect and prevent Internet Control Message Protocol (ICMP) floods. An ICMP
flood occurs when ICMP echo requests are broadcast with the purpose of flooding a system with so
much data that it first slows down, and then times out and is disconnected. The threshold defines the
number of ICMP packet... | [
{
"name": "threshold number",
"desc": "Number of ICMP packets per second allowed to ping the same destination address"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
flood (Security UDP) | flood {
threshold number;
white-list name;
} | [edit security screen ids-option screen-name udp] | Configure the device to detect and prevent UDP floods. UDP flooding occurs when an attacker sends
UDP packets to slow down the system to the point that it can no longer process valid connection
requests.
The threshold defines the number of UDP packets per second allowed to ping the same destination IP
address. When the... | [
{
"name": "threshold number",
"desc": "Number of UDP packets per second allowed to ping the same destination address"
},
{
"name": "white-list name",
"desc": "Configure a list of IP addresses that are exempted from UDP flood detection, which"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
flood (VLANs) | flood {
input filter-name;
} | [edit vlans vlan-name],
[edit vlans vlan-name forwarding-options (Bridge Domains or VLANs)] | Apply a flood filter to traffic ingressing a VLAN. Flood filters are triggered only for broadcast, unknown
unicast, and multicast (BUM) traffic.
Flood filters and firewall filters can coexist on the same VLAN. If the actions in the filters are conflicting,
then the firewall filter takes priority over the flood filter.... | [
{
"name": "filter-name",
"desc": "Name of a filter defined at the [edit firewall family family-name filter] hierarchy level."
},
{
"name": "input",
"desc": "Apply a flood filter to VLAN ingress traffic."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Configuring Unknown Unicast Forwarding (ELS)",
"Configuring Firewall Filters",
"Overview of Firewall Filters (QFX Series)"
] |
flood | flood {
input filter-name;
} | [edit forwarding-options family vpls],
[edit routing-instances instance-name forwarding-options family vpls] | Apply a forwarding table filter to a flood table. | [
{
"name": "input filter-name",
"desc": "Name of the forwarding table filter."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Applying Forwarding Table Filters",
"Layer 2 Port Mirroring Firewall Filters"
] |
flood-as-unknown-unicast | flood-as-unknown-unicast; | [edit interfaces irb unit name family inet address local-ip-address/prefix-length | arp local-ip-
address mac local-ip-address] | You can configure the flood-as-unknown-unicast statement for IRB interfaces located in any Layer 2 domain.
You can enable the flood-as-unknown-unicast statement for unicast MAC addresses. When a switch receives
traffic from a unicast MAC address that is the destination MAC address, the switch floods the packets
on the ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1. | [] |
flood-groups | flood-groups [ ip-addresses ]; | [edit bridge-domains bridge-domain-name multicast-snooping-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name multicast-snooping-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name multicast-
snooping-opt... | Establish a list of flood group addresses for multicast snooping. | [
{
"name": "ip-addresses",
"desc": "List of IP addresses subject to flooding."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring Multicast Snooping"
] |
flood-reflector (Protocols IS-IS) | flood-reflector {
client;
reflector {
cluster-id;
}
} | [edit logical-systems logical-system-name protocols isis interface interface-name level level-
number],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name level level-number],
[edit protocols isis interface interface-name level level-number],
[edit... | IS-IS supports flood-reflector interfaces. Flood reflectors enable the creation of topologies where Level
1 areas provide transit forwarding for Level 2 destinations within a Level 2 topology. This is
accomplished by creating Level 2 flood-reflection adjacencies within each Level 1 area.
The Level 2 flood reflection ad... | [
{
"name": "client",
"desc": "Configure interface as a flood-reflector client."
},
{
"name": "reflector",
"desc": "Configure interface as a flood reflector."
},
{
"name": "cluster-id",
"desc": "The flood-reflector cluster identifier that allows a flood reflector client to establish fl... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"How to Configure Flood-Reflector Interfaces in IS-IS Networks"
] |
flood-reports-to-inter-switch-interface (IGMP Snooping) | flood-reports-to-inter-switch-interface; | [edit protocols igmp-snooping vlan vlan-name],
[edit routing-instances routing-instance-name protocols igmp-snooping vlan vlan-name],
[edit routing-instances routing-instance-name bridge-domains bd-name protocols igmp-snooping],
[edit bridge-domains bd-name protocols igmp-snooping] | Flood IGMP reports to the inter-switch link (ISL) and restrict sending it to the host links. This can be
configured on a vlan or bridge-domains level.
Default
This configuration is disabled by default. | [] | Statement introduced in Junos OS Release 25.2R1. | [
"No Link Title"
] | |
flood-reports-to-inter-switch-interface (MLD Snooping) | flood-reports-to-inter-switch-interface; | [edit protocols mld-snooping vlan vlan-name],
[edit routing-instances routing-instance-name protocols mld-snooping vlan vlan-name],
[edit routing-instances routing-instance-name bridge-domains bd-name protocols mld-snooping],
[edit bridge-domains bd-name protocols mld-snooping] | Flood MLD reports to the inter-switch link (ISL) and restrict sending it to the host links. This can be
configured on a vlan or bridge-domains level.
Default
This configuration is disabled by default. | [] | Statement introduced in Junos OS Release 25.2R1. | [
"No Link Title"
] | |
flow (IPv6) | flow {
discard-action-for-unresolved-redir-addr;
interface-group (Routing Options) group-name <exclude>;
(per-route-accounting | no-per-route-accounting);
route name {
match {
destination {
ipv6-prefix;
prefix-offset number;
}
... | [edit routing-options rib inet6.0],
[edit routing-instances routing-instance-name routing-options rib inet6.0] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "discard-action-for-unresolved-redir-",
"desc": ""
},
{
"name": "addr",
"desc": "Configure the discard action for BGP flow specification routes that were not resolved using the redirect to IP action."
},
{
"name": "interface-group",
"desc": ""
},
{
"name": "group<ex... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Example: Configuring BGP to Carry IPv6 Flow Specification Routes",
"Example: Enabling BGP to Carry Flow-Specification Routes",
"Understanding BGP Flow Routes for Traffic Filtering"
] |
flow (protocols bgp) | flow {
no-validate policy-name;
secondary-independent-resolution;
} | [edit protocols bgp group group-name family (inet | inet-vpn | inet6 | inet6-vpn)],
[edit protocols bgp group group-name neighbor address family (inet | inet-vpn | inet6 | inet6-
vpn)],
[edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet-
vpn | inet6 | inet6-vpn)],
[edit ro... | Enables BGP to support flow routes.
NOTE: This statement is supported for the default instance, VRF instance, and virtual-
router instance only. It is configured with the instance-type statement at the [edit routing-
instance instance-name] hierarchy level.
The remaining statements are explained separately. See CLI Exp... | [
{
"name": "secondary-independent-",
"desc": ""
},
{
"name": "resolution",
"desc": "Configure to resolve flow specification routes in the VRF table independent of VPN flow route. This option is currently supported for inet and inet-vpn families only."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
secondary-independent-resolution option introduced in Junos OS Release 18.4R1 for the MX Series and PTX
Series. | [
"Example: Enabling BGP to Carry Flow-Specification Routes"
] |
flow (Security Flow) | flow {
advanced-options {
drop-matching-link-local-address;
drop-matching-reserved-ip-address;
reverse-route-packet-mode-vr;
}
aging {
early-ageout seconds;
high-watermark percent;
low-watermark percent;
}
allow-dns-reply;
allow-embedded-icmp;
... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "advanced-options",
"desc": "Flow configuration advanced options. Values:"
},
{
"name": "drop-matching-link-local-address",
"desc": "Drop matching link local address."
},
{
"name": "drop-matching-reserved-ip-address",
"desc": "Drop matching reserved source"
},
{
"n... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.5. The power-mode-ipsec option added in Junos OS Release
18.3R1 for vSRX Virtual Firewall instances, in Junos OS Release 18.4R1 for SRX4100 and SRX4200
devices, and in Junos OS Release 18.2R2 for SRX5400, SRX5600, and SRX5800 devices. The multicast-
nh-resolve-retry and the stri... | [
"Understanding Traffic Processing on Security Devices",
"Understanding Session Characteristics for SRX Series Services Gateways",
"Understanding Packet Flow in Logical Systems for SRX Series Devices"
] |
flow (Security IDP) | flow {
(allow-icmp-without-flow | no-allow-icmp-without-flow);
drop-if-no-policy-loaded;
drop-on-failover;
drop-on-limit;
fifo-max-size value;
hash-table-size value;
idp-bypass-cpu-threshold idp-bypass-cpu-threshold;
idp-bypass-cpu-tolerance idp-bypass-cpu-tolerance;
idp-bypass-cpu-u... | [edit security idp sensor-configuration] | Configure the IDP engine to manage the packet flow. | [
{
"name": "allow-nonsyn-connection",
"desc": "Allow TCP non-syn connection."
},
{
"name": "drop-if-no-policy-loaded",
"desc": "Drop all traffic till IDP policy gets loaded."
},
{
"name": "drop-on-failover",
"desc": "Drop traffic on HA failover sessions."
},
{
"name": "drop-on... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Options intel-inspect-cpu-usg-threshold, intel-inspect-cpu-usg-tolerance, intel-inspect-disable-content-
decompress, intel-inspect-enable, intel-inspect-free-mem-threshold, intel-inspect-mem-tolerance, intel-
inspect-protocols, intel-inspect-session-bytes-depth, and intel-i... | [] |
flow | flow {
discard-action-for-unresolved-redir-addr;
(fast-lookup-filter | no-fast-lookup-filter);
firewall-install-disable;
interface-group (Routing Options) group-name <exclude>;
(per-route-accounting | no-per-route-accounting);
route name
match {
destination prefix;
... | [edit routing-options],
[edit routing-instances routing-instance-name routing-options] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "discard-action-for-unresolved-redir-",
"desc": ""
},
{
"name": "addr",
"desc": "For action redirect IP if redirect address is unresolved install discard action filter."
},
{
"name": "fast-lookup-filter",
"desc": "Enable fast lookup filter. NOTE: The option fast-lookup-filt... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
term-order option introduced in Junos OS Release 10.0
firewall-install-disable option introduced in Junos OS Releases 12.1X48 and 12.3 for PTX Series routers.
interface-group option introduced in Junos OS Release 16.1R1.
per-route-accounting option introduced in Junos O... | [
"Example: Enabling BGP to Carry Flow-Specification Routes",
"Understanding BGP Flow Routes for Traffic Filtering"
] |
flow-action | flow-action (drop | forward) | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber default-local-
policy] | Specify the action to take on a subscriber’s data packets entering the access interface of the TDF
domain when a TDF IP-based subscriber session does not exist. | [
{
"name": "drop",
"desc": "Drop the subscriber’s packets."
},
{
"name": "forward",
"desc": "Forward the subscriber’s packets."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
flow-active-timeout (Flow Monitoring) | flow-active-timeout seconds; | [edit forwarding-options accounting name output],
[edit forwarding-options monitoring name output],
[edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls | vpls) output],
[edit forwarding-options sampling family (inet |inet6 |mpls |vpls) output],
[edit services flow-monitoring version9 temp... | Set the interval after which an active flow is exported.
NOTE:
•
The router must include an Adaptive Services, Multiservices, or Monitoring Services
PIC for this statement to take effect.
•
For Trio-based routers, if you configure the inline-jflow statement at the [edit
forwarding-options sampling instance instance-na... | [
{
"name": "seconds",
"desc": "Duration of the timeout period."
},
{
"name": "services configurations)",
"desc": "Default: 1800 seconds (for forwarding-options configurations); 60 seconds (for services configurations) NOTE: In active flow monitoring, the cflowd or flow monitoring version 9 record... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level added in
Junos OS Release 10.2.
Support at the [edit services flow-monitoring version9 template template-name] hierarchy level added in Junos
OS Release 16.1 for MPLS tra... | [
"Configuring Time Periods when Flow Monitoring is Active and Inactive",
"Configuring the Version 9 Template Properties",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices",
"Configuring Discard Accounting",
"C... |
flow-collector (Flow Collection) | flow-collector {
analyzer-address address;
analyzer-id name;
destinations {
ftp:url {
password "password";
}
}
file-specification {
variant variant-number {
data-format format;
name-format format;
transfer {
reco... | [edit services] | Define the flow collection.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Flow Collection Overview"
] |
flow-control (ACX Series) | (flow-control | no-flow-control); | [edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-name multiservice-options],
[edit interfaces interface-range name aggregated-ether-... | For aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces only, explicitly enable flow
control, which regulates the flow of packets from the router or switch to the remote side of the
connection. Enabling flow control is useful when the remote device is a Gigabit Ethernet switch. Flow
control is not suppo... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"Configuring Flow Control",
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)"
] |
flow-control (Interfaces) | (flow-control | no-flow-control); | [edit interfaces interface-name fastether-options]
[edit interfaces interface-name gigether-options]
[edit interfaces interface-name redundant-ether-options] | For Fast Ethernet, Gigabit Ethernet, and redundant Ethernet interfaces, flow control regulates the flow
of packets from the device to the remote side of the connection.
Default
Flow control is the default behavior for Fast Ethernet and Gigabit Ethernet interfaces. Flow control is
disabled by default for redundant Ether... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [
"Understanding Ethernet Interfaces"
] |
flow-control | (flow-control | no-flow-control); | [edit interfaces interface-name ether-options] | Explicitly enable or disable symmetric Ethernet PAUSE flow control, which regulates the flow of packets
from the switch to the remote side of the connection by pausing all traffic flows on a link during periods
of network congestion. Symmetric flow control means that Ethernet PAUSE is enabled in both
directions. The in... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)",
"Junos OS Network Interfaces Library for Routing Devices"
] |
flow-control-options | flow-control-options {
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
up-on-flow-control;
} | [edit interfaces mo-fpc/pic/port multiservice-options] | Configure the flow control options for application recovery in case of a prolonged flow control failure.
•
down-on-flow-control—Bring interface down during prolonged flow control.
•
dump-on-flow-control—Cause core dump during prolonged flow control.
NOTE: Starting with Junos OS Release 15.1, on MX Series routers with ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 8.4. | [] |
flow-control-queue (Output Congestion Notification) | flow-control-queue [ queue | list-of-queues ]; | [edit class-of-service congestion-notification-profile profile-name output ieee-802.1 code-point code-
point-bits] | Specify one or more output queues to pause, to support priority-based flow control (PFC). The specified
queues pause when the interface receives a PFC frame with a matching IEEE 802.1p code point.
Default
Queue 3 (mapped to the fcoe forwarding class) and queue 4 (mapped to the no-loss forwarding class)
are programmed a... | [
{
"name": "[ queue | list-of-queues]",
"desc": "The output queue or a list of output queues to pause."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit",
"Switch Interfaces",
"Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch",
"Interface",
"Example: Configuring ... |
flow-descriptions | flow-descriptions flow-identifier {
direction (uplink | downlink | both);
local-port-range {
low lower-boundary high upper-boundary;
}
local-ports number;
no-send-to-ue;
protocol protocol-number;
remote-address (ipv4-address ipv4-address | ipv6-address ipv6-address);
remote-port-... | [edit unified-edge pcef],
[edit services pcef] | Specify a service data flow (SDF) filter (flow identifier) that includes one or more filtering parameters
(address, protocol, and port) to identify the subscriber traffic that you want the SDF filter to detect. SDF
filters are specified in a PCC rule to identify the Layer 3 or Layer 4 IP packet flows that you want to
r... | [
{
"name": "flow-identifier",
"desc": "Name of the SDF filter. Range: 1 through 63 characters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef] hierarchy level introduced for Junos OS Broadband Subscriber
Management in Junos OS Release 17.2 on MX Series. | [
"Configuring Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management"
] |
flow-detect-time (DDoS Flow Detection) | flow-detect-time seconds; | [edit system ddos-protection protocols protocol-group packet-type flow-detection] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure how much time must pass before a suspicious flow that has exceeded the bandwidth allowed
for the packet type is confirmed to be a culprit flow.
BEST PRACTICE: We recommend that you use the default value for the detectio... | [
{
"name": "seconds",
"desc": "Period of excessive bandwidth required for flow to be a culprit flow."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Detection Period for Suspicious Flows",
"Configuring Flow Detection for Control Plane DDoS Protection"
] |
flow-detection (DDoS Flow Detection) | flow-detection; | [edit system ddos-protection global] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches) Enable
flow detection globally for all protocol groups and packet types except the following, which do not have
typical Ethernet, IP, or IPv6 headers:
•
Protocol groups: fab-probe, frame-relay, inline-ka, isis, jfm, mlp, pfe-aliv... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. Statement is supported on PTX10003 and PTX10008.
Use Feature Explorer to confirm platform support for this feature.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Enabling Flow Detection for All Protocol Groups and Packet Types",
"Setting Up and Using Flow Detection"
] |
flow-detection (DDoS Packet Level) | flow-detection {
flow-detect-time detect-period;
no-flow-logging;
timeout-active-flows enable-period;
flow-level-bandwidth {
logical-interface flow-bandwidth;
physical-interface flow-bandwidth;
subscriber flow-bandwidth;
}
flow-level-control {
logical-interface f... | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure control plane DDoS protection suspicious control flow detection for a packet type.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Setting Up and Using Flow Detection"
] |
flow-detection-mode (DDoS Flow Detection) | flow-detection-mode (automatic | off | on) | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure the mode of operation for flow detection for a protocol group or packet type. Use this
statement to override global flow detection settings configured with the flow-detection-mode statement at
the [edit system ddos-prot... | [
{
"name": "automatic",
"desc": "Detect flows only when the policer is being violated."
},
{
"name": "off",
"desc": "Disable flow detection."
},
{
"name": "on",
"desc": "Always monitor and detect flows, even when the policer is not being violated."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring How Flow Detection Operates for Individual Protocol Groups or Packets",
"Setting Up and Using Flow Detection"
] |
flow-detection-mode (DDoS Global Flow Detection) | flow-detection-mode (automatic | off | on) | [edit system ddos-protection global] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure the mode of operation for flow detection globally for almost all protocol groups and packet
types. The operation mode is effective only when flow detection is enabled.
NOTE: You cannot enable flow detection globally for... | [
{
"name": "automatic",
"desc": "Detect flows only when the policer is being violated."
},
{
"name": "off",
"desc": "Disable flow detection."
},
{
"name": "on",
"desc": "Always monitor and detect flows, even when the policer is not being violated."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring How Flow Detection Operates for Individual Protocol Groups or Packets",
"Setting Up and Using Flow Detection"
] |
flow-export-destination (Flow Collection) | flow-export-destination {
(cflowd-collector | collector-pic);
} | [edit forwarding-options monitoring group-name family inet output] | Configure flow collection. | [
{
"name": "cflowd-collector",
"desc": "Use the cflowd collector."
},
{
"name": "collector-pic",
"desc": "Use the collector PIC."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Exporting Flows",
"Configuring Passive Flow Monitoring"
] |
flow-export-rate | flow-export-rate rate; | [edit forwarding-options sampling instance instance-name family inet output inline-jflow] | Specify the flow export rate of monitored packets in kpps. If you have multiple line cards of different
types running on the same router, the flow-export-rate will be applied to each card. However, the rate
applied to the PFEs on the card will vary in accordance with the number of PFEs that are on the card.
On the MX S... | [
{
"name": "rate",
"desc": "Flow export rate of monitored packets in kpps (from 1 through 400). Default: 1 kpps (applies to all PFEs on the FPC) NOTE: The maximum rate per PFE is 100 kpps for LU, 800 kpps for XL/EA, so for an FPC with four LU PFEs (such as AS cards) you can set a maximum flow-export-rate of... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Discard Accounting",
"Configuring Flow Monitoring",
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
flow-export-timer | flow-export-timer seconds | [edit system packet-forwarding-options] | Configure the flow export period in seconds. The software exports a IPFIX packet periodically at the
configured flow-export timer interval. After you configure the flow export period, you must reboot the
device for it to take effect.
Default
10 seconds | [
{
"name": "seconds",
"desc": "Range: 10 to 600 seconds."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | [] | |
flow-gate | flow-gate {
maximum amount;
reserved amount;
} | [edit system security-profile] | Specifies the number of flow gates, also known as pinholes, that user logical system administrators and
primary logical system administrators can configure for their logical systems, if the security profile is
bound to the logical systems.
The primary administrator:
•
uses security profiles to provision logical systems... | [
{
"name": "maximum",
"desc": ""
},
{
"name": "amount",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows, it can utilize resources configured for the global maximum amount if they"
},
{
"name": "are available",
"desc": "... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems Security Profiles (Primary Administrators Only)"
] |
flow-groups | flow-groups {
flow-group-name {
node-device (node-device-name | serial-ID | alias);
interconnect-device interconnect-device-name;
}
node-device (node-device-name | serial-ID | alias) {
interconnect-device interconnect-device- name {
preference (high | normal | never);
... | [edit fabric] | In a QFabric system, a hash function is used to select an Interconnect device to forward traffic between
two ingress switches, which are called Node devices. Since this hash function is performed on all
Interconnect devices, it is possible for redundant multicast streams to flow through one Interconnect
device, making... | [
{
"name": "node-device node-device-name",
"desc": "Specify a QFabric system ingress Node switch by device name or alias in the QFabric system."
},
{
"name": "interconnect-device",
"desc": ""
},
{
"name": "interconnect-device-name",
"desc": "Specify a QFabric system Interconnect devic... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D15. | [
"Example: Creating a QFabric Flow Group",
"Understanding QFabric Multicast Flow Groups",
"Segregating QFabric Traffic Flows With Flow Groups"
] |
flow-inactive-timeout (Flow Monitoring) | flow-inactive-timeout seconds; | [edit forwarding-options accounting name output],
[edit forwarding-options monitoring name output],
[edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls | vpls) output],
[edit forwarding-options sampling family (inet |inet6 |mpls) output],
[edit services flow-monitoring version9 template t... | Configure the time that elapses before a flow is considered inactive.
NOTE: The router must include an Adaptive Services, Multiservices, or Monitoring
Services PIC for this statement to take effect. | [
{
"name": "seconds",
"desc": "Duration of the timeout period."
},
{
"name": "services configurations)",
"desc": "Default: 60 seconds (for forwarding-options configurations); 60 seconds (for services configurations)"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level added in
Junos OS Release 10.2.
Support at the [edit services flow-monitoring version9 template template-name] hierarchy level added in Junos
OS Release 16.1 for MPLS tr... | [
"Configuring Time Periods when Flow Monitoring is Active and Inactive",
"Configuring the Version 9 Template Properties",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices",
"Configuring Discard Accounting",
"C... |
flow-key (Flow Monitoring) | flow-key {
flow-direction;
vlan-id;
output-interface;
} | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Include VLAN IDs in both the ingress and egress directions in the flow key, enable flow direction
information in a Version 9 or IPFIX flow template, or both, and configure the output-interface for bridge
or VPLS family for inline flow monitoring on the MX Series. | [
{
"name": "flow-direction",
"desc": "Enable reporting of the direction of the flow. The field contains 0x00 (ingress) or 0x01 (egress). The flow direction field in the output record contains the invalid value 0xFF if you do not configure flow-direction."
},
{
"name": "vlan-id",
"desc": "Include ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.2.
output-interface option added in Junos OS Release 18.2R1. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250",
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX S... |
flow-label | flow-label; | [edit routing-instances name protocols evpn] | Advertise that the device is able to support flow-aware transport (FAT) labels for EVPN-MPLS E- LAN
services. With FAT flow labels, you can load balance MPLS packets across equal-cost multipath (ECMP)
paths or link aggregation groups (LAGs) without the need for deep packet inspection of the payload.
RFC 6391 describes ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 22.2R1. | [] |
flow-label-receive | flow-label-receive; | [edit protocols l2circuit neighbor neighbor-id interface interface-name],
[edit routing-instances routing-instance-name protocols l2vpn site name],
[edit routing-instances routing-instance-name protocols l2vpn site name interface interface-
name],
[edit routing-instances routing-instance-name protocols vpls] | Configure the router to signal the capability to pop the flow label in the receive direction to the remote
provider edge (PE) router.
The flow-aware transport of pseudowires (FAT) flow labels enable load-balancing of MPLS packets
across equal-cost multipath (ECMP) paths or link aggregation groups (LAGs) without the nee... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring the FAT Flow Label for FEC 128 VPWS Pseudowires for Load-Balancing MPLS Traffic",
"Configuring the FAT Flow Label for FEC 128 VPLS Pseudowires for Load-Balancing MPLS Traffic",
"Configuring the FAT Flow Label for FEC 129 VPWS Pseudowires for Load-Balancing MPLS Traffic",
"Configuring the FAT Flow... |
flow-label-receive-static | flow-label-receive-static; | [edit protocols l2circuit neighbor neighbor-id interface interface-name]
[edit routing-instances instance-name protocols evpn],
[edit routing-instances instance-name protocols evpn interface interface-name] | Configure the router to pop the flow label on pseudowire packets received from a remote provider edge
(PE) router. The ingress PE router inserts the flow label in the pseudowire packet regardless of the
information exchanged in the signaling plane. If the egress PE router cannot handle the pseudowire
packet with the fl... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Support in a EVPN-VPWS routing instance added in Junos OS Release 21.1R1. | [
"Configuring the FAT Flow Label for FEC 128 VPWS Pseudowires for Load-Balancing MPLS Traffic",
"FAT Flow Labels in EVPN-VPWS Routing Instances"
] |
flow-label-static | flow-label-static; | [edit routing-instances name protocols evpn] | For EVPN-MPLS E-LAN services, configure the router to signal the ability to push the flow-aware
transport (FAT) flow label on pseudowire packets received from a provider edge (PE) router or to pop
the FAT flow label on pseudowire packets transmitted to a PE router. The ingress PE router inserts the
flow label in the ps... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 22.2R1. | [] |
flow-label-transmit | flow-label-transmit; | [edit protocols l2circuit neighbor neighbor-id interface interface-name],
[edit routing-instances routing-instance-name protocols l2vpn site name],
[edit routing-instances routing-instance-name protocols l2vpn site name interface interface-
name],
[edit routing-instances routing-instance-name protocols vpls] | Configure the router to signal the capability to push the flow label in the transmit direction to the
provider edge (PE) router.
The flow-aware transport of pseudowires (FAT) flow labels enable load-balancing of MPLS packets
across equal-cost multipath (ECMP) paths or link aggregation groups (LAGs) without the need for... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring the FAT Flow Label for FEC 128 VPWS Pseudowires for Load-Balancing MPLS Traffic",
"Configuring the FAT Flow Label for FEC 128 VPLS Pseudowires for Load-Balancing MPLS Traffic",
"Configuring the FAT Flow Label for FEC 129 VPWS Pseudowires for Load-Balancing MPLS Traffic",
"Configuring the FAT Flow... |
flow-label-transmit-static | flow-label-transmit-static; | [edit protocols l2circuit neighbor neighbor-id interface interface-name],
[edit routing-instances instance-name protocols evpn],
[edit routing-instances instance-name protocols evpn interface interface-name] | Configure the router to push the flow label on pseudowire packets it sends to a remote provider edge
(PE) router. The ingress PE router inserts the flow label in the pseudowire packet regardless of the
information exchanged in the signaling plane. If the egress PE router can't handle a pseudowire packet
that contains t... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Support in a EVPN-VPWS routing instance added in Junos OS Release 21.1R1. | [
"Configuring the FAT Flow Label for FEC 128 VPWS Pseudowires for Load-Balancing MPLS Traffic",
"FAT Flow Labels in EVPN-VPWS Routing Instances"
] |
flow-level-bandwidth (DDoS Flow Detection) | flow-level-bandwidth {
logical-interface flow-bandwidth;
physical-interface flow-bandwidth;
subscriber flow-bandwidth;
} | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure allowed flow bandwidth for the packet type at each flow aggregation level.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Maximum Flow Bandwidth at Each Flow Aggregation Level",
"Setting Up and Using Flow Detection"
] |
flow-level-control (DDoS Flow Detection) | flow-level-control {
logical-interface flow-control-mode;
physical-interface flow-control-mode;
subscriber flow-control-mode;
} | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches) Specify
how traffic in the detected flow is handled for the protocol group or packet type at one or more flow
aggregation levels. Use this statement to override global flow control mode settings configured with the
flow-level-con... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring How Traffic in a Culprit Flow Is Controlled at Each Flow Aggregation Level",
"Setting Up and Using Flow Detection"
] |
flow-level-control (DDoS Global Flow Detection) | flow-level-control flow-control-mode; | [edit system ddos-protection global] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches) Specify
how traffic in the detected flow is handled globally for all protocol groups and packet types at all flow
aggregation levels.
To override the global configuration for a protocol group or packet type, use the flow-level-co... | [
{
"name": "flow-control-mode",
"desc": "Mode for how traffic in the detected flow is controlled globally."
},
{
"name": "drop",
"desc": "Drop all traffic in flow."
},
{
"name": "keep",
"desc": "Keep all traffic in flow."
},
{
"name": "police",
"desc": "Police the traffic ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring How Traffic in a Culprit Flow Is Controlled Globally",
"Setting Up and Using Flow Detection",
"Setting Up and Using Flow Detection"
] |
flow-level-detection (DDoS Flow Detection) | flow-level-detection {
logical-interface flow-detection-mode;
physical-interface flow-detection-mode;
subscriber flow-detection-mode;
} | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure the mode of operation for flow detection for the packet type at each flow aggregation level.
The remaining statements are explained separately. See CLI Explorer.
NOTE: Flow detection operates for individual flow aggrega... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring How Flow Detection Operates at Each Flow Aggregation Level",
"Setting Up and Using Flow Detection"
] |
flow-map | flow-map flow-map-name {
bandwidth (bps | adaptive);
forwarding-cache {
timeout (never non-discard-entry-only | minutes);
}
policy [ policy-names ];
redundant-sources [ addresses ];
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Configure multicast flow maps. | [
{
"name": "flow-map-name",
"desc": "Name of the flow-map."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Example: Configuring a Multicast Flow Map"
] |
flow-monitoring (Inline Monitoring Services) | flow-monitoring {
counter-profile profile-identifier;
flow-rate kbps burst-size bytes;
flow-limit number;
sampling-profile profile-name;
sampling-rate bytes;
security-enable;
} | [edit services inline-monitoring template template-name] | Configures optional parameters for flow-based telemetry (FBT) for the EX4100, EX4100-F, and EX4400
switches. FBT enables per-flow-level analytics, using inline monitoring services to create flows, collect
them, and export them to a collector. A flow is a sequence of packets that have the same source IP,
destination IP,... | [
{
"name": "counter-profile",
"desc": ""
},
{
"name": "profile-identifier",
"desc": "Specify which counters should be exported to the collector, by selecting one of the pre-defined profile names. Per_flow_6_counters: packet range counter (3 counters), time-to-live (TTL) range counter, TCP window... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"Flow-Based Telemetry"
] |
flow-monitoring | flow-monitoring {
version9 {
template template-name {
flow-active-timeout seconds;
flow-inactive-timeout seconds;
flow-key {
flow-direction;
vlan-id;
output-interface;
}
(ipv4-template | ipv6-templa... | [edit services] | Specify the active monitoring properties for flow aggregation version 9 or IPFIX.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
data-record-fields option introduced in Junos OS Evolved Release 21.4R1.
multi-bgp-path option added in Junos OS Release 24.2R1.
include-policy-map-name option added in Junos OS Evolved 24.4R1. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices"
] |
flow-profile | flow-profile profile-name | default-profile {
session-sync disabled;
session-sync-min-age seconds;
} | [edit logical-systems name security flow],
[edit logical-systems name tenants name security flow],
[edit security flow],
[edit tenants name security flow] | Configure flow profile for selective session synchronization in a Multinode High Availability (MNHA)
deplyments. | [
{
"name": "name",
"desc": "Name for the flow-profile. This is a user defined profile where you can define selective session synchronization options. You must apply the user-defined profile to a security policy; otherwise the default profile will be applied to the security policy."
},
{
"name": "defa... | [none specified] | Statement introduced in Junos OS Release 25.4R1. | [] |
flow-recover-time (DDoS Flow Detection) | flow-recover-time seconds; | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure how much time must pass before a culprit flow for the packet type is considered to have
returned to normal. The period starts when the flow drops below the threshold that triggered the last
violation. | [
{
"name": "seconds",
"desc": "Period required for the traffic to recover."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Recovery Period for a Culprit Flow",
"Setting Up and Using Flow Detection"
] |
flow-report-rate (DDoS Flow Detection) | flow-report-rate report-rate; | [edit system ddos-protection global] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches) Set the
rate at which culprit flow events are reported by system log messages, for all protocol groups and packet
types on all line cards. | [
{
"name": "report-rate",
"desc": "Number of flows per second. Range: 1 through 50,000 Default: 10"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Culprit Flow Reporting Rate for All Protocol Groups and Packet Types",
"Setting Up and Using Flow Detection"
] |
flow-sample | flow-sample {
ae-parent-index;
} | [edit forwarding-options sflow] | Configure flow sample inputs. | [
{
"name": "ae-parent-",
"desc": ""
},
{
"name": "index",
"desc": "Configure to send aggregated Ethernet parent index to an sFlow datagram. When you configure sFlow, a sampled packet is captured from the traffic stream and the packet details are added to an sFlow datagram. This datagram contains ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.