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 |
|---|---|---|---|---|---|---|---|
fpc-restart | fpc-restart; | [edit chassis fabric degraded] | Allow the user to restart the FPCs when a traffic null route condition is detected in the routing matrix.
To enable this feature set the fpc-restart statement at the edit chassis fabric degraded hierarchy level.
Default
FPCs are not restarted when a null route condition is detected. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement added in Junos OS Release 13.2R6. | [
"Fabric Resiliency and Degradation",
"Disabling Line Card Restart to Limit Recovery Actions from Degraded Fabric Conditions"
] |
fpc-resync | fpc-resync; | [edit chassis] | (On M320, T320, T640, T1600, T4000, TX Matrix, and TX Matrix Plus routers only) When a Flexible PIC
Concentrator (FPC) is brought online, resynchronize the sequence numbers of the FPC with the other
active FPCs.
NOTE: In order to prevent null-route filtering, the fpc-resync command will have no effect
if a single LMNR ... | [] | 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. | [
"Resynchronizing FPC Sequence Numbers with Active FPCs when an FPC Comes Online"
] |
fpc-slice | fpc-slice fpc fpc-slot {
slc slc-id {
pfe-id-list pfe-id-list;
cores number-of-cores;
dram dram-value;
}
} | [edit chassis network-slices guest-network-functions gnf gnf-id] | Configure smaller logical partitions or sub line cards (SLC) of a line card, allocate resources to the SLCs,
and assign each SLC to a guest network function (GNF).
This feature is applicable only to the MPC11E line card. An MPC11E line card supports two sub line
cards (SLCs). You can assign each GNF with an SLC, which ... | [
{
"name": "fpc-slot",
"desc": "The slot number of the line card on which you want to configure SLCs."
},
{
"name": "slc slc-id",
"desc": "Specify the sub line card (SLC) ID which you want to assign to the selected GNF. NOTE: Do not assign: two or more SLCs of the same line card to the same GNF.... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [] |
fpcs (Node Slicing) | fpcs fpcs; | [edit chassis network-slices guest-network-functions gnf] | Assign FPCs to a guest network function.
NOTE: A given FPC cannot be assigned to more than one GNF. | [
{
"name": "fpcs",
"desc": "The FPC to be assigned to a guest network function. Range: 0–63"
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [] |
fpcs (NSSU Upgrade Groups) | fpcs (slot-number | [list-of-slot-numbers]); | [edit chassis nssu upgrade-group group-name],
[edit chassis nssu upgrade-group group-name member member-id] | Configure switch line cards, Virtual Chassis member switches, or Virtual Chassis Fabric (VCF) member
switches as part of an NSSU upgrade group.
To reduce the time an NSSU takes, you can configure line-card upgrade groups for an EX6200 or
EX8200 switch with redundant Routing Engines; an EX8200 Virtual Chassis; an EX4650... | [
{
"name": "list-of-slot-numbers",
"desc": "A list of slot numbers of multiple line cards or member IDs of Virtual Chassis or VCF members to be included in the upgrade group. Separate multiple slot numbers or"
},
{
"name": "member IDs with spaces and enclose the list in square brackets",
"desc": ... | 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. | [
"Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on EX Series",
"Switches",
"Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade"
] |
fragment (IDS Screen Next Gen Services) | fragment; | [edit services screen ids-option screen-name icmp] | Identify and drop ICMP packets that are IP fragments. These are considered suspicious packets because
ICMP packets are usually short. When the target receives these packets, the results can range from
processing packets incorrectly to crashing the entire system. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
fragment-limit | fragment-limit number-of-fragments; | [edit interfaces interface-name services-options]
[edit security flow] | Configure the maximum number of fragments permitted in a packet before the packet is dropped. | [
{
"name": "number-of-fragments",
"desc": "Maximum number of fragments permitted."
}
] | 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.
Statement added in Junos OS Release 20.3R1 for Next Gen Services on MX240, MX480, and MX960
routers. | [
"Configuring Fragmentation Control for MS-DPC and MS-PIC Service Interfaces"
] |
fragment-threshold (Forwarding Class Maps) | fragment-threshold bytes; | [edit class-of-service fragmentation-maps forwarding-class class-name] | For link services IQ (lsq) interfaces only, set the fragmentation threshold for an individual forwarding
class.
Default
If you do not include this statement, the fragmentation threshold you set at the [edit interfaces interface-
name unit logical-unit-number] or [edit interfaces interface-name mlfr-uni-nni-bundle-optio... | [
{
"name": "bytes",
"desc": "Maximum size, in bytes, for multilink packet fragments. Any nonzero value must be a multiple of"
}
] | 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"
] |
fragment-threshold (Interfaces LSQ) | fragment-threshold bytes; | [edit interfaces lsq-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces lsq-fpc/pic/port unit logical-unit-number] | For voice services interfaces, set the fragmentation threshold, in bytes. | [
{
"name": "bytes",
"desc": "Maximum size, in bytes, for multilink packet fragments. The value must be a multiple of 64 bytes,"
}
] | 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 Delay-Sensitive Packet Interleaving"
] |
fragment-threshold | fragment-threshold bytes; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options],
[edit interfaces (ls-fpc/pic/port| ml-fpc/pic/port) unit logical-unit-number],
[edit logical-systems logical-system-name interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-
options],
[edit logical-systems logical-system-name interfaces (ls-fpc/p... | For multilink and link services interfaces only, set the fragmentation threshold, in bytes. | [
{
"name": "bytes",
"desc": "Maximum size, in bytes, for multilink packet fragments. Any nonzero value must be a multiple of"
}
] | 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. | [
"Example: Configuring a Multilink Interface with MLPPP"
] |
fragmentation-map | fragmentation-map map-name; | [edit class-of-service interfaces interface-name unit logical-unit-number] | For AS PIC link services IQ (lsq) and virtual LSQ redundancy (rlsq) interfaces, associate a fragmentation
map with a multilink PPP interface or MLFR FRF.16 DLCI.
Default
If you do not include this statement, traffic in all forwarding classes is fragmented. | [
{
"name": "map-name",
"desc": "Name of the fragmentation map."
}
] | 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. | [
"Fragmentation by Forwarding Class Overview",
"Configuring Fragmentation by Forwarding Class",
"Configuring Fragmentation by Forwarding Class",
"Example: Configuring Fragmentation by Forwarding Class",
"Configuring Drop Timeout Interval for Fragmentation by Forwarding Class"
] |
fragmentation-maps | fragmentation-maps {
map-name {
forwarding-class class-name {
drop-timeout milliseconds;
fragment-threshold bytes;
multilink-class number;
no-fragmentation;
}
}
} | [edit class-of-service] | For Multiservices and Services PIC link services IQ (lsq) and virtual LSQ redundancy (rlsq) interfaces,
define fragmentation properties for individual forwarding classes.
Default
If you do not include this statement, traffic in all forwarding classes is fragmented. | [
{
"name": "map-name",
"desc": "Name of the fragmentation map."
}
] | 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. | [
"Fragmentation by Forwarding Class Overview",
"Configuring Fragmentation by Forwarding Class",
"Example: Configuring Fragmentation by Forwarding Class",
"Configuring Drop Timeout Interval for Fragmentation by Forwarding Class",
"fragmentation-map"
] |
frame-error | frame-error count; | [edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds] | Configure the threshold value for sending frame error events or taking the action specified in the action
profile.
Frame errors occur on the underlying physical layer. The threshold is reached when the number of frame
errors reaches the configured value.
The window or period during which frame errors are counted is 5 s... | [
{
"name": "count",
"desc": "Threshold count for frame error events."
}
] | 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. | [
"Configuring Threshold Values for Local Fault Events on an Interface",
"Configuring Threshold Values for Fault Events in an Action Profile"
] |
frame-mode (Dynamic Traffic Shaping) | frame-mode (bytes | $junos-cos-byte-adjust | frame-mode-bytes frame-mode-bytes |$junos-cos-byte-
adjust-frame); | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name overhead-
accounting],
[edit class-of-service traffic-control-profiles profile-name overhead-accounting] | Configure the mode to shape downstream ATM traffic based as frames.
Default
The default is frame-mode. | [
{
"name": "bytes",
"desc": "Byte adjustment value for the cell-mode or frame-mode shaping options."
},
{
"name": "$junos-cos-byte-adjust",
"desc": "Predefined variable for byte adjustment that is replaced with a value obtained from the RADIUS server when a subscriber authenticates over the inter... | 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.
Variable $junos-cos-byte-adjust-frame introduced in Junos OS Release 13.1. | [
"CoS Adjustment Control Profiles Overview",
"Configuring CoS Adjustment Control Profiles",
"Configuring Dynamic Shaping Parameters to Account for Overhead in Downstream Traffic Rates",
"Bandwidth Management for Downstream Traffic in Edge Networks Overview",
"egress-shaping-overhead"
] |
frame-period | frame-period count; | [edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds] | Configure the number of frame errors within the last N frames that has exceeded a threshold. Threshold
for sending frame period error events or taking the action specified in the action profile.
A frame error is any frame error on the underlying physical layer. The frame period threshold is reached
when the number of ... | [
{
"name": "count",
"desc": "Threshold count for frame period error events."
}
] | 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. | [
"Configuring Threshold Values for Local Fault Events on an Interface",
"Configuring Threshold Values for Fault Events in an Action Profile"
] |
frame-period-summary | frame-period-summary count; | [edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds] | Configure the threshold value for sending frame period summary error events or taking the action
specified in the action profile.
An errored frame second is any 1-second period that has at least one errored frame. This event is
generated if the number of errored frame seconds is equal to or greater than the specified t... | [
{
"name": "count",
"desc": "Threshold count for frame period summary error events."
}
] | 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. | [
"Configuring Threshold Values for Local Fault Events on an Interface",
"Configuring Threshold Values for Fault Events in an Action Profile"
] |
frame-relay-de (CoS Interfaces) | frame-relay-de (name | default); | [edit class-of-service interfaces interface-name unit logical-unit-number loss-priority-maps],
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Assign the loss priority map or the rewrite rule to a logical interface. | [
{
"name": "default",
"desc": "Apply default loss priority map or default rewrite rule. The default loss priority map contains"
},
{
"name": "the following settings:",
"desc": ""
},
{
"name": "loss-priority low code-point 0;",
"desc": ""
},
{
"name": "loss-priority high code-p... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
frame-relay-de (CoS Loss Priority) | frame-relay-de map-name {
loss-priority level code-point (0 | 1);
} | [edit class-of-service loss-priority-maps] | Define a Frame Relay discard-eligible bit loss-priority map. | [
{
"name": "level",
"desc": "Level of loss priority to be applied based on the specified CoS values. The level can be low,"
},
{
"name": "map-name",
"desc": "Name of the loss-priority map."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
frame-relay-de (CoS Rewrite Rule) | frame-relay-de rewrite-name {
forwarding-class class-name {
loss-priority level code-point (0 | 1);
}
import (default | rewrite-name);
} | [edit class-of-service rewrite-rules] | Define a Frame Relay discard-eligible bit rewrite rule. | [
{
"name": "level",
"desc": "Level of loss priority on which to base the rewrite rule. The loss priority level can be low,"
},
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules]"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
frame-relay-de (Defining Loss Priority Maps) | frame-relay-de name {
loss-priority level code-points [ alias | bits ];
} | [edit class-of-service loss-priority-maps] | Define a Frame Relay discard eligibility (DE) bit loss priority map. | [
{
"name": "name",
"desc": "Name of the loss priority map."
},
{
"name": "loss-priority",
"desc": ""
},
{
"name": "level",
"desc": "Level of the loss priority to be applied based on the specified CoS values. The loss priority"
},
{
"name": "level can be one of the following:",... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Defining a Custom Frame Relay Loss Priority Map"
] |
frame-relay-de (Defining Loss Priority Rewrites) | frame-relay-de name {
loss-priority level code-point [ alias | bits ];
} | [edit class-of-service loss-priority-rewrites] | Define a Frame Relay discard eligibility (DE) bit loss priority rewrite. | [
{
"name": "name",
"desc": "Name of the loss priority rewrite."
},
{
"name": "loss-priority",
"desc": ""
},
{
"name": "level",
"desc": "Level of the loss priority to be applied based on the specified CoS values. The loss priority"
},
{
"name": "level can be one of the followin... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
framed-ip-address | framed-ip-address {
equals value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP Framed-IP-Address (IPv4) for the incoming RADIUS request from the
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 statement is explained separ... | [] | 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 Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
framed-ipv6-prefix | framed-ipv6-prefix {
equals value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP Framed-IPv6-Prefix for the incoming RADIUS request from the 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 statement is explained separately.... | [] | 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 Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
framed-pool | framed-pool framed-pool; | [edit access group-profile profile-name ppp],
[edit access profile profile-name client client-name ppp] | Configure the address pool. | [
{
"name": "framed-pool",
"desc": "References a configured address pool."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Point-to-Point Protocol (PPP)"
] |
framing (10-Gigabit Ethernet Interfaces) | framing (lan-phy | wan-phy);
precise-bandwidth; | [edit interfaces xe-fpc/pic/port],
[edit interfaces et-fpc/pic/port] | For routers supporting the 10-Gigabit Ethernet interface, configure the framing format. WAN PHY mode
is supported on MX240, MX480, MX960, T640, T1600,T4000, and PTX Series Packet Transport Routers
routers only.
NOTE:
•
The T4000 Core Router supports only LAN PHY mode in Junos OS Release 12.1R1.
Starting with Junos OS ... | [
{
"name": "lan-phy",
"desc": "10GBASE-R interface framing format that bypasses the WIS sublayer to directly stream block-encoded Ethernet frames on a 10-Gigabit Ethernet serial interface."
},
{
"name": "wan-phy",
"desc": "10GBASE-W interface framing format that allows 10-Gigabit Ethernet wide ar... | 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.
The option precise-bandwidth introduced in Junos OS Release 19.3R1 for MX Series Routers. | [
"Framing Overview",
"Configuring SONET Options for 10-Gigabit Ethernet Interfaces"
] |
framing (E1 Options for BITS Interfaces) | framing (g704 | g704-no-cro4); | [edit chassis synchronization interfaces bits e1-options] | Configure the framing format for the building-integrated timing supply (BITS) interface when the signal
type is E1. Valid only when e1 is the signal-type configured at the [edit chassis synchronization source
interfaces interface-name bits signal-type] hierarchy. | [
{
"name": "g704",
"desc": "G.704 framing format for E1 interfaces."
},
{
"name": "g704-no-crc4",
"desc": "G.704 framing with no cyclic redundancy check 4 (CRC4) for E1 interfaces."
}
] | 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. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview"
] |
framing (E1 Options) | framing (g704 | g704-no-crc4); | [edit chassis synchronization interfaces external e1-options],
[edit chassis synchronization interfaces (external-0/0 | external-1/0) e1-options] | Configure the framing format for the E1 interface. | [
{
"name": "g704",
"desc": "Set the G.704 framing format for E1 interfaces."
},
{
"name": "g704-no-crc4",
"desc": "Set the G.704 framing without CRC4 for E1 interfaces."
}
] | 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. | [] |
framing (T1 Options for BITS Interfaces) | framing (esf | sf); | [edit chassis synchronization interfaces bits t1-options] | Configure the framing format for the building-integrated timing supply (BITS) interface when the signal
type is T1 . Valid only when t1 is the signal-type configured at the [edit chassis synchronization source
interfaces interface-name bits signal-type] hierarchy. | [
{
"name": "esf",
"desc": "Extended superframe (ESF) mode for T1 interfaces."
},
{
"name": "sf",
"desc": "Superframe (SF) mode for T1 interfaces."
}
] | 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. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview"
] |
framing (T1 Options) | framing (esf | sf); | [edit chassis synchronization interfaces external t1-options],
[edit chassis synchronization interfaces (external-0/0 | external-1/0) t1-options] | Configure the framing format for the T1 interface. | [
{
"name": "esf",
"desc": "Set the framing format as extended super frame."
},
{
"name": "sf",
"desc": "Set the framing format as super frame."
}
] | 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. | [] |
free-fw-memory-watermark (Resource Monitor) | free-fw-memory-watermark number; | [edit system services resource-monitor] | Configure the percentage of free memory space used for firewall or filters to be monitored with a
watermark value. You can configure the resource-monitoring capability on MX80, MX104, MX240,
MX480, MX960, MX2010, and MX2020 routers with I-chip-based DPCs and Trio-based FPCs. | [
{
"name": "number",
"desc": "Percentage of free memory space used for firewall and filters to be monitored with a watermark value. When the configured watermark is exceeded, error logs are triggered. The default watermark values for the percentage of free ukernel or heap memory, next-hop memory, and firewal... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
free-heap-memory-watermark (Resource Monitor) | free-heap-memory-watermark number; | [edit system services resource-monitor] | Configure the percentage of free memory space used for ukernel or heap (ASIC) memory to be
monitored with a watermark value. You can configure the resource-monitoring capability on MX80,
MX104, MX240, MX480, MX960, MX2010, and MX2020 routers with I-chip-based DPCs and Trio-
based FPCs. | [
{
"name": "number",
"desc": "Percentage of free memory space used for ukernel or heap to be monitored with a watermark value. When the configured watermark is exceeded, error logs are triggered. The default watermark values for the percentage of free ukernel or heap memory, next-hop memory, and firewall fil... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
free-nh-memory-watermark (Resource Monitor) | free-nh-memory-watermark number; | [edit system services resource-monitor] | Configure the percentage of free memory space used for next-hops to be monitored with a watermark
value. The default value and the configured value of the watermark value for the percentage of free
next-hop memory also applies to encapsulation memory. You can configure the resource-monitoring
capability on MX80, MX104,... | [
{
"name": "number",
"desc": "Percentage of free memory space used for next-hops to be monitored with a watermark value. The NH memory watermark is applicable only for encapsulation memory (output WAN static RAM memory). When the configured watermark is exceeded, error logs are triggered. The default waterma... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
frequency-lock-threshold | frequency-lock-threshold frequency-offset | [edit protocols ptp] | The frequency lock threshold option controls the frequency offset in parts per billion (ppb) that the
servo will lock with. Locking with a higher frequency lock threshold allows a quicker frequency lock,
although at the expense of a higher phase offset per window in the phase aligned state. This option can
be used for ... | [
{
"name": "frequency-offset",
"desc": "The frequency offset value in parts per billion (ppb). Range: 1 ppb through 15 ppb Default: 1 ppb"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1 for MX10008.
Supported on ACX7100-32C, ACX7100-48L, and ACX7024 in Junos OS Evolved Release 24.2R1. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] |
from (Application Aware Access List) | from {
application-group-any;
application-groups [ application-group-names ];
application-unknown;
applications [ application-names ];
destination-address address <any-unicast>;
destination-address-range low minimum-value high maximum-value;
destination-prefix-list list-name;
nested-app... | [edit services aacl rule rule-name term term-name] | Specify match conditions for the AACL term. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 9.5. | [
"Configuring AACL Rules"
] |
from (Captive Portal Content Delivery Tags) | from {
destination-address address <except>;
} | [edit services captive-portal-content-delivery rule rule-name term term-name] | Specify one or more addresses in a CPCD rule term to identify traffic that can have header tags inserted
into GET messages. Tag insertion is supported only for Routing-Engine-based, static CPCD. | [
{
"name": "address",
"desc": "Destination IPv4 or IPv6 address for traffic to be tagged."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified address from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [
"Configuring Routing Engine-Based, Static HTTP Redirect Services"
] |
from (Firewall) | from {
match-conditions;
egress-to-ingress;
} | [edit firewall family family-name filter filter-name term term-name] | Match packet fields to values specified in a match condition. If the from statement is not included in a
firewall filter configuration, all packets are considered to match and the actions and action modifiers in
the then statement are implemented. | [
{
"name": "match-conditions",
"desc": "Conditions that define the values or fields that the incoming or outgoing packets"
},
{
"name": "egress-to-ingress",
"desc": "Include this option to increase the number of egress VLAN firewall filter terms from"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Option egress-to-ingress introduced in Junos OS Release 19.1R1 for the QFX5110. | [
"Firewall Filter Match Conditions and Actions (QFX5100, QFX5110, QFX5120, QFX5200, EX4600,",
"EX4650)",
"Configuring Firewall Filters",
"Understanding Firewall Filter Match Conditions"
] |
from (HTTP Header Enrichment) | from {
destination-address {
(any-ipv4 | any-ipv4 except);
(any-ipv6 | any-ipv6 except);
(any-unicast | any-unicast except);
(prefix | prefix except);
}
destination-address-range {
high address low address <except>;
}
destination-port-range {
high port... | [edit services hcm tag-rule rule-name term term-number] | Specify the match criteria for the term in the tag rule. If all the conditions specified in the match criteria
are met, then the HTTP header enrichment actions specified in the then statement are applied.
If you want the HTTP header enrichment actions specified in the then statement to be applied to all
HTTP requests, ... | [] | 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 HTTP Header Enrichment Overview"
] |
from (IDS MS-DPC) | from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-unicast) <except>;
destination-address-range low minimum-value high maximum-value <except>;
source-address (address | any-unicast) <except>;
source-address-range low minimum-value high maximu... | [edit services ids rule rule-name term term-name] | Specify input conditions for the IDS term when using the MS-DPC. | [] | 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 Match Conditions in IDS Rules"
] |
from (PCC Rules) | from {
<application-groups [application-group-name]>;
<applications [application-name]>;
flows ([flow-identifier] | any);
} | [edit unified-edge pcef pcc-rules rule-name],
[edit services pcef pcc-rules rule-name] | Specify the match criteria for the policy and charging control (PCC) rules. Any referenced SDF filter,
application, or application group in the from statement must be configured.
If you are using Junos OS Subscriber Aware, specify the match criteria at the [edit unified-edge pcef pcc-
rules rule-name] hierarchy level.
... | [] | 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] 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
Release ... | [
"Configuring Policy and Charging Control Rules"
] |
from (PCP) | from {
application-sets set-name;
applications [ application-name ];
destination-address address <except>;
destination-address-range high maximum-value low minimum-value <except>;
destination-port high maximum-value low minimum-value;
destination-prefix-list list-name <except>;
source-addre... | [edit services pcp rule rule-name term term-name] | Specify the match conditions for a PCP rule term. A PCP rule assigns the PCP server that handles
selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC.
The remaining statements are explained s... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
from (Protocols MPLS) | from address; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Specify the source address to use for the LSP.
The address you specify does not affect the outgoing interface used by the LSP.
Default
If you do not include this statement, the software automatically selects the loopback interface as the
address. | [
{
"name": "address",
"desc": "IP address."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Ingress Router Address for LSPs"
] |
from (Security NAT) | from {
interface [interface-name];
routing-instance [routing-instance-name];
zone [zone-name];
} | [edit security nat destination rule-set rule-set-name]
[edit security nat source rule-set rule-set-name]
[edit security nat static rule-set rule-set-name] | Specify the source of the packet among the routing instance, interface, or zone. | [
{
"name": "interface [interface-name]",
"desc": "Name of the interface."
},
{
"name": "routing-instance [routing-instance-name]",
"desc": "Name of the routing instance."
},
{
"name": "zone [zone-name]",
"desc": "Name of the zone."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.3. | [] |
from (Services CoS) | from {
applications [ application-name ];
application-sets [ set-name ];
destination-address address;
source-address address;
} | [edit services cos rule rule-name term term-name] | Specify input conditions for a CoS term. | [] | 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 Rule Sets on Services PICs"
] |
from (Services NAT) | from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-unicast) <except>;
destination-address-range low minimum-value high maximum-value <except>;
destination-port range high maximum-value low minimum-value;
source-address address (address | any-... | [edit services nat rule rule-name term term-name] | Specify input conditions for the NAT term. | [] | 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. | [
"Network Address Translation Rules Overview"
] |
from (Services Stateful Firewall) | from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-ipv4 | any-ipv6 | any-unicast) <except>;
destination-address-range low minimum-value high maximum-value <except>;
destination-prefix-list list-name <except>;
source-address (address | any-ipv... | [edit services stateful-firewall rule rule-name term term-name] | Specify input conditions for a stateful firewall term. | [] | 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 Stateful Firewall Rules"
] |
from (services-ipsec-vpn) | from {
destination-address address;
ipsec-inside-interface interface-name;
source-address address;
} | [edit services ipsec-vpn rule rule-name term term-name] | Specify input conditions for the IPsec term. | [] | 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 IPsec Rules"
] |
from (Subscriber Secure Policy) | from {
apply-groups group-name;
apply-groups-except group-name;
destination-address address;
destination-port port-number;
dscp dscp-value;
protocol protocol;
source-address address;
source-port port-number;
} | [edit services radius-flow-tap policy policy-name (inet | inet6)] | Define the match criteria for the drop-policy rule.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | 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 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
from (TDF Domain Selection) | from {
3gpp-imsi {
equals value;
has-prefix value;
has-suffix value;
matches value;
}
attribute name {
code numeric-code;
vendor-id vendor-id;
format {
integer {
equals {
value;
}
... | [edit unified-edge gateways tdf gateway-name domain-selection term term-name] | Specify the match criteria for the TDF domain selection or PCEF profile selection term.
NOTE: For any term, the subscriber must match all the match conditions specified in a
from statement. If you do not configure the from statement, then all subscribers are
considered a match.
The remaining statements are explained se... | [] | 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 Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
from-zone (Security IDP Policy) | from-zone (zone-name | any); | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match]
[edit security idp idp-policy policy-name rulebase-ips rule rule-name match] | Specify a source zone to be associated with the security policy. The default value is any. | [
{
"name": "zone-name",
"desc": "Name of the source zone object."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
from-zone (Security Policies Global) | from-zone {
[zone-name];
any;
} | [edit security policies global policy policy-name match] | Identify a single source zone or multiple source zones to be used as a match criteria for a policy. You
must configure specific zones or default to any zone, but you cannot have both in a global policy. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [
"Security Policies Overview"
] |
from-zone (Security Policies) | from-zone zone-name to-zone zone-name {
policy policy-name {
description description;
match {
application {
[application];
any;
}
destination-address {
[address];
any;
... | [edit security policies] | Specify a source zone and destination zone to be associated with the security policy. | [
{
"name": "from-zone zone-name",
"desc": "Name of the source zone."
},
{
"name": "to-zone zone-name",
"desc": "Name of the destination zone."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. Support for the services-offload option added in Junos OS
Release 11.4. Support for the source-identity option added in Junos OS Release 12.1. Support for the
description option added in Junos OS Release 12.1. Support for the ssl-termination-profile and web-
redirect-to-htt... | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements",
"Unified Policies Configuration Overview"
] |
fru-poweron-sequence | fru-poweron-sequence fru-poweron-sequence; | [edit chassis] | (MX Series 5G Universal Routing Platforms, SRX5xxx Series Platforms) Configure the power-on
sequence for the DPCs in the chassis for routers with the enhanced AC Power Entry Module (PEM).
(T640 routers, T1600 routers, T4000 routers, MX2020 routers, and PTX Series packet transport routers)
Configure the power-on sequenc... | [
{
"name": "(MX Series 5G Universal Routing Platforms only) fru-poweron-sequence",
"desc": "Power-on sequence for the DPCs"
},
{
"name": "fru-poweron-sequence",
"desc": "Power-on sequence for the FPCs in the chassis. The numbers indicate 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 10.0. | [
"Redistribute the Available Power by Configuring Power-On Sequence"
] |
fte (Port) | fte {
(port port-number | port-range port-range-low port-range-high);
} | [edit chassis fpc slot pic pic-number] | Configure a specific port or a range of ports to operate as 40-Gigabit Ethernet data plane uplink (fte)
type ports.
CAUTION: The Packet Forwarding Engine on the switch is restarted when you commit
the port type configuration changes. As a result, you might experience packet loss on the
switch. | [
{
"name": "port-number",
"desc": "Port number on which you want to configure the port type. Valid values are 2 through 7."
},
{
"name": "port-range-low",
"desc": "Lowest-numbered port in the range of ports. The lowest possible value is 2."
},
{
"name": "port-range-high",
"desc": "Hig... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Configuring the QSFP+ Port Type on QFX3500 Standalone Switches",
"Configuring the Port Type on QFX3600 Standalone Switches",
"Configuring the QSFP+ Port Type on QFX5100 Devices"
] |
ftp (Access) | ftp {
banner {
fail string;
login string;
success string;
}
} | [edit access firewall-authentication pass-through] | Configure banners for the FTP login prompt, successful authentication, and failed authentication. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"SRX Firewall Users",
"Obtaining Username and Role Information Through Firewall Authentication"
] |
ftp (Content Security Policy Anti-Virus) | ftp {
download-profile profile-name;
upload-profile profile-name;
} | [edit security utm default-configuration]
[edit security utm utm-policy policy-name anti-virus] | Configure a Content Security policy for the antivirus FTP protocol and attach this policy to a security
profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
ftp (Content Security Policy Content Filtering) | ftp {
download-profile profile-name;
upload-profile profile-name;
} | [edit security utm default-configuration]
[edit security utm utm-policy policy-name content-filtering] | Configure a Content Security policy for the content-filtering FTP protocol and attach this policy to a
security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
ftp (Flow Collector Files) | ftp:url; | [edit services flow-collector destination] | Specify the primary and secondary destination FTP server addresses. | [
{
"name": "url",
"desc": "FTP server address. The URL can include the following macros, typed in braces:"
},
{
"name": "{%D}",
"desc": "Date"
},
{
"name": "{%T)",
"desc": "Time when the file is created"
},
{
"name": "{%I}",
"desc": "Description string for the logical inte... | 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 Destination FTP Servers for Flow Records"
] |
ftp (Security ALG) | ftp {
allow-mismatch-ip-address;
disable;
ftps-extension;
line-break-extension;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "allow-mismatch-ip-address",
"desc": "Control commands in FTP, such as PORT and EPRT, contain IP addresses"
},
{
"name": "disable",
"desc": "Disable the FTP ALG. By default, the FTP ALG is enabled. You can enable or disable FTP ALG"
},
{
"name": "ftps-extension",
"desc": "E... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 11.4.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"FTP ALG Overview"
] |
ftp (Services CoS Next Gen Services) | ftp {
data {
dscp (alias | bits);
forwarding-class class-name;
}
} | [edit services cos application-profile profile-name] | Configure CoS actions for FTP traffic in an application profile. The application profile can then be used in
CoS rule actions. | [
{
"name": "dscp (alias | bits)",
"desc": "Either a code point alias or a DSCP bit value to apply to the FTP packets."
},
{
"name": "forwarding-class class-name",
"desc": "Forwarding class name to apply to the FTP packets. The choices are:"
},
{
"name": "assured-forwarding",
"desc": "... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Class of Service for Services PICs (Next Gen Services)"
] |
ftp (Services CoS) | ftp {
data {
dscp (alias | bits);
forwarding-class class-name;
}
} | [edit services cos application-profile profile-name ftp] | Set the appropriate dscp and forwarding-class value for FTP.
Default
By default, the system does not alter the DSCP or forwarding class for FTP traffic. | [] | 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. | [
"Configuring CoS Rules on Services PICs"
] |
ftp (Transfer Log Files) | ftp:url; | [edit services flow-collector transfer-log-archive archive-sites] | Specify the primary and secondary destination FTP server addresses. | [
{
"name": "url",
"desc": "FTP server address."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Transfer Logs"
] |
ftp | ftp {
authentication-order [authentication-methods];
connection-limit limit;
rate-limit limit;
enable-anonymous-login;
} | [edit system services] | Allow FTP requests from remote systems to the local device. | [
{
"name": "authentication-order",
"desc": ""
},
{
"name": "[authentication-methods",
"desc": "Configure the order in which the software tries different user authentication methods when attempting to authenticate a user. For each login attempt, the software tries the authentication methods in ord... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Option ldaps introduced in Junos OS Release 20.2R1.
Option enable-anonymous-login introduced in Junos OS Release 23.2R2. | [
"Configuring FTP Service for Remote Access to the Router or Switch",
"Junos OS User Authentication Methods"
] |
full | [] | [] | |||||
function (Diameter Network Element for Subscriber Management) | function function-name; | [edit access diameter network-element element-name] | Specify the function associated with a Diameter network element. | [
{
"name": "function-name",
"desc": "Function associated with the network element."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
function (Diameter Network Element) | function [function-name]; | [edit diameter network-element element-name] | Specify one or more applications (function) associated with a Diameter network element.
Default
By default, all functions are associated with (supported by) the network element. | [
{
"name": "function-name",
"desc": "Application (function) associated with the route. You can list multiple functions with the"
},
{
"name": "gx-plus",
"desc": "Associate the Gx-Plus application with the network element."
},
{
"name": "jsrc",
"desc": "Associate the JSRC application w... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
Support for PTSP introduced in Junos OS Release 10.2.
Support for Gx-Plus introduced in Junos OS Release 11.2.
Support for PTSP discontinued in Junos OS Release 13.1.
Support for NASREQ added in Junos OS Release 16.1. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
function (Diameter Route) | function function-name <partition partition-name>; | [edit diameter network-element element-name forwarding route dne-route-name] | Specify the application (function) associated with a destination and metric. Together, these three
elements define a route reachable through a Diameter network element.
Default
All functions are associated with the route. | [
{
"name": "function-name",
"desc": "Application (function) associated with the route. Gx-Plus, JSRC, NASREQ, and packet-triggered-subscribers are the applications currently supported."
},
{
"name": "partition partition-name",
"desc": "(Optional) Partition associated with the application (functio... | 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.
Support for PTSP introduced in Junos OS Release 10.2.
Support for Gx-Plus introduced in Junos OS Release 11.2.
Support for PTSP discontinued in Junos OS Release 13.1.
Support for NASREQ added in Junos OS Release 16.1. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
functional-zone | functional-zone {
management {
description text;
host-inbound-traffic {
protocols protocol-name {
except;
}
system-services service-name {
except;
}
}
interfaces interfa... | [edit security zones] | Configure a functional zone. | [] | 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. The description option added in Junos OS Release 12.1. | [
"Understanding Functional Zones",
"G"
] |
g-duplicates-dropped-periodicity | g-duplicates-dropped-periodicity seconds; | [edit services dynamic-flow-capture] | Specify the frequency for sending notifications to affected control sources when transmission of
duplicate sets of data is restricted because the g-max-duplicates threshold has been reached. This setting is
applied globally; the duplicates-dropped-periodicity setting applied at the capture-group level overrides the
glo... | [
{
"name": "seconds",
"desc": "Period for sending DuplicatesDropped notifications."
}
] | 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. | [
"Limiting the Number of Duplicates of a Packet"
] |
g-max-duplicates | g-max-duplicates number; | [edit services dynamic-flow-capture] | Specify the maximum number of content destinations to which DFC PICs can send data from a single
input set of packets. Limiting the number of duplicates reduces the load on the PIC. This setting is
applied globally; the max-duplicates setting applied at the capture-group level overrides the global setting.
Default
If n... | [
{
"name": "number",
"desc": "Maximum number of content destinations."
}
] | 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. | [
"Limiting the Number of Duplicates of a Packet"
] |
garp-na-enable | garp-na-enable; | [edit protocols l2-learning] | Enable sending unsolicited GARP or NA messages.
When learning a new MAC-IP binding on a local PE device, or learning a MAC-IP binding on a remote PE
device via EVPN, an unsolicited GARP or NA message is sent to all connected access CE devices. This
message enables the connected CE devices to update their ARP or ND cach... | [] | [none specified] | Statement introduced in Junos OS Release 23.4R1. | [] |
gate-status | gate-status (uplink | downlink | uplink-downlink | disable-both); | [edit unified-edge pcef pcc-action-profiles profile-name],
[edit services pcef pcc-action-profiles profile-name] | Configure the gate status in a PCC action profile to enable or disable the forwarding of service flow
packets. The gate status determines whether the uplink and downlink gates are opened or closed.
If you are using Junos OS Subscriber Aware, configure the gate status at the [edit unified-edge pcef pcc-
action-profiles ... | [
{
"name": "disable-both",
"desc": "Disable forwarding of service data flow packets in the uplink and downlink directions."
},
{
"name": "downlink",
"desc": "Enable forwarding of service data flow packets in the downlink direction."
},
{
"name": "uplink-downlink",
"desc": "Enable forw... | 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",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Application-Aware Po... |
gate-timeout | gate-timeout seconds; | [edit applications application ike-esp-nat] | For an IKE ALG application, configure the length of time that can pass after IKE establishes the security
association between the IPsec client and server and before the ESP traffic starts in both directions. If the
ESP traffic has not started before this timeout value, the ESP gates are deleted and the ESP traffic is
b... | [
{
"name": "seconds",
"desc": "Number of seconds. Default: 120 seconds"
}
] | 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. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring Application Properties"
] |
gatekeeper | gatekeeper {
threshold rate;
} | [edit logical-systems name security alg h323 application-screen message-flood],
[edit logical-systems name tenants name security alg h323 application-screen message-flood],
[edit security alg h323 application-screen message-flood],
[edit services alg h323 application-screen message-flood],
[edit tenants name security a... | Configure the gatekeeper parameter to limit the rate of requests processed from remote access server
(RAS) to the gatekeeper. Messages exceeding the threshold are dropped. | [
{
"name": "threshold rate",
"desc": "Threshold measured in messages per second."
}
] | 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. | [] |
gateway (Security Group VPN Member IKE) | gateway gateway-name {
ike-policy policy-name;
local address ip-address;
local-identity {
(hostname hostname | inet ip-address | inet6 ipv6-address | user-at-hostname e-mail-
address);
}
remote-identity {
(hostname hostname | inet ip-address | user-at-hostname e-mail-address);
}
... | [edit security group-vpn member ike] | Configure IKE gateway for group VPN member. An IKE gateway initiates and terminates network
connections between a firewall and a security device. | [
{
"name": "gateway gateway-name",
"desc": "Name of the gateway."
},
{
"name": "ike-policy policy-name",
"desc": "Name of the IKE policy."
},
{
"name": "local address ip-address",
"desc": "Configure the IPv4 address the member uses when accessing the group server."
},
{
"name"... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. Support for the routing-instance option added in Junos
OS Release 15.1X49-D30 for vSRX Virtual Firewall. | [
"Group VPNv2 Overview"
] |
gateway (Security Group VPN Server IKE) | gateway gateway-name {
address ip-address;
dead-peer-detection {
always-send;
interval seconds;
threshold number;
}
dynamic {
(hostname hostname | inet ip-address | user-at-hostname e-mail-address);
}
ike-policy policy-name;
local-address ip-address;
local... | [edit security group-vpn server ike] | Configure IKE gateway for group VPN server. | [
{
"name": "gateway gateway-name",
"desc": "Name of the gateway."
},
{
"name": "address ip-address",
"desc": "Specify the IP address of the peer."
},
{
"name": "dead-peer-detection",
"desc": "Enable DPD between group server cluster servers."
},
{
"name": "dynamic",
"desc":... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Support for the Group VPN server added in Junos OS Release 15.1X49-D30 for vSRX Virtual Firewall. | [
"Group VPNv2 Overview"
] |
gateway (Security IKE) | gateway gateway-name {
aaa {
access-profile access-profile {
config-payload-password config-payload-password;
}
client {
password;
username;
}
use-routing-instance-address;
no-push-to-identity-management;
}
address [ip-addr... | [edit security ike] | Configure an IKE gateway. | [
{
"name": "gateway-name",
"desc": "Name of the gateway."
},
{
"name": "address",
"desc": "Specify either the IPv4 or IPv6 addresses or the hostnames of the primary Internet Key Exchange (IKE) gateway (peer) and up to four backup gateways. Consider the following points before configuring multiple... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. Support for IPv6 addresses added in Junos OS Release
11.1. The inet6 option added in Junos OS Release 11.1. Support for the advpn option added in Junos OS
Release 12.3X48-D10.
Option fragmentation is introduced in Junos OS Release 15.1X49-D80.
Option tcp-encap-profile is in... | [
"IPsec Overview",
"Example: Configuring AutoVPN with Pre-Shared Key"
] |
gateway-name (LNS Local Gateway) | gateway-name gateway-name; | [edit services l2tp tunnel-group group-name local-gateway] | Specify the gateway name for the LNS, which the LNS returns to the LAC in response to the LAC’s
SCCRQ message. This name must match the remote gateway name configured on the LAC, or the tunnel
cannot be established. | [
{
"name": "gateway-name",
"desc": "Name of the LNS."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"L2TP LNS Inline Service Interfaces"
] |
gateway-name (Tunnel Profile Remote Gateway) | gateway-name server-name; | [edit access tunnel-profile profile-name tunnel tunnel-id remote-gateway] | Specify the hostname expected by the remote gateway—the LNS—from the source gateway—the LAC—
when you set up a tunnel. | [
{
"name": "server-name",
"desc": "Name of the LNS."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
gateway-name (Tunnel Profile Source Gateway) | gateway-name client-name; | [edit access tunnel-profile profile-name tunnel tunnel-id source-gateway] | Specify the hostname provided by the source gateway—the LAC—to the remote gateway—the LNS—
when you set up a tunnel. | [
{
"name": "client-name",
"desc": "Name of the LAC."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
gbp-pure-l2-profile | gbp-pure-l2-profile; | [edit chassis forwarding-options] | Configure your device to run Group-Based Policy (GBP) in a pure layer 2 environment. A pure layer 2
device does not run EVPN-VXLAN or contain VTEPs.
This setting tells the switch to allocate a share of its resources for L2 group-based policies, whereas
otherwise the resources would remain committed for use by all other... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [
"Microsegmentation Using Group-Based Policies"
] |
general-ikeid | general-ikeid; | [edit security ike gateway gateway_name dynamic] | During IKE Phase 1 negotiation, when negotiation request is received, there are two identity checks.
1. IKE-ID validation from ID payload.
2. Phase 1 authentication by pre-shared key or RSA/DSA certificate.
Configure remote-identity to lookup the certificate of the peer for certificate authentication. This remote-
iden... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1 | [
"Example: Configuring AutoVPN with Pre-Shared Key"
] |
general-param (Flat-File Accounting Options) | general-param {
all-fields;
accounting-type;
descr;
line-id;
logical-interface;
nas-port-id;
physical-interface;
routing-instance;
timestamp;
user-name;
vlan-id;
} | [edit accounting-options flat-file-profile profile-name fields] | Specify general, nonstatistical interface parameters that are displayed as part of the header for the
accounting file. | [
{
"name": "all-fields",
"desc": "Display all available nonstatistical fields. Many fields are available for both logical interfaces and physical interfaces, but some fields are available for only one interface type."
},
{
"name": "accounting-type",
"desc": "(Logical interfaces only ) Display the... | 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.
user-name option added in Junos OS Release 17.1. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Configuring Service Accounting in Local Flat Files",
"Flat-File Accounting Overview"
] |
generate | generate {
defaults {
generate-options;
}
route destination-prefix {
policy policy-name;
generate-options;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name],
[edit routing-options],
[edit routing-options rib routing-table-name] | Configure generated routes, which are used as routes of last resort. | [
{
"name": "defaults",
"desc": "(Optional) Specify global generated route options. These options only set default attributes"
},
{
"name": "generate-options",
"desc": "Additional information about generated routes, which is included with the route"
},
{
"name": "(active | passive);",
... | 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. | [] |
generate-event | generate-event {
event-name (time-interval seconds <start-time start-time> | time-of-day time) <no-drift>;
} | [edit event-options] | Generate an internal event based on a time interval or the time of day. You can configure up to 10
internal events.
Configure time-interval to specify the frequency at which to generate an event, or configure time-of-day to
specify the time at which to generate a daily event. | [
{
"name": "event-name",
"desc": "Name of an internally generated event."
},
{
"name": "no-drift",
"desc": "Do not propagate the delay caused in triggering an event to the triggering of the next event."
},
{
"name": "start-time",
"desc": ""
},
{
"name": "start-time",
"desc... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5.
no-drift option added in Junos OS Release 14.1R1.
start-time option added in Junos OS Release 20.4R1. | [
"Generate Internal Events to Trigger Event Policies"
] |
generate-snmp-traps | generate-snmp-traps; | [edit services]
[edit services video-monitoring] | If this statement is configured, the service generates SNMP traps for severity levels such as Info,
Warning, Critical, or Cleared. For example, if DF alarm changes from info to warning, or from warning to
critical, mdiDFAlarm trap be triggered.
NOTE: SNMP traps are not generated if SNMP trap generation is not enabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Inline Video Monitoring on MX Series Routers"
] |
geo-ip (global-filter) | geo-ip{
rule {
match {
country country-name;
}
then {
action (drop | drop-and-sample);
}
}
} | [edit services web-filter profile profile-name security-intelligence-policy] | Configure the global GeoIP policy for the web-filter profile. | [
{
"name": "country",
"desc": "A list of country codes for which the actions defined under the profile is applied to all"
},
{
"name": "drop",
"desc": "Drop the packets."
},
{
"name": "drop-and-sample",
"desc": "Drop and sample the packets."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1 on MX Series routers with Juniper Advanced Threat
Prevention Cloud . | [
"URL Filtering"
] |
geo-ip (group-filter) | geo-ip{
rule {
match {
group {
(group-name1, group-name2) ;
}
}
then {
action(drop | drop-and-sample);
}
}
} | [edit services web-filter profile profile-name url-filter-template template-name security-
intelligence-policy] | Configure the group-based GeoIP policy for the web-filter template. | [
{
"name": "group",
"desc": "A group of countries to which the defined action is applicable."
},
{
"name": "drop",
"desc": "Drop the packets."
},
{
"name": "drop-and-sample",
"desc": "Drop and sample the packets."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1 on MX Series routers with Juniper Advanced Threat
Prevention Cloud . | [
"GeoIP Filtering"
] |
get-route-range | get-route-range; | [edit logical-systems name policy-options policy-statement name from route-filter],
[edit logical-systems name policy-options policy-statement name term name from route-filter],
[edit policy-options policy-statement name from route-filter],
[edit policy-options policy-statement name term name from route-filter] | Get the range of IPv4 prefixes that goes over a particular tunnel. | [] | routing | Statement introduced in Junos OS Release 19.2R1. | [] |
ggsn-address (OCS Partition) | ggsn-address address; | [edit access ocs partition partition-name] | Include the GGSN-Address AVP value in all CCR-GY messages. | [
{
"name": "address",
"desc": "Address of the GGSN-Address AVP value to include in all CCR-GY messages."
}
] | 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",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
ggsn-mcc-mnc (OCS Partition) | ggsn-mcc-mnc ggsn-mcc-mnc; | [edit access ocs partition partition-name] | Configure the value of the 3GPP-GGSN-MCC-MNC AVP value to include in all CCR-GY messages. The
value is the mobile country code (MCC) and mobile network code (MNC) of the network that the GGSN
belongs to.The combined MCC and MNC uniquely identify the mobile network operator. | [
{
"name": "ggsn-mcc-mnc",
"desc": "Value of the mobile network country and network codes to include in all CCR-GY messages."
}
] | 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",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
gigether-options (Chassis Cluster) | gigether-options {
802.3ad {
backup | primary | bundle;
lacp {
port-priority priority;
}
}
auto-negotiation {
remote-fault {
local-interface-offline | local-interface-online;
}
}
no-auto-negotiation;
ethernet-switch-profile {
... | [edit interfaces interface-name] | Configure Gigabit Ethernet specific interface properties. | [] | 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. | [
"Example: Configuring Chassis Cluster Redundant Ethernet Interfaces"
] |
gigether-options | gigether-options {
802.3ad {
aex (primary | backup);
distribution-list list-name;
lacp {
port-priority;
}
}
(asynchronous-notification | no-asynchronous-notification);
(auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online | local-interf... | [edit interfaces interface-name] | Configure Gigabit Ethernet specific interface properties.
In Junos OS Evolved, when you configure set interfaces interface gigether-options 802.3ad ae name at the
same time as you apply a second configuration to the same interface at the [edit interfaces interface]
hierarchy, the second configuration will not take effe... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Ethernet Interfaces Overview"
] |
global (DDoS) | global {
disable-fpc;
disable-logging;
disable-routing-engine;
flow-detection;
flow-level-control;
flow-detection-mode;
flow-report-rate;
violation-report-rate;
} | [edit system ddos-protection] | (MX Series routers with only MPCs, T4000 routers with only FPC5s, PTX Series routers, EX9200
switches, or QFX Series switches) Modify DDoS policers, event logging, and flow detection globally for
all protocols.
NOTE: The following statements are not supported on PTX Series routers and QFX
Series switches: disable-routi... | [] | 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.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Disabling Control Plane DDoS Protection Policers and Logging Globally"
] |
global (Gx-Plus) | global {
include-ipv6;
max-outstanding-requests number;
} | [edit access gx-plus] | Configure global attributes for the Gx-Plus application.
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 11.2. | [
"Configuring Gx-Plus"
] |
global (OCS) | global {
service-context-id service-context ;
} | [edit access ocs] | Configure global attributes and data elements of the 3rd Generation Partnership Project (3GPP)
Diameter credit control service charging system for the Online Charging System (OCS), which interacts
with the Policy and Charging Enforcement Function (PCEF). The PCEF optionally reports usage and
receives additional authori... | [] | 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 OCS Global Parameters",
"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 Betwe... |
global (PCRF) | global {
rule-param avp-code;
} | [edit access pcrf] | Configure global attributes and data elements of the 3rd Generation Partnership Project (3GPP)
Diameter credit control service charging system for the Online Charging System (OCS), which interacts
with the Policy and Charging Rules Function (PCRF). The PCRF optionally reports usage and receives
additional authorization... | [] | 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. | [
"3GPP Policy and Charging Control Overview for Wireline Provisioning and Accounting",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCRF, and OCS"
] |
global (Security IDP) | global {
(enable-all-qmodules | no-enable-all-qmodules);
(enable-packet-pool | no-enable-packet-pool);
memory-limit-percent value;
(policy-lookup-cache | no-policy-lookup-cache);
} | [edit security idp sensor-configuration] | Configure the global rulebase IDP security policy. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
global (Security Policies) | global {
policy policy-name {
description description;
match {
application {
[application];
any;
}
destination-address {
[address];
any;
any-ipv4;
... | [edit security policies] | Configure a global policy. | [] | 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. Statement updated with from-zone and to-zone policy
match options in Junos OS Release 12.1X47-D10. | [
"Global Policy Overview"
] |
global-advertisements-threshold | global-advertisements-threshold advertisement-value; | [edit protocols vrrp] | Configure the number of fast advertisements that can be missed by a backup router before the primary
router is declared as down.
NOTE:
•
The advertisement value configured using the global-advertisements-threshold statement
is applicable to all the Virtual Router Redundancy Protocol (VRRP) groups in the
system.
•
Set... | [
{
"name": "advertisement-value",
"desc": "Number of VRRP advertisements missed before the primary router is declared as"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Improving the Convergence Time for VRRP",
"Configuring VRRP to Improve Convergence Time"
] |
global-arp-prefix-limit (Host Fast Reroute) | global-arp-prefix-limit number; | [edit logical-systems logical-system-name routing-options host-fast-reroute],
[edit routing-options host-fast-reroute] | Set the ARP prefix limit for all host fast-reroute (HFRR) profiles on the routing device.
When you configure HFRR, an optional ARP prefix limit sets a maximum for the number of ARP routes
and, therefore FRR routes created for each HFRR profile in the routing table. This limit prevents ARP
attacks from exhausting the vi... | [
{
"name": "number",
"desc": "Maximum number of ARP HFRR routes allowed. Range: 1 through 10,000 HFRR routes"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring Link Protection with Host Fast Reroute"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.