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 |
|---|---|---|---|---|---|---|---|
flow-server | flow-server hostname {
aggregation {
autonomous-system;
destination-prefix;
protocol-port;
source-destination-prefix {
caida-compliant;
}
source-prefix;
}
autonomous-system-type (origin | peer);
dscp dscp-value;
forwarding-class class-name;... | [edit forwarding-options sampling instance instance-name family (inet | inet6 | mpls | vpls |
bridge) output],
[edit forwarding-options sampling family (inet | inet6 | mpls | vpls | bridge) output] | Configure a server to either:
•
Collect an aggregate of sampled flows and send the aggregate to a specified host system that runs
the collection utility cfdcollect, or
•
Specify a host system to collect sampled flows using the version 9 or IPFIX format.
You can configure up to one version 5 and one version 8 flow form... | [
{
"name": "hostname",
"desc": "IP address–IPv4 or IPv6–or identifier of the host system (the workstation either running the"
}
] | 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.
version9 statement introduced in Junos OS Release 8.3.
Support at the following hierarchy levels introduced in Junos OS Release 18.2R1: [edit forwarding-options
sampling instance instance-name family bridge], , [edit forwarding-options sampling family bridge].
Support f... | [
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
flow-session | flow-session {
maximum amount;
reserved amount;
} | [edit system security-profile] | Specifies the number of flow sessions that user logical system administrators and primary logical system
administrators configure for their logical systems if the security profile is bound to the logical systems.
The primary administrator:
•
uses security profiles to provision logical systems with resources.
•
binds s... | [
{
"name": "maximum",
"desc": ""
},
{
"name": "amount",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows, it can utilize resources configured for the global maximum amount if they"
},
{
"name": "are available",
"desc": "... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems Security Profiles (Primary Administrators Only)",
"Example: Configuring Logical Systems Security Profiles (Primary Administrators Only)"
] |
flow-specs | flow-specs {
flow-specification-name {
ethernet-frame-size ethernet-frame-size;
multicast-ipv4 {
dest-ip-multicast-group ipv4-mcast-address;
source-ip ipv4-address;
}
multicast-vlan-flood;
unicast-ethernet {
destination-mac destination-mac-... | [edit protocols oam fabric] | Configure the fabric flow specification parameters for internal fabric monitoring. The following
conditions apply:
•
You must specify a protocol type for each flow specification: unicast-ethernet, unicast-ethernet-ipv4,
multicast-ipv4, or multicast-vlan-flood.
•
You can specify only one type for each flow specification... | [
{
"name": "flow-specification-name",
"desc": "Name of the flow specification. Syntax: 1 to 20 alphanumeric characters"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
flow-table-size (Chassis) | flow-table-size size; | [edit chassis fpc slot inline-video-monitoring] | Configure the number of video flows that can be measured per Packet Forwarding Engine by an MPC at
a given time. This value takes effect the next time the MPC is rebooted. | [
{
"name": "size",
"desc": "Number of video flows per Packet Forwarding Engine. Range: 16 through 8192"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Inline Video Monitoring on MX Series Routers"
] |
flow-table-size | flow-table-size {
ipv4-flow-table-size units;
ipv6-extended-attrib;
ipv6-flow-table-size units;
mpls-flow-table-size units;
vpls-flow-table-size units;
} | [edit chassis fpc slot-number inline-services] | Configure the size of hash tables in units of 256K entries for inline services sampling. You cannot
configure the size of the flow hash table for ACX Series routers running Junos OS Evolved.
Starting with Junos OS Release 15.1F2, by default, the software allocates one 1K IPv4 flow table. To
allocate 15 256K IPv4 flow ... | [] | 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.
ipv6-extended-attrib option added in Junos OS Release 14.2 for MX Series routers.
vpls-flow-table-size option added in Junos OS Release 13.2 for MX Series routers.
bridge-flow-table-size option added in Junos OS Release 18.2R1 for MX Series routers, replacing the vpls-
flo... | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250",
"Including Fragmentation Identifier and IPv6 Extension Header Elements in IPFIX Templates on MX",
"Series Routers"
] |
flow-tap | flow-tap {
(interface interface-name | tunnel-interface interface-name);
family (inet | inet6);
} | [edit services] | 17.3R1
Starting in Junos OS Release 17.3R1, the FlowTapLite service can run concurrently with the radius-flow-
tap service on the same MX Series router. | [
{
"name": "interface",
"desc": ""
},
{
"name": "interface-name",
"desc": "Use the specified interface for the FlowTap application."
},
{
"name": "tunnel-interface",
"desc": ""
},
{
"name": "interface-name",
"desc": "Use the specified tunnel interface for the FlowTapLite a... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
ccc option introduced in Junos OS Release 17.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 Junos Packet Vision on MX, M and T Series Routers"
] |
flow-tap-dtcp | flow-tap-dtcp {
ssh {
connection-limit limit;
rate-limit limit;
}
} | [edit system services] | Configure Dynamic Tasking Control Protocol (DTCP) sessions to run over SSH in support of the flow-tap,
FlowTapLite, or radius-flow-tap services. Note that the flow-tap feature is not supported on outbound,
or egress, traffic. Only inbound, or ingress, traffic is supported.
This statement is required for DTCP-initiated ... | [
{
"name": "connection-limit limit",
"desc": "(Optional) Maximum number of connections allowed."
},
{
"name": "rate-limit limit",
"desc": "(Optional) Maximum number of connection attempts allowed per minute."
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring a DTCP-over-SSH Connection to the Mediation Device",
"Configuring Flow-Tap Security Properties on MX, M and T Series Routers",
"Configuring FlowTapLite on MX Series Routers and M320 Routers with FPCs",
"Configuring DTCP-over-SSH Service for the Flow-Tap Application"
] |
flow-timeout-time (DDoS Flow Detection) | flow-timeout-time seconds; | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure the period of time that a culprit flow is suppressed for the packet type. The timeout period is
effective only when timing out has been enabled with the "timeout-active-flows" on page 30520
statement. | [
{
"name": "seconds",
"desc": "Period that the traffic is suppressed."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Timeout Period for a Culprit Flow",
"Setting Up and Using Flow Detection"
] |
flows (PCC Rules) | flows ([flow-identifier] | any); | [edit unified-edge pcef pcc-rules rule-name from],
[edit services pcef pcc-rules rule-name from] | Specify the service data flow (SDF) filters (flow identifiers) that define the match criteria for the policy
and charging control (PCC) rule. You can configure a maximum of 15 SDF filters. You must include the
flows statement in a PCC rule. If you do not want to filter subscriber traffic based on SDF filters, use the
a... | [
{
"name": "flow-identifier",
"desc": "Name of an SDF filter that is used to detect IP packet flows. You can configure a maximum of 15 SDF filters. The referenced SDF filters must be configured. Range: 1 through 63 characters."
},
{
"name": "any",
"desc": "All IP packet flows."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-rules rule-name from] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Junos OS
Rel... | [
"Configuring Policy and Charging Control Rules",
"Configuring Service Data Flow Filters"
] |
flowspec-attribute | flowspec-attribute name {
action {
mark;
rate-limit;
redirect;
routing-instance;
sample;
}
invert-match {
destination;
destination-port {
port-range port-range-value {
contains;
exact;
part-of... | [edit logical-systems name policy-options],
[edit policy-options] | Attributes of a flow specification. Use in configuring policies to match certain conditions and take policy
actions (accept/reject) accordingly for validating the flow specifications at the edge routers. | [
{
"name": "name",
"desc": "Flowspec attribute name"
},
{
"name": "action",
"desc": "Define flowspec action attributes"
},
{
"name": "mark",
"desc": "Flowspec action traffic-mark"
},
{
"name": "rate-limit",
"desc": "Flowspec action rate-limit"
},
{
"name": "redirec... | Routing — To view this statement in the configuration.
routing-control — To add this statement to the configuration | Statement introduced in Junos OS Release 25.2. | [
"No Link Title"
] |
fnp | fnp {
interval <100ms | 1s | 10s | 1m | 10m>;;
loss-threshold number
interface interface name {
domain-id domain-id
}
} | [edit protocols oam ethernet] | On routers with ge, xe, or ae interfaces, configure an OAM Ethernet failure notification protocol. | [
{
"name": "interval number",
"desc": "Specifies the time between the transmission of FNP messages."
},
{
"name": "loss-threshold number",
"desc": "FNP messages that can be lost before the FNP message is considered aged out and"
},
{
"name": "interface interface-name",
"desc": "Name o... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 11.4. | [
"Ethernet Failure Notification Protocol Overview",
"Configuring the Failure Notification Protocol"
] |
force switch | request protection-group ethernet-aps force-switch md <md> ma <ma> | [edit protocols protection-group ethernet-aps] | Forces traffic to switch from the active path to the alternate path. If the working path is the active path,
traffic will be switched to the protection path. If the protection path is the active path, traffic will be
switched to the protection path. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Ethernet Automatic Protection Switching Overview"
] | |
force-continue (OCS Partition) | force-continue; | [edit access ocs partition partition-name] | Enable subscriber traffic to flow before the first interrogation with the Online Charging System (OCS)
occurs.
Wireline customers often control user services solely through the Policy Control and Charging Rules
Function (PCRF) and use the OCS as a convenient real-time usage monitoring mechanism rather than as
an enforc... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"3GPP Policy and Charging Control Overview for Wireline Provisioning and Accounting",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between t... |
force-control-packets-on-transit-path | force-control-packets-on-transit-path; | [edit interfaces interface-name unit logical-unit-number] | Force host-injected control packets to follow the transit path. Host-injected control traffic reaches the
GRE tunnel interface queues at the PFE when the control session is over the GRE tunnel interface. This
includes control protocols OSPF, BGP, PIM, RSVP, LDP, OAM, BFD and MSDP.
Injection of control traffic ensures t... | [] | interface | Statement introduced in Junos OS Release 20.1R1. | [] |
force-discover (DHCP Client) | force-discover; | [edit interfaces interface-name unit logical-unit-number dhcp-client] | Forces the DHCP client to send a DHCP discover packet after one to three failed dhcp-request attempts.
The force-discover option ensures that the DHCP server will assign the same or a new IP address to the
client. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D80.
Starting with Junos OS Release 17.3R1, on all SRX Series Firewalls and vSRX Virtual Firewall instances,
the CLI option dhcp-client at [edit interfaces interface-name unit logical-unit-number family inet] hierarchy is
changed to dhcp to keep consistent with other Jun... | [
"DHCP Client",
"DHCPv6 Client",
"Minimum DHCP Client Configuration"
] |
force-entry (IDS MS-DPC) | (force-entry | ignore-entry); | [edit services ids rule rule-name term term-name then] | Specify handling of entries in the IDS events cache when using the MS-DPC:
•
force-entry—Ensure that the entry has a permanent place in the IDS cache after one event is
registered.
•
ignore-entry—Ensure that all IDS events are ignored. | [] | 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 Actions in IDS Rules"
] |
force-fbf-terms | force-fbf-terms | [edit system packet-forwarding-options firewall] | When a firewall filter is configured with two terms; the first term without filter based forwarding action,
and the second term with a filter based forwarding action, the packet is assigned the routing instance
specified by the filter based forwarding action in the second term. This happens even if the first term is
co... | [] | firewall – To view this statement in the configuration
firewall-control - To add this statement to the configuration | Statement introduced in Junos OS Evolved Release 24.4R1 | [] |
force-ip-reassembly | force-ip-reassembly; | [edit security flow] | Reassemble all IP fragmented packets before forwarding.
This option is disabled by default. You can disable this option by deleting this flag from the CLI.
Force reassembly happens when all the fragment packets are received, and the session has been created
(first path) or session has been matched (fast path) in the se... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Traffic Processing on Security Devices"
] |
force-premium (Firewall Filter Action) | force-premium; | [edit firewall family family-name filter filter-name term term-name then],
[edit logical-systems logical-system-name firewall family family-name filter filter-name term term-
name then] | Firewall filter option to force premium treatment for traffic (MX Series routers)— By default, a
hierarchical policer processes the traffic it receives according to the traffic’s forwarding class. Premium,
expedited-forwarding traffic has priority for bandwidth over aggregate, best-effort traffic. Now you can
include t... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3 for family inet and inet6.
Support for family vpls, ccc, and bridge added in Junos OS Releases 13.3R8, 13.3R10, 14.1R8, 14.2R7,
15.1R4,16.1R1, and 17.1R1. | [
"Firewall Filter Nonterminating Actions"
] |
force-switch | force-switch; | [edit chassis synchronization source (external | interface-name)] | For MX Series routers operating with Synchronous Ethernet, force a router to use the clock source.
provided that the source is enabled and not locked out. Only one configured source may be force-
switched. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2R4. | [] |
force-up (EX and QFX Series) | force-up; | [edit interfaces interface-name ether-options 802.3ad lacp],
[edit interfaces interface-name aggregated-ethernet-options lacp] | Set the state of the interface as UP when the peer has limited LACP capability. | [] | interface— To view this statement in the configuration.
interface-control— To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Understanding Aggregated Ethernet Interfaces and LACP for Switches",
"Configuring Aggregated Ethernet LACP (CLI Procedure)",
"Example: Configuring Link Aggregation with LACP Between a QFX Series Product and an",
"Aggregation Switch",
"Junos OS Network Interfaces Library for Routing Devices",
"Configuring... |
force-up | force-up; | [edit interfaces interface-name aggregated-ethernet-options lacp] | Configure the peer interface (in MC-LAG) to remain up even with limited LACP capability. | [] | interface— To view this statement in the configuration.
interface-control— To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2.
NOTE: For EX9200 switches, you must configure force-up on physical interfaces of both
MC-LAG peers for this feature to work properly. | [
"Forcing MC-LAG Links or Interfaces with Limited LACP Capability to Be Up"
] |
force-version (IEEE 802.1D STP) | force-version stp; | [edit logical-systems logical-system-name protocols (rstp | vstp)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(rstp | vstp)],
[edit protocols (rstp | vstp)],
[edit routing-instances routing-instance-name protocols (rstp | vstp)] | Forces the spanning-tree version to be the original IEEE 802.1D STP protocol. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for logical systems added in Junos OS Release 9.6.
Support for logical systems added in Junos OS Release 9.6. | [] |
format (Flat-File Accounting Options) | format (csv | ipdr); | [edit accounting-options flat-file-profile profile-name] | Specify the format for logging the flat-file accounting statistics. | [
{
"name": "csv",
"desc": "Comma-separated values (CSV) format."
},
{
"name": "ipdr",
"desc": "IP Detail Record (IPDR) format. Default: ipdr"
}
] | 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"
] |
format (LRF Profile) | format ipfix; | [edit services lrf profile profile-name template template-name] | Configure a format for the template. Only the IPFIX format is supported for this release. | [] | 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.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
format (Next Gen Services Service-Set Remote System Logging) | format format; | edit services service-set name syslog stream stream-name | Specify the file format for the log messages being sent to the remote server. | [
{
"name": "binary",
"desc": "Binary syslog defined by Juniper Networks. Requires Juniper Networks decoders on the server side to decode the logs."
},
{
"name": "sd-syslog",
"desc": "Structured syslog (defined by RFC5424)"
},
{
"name": "syslog",
"desc": "Traditional syslog (defined by... | 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"
] |
format (Security Log Stream) | format (binary | protobuf | sd-syslog | syslog | welf) | [edit security log stream stream-name]
[edit logical-systems name security log stream stream-name]
[edit tenants tenant-name security log stream stream-name] | Set the format for remote security message logging to binary, protobuf, syslog (system log), sd-syslog
(structured system log), or welf. Note that for the WELF format, the category must be set to content-
security (see "category" on page 3431).
Use Feature Explorer to confirm platform and release support for specific f... | [
{
"name": "binary",
"desc": "Binary encoded text to conserve resources."
},
{
"name": "protobuf",
"desc": "Protobuf structured log file."
},
{
"name": "sd-syslog",
"desc": "Structured system log file."
},
{
"name": "syslog",
"desc": "Traditional system log file."
},
{... | 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 . Updated in Junos OS Release 12.1 .
The [edit logical-systems name security log stream stream-name] hierarchy level introduced in Junos OS
Release 18.2R1.
The [edit tenants tenant-name security log stream stream-name] hierarchy level introduced in Junos OS
Release 18.3R1. | [
"Application Security User Guide for Security Devices",
"Logical Systems and Tenant Systems User Guide for Security Devices"
] |
format (Security Log) | format (binary | protobuf | sd-syslog | syslog) | [edit security log] | Set the default log format for event mode security logging on the device. | [
{
"name": "binary",
"desc": "Binary encoded text to conserve resources."
},
{
"name": "protobuf",
"desc": "Protobuf structured log file."
},
{
"name": "sd-syslog",
"desc": "Structured system log file."
},
{
"name": "syslog",
"desc": "Traditional system log file."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced prior to Junos OS Release 10.0. Statement updated in Junos OS Release 12.1. | [] |
format (Unified Edge Gateways) | format {
integer {
equals {
value;
}
greater-than value;
less-than value;
}
string {
equals {
value;
}
has-prefix{
value;
}
has-suffix {
value;
}
matches {
valu... | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name] | Specify the custom AVP attribute’s format and value to match for the incoming RADIUS request from
the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
The remaining statem... | [] | 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 Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
forward-and-send-to-re | forward-and-send-to-re; | [edit interfaces interface-name unit logical-unit-number family inet targeted-broadcast],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet targeted-broadcast] | Specify that IP packets destined for a Layer 3 broadcast address be forwarded to an egress interface and
the Routing Engine. The packets are broadcast only if the egress interface is a LAN interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Targeted Broadcast",
"Understanding Targeted Broadcast"
] |
forward-delay | forward-delay seconds; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-ins... | For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol
(VSTP), or Multiple Spanning Tree Protocol (MSTP), specifies the length of time an STP bridge port
remains in the listening and learning states before transitioning to the forwarding state. | [
{
"name": "seconds",
"desc": "(Optional) Number of seconds the bridge port remains in the listening and learning states."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding Forward Delay Before Ports Transition to Forwarding State",
"Understanding STP",
"Understanding MSTP",
"Understanding VSTP",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Configuring Faster Convergence and Network Stability on ELS Switches with RSTP",
"... |
forward-on-source-bridge-domain | forward-on-source-bridge-domain {
forward-policy [ forwarding-policy-name ... ];
} | [edit routing-instances name protocols evpn oism enhanced] | Enable enhanced optimized intersubnet multicast (OISM) to forward multicast data traffic on the
multicast source VLAN for traffic that matches the provided forwarding policy (or policies).
When you configure enhanced OISM, you allocate an OISM supplemental bridge domain (SBD) for each
Layer 3 (L3) virtual routing and f... | [
{
"name": "(Required) forward-policy",
"desc": ""
},
{
"name": "[ forwarding-policy-name ... ]",
"desc": "Routing policy or policies to match multicast groups (or sources and groups) for which the device should forward that multicast traffic on the source VLAN."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 25.2R1. | [
"Enhanced OISM Exception Policy to Forward on Source VLAN Instead of SBD for Packets with",
"TTL=1",
"Overview of Enhanced OISM",
"How Enhanced OISM Works"
] |
forward-only (DHCP Relay Agent Option) | forward-only; | [edit forwarding-options dhcp-relay dhcpv6 relay-option (default-action | equals | starts-with)],
[edit forwarding-options dhcp-relay group group-name relay-option (default-action | equals | starts-
with)],
[edit forwarding-options dhcp-relay dhcpv6 group group-name relay-option (default-action | equals
| starts-with)... | Forward specified DHCP client packets, without creating a new subscriber session, when you use DHCP
relay selective processing feature. You can configure the forwarding operation globally or for a group of
interfaces, and for either DHCP or DHCPv6 relay agent. Use this command to manage subscribers,
when large number o... | [] | 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. | [
"Using DHCP Option Information to Selectively Process DHCP Client Traffic"
] |
forward-only (DHCP Relay Agent) | forward-only {
logical-system <current | default | logical-system-name>;
routing-instance <current | default | routing-instance-name>;
} | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name ... | Specify the VRF location of the DHCP server when configuring secure DHCP traffic between the DHCP
server and DHCP client when the two reside in different VRFs.
Default
Logical system and routing instance from where the configuration is applied. | [
{
"name": "logical-system",
"desc": "(Optional) Logical system in which the DHCP server resides."
},
{
"name": "current",
"desc": "Logical system from which the configuration is applied."
},
{
"name": "default",
"desc": "Root logical system."
},
{
"name": "logical-system-name... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 13.3R3, 14.1R2, and 14.2R1. | [
"DHCP Message Exchange Between DHCP Clients and DHCP Server in Different VRFs",
"Configuring DHCP Message Exchange Between DHCP Server and Clients in Different Virtual Routing",
"Instances"
] |
forward-only (DNS) | forward-only; | [edit system services dns dns-proxy view view-name domain domain-name] | Specify that the server to forward only DNS queries. This configuration prevents the device from
acquiring public IP addresses, in case the IP address specified in forwarders option is not reachable, by
terminating the DNS query. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"DNS Overview"
] |
forward-only | forward-only; | [edit interfaces interface-name unit logical-unit-number family inet targeted-broadcast],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet targeted-broadcast] | Specify that IP packets destined for a Layer 3 broadcast address be forwarded to an egress interface
only. The packets are broadcast only if the egress interface is a LAN interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Targeted Broadcast",
"Understanding Targeted Broadcast"
] |
forward-only-replies (DHCP Relay Agent) | forward-only-replies; | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay ...],
[edit routing-instances routing-instanc... | Specify that reply packets are for the forward-only support that is configured in option 82 interface ID
of the reply packet. You must configure this statement for forward-only support when the client and
server are in different logical system/routing instances. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 13.3R3, 14.1R2, and 14.2R1. | [
"DHCP Message Exchange Between DHCP Clients and DHCP Server in Different VRFs",
"Configuring DHCP Message Exchange Between DHCP Server and Clients in Different Virtual Routing",
"Instances"
] |
forward-policy-mismatch (Security Group VPN Member) | vpn vpn-name {
ike-gateway gateway-number;
group group-number;
match-direction (input);
tunnel mtu mtu-size;
} | [edit security group-vpn member ipsec] | Configure the forward policy mismatch for group VPN member. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Group VPNv2 Overview"
] |
forward-snooped-clients (DHCP Local Server) | forward-snooped-clients (all-interfaces | configured-interfaces | non-configured-interfaces); | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server],
[edit logical-systems logical-system-name system services dhcp-local-server],
[edit routing-instances routing-instance-name system services dhcp-local-server],
[edit system services dhcp-local-server] | Configure how the DHCP local server filters and handles DHCP snooped packets on the specified
interfaces. | [
{
"name": "all-interfaces",
"desc": "Perform the action on all interfaces."
},
{
"name": "configured-interfaces",
"desc": "Perform the action only on interfaces that are configured as part of an interface"
},
{
"name": "non-configured-interfaces",
"desc": "Perform the action only on ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Snooping Support",
"Configuring DHCP Snooped Packets Forwarding Support for DHCP Local Server"
] |
forward-snooped-clients (DHCP Relay Agent) | forward-snooped-clients (all-interfaces | configured-interfaces | non-configured-interfaces); | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name forwarding-options dhcp-relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay],
[edit routing-instances routing-instance-name fo... | Configure how DHCP relay agent filters and handles DHCP snooped packets on the specified interfaces.
The router or switch determines the DHCP snooping action to perform based on a combination of the
forward-snooped-clients configuration and the configuration of either the allow-snooped-clients statement or
the no-allow... | [
{
"name": "all-interfaces",
"desc": "Perform the action on all interfaces."
},
{
"name": "configured-interfaces",
"desc": "Perform the action only on interfaces that are configured as part of an interface"
},
{
"name": "non-configured-interfaces",
"desc": "Perform the action only on ... | 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.
Support at the [edit forwarding-options dhcp-relay dhcpv6] hierarchy level introduced in Junos OS Release
15.1X53-D56 for EX Series switches and Junos OS Release 17.1R1. | [
"DHCP Snooping Support",
"Configuring DHCP Snooped Packets Forwarding Support for DHCP Relay Agent",
"DHCP Snooping for Network Security"
] |
forwarding (Diameter Network Element) | forwarding {
route dne-route-name {
destination realm realm-name <host hostname>;
function function-name <partition partition-name>;
metric route-metric;
}
} | [edit diameter network-element element-name] | Define the criteria that specify which destinations are reachable through the Diameter network element.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
forwarding-cache (Bridge Domains) | forwarding-cache {
threshold suppress value <reuse value>;
} | [edit bridge-domains bridge-domain-name multicast-snooping-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name multicast-snooping-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name multicast-
snooping-opt... | Establish multicast snooping forwarding cache parameter values. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring Multicast Snooping"
] |
forwarding-cache (Flow Maps) | forwarding-cache {
timeout (minutes | never non-discard-entry-only );
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast flow-map flow-map-name],
[edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name],
[edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-nam... | Configure multicast forwarding cache properties for the flow map. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Example: Configuring a Multicast Flow Map"
] |
forwarding-class (BA Classifiers) | forwarding-class class-name {
loss-priority level code-points [ aliases ] [ bit-patterns ];
} | [edit class-of-service classifiers type classifier-name] | Define forwarding class classifier name and option values. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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 Behavior Aggregate Classifiers"
] |
forwarding-class (CoS Host Outbound Traffic) | forwarding-class class-name; | [edit class-of-service host-outbound-traffic] | Specify the name of the forwarding class to which host outbound traffic is assigned on all egress
interfaces. The output queue associated with the forwarding class must be properly configured on all
interfaces. In the case of a restricted interface, the traffic flows through a restricted queue.
For egress interfaces ho... | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for distributed protocol handler traffic introduced in Junos OS Release 13.2. | [
"Understanding How Forwarding Classes Assign Classes to Output Queues",
"Default Routing Engine Protocol Queue Assignments",
"Changing the Default Queuing and Marking of Host Outbound Traffic"
] |
forwarding-class (Dynamic Scheduler Maps) | forwarding-class class-name; | [edit dynamic-profiles profile-name class-of-service scheduler-maps map-name] | Associate a scheduler with a scheduler map. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
forwarding-class (Fibre Channel Interfaces) | forwarding-class lossless-forwarding-class-name; | [edit class-of-service interfaces fibre-channel-interface-name] | Configure a Layer 3 fixed classifier on a Fibre Channel (FC) interface. The fixed classifier places all traffic
received from the FC network into the specified forwarding class. The forwarding class must be lossless.
(That is, the forwarding class must be either the default fcoe or no-loss forwarding class, or the forw... | [
{
"name": "lossless-forwarding-class-name",
"desc": "Name of the lossless forwarding class."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Example: Configuring IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS Classifiers"
] |
forwarding-class (Firewall Filter Action) | forwarding-class class-name; | [edit firewall family family-name filter filter-name term term-name then],
[edit logical-systems logical-system-name firewall family family-name filter filter-name term term-
name then] | Set the forwarding class of incoming packets. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Firewall Filter Nonterminating Actions",
"Policer Color-Marking and Actions",
"Multifield Classification Overview"
] |
forwarding-class (for DHCP Snooping or DAI Packets) | forwarding-class class class-name; | [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) (examine-dhcp | arp-
inspection)] | Assign a user-defined or a predefined forwarding class to the packets that have been checked for DHCP
snooping or dynamic ARP inspection (DAI).
NOTE: To assign a user-defined class, you must first configure the user-defined class by
using the "forwarding-classes" on page 7803 configuration statement at the [edit class-... | [
{
"name": "class-name",
"desc": "Name of the forwarding class. The forwarding class can be one of the predefined"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Example: Prioritizing Snooped and Inspected Packet",
"Understanding Junos OS CoS Components for EX Series Switches",
"Understanding DHCP Snooping (non-ELS)",
"Understanding ARP Spoofing and Inspection"
] |
forwarding-class (Forwarding Policy) | forwarding-class class-name {
discard;
lsp-next-hop [ lsp-regular-expression ];
next-hop [ next-hop-name];
non-labelled-next-hop;
non-lsp-next-hop;
match-next-hop-forwarding-class;
transport-class {
color color;
}
} | [edit class-of-service forwarding-policy next-hop-map map-name]
[edit class-of-service forwarding-policy class class-name classification-override] | Define forwarding class name and associated next hops. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
},
{
"name": "non-labelled-next-hop",
"desc": "Match any non-labelled next hop."
},
{
"name": "match-next-hop-forwarding-class",
"desc": "Match any pre-defined forwarding-class or a forwarding-class that is configured us... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced for QFX10000 Series switches in Junos OS Release 17.1R1.
non-labelled-next-hop option introduced in Junos OS Release 19.1R1 for all platforms.
match-next-hop-forwarding-class option introduced in Junos OS Evolved Release 21.3R1 for PTX10008
platform... | [
"Overriding the Input Classification"
] |
forwarding-class (Fragmentation) | forwarding-class class-name {
drop-timeout milliseconds;
fragment-threshold bytes;
multilink-class number;
no-fragmentation;
} | [edit class-of-service fragmentation-maps map-name] | For Multiservices and Services PICs link services IQ interfaces (lsq) only, define a forwarding class name
and associated fragmentation properties within a fragmentation map.
The fragment-threshold and no-fragmentation statements are mutually exclusive.
Default
If you do not include this statement, the traffic in forwa... | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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 Fragmentation by Forwarding Class"
] |
forwarding-class (Gigabit Ethernet IQ Classifier) | forwarding-class class-name {
loss-priority (high | low);
} | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
output-priority-map classifier premium] | For Gigabit Ethernet IQ interfaces only, define forwarding class name and option values. | [
{
"name": "class-name",
"desc": "Name of forwarding class."
}
] | 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 Gigabit Ethernet Policers",
"Junos OS Class of Service User Guide for Routing Devices"
] |
forwarding-class (Interfaces) | forwarding-class class-name; | [edit class-of-service interfaces interface-name unit logical-unit-number] | Associate a forwarding class configuration or default mapping with a specific interface. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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 Classes to Interfaces"
] |
forwarding-class (Multifield Classifiers) | forwarding-class class-name; | [edit firewall family family-name filter filter-name term term-name then] | Set the forwarding class of incoming packets. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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"
] |
forwarding-class (PCC Action Profiles) | forwarding-class class-name; | [edit unified-edge pcef pcc-action-profiles profile-name],
[edit services pcef pcc-action-profiles profile-name] | Specify the forwarding class to which packets must be assigned.
If you are using Junos OS Subscriber Aware, specify the forwarding class at the [edit unified-edge pcef
pcc-action-profiles profile-name] hierarchy level.
If you are using Junos OS Broadband Subscriber Management, specify the forwarding class at the [edit
... | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Juno... | [
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management",
"Configuring Policy and Charging Control Act... |
forwarding-class (Restricted Queues) | forwarding-class class-name queue queue-number; | [edit class-of-service restricted-queues] | For M320 and T Series routers only, map forwarding classes to restricted queues. You can map up to
eight forwarding classes to restricted queues. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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. | [] |
forwarding-class (RFC 2544 Benchmarking) | forwarding-class class-name; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Specify the forwarding class to be used for test frames. The forwarding class specifies the manner in
which the test frames are processed by the Packet Forwarding Engine of the router. If you do not
configure this parameter, test frames are treated as best-effort traffic. | [
{
"name": "class-name",
"desc": "Name of the forwarding class. You must have previously configured this forwarding class by including the forwarding-class statement at the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
forwarding-class (Sampling) | forwarding-class class-name; | [edit forwarding-options sampling instance instance-name family (inet | inet6) output flow-
server hostname] | Specify the forwarding class to which exported packets for inline active flow monitoring are sent.
Default
If you do not include the forwarding-class statement, exported packets are sent to the best effort queue. | [
{
"name": "forwarding-class class-name",
"desc": "Name of the forwarding class:"
},
{
"name": "assured-forwarding",
"desc": ""
},
{
"name": "best-effort",
"desc": ""
},
{
"name": "expedited-forwarding",
"desc": ""
},
{
"name": "network-control",
"desc": ""
}... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Sampling Instance on MX, M and T Series Routers or QFX Series Switches"
] |
forwarding-class (Services CoS Fragmentation Properties) | forwarding-class class-name {
(fragment-threshold bytes | no-fragmentation);
multilink-class number;
} | [edit class-of-service fragmentation-maps] | For link services IQ (lsq) interfaces only, define a forwarding class name and associated fragmentation
properties within a fragmentation map.
The fragment-threshold and no-fragmentation statements are mutually exclusive.
Default
If you do not include this statement, the traffic in forwarding class class-name is fragme... | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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 CoS Fragmentation by Forwarding Class on LSQ Interfaces"
] |
forwarding-class (Services PIC Classifiers) | forwarding-class class-name; | [edit services cos application-profile profile-name (ftp | sip) (data | video | voice)],
[edit services cos rule rule-name term term-name then],
[edit services cos rule rule-name term term-name then reflexive | revert | reverse] | Define the forwarding class to which packets are assigned. | [
{
"name": "class-name",
"desc": "Name of the target application."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring CoS Rules on Services PICs"
] |
forwarding-class | [edit class-of-service host-outbound-traffic] | Map forwarding class names and option values to other CoS objects.
•
Classifiers—Assign incoming traffic to the specified forwarding class based on the specified code
point values and assign that traffic the specified loss priority.
•
Rewrite rules—At the egress interface, change (rewrite) the value of the code point b... | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
}
] | 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 CoS on EX Series Switches",
"Defining CoS Forwarding Classes (CLI Procedure)",
"Defining CoS Forwarding Classes (J-Web Procedure)",
"Understanding CoS Forwarding Classes"
] | |
forwarding-class-accounting | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number] | Forwarding class accounting (non-enhanced mode) is enabled for IPv4, IPv6, MPLS, Layer 2 and other
packets simply by enabling the feature.
NOTE: Forwarding class accounting (enhanced mode) is not supported in "hyper-mode
(forwarding-options)" on page 8593.
Both bytes and packet total are counted. For Layer 2 traffic, o... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Forwarding class accounting statement (non-enhanced mode) introduced in Junos OS Release 13.3R3.
Enhanced CoS Accounting statement introduced in Junos OS Release 14.1. | [
"CoS-Based Interface Counters for IPv4 or IPv6 Aggregate on Layer 2"
] | |
forwarding-class-default (Forwarding Policy) | forwarding-class-default class-name {
discard;
lsp-next-hop [ lsp-regular-expression ];
next-hop [ next-hop-name];
non-lsp-next-hop;
match-next-hop-forwarding-class;
} | [edit class-of-service forwarding-policy next-hop-map map-name] | Define the next hop for traffic that does not meet any forwarding class in the next-hop map. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
},
{
"name": "match-next-hop-forwarding-class",
"desc": "Match any pre-defined forwarding-class or a forwarding-class that is"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Statement introduced for QFX10000 Series switches in Junos OS Release 17.1R1.
match-next-hop-forwarding-class option introduced in Junos OS Evolved Release 21.3R1 for PTX10008
platform. | [
"Load Balancing VPLS Non-Unicast Traffic Across Member Links of an Aggregate Interface"
] |
forwarding-class-set (Interconnect Device) | forwarding-class-set fabric-forwarding-class-set-name {
scheduler scheduler-name;
} | [edit class-of-service scheduler-map-forwarding-class-sets scheduler-map-fcset-name] | Specify an existing fabric forwarding class set to map to a scheduler. The scheduler provides bandwidth
and drop profile characteristics for all of the forwarding classes assigned to the forwarding class set. | [
{
"name": "fabric-fowarding-class-set-name",
"desc": "Name of the fabric forwarding class set."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1R2. | [
"Example: Configuring CoS Scheduling Across the QFabric System",
"Understanding CoS Fabric Forwarding Class Sets",
"Understanding CoS Scheduling Across the QFabric System"
] |
forwarding-class-set | forwarding-class-set forwarding-class-set-name {
output-traffic-control-profile profile-name;
} | [edit class-of-service interfaces interface-name] | Apply a previously defined forwarding class set to an output traffic control profile. | [
{
"name": "fowarding-class-set-name",
"desc": "Name of the forwarding class set."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Assigning CoS Components to Interfaces",
"Understanding CoS Forwarding Class Sets (Priority Groups)"
] |
forwarding-class-sets | forwarding-class-sets forwarding-class-set-name {
class class-name;
} | [edit class-of-service] | Assign forwarding classes to forwarding class sets (priority groups). | [
{
"name": "fowarding-class-set-name",
"desc": "Name of the forwarding class set."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Example: Configuring Forwarding Class Sets",
"Understanding CoS Forwarding Class Sets (Priority Groups)"
] |
forwarding-classes | [edit class-of-service] | Define forwarding class names and accociate with queue numbers.
SRX Series Firewalls
All traffic traversing the SRX Series Firewall is passed to an SPC to have service processing applied.
Junos OS provides a configuration option to enable packets with specific Differentiated Services
(DiffServ) code points (DSCP) prec... | [
{
"name": "class class-name",
"desc": "Define the forwarding class name."
},
{
"name": "queue-num queue-number",
"desc": "Output queue number to associate with forwarding class."
},
{
"name": "priority",
"desc": "Fabric priority value:"
},
{
"name": "high",
"desc": "Forwa... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | The policing-priority option was introduced in Junos OS Release 9.5.
Statement updated in Junos OS Release 11.4.
The spu-priority option was introduced in Junos OS Release 11.4R2.
The no-loss option was introduced in Junos OS Release 12.3.
Change from two to four queues made in Junos OS Release 12.3X48-D40 and in Junos... | [
"Configuring a Custom Forwarding Class for Each Queue",
"Forwarding Classes and Fabric Priority Queues",
"Configuring Hierarchical Layer 2 Policers on IQE PICs",
"Classifying Packets by Egress Interface"
] | |
forwarding-context (Protocols BGP) | forwarding-context forwarding-context; | [edit logical-systems name protocols bgp],
[edit logical-systems name routing-instances name protocols bgp],
[edit logical-systems name tenants name routing-instances name protocols bgp],
[edit protocols bgp],
[edit protocols bgp group name neighbor name],
[edit routing-instances name protocols bgp],
[edit tenants name... | The MPLS-forwarding type routing-instance can be used for segregating Inter-AS BGP neighbors that
require MPLS spoof-protection to ensure the packets remain distinct from other peers.
Setting a forwarding context on a neighbor interface can be useful, for example, when configuring a
common AS boundary router so that i... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Example: Preventing BGP Session Resets",
"Junos OS Administration Library for Routing Devices"
] |
forwarding-db-size | forwarding-db-size size; | [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-
provider] | Configure the size of the forwarding database (FDB). When this setting is changed, the PIC reboots.
NOTE: You need to enable the forwarding-options sampling statement for the FDB to be
created. | [
{
"name": "size",
"desc": "Size of the FDB, in megabytes (MB). The size of the FDB and the size of the policy database"
}
] | 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. | [] |
forwarding-instance | forwarding-instance {
identifier identifier;
} | [edit routing-instances mac-vrf-routing-instance-name],
[edit tenants tenant-name routing-instances mac-vrf-routing-instance-name] | QFX10000 line of switches, and ACX7100-32C, and ACX7100-48L devices—Configure the forwarding-
instance parameters for a MAC-VRF routing instance.
If you configure the forwarding instance with an identifier, then the switch maps the specified MAC-VRF
routing instance to the forwarding instance specified by the identifi... | [
{
"name": "identifier",
"desc": ""
},
{
"name": "forwarding-instance-",
"desc": ""
},
{
"name": "identifier",
"desc": "Forwarding instance identifier. Specify the forwarding instance identifier as an integer value. QFX10000 line of switches: Identifier number range is 1 - 99. ACX7100... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"MAC-VRF Routing Instance Type Overview",
"Overlapping VLAN Support Using Multiple Forwarding Instances or VLAN Normalization"
] |
forwarding-mode (100-Gigabit Ethernet) | forwarding-mode {
(sa-multicast | ...the following vlan-steering statement...);
vlan-steering {
vlan-rule (high-low | odd-even);
}
} | [edit chassis fpc slot pic slot] | Configure the interoperation mode for 100-Gigabit Ethernet PIC or the 100-Gigabit Ethernet MIC.
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 10.4.
Statement introduced in Junos OS Release 12.1 for MX Series routers. | [
"Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP",
"Configuring 100-Gigabit Ethernet MICs to Interoperate with Type 4 100-Gigabit Ethernet PICs",
"(PD-1CE-CFP-FPC4) Using SA Multicast Mode",
"Interoperability Between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4 and PF-1CGE-CFP",
... |
forwarding-mode (PTX Series Packet Transport Routers) | forwarding-mode {
sa-multicast
} | [edit chassis fpc slot pic slot port port-number] | Configure interoperability between 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4 and P1-
PTX-2-100GE-CFP.
The remaining statement is 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 12.1X48R4. | [
"Configuring the Interoperability Between the 100-Gigabit Ethernet PICs P1-PTX-2-100GE-CFP and",
"PD-1CE-CFP-FPC4",
"Interoperability Between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4 and PF-1CGE-CFP",
"Configuring the Interoperability Between the 100-Gigabit Ethernet PICs PF-1CGE-CFP and PD-1CE-",
"CFP... |
forwarding-mode (Security Content Security Policy) | forwarding-mode {
hold;
inline-tap;
} | [edit security utm default-configuration anti-virus] | The default configuration for anti-virus is to use the continuous delivery function (CDF). It holds the last
packet and sends out all other packets. It saves system memory and makes the packet transmission
faster. This mode sends the last packet if the result is “permit” and sends RST message to both the client
and the... | [
{
"name": "hold",
"desc": "Hold mode (hold file until analysis is complete, default is CDF mode)."
},
{
"name": "inline-tap",
"desc": "Detect-only mode without blocking (default is off)."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2. | [
"Unified Threat Management Overview"
] |
forwarding-options (Bridge Domains or VLANs) | forwarding-options {
dhcp-security {
arp-inspection;
group group-name {
interface interface-name {
static-ip ip-address {
mac mac-address;
}
}
overrides {
no-option82;
(trusted ... | [edit],
[edit bridge-domains bridge-domain-name],
[edit vlans vlan-name]
[edit chassis] | Configure a unified forwarding table profile to allocate the amount of memory available for the
following:
•
MAC addresses.
•
Layer 3 host entries.
•
Longest prefix match table entries.
This feature enables you to select a profile that optimizes the amount of memory available for various
types of forwarding-table entr... | [
{
"name": "profile-name",
"desc": "name of the profile to use for memory allocation in the unified forwarding table. Table 56 on page 7821 lists the profiles you can choose that have set values and the associated values for each type of entry. On QFX5200 Series switches only, you can also select custom-prof... | 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.
Hierarchy level [edit vlans vlan-name] introduced in Junos OS Release 13.2X50-D10 for EX Series
switches.
Hierarchy level [edit bridge-domains bridge-domain-name] introduced in Junos OS Release 14.1 for MX Series
routers.
custom-profile option introduced in Junos OS Rel... | [
"Understanding the Unified Forwarding Table",
"Example: Configuring a Unified Forwarding Table Custom Profile",
"Configuring Traffic Forwarding and Monitoring"
] |
forwarding-options (Routing Instance) | forwarding-options {
access-security ...
accounting name ...
dhcp-relay ...
enhanced-hash-key ...
family family-name ...
fast-reroute-priority(high | low | medium);
helpers ...
inband-telemetry
ip-options-protocol-queue protocol-name ...
lag-heap-optimization;
link-layer-... | [edit]
[edit routing-instances routing-instance-name] | Configure traffic forwarding options. For more information about each option, click a linked statement in
the Syntax section. | [
{
"name": "access-security",
"desc": "Configure IPv6 access security options."
},
{
"name": "accounting",
"desc": "Specify the discard accounting instance name and options."
},
{
"name": "dhcp-relay",
"desc": "Configure extended Dynamic Host Configuration Protocol (DHCP) relay and DH... | 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 Stateless IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard",
"Configuring Discard Accounting",
"Extended DHCP Relay Agent Overview",
"Configuring Symmetrical Load Balancing on an 802.3ad Link Aggregation Group on MX Series",
"Routers",
"Applying Forwar... |
forwarding-options (Security) | forwarding-options {
allow-dataplane-sleep;
family {
inet6 {
mode (drop | flow-based | packet-based);
}
iso {
mode packet-based;
}
mpls {
mode (flow-based | packet-based);
}
}
mirror-filter filter-name;
... | [edit security] | Determine how the inet6, iso, and mpls protocol families manage security forwarding options.
NOTE:
•
Packet-based processing is not supported on the following SRX Series Firewalls:
SRX5400, SRX5600, and SRX5800.
•
On SRX Series Firewalls, the default mode for processing traffic is flow mode. You can
configure SRX Ser... | [
{
"name": "allow-dataplane-",
"desc": ""
},
{
"name": "sleep",
"desc": "Enable sleep on dataplane."
},
{
"name": "family",
"desc": "Specify the protocol family to be used for packet forwarding."
},
{
"name": "inet6",
"desc": "Specify forwarding options for IPv6 traffic."
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
secure-wire option introduced in Junos OS Release 19.3R1.
resource-manager option introduced in Junos OS Release 19.4R1 for vSRX Virtual Firewall.
mode option introduced in Junos OS Release 20.1R1.
enhanced-logging option introduced in Junos OS Release 23.1R1 to assign a de... | [
"MPLS Overview",
"Understanding Packet-Based Processing",
"Understanding Traffic Processing on Security Devices"
] |
forwarding-options (Unified Forwarding Table Profile) | forwarding-options {
custom-profile {
exact-match-entries {
num-banks num-banks;
}
l2-entries {
num-banks num-banks;
}
l3-entries {
num-banks num-banks;
}
lpm-entries {
num-banks(0 | 2 | 4);
prefix-65... | [edit chassis] | Configure a unified forwarding table profile to allocate the amount of memory available for the
following:
•
MAC addresses.
•
Layer 3 host entries.
•
Longest prefix match table entries.
This feature enables you to select a profile that optimizes the amount of memory available for various
types of forwarding-table entri... | [
{
"name": "custom-profile",
"desc": "On QFX5200 Series switches only, you can select custom-profile. This profile enables you to allocate from one to four banks of shared hash memory to a specific type of forwarding-table entry. Each shared hash memory bank can store a maximum of the equivalent of 32,000 IP... | 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.
custom-profile option introduced in Junos OS Release 15.1x53-D30 for QFX5200 Series switches only.
VXLAN GBP profile options introduced in Junos OS Release 23.2R1 for EX4100, EX4400, EX4600,
QFX5120-32C and QFX5120-48Y switches only. | [
"Understanding the Unified Forwarding Table",
"Example: Configuring a Unified Forwarding Table Custom Profile",
"Configuring Traffic Forwarding and Monitoring"
] |
forwarding-packages | forwarding-packages {
mobility{
user-plane;
sgw;
}
} | [edit chassis fpc fpc-slot pfe pfe-id] | Configure the Packet Forwarding Engine so that it can be used to anchor mobile sessions. If this
configuration is changed, then the FPC reboots.
The forwarding-packages statement can be configured at the Packet Forwarding Engine level. Therefore,
you can configure a subset of Packet Forwarding Engines in an FPC to be m... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced for Junos Multi-Acess User Plane in Junos OS Release 19.4R1. | [] |
forwarding-policy | forwarding-policy {
next-hop-map map-name {
forwarding-class class-name {
discard;
lsp-next-hop [ lsp-regular-expression ];
next-hop [ next-hop-name ];
non-lsp-next-hop;
}
forwarding-class-default {
discard;
lsp-next-hop... | [edit class-of-service] | Define CoS-based forwarding policy options.
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.
Statement introduced for QFX10000 Series switches in Junos OS Release 17.1R1 to support CoS-based
forwarding (CBF). [set class-of-service forwarding-policy class] is not supported on QFX10000 Series
switches. | [
"Configuring CoS-Based Forwarding"
] |
forwarding-process | forwarding-process {
application-services (Security Forwarding Process) {
enable-gtpu-distribution;
inline-fpga-crypto (disabled | enabled);
maximize-alg-sessions;
maximize-idp-sessions {
inline-tap;
... | [edit security] | You can configure SRX5400, SRX5600, and SRX5800 devices to switch from an integrated firewall mode
to maximize Intrusion Detection and Prevention (IDP) mode to run IDP processing in tap mode and
increase the capacity of processing with the maximize-idp-sessions option. Inline tap mode can only be
configured if the forw... | [
{
"name": "enhanced-services-mode",
"desc": "Enable enhanced application services mode. When Enhanced Service Mode is enabled, resources such as MBUF, JBUF, SERVICE-MEM, TCP-PROXY TCB, SZ-INFO and user heap are increased in size and Layer 4 session numbers are reduced by half. The remaining statements are e... | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.6. This statement is supported.
Option enhanced-services-mode introduced in Junos OS Release 20.3R1 on vSRX Virtual Firewall 3.0. | [
"Understanding Traffic Processing on Security Devices"
] |
forwarding-rib | forwarding-rib name {
inet-import [ inet-import ... ];
} | [edit logical-systems name routing-instances name routing-options dynamic-tunnels],
[edit logical-systems name routing-options dynamic-tunnels],
[edit logical-systems name tenants name routing-instances name routing-options dynamic-tunnels],
[edit routing-instances name routing-options dynamic-tunnels],
[edit routing-o... | Configure policy control for forwarding routing table next hops for MPLS-over-UDP dynamic tunnels.
With this configuration, you can resolve the dynamic tunnel destination routes over select prefixes. | [
{
"name": "name",
"desc": "Name of the routing table."
},
{
"name": "inet-import",
"desc": "Name of the import policy for IPv4 dynamic-tunnels."
}
] | routing | Statement introduced in Junos OS Release 18.3R1. | [
"Example: Configuring Next-Hop-Based MPLS-Over-UDP Dynamic Tunnels"
] |
forwarding-state-bit (Long-Lived Graceful Restart for BGP Restarter) | forwarding-state-bit (from-fib | set); | [edit logical-systems logical-system-name protocols bgp family address-family subsequent-address-
family graceful-restart],
[edit logical-systems logical-system-name protocols bgp group group-name family address-family
subsequent-address-family graceful-restart],
[edit logical-systems logical-system-name protocols bgp... | Configure the forwarding-state bit flag negotiation for BGP for all address families. In addition to the
global setting for the Forwarding State bit, the Forwarding State bit behavior can be specified for
individual families. Changing the forwarding-state-bit setting has no effect on any existing sessions. Per-
family ... | [
{
"name": "set",
"desc": "Causes the value to be set according to the state of the associated FIB. Changing the per-family forwarding-state-bit setting has no effect on any existing sessions."
},
{
"name": "from-fib",
"desc": "Forces the Forwarding State bit to be set to 1."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
forwarding-state-bit (Per Family for BGP Graceful Restart) | forwarding-state-bit (as-rr-client | from-fib); | [edit logical-systems logical-system-name protocols bgp graceful-restart],
[edit logical-systems logical-system-name protocols bgp group group-name graceful-restart],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address
graceful-restart],
[edit logical-systems logical-system-name r... | Configure the forwarding-state bit flag negotiation for BGP for individual address families. In addition to
the global setting for the Forwarding State bit, the Forwarding State bit behavior can be specified for
individual families. Changing the forwarding-state-bit setting has no effect on any existing sessions. Per-
... | [
{
"name": "set",
"desc": "Causes the value to be set according to the state of the associated FIB. Changing the per-family forwarding-state-bit setting has no effect on any existing sessions."
},
{
"name": "from-fib",
"desc": "Forces the Forwarding State bit to be set to 1."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
forwarding-table | forwarding-table {
chained-composite-next-hop;
ecmp-fast-reroute;
evpn-egress-link-protection;
evpn-vpws-ack-disable;
export [ policy-name ];
(indirect-next-hop | no-indirect-next-hop);
(indirect-next-hop-change-acknowledgements | no-indirect-next-hop-change-acknowledgements;)
krt-nexth... | [edit logical-systems logical-system-name routing-options],
[edit routing-options] | Configure information about the routing device’s forwarding table.
Some of the remaining statements are explained separately. See CLI Explorer. | [
{
"name": "evpn-egress-link-protection",
"desc": "Enables multihomed PE devices to support fast reroutes (FFRs)."
},
{
"name": "evpn-vpws-ack-disable",
"desc": "By default, the acknowledgement requirement prior to advertising an EVPN-VPWS route is enabled on the routing device. Use this statemen... | 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.
srv6-chain-merge option introduced in Junos OS Release 21.3R1.
multicast-composite-delete-defer-timeout option introduced in Junos OS Release 22.1R2 and Junos OS
Evolved Release 22.1R2.
route-origin-proto-tlv option introduced in Junos OS Release 22.4R1 and Junos OS Evo... | [
"Example: Load Balancing BGP Traffic",
"Configuring Per-Packet Load Balancing"
] |
fpc (Chassis) | fpc fpc-slot {
error no-loss {
buffer {
percentage percent;
}
}
pic <slot>
power (off | on)
max-power power
pfe-instance pfe-instance_id power (off| on)
{
port <port_no> no-temperature-monitoring
}
no-vlan-tagging
} | [edit chassis] | Configure the FPC slot number. (ACX and PTX Series devices) Configure no VLAN tagging for a specific
FPC. Additionally, configure power off configuration (PTX10003 devices only). | [
{
"name": "auto-speed detection",
"desc": "Disables automatic speed detection."
},
{
"name": "cfp-to-et",
"desc": "Enable ET interface and remove CFP client."
},
{
"name": "lossless-flow-control",
"desc": "Lossless buffer config for Ethernet Mac pause."
},
{
"name": "pfe pfe_... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Platform-Specific fpc (Chassis) Behavior
Use Feature Explorer to confirm platform, and release support for specific features.
Use the following table to review platform-specific behaviors for your platfo... | Statement introduced in Junos OS Evolved Release 24.1R1 for ACX Series Routers.
power-off option introduced for PTX10003 devices in Junos OS Evolved Release 22.4R1.
tunnel-services and bandwidth options introduced for ACX Series devices in Junos OS Evolved Release
24.2R1.
mic slot power off option introduced in Junos O... | [] |
fpc (DDoS) | fpc slot-number;
bandwidth-scale percentage;
burst-scale percentage;
disable-fpc;
} | For MX Series routers, T4000 routers, and EX9200 switches:
[edit system ddos-protection protocols protocol-group (aggregate | packet-type)]
For PTX Series routers and QFX Series switches:
[edit system ddos-protection protocols protocol-group (aggregate | packet-type)] | Modify DDoS protection aggregate or packet-type policer default values on the specified line card.
This configuration statement is supported on MX Series routers with MPCs, T4000 routers with FPC5s,
PTX Series routers, EX9200 switches, and QFX Series switches. | [
{
"name": "slot-number",
"desc": "Slot number of the card. On fixed form-factor devices, specify the line card as FPC 0."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers"
] |
fpc (Interfaces) | fpc slot-number ; | [edit interfaces pic-set pic-set-name] | Sets the PIC bundle and the FPC slot.
The pic-set bundles all the PICs and corresponding logical interfaces. A PIC can only join only one pic-
bundle, and cannot join multiple pic-bundles at same time. When the pic-set configuration changes, all
the logical interfaces related to the PIC should be synchronized to all me... | [
{
"name": "apply-groups",
"desc": "Inherit configuration data from these groups."
},
{
"name": "apply-groups-except",
"desc": "Do not inherit configuration data from these groups."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 9.6. | [
"Understanding Interfaces"
] |
fpc (Junos Fusion Satellite Device Cluster) | fpc slot-id{
alias alias;
description description;
member-id member-id-number;
system-id mac-address;
} | [edit chassis satellite-management cluster cluster-name] | Configure an FPC identifier for a satellite device in a satellite device cluster for a Junos Fusion, or modify
the configuration of an existing satellite device in a satellite device cluster in a Junos Fusion. | [
{
"name": "slot-id",
"desc": "Specifies the FPC identifier of the device. In a Junos Fusion, the slot-id must be 34 or larger, and functions as the FPC identifier in the interface name when configuring satellite device interfaces. The remaining statements are explained separately."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Configuring or Expanding a Junos Fusion Enterprise"
] |
fpc (Junos Fusion) | fpc slot-id{
alias alias;
cascade-ports interface-name;
description description;
environment-monitoring-policy policy;
serial-numberserial-number;
system-id mac-address;
uplink-failure-detection {
candidate-uplink-policy policy;
}
local switching;
selective-vlan-switching... | [edit chassis satellite-management] | Configure an FPC identifier for a satellite device within a Junos Fusion, or modify the configuration of an
existing satellite device in a Junos Fusion. | [
{
"name": "slot-id",
"desc": "Specifies the FPC identifier of the device and functions as the FPC identifier in the interface name when configuring satellite device interfaces. In a Junos Fusion Enterprise or Junos Fusion Provider Edge, the slot-id must have a value of 34 or greater. NOTE: MPC10E and MPC11E... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3.
local-switching and selective-vlan-switching introduced in Junos OS Release 17.2R1 for Junos Fusion
Provider Edge. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
fpc (M320, T320 and T640 Devices) | fpc slot-number {
fpc
slot slot-number
{ pfe pfe-instance
{ temp-perf-throttle-disable;
temp-volt-reduction-disable;
power (off | on);
}
{ error {
[fatal | major | minor] {
threshold threshold-value;
action (alarm | dis... | [edit chassis] | Configure properties for the PICs in individual Flexible PIC Concentrators (FPCs). | [
{
"name": "slot-number",
"desc": "Slot number in which the FPC is installed."
},
{
"name": "pfe",
"desc": "Slot number in which the PFE is installed."
}
] | 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.
Error statement introduced for PTX Series routers in Junos OS Release 13.3. | [
"Configure FPC Error Levels and Actions",
"Automatic Performance Throttling of PFEs"
] |
fpc (MX Series 5G Universal Routing Platforms) | fpc slot-number {
inline-services {
flow-table-size {
ipv4-flow-table-size units;
ipv4-flow-table-size units;
ipv6-extended-attrib;
}
}
ir-mode (R | IR);
pfe identifier {
exception-reporting {
category category-name {
i... | [edit chassis] | Configure properties for the DPC or MPC and corresponding Packet Forwarding Engines to create
tunnel interfaces.
(MX Series Virtual Chassis only) When you configure chassis properties for MPCs installed in a Virtual
Chassis member router, statements included at the [edit chassis member member-id fpc slot slot-number]
h... | [
{
"name": "fpc slot-number",
"desc": "Specify the slot number of the DPC."
},
{
"name": "pic number",
"desc": "Specify the number of the Packet Forwarding Engine. Each DPC includes four Packet"
},
{
"name": "port-mirror-instance port-mirroring-instance-name-fpc-level",
"desc": "Assoc... | 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.
port-mirror-instance option added in Junos OS Release 9.3.
ipv6-extended-attrib option added in Junos OS Release 14.2 for MX Series routers.
exception-reporting option added in Junos OS Release 21.2R1. | [
"Configuring Port-Mirroring Instances on MX Series 5G Universal Routing Platforms",
"Virtual Chassis Components Overview"
] |
fpc (Notification Control) | fpc slot-number {
disable;
} | [edit poe notification-control] | Enable the specified PoE controller to generate PoE traps.
Default
PoE traps are disabled by default. | [
{
"name": "slot-number",
"desc": "Indicates the PoE controller by FPC slot number, where slot-number is:"
},
{
"name": "0",
"desc": "On an EX2200, EX3200, standalone EX3300, standalone EX4200, or standalone EX4300 switch"
},
{
"name": "Member ID",
"desc": "On an EX3300, EX4200, or EX... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring PoE Interfaces on EX Series Switches"
] |
fpc (PTX Series Devices) | fpc slot-number {
error
pfe
pic
sampling-instance instance_string;
traffic-manager {
(enhanced-priority-mode | no-enhanced-priority-mode)
}
optical-options
} | [edit chassis] | Configure properties for the PICs in individual Flexible PIC Concentrators (FPCs). Configure FPC Restart,
offline and online (PTX10003 devices only). | [
{
"name": "slot-number",
"desc": "Slot number in which the FPC is installed."
},
{
"name": "pfe",
"desc": "Slot number in which the PFE is installed. If FPC power off is set along with PFE power ON, then"
},
{
"name": "sampling-instance instance_string",
"desc": "You can configure ac... | 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.
Error statement introduced for PTX Series devices in Junos OS Release 13.3. | [
"Configure FPC Error Levels and Actions",
"Automatic Performance Throttling of PFEs",
"Manage FPC Errors",
"Managing Errors"
] |
fpc (QFX Series) | fpc slot {
auto-speed-detection disable;
pic pic-number{
tunnel-port port-number tunnel-services;
port port-number{
channel-speed (speed|disable-auto-speed-detection) ;
}
port-range port-range-low port-range-high {
channel-speed (speed|disable-auto-speed-... | [edit chassis] | Configure the FPC slot number. For QFX3500 switches, the slot is a line card slot.
For generic routing encapsulation (GRE) tunneling, use the tunnel-port statement to specify the port that
you want to convert to a GRE tunnel port. | [
{
"name": "slot",
"desc": "Number of the FPC slot. For QFX3500, QFX3600, QFX5200, and OCX Series devices, the slot"
}
] | 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. | [
"show chassis fpc"
] |
fpc (Subscriber Limits) | fpc slot-number {
limit limit;
pic number {
limit limit;
port number {
limit limit;
}
}
} | [edit system services resource-monitor subscribers-limit client-type name] | Configure the maximum number of subscribers of a client type allowed to be logged in on the MPC in
the specified slot. When that number is reached, subsequent logins on the card are denied until the
current number of subscribers drops below the maximum allowed. You can also specify the maximum
number of subscribers of ... | [
{
"name": "limit",
"desc": "Maximum number of subscribers. Range: 1 through 256,000"
},
{
"name": "slot-number",
"desc": "Number of the MPC slot in the chassis. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax se... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Limiting Subscribers by Client Type and Hardware Element with Resource Monitor",
"Resource Monitoring for Subscriber Management and Services"
] |
fpc (TX Matrix and TX Matrix Plus Routers) | fpc slot-number {
pic pic-number {
atm-cell-relay-accumulation;
atm-l2circuit-mode (cell | aal5 | trunk trunk);
framing (sdh | sonet);
idle-cell-format {
itu-t;
payload-pattern payload-pattern-byte;
}
max-queues-per-interface (8 | 4);
... | [edit chassis lcc number] | On a TX Matrix or TX Matrix Plus router, configure properties for the PICs in individual FPCs. | [
{
"name": "slot-number",
"desc": "Slot number in which the FPC is installed."
}
] | 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. | [
"TX Matrix Router and T640 Router Configuration Overview",
"TX Matrix Plus Router Configuration Overview",
"Configuring the Junos OS to Enable SONET/SDH Framing for SONET/SDH PICs",
"TX Matrix Router Chassis and Interface Names",
"TX Matrix Plus Router Chassis and Interface Names"
] |
fpc error | fpc slot number {
error {
(fatal | major | minor) {
threshold threshold-value;
action (alarm | disable-pfe | offline-pic | log | get-state |offline | reset);
}
}
} | [edit chassis] | Configure the threshold at which FPC errors will take the action you configure to be performed by the
device.
Some devices include an internal framework for detecting and correcting FPC errors that can have the
potential to affect services. For each FPC on the device, you can classify errors according to severity, set
... | [
{
"name": "fatal",
"desc": "Fatal error on the FPC. An error that results in the blockage of a considerable amount of traffic"
},
{
"name": "major",
"desc": "Major error on the FPC. An error that results in continuing loss of packet traffic but does not"
},
{
"name": "minor",
"desc":... | routing—To view this in the configuration.
routing-control—To add this to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40. This command is supported. | [] |
fpc-feb-connectivity | fpc-feb-connectivity {
fpc number feb (slot-number | none);
} | [edit chassis] | On the M120 router only, configure a connection between any Flexible PIC Concentrator (FPC) and any
Forwarding Engine Board (FEB). | [
{
"name": "fpc number",
"desc": "Specify the FPC slot number."
},
{
"name": "feb slot-number",
"desc": "Specify the FEB slot number."
},
{
"name": "none",
"desc": "Disconnect the FPC from the FEB."
}
] | 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. | [
"Configuring the Junos OS to Support FPC to FEB Connectivity on M120 Routers"
] |
fpc-nmi-volt-fail-knob | fpc-nmi-volt-fail-knob (enable | disable) | [edit chassis] | Enable or disable the non maskable interrupt (NMI) for the voltage failure errors on the flexible pic
concentrator (FPC). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration | Statement introduced in Junos OS Release 10.4R15, 11.4R8-S2, 11.4R9, 12.1R8, 12.2R6, 12.3R3-S1,
12.3R4, 13.1R3, and 13.2R1 | [
"Configuring Voltage Level Monitoring of FPCs"
] |
fpc-offline-on-blackholing | fpc-offline-on-blackholing; | [edit chassis fabric degraded] | Take the FPC offline and raise an alarm if a traffic null route condition is detected in the routing matrix.
By default, FPCs remain online when a null route condition is detected. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.