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 |
|---|---|---|---|---|---|---|---|
features | features {
aggregate-intf-member-id;
chip-delay;
egress-drop-reason;
flow-start-end-time;
ingress-drop-reason;
inter-arrival-time;
inter-departure-time;
queue-congestion-level;
security-enable;
shared-pool-congestion;
} | [edit services inline-monitoring feature-profile] | When you monitor packets, you need to specify what information you want to collect about them. | [
{
"name": "aggregate-intf-member-id",
"desc": "ID for a member of a link aggregation group (LAG) or an equal-cost multipath (ECMP) group."
},
{
"name": "chip-delay",
"desc": "The amount of time the packet takes to transit the ASIC."
},
{
"name": "egress-drop-reason",
"desc": "The rea... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [
"Flow-Based Telemetry"
] |
feb (Assigning a FEB to a Redundancy Group) | feb slot-number (backup | primary); | [edit chassis redundancy feb redundancy-group group-name] | On M120 routers only, configure a Forwarding Engine Board (FEB) as part of a FEB redundancy group. | [
{
"name": "slot-number",
"desc": "Slot number of the FEB. The range of values is from 0 to 5."
},
{
"name": "backup",
"desc": "(Optional) For each redundancy group, you must configure exactly one backup FEB."
},
{
"name": "primary",
"desc": "(Optional) For each redundancy group, you ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring FEB Redundancy on the M120 Router"
] |
feb (chassis) | feb slot slot-number{
pfe {
core name {
channel name {
tunnel-services {
bandwidth(100g | 10g | 1g | 2.5g | 200g | 20g | 300g | 30g | 400g | 40g |
480g | 50g | 60g | 70g | 80g | 90g | bandwidth);
}
}
}
} | [edit chassis] | Configure the Forwarding Engine Board (FEB) slot number. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.1R1 for ACX Series Routers. | [] |
feb (Creating a Redundancy Group) | feb {
redundancy-group group-name {
description description;
feb slot-number (backup | primary);
no-auto-failover;
}
} | [edit chassis redundancy] | On M120 routers only, configure a Forwarding Engine Board (FEB) redundancy group. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring FEB Redundancy on the M120 Router"
] |
fec (ether) | fec(fec108 | fec74 | fec91 | none); | [edit dynamic-profiles name interfaces name ether-options],
[edit dynamic-profiles name logical-systems name interfaces name ether-options],
[edit interfaces name ether-options] | (PTX10001-36MR, PTX10003-8T, PTX10003-16T, PTX10004, PTX10008, QFX5220-32CD, and
QFX5220-128C) Enable or disable RS-FEC (Reed-Solomon Forward Error Correction) for 25, 50, 100,
400-Gigabit Ethernet interface. By default, the Junos OS software enables or disables forward error
correction based on the plugged-in optics. ... | [
{
"name": "fec108",
"desc": "IEEE 802.3by Clause 108, Reed-Solomon FEC (RS-FEC) on 25g links"
},
{
"name": "fec74",
"desc": ""
},
{
"name": "FEC74 enabled",
"desc": ""
},
{
"name": "fec91",
"desc": "IEEE 802.3bj Clause 91, Reed-Solomon FEC (RS-FEC)"
},
{
"name": "... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1 | [] |
fec (gigether) | fec (fec91 | fec74 | none) | [edit interfaces interface-name gigether-options] | Supported on the following:
•
ACX6360-OX Transponders
•
ACX6360 routers
•
MX Series Routers with MPC7E, MPC8E, and MPC9E
•
MX10003 Router with MX10003 MPC
•
MX204 Router
•
PTX1000
•
FPC3-PTX-U2 and FPC3-PTX-U3 on PTX5000
•
QFX series switches
(ACX6360-OX Transponders, ACX6360 routers, MX Series Routers with MPC7E, MPC... | [
{
"name": "fec91",
"desc": "Enables RS-FEC. RS-FEC is compliant with IEEE 802.3-2015 Clause 91."
},
{
"name": "fec74",
"desc": "Enables RS-FEC. RS-FEC is compliant with IEEE 802.3-2015 Clause 74."
},
{
"name": "none",
"desc": "Disables RS-FEC."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1 | [
"Determining Transceiver Support for the PTX1000",
"Understanding the features of ACX6360"
] |
fec (MX Series) | fec ( sdfec | hgfec | sdfec15 | none); | [edit interfaces interface-name optics-options] | Enable forward error correction (FEC) mode.
Default
If you do not specify a mode, the default mode is gfec. On PTX Series routers with P1-PTX-2-100G-
WDM, the default value is gfec-sdfec. On PTX Series routers with PTX-5-100G-WDM and on MX Series
routers with MIC3-100G-DWDM, the default value is sdfec. | [
{
"name": "efec",
"desc": "(M Series, MX Series routers and PTX Series routers only) G.975.1 I.4 enhanced forward error"
},
{
"name": "gfec",
"desc": "(M series, MX Series routers and PTX Series routers only) G.709 generic forward error correction"
},
{
"name": "gfec-sdfec",
"desc": ... | 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.
Statement and gfec-sdfec option introduced in Junos OS Release 13.2 for PTX Series routers. with P1-
PTX-2-100G-WDM PIC.
Options efec, gfec, and ufec introduced in Junos OS Release 13.3 for MX Series routers. with
MPC5E-100G10G, MPC5E-40G10G, MIC6-10G-OTN, and MIC6-100G-CFP... | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM",
"Supported Forward Error Correction Modes on MX Series Routers",
"Supported Forward Error Correction Modes on PTX Series Routers",
"Unders... |
fec (protocols ldp) | fec fec-address {
bfd-liveness-detection {
detection-time threshold milliseconds;
ecmp;
failure-action {
remove-nexthop;
remove-route;
}
holddown-interval milliseconds;
ingress-policy ingress-policy-name;
minimum-interval milliseconds;... | [edit logical-systems logical-systems-name protocols ldp oam],
[edit protocols ldp oam] | Allows you to configure BFD for a specific LDP forwarding equivalence class (FEC). | [
{
"name": "fec-address",
"desc": "Specify the FEC address. The other statements are explained separately."
}
] | 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. | [
"Configuring BFD for LDP LSPs"
] |
fec | fec (efec | gfec | gfec-sdfec |hgfec | sd-fec | ufec | none); | [edit interfaces name ether-options] | Enable forward error correction (FEC) mode.
Default
The default value is gfec. | [
{
"name": "efec",
"desc": "Enhanced forward error correction (EFEC) is configured to detect and correct bit errors. This mode"
},
{
"name": "gfec",
"desc": "Gneric forward error correction (GFEC) mode is configured to detect and correct bit errors."
},
{
"name": "gfec-sdfec",
"desc":... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM",
"Understanding Pre-FEC BER Monitoring and BER Thresholds"
] |
feed-name | feed-name feed-name | [edit services web-filter profile profile-name],
[edit services web-filter profile profile-name dns-filter-template template-name],
[edit services web-filter profile profile-name dns-filter-template template-name term term-name] | Configure the feed name. The feed name can be specified under profile has lesser precedence compared
to the one configured under the template. The feed name configured in term takes higher precedence
than the one configured under the template. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1 | [
"DNS Request Filtering for Disallowed Website Domains"
] |
feed-server | feed-server name {
(hostname hostname | url url);
description description;
feed-name name {
description description;
hold-interval seconds;
path path;
update-interval seconds;
}
hold-interval seconds;
password password;
tls-profile tls-profile;
update-interval seconds;
user-name user-name... | [edit security dynamic-address] | Security dynamic address feed-server | [
{
"name": "name",
"desc": "Security dynamic address feed-server name"
},
{
"name": "hold-interval",
"desc": "Time to keep IP entry when update failed (seconds) Default: 86400 Range: 0 through 4294967295"
},
{
"name": "hold-interval",
"desc": "Time to keep IP entry when update faile... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X46-D25 on SRX Series Firewalls and on cSRX
Container Firewall in Junos OS Release 22.2R1.
Starting with Junos OS Release 25.2R1, you can authenticate dynamic address feed servers before
downloading feeds into the SRX Series devices and vSRX 3.0, using the username and passw... | [] |
feeds (T640, T1600, and T4000 Routers with Six-Input DC Power Supply) | feeds number-of-input-feeds; | [edit chassis pem],
[edit chassis lcc lcc-number pem] | Configure the number of input feeds connected to the six-input DC power supply on T640, T1600, or
T4000 routers. The value assigned to the feeds statement must be equal to the number of input feeds
provided to the power supply.
When providing four or five input feeds on standalone routers, you must configure the feeds ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring the Six-Input DC Power Supply on T Series Routers"
] |
fib-install-priority | fib-install-priority <high/medium/> | [edit policy-options policy-statement policy-name term term-name then] | Assign a FIB install priority, as high or low, for matching routes. Non-matching routes are by default
classified as unprioritized. When the routes are installed in the forwarding table, the number of
forwarding table entries that routes of a particular priority get depends on the memory percentage
allotted for the pri... | [] | •
interface—To view this statement in the configuration.
•
interface-control—To add this statement to the configuration. | Command support introduced in Junos OS Evolved Release 22.4R1 for the PTX Series. | [] |
fib-local | fib-local; | [edit chassis fpc fpc-number route-localization] | Configure the Packet Forwarding Engine on an FPC as FIB-local.
NOTE: At least, one Packet Forwarding Engine must be configured as fib-local for the
commit operation to be successful. If you do not configure fib-local for the Packet
Forwarding Engine, the CLI displays an appropriate error message and the commit fails. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring Packet Forwarding Engine FIB Localization"
] |
fib-next-hop-split | fib-next-hop-split {
labeled-isis;
} | [edit routing-options forwarding-table] | You must configure the fib-next-hop-split statement in conjunction with the "egress-chaining" on page
6484 and "transit" on page 31227 statements to enable route resolution over labeled IS-IS routes using
flattened router next hops. Configuring the fib-next-hop-split statement alone does not have any effect.
When you c... | [
{
"name": "labeled-isis",
"desc": "Create composite-chained next hops for labeled IS-IS routes. In addition to enabling fib-next-hop-split, you can also configure \"egress-chaining\" on page 6484 to reduce the number of chained next hops present in a route that involves resolution over multiple routes with ... | routing | Statement introduced in Junos OS Release 20.4R1. | [] |
fib-prioritization | chassis {
fib-prioritization {
high-priority-memory-percent 0...100
medium-priority-memory-percent 0...100
}
} | [edit chassis] | Configure the memory allocation percent to install high and medium priority routes in the Forwarding
Information Base (FIB) at device level. Reserve a percentage of memory on chassis for high-priority and
medium priority routes, for IPv4, IPv6, and MPLS, BGP, IGP, static, aggregate, generated, and PRPD
routes protocol ... | [
{
"name": "fib-prioritization",
"desc": "FIB prefix prioritization to install high and medium priority routes at chassis-level."
}
] | •
interface—To view this statement in the configuration.
•
interface-control—To add this statement to the configuration. | Command support introduced in Junos OS Evolved Release 22.4R1 for the PTX Series. | [] |
fib-remote | fib-remote; | [edit chassis fpc fpc-number route-localization] | Configure the Packet Forwarding Engine on an FPC as FIB-remote. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring Packet Forwarding Engine FIB Localization"
] |
fibre-channel (Alarm) | fibre-channel {
link-down (red | yellow | ignore);
} | [edit chassis alarm],
[edit chassis interconnect-device name alarm],
[edit chassis node-group name alarm] | Configure alarms for a Fibre Channel interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [] |
fibre-channel (Family Interfaces) | fibre-channel {
port-mode (f-port | np-port);
} | [edit interfaces vlan unit logical-unit-number family],
[edit interfaces interface-name unit logical-unit-number family] | Configure the port mode for FCoE VLAN interfaces and native FC interfaces. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric",
"Configuring an FCoE VLAN Interface on an FCoE-FC Gateway",
"Converting an Ethernet Interface To a Fibre Channel Interface",
"show vlans",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
fibre-channel (Port) | fibre-channel {
port-range {
port-range-low port-range-high;
}
} | [edit chassis fpc fpc-id pic pic-id] | Specify a range of ports to carry FC traffic when the switch is configured as an FCoE-FC gateway. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric",
"Configuring a Physical Fibre Channel Interface",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
fibrechannel-options | fibrechannel-options {
bb-sc-n
(loopback | no-loopback);
speed (auto-negotiation | 2g | 4g | 8g);
} | [edit interfaces interface-name] | Configure FC interface properties such as speed and loopback mode. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Converting an Ethernet Interface To a Fibre Channel Interface"
] |
fields (Flat-File Accounting Options) | 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-packets;
total-drop-packets;
}
general-param {
all-field... | [edit accounting-options flat-file-profile profile-name] | Specify the accounting statistics and the nonstatistical information to be collected for an interface and
recorded in the accounting flat file created by the profile. | [
{
"name": "all-fields",
"desc": "Include all available statistical fields in the accounting file. Many fields are available for both logical interfaces and physical interfaces, but some fields are available only for one or the other interface type."
},
{
"name": "service-accounting",
"desc": "In... | 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. | [
"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"
] |
fields (for Interface Profiles) | fields {
field-name;
} | [edit accounting-options interface-profile profile-name] | Statistics to collect in an accounting-data log file for an interface. | [
{
"name": "field-name",
"desc": "Name of the field:"
},
{
"name": "input-bytes",
"desc": "Input bytes"
},
{
"name": "input-errors",
"desc": "Generic input error packets"
},
{
"name": "input-multicast",
"desc": "Input packets arriving by multicast"
},
{
"name": "in... | 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. | [
"Configuring the Interface Profile"
] |
fields (for Routing Engine Profiles) | fields {
field-name;
} | [edit accounting-options routing-engine-profile profile-name] | Statistics to collect in an accounting-data log file for a Routing Engine. | [
{
"name": "field-name",
"desc": "Name of the field:"
},
{
"name": "cpu-load-1",
"desc": "Average system load over the last 1 minute"
},
{
"name": "cpu-load-5",
"desc": "Average system load over the last 5 minutes"
},
{
"name": "cpu-load-15",
"desc": "Average system load o... | 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. | [
"Configuring the Routing Engine Profile"
] |
file (Analytics) | file filename {
files number-of-files;
size size;
} | [edit services analytics collector local]
[edit services analytics queue-statistics]
[edit services analytics traffic-statistics] | 13.2X51-D15
In Junos OS Release 13.2X51-D15 or later, you configure a single filename to store both queue and
traffic monitoring statistics.
13.2X51-D10
In Junos OS Release 13.2X51-D10 and earlier, you configure separate files for storing monitoring
data, one for queue statistics, and another for traffic statistics. | [
{
"name": "filename",
"desc": "Specify a filename for storing queue and traffic monitoring statistics in the Comma-separated Values (CSV) format. The file is stored in the /var/log/ directory of your device. If you do not specify a filename, the data is not stored in a file. NOTE: In Junos OS Release 13.2X5... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Network Analytics Overview"
] |
file (App Engine Virtual Machine Management Service) | file {filename <files number> | match | no-world-readable | size size | world-readable
} | [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": "filename",
"desc": "Name of the file in which the trace information is stored. By default, the file is created in the /var/log directory."
},
{
"name": "files",
"desc": ""
},
{
"name": "number",
"desc": "(Optional) Maximum number of trace files. When a trace file reaches t... | system-control | Statement introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] |
file (Associating with a Profile) | file filename; | [edit accounting-options class-usage-profile profile-name],
[edit accounting-options filter-profile profile-name],
[edit accounting-options interface-profile profile-name],
[edit accounting-options mib-profile profile-name],
[edit accounting-options routing-engine-profile profile-name] | Specify the accounting log file associated with the profile. | [
{
"name": "filename",
"desc": "Name of the log file. You must specify a filename already configured in the file statement at"
}
] | 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.
The [edit accounting-options mib-profile profile-name] hierarchy added in Junos OS Release 8.2. | [
"Configuring the Interface Profile",
"Configuring the Filter Profile",
"Configuring the MIB Profile",
"Configuring the Routing Engine Profile"
] |
file (Commit Scripts) | file filename {
allow-transients;
cert-file path;
checksum hash-algorithm hash-value;
optional;
refresh;
refresh-from url;
routing-instance routing-instance-name;
source url;
} | [edit system scripts commit] | Enable a Junos OS commit script that is located in the /var/db/scripts/commit directory on the hard
disk or the /config/scripts/commit directory on the flash drive. During a commit operation, enabled
commit scripts are executed in the order specified in the configuration. | [
{
"name": "filename",
"desc": "Name of a Python, Extensible Stylesheet Language Transformations (XSLT), or Stylesheet Language Alternative syntaX (SLAX) file containing a commit script."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Storing and Enabling Scripts",
"Controlling Execution of Commit Scripts During Commit Operations"
] |
file (Configuring a Log File) | file filename {
archive-sites {
site-name;
}
backup-on-failure (master-and-slave | master-only);
compress;
files number;
nonpersistent;
push-backup-to-master;
size bytes;
start-time time;
transfer-interval minutes;
} | [edit accounting-options] | Specify a log file to be used for accounting data. | [
{
"name": "filename",
"desc": "Name of the file in which to write accounting data."
}
] | 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. | [
"Configuring Accounting-Data Log Files",
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
file (Event Scripts) | file filename {
cert-file path;
checksum hash-algorithm hash-value;
dampen {
dampen-options {
cpu-factor cpu-factor;
line-interval line-interval;
time-interval time-interval;
}
}
python-script-user username;
refresh;
refresh-from url;
... | [edit event-options event-script] | Enable a Junos OS event script that is located in the /var/db/scripts/event directory on the hard disk or
the /config/scripts/event directory on the flash drive. After enabling an event script, an event policy can
execute the event script when triggered. | [
{
"name": "filename",
"desc": "Name of a Python, Extensible Stylesheet Language Transformations (XSLT), or Stylesheet Language Alternative syntaX (SLAX) file containing an event script."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Store and Enable Junos Automation Scripts",
"Enable and Execute Event Scripts"
] |
file (Extended DHCP Relay Agent and Helpers Trace Options) | file filename <files number> <match regular-expression> <size bytes> <world-readable | no-world-
readable>; | [edit forwarding-options dhcp-relay traceoptions],
[edit forwarding-options helpers 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": "filename",
"desc": "Name of the file containing the trace information."
}
] | 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. | [
"Tracing BOOTP, DNS, and TFTP Forwarding Operations"
] |
file (Flat-File Accounting Options) | file filename; | [edit accounting-options flat-file-profile profile-name] | Specify the name of the accounting file created by a flat-file profile. By default, the filename becomes
the name of the local directory where the accounting file is backed up: /var/log/pfedBackup/filename. | [
{
"name": "filename",
"desc": "Name of the accounting file. The complete output filename is in the format filename.hostname.file-number_timestamp.gz."
}
] | 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. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
file (JET) | file filename {
arguments arguments;
cert-file path;
checksum hash-algorithm hash-value;
daemonize;
interpreter (bash | python | python3);
optional;
refresh;
refresh-from;
respawn-on-normal-exit;
routing-instance;
source;
start {
start-options {
mem-f... | [edit system extensions extension-service application] | 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": "arguments",
"desc": ""
},
{
"name": "arguments",
"desc": "Specify the command-line arguments called by a JET application. A program can take any number of command-line arguments. Enter the arguments in the way the application expects. Developer must supply this information."
},
{
... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1.
refresh, refresh-from, respawn-on-normal-exit, routing-instance, and source options added in Junos OS Release
18.1R1.
interpreter option added in Junos OS Evolved Release 20.3R1.
optional option added in Junos OS and Junos OS Evolved Release 23.2R1. | [] |
file (Next Gen Services Global System Logging) | file <filename> <files files> <match match> <size size> <(world-readable | no-world-readable)>; | [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": "filename",
"desc": "Name of file in which to write trace information"
},
{
"name": "files",
"desc": "Maximum number of trace files Default: 3 Range: 2 through 1000"
},
{
"name": "match",
"desc": "Regular expression for lines to be logged"
},
{
"name": "no-world-r... | 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"
] |
file (Op Scripts) | file filename {
allow-commands “regular-expression”;
arguments {
argument-name {
description descriptive-text;
}
}
cert-file path;
checksum hash-algorithm hash-value;
command filename-alias;
dampen {
dampen-options {
cpu-factor cpu-factor;
... | [edit system scripts op] | Enable a Junos OS op script that is located in the /var/db/scripts/op directory on the hard disk or the /
config/scripts/op directory on the flash drive. After enabling an op script, you can execute the script
from the CLI using the op command. | [
{
"name": "filename",
"desc": "Name of a Python, Extensible Stylesheet Language Transformations (XSLT), or Stylesheet Language Alternative syntaX (SLAX) file containing an op script."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Storing and Enabling Scripts",
"Enabling an Op Script and Defining a Script Alias"
] |
file (Packet Forwarding Engine Traffic Traceoptions) | file < filename> <files files> <match match> <size size> <(world-readable | no-world-readable)>; | [edit services pfe traffic 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": "filename",
"desc": "Name of the file containing the trace information."
},
{
"name": "files",
"desc": "Maximum number of trace files. Default: 3 Range: 2 through 1000"
},
{
"name": "match",
"desc": "Regular expression for lines to be logged."
},
{
"name": "no-wor... | interface—To view this statement in the configuration.
interface-control—To view this statement in the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
file (QFabric System) | file filename {
archive {
size maximum-file-size;
}
explicit-priority;
facility severity;
match "regular-expression";
structured-data {
brief;
}
} | [edit system syslog] | Configure the logging of system messages to a file. | [
{
"name": "facility",
"desc": "Class of messages to log. To specify multiple classes, include multiple facility severity statements."
},
{
"name": "filename",
"desc": "Filename that you specify with the show log command. Default: Filename messages"
},
{
"name": "severity",
"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.3. | [] |
file (Sampling) | file {
disable;
filename filename;
files number;
size bytes;
(stamp | no-stamp);
(world-readable | no-world-readable);
} | [edit forwarding-options sampling family inet output] | Collect the traffic samples in a file.
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. | [
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Collecting Traffic Sampling Output in a File"
] |
file (Security Certificates) | file certificate-filename; | [edit security certificates certification-authority ca-profile-name] | (Encryption interface on M Series and T Series routers and EX Series switches only) Specify the file from
which to read the digital certificate. | [
{
"name": "certificate-filename",
"desc": "File from which to read the digital certificate."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Specifying a File to Read the Digital Certificate"
] |
file (Security Log) | file {
files max-file-number;
name file-name;
path binary-log-file-path;
size maximum-file-size;
} | [edit security log]
[edit logical-systems name security log]
[edit tenants tenant-name security log]
[edit security log mode event]
[edit security log mode stream]
[edit security log mode stream-event] | Configure security log file options for logs in binary format. | [
{
"name": "files number",
"desc": "Specify the maximum number of binary log files."
},
{
"name": "name name",
"desc": "Name of the file to log messages."
},
{
"name": "path filepath",
"desc": "Specify the path of the binary log file."
},
{
"name": "size maximum-file-size",
... | 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.
The [edit logical-systems name security log] and [edit tenants tenant-name security log] hierarchy levels
introduced in Junos OS Release 19.1R1. | [] |
file (SNMP Scripts) | file filename {
cert-file path;
checksum hash-algorithm hash-value;
oid id {
priority;
}
python-script-user username;
refresh;
refresh-from;
routing-instance routing-instance-name;
source;
start {
start-options {
mem-factor percentage;
}
}
... | [edit system scripts snmp] | For Junos OS SNMP scripts, enable an SNMP script that is located in the /var/db/scripts/snmp
directory. If the load-scripts-from-flash option is configured, the system reads SNMP scripts from the /
config/scripts/snmp directory instead. | [
{
"name": "filename",
"desc": "Name of an Python, Extensible Stylesheet Language Transformations (XSLT), or Stylesheet Language Alternative syntaX (SLAX) file containing an SNMP script."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
file (System Logging) | file filename {
facility severity;
allow-duplicates;
archive {
archive-sites {
url <password password>;
}
(binary-data | no-binary-data);
files number;
size size;
start-time;
transfer-interval;
(no-world-readable | world-readable);... | [edit system syslog] | Configure the logging of system messages to a file.
Starting in Junos OS Release 20.3R1, the change-log is a default option at [edit system syslog file name]
hierarchy for SRX Series Firewalls. As the default option, change-log records all the configuration changes.
In Junos OS releases earlier than 20.2R1, you need to... | [
{
"name": "facility",
"desc": "Class of messages to log. To specify multiple classes, include multiple facility severity"
},
{
"name": "severity",
"desc": "Severity of the messages that belong to the facility specified by the paired facility name."
},
{
"name": "file filename",
"desc... | 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. | [
"Directing System Log Messages to a Log File",
"SRX Firewall Users"
] |
file (Trace Options) | file filename {
files number;
size bytes;
world-readable | no-world-readable>;
} | [edit forwarding-options port-mirroring traceoptions],
[edit forwarding-options sampling 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": "filename",
"desc": "Name of the file containing the trace information."
}
] | 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. | [
"Tracing Traffic Sampling Operations",
"Tracing Traffic-Sampling Operations"
] |
file (Tracing for Origin AS Validation) | file filename <files number> <size size> <world-readable | no-world-readable>; | [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": "filename",
"desc": "Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log."
},
{
"name": "files",
"desc": ""
},
{
"name": "number",
"desc": "(Optional) Maximum number of trac... | 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. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
file archive | file archive destination destination source source
<compress>
<exclude> filepattern
<routing-instance>
<source-address> | Archive, and optionally compress, one or multiple local system files as a single file, locally or at a remote
location.
For information on valid filename and URL formats, see Format for Specifying Filenames and URLs in
Junos OS CLI Commands. | [
{
"name": "destination destination",
"desc": "Destination of the archived file or files. Specify the destination as a URL or filename. The Junos OS adds one of the following suffixes if the destination filename does not already have it:"
},
{
"name": "For archived files",
"desc": "The suffix .ta... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file archive (Multiple Files)
The following sample command archives all messages files in the local directory /var/log/ as the single
file messages-archive.tar.
user@host> file archive source /... | Command introduced before Junos OS Release 7.4.
exclude option added in Junos OS Release 20.3R1 and Junos OS Evolved Release 20.3R1.
routing-instance option added in Junos OS Release 18.4R1.
source-address option added in Junos OS Release 18.4R1. | [
"Format for Specifying Filenames and URLs in Junos OS CLI Commands"
] | |
file change-owner | file change-owner filename
<user user>
<group group>
<to to>
<recurse> | Change the ownership of a file to a specified user, group or both. | [
{
"name": "filename",
"desc": "Filename to change owner."
},
{
"name": "user",
"desc": "New owner of the file."
},
{
"name": "group",
"desc": "New group of the file."
},
{
"name": "to",
"desc": "New owner:group of the file."
},
{
"name": "recurse",
"desc": "Op... | maintenance
Sample Output
file change-owner (user)
The following sample command changes the owner of /var/tmp/config.txt to labuser. The group remains
unchanged.
user@host> file change-owner user labuser /var/tmp/config.txt
file change-owner (group)
The following sample command changes the group of /var/tmp/config.txt ... | Command introduced before Junos OS Release 7.4. | [] | |
file change-permission | file change-permission filename filename permission permission | Change permission of file. | [
{
"name": "filename",
"desc": "Filename to change mode."
},
{
"name": "permission",
"desc": "File permission, either as symbolic (go+rw) or octal (642)."
}
] | maintenance
Sample Output
file change-permission (Octal Mode)
The following sample command makes a file readable by anyone and writable by the owner only.
user@host> file change-permission /tmp/foo.txt permission 644
file change-permission (Symbolic Mode)
The following sample command makes a file readable or executabl... | Command introduced before Junos OS Release 7.4. | [] | |
file checksum md5 | file checksum md5 <pathname> filename | Calculate the Message Digest 5 (MD5) checksum of a file.
NOTE:
Junos OS uses the md5 command to calculate file checksums while Junos OS Evolved uses
the md5sum command instead. This difference in tools might cause variations in output
format and usage. Make sure to consider these differences when verifying file integri... | [
{
"name": "pathname",
"desc": "(Optional) Path to a filename."
},
{
"name": "filename",
"desc": "Name of a local file for which to calculate the MD5 checksum."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file checksum md5
user@host> file checksum md5 jbundle-5.3R2.4-export-signed.tgz
MD5 (jbundle-5.3R2.4-export-signed.tgz) = $ABC123 | Command introduced before Junos OS Release 7.4. | [
"Configuring Checksum Hashes for a Commit Script",
"Configuring Checksum Hashes for an Event Script",
"Configuring Checksum Hashes for an Op Script",
"Configuring Checksum Hashes for an SNMP Script",
"Executing an Op Script from a Remote Site"
] | |
file checksum sha1 | file checksum sha1 <pathname> filename | Calculate the Secure Hash Algorithm (SHA-1) checksum of a file. | [
{
"name": "pathname",
"desc": "(Optional) Path to a filename."
},
{
"name": "filename",
"desc": "Name of a local file for which to calculate the SHA-1 checksum."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file checksum sha1
user@host> file checksum sha1 /var/db/scripts/opscript.slax
SHA1 (/var/db/scripts/commitscript.slax) = $ABC123 | Command introduced in Junos OS Release 9.5. | [
"Configuring Checksum Hashes for a Commit Script",
"Configuring Checksum Hashes for an Event Script",
"Configuring Checksum Hashes for an Op Script",
"Configuring Checksum Hashes for an SNMP Script",
"Executing an Op Script from a Remote Site"
] | |
file checksum sha-256 | file checksum sha-256 <pathname> filename | Calculate the Secure Hash Algorithm 2 family (SHA-256) checksum of a file. | [
{
"name": "pathname",
"desc": "(Optional) Path to a filename."
},
{
"name": "filename",
"desc": "Name of a local file for which to calculate the SHA-256 checksum."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file checksum sha-256
user@host> file checksum sha-256 /var/db/scripts/commitscript.slax
SHA256 (/var/db/scripts/commitscript.slax) =$ABC123 | Command introduced in Junos OS Release 9.5. | [
"Configuring Checksum Hashes for a Commit Script",
"Configuring Checksum Hashes for an Event Script",
"Configuring Checksum Hashes for an Op Script",
"Configuring Checksum Hashes for an SNMP Script",
"Executing an Op Script from a Remote Site"
] | |
file compare | file compare (files filename filename)
<context | unified>
<ignore-white-space> | Compare two local files and describe the differences between them in default, context, or unified output
styles:
•
Default—In the first line of output, c means lines were changed between the two files, d means lines
were deleted between the two files, and a means lines were added between the two files. The
numbers prec... | [
{
"name": "files filename",
"desc": "Names of two local files to compare."
},
{
"name": "context",
"desc": "(Optional) Display output in context format."
},
{
"name": "ignore-white-space",
"desc": "(Optional) Ignore changes in the amount of white space."
},
{
"name": "unified... | none
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file compare files
user@host> file compare files /tmp/one /tmp/two
100c100
< full-name "File 1";
---
> full-name "File 2";
102c102
< class foo; # 'foo' is not define... | Command introduced before Junos OS Release 7.4. | [
"Format for Specifying Filenames and URLs in Junos OS CLI Commands",
"Viewing Core Files from Junos OS Processes"
] | |
file compress | file compress file file | Compress file. | [
{
"name": "file",
"desc": "File to compress."
}
] | maintenance
Sample Output
file compress
The following sample command creates a .gz file in the same directory.
user@host> file compress file /tmp/foo.txt | Command introduced before Junos OS Release 7.4. | [] | |
file copy | file copy source destination
<no-check-certificate>
<routing-instance routing-instance-name>
<source-address source-address>
<staging-directory directory-location> | Copy files from one location to another location on the local device or to or from a location on a remote
device reachable by the local device.
The source and destination can specify local paths and FTP, HTTP, HTTPS, and SCP URLs. For
information about valid filename and URL formats, see Format for Specifying Filenames... | [
{
"name": "source",
"desc": "Specify the source URL."
},
{
"name": "destination",
"desc": "Specify the destination URL."
},
{
"name": "no-check-certificate",
"desc": "Bypass certificate validity checks when downloading a file from an HTTPS URL. We recommend that you use this option o... | maintenance
Sample Output
Following are some file copy examples.
Copy a File from the Local Device to a Personal Computer
user@host> file copy /var/tmp/rpd.core.4 mypc:/c/junipero/tmp
...transferring.file...... | 0 KB | 0.3 kB/s | ETA: 00:00:00 | 100%
Copy a Configuration File between Routing Engines
The fol... | Command introduced before Junos OS Release 7.4.
source-address option added in Junos OS Release 7.4.
staging-directory option added in Junos OS Release 17.3R1.
no-check-certificate option added in Junos OS Evolved Release 23.1R1.
no-stage option added in Junos OS Release 24.2R1. | [
"Format for Specifying Filenames and URLs in Junos OS CLI Commands",
"Default Directories for Junos OS File Storage on the Network Device"
] | |
file delete | file delete filename
<purge> | Delete a file on the local router or switch. | [
{
"name": "filename",
"desc": "Name of the file to delete. For a routing matrix, include chassis information in the filename if the file to be deleted is not local to the Routing Engine from which the command is issued."
},
{
"name": "purge",
"desc": "(Optional) Overwrite regular files before de... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file delete
user@host> file list /var/tmp
dcd.core
rpd.core
snmpd.core
user@host> file delete /var/tmp/snmpd.core
user@host> file list /var/tmp
dcd.core
rpd.core
file delete (Routing Matrix)
use... | Command introduced before Junos OS Release 7.4. | [] | |
file link | file link source source destination destination
<symbolic-link> | Create link between files. | [
{
"name": "source",
"desc": "Source file name."
},
{
"name": "destination",
"desc": "Destination link name."
},
{
"name": "symbolic-link",
"desc": "Create a symbolic link."
}
] | maintenance
Sample Output
file link
The following sample command creates hard or symbolic links between files.
user@host> file link symbolic-link source /tmp/foo.txt destination /tmp/foo-link.txt | Command introduced before Junos OS Release 7.4. | [] | |
file list | file list <detail | recursive> <path> | Display a list of files on the local router or switch. | [
{
"name": "none",
"desc": "Display a list of files in the default directory. The default directory is the home directory of the user logged in to the router or switch."
},
{
"name": "detail",
"desc": "(Optional) Display detailed information about the files. The output is similar to what is displ... | maintenance
Sample Output
file list
The following command lists the contents of the /var/tmp directory.
user@host> file list /var/tmp
/var/tmp:
trace_debug
package.log
pics/
downloads/
file list (detailed)
The following command lists detailed information about the contents of the /var/tmp directory.
user@host> file li... | Command introduced before Junos OS Release 7.4. | [] | |
file rename | file rename source destination | Rename a file on the local router or switch. | [
{
"name": "destination",
"desc": "New name for the file."
},
{
"name": "source",
"desc": "Original name of the file. For a routing matrix, the filename must include the chassis information."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file rename
The following example lists the files in /var/tmp, renames one of the files, and then displays the list of
files again to reveal the newly named file.
user@host> file list /var/tmp ... | Command introduced before Junos OS Release 7.4. | [] | |
file show | file show filename
<encoding (base64 | raw)> | Display the contents of a file. | [
{
"name": "filename",
"desc": "Name of a file. For a routing matrix, the file name must include the chassis information."
},
{
"name": "encoding (base64 |",
"desc": ""
},
{
"name": "raw)",
"desc": "(Optional) Encode file contents with base64 encoding or show raw text."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
file show
user@host> file show /var/log/messages
Apr 13 21:00:08 dev1 /kernel: so-1/1/2: loopback suspected; going to standby.
Apr 13 21:00:40 dev1 /kernel: so-1/1/2: loopback suspected; going t... | Command introduced before Junos OS Release 7.4. | [] | |
file | file <filename> <files files> <match match> <size size> <(world-readable | no-world-readable)>; | [edit security dynamic-vpn traceoptions (Security Dynamic VPN)] | 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": "filename",
"desc": "Name of file in which to write trace information"
},
{
"name": "files",
"desc": "Maximum number of trace files Default: 3 Range: 2 through 1000"
},
{
"name": "match",
"desc": "Regular expression for lines to be logged"
},
{
"name": "no-world-r... | trace | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Dynamic VPN Overview"
] |
file | file <archive | change-owner | change-permission | checksum | compare | compress | copy | delete |
delete-directory | link | list | make-directory | routing-instance | rename | show | staging-
directory directory-location>
<source-address source-address> | Archive files from the device, copy files to and from the router or switch, calculate the file checksum,
compare files, delete a file from the device, list files on the device, rename a file, show file contents, or
show the local address to initiate a connection. | [
{
"name": "archive (Optional)",
"desc": "Archive, and optionally compress, one or multiple local system files as a single file, locally or at a remote location."
},
{
"name": "change-owner (Optional)",
"desc": "Change owner of file."
},
{
"name": "change-permission",
"desc": ""
},
... | maintenance | Command introduced before Junos OS Release 7.4. | [
"Viewing Files and Directories on a Juniper Networks Device"
] | |
file-dump-on-wrap (clksyncd) | file-dump-on-wrap; | [edit logical-systems name protocols clock-synchronization memory-logging clksyncd],
[edit protocols clock-synchronization memory-logging clksyncd] | Enable or disable dump-on-wrap for clksyncd process. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
file-serialization | (file-serialization | no-file-serialization); | [edit security policies],
[edit services policies] | Perform policy changes propagation to the dataplane using file serialization. By serializing policy
configurations into files, the system ensure that they are read and applied by the PFE in a controlled and
reliable manner.
By default, the file-based serialization feature is enabled. You can disable the file-serializat... | [] | security—To view this statement in the configuration
security-control—To add this statement to the configuration | Statement introduced in Junos OS Release 24.4R1 | [] |
file-specification (File Format) | file-specification {
variant variant-number {
data-format format;
name-format format;
transfer {
record-level number;
timeout seconds;
}
}
} | [edit services flow-collector] | Configure the file format for the flow collection files.
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. | [
"Configuring File Formats"
] |
file-specification (Interface Mapping) | file-specification {
variant variant-number;
} | [edit services flow-collector interface-map] | Configure the default file specification for interface mapping. | [
{
"name": "variant-number",
"desc": "Default file format variant."
}
] | 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. | [] |
file-type | file-type {
values [ values ];
} | [edit security idp (Security) dynamic-attack-group name filters] | File type the attack is valid for. | [
{
"name": "values",
"desc": "Values for file-type field."
}
] | security | Statement introduced in Junos OS Release 18.2R1. | [] |
filename (Next Gen Services Global System Logging) | filename; | [edit services rtlog traceoptions file] | 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": "filename",
"desc": "Name of file in which to write trace information"
}
] | 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"
] |
filename (Sampling) | filename filename; | [edit forwarding-options sampling family family-name output file] | Configure the name of the output file. | [
{
"name": "filename",
"desc": "Name of the file in which to place the traffic samples. All files are placed in the directory /var/"
}
] | 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. | [
"Collecting Traffic Sampling Output in a File"
] |
filename | filename filename; | [edit forwarding-options sampling family (inet |inet6 |mpls) output file] | Configure the name of the output file. | [
{
"name": "filename",
"desc": "Name of the file in which to place the traffic samples. All files are placed in the directory /var/"
}
] | 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. | [
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
filename-extension | filename-extension object-name {
value [value];
} | [edit security utm default-configuration]
[edit security utm custom-objects] | When scanning content, you can use a file extension list to define a set of file extensions that are used
in file extension scan mode (scan-by-extension). | [
{
"name": "object-name",
"desc": "Name of the extension-list object."
},
{
"name": "value value",
"desc": "Value of the extension-list object. You can configure multiple values separated by spaces"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
filename-prefix | filename-prefix prefix; | [edit services flow-collector transfer-log-archive] | Configure the filename prefix for log files. | [
{
"name": "prefix",
"desc": "Filename identifier."
}
] | 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. | [
"Configuring Transfer Logs"
] |
files (accounting) | files number; | [edit accounting-options file filename] | Specify the maximum number of log files to be used for accounting data. | [
{
"name": "number",
"desc": "The maximum number of files. When a log file (for example, profilelog) reaches its maximum size,"
}
] | 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. | [
"Configuring Accounting-Data Log Files"
] |
files (Next Gen Services Global System Logging) | files files; | [edit services rtlog traceoptions file filename] | 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": "files",
"desc": "Maximum number of trace files Default: 3 Range: 2 through 1000"
}
] | 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"
] |
files (Sampling and Traceoptions) | files number; | [edit forwarding-options helperstraceoptions file],
[edit forwarding-options port-mirroring traceoptions file],
[edit forwarding-options sampling family family-name output file],
[edit forwarding-options sampling traceoptions file] | 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": "number",
"desc": "Maximum number of traffic sampling or trace log files. When a file named sampling-file"
}
] | 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. | [
"Collecting Traffic Sampling Output in a File",
"Tracing Traffic-Sampling Operations"
] |
files (syslog) | files number; | [edit system syslog archive],
[edit system syslog file filename archive] | Configure the maximum number of archived log files to retain. When the Junos OS logging utility has
written a defined maximum amount of data to a log file logfile, it closes the file, compresses it, and
renames it to logfile.0.gz (for information about the maximum file size, see "size" on page 29095). The
utility then ... | [
{
"name": "number",
"desc": "Maximum number of archived files."
}
] | 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. | [] |
files | files number; | [edit forwarding-options port-mirroring traceoptions file],
[edit forwarding-options sampling family (inet |inet6 |mpls) output file],
[edit forwarding-options sampling traceoptions file] | 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": "number",
"desc": "Maximum number of traffic sampling or trace log files. When a file named sampling-file reaches its"
}
] | 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. | [
"Configuring Port Mirroring on M, T MX, ACX, and PTX Series Routers",
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
fill-level (Drop Profiles) | fill-level percentage; | [edit class-of-service drop-profiles profile-name] | When configuring RED, map the fullness of a queue to a drop probability. | [
{
"name": "percentage",
"desc": "How full the queue is, expressed as a percentage. You configure the fill-level and drop-probability statements in pairs. To specify multiple fill levels, include multiple fill-level and drop-probability statements. The values you assign to each statement pair must increase r... | 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. | [
"Managing Congestion Using RED Drop Profiles and Packet Loss Priorities",
"Defining Packet Drop Behavior by Configuring RED Drop Profiles"
] |
fill-level (Interpolated Value) | fill-level [values]; | [edit class-of-service drop-profiles profile-name interpolate] | Define up to 64 values for interpolating queue fill level. | [
{
"name": "values",
"desc": "Data points for mapping queue fill percentage."
}
] | 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. | [
"Managing Congestion Using RED Drop Profiles and Packet Loss Priorities",
"Defining Packet Drop Behavior by Configuring RED Drop Profiles"
] |
fill-level | [edit class-of-service drop-profiles profile-name interpolate] | When configuring weighted random early detection (WRED), map the fullness of a queue to a packet
"drop-probability" on page 6235 value. You configure the fill-level and drop-probability statements in
related pairs. The pairs of fill level and drop probability values set a probability of dropping packets at a
specified ... | [
{
"name": "low-value (switches that support only two fill level/drop probability pairs)",
"desc": "Fullness of the queue before"
},
{
"name": "high-value (switches that support only two fill level/drop probability pairs)",
"desc": "Fullness of the queue before"
},
{
"name": "level1 level... | 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. | [] | |
filter (Applying to a Logical Interface) | filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
} | Protocol-independent firewall filter on MX Series router logical interface:
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
All other standard firewall filters on all other devices:
[edit interfaces interface-name u... | Apply a stateless firewall filter to a logical interface at a specific protocol level. | [
{
"name": "group filter-group-number",
"desc": "(Only Ex, M, MX, and T Series) Number of the group to which the interface"
},
{
"name": "belongs. Range: 1 through 255",
"desc": ""
},
{
"name": "input filter-name",
"desc": "Name of one filter to evaluate when packets are received on t... | 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. | [
"Guidelines for Configuring Firewall Filters",
"Guidelines for Applying Standard Firewall Filters"
] |
filter (Applying to an Interface) | filter {
input filter-name;
output filter-name;
} | [edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family] | Apply a filter to an interface. You can also use filters for encrypted traffic. When you configure filters,
you can configure the family inet, inet6, mpls, or vpls only.
NOTE: MPLS firewall filters applied on output interface are not supported on PTX10003
router due to product limitation. | [
{
"name": "input filter-name",
"desc": "Name of one filter to evaluate when packets are received on the interface."
},
{
"name": "output filter-name",
"desc": "Name of one filter to evaluate when packets are transmitted on the interface."
}
] | 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. | [
"Configuring and Applying Tricolor Marking Policers",
"Example: Classifying Packets Based on Their Destination Address",
"Example: Configuring and Verifying a Complex Multifield Filter",
"Example: Writing Different DSCP and EXP Values in MPLS-Tagged IP Packets",
"Configuring a Simple Filter",
"Configuring... |
filter (Configuring) | filter filter-name {
accounting-profile name;
enhanced-mode;
fast-lookup-filter;
filter-list-template;
interface-shared;
interface-specific;
physical-interface-filter;
promote gre-key;
term term-name {
... term configuration ...
}
} | [edit firewall family family-name],
[edit logical-systems logical-system-name firewall family family-name] | Configure firewall filters. | [
{
"name": "filter-name",
"desc": "Name that identifies the filter. This must be a non-reserved string of not more than 64"
}
] | firewall—To view this statement in the configuration.
firewall-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.
physical-interface-filter statement introduced in Junos OS Release 9.6.
Support for the interface-shared statement introduced in Junos OS Release 12.2. | [
"Guidelines for Configuring Firewall Filters",
"Guidelines for Applying Standard Firewall Filters",
"Configuring Multifield Classifiers",
"Using Multifield Classifiers to Set Packet Loss Priority",
"simple-filter"
] |
filter (Dynamic Interface Unit) | filter {
input filter-name (
shared-name filter-shared-name;
}
output filter-name {
shared-name filter-shared-name;
}
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number],
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number] | Apply a dynamic filter to an interface, regardless of its family type. | [
{
"name": "input filter-name",
"desc": "Name of one filter to evaluate when packets are received on the interface."
},
{
"name": "output filter-name",
"desc": "Name of one filter to evaluate when packets are transmitted on the interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Guidelines for Configuring Firewall Filters",
"Understanding Dynamic Firewall Filters",
"Classic Filters Overview",
"Basic Classic Filter Syntax",
"Dynamically Attaching Statically Created Filters for Any Interface Type"
] |
filter (Dynamic Profiles Filter Attachment) | filter {
adf {
counter;
input-precedence precedence;
not-mandatory;
output-precedence precedence;
rule rule-value;
}
input filter-name {
precedence precedence;
shared-name filter-shared-name;
}
output filter-name {
precedence precedenc... | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family],
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family],
[edit dynamic-profiles profile-name interfaces pp0 unit “$junos–interface–unit” family family] | Apply a dynamic filter to an interface. You can configure filters for family any ,family inet, or family inet6.
The filters can be classic filters, fast update filters, or (for the adf statement) Ascend-Data-Filters. | [
{
"name": "input filter-name",
"desc": "Name of one filter to evaluate when packets are received on the interface."
},
{
"name": "output filter-name",
"desc": "Name of one filter to evaluate when packets are transmitted on the interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support at the [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family family]
hierarchy level introduced in Junos OS Release 10.1.
shared-name statement added in Junos OS Release 12.2. | [
"Junos OS Routing Policies, Firewall Filters and Traffic Policers User Guide for Routing Devices",
"Firewall Filters Overview",
"Understanding Dynamic Firewall Filters",
"Classic Filters Overview",
"Basic Classic Filter Syntax",
"Parameterized Filters Overview"
] |
filter (Dynamic Profiles Filter Creation) | filter filter-name {
enhanced-mode-override;
instance-shared;
interface-shared;
interface-specific;
service-accounting;
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
}
} | [edit dynamic-profiles profile-name firewall family family] | Create firewall filters to be applied by dynamic profile. | [
{
"name": "filter-name",
"desc": "Name that identifies the filter. The name can contain letters, numbers, and hyphens (-) and can be up to 64 characters long. To include spaces in the name, enclose it in quotation marks (“ ”). The name can also be a predefined variable."
},
{
"name": "service-accoun... | 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.
The service-accounting option introduced in Junos OS Evolved Release 25.4R1. | [] |
filter (export routing policy action) | slice slice-name | [edit policy-options policy-statement policy-name term term-name then] | Enables a firewall filter to be attached to a matched route. | [] | •
routing—To view this statement in the configuration
•
routing-control—To add this statement to the configuration | Statement introduced in Junos OS 22.2R1. | [] |
filter (Firewall Filters) | filter filter-name {
interface-specific;
micro-segmentation;
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
}
} | [edit firewall family family-name] | Configure firewall filters. | [
{
"name": "filter-name",
"desc": "Name that identifies the filter. The name can contain letters, numbers, and hyphens (-), and"
},
{
"name": "micro-segmentation",
"desc": "Enables Group Based Policy (GBP) tagging for use with macro and micro"
},
{
"name": "ip-version ipv4 <ip address> | ... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Option interface-specific introduced in Junos OS Release 9.5 for EX Series switches.
Option micro-segmentation introduced in Junos OS Release 22.4R1 for supported EX4100, EX4400,
EX4650, and QFX5120 Series switches. | [
"Firewall Filter Match Conditions, Actions, and Action Modifiers for EX Series Switches",
"Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on EX Series Switches",
"Configuring Firewall Filters (CLI Procedure)",
"Firewall Filters for EX Series Switches Overview"
] |
filter (Flow Monitoring) | filter {
input filter-name;
output filter-name;
group filter-group-number;
} | [edit interfaces interface-name unit logical-unit-number family inet] | Apply a firewall filter to an interface. You can also use filters for encrypted traffic. | [
{
"name": "group filter-group-number",
"desc": "Use the specified interface to be part of a filter group. The default filter group"
},
{
"name": "input filter-name",
"desc": "Use the specified filter to evaluate when packets are received on the interface."
},
{
"name": "output filter-nam... | 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. | [
"Configuring Flow Monitoring"
] |
filter (Identity Management Advanced Query) | filter {
domain name;
exclude-ip {
address-book book-name;
address-set address-set;
}
include-ip {
address-book book-name;
address-set address-set;
}
} | [edit services user-identification identity-management] | The advanced user identity query feature enables the SRX Series Firewall to communicate with the
Juniper Identity Management Service (JIMS) server to obtain user identity information for an individual
user (ip-query) or a group of users (batch query).
Optionally, you can configure filters to convey to the JIMS server a... | [
{
"name": "include-ip",
"desc": "address-book book-name address-set address-set-name. Optionally, configure a filter that directs the SRX Series Firewall to issue a query to the JIMS server to include in its response record user identity information for users based on IP addresses in certain address-ranges.... | 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 Advanced Query Feature for Obtaining User Identity Information from JIMS"
] |
filter (interfaces) | filter {
input filter-name;
output filter-name;
} | [edit interfaces interface-name unit logical-unit-number family inet] | Define the filters to be applied on an interface. | [
{
"name": "input filter-name",
"desc": "Identifier for the input filter."
},
{
"name": "output filter-name",
"desc": "Identifier for the output 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. | [
"Configuring Filters for Traffic Transiting the ES PIC"
] |
filter (Interfaces) | filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
} | [edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family] | NOTE: On EX Series switches, the group, input-list, output-filter statements are not
supported under the [edit interfaces interface-name unit logical-unit-number family inet],
[edit interfaces interface-name unit logical-unit-number family inet6], and [edit interfaces
interface-name unit logical-unit-number family mpls... | [
{
"name": "group filter-group-number",
"desc": "Define an interface to be part of a filter group. The default filter group"
},
{
"name": "input filter-name",
"desc": "Name of one filter to evaluate when packets are received on the interface."
},
{
"name": "output filter-name",
"desc"... | 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 a Filter to an Interface",
"Junos OS Administration Library for Routing Devices",
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Configuring Firewall Filters (CLI Procedure)",
"family"
] |
filter (IPv4, IPv6, and MPLS) | filter {
input input-filter-name;
output output-filter-name;
} | [edit forwarding-options family (inet | inet6 | mpls)] | Apply a forwarding table filter to a forwarding table. | [] | 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"
] |
filter (Layer 2 and Layer 3 Interfaces) | filter (input | output) filter-name; | [edit interfaces interface-name unit logical-unit-number family family-name] | Apply a firewall filter to traffic transiting a port or Layer 3 interface.
Default
All incoming traffic is accepted unmodified on the port or Layer 3 interface, and all outgoing traffic is
sent unmodified from the port or Layer 3 interface. | [
{
"name": "filter-name",
"desc": "Name of a firewall filter defined at the [edit firewall family family-name filter] hierarchy"
},
{
"name": "input",
"desc": "Apply a firewall filter to traffic entering the port or Layer 3 interface."
},
{
"name": "output",
"desc": "Apply a firewall ... | 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 Firewall Filters",
"Overview of Firewall Filters (QFX Series)"
] |
filter (Layer 3 Interfaces) | filter (input | output) filter-name; | [edit interfaces interface-name unit logical-unit-number family family-name] | Apply a firewall filter to traffic transiting a Layer 3 interface.
Default
All incoming traffic is accepted unmodified on the Layer 3 interface, and all outgoing traffic is sent
unmodified from the Layer 3 interface. | [
{
"name": "filter-name",
"desc": "Name of a firewall filter defined at the [edit firewall family family-name filter] hierarchy"
},
{
"name": "input",
"desc": "Apply a firewall filter to traffic entering the Layer 3 interface."
},
{
"name": "output",
"desc": "Apply a firewall filter t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D20. | [
"Configuring Firewall Filters",
"Overview of Firewall Filters (OCX Series)"
] |
filter (memory-enhanced) | filter; | [edit chassis memory-enhanced] | Enables storing of firewall filters across multiple static RAM (SRAM) segments, resulting in proper
utilization of SRAM segments. This feature is useful in routers with small routing tables and large firewall
filters. This statement is supported on T Series routers. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement added in Junos OS Release 11.1. | [
"Allocating More Memory for Routing Tables, Firewall Filters, and Layer 3 VPN Labels"
] |
filter (routing-options) | filter {
input filter-name;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name],
[edit logical-systems logical-system-name routing-options rib routing-table-name],
[edit routing-instances routing-instance-name routing-options rib routing-table-name],
[edit routing-options rib ... | Specify the name of the routing table from which Junos OS should export routing information. | [
{
"name": "input filter-name",
"desc": "Forwarding table filter name."
}
] | 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. | [
"Configuring Forwarding Table Filters",
"Applying Forwarding Table Filters"
] |
filter (Security) | filter threat-attack | [edit security log stream stream-name] | Configure the log stream filter to transmit only threat and attack logs to the ClearPass Policy Manager
(CPPM). The integrated ClearPass authentication and enforcement feature sends to the CPPM threat
and attack logs detected by the SRX Series Firewall security modules. You can use these reports to
inform your approach... | [] | 1. security—To view this statement in the configuration.
2. security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
filter (VLANs) | filter (input | output) filter-name; | [edit vlans vlan-name],
[edit vlans vlan-name forwarding-options] | Apply a firewall filter to traffic entering or exiting a VLAN.
Default
All incoming traffic is accepted unmodified to the VLAN, and all outgoing traffic is sent unmodified from
the VLAN. | [
{
"name": "filter-name",
"desc": "Name of a firewall filter defined in a filter statement."
},
{
"name": "input",
"desc": "Apply a firewall filter to VLAN ingress traffic."
},
{
"name": "output",
"desc": "Apply a firewall filter to VLAN egress traffic."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on EX Series Switches",
"Configuring Firewall Filters",
"Configuring Firewall Filters (CLI Procedure)",
"Overview of Firewall Filters (QFX Series)",
"Firewall Filters for EX Series Switches Overview",
"Configuring VLANs for EX Serie... |
filter (VPLS) | filter input filter-name; | [edit forwarding-options family vpls],
[edit logical-systems logical-system-name forwarding-options family vpls],
[edit logical-systems logical-system-name routing -instances instance-name forwarding-options
family vpls],
[edit routing-instances instance-name forwarding-options family vpls] | Apply a forwarding table filter for VPLS. | [] | 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"
] |
filter | filter filter-name {
interface-specific
micro-segmentation;
no-longest-prefix-match;
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
}
} | [edit firewall family family-name] | Configure firewall filters. | [
{
"name": "filter-name",
"desc": "Name that identifies the filter. The name can contain letters, numbers, and hyphens (-), and"
},
{
"name": "micro-segmentation",
"desc": "Indicates that this firewall filter is a Group Based Policy (GBP) tagging filter. A GBP"
},
{
"name": "ip-version ip... | 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 to support GBP tagging filters.
Option no-longest-prefix-match introduced in Junos OS Release 24.4R1 to disable longest prefix match
on IP-based GBP tagging filters. | [
"Firewall Filter Match Conditions and Actions (QFX5100, QFX5110, QFX5120, QFX5200, EX4600,",
"EX4650)",
"Configuring Firewall Filters",
"Overview of Firewall Filters (QFX Series)",
"Microsegmentation Using Group-Based Policies"
] |
filter-duplicates | filter-duplicates; | [edit snmp] | Filter duplicate Get, GetNext, or GetBulk SNMP requests. | [] | 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 Duplicate SNMP Requests",
"Understanding the Implementation of SNMP on the QFabric System",
"Example: Configuring SNMP"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.