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 |
|---|---|---|---|---|---|---|---|
failover (Chassis) | failover {
on-disk-failure;
on-loss-of-keepalives;
on-re-to-fpc-stale;
} | [edit chassis redundancy] | Specify conditions on the primary Routing Engine that cause the backup router to take primary role.
On Junos OS devices this statement enables automatic Routine Engine switchover. By default this
statement is disabled on Junos OS Evolved, but it may be enabled if you are upgrading an existing
configuration from Junos O... | [
{
"name": "on-disk-failure",
"desc": "Instruct the backup router to take primary role if it detects hard disk errors on the primary Routing Engine."
},
{
"name": "on-re-to-fpc-stale",
"desc": "Instruct the backup router to take mastership if the em0 interface fails on the master Routing Engine. ... | 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.
on-re-to-fpc-stale option introduced in Junos OS Release 15.2. | [
"On Detection of a Hard Disk Error on the Primary Routing Engine",
"Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure)"
] |
failover (System Process) | failover (alternate-media | other-routing-engine); | [edit system processes process-name] | Configure the router to reboot if the software process fails four times within 30 seconds, and specify the
software to use during the reboot. | [
{
"name": "process-name",
"desc": "Junos OS process name. Some of the processes that support the failover statement are"
},
{
"name": "alternate-media",
"desc": "Use the Junos OS image on alternate media during the reboot."
},
{
"name": "other-routing-engine",
"desc": "On routers wit... | 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. | [
"When a Software Process Fails",
"processes"
] |
failover-delay | failover-delay milliseconds; | [edit protocols vrrp] | If you configure multiple VRRP groups on an interface (using multiple VLANs), traffic for some of the
groups might be briefly dropped if a failover occurs. This can happen because the new primary must
send gratuitous ARP replies for each VRRP group to update the ARP tables in the connected devices,
and there is a short... | [
{
"name": "milliseconds",
"desc": "Specify the failover delay time, in milliseconds."
}
] | 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. | [
"Troubleshooting VRRP",
"show vrrp"
] |
failover-resync | failover-resync (failover-protocol | silent-failover); | [edit services l2tp tunnel] | Configure the method used by the LAC or the LNS to resynchronize with its peer in the event of a
control plane failover. Failure can be the result of a Routing Engine switchover, a daemon restart, or
some other cause. During tunnel setup, the L2TP endpoints negotiate the resynchronization method;
silent failover is the... | [
{
"name": "failover-protocol",
"desc": "Specify the L2TP failover protocol as the resynchronization method, but fall back to silent failover if the other endpoint does not support it."
},
{
"name": "silent-failover",
"desc": "Specify silent failover as the resynchronization method. Default: sil... | 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. | [
"Configuring the L2TP Peer Resynchronization Method",
"L2TP Failover and Peer Resynchronization"
] |
failover-within-preference (L2TP LAC) | failover-within-preference; | [edit services l2tp] | Enable L2TP LAC tunnel selection within a preference level. When the router is unable to connect to a
destination at a given preference level, it attempts to connect to another destination at the same level.
By default, when a connection attempt fails at one preference level, the next attempt is made at the next
lower ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers",
"L2TP LAC Tunneling for Subscribers"
] |
failure-action (Protocols LDP) | failure-action {
remove-nexthop;
remove-route;
} | [edit logical-systems logical-system-name protocols ldp oam bfd-livenesss-detection],
[edit logical-systems logical-system-name protocols ldp oam fec address bfd-livenesss-detection],
[edit protocols ldp oam bfd-livenesss-detection],
[edit protocols ldp oam fec address bfd-livenesss-detection] | Configure route and next-hop properties in the event of a BFD session failure event on an LDP LSP. The
failure event could be an existing BFD session that has gone down or could be a BFD session that never
came up. LDP adds back the route or next hop when the relevant BFD session comes back up. | [
{
"name": "remove-nexthop",
"desc": "Remove a route corresponding to a next hop of the LSP’s route at the ingress node when"
},
{
"name": "remove-route",
"desc": "Remove the route corresponding to an LSP from the appropriate routing tables when a BFD"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring a Failure Action for the BFD Session on an LDP LSP"
] |
failure-action (Protocols MPLS) | failure-action {
make-before-break teardown-timeout seconds;
teardown;
} | [edit logical-systems logical-system-name protocols mpls oam bfd-liveness-detection],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name oam bfd-
liveness-detection],
[edit protocols mpls label-switched-path lsp-name oam bfd-liveness-detection],
[edit protocols mpls oam bfd-liveness-d... | Configure route and next-hop properties in the event of a Bidirectional Forwarding Detection (BFD)
protocol session failure event on an RSVP label-switched path (LSP). The failure event could be an
existing BFD session that has gone down or a BFD session that never came up. RSVP adds back the
route or next hop when the... | [
{
"name": "make-before-break",
"desc": "When a BFD session fails for an RSVP LSP, an attempt is made to signal a new LSP"
},
{
"name": "teardown",
"desc": "When a BFD session fails for an RSVP LSP, the associated LSP path is taken down and"
},
{
"name": "teardown-timeout seconds",
"d... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring a Failure Action for the BFD Session on an RSVP LSP"
] |
failure-action | failure-action (clear-binding | clear-binding-if-interface-up | log-only); | [edit system services dhcp-local-server liveness-detection],
[edit system services dhcp-local-server dhcpv6 liveness-detection],
[edit forwarding-options dhcp-relay liveness-detection],
[edit forwarding-options dhcp-relay dhcpv6 liveness-detection],
[edit system services dhcp-local-server group group-name liveness-dete... | Configure the action the router (or switch) takes when a liveness detection failure occurs. | [
{
"name": "clear-binding",
"desc": "The DHCP client session is cleared when a liveness detection failure occurs, except when"
},
{
"name": "clear-binding-if-interface-up",
"desc": "The DHCP client session is cleared only when a liveness detection failure"
},
{
"name": "log-only",
"de... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"DHCP Liveness Detection Overview",
"Configuring Detection of DHCP Local Server Client Connectivity with BFD",
"Configuring Detection of DHCP Relay or DHCP Relay Proxy Client Connectivity with BFD",
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring... |
fallback-block (Security Antivirus) | fallback-block {
administrator-email email-address;
allow-email;
custom-message message;
custom-message-subject message-subject;
display-host;
(notify-mail-sender | no-notify-mail-sender);
type (message | protocol-only);
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options]
[edit security utm feature-profile anti-virus sophos-... | Configure notifications for fallback blocking actions. Fallback options tell the system how to handle the
errors returned by either the scan engine or the scan manager. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5. Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS R... | [] |
fallback-key | fallback-key {
cak hexadecimal-number;
ckn hexadecimal-number;
} | [edit security macsec connectivity-association connectivity-association-name] | Specifies the fallback preshared key (PSK) to be used to enable MACsec using static connectivity
association key (CAK) security mode. You can configure a fallback PSK to prevent traffic loss in case the
primary PSK fails to establish a connection.
When you enable MACsec using static CAK security mode, a preshared PSK i... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"Configuring Advanced MACsec Features"
] |
fallback-non-block (Security Antivirus) | fallback-non-block {
custom-message message;
custom-message-subject message-subject;
(notify-mail-recipient | no-notify-mail-recipient);
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options]
[edit security utm feature-profile anti-virus sophos-e... | Configure notifications for fallback nonblocking actions. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5. Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS R... | [] |
fallback-option (ICAP Redirect Service) | fallback-option {
connectivity (block | log-permit | permit);
default-action (block | log-permit | permit);
timeout (block | log-permit | permit);
} | [edit services icap-redirect profile name],
[edit logical-systems logical-system-name services icap-redirect profile name] | Specify fallback options for the device. Fallback settings enable the device to handle errors.
The fallback option is used to define the actions such as permit, log-and-permit, or block. This is the
action that occurs when a request fails due to conditions such as too many requests, or a timeout
occurred, or connectivi... | [
{
"name": "connectivity",
"desc": "Fallback settings when connection-related failures occur. Values:"
},
{
"name": "block",
"desc": "Log the error and deny the requests."
},
{
"name": "log-permit",
"desc": "Log the error and permit the requests."
},
{
"name": "permit",
"... | system | Statement introduced in Junos OS Release 18.1R1.
The logical system option is introduced in Junos OS Release 18.3R1. | [
"ICAP Service Redirect"
] |
fallback-options (Security Antivirus Juniper Express Engine) | fallback-options {
content-size (block | log-and-permit);
default (block | log-and-permit);
engine-not-ready (block | log-and-permit);
out-of-resources (block | (log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block | log-and-permit);
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name] | Fallback options tell the system how to handle the errors. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express Antivirus feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Express Antivirus Configuration Overview"
] |
fallback-options (Security Antivirus Kaspersky Lab Engine) | fallback-options {
content-size (block | log-and-permit);
corrupt-file (block | log-and-permit);
decompress-layer (block | log-and-permit);
default (block | log-and-permit);
engine-not-ready (block | log-and-permit);
out-of-resources (block | (log-and-permit);
password-file (block | (log-and... | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name] | Fallback options tell the system how to handle the errors returned by either the scan engine or the scan
manager. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Kaspersky feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Full Antivirus Configuration Overview"
] |
fallback-options (Security Antivirus Sophos Engine) | fallback-options {
content-size (block | log-and-permit | permit);
default (block | log-and-permit | permit);
engine-not-ready (block | log-and-permit | permit);
out-of-resources (block | log-and-permit | permit);
timeout (block | log-and-permit | permit);
too-many-requests (block | log-and-per... | [edit security utm default-configuration anti-virus]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name] | Configure fallback options to instruct the system how to handle errors. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration anti-virus] hierarchy level is introduced in Junos OS Release
18.2R1.
The server-connection-err option is introduced in Junos OS Release 23.1R2. | [
"Sophos Antivirus Configuration Overview"
] |
fallback-settings (Security Web Filtering Juniper Local) | fallback-settings {
default (block | log-and-permit);
server-connectivity (block | log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block | log-and-permit);
} | [edit security utm default-configuration],
[edit security utm feature-profile web-filtering juniper–local profile profile-name] | Fallback settings tell the system how to handle errors. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Web Filtering Overview"
] |
fallback-settings (Security Web Filtering Websense Redirect) | fallback-settings {
default (block | log-and-permit);
server-connectivity (block | log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block | log-and-permit);
} | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name] | Fallback settings tell the system how to handle errors. | [] | 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. | [
"Understanding Redirect Web Filtering"
] |
fallback-settings (Security Web Filtering) | fallback-settings {
default (block | log-and-permit);
server-connectivity (block | log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block | log-and-permit);
} | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated profile profile-name]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name] | Fallback settings tell the system how to handle errors. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Surf-Control feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, Statement introduced in Junos OS Release 9.5 .
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
falling-event-index (RMON) | falling-event-index index; | [edit snmp rmon alarm index] | Set the index number of the event entry that is used when a falling threshold is crossed. You specify the
falling-event index when you configure an SNMP RMON alarm. If this value is zero, no event is
triggered. | [
{
"name": "index",
"desc": "Index of the event entry that is used when a falling threshold is crossed."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"RMON MIB Event, Alarm, Log, and History Control Tables",
"Configuring RMON Alarms and Events",
"Monitoring RMON MIB Tables",
"Understanding RMON",
"Junos OS Network Management Configuration Guide"
] |
falling-event-index | falling-event-index index; | [edit snmp rmon alarm index] | The index of the event entry that is used when a falling threshold is crossed. If this value is zero, no
event is triggered. | [
{
"name": "index",
"desc": "Index of the event entry that is used when a falling threshold is crossed."
}
] | 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. | [
"Configuring the Falling Event Index or Rising Event Index"
] |
falling-threshold (Health Monitor) | falling-threshold percentage; | [edit snmp health-monitor] | Set the lower threshold for the monitored object when you configure a health monitor alarm. By setting
a rising and a falling threshold for a monitored variable, you can be alerted whenever the value of the
variable falls outside the allowable operational range. | [
{
"name": "percentage",
"desc": "Lower threshold for the alarm entry."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D20. | [
"rising-threshold",
"Configuring Health Monitoring"
] |
falling-threshold (integer) | falling-threshold integer; | [edit snmp rmon alarm index] | Set the lower threshold for the sampled variable (monitored object) when you configure an SNMP
RMON alarm. By setting a rising and a falling threshold for a variable, you can be alerted whenever the
value of the variable falls outside the allowable operational range. | [
{
"name": "integer",
"desc": "The lower threshold for the alarm entry."
}
] | 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. | [
"Configuring the Falling Threshold or Rising Threshold"
] |
falling-threshold (percentage) | falling-threshold percentage; | [edit snmp health-monitor],
[edit snmp health-monitor idp] | Set the lower threshold for the monitored object when you configure a health monitor alarm. By setting
a rising and a falling threshold for a monitored variable, you can be alerted whenever the value of the
variable falls outside the allowable operational range. | [
{
"name": "percentage",
"desc": "The lower threshold for the alarm entry."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring the Falling Threshold or Rising Threshold"
] |
falling-threshold (RMON) | falling-threshold integer; | [edit snmp rmon alarm index] | Set the lower threshold for the sampled variable (monitored object) when you configure an SNMP
RMON alarm. By setting a rising and a falling threshold for a variable, you can be alerted whenever the
value of the variable falls outside the allowable operational range. | [
{
"name": "integer",
"desc": "Lower threshold for the alarm entry."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"RMON MIB Event, Alarm, Log, and History Control Tables",
"Configuring RMON Alarms and Events",
"Monitoring RMON MIB Tables",
"Understanding RMON",
"Junos OS Network Management Configuration Guide"
] |
falling-threshold-interval | falling-threshold-interval seconds; | [edit snmp rmon alarm index] | Set the interval between samples after the rising threshold is exceeded and the value of the sample
starts to drop. If the value of the sample drops and exceeds the falling threshold, the regular sampling
interval is used. | [
{
"name": "seconds",
"desc": "Time between samples, in seconds."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring the Falling Threshold Interval"
] |
false-positives | false-positives {
values [frequently occasionally rarely unknown];
} | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify a false positives filter to track attack objects based on the frequency that the attack produces a
false positive on your network. | [
{
"name": "values",
"desc": "Name of the false positives filter. You can select from the following false positive frequency:"
},
{
"name": "frequently",
"desc": "Frequently track false positive occurrences."
},
{
"name": "occasionally",
"desc": "Occasionally track false positive occu... | 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. | [] |
family (Address Pools) | family (inet | inet6) {
network {
[network-prefix] {
external-assigned;
}
}
} | [edit access address-assignment address-pools name] | Specify the protocol family information for the address pool. Address pools must have either inet (IPv4)
or inet6 (IPv6) configured.
NOTE: A address pool can have either inet (IPv4) or inet6 (IPv6) configured, but not both. | [
{
"name": "inet",
"desc": "IP version 4 (IPv4) suite."
},
{
"name": "inet6",
"desc": "IP version 6 (IPv6) suite."
}
] | 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. | [
"Understanding Source IP Filtering with Address Pools in TDF Domains for IP-Based Subscribers",
"Configuring Address Pools for Source-IP Filtering of IP-Based Subscribers"
] |
family (Address-Assignment Pools) | family family {
dhcp-attributes {
[protocol-specific attributes]
}
excluded-address ip-address;
excluded-range name low minimum-value high maximum-value;
host hostname {
hardware-address mac-address;
ip-address ip-address;
}
network ip-prefix/<prefix-length>;
pref... | [edit access address-assignment pool pool-name] | Configure the protocol family for the address-assignment pool.
NOTE: Subordinate statement support depends on the platform. See individual
statement topics for more detailed support information. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "inet",
"desc": "Internet Protocol version 4 suite"
},
{
"name": "inet6",
"desc": "Internet Protocol version 6 suite"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Address-Assignment Pools Overview",
"Address-Assignment Pool Configuration Overview"
] |
family (Aggregated Multiservices) | family family; | [edit interfaces interface-name unit interface-unit-number] | Configure protocol family information for the logical interface. | [
{
"name": "family",
"desc": "Protocol family. Currently, only one option, inet (IP version 4 suite), is supported."
}
] | 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. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
family (Bootstrap) | family (inet | inet6) {
export [ policy-names ];
import [ policy-names ];
priority number;
} | [edit logical-systems logical-system-name protocols pim rp bootstrap],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp bootstrap],
[edit protocols pim rp bootstrap],
[edit routing-instances routing-instance-name protocols pim rp bootstrap] | Configure which IP protocol type bootstrap properties to apply. | [
{
"name": "inet",
"desc": "Apply IP version 4 (IPv4) local RP properties."
},
{
"name": "inet6",
"desc": "Apply IPv6 local RP properties."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring PIM Bootstrap Properties for IPv4",
"Configuring PIM Bootstrap Properties for IPv4 or IPv6"
] |
family (chassis) | family {
inet {
layer-3;
layer-4;
symmetric-hash {
complement;
}
}
multiservice {
source-mac;
destination-mac;
payload {
ip {
layer-3;
layer-4;
}
}
symmetric-hash {
... | [edit chassis fpc slot-number pic pic-number hash-key] | (MX Series 5G Universal Routing Platforms only) Configure data used in a hash key for a specific
protocol family when configuring PIC-level symmetrical load balancing on an 802.3ad Link Aggregation
Group. | [
{
"name": "inet",
"desc": "Configure data used in a hash key for the inet protocol family."
},
{
"name": "multiservice",
"desc": "Configure data used in a hash key for the multiservice protocol family."
}
] | 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. | [
"Configuring PIC-Level Symmetrical Hashing for Load Balancing on 802.3ad LAGs for MX Series",
"Routers"
] |
family (Dynamic Demux Interface) | family family {
access-concentrator name;
address address;
demux-source {
source-address;
}
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
input filter-name;
output filter-name;
}
mac-validate (loose | strict);
max-session... | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number] | Configure protocol family information for the logical interface.
NOTE: Not all subordinate stanzas are available to every protocol family. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "inet",
"desc": "Internet Protocol version 4 suite"
},
{
"name": "inet6",
"desc": "Internet Protocol version 6 suite"
},
{
"name": "pppoe",
"desc": "(MX Series routers with MPCs only) Point-to-Point Protocol over... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
pppoe option added in Junos OS Release 11.2. | [
"Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles",
"Subscriber Interfaces and Demultiplexing Overview"
] |
family (Dynamic Firewalls) | family family {
fast-update-filter filter-name {
interface-specific;
match-order [match-order];
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
only-at-c... | [edit dynamic-profiles profile-name firewall] | Configure fast update filters or parameterized filters for a protocol family in a dynamic client profile or a
dynamic service profile. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "any",
"desc": "Filter packets based on protocol-independent match conditions."
},
{
"name": "inet",
"desc": "Filter Internet Protocol version 4 suite packets."
},
{
"name": "inet6",
"desc": "filter Internet Prot... | 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.
any option added in Junos OS Release 16.1. | [
"Configuring Fast Update Filters",
"Parameterized Filters Overview",
"Guidelines for Configuring Firewall Filters",
"Configuring Unique Identifiers for Parameterized Filters"
] |
family (Dynamic PPPoE) | family family {
unnumbered-address interface-name;
address address;
service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-service-filter filter-name;
}
output {
service-set service-set-name ... | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit] | Configure protocol family information for the logical interface. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "inet",
"desc": "Internet Protocol version 4 suite"
},
{
"name": "inet6",
"desc": "Internet Protocol version 6 suite"
}
] | 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. | [
"Configuring a PPPoE Dynamic Profile",
"Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview"
] |
family (Dynamic Standard Interface) | family family {
access-concentrator name;
address address;
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
adf {
counter;
input-precedence precedence;
not-mandatory;
output-precedence precedence;
rul... | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | Configure protocol family information for the logical interface.
NOTE: Not all subordinate stanzas are available to every protocol family. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "inet",
"desc": "IP version 4 suite"
},
{
"name": "inet6",
"desc": "IP version 6 suite"
},
{
"name": "pppoe",
"desc": "(MX Series routers with MPCs only) Point-to-Point Protocol over Ethernet"
},
{
"name"... | 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.
pppoe option added in Junos OS Release 11.2. | [
"Static Routing on Logical Systems",
"Configuring the Protocol Family"
] |
family (ELS) | family {
ethernet-switching {
filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
}
interface-mode (access | trunk);
recovery-timeout second... | [edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-range interface-name unit logical-unit-number family] | Configure protocol family information for the logical interface on QFX Series switches.
Default
Access interfaces on the QFX Series are set to family ethernet-switching by default. If you are going to
change the family setting for an interface, you might have to delete this default setting or any user-
configured famil... | [
{
"name": "10-Gigabit Ethernet (xe)",
"desc": "Not all interface types support all family substatements. Check your switch CLI for supported substatements for a particular protocol family configuration."
}
] | 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",
"Configuring Link Aggregation",
"Configuring IRB Interfaces on Switches",
"Junos OS Network Interfaces Library for Routing Devices"
] |
family (Exclude Prefix) | family {
inet {
apply-groups [group-names];
apply-groups-except [group-names];
network address net-mask;
}
inet6 {
apply-groups [group-names];
apply-groups-except [group-names];
network address net-mask;
}
} | [edit unified-edge gateways tdf gateway-name domains domain-name subscriber-exclude-prefix] | Specify the IP version for the network prefix of source IP addresses for uplink packets and destination IP
addresses for downlink packets that must not undergo TDF processing.
The remaining statements are explained separately. See CLI Explorer. | [] | 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",
"Configuring IFL-Based TDF Subscribers and Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based and IFL-Based TDF Subscribers Overview",
"IP-Based Sub... |
family (Filtering) | family family-name {
filter {
input input-filter-name;
output output-filter-name;
}
flood {
input filter-name;
}
route-accounting;
source-checking;
} | [edit forwarding-options] | Specify address family for filters. | [
{
"name": "family-name",
"desc": "Address family. Specify inet for IP version 4 (IPv4), inet6 for IP version 6 (IPv6), mpls for"
}
] | 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.
route-accounting option introduced in Junos OS Release 8.3; supported only with IPv6.
source-checking option introduced in Junos OS Release 12.3 on MX Series 5G Universal Routing
Platforms; supported only with IPv6. | [
"Applying Forwarding Table Filters"
] |
family (Firewall Filter) | family family-name {
filter filter-name {
interface-specific;
micro-segmentation;
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
}
}
} | [edit firewall] | Configure a firewall filter for IP version 4 or IP version 6. | [
{
"name": "family-name",
"desc": "Version or type of addressing protocol:"
},
{
"name": "any",
"desc": "Filter packets based on protocol-independent match conditions."
},
{
"name": "ethernet-switching",
"desc": "Filter Layer 2 (Ethernet) packets and Layer 3 (IP) packets."
},
{
... | 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.
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"
] |
family (Firewall) | family family-name {
filter filter-name {
accounting-profile name;
enhanced-mode;
interface-specific;
physical-interface-filter;
}
prefix-action name {
count;
destination-prefix-length prefix-length;
policer policer-name;
source-prefix-length p... | [edit firewall],
[edit logical-systems logical-system-name firewall] | Configure a firewall filter for IP version 4 (IPv4) or IP version 6 (IPv6) traffic. Only on MX Series routers
and EX Series switches, configure a firewall filter for Layer 2 traffic in a bridging environment. | [
{
"name": "family-name",
"desc": "Version or type of addressing protocol:"
},
{
"name": "any",
"desc": "Protocol-independent match conditions."
},
{
"name": "bridge",
"desc": "(MX Series routers only) Layer 2 packets that are part of bridging domain."
},
{
"name": "ethernet-s... | 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.
simple-filter statement introduced in Junos OS Release 7.6.
any family type introduced in Junos OS Release 8.0.
bridge family type introduced in Junos OS Release 8.4 (MX Series routers only). | [
"Guidelines for Configuring Firewall Filters",
"Guidelines for Configuring Service Filters",
"Guidelines for Configuring Simple Filters"
] |
family (interfaces) | family family {
accounting {
destination-class-usage;
source-class-usage {
(input | output | input output);
}
}
access-concentrator name;
address address {
... the address subhierarchy appears after the mai... | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | 20.1R1
Starting in Junos OS Release 20.1R1, aggregated ethernet interfaces supports VLAN TCC (Translational
cross-connect) encapsulation on MX series platforms. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "any",
"desc": "Protocol-independent family used for Layer 2 packet filtering"
},
{
"name": "bridge",
"desc": "(M Series and T Series routers only) Configure only when the physical interface is configured"
},
{
"name... | 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.
Option max-sessions-vsa-ignore introduced in Junos OS Release 11.4.
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 | [
"Configuring the Protocol Family"
] |
family (Interfaces) | family inet {
address address {
...
}
service {
input {
[ service-set service-set-name <service-filterfilter-name> ];
post-service-filter filter-name;
}
output {
[ service-set service-set-name <service-filter filter-name> ];
}
... | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure protocol family information for the logical interface. | [
{
"name": "family",
"desc": "Protocol family. Valid settings for service interfaces include inet (IPv4) and mpls."
}
] | 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. | [
"Junos OS Network Interfaces Library for Routing Devices",
"Configuring the Address and Domain for Services Interfaces",
"Junos OS Network Interfaces Library for Routing Devices"
] |
family (Link Interfaces) | family family {
address address {
destination address;
}
} | [edit interfaces interface-name unit logical-unit-number] | Configure protocol family information for the logical interface. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "ccc",
"desc": "Circuit cross-connect protocol suite"
},
{
"name": "inet",
"desc": "IP version 4 (IPv4)"
},
{
"name": "inet6",
"desc": "IP version 6 (IPv6)"
},
{
"name": "iso",
"desc": "Open Systems I... | 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. | [
"Link and Multilink Services Interfaces User Guide for Routing Devices",
"Junos OS Network Interfaces Library for Routing Devices"
] |
family (Local RP) | family (inet | inet6) {
disable;
address address;
anycast-pim {
local-address address;
rp-set {
address address <forward-msdp-sa>;
}
}
group-ranges {
destination-ip-prefix</prefix-length>;
}
hold-time seconds;
override;
priority number;
} | [edit logical-systems logical-system-name protocols pim rp local],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp local],
[edit protocols pim rp local],
[edit routing-instances routing-instance-name protocols pim rp local] | Configure which IP protocol type local RP properties to apply. | [
{
"name": "inet",
"desc": "Apply IP version 4 (IPv4) local RP properties."
},
{
"name": "inet6",
"desc": "Apply IPv6 local RP properties."
}
] | 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 Local PIM RPs"
] |
family (logical-interface) | family family {
ipsec-sa sa-name;
} | [edit interfaces interface-name unit logical-unit-number] | Configure protocol family information for the logical interface. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "ccc",
"desc": "Circuit cross-connect protocol suite"
},
{
"name": "inet",
"desc": "IP version 4 suite"
},
{
"name": "inet6",
"desc": "IP version 6 suite"
},
{
"name": "iso",
"desc": "Open Systems Int... | 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 Encryption Interfaces",
"Junos OS Network Interfaces Library for Routing Devices"
] |
family (Monitoring) | family inet {
output {
flow-active-timeout seconds;
flow-inactive-timeout seconds;
export-format format;
cflowd hostname {
aggregation {
autonomous-system;
destination-prefix;
protocol-port;
source-destinatio... | [edit forwarding-options monitoring name] | Specify input and output interfaces and properties for flow monitoring. Only IPv4 (inet) is supported.
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 Flow Monitoring",
"Configuring Passive Flow Monitoring"
] |
family (Multi-destination) | family {
ethernet {
broadcast forwarding-class-name;
}
inet {
classifiers{
(dscp | inet-precedence) classifier-name;
}
}
} | [edit class-of-service multi-destination] | Specify the multidestination traffic family.
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 in Junos OS Release 9.5. | [
"Understanding CoS Schedulers",
"Understanding CoS Forwarding Classes",
"Understanding CoS Classifiers"
] |
family (Multifield Classifier) | family family-name {
filter filter-name {
term term-name {
... term_configuration ...
}
}
} | [edit firewall] | Configure a firewall filter for IP version 4 (IPv4) or IP version 6 (IPv6) traffic. | [
{
"name": "family-name",
"desc": "Protocol family:"
},
{
"name": "ccc",
"desc": "Circuit cross-connect parameters"
},
{
"name": "inet",
"desc": "IPv4 parameters"
},
{
"name": "inet6",
"desc": "IPv6 protocol parameters"
},
{
"name": "iso",
"desc": "OSI ISO prot... | 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 Multifield Classifiers"
] |
family (Port Mirroring) | [edit forwarding-options port-mirroring] | Specify the type of interface that will be used to forward port mirrored packet to an analyzer device.
Configure the protocol family to be sampled. Only IPv4 (inet) and IPv6 (inet6) are supported.
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.
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 Port Mirroring on M, T MX, ACX, and PTX Series Routers",
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis"
] | |
family (Protocols AMT Relay) | family {
inet {
anycast-prefix ip-prefix/<prefix-length>;
local-address ip-address;
}
} | [edit logical-systems logical-system-name protocols amt relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay],
[edit protocols amt relay],
[edit routing-instances routing-instance-name protocols amt relay] | Configure the protocol address family for Automatic Multicast Tunneling (AMT) relay functions. Only the
inet family for IPv4 protocol addresses is supported.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the AMT Protocol"
] |
family (Protocols BGP) | family {
(inet | inet6 | inet-vpn | inet6-vpn | iso-vpn) {
(any | flow | labeled-unicast | multicast | unicast | segment-routing-te) {
accepted-prefix-limit {
maximum number;
teardown <percentage-threshold> idle-timeout (forever | minutes);
drop-excess <percentage>;
hide-exc... | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Enable multiprotocol BGP (MP-BGP) by configuring BGP to carry network layer reachability information
(NLRI) for address families other than unicast IPv4, to specify MP-BGP to carry NLRI for the IPv6
address family, or to carry NLRI for VPNs.
NOTE:
•
When you configure the family statement at multiple BGP hierarchy lev... | [
{
"name": "any",
"desc": "Configure the family type to be both unicast and multicast."
},
{
"name": "evpn",
"desc": "Configure NLRI parameters for Ethernet VPNs (EVPNs)."
},
{
"name": "inet",
"desc": "Configure NLRI parameters for IPv4."
},
{
"name": "inet6",
"desc": "Con... | 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.
inet-mvpn and inet6-mpvn statements introduced in Junos OS Release 8.4.
inet-mdt statement introduced in Junos OS Release 9.4.
Support for the loops statement introduced in Junos OS Release 9.6.
evpn statement introduced in Junos OS Release 13.2.
traffic-engineering st... | [
"Configuring IBGP Sessions Between PE Routers in VPNs",
"Understanding Multiprotocol BGP",
"autonomous-system",
"local-as"
] |
family (Protocols IS-IS) | family inet {
shortcuts {
multicast-rpf-routes;
}
}
family inet-mpls {
shortcuts;
}
family inet6 {
shortcuts;
}
family inet6-mpls {
shortcuts;
} | [edit logical-systems logical-system-name protocols isis traffic-engineering],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
traffic-engineering],
[edit protocols isis traffic-engineering],
[edit routing-instances routing-instance-name protocols isis traffic-engineeri... | Configure the address family for traffic engineering IS-IS interior gateway protocol (IGP) shortcuts. | [
{
"name": "inet",
"desc": "Configure the IPv4 address family."
},
{
"name": "inet-mpls",
"desc": "Configure the IPv4 MPLS address family."
},
{
"name": "inet6",
"desc": "Configure the IPv6 address family."
},
{
"name": "inet6-mpls",
"desc": "Configure the IPv6 address fam... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
Support for IPv6 for IGP shortcuts introduced in Junos OS Release 9.3.
Support for inet-mpls and inet6-mpls statements introduced in Junos OS Release 17.2 for the MX Series
routers, PTX Series routers, QFX5100, and QFX10000 switches. | [] |
family (protocols ldp) | family {
inet;
inet6;
} | [edit protocols ldp] | Configure the address family as inet for IPv4 or inet6 for IPv6, or both. If the address family is not
configured, then the default address family is IPv4. | [] | 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. | [
"LDP Native IPv6 Support Overview",
"Example: Configuring LDP Native IPv6 Support",
"Configuring LDP Native IPv6 Support"
] |
family (Protocols PIM Interface) | family (inet | inet6) {
bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-rece... | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name],
[edit protocols pim interface (Protocols PIM) interface-name],
[edit routing-in... | Configure one of the following PIM protocol settings for the specified family on the specified interface:
•
BFD protocol settings
•
Disable PIM | [
{
"name": "inet",
"desc": "Enable the PIM protocol for the IP version 4 (IPv4) address family."
},
{
"name": "inet6",
"desc": "Enable the PIM protocol for the IP version 6 (IPv6) address family."
}
] | Statement introduced in Junos OS Release 9.6.
Support for the Bidirectional Forwarding Detection (BFD) Protocol statements was introduced in Junos
OS Release 12.2. | [
"Configuring PIM and the Bidirectional Forwarding Detection (BFD) Protocol",
"Disabling PIM"
] | |
family (Protocols PIM) | family (inet | inet6) {
disable;
} | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit logical-systems logical-system-name routing-instances rout... | Disable the PIM protocol for the specified family. | [
{
"name": "inet",
"desc": "Disable the PIM protocol for the IP version 4 (IPv4) address family."
},
{
"name": "inet6",
"desc": "Disable the PIM protocol for the IP version 6 (IPv6) address family."
}
] | Statement introduced in Junos OS Release 9.6. | [
"Disabling PIM",
"disable (PIM Graceful Restart)"
] | |
family (QFX) | family family-name {
filter filter-name {
interface-specific;
micro-segmentation;
term term-name {
from {
match-conditions;
egress-to-ingress;
}
then {
action;
action-modifiers;
... | [edit firewall] | Configure the fields a firewall filter can match on. | [
{
"name": "family-name",
"desc": "Type of addressing protocol:"
},
{
"name": "ethernet-switching",
"desc": "Filter Layer 2 Ethernet packets and Layer 3 (IP) packets (allows some Layer 3"
},
{
"name": "egress-to-ingress",
"desc": "Include this option to increase the number of egress V... | 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.
evpn options introduced in Junos OS Release 15.1 for the MX Series.
egress-to-ingress option introduced in Junos OS Release 19.1R1 for the QFX5110.
any option introduced in Junos OS Release 22.4R1 for supported QFX5120, EX4100, EX4400, and
EX4650 Series switches.
micro-seg... | [
"Firewall Filter Match Conditions and Actions (QFX5100, QFX5110, QFX5120, QFX5200, EX4600,",
"EX4650)",
"Configuring Firewall Filters",
"Overview of Firewall Filters (QFX Series)"
] |
family (RFC 2544 Benchmarking Tests) | family (bridge | ccc | ethernet-switching | inet | vpls); | [edit services monitoring rfc2544 tests test-name test-name] | Configure the address type family for the benchmarking test. | [
{
"name": "bridge",
"desc": "(Junos OS) Run the test on a Layer 2 Ethernet line (E- Line) or an Ethernet LAN (E-LAN) service configured in a bridge domain. You can run the RFC2544-based benchmarking test only in the egress direction or the user-to-network interface (UNI) direction of an Ethernet line."
},... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X52.
bridge option introduced in Junos OS Release 12.3X53 for ACX Series routers.
bridge option introduced in Junos OS Release 14.2 for MX104 Universal Routing Platforms.
Statement introduced in Junos OS Evolved Release 21.1R1 for the inet option only.
ccc and ethernet-switc... | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers"
] |
family (Sampling) | family (inet | inet6 | mpls | vpls | bridge) {
disable;
input {
max-packets-per-second max-packets-per-second;
maximum-packet-length maximum-packet-length;
rate rate;
run-length run-length
}
output {
aggregate-export-interval seconds;
file {
... | [edit forwarding-options sampling],
[edit forwarding-options sampling instance instance-name],
[edit forwarding-options sampling instance instance-name family (inet | inet6 | bridge) | Configure the protocol family to be sampled. IPv4 (inet) is supported for most purposes, but you can
configure family mpls to collect and export MPLS label information, family inet6 to collect and export IPv6
traffic using flow aggregation version 9, and vpls to collect and export VPLS information, and bridge to
colle... | [] | 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.
mpls option introduced in Release 8.3.
inet6 option introduced in Release 9.4.
vpls option introduced in Junos OS Release 13.2 for MX Series routers.
bridge option introduced in Release 18.2R1 for MX Series routers.
Support for IPv6 addresses for the flow-server address... | [
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Configuring Traffic Sampling"
] |
family (sFlow) | family {
inet {
structure-list {
extended-gateway {
communities {
count count;
}
destination-as-path {
count count;
}
}
}
}
inet6 {
structure-list {
... | [edit protocols sflow] | Configure the protocol family to export the extended gateway structure in sFlow records. Both IPv4
(inet) and IPv6 (inet6) protocols are supported. | [
{
"name": "inet",
"desc": "Configure the IPv4 address family."
},
{
"name": "structure-list",
"desc": ""
},
{
"name": "sFlow structure list",
"desc": ""
},
{
"name": "inet6",
"desc": "Configure the IPv6 address family."
},
{
"name": "structure-list",
"desc": "... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1. | [] |
family (TDF Interface) | family family-name; | [edit interfaces mif unit interface-unit-number] | Configure the protocol family information for the TDF logical interface. | [
{
"name": "family-name",
"desc": "Protocol family. The following options are supported:"
},
{
"name": "inet",
"desc": "IP version 4 suite."
},
{
"name": "inet6",
"desc": "IP version 6 suite."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a TDF Logical Interface"
] |
family (Voice Services) | family (inet | mlppp | ...) {
address address {
...
}
bundle interface-name;
} | [edit interfaces interface-name unit logical-unit-number] | Configure protocol family information for the logical interface. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "inet",
"desc": "IP version 4"
},
{
"name": "mlppp",
"desc": "MLPPP"
}
] | 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. | [
"Junos OS Network Interfaces Library for Routing Devices",
"Configuring Network Interfaces for Voice Services",
"Junos OS Network Interfaces Library for Routing Devices"
] |
family (VRF Advertisement) | family {
inet-mvpn;
inet6-mvpn;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name vrf-advertise-
selective],
[edit routing-instances routing-instance-name vrf-advertise-selective] | Explicitly enable IPv4 or IPv6 MVPN routes to be advertised from the VRF instance while preventing all
other route types from being advertised.
The options 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 10.1. | [
"Configuring PIM-SSM GRE Selective Provider Tunnels"
] |
family bridge (GRE Interfaces) | family bridge {
interface-mode (access | trunk);
core-facing;
vlan-id number;
vlan-id-list vlan-list;
} | [edit interfaces gr-fpc/pic/port.unit] | Configure the bridge domain family on GRE interfaces. To enable Layer 2 Ethernet packets to be
terminated on GRE tunnels, you must configure the bridge domain protocol family on the gr- interfaces
and associate the gr- interfaces with the bridge domain. You must configure the GRE interfaces as core-
facing interfaces, ... | [
{
"name": "interface-mode",
"desc": "Specify the type of VLAN tagging on packets that the interface accepts."
},
{
"name": "access",
"desc": "Configure a logical interface to accept untagged packets. Specify the VLAN to which this"
},
{
"name": "trunk",
"desc": "Configure a single lo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement at the [edit interfaces gr-fpc/pic/port.unit] hierarchy level introduced in Junos OS Release
15.1 for MX Series routers. | [
"Layer 2 Services over GRE Tunnel Interfaces on MX Series with MPCs"
] |
family bridge | family bridge {
apply-groups value;
apply-groups-except value;
core-facing;
interface-mode access | trunk;
inner-vlan-id-list inner-vlan-id-range;
storm-control;
vlan-id vlan-id ;
vlan-id-list vlan-id-range;
} | [edit interfaces]
[edit logical-systems name interfaces] | Family bridge is used when you want a port that has more than one logical unit, each with the same or
different encapsulations. Bridge domains are associated with GRE interface with the corresponding BD
VLAN. | [] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
Starting in Junos OS release 17.4R1 for MX Series routers, support for storm control was added for
logical systems. | [
"Tunnel Services Overview",
"Tunnel Interface Configuration on MX Series Routers Overview"
] |
family fcoe | QFX Series Standalone Switches
family fcoe {
oxid (enable | disable);
}
QFabric Systems
family fcoe {
ethernet-interfaces {
node-group (node-group-name | all) {
oxid (enable | disable);
}
}
fabric-interfaces {
node-group (node-group-name | all) {
oxid (ena... | [edit forwarding-options hash-key] | Configure whether or not to use the originator exchange identifier (OxID) field for hash control for FCoE
traffic load balancing. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Ethernet-interfaces and fabric-interfaces statements introduced in Junos OS Release 13.2X52-D10 for
the QFX Series. | [
"Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on Standalone Switches",
"Understanding OxID Hash Control for FCoE Traffic Load Balancing on Standalone Switches"
] |
family inet (Interfaces) | inet {
accounting {
destination-class-usage;
source-class-usage {
input;
output;
}
}
address (source–address/prefix) {
arp destination-address {
(mac mac-address | multicast-mac multicast-mac-address);
publish publish-address;
... | [edit interfaces interface unit unit ] | Assign an IP address to a logical interface. | [
{
"name": "ipaddress",
"desc": "Specify the IP address for the interface. The remaining statements are explained separately."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement supported in Junos 10.2 for SRX Series Firewalls. | [
"Understanding Interfaces"
] |
family inet6 | inet6 {
accounting {
destination-class-usage;
source-class-usage {
input;
ouput;
}
}
address source–address/prefix {
eui-64;
ndp address {
(mac mac-address | multicast-mac multicast-mac-address);
publish;
}
... | [edit interfaces interface unit unit ] | Assign an IPV6 address to a logical interface. | [
{
"name": "ipaddress",
"desc": "Specify the IP address for the interface. The remaining statements are explained separately."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement supported in Junos 10.2 for SRX Series Firewalls. | [
"Understanding Interfaces"
] |
family inet | family inet {
layer-3;
layer-4;
session-id;
symmetric-hash {
complement;
}
} | [edit forwarding-options hash-key] | Configure layer information for the load-balancing specification. Only the IPv4 protocol is supported. | [
{
"name": "family inet",
"desc": "Incorporate port data into the hash key for flow determination. By default, port data is"
},
{
"name": "layer-3",
"desc": "Incorporate Layer 3 (IP) data into the hash key. You must include the layer-3 statement. If you"
},
{
"name": "layer-4",
"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. | [
"Configuring Per-Packet Load Balancing"
] |
family mpls | family mpls {
all-labels;
label-1;
label-2;
label-3;
no-labels;
no-label-1-exp;
payload {
ether-pseudowire {
zero-control-word;
}
ip {
disable;
layer-3-only;
port-data {
source-msb;
source... | [edit forwarding-options hash-key] | For aggregated Ethernet and SONET/SDH interfaces only, configure load balancing based on MPLS
labels and payload. Only the IPv4 protocol is supported. | [
{
"name": "family mpls",
"desc": "(Aggregated Ethernet interfaces, aggregated SONET/SDH interfaces, and multiple equal-cost MPLS next hops only) Incorporate MPLS label and payload information into the hash key for per-"
},
{
"name": "all-labels",
"desc": "(PTX Series Packet Transport Routers onl... | 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.
no-label-1-exp option introduced in Junos OS Release 8.0.
label-3 and no-labels options introduced in Junos OS Release 8.1.
ether-pseudowire statement introduced in Junos OS Release 9.1 (M320 and T Series routers only); support
extended to M120 and MX Series routers in ... | [
"Configuring Load Balancing Based on MPLS Labels",
"Configuring Load Balancing for Ethernet Pseudowires"
] |
family multiservice | family multiservice {
destination-mac;
label-1;
label-2;
payload {
ip {
layer-3 {
(source-ip-only | destination-ip-only);
}
layer-3-only;
layer-4;
}
}
source-mac;
symmetric-hash {
complement;
}
} | [edit forwarding-options hash-key] | Configure load balancing based on Layer 2 media access control information. On MX Series routers,
configure VPLS load balancing. On M120 and M320 routers only, configure VPLS load balancing based
on MPLS labels and IP information. For IPv4 traffic, only the IP source and destination addresses are
included in the hash k... | [
{
"name": "destination-mac",
"desc": "Include the destination-address MAC information in the hash key for Layer 2 load"
},
{
"name": "label-1 (M120 and M320 routers only)",
"desc": "Include the first MPLS label in the hash key. Used for including a"
},
{
"name": "label-2 (M120 and M320 r... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0.
ip, label-1, label-2, layer-3-only, and payload options introduced in Junos OS Release 9.4.
layer-3, layer-. source-ip-only, and destination-ip-only options introduced in Junos OS Release 9.5.
symmetric-hash and complement options introduced in Junos OS Release 9.6. | [
"Configuring Load Balancing Based on MAC Addresses",
"Configuring VPLS Load Balancing Based on IP and MPLS Information",
"Configuring VPLS Load Balancing on MX Series 5G Universal Routing Platforms",
"Configuring VPLS Load Balancing"
] |
family route-target | family route-target {
advertise-default;
external-paths number;
prefix-limit number;
proxy-generate <route-target-policy route-target-policy-name>;
} | [edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit protocols bgp group group-name],
[edit protocols bgp group group-name neighbor address] | Enable BGP route target filtering on the VPN.
The family route-target statement is useful for filtering VPN routes before they are sent. Provider edge
(PE) routers inform the route reflector (RR) which routes to send, using family route-target to provide the
route-target-interest information. The RR then sends to the P... | [
{
"name": "advertise-default",
"desc": "Cause the router to advertise the default route target route (0:0:0/0) and suppress all"
},
{
"name": "external-paths number",
"desc": "Cause the router to advertise the VPN routes that reference a given route target."
},
{
"name": "prefix-limit nu... | 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 BGP Route Target Filtering for VPNs",
"Understanding Proxy BGP Route Target Filtering for VPNs",
"Example: Configuring an Export Policy for BGP Route Target Filtering for VPNs"
] |
family vpls (Layer 2 Pseudowires) | family vpls; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | Specify that the protocol family for the logical interface is VPLS. | [] | router—To view this statement in the configuration.
router-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Applying the Policers to Dynamic Profile Interfaces",
"Creating a Dynamic Profile for the Complex Configuration"
] |
family-state-change-immediate-update | family-state-change-immediate-update family-state-change-immediate-update; | [edit access profile profile-name accounting] | Send an Acct-Update message to notify address family activation state change. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4. | [
"Exchange of DHCPv4 and DHCPv6 Parameters with the RADIUS Server Overview"
] |
fast-aps-switch | fast-aps-switch; | [edit interfaces interface-name sonet-options aps] | (M320 routers with Channelized OC3/STM1 Circuit Emulation PIC with SFP only, EX Series switches,
and MX series routers with Channelized OC3/STM1 Circuit Emulation PIC with SFP only using
container interfaces) Reduce the Automatic Protection Switching (APS) switchover time in Layer 2
circuits.
NOTE:
•
The fast APS swit... | [] | 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. | [
"Reducing APS Switchover Time in Layer 2 Circuits"
] |
fast-failover | fast-failover (ge | vcp disable | xe); | [edit virtual-chassis] | Enable the fast failover feature on an uplink Virtual Chassis port (VCP).
Fast failover is not supported on an EX2200 Virtual Chassis or EX8200 Virtual Chassis.
Default
Fast failover is enabled, by default, on dedicated VCPs.
Fast failover is not enabled on uplink VCPs, including the uplink ports that are, by default, ... | [
{
"name": "ge",
"desc": "Enable fast failover on all Gigabit Ethernet uplink VCPs in the ring topology."
},
{
"name": "vcp disable",
"desc": "Disable fast failover on all dedicated VCPs in the ring topology."
},
{
"name": "xe",
"desc": "Enable fast failover on all 10-Gigabit Ethernet... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When an EX4200",
"Virtual Chassis Switch or Intermember Link Fails",
"Configuring Fast Failover in an EX Series Virtual Chassis",
"Disabling Fast Failover in an EX Series Virtual Chassis"
] |
fast-interval | fast-interval milliseconds; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
fam... | Configure the interval, in milliseconds, between Virtual Router Redundancy Protocol (VRRP)
advertisement packets.
All routers in the VRRP group must use the same advertisement interval. | [
{
"name": "milliseconds",
"desc": "Interval between advertisement packets."
}
] | 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 Advertisement Interval for the VRRP Primary Router"
] |
fast-lookup-filter (Protocols BGP) | fast-lookup-filter | no-fast-lookup-filter; | [edit logical-systems name routing-instances name routing-options flow],
[edit logical-systems name routing-options flow],
[edit logical-systems name tenants name routing-instances name routing-options flow],
[edit routing-instances name routing-options flow],
[edit routing-options flow] | As BGP flowspec filters grow, they can sometimes cause congestion or packet drops. You can enable the
fast lookup for the BGP flowspec filters to perform a parallel lookup, which can significantly improve
packet throughput and filter performance.
NOTE: Currently we support fast lookup only on MX Series devices with MPC... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [
"Example: Enabling BGP to Carry Flow-Specification Routes"
] |
fast-lookup-filter (PTX) | fast-lookup-filter | [edit firewall family family-name filter output filter-name],
[edit logical-systems logical-system-name firewall family family-name filter output filter-name] | On PTX platforms, the fast-lookup-filter (FFT) is available on Inet, Inet 6, Ethernet-Switching, Any, MPLS
(no MPLS label match support) and CCC firewall filter families. Using fast-lookup-filter on output filters
prioritizes the filters for fast processing. Applying the fast-lookup-filter configuration on output firew... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved 23.1 R1 for PTX platforms. | [
"fast-lookup-filter"
] |
fast-lookup-filter | fast-lookup-filter; | [edit firewall family family-name filter filter-name],
[edit logical-systems logical-system-name firewall family family-name filter filter-name] | 15.1
Support for MPC2E-NG and MPC3E-NG MPCs was added in Junos OS Release 15.1R1.
13.3R6
Support for the next-header firewall match condition was added in Junos OS Release 13.3R6
13.3R3
Statement introduced in Junos OS Release 13.3R3 for MX 240, MX 480, MX 960, MX 2010, and MX
2020 routers with MPC5E, MPC5EQ, or MPC6E, | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3R3 for MX 240, MX 480, MX 960, MX 2010, and MX
2020 routers with MPC5E, MPC5EQ, or MPC6E, and later for MPC7E, MPC8E, and MPC9E MPCs.
Support for the next-header firewall match condition was added in Junos OS Release 13.3R6
Support for MPC2E-NG and MPC3E-NG MPCs was added in... | [
"MX Series 5G Universal Routing Platform Interface Module Reference",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide",
"MX Series Interface Module Reference manual"
] |
fast-lookup-tuple | fast-lookup-tuple | [edit firewall family inet filter firewall filter name term term name from] | Use fast-lookup-tuple for better firewall filter processing performance by matching exact values of the five
tuple or five combined match conditions. It enables high scale firewall filter performance improvement
with only 5-tuple configurations per term without range configurations by avoiding execution of
multiple ter... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos 24.2 on MX platforms | [] |
fast-lookup-tuple-list (policy-options) | fast-lookup-tuple-list list name | [edit policy-options] | Define a list of fast-lookup-tuple or 5-tuple combinations. In the following example, the five-tuple-list
list has a list of three 5-tuple combinations defined.
policy-options {
fast-lookup-tuple-list five-tuple-list {
10.11.12.13:20.21.22.23:17:168:65534
10.11.12.13:20.21.22.23:17:168:65535
... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos 24.2 on MX platforms | [] |
fast-lookup-tuple-list | fast-lookup-tuple-list list name | [edit firewall family inet filter firewall filter name term term name from] | Match any of the list of 5-tuple (fast-lookup-tuple) combinations. The list is defined under policy
options.
fast-lookup-tuple-list is only for INET firewall filter family. No range of values is supported for each of the
5-tuple fields. fast-lookup-tuple-list can be applied at all bind points including chain filters, l... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos 24.2 on MX platforms | [] |
fast-poe | fast-poe; | [edit poe] | Fast Power over Ethernet (fast PoE) delivers PoE power to devices connected to the ports even before
the switch is fully operational. This is beneficial when the connected devices need only power, and not
network connectivity.
NOTE: Fast PoE is disabled if and when you issue commands to zeroize the switch, do a
USB ins... | [] | system | Statement introduced in Junos OS Release 21.1. | [] |
fast-reroute (Protocols MPLS) | fast-reroute {
(bandwidth bps | bandwidth-percent percentage);
(exclude [ group-names ] | no-exclude );
hop-limit number;
(include-all [ group-names ] | no-include-all);
(include-any [ group-names ] | no-include-any);
} | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Establish detours for the LSP so that if a node or link in the LSP fails, the traffic on the LSP can be
rerouted with minimal packet loss. | [] | 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.
Statement introduced in Junos OS Release 14.1X53-D10 for the QFX Series and for EX4600 switches. | [
"Configuring Fast Reroute",
"Fast Reroute Overview",
"MPLS Feature Support on QFX Series and EX4600 Switches",
"Understanding Interprovider and Carrier-of-Carriers VPNs"
] |
fast-reroute (Protocols RSVP) | fast-reroute optimize-timer seconds; | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Configure the optimize timer for fast reroute. The optimize timer triggers a periodic optimization
process that recomputes the fast reroute detour LSPs to use network resources more efficiently. | [
{
"name": "seconds",
"desc": "Specify the number of seconds between fast reroute detour LSP optimizations."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement added in Junos OS Release 7.5.
Statement introduced in Junos OS Release 14.1. | [
"Configuring the Optimization Interval for Fast Reroute Paths"
] |
fast-reroute-priority | fast-reroute-priority (high | low | medium); | [edit forwarding-options]
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options],
[edit routing-instances routing-instance-name forwarding-options] | Specify the fast reroute priority for a VPLS routing instance. You can configure high, medium, or low fast
reroute priority to prioritize specific VPLS routing instances for faster convergence and traffic
restoration. Because the router repairs next hops for high-priority VPLS routing instances first, the
traffic trave... | [
{
"name": "high",
"desc": "Set the fast reroute priority for a VPLS routing instance to high. During a fast reroute event, the"
},
{
"name": "low",
"desc": "Set the fast reroute priority for a VPLS routing instance to low, which is the default. During a fast"
},
{
"name": "medium",
"... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring VPLS Fast Reroute Priority"
] |
fast-synchronize | fast-synchronize; | [edit system commit] | 25.4R1
Starting in Junos OS and Junos OS Evolved 25.4R1, we support fast-synchronize commit model as the
default commit model for all Junos OS and Junos OS Evolved dual Routing Engine devices, EX Series
Virtual Chassis, and MX Series Virtual Chassis. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.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 | [
"Configuring Multiple Routing Engines to Synchronize Committed Configurations Automatically"
] |
fast-update-filter (Dynamic Firewalls) | fast-update-filter filter-name {
interface-specific;
match-order [match-order];
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
only-at-create;
}
} | [edit dynamic-profiles profile-name firewall family family] | Configure fast update firewall filters in a dynamic profile. | [
{
"name": "filter-name",
"desc": "Name that identifies the filter. The name can contain letters, numbers, and hyphens (-) and"
}
] | 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. | [
"Configuring Fast Update Filters"
] |
fastether-options | fastether-options {
802.3ad {
aex (primary | backup);
lacp {
port-priority;
}
}
(flow-control | no-flow-control);
ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
... | [edit interfaces interface-name] | Configure Fast Ethernet-specific interface properties.
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. | [
"Ethernet Interfaces Overview"
] |
fatal | fatal {
threshold threshold-value;
action (chassis error) {
alarm;
disable-pfe;
get-state;
log;
offline;
reset;
}
} | [edit chassis fpc slot-number error ],
[edit chassis] | Severity level of the error. An error that results in blockage of considerable amount of traffic across
modules is a fatal error. The severity level of an error cannot be configured by a user.
The other statements are explained separately. | [] | interface
To view this statement in the configuration.
interface-control
To add this statement to the configuration. | Statement introduced for PTX Series routers in Junos OS Release 13.3.
Statement introduced for MX240, MX480, MX960, and MX2020 routers in Junos OS Release 14.2. | [
"Fabric Resiliency",
"Managing Errors"
] |
fate-sharing | fate-sharing {
group group-name {
cost value;
from address <to address>;
use-for-post-convergence-lfa; }
} | [edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit routing-options],
[edit routing-instances routing-instance-name routing-options] | Specify a backup path in case the primary path becomes unusable.
You specify one or more objects with common characteristics within a group. All objects are treated
as /32 host addresses. The objects can be a LAN interface, a router ID, or a point-to-point link.
Sequence is insignificant.
Changing the fate-sharing data... | [
{
"name": "cost value",
"desc": "Cost assigned to the group."
},
{
"name": "from address",
"desc": "Address of the router or address of the LAN/NBMA interface. For example, an Ethernet"
},
{
"name": "group group-name",
"desc": "Each fate-sharing group must have a name, which can have... | 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 Alternate Backup Paths Using Fate Sharing",
"MPLS Applications User Guide"
] |
fc2 | fc2 {
traceoptions {
file filename <replace> <size size> <files number> <no-stamp>;
<world-readable | no-world-readable>;
flag flag <flag-modifier>;
}
} | [edit fc-fabrics fc-fabric-name] | 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. | [] | |
fc-fabrics | fc-fabrics {
fc-fabric-name {
description
fabric-id fc-fabric-id;
fabric-type proxy;
interface {
interface-name {
max-login-sessions max-login-sessions;
}
interface-name {
max-login-sessions max-login-sessions;
... | [edit] | 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": "fc-fabric-name",
"desc": "Unique name of the FC fabric."
}
] | 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 VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch",
"Configuring a Physical Fibre Channel Interface",
"Converting an Ethernet Interface To a Fibre Channel Interface",
"Configuring an FCoE VLAN Interface on an FCoE-FC Gateway",
"Assigning Interfaces to a Fibre Channel... |
fc-map | fc-map fc-map-value; | Original CLI
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name) examine-fip]
ELS CLI for Platforms that Support FCoE
[edit vlans vlan-name forwarding-options fip-security]
NOTE: The fc-map configuration statement is in a different hierarchy on the original CLI
than on the Enhanced Layer 2 Softw... | Set the FCoE mapped address prefix (FC-MAP) value for the FCoE VLAN to match the FC switch (or
FCoE forwarder) FC-MAP value for the FC fabric. The FC-MAP value is a unique MAC address prefix an
FC switch uses to identify FCoE traffic for a given FC fabric (traffic on a particular FCoE VLAN).
You can configure the FC-MA... | [
{
"name": "fc-map-value",
"desc": "FC-MAP value, hexadecimal value preceded by “0x”."
},
{
"name": "0x0EFD00 for VN2VN_Port FIP snooping",
"desc": ""
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Statement introduced for the ELS CLI in Junos OS Release 13.2 for the QFX Series. | [
"examine-fip",
"Example: Configuring an FCoE Transit Switch",
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch"
] |
fc-options | fc-options
max-login-sessions-per-node max-login-sessions-per-node;
no-fip-snooping-scaling;
traceoptions {
file filename <replace> <size size> <files number> <no-stamp>;
<world-readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
} | [edit] | 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... | [] | 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.
Statement no-fip-snooping-scaling introduced in Junos OS Release 13.2X52-D10 for the QFabric system. | [] |
fcoe | fcoe {
no-auto-negotiation;
} | [edit protocols dcbx interface interface-name applications] | Disable advertising the FCoE state of the interface to the peer. To disable FCoE on the interface, do not
configure the FCoE forwarding class on the interface. | [
{
"name": "no-auto-negotiate",
"desc": "Disable automatic negotiation of FCoE capability."
}
] | 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. | [
"Understanding DCB Features and Requirements",
"Understanding DCB Features and Requirements on EX Series Switches"
] |
fcoe-lag | fcoe-lag; | [edit interfaces lag-interface-name aggregated-ether-options] | Configure a special link aggregation group (LAG) to transport Fibre Channel over Ethernet (FCoE) traffic
and regular Ethernet traffic across the same link aggregation bundle.
An FCoE LAG ensures that FCoE traffic uses the same link within a LAG to transmit and receive
information between an FCoE device and a Fibre Chan... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Configuring an FCoE LAG",
"Configuring VLANs for FCoE Traffic on an FCoE Transit Switch",
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch",
"Understanding FCoE LAGs"
] |
fcoe-trusted | fcoe-trusted; | Original CLI
[edit ethernet-switching-options secure-access-port interface interface-name]
ELS CLI for Platforms that Support FCoE
[edit vlans vlan-name forwarding-options fip-security interface interface-name]
NOTE: The fcoe-trusted configuration statement is in a different hierarchy on the original
CLI than on the En... | Configure the specified 10-Gigabit Ethernet interface to trust Fibre Channel over Ethernet (FCoE) traffic.
If an interface is connected to another switch such as an FCoE forwarder (FCF) or a transit switch, you
can configure the interface as trusted so that the interface forwards FCoE traffic from the switch to the
FCo... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Statement introduced for the FC fabric in Junos OS Release 11.3 for the QFX Series.
Statement introduced for the ELS CLI in Junos OS Release 13.2 for the QFX Series. | [
"Example: Configuring an FCoE Transit Switch",
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch",
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch"
] |
feature-profile | feature-profile {
anti-spam {
address-blacklist list-name;
address-whitelist list-name;
sbl {
profile profile-name {
custom-tag-string [string];
(sbl-default-server | no-sbl-default-server);
spam-action (block | tag-header | tag-su... | [edit security utm default-configuration]
[edit security utm] | 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... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Starting in Junos OS Release 21.4R1, content evaluation is based of the file content. The file type-based
evaluation of content is deprecated and the related configurations are hidden. So, the content filtering
options in this hierarchy is deprecated and not supported from Junos OS Release 21.4R1.
You can use the legac... | [
"UTM Supported Features"
] |
features (VNF) | features {
hugepages;
} | [edit virtual-network-functions] | Displays the supported features of a VNF. | [
{
"name": "features",
"desc": "Features of a VNF."
},
{
"name": "hugepages",
"desc": "Option to support memory pages with a size of 2 MB and 1 GB."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.