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 |
|---|---|---|---|---|---|---|---|
bandwidth (MPC Bandwidth) | bandwidth bandwidth; | [edit chassis fpc slot] | Configure the MPC bandwidth.
By default, MPC8E provides a maximum bandwidth of 960 Gbps. You can upgrade MPC8E to provide an
increased bandwidth of 1600 Gbps (1.6 Tbps) by using an add-on license. After you purchase the license
and configure the bandwidth 1.6T statement, MPC8E provides an increased bandwidth of 1.6 Tbp... | [
{
"name": "bandwidth",
"desc": "Configure the MPC to operate at a specified bandwidth. You can specify 1.6T as the value to configure the MPC to operate at a bandwidth of 1.6 Tbps."
}
] | 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. | [
"MPC8E"
] |
bandwidth (multicast) | bandwidth ( bps | adaptive ); | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast flow-map],
[edit logical-systems logical-system-name routing-options multicast flow-map],
[edit routing-instances routing-instance-name routing-options multicast flow-map],
[edit routing-options multicast flow-m... | Configure the bandwidth property for multicast flow maps. | [
{
"name": "adaptive",
"desc": "Specify that the bandwidth is measured for the flows that are matched by the flow map."
},
{
"name": "bps",
"desc": "Bandwidth, in bits per second, 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.3. | [
"Example: Configuring a Multicast Flow Map"
] |
bandwidth (Protocols Layer 2 Circuit) | bandwidth (bandwidth | ctnumber bandwidth); | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit protocols l2circuit neighbor address interface interface-name] | Specify bandwidth allocation for a Layer 2 circuit or for the class types of a Layer 2 circuit. | [
{
"name": "bandwidth",
"desc": "Configure the bandwidth in bits per second for the Layer 2 circuit. You cannot configure the"
},
{
"name": "ctnumber bandwidth",
"desc": "Configure the bandwidth in bits per second for a class type on the Layer 2 circuit. You"
}
] | 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 Bandwidth Allocation and Call Admission Control in Layer 2 Circuits"
] |
bandwidth (Protocols RSVP) | bandwidth bps; | [edit logical-systems logical-system-name protocols rsvp interface interface-name],
[edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection bypass bypass-name],
[edit protocols... | For certain logical interfaces (such as Asynchronous Transfer Mode [ATM], Permanent Virtual Circuit
[PVC], or Frame Relay), you cannot determine the correct bandwidth from the hardware. This statement
enables you to specify the actual available bandwidth.
This statement also enables you to specify the bandwidth for a ... | [
{
"name": "bps",
"desc": "Bandwidth in bits per second. You can specify this as an integer value. If you do so, count your zeros"
}
] | 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 Bandwidth for Bypass LSPs",
"Configuring Link Protection on Interfaces Used by LSPs",
"Configuring Bypass LSPs"
] |
bandwidth (RFC 2544 Benchmarking) | bandwidth bits-per-second (kbps | mbps | gbps) | [edit services monitoring rfc2544 test-profile profile-name] | For an RFC 2544 benchmarking test, configure the rate of the traffic generated and sent out at the
interface, in kilobits per second (kbps), megabits per second (mbps), or gigabits per second (gbps). The
maximum rate is 100 gbps. This rate determines the characteristics of the network under test. This value
is typicall... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R1. | [] |
bandwidth (Static LSP) | bandwidth bps; | [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
bypass],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
transit incoming-la... | When configuring a static LSP, specify the traffic rate associated with the LSP. | [
{
"name": "bps",
"desc": "Bandwidth, in bits per second. You can specify this as an integer value. You can also use the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring Static LSPs"
] |
bandwidth (storm control) | bandwidth bandwidth; | [edit ethernet-switching-options storm-control interface (all | interface-name)] | Configure the storm control level as the bandwidth in kilobits per second of the applicable traffic
streams, as follows:
•
On EX2200, EX3200, EX3300, EX4200, and EX6200 switches—Applies to the combined broadcast
and unknown unicast streams by default. Storm control does not apply to multicast traffic by default
on thes... | [
{
"name": "bandwidth",
"desc": "Traffic rate in kilobits per second of the combined applicable traffic streams."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Autorecovery for Port Security Events",
"Enabling and Disabling Storm Control (non-ELS)"
] |
bandwidth (Tunnel Services) | bandwidth bandwidth-value; | [edit chassis fpc slot-number pic number tunnel-services]
[edit chassis fpc slot-number pfe pfe-id core core-id channel channel-id tunnel-services]
[edit chassis feb slot slot-number pfe pfe-id core core-id channel channel-id tunnel-services] | (ACX Series, MX Series 5G Universal Routing Platforms and T4000 Core Routers only) Configure the
amount of bandwidth in gigabits per second reserved on each Packet Forwarding Engine for tunnel
traffic using tunnel services. Configuring the bandwidth creates a virtual tunnel interface that is
represented as interface-<f... | [
{
"name": "bandwidth-value",
"desc": "Amount of bandwidth in Gbps to reserve for tunnel traffic using tunnel services:"
},
{
"name": "1g",
"desc": "10g through 100g in 10 Gbps increments: 10g, 20g, 30g, 40g, 50g, 60g, 70g, 80g, 90g, 100g 100g through 400g in 100 Gbps increments: 100g, 200g, 300... | 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.
Statement introduced in Junos OS Evolved Release 24.1R1 for ACX7K Series Routers. | [
"Example: Configuring Tunnel Interfaces on a Gigabit Ethernet 40-Port DPC",
"Tunnel Interface Configuration on MX Series Routers Overview",
"Configuring Tunnel Interfaces on T4000 Routers",
"Example: Configuring Tunnel Interfaces on a 10-Gigabit Ethernet 4-Port DPC",
"Example: Configuring Tunnel Interfaces ... |
bandwidth-based-metrics (Protocols OSPF) | bandwidth-based-metrics {
bandwidth value;
metric number;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface
interface-name],
[edit logical-systems logical-system-name protocols ospf area area-id interface interface-name
topology topology-name],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multic... | Specify a set of bandwidth threshold values and associated metric values for an OSPF interface or for a
topology on an OSPF interface. When the bandwidth of an interface changes, Junos OS automatically
sets the interface metric to the value associated with the appropriate bandwidth threshold value. | [
{
"name": "bandwidth value",
"desc": "Specify the bandwidth threshold in bits per second."
},
{
"name": "metric number",
"desc": "Specify a metric value to associate with a specific bandwidth value."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Example: Dynamically Adjusting OSPF Interface Metrics Based on Bandwidth",
"Example: Dynamically Adjusting OSPF Interface Metrics Based on Bandwidth"
] |
bandwidth-based-metrics | bandwidth-based-metrics {
bandwidth threshold {
metric metric;
}
} | [edit logical-systems name protocols isis interface-group name level name topology],
[edit logical-systems name routing-instances name protocols isis interface-group name level name
topology],
[edit logical-systems name tenants name routing-instances name protocols isis interface-group
name level name topology],
[edi... | Specify a set of bandwidth threshold values and associated metric values for an IS-IS interface or a
group of interfaces configured under IS-IS interface-group. Depending on the combined bandwidth of the
member interfaces, IS-IS advertises the specified metric value for the interface. When the cumulative
bandwidth of a... | [
{
"name": "bandwidth threshold",
"desc": "Specify the bandwidth threshold in bits per second. Range: 9600 through 1,000,000,000,000,000"
},
{
"name": "metric metric metric",
"desc": "Specify a metric value to associate with a specific bandwidth value. Range: 0 through 16,777,215"
}
] | routing—To view this statement in the configuration. | Statement introduced in Junos OS Release 16.1R1. | [] |
bandwidth-degradation | bandwidth-degradation {
action (log-only | restart | offline | restart-then-offline);
no-fabric-switchover;
percentage (1-99);
} | [edit chassis fpc slot-number fabric] | Configure a FPC to take a specific action once bandwidth degradation reaches a certain percentage to
avoid causing a null route in the chassis.
NOTE: This configuration statement is mutually exclusive with the offline-on-fabric-
bandwidth-reduction statement. If both statements are configured, the commit check fails
an... | [
{
"name": "log-only",
"desc": "A message gets logged in the chassisd and message files when the fabric degradation threshold is reached. No other actions are taken."
},
{
"name": "restart",
"desc": "The FPC with a degraded fabric plane is restarted once the threshold is reached."
},
{
"n... | 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. | [
"Managing Bandwidth Degradation"
] |
bandwidth-kbps | bandwidth-kbps kbps; | [edit services rpm rfc2544-benchmarking profilestest-profile profile-name] | Define the theoretical maximum bandwidth, in kilobits per second, for the test. The theoretical limit of
the media for the frame size configured for the test. This value is typically set to the bandwidth of the
server being tested. The range is 1,000 Kbps through 1,000,000 Kbps (1 Gbps). The value defined is the
highes... | [
{
"name": "kbps",
"desc": "Bandwidth limit, in kilobits per second (kpbs). Range: 1,000 kbps through 1,000,000 Kbps."
}
] | 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"
] |
bandwidth-level | bandwidth-level kbps; | [edit forwarding-options storm-control-profiles profile-name all] | Configure the storm control level as the bandwidth in kilobits per second of the available bandwidth
used by the combined broadcast, multicast, and unknown unicast traffic streams.
NOTE: When you configure storm control level on an aggregated Ethernet interface, the
storm control level for each member of the aggregated... | [
{
"name": "bandwidth-level kbps",
"desc": "Traffic rate in kilobits per second of the combined broadcast, multicast, and"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Example: Configuring Storm Control to Prevent Network Outages on EX Series Switches",
"Example: Using Storm Control to Prevent Network (MX Routers)",
"Enabling and Disabling Storm Control (ELS)"
] |
bandwidth-limit (Hierarchical Policer) | bandwidth-limit bps; | [edit dynamic-profiles profile-name firewall hierarchical-policer aggregate if-exceeding],
[edit dynamic-profiles profile-name firewall hierarchical-policer premium if-exceeding],
[edit firewall hierarchical-policer aggregate if-exceeding],
[edit firewall hierarchical-policer premium if-exceeding] | On M40e, M120, and M320 (with FFPC and SFPC) edge routers; on MPCs hosted on MX Series routers;
on T320, T640, and T1600 core routers with Enhanced Intelligent Queuing (IQE) PICs; and on T4000
routers with Type 5 FPC and Enhanced Scaling Type 4 FPC, configure the maximum average bandwidth
for premium or aggregate traff... | [
{
"name": "bps",
"desc": "You can specify the number of bits per second either as a decimal number or as a decimal number"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles ... if-exceeding] hierarchy level introduced in Junos OS Release 11.4. | [
"Hierarchical Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Determining Proper Burst Size for Traffic Policers"
] |
bandwidth-limit (Policer for Gigabit Ethernet Interfaces) | bandwidth-limit bps; | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
policer cos-policer-name aggregate],
[edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
policer cos-policer-name premium] | Define a policer to apply to nonpremium traffic. | [
{
"name": "bps",
"desc": "Bandwidth limit, in bits per second. Specify either as a complete decimal number or as a decimal"
}
] | 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"
] |
bandwidth-limit (Policer) | bandwidth-limit bps; | [edit dynamic-profiles profile-name firewall policer policer-name if-exceeding],
[edit firewall policer policer-name if-exceeding],
[edit logical-systems logical-system-name policer policer-name if-exceeding] | For a single-rate two-color policer, configure the bandwidth limit as a number of bits per second. Single-
rate two-color policing uses the single token bucket algorithm to measure traffic-flow conformance to a
two-color policer rate limit.
Traffic at the interface that conforms to the bandwidth limit is categorized gr... | [
{
"name": "bps",
"desc": "You can specify the number of bits per second either as a decimal number or as a decimal number"
},
{
"name": "(ACX series routers)",
"desc": "Single-Rate Two-Color Policer"
},
{
"name": "22000..400000000000",
"desc": "Single-Rate Three-Color Policer committ... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... if-exceeding] hierarchy level introduced in Junos OS Release 11.4. | [
"Two-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Determining Proper Burst Size for Traffic Policers"
] |
bandwidth-limit | bandwidth-limit bps; | [edit firewall policer policer-name if-exceeding]
[edit logical-systems logical-system-name firewall policer policer-name if-exceeding] | Specify the traffic rate in bits per second. | [
{
"name": "bps",
"desc": "Traffic rate to be specified in bits per second. Specify bps as a decimal value or as a decimal"
},
{
"name": "k (thousand)",
"desc": ""
},
{
"name": "m (million)",
"desc": "g (billion, which is also called a thousand million) Range: 1000 (1k) through 102,... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on EX Series Switches",
"Configuring Policers to Control Traffic Rates (CLI Procedure)",
"Understanding the Use of Policers in Firewall Filters",
"Basic Single-Rate Two-Color Policers"
] |
bandwidth-model | bandwidth-model {
extended-mam;
mam;
rdm;
} | [edit logical-systems logical-system-name protocols mpls diffserv-te],
[edit protocols mpls diffserv-te] | Configure the bandwidth model for differentiated services. Note that you cannot configure both
bandwidth models at the same time. | [
{
"name": "extended-mam",
"desc": "The extended maximum allocation model (MAM) is a bandwidth model based on MAM."
},
{
"name": "mam",
"desc": "The MAM is defined in RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering."
},
{
"name": "rdm",... | 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 Bandwidth Model"
] |
bandwidth-percent (protocols mpls) | bandwidth-percent percentage; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name fast-
reroute],
[edit protocols mpls label-switched-path lsp-name fast-reroute] | Configure the percentage of bandwidth to reserve for the detour path in case the primary path for a
traffic engineered LSP or a multiclass LSP fails. The percentage configured indicates the percentage of
the protected path’s bandwidth that is reserved for the detour path. | [
{
"name": "percentage",
"desc": "The percentage of the protected path’s bandwidth that is reserved for the detour path."
}
] | 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 Fast Reroute",
"Configuring Fast Reroute for Traffic-Engineered LSPs",
"Configuring Fast Reroute for Multiclass LSPs"
] |
bandwidth-percent | bandwidth-percent percentage; | [edit dynamic-profiles profile-name firewall policer policer-name if-exceeding],
[edit firewall policer policer-name if-exceeding],
[edit logical-systems logical-system-name policer policer-name if-exceeding] | For a single-rate two-color policer, configure the bandwidth limit as a percentage value. Single-rate two-
color policing uses the single token bucket algorithm to measure traffic-flow conformance to a two-color
policer rate limit.
Traffic at the interface that conforms to the bandwidth limit is categorized green. Traf... | [
{
"name": "percentage",
"desc": "Traffic rate as a percentage of either the physical interface media rate or the logical interface"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... if-exceeding] hierarchy level introduced in Junos OS Release 11.4. | [
"Two-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Determining Proper Burst Size for Traffic Policers",
"Bandwidth Policers"
] |
bandwidth-percentage | bandwidth-percentage percentage; | [edit forwarding-options storm-control-profiles profile-name all] | Configure the storm control level as the percentage of total interface bandwidth used by the combined
broadcast, multicast, and unknown unicast traffic streams on an interface. The storm control level is
configured as part of the storm control profile. As an example, a 10 Gbps interface with a 10% storm-
control bandw... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Example: Configuring Storm Control to Prevent Network Outages on EX Series Switches",
"Example: Using Storm Control to Prevent Network (MX Routers)",
"Enabling and Disabling Storm Control (ELS)"
] |
bandwidth-requested | bandwidth-requested bps; | [edit logical-systems name protocols source-packet-routing compute-profile compute-profile-name],
[edit protocols source-packet-routing compute-profile compute-profile-name] | SR path requested bandwidth in bits per second (bps).
Configure the requested bandwidth (in bps) for delegated SR-TE LSPs. The Path Computation Client
(PCC) reports the requested bandwidth value in PCRpt messages to the Path Computation Element
(PCE). This configuration applies to delegated SR-TE LSPs; it is not used f... | [
{
"name": "bps",
"desc": "Requested bandwidth, in bits per second (bps)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2. | [
"PCEP Configuration"
] |
bandwidth-reservation-priority | bandwidth-reservation-priority {
reservation-priority;
setup-priority;
} | [edit logical-systems name protocols source-packet-routing compute-profile compute-profile-name],
[edit protocols source-packet-routing compute-profile compute-profile-name] | Configure the reservation priority and setup priority for delegated SR-TE LSPs.
These values control how bandwidth reservations are handled and how LSPs are preempted when
network resources are constrained. Both values must be configured together.
•
Reservation priority determines how likely an LSP is to hold onto reso... | [
{
"name": "reservation-priority",
"desc": "Defines the reservation priority of the LSP. Range: 0 through 7 0 is the highest priority (least likely to be preempted). 7 is the lowest priority (most likely to be preempted)."
},
{
"name": "setup-priority",
"desc": "Defines the setup (holding) pri... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2. | [
"PCEP Configuration"
] |
bandwidth-scale (DDoS) | bandwidth-scale percentage; | [edit system ddos-protection protocols protocol-group (aggregate | packet-type) fpc slot-number] | (MX Series routers with only MPCs, T4000 routers with only FPC5s, PTX Series routers, EX9200
switches, or QFX Series switches) Configure the percentage by which the DDoS bandwidth rate limit is
scaled down for the aggregate or packet-type policer on the card in the specified slot. | [
{
"name": "percentage",
"desc": "Percentage multiplied by the bandwidth rate limit to reduce the number of packets per"
}
] | 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"
] |
bandwidth-threshold | bandwidth-threshold bits-per-second priority-cost priority; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id track interface interface-name],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id track interface interface-name],
[edit logical-systems logical-syste... | Specify the bandwidth threshold for Virtual Router Redundancy Protocol (VRRP) logical interface
tracking. | [
{
"name": "bits-per-second",
"desc": "Bandwidth threshold for the tracked interface. When the bandwidth of the tracked"
},
{
"name": "priority-cost priority",
"desc": "The value subtracted from the configured VRRP priority when the tracked"
}
] | 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 a Logical Interface to Be Tracked for a VRRP Group"
] |
banner (Access FTP HTTP Telnet Authentication) | banner {
fail string;
login string;
success string;
} | [edit access firewall-authentication pass-through (ftp | http | telnet)] | Configure the banners that appear to users during the FTP, HTTP, HTTPS, and Telnet firewall
authentication process. The banners appear during login, after successful authentication, and after 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.
HTTPS for Web authentication is supported on SRX5400, SRX5600, and SRX5800 devices and SRX
Series Firewalls from Junos OS Release 12.1X44-D10 and on SRX300, SRX320, SRX340, SRX345,
SRX380, and SRX1500 Services Gateways from Junos OS Release 15.1X49-D40. | [
"Customize Banner",
"Example: Customize Banner",
"Configure a Custom Logo and Banner Messages"
] |
banner (Access Web Authentication) | banner {
fail string;
logout string;
success string;
} | [edit access firewall-authentication web-authentication] | Configure the banner that appears to users during the Web authentication process. The banner appears
during login, after successful authentication, and after 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. | [
"Customize Banner",
"Example: Customize Banner",
"Configure a Custom Logo and Banner Messages"
] |
base-distinguished-name | base-distinguished-name base-distinguished-name; | [edit access ldap-options],
[edit access profileprofile-name ldap-options] | Specify the base distinguished name (DN), which can be used in one of the following ways:
•
If you are using the assemble statement so that the user's distinguished name is being assembled, the
base distinguished name is appended to a username to generate the user's distinguished name. The
resulting distinguished name ... | [
{
"name": "base-distinguished-name",
"desc": "Series of basic properties that define the user. For example in the base"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
batch query | batch-query {
items-per-batch items-per-batch;
query-interval seconds;
} | [edit services user-identification identity-management] | Configure the SRX Series Firewall to communicate with the Juniper Identity Management Service server
to obtain an access token to use to query the server for identity information for an individual user (IP
query and user query) or a group of users (batch query). The access token allows the SRX Series Firewall
to connec... | [
{
"name": "items-per-batch",
"desc": "The maximum number of user identity items that the SRX Series Firewall will accept in one batch in response to the query. Default: 200 Range: 100-1000 query-interval. Interval in seconds after which the SRX Series Firewall will issue a query request for newly generate... | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D100. | [
"Understanding Advanced Query Feature for Obtaining User Identity Information from JIMS"
] |
bb-sc-n | bb-sc-n bb-sc-n; | [edit interfaces interface-name fibrechannel-options] | Configure the buffer-to-buffer credit state change number to prevent the permanent loss of Fibre
Channel credits over time (buffer-to-buffer credit recovery). | [
{
"name": "bb-sc-n",
"desc": "Number of buffer-to-buffer state change credits."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric",
"Converting an Ethernet Interface To a Fibre Channel Interface",
"Configuring a Physical Fibre Channel Interface",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
beacon-period | beacon-period milliseconds; | [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) examine-fip examine-
vn2vn],
[edit vlans vlan-name forwarding-options fip-security] | Set the interval between periodic beacons. Beacons perform virtual link maintenance for VN_Ports in a
way that is similar to FIP keepalive advertisements.
The ENode sends periodic beacons every 90 seconds on behalf of the VN_Port. Each received beacon
resets the session timer for the virtual link connection to the othe... | [
{
"name": "milliseconds",
"desc": "Time in milliseconds between beacons."
}
] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2.
Statement introduced for the ELS CLI in Junos OS Release 13.2 for the QFX Series. | [
"Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to the Same FCoE",
"Transit Switch)",
"Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to Different FCoE",
"Transit Switches)",
"Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Indirectly Connec... |
bearer-type (L2TP Tunnel Switching) | bearer-type action; | [edit access tunnel-switch-profile profile-name avp] | Specify the action taken on the Bearer Type AVP (18) in the L2TP packets during tunnel switching if the
AVP is negotiated when the first session is created. | [
{
"name": "action",
"desc": "One of the following actions:"
},
{
"name": "drop",
"desc": "Drop the AVP."
},
{
"name": "regenerate",
"desc": "Regenerate the AVP based on the local policy at the LTS and send it in the switched"
},
{
"name": "relay",
"desc": "Forward the AVP... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
ber-threshold-clear | ber-threshold-clear value; | [edit interfaces interface-name otn-options signal-degrade]
[edit interfaces interface-name otn-options odu-signal-degrade] | Specify bit error rate (BER) threshold to clear the interface alarm for signal degradation.
You can configure the BER clear threshold to customize the BER that will clear an interface alarm when
signal degrade monitoring is enabled.
NOTE: Configuring a high BER threshold for signal degradation and a long interval might... | [
{
"name": "Values: value",
"desc": "BER threshold for clearing the signal degradation in scientific notation. Both the"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Understanding Pre-FEC BER Monitoring and BER Thresholds",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
ber-threshold-signal-degrade | ber-threshold-signal-degrade value; | [edit interfaces interface-name otn-options signal-degrade]
[edit interfaces interface-name otn-options odu-signal-degrade] | Specify the bit error rate (BER) threshold to raise an interface alarm for signal degradation.
You can configure the BER signal degrade threshold to customize the BER that will raise an interface
alarm when signal degrade monitoring is enabled.
NOTE: Configuring a high BER threshold for signal degradation and a long in... | [
{
"name": "value",
"desc": "BER threshold for signal degradation in scientific notation. Both the mantissa and exponent are"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Understanding Pre-FEC BER Monitoring and BER Thresholds",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
bert-algorithm | bert-algorithm algorithm; | [edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options] | Configure the pattern to send in the bit stream during a bit error rate test (BERT). Applies to T1, E3, T3,
and multichannel DS3 interfaces, the channelized interfaces (DS3, OC12, STM1), and channelized IQ
and IQE interfaces (E1, E3 and DS3).
NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1 IQE... | [
{
"name": "algorithm",
"desc": "Pattern to send in the bit stream. There are two categories of test patterns: pseudorandom"
},
{
"name": "all-ones-repeating",
"desc": "Pattern is all ones."
},
{
"name": "all-zeros-repeating",
"desc": "Pattern is all zeros."
},
{
"name": "alte... | 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. | [
"Interface Diagnostics",
"Configuring E1 BERT Properties",
"Configuring E3 BERT Properties",
"Configuring T1 BERT Properties",
"Configuring T3 BERT Properties",
"Examples: Configuring T3 Interfaces"
] |
bert-error-rate | bert-error-rate rate; | [edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options] | Configure the bit error rate to use in a BERT procedure. Applies to E1, E3, T1, or T3 interfaces, and to
the channelized interfaces (DS3, OC3, OC12, and STM1).
NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1 IQE
PICs, the bert-error-rate statement must be included at the [edit interfaces ce1-f... | [
{
"name": "rate",
"desc": "Bit error rate."
}
] | 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. | [
"ds0-options",
"e1-options",
"e3-options",
"t1-options",
"t3-options",
"Interface Diagnostics",
"Configuring E1 BERT Properties",
"Configuring E3 BERT Properties",
"Configuring T1 BERT Properties",
"Configuring T3 BERT Properties",
"Examples: Configuring T3 Interfaces"
] |
bert-period | bert-period seconds; | [edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options] | Configure the duration of a BERT test. Applies to E1, E3, T1, and T3 interfaces, and to E1, E3, T1, and
T3 partitions on the channelized interfaces (CE1, CT1, DS3, OC3, OC12, OC48, STM1, STM4, and
STM16).
E1 and T1 IQ, IQE, and standard interfaces support an extended BERT period range, up to 86,400
seconds (24 hours).
... | [
{
"name": "seconds",
"desc": "Test duration. Range and default values vary by interface type."
},
{
"name": "PIC-dependent",
"desc": "Normal BERT period: either 1 through 239 seconds or 1 through 240 seconds"
},
{
"name": "PIC-dependent",
"desc": "Extended BERT period: from 1 through... | 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. | [
"Interface Diagnostics",
"Configuring E1 BERT Properties",
"Configuring E3 BERT Properties",
"Configuring T1 BERT Properties",
"Configuring T3 BERT Properties"
] |
best-site | best-site; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
site site-name],
[edit routing-instances routing-instance-name protocols vpls site site-name] | Enables the VPLS multihoming best site functionality, allowing the site on which it has been enabled to
be the preferred site for this PE router. This statement must be configured on all PE routers within the
optimized VPLS routing instance.
NOTE: In the VPLS documentation, the word router in terms such as PE router is... | [] | 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: VPLS Multihoming, Improved Convergence Time"
] |
bfd (protocols) | bfd {
traceoptions {
file filename <files number> <match regular-expression> <size size> <world-
readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
} ... | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "(Optional) Disable the BFD tracing operation. You can use this option to disable a single"
},
{
"name": "file filename",
"desc": "Name of the file to receive the output of the tracing operation. Enclose the name in"
},
{
"name": "files number",
"desc": "... | routing and trace—To view this statement in the configuration.
routing-control and trace–control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection"
] |
bfd | bfd {
version (0 | 1 | automatic);
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
detection-time {
threshold milliseconds;
}
... | [edit system services dhcp-local-server liveness-detection method],
[edit system services dhcp-local-server dhcpv6 liveness-detection method],
[edit forwarding-options dhcp-relay liveness-detection method],
[edit forwarding-options dhcp-relay dhcpv6 liveness-detection method],
[edit system services dhcp-local-server gr... | Configure Bidirectional Forwarding Detection (BFD) as the liveness detection method.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients"
] |
bfd-liveliness (Activeness Probe) | bfd-liveliness {
destination-ip destination-ip;
interface interface;
minimum-interval milliseconds;
multiplier multiplier;
routing-instance routing-instance;
source-ip source-ip;
} | [edit chassis high-availability services-redundancy-group name activeness-probe] | Configure BFD monitoring for split-brain detection in a Multinode High Availability setup. | [
{
"name": "destination-ip destination-ip",
"desc": ""
},
{
"name": "interface interface-name",
"desc": ""
},
{
"name": "minimum-interval milliseconds",
"desc": ""
},
{
"name": "multiplier multiplier",
"desc": ""
},
{
"name": "routing-instance routing-instance",
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
bfd-liveliness | bfd-liveliness {
destination-ip destination-ip {
interface interface;
routing-instance routing-instance;
session-type(multihop | singlehop);
src-ip src-ip;
weight value;
}
threshold value; | [edit chassis high-availability services-redundancy-group name monitor],
[edit chassis high-availability services-redundancy-group name monitor monitor-object name] | Configure Bidirectional Forwarding Detection (BFD) monitoring to detect failures in a network. You can
configure Multinode High Availability to monitor one or more links using BFD. This configuration
triggers a failover in the event of BFD failure. Configure BFD liveliness by specifying source and
destination IP and t... | [
{
"name": "<dst-ip>",
"desc": "Destination IPV4/IPV6 address for BFD monitoring"
},
{
"name": "interface interface",
"desc": ""
},
{
"name": "routing-instance routing-instance",
"desc": ""
},
{
"name": "session-type",
"desc": ""
},
{
"name": "src-ip src-ip",
"... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [] |
bfd-liveness-detection (BGP) | bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
holddown-interval milliseconds;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
mu... | [edit logical-systems name protocols bgp],
[edit logical-systems name protocols bgp group group-name],
[edit logical-systems name protocols bgp group group-name neighbor address],
[edit logical-systems name routing-instances name protocols bgp],
[edit log... | Configure bidirectional failure detection (BFD) timers and authentication for BGP.
For IBGP and multihop EBGP support, configure the bfd-liveness-detection statement at the global [edit
bgp protocols] hierarchy level. You can also configure IBGP and multihop support for a routing instance or
a logical system. | [
{
"name": "holddown-interval",
"desc": ""
},
{
"name": "milliseconds",
"desc": "(Optional) Configure an interval specifying how long a BFD session must remain up before a state change notification is sent. When you configure the hold-down interval for the BFD protocol for EBGP, the BFD session i... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
detection-time threshold and transmit-interval threshold options introduced in Junos OS Release 8.2.
Support for logical routers introduced in Junos OS Release 8.3.
Support for IBGP and multihop EBGP sessions introduced in Junos OS Release 8.3.
holddown-interval option intr... | [
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection",
"Example: Configuring BFD Authentication for Securing Static Routes",
"Example: Configuring BFD on Internal BGP Peer Sessions",
"Example: Configuring BFD Authentication for BGP",
"Understanding BFD for BGP"
] |
bfd-liveness-detection (EVPN Node Detection) | bfd-liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
inline-disable;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier multiplier;
neighbor neighbor;
pdu-size bytes;
transmit-interval {
minimum-interval milliseconds;
... | [edit logical-systems name protocols evpn node-detection],
[edit protocols evpn node-detection] | Configure Bidirectional Forwarding Detection (BFD) timers and options for EVPN node detection. | [
{
"name": "no-adaptation",
"desc": "Disable the BFD adaptation. Include this statement to prevent the BFD sessions from adapting to changing network conditions."
},
{
"name": "detection-time",
"desc": "Mandatory"
},
{
"name": "threshold milliseconds",
"desc": "Configure a threshold f... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [
"Backup Liveness Detection on EVPN Dual Homing"
] | |
bfd-liveness-detection (LAG) | bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
damping {
half-life-interval seconds;
increment increment;
max-suppress-time seconds;
reuse reuse;
suppress suppress;
}
detect... | [edit interfaces name aggregated-ether-options],
[edit dynamic-profiles name interfaces name aggregated-ether-options],
[edit dynamic-profiles name logical-systems name interfaces name aggregated-ether-options] | Configure Bidirectional Forwarding Detection (BFD) timers and authentication for aggregated Ethernet
interfaces. | [
{
"name": "holddown-interval",
"desc": ""
},
{
"name": "milliseconds",
"desc": "Specify a time limit, in milliseconds, indicating the time that a BFD session remains up before a state change notification is sent. If the BFD session goes down and then comes back up during the hold-down interval, ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"authentication",
"detection-time",
"transmit-interval",
"Configuring Micro BFD Sessions for LAG",
"Example: Configuring Independent Micro BFD Sessions for LAG",
"Understanding Independent Micro BFD Sessions for LAG"
] |
bfd-liveness-detection (Layer 2 VPN and VPLS) | bfd-liveness-detection {
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
pdu-size bytes;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
... | [edit logical-systems name routing-instances instance_name protocols l2vpn oam],
[edit logical-systems name routing-instances instance_name protocols vpls neighbor neighbor-id
oam],
[edit logical-systems name routing-instances instance_name protocols vpls mesh-group mesh-group-
name neighbor neighbor-id oam],
[edit l... | Configure bidirectional failure detection timers.
The BFD failure detection timers are adaptive and can be adjusted to be more or less aggressive. For
example, the timers can adapt to a higher value if the adjacency fails, or a neighbor can negotiate a
higher value for a timer than the configured value. The timers adap... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Statement introduced in Junos OS Release 13.2 for Layer 2 VPNs and VPLS.
pdu-size option introduced in Junos OS Release 23.2 for MX Series devices. | [
"Configuring BFD for Layer 2 VPN and VPLS",
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection"
] |
bfd-liveness-detection (LSP) | bfd-liveness-detection {
minimum-interval milliseconds;
multiplier multiplier;
no-router-alert-option;
sbfd {
remote-discriminator remote-discriminator;
}
} | [edit protocols source-packet-routing segment-list],
[edit protocols source-packet-routing source-routing-path lsp-name primary segment-list-name],
[edit protocols source-packet-routing source-routing-path lsp-name secondary segment-list-name] | Bidirectional forwarding detection options. | [
{
"name": "minimum-interval",
"desc": "Minimum transmit and receive interval (milliseconds). Range: 1 through 255000"
},
{
"name": "multiplier",
"desc": "Detection time multiplier. Default: 3 Range: 1 through 255"
},
{
"name": "no-router-alert-option",
"desc": "Do not set the Rout... | routing | Statement introduced in Junos OS Release 18.4R1.
Support at the following hierarchy levels introduced in Junos OS Release 19.1R1: [edit protocols source-
packet-routing source-routing-path lsp-name primary segment-list-name], and [edit protocols source-packet-routing
source-routing-path lsp-name secondary segment-list-... | [] |
bfd-liveness-detection (Protocols IS-IS) | bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
... | [edit logical-systems logical-system-name protocols isis interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name],
[edit protocols isis interface interface-name],
[edit protocols isis interface interface-name family (inet | in... | Configure bidirectional failure detection timers and authentication.
NOTE: Starting with Junos OS Release 16.1, you can configure IS-IS BFD sessions for
the IPv6 address family. Therefore, this configuration statement is also available under
the [edit protocols isis interface interface-name family inet|inet6] hierarchy... | [
{
"name": "authentication algorithm algorithm-name",
"desc": "Configure the algorithm used to authenticate the specified BFD"
},
{
"name": "authentication key-chain key-chain-name",
"desc": "Associate a security key with the specified BFD session using the"
},
{
"name": "authentication l... | 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.
detection-time threshold and transmit-interval threshold options added in Junos OS Release 8.2.
Support for logical systems introduced in Junos OS Release 8.3.
no-adaptation statement introduced in Junos OS Release 9.0.
authentication algorithm, authentication key-chain... | [
"Example: Configuring BFD for IS-IS",
"Understanding BFD Authentication for IS-IS"
] |
bfd-liveness-detection (Protocols LDP) | bfd-liveness-detection {
detection-time threshold milliseconds;
ecmp;
failure-action {
remove-nexthop;
remove-route;
}
holddown-interval seconds;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
minimum-transmit-interval milliseconds;
multiplier d... | [edit logical-systems logical-system-name protocols ldp oam],
[edit logical-systems logical-system-name protocols ldp oam fec address],
[edit protocols ldp oam],
[edit protocols ldp oam fec address] | Enable Bidirectional Forwarding Detection (BFD) for all MPLS LSPs or for just a specific LSP. | [
{
"name": "minimum-interval",
"desc": "Minimum transmit and receive interval."
},
{
"name": "minimum-receive-interval",
"desc": "Minimum receive interval."
},
{
"name": "minimum-transmit-interval",
"desc": "Minimum transmit interval."
},
{
"name": "multiplier",
"desc": "D... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Support for the bfd-liveness-detection statement at the [edit protocols ldp oam fec address] hierarchy level
and the ecmp option added in Junos OS Release 9.0.
Support for the failure-action statement with the remove-nexthop and remove-route options and the holddown-
inter... | [
"Configuring BFD for LDP LSPs"
] |
bfd-liveness-detection (Protocols MPLS) | bfd-liveness-detection {
failure-action {
make-before-break teardown-timeout seconds;
teardown;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier detection-time-multiplier
pdu-size bytes;
} | [edit protocols mpls label-switched-path lsp-name oam],
[edit protocols mpls oam] | Enable Bidirectional Forwarding Detection (BFD) for all of the MPLS LSPs or for just a specific LSP. | [
{
"name": "minimum-interval",
"desc": "Minimum transmit and receive interval."
},
{
"name": "minimum-receive-interval",
"desc": "Minimum receive interval."
},
{
"name": "minimum-transmit-interval",
"desc": "Minimum transmit interval."
},
{
"name": "multiplier",
"desc": "D... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
failure-action option added in Junos OS Release 8.5.
pdu-size option introduced in Junos OS Release 23.2 for MX Series devices. | [
"Configuring BFD for MPLS IPv4 LSPs",
"Configuring Bidirectional Forwarding Detection for MPLS (CLI Procedure)"
] |
bfd-liveness-detection (Protocols OSPF) | bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
full-neighbors-only
holddown-interval holddown-interval;
minimum-interval milliseconds;
minimum-receive... | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface
interface-name],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast) area area-id interface interface-name],
[edit logical-systems logical-system-name routing-instance... | Configure bidirectional failure detection timers and authentication for OSPF.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "authentication algorithm algorithm-name",
"desc": "Configure the algorithm used to authenticate the specified BFD"
},
{
"name": "authentication key-chain key-chain-name",
"desc": "Associate a security key with the specified BFD session using the"
},
{
"name": "authentication l... | 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.
detection-time threshold and transmit-interval threshold options added in Junos OS Release 8.2.
Support for logical systems introduced in Junos OS Release 8.3.
no-adaptation option introduced in Junos OS Release 9.0.
no-adaptation option introduced in Junos OS Release ... | [
"Example: Configuring BFD for OSPF",
"Example: Configuring BFD Authentication for OSPF"
] |
bfd-liveness-detection (Protocols PIM) | bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;... | [edit protocols pim interface (Protocols PIM) interface-name family (inet | inet6)],
[edit routing-instances routing-instance-name protocols pim interface (Protocols PIM) interface-
name family (inet | inet6)] | Configure bidirectional forwarding detection (BFD) timers and authentication for PIM.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
authentication option introduced in Junos OS Release 9.6.
pdu-size option introduced in Junos OS Release 23.2 for MX Series devices. | [
"Configuring BFD for PIM",
"Configuring BFD Authentication for PIM"
] |
bfd-liveness-detection (Protocols RIP) | bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
... | [edit logical-systems logical-system-name protocols rip group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip
group group-name neighbor neighbor-name],
[edit protocols rip group group-name],
[edit routing-instances routing-instance-name protocols rip group g... | Configure bidirectional failure detection timers and authentication.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "authentication algorithm algorithm-name",
"desc": "Configure the algorithm used to authenticate the specified BFD"
},
{
"name": "authentication key-chain key-chain-name",
"desc": "Associate a security key with the specified BFD session using the"
},
{
"name": "authentication l... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0.
Options detection-time threshold and transmit-interval threshold introduced in Junos OS Release 8.2.
Support for logical systems introduced in Junos OS Release 8.3.
Option no-adaptation introduced in Junos OS Release 9.0.
Options authentication algorithm, authentication key... | [
"Example: Configuring BFD for RIP",
"Example: Configuring BFD Authentication for RIP"
] |
bfd-liveness-detection (Routing Options Static Route) | bfd-liveness-detection {
description Site- xxx;
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
echo
minimum-interval milliseconds
echo-lite
minimum-interval millise... | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name static route destination-prefix],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name static route destination-prefix qualified-... | Configure bidirectional failure detection timers and authentication criteria for static routes. | [
{
"name": "authentication algorithm algorithm-name",
"desc": "Configure the algorithm used to authenticate the specified"
},
{
"name": "authentication key-chain key-chain-name",
"desc": "Associate a security key with the specified BFD session using"
},
{
"name": "authentication loose-che... | 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.
detection-time threshold and transmit-interval threshold options introduced in Junos OS Release 8.2.
local-address statement introduced in Junos OS Release 8.2.
minimum-receive-ttl statement introduced in Junos OS Release 8.2.
Support for logical routers introduced in J... | [
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection",
"Example: Configuring BFD Authentication for Securing Static Routes"
] |
bfd-liveness-detection (Source Packet Routing Template) | bfd-liveness-detection {
minimum-interval milliseconds;
multiplier multiplier;
no-router-alert-option;
sbfd;
}
bfd-liveness-detection {
minimum-interval milliseconds;
multiplier multiplier;
no-router-alert-option;
pdu-size bytes;
sbfd {... | [edit protocols source-packet-routing source-routing-path-template] | Configure Bidirectional forwarding detection (BFD) options for PCE-initiated segment routing LSP
template.
NOTE: The BFD configuration is applied at the top level and not individually per
segment list. As a result, each path of the PCE-initiated LSP inherits the same BFD
configuration. | [
{
"name": "minimum-interval",
"desc": "Specify in milliseconds the minimum transmit and receive interval. Range: 1 through 255000 milliseconds"
},
{
"name": "multiplier",
"desc": "Specify the detection time multiplier. Default: 3 Range: 1 through 255"
},
{
"name": "no-router-alert-opt... | routing | Statement introduced in Junos OS Release 19.4R1.
pdu-size option introduced in Junos OS Release 23.2 for MX Series devices. | [
"PCEP Configuration"
] |
bfd-liveness-detection (VRRP) | bfd-liveness-detection {
local-ip-addr local-ip-address;
peer-ip-addr peer-ip-address;
routing-instance routing-instance-name;
liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
inline-disable;
minimum-interval milliseconds;... | [edit dynamic-profiles name interfaces name unit name family inet address name vrrp-group name
track],
[edit dynamic-profiles name interfaces name unit name family inet6 address name vrrp-inet6-group
name track],
[edit dynamic-profiles name interfaces interface-range name unit name family inet address name
vrrp-grou... | Configure Bidirectional Forwarding Detection (BFD) timers and options for VRRP tracking. | [
{
"name": "local-ip-addr",
"desc": "BFD local address."
},
{
"name": "peer-ip-addr",
"desc": "BFD neighbor address."
},
{
"name": "routing-instance",
"desc": "Name of the routing instance, or \"default\"."
},
{
"name": "liveness-detection",
"desc": "Configure bidirectiona... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [
"Configuring VRRP"
] |
bgp (RPM) | bgp {
data-fill data;
data-size size;
destination-port port;
history-size size;
logical-system logical-system-name <routing-instances routing-instance-name>;
moving-average-size size;
probe-count count;
probe-interval seconds;
probe-type type;
routing-instances instance-name;
... | [edit services rpm bgp] | Configure BGP neighbor discovery through Real-Time Performance Monitoring (RPM). | [
{
"name": "bgp",
"desc": "Define properties for configuring BGP neighbor discovery."
}
] | 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 BGP Neighbor Discovery Through RPM"
] |
bgp | bgp { ... } | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | Enable BGP on the routing device or for a routing instance.
Default
BGP is disabled. | [] | 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. | [
"BGP User Guide"
] |
bgp-error-tolerance (Protocols BGP) | bgp-error-tolerance {
(malformed-route-limit number | no-malformed-route-limit);
malformed-update-log-interval seconds;
} | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit protocols bgp],
[edit protocols bgp group group-name],
[edit protocols bgp group group-na... | Enable error handling for BGP update messages.
Starting in Junos OS Release 24.2R1, BGP error handling is enabled by default. You can still configure
sub-options such as, malformed-route-limit, malformed-update-log-interval, and no-malformed-route-limit under
this configuration statement. Note that If you delete the bg... | [
{
"name": "malformed-route-limit",
"desc": ""
},
{
"name": "number",
"desc": "Configure a limit on the number of malformed hidden routes stored in memory. NOTE: When the value of malformed-route-limit is reduced, only new malformed BGP update messages are affected and the existing malformed rout... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Understanding Error Handling for BGP Update Messages",
"Example: Configuring Error Handling for BGP Update Messages"
] |
bgp-identifier | bgp-identifier identifier; | [edit protocols bgp],
[edit protocols bgp group groupname],
[edit protocols bgp group groupname neighbor peer address ] | Configure BGP using BGP identifier. | [] | 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. | [] |
bgp-orf-cisco-mode | bgp-orf-cisco-mode; | [edit logical-systems logical-system-name protocols bgp outbound-route-filter],
[edit logical-systems logical-system-name protocols bgp group group-name outbound-route-filter],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address
outbound-route-filter],
[edit logical-systems logica... | Enable interoperability with routing devices that use the vendor-specific outbound route filter
compatibility code of 130 and code type of 128.
NOTE: To enable interoperability for all BGP peers configured on the routing device,
include the statement at the [edit routing-options outbound-route-filter] hierarchy level.
... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support for the BGP group and neighbor hierarchy levels introduced in Junos OS Release 9.2.
Support for the BGP group and neighbor hierarchy levels introduced in Junos OS Release 9.3 for EX
Series switches. | [
"Example: Configuring BGP Prefix-Based Outbound Route Filtering"
] |
bgp-peer | bgp-peer ip-address; | [edit routing-instances name protocols evpn mclag] | Configure an aggregation device in a Junos Fusion Enterprise or a multichassis link aggregation group
(MC-LAG) topology to interwork with an Ethernet VPN-MPLS (EVPN-MPLS) device. | [
{
"name": "ip-address",
"desc": "IP address of the BGP peer. Typically, a BGP peer is identified by the IP address of the device’s loopback interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"Understanding EVPN-MPLS Interworking with Junos Fusion Enterprise and MC-LAG"
] |
bgp-static | bgp-static {
route destination-prefix/prefix-length {
as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> <aggregator as-
number in-address>;
community [ community-ids ];
(metric | metric2 | metric3 | metric4) value <type type>;
(preference | preference2 | color | ... | [edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-options rib routing-table-name],
[edit routing-options],
[edit routing-options rib routing-table-name] | Specify a BGP-static route. You can specify any number of routes within a single BGP-static statement,
and you can specify any number of BGP-static options in the configuration. | [
{
"name": "route destination-prefix/",
"desc": ""
},
{
"name": "prefix-length",
"desc": "destination-prefix is the network portion of the IP address, and prefix-length is the destination prefix length."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Configuring BGP-Static Routes for Preventing Route Flaps",
"Example: Configuring BGP-Static Routes to Prevent Route Flaps",
"Understanding BGP-Static Routes for Preventing Route Flaps"
] |
bgpmcast | bgpmcast {
traceoptions {
file <file name>;
flag all detail;
}
} | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1 | [
"Controller-Based BGP Multicast Signaling"
] |
bidirectional (Interface) | bidirectional {
df-election {
backoff-period milliseconds;
offer-period milliseconds;
robustness-count number;
}
} | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name],
[edit protocols pim interface (Protocols PIM) interface-name],
[edit routing-inst... | Configure parameters for bidirectional PIM.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding Bidirectional PIM",
"Example: Configuring Bidirectional PIM"
] |
bidirectional (RP) | bidirectional {
address address {
group-ranges {
destination-ip-prefix</prefix-length>;
}
hold-time seconds;
priority number;
}
} | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure the routing device’s rendezvous-point (RP) properties for bidirectional PIM.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding Bidirectional PIM",
"Example: Configuring Bidirectional PIM"
] |
bier | bier {
sub-domain sub-domain-id {
bfr-id bfr-id;
bfr-prefix bfr-prefix;
encapsulation {
mpls;
bitstringlen 256;
number-sets number of sets;
}
... | [edit protocols] | Enable Bit Index Explicit Replication (BIER) on the routing device.
You must include the bier statement in the configuration to enable BIER on the router. | [
{
"name": "sub-domain",
"desc": "Assign a numeric value to the sub-domain. It represents a specific topology within a BIER domain. Range: 0 through 255."
},
{
"name": "bfr-id",
"desc": "A BFR-ID is a number assigned to an ingress or egress BFR. A BFR-ID must be unique within that BIER sub-domai... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos Evolved OS Release 23.4R2-S1. | [] |
bier-sub-domain (Protocols IS-IS) | bier-sub-domain sub-domain-id; | [edit protocols isis] | To include the BIER sub-domain in the IS-IS sub-TLVs, configure bier-sub-domain under protocols isis. Key
BIER information like BFR-IDs and BFER-Prefixes in each sub-domain are flooded through the IS-IS
domain to generate the BIER forwarding table. | [
{
"name": "name",
"desc": "Enable bier subdomain-id"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R2-S1. | [] |
bits (Chassis Synchronization) | bits {
source-mode (chassis | ptp-clock);
squelch {
method (ais | ql-dnu | rai | shut);
}
ssm option-2 (GEN-1 | GEN-2);
} | [edit chassis synchronization interfaces]
[edit chassis synchronization output interfaces] | Configure the parameters of the building-integrated timing supply (BITS) interface.
NOTE: bits is not supported on the ACX1000 router. | [
{
"name": "ssm option-2 (GEN-1 |",
"desc": ""
},
{
"name": "GEN-2)",
"desc": "(ACX710 only) Specify the type of synchronization status message (SSM). Choose message type Generation 1 or Generation 2."
}
] | 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.
source-mode, squelch, and ssm options introduced in Junos OS Release 20.2R1. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview"
] |
black-list | black-list {
IP-address-list IP-address-list-name;
file-name file-name;
} | [edit services web-filter profile profile-name security-intelligence-policy] | Configure a global blocklist of IP addresses to block packets to the destined countries. | [
{
"name": "IP-address-list ip-address-list-name",
"desc": "Contains the list of IP addresses that must be blocked. ip-address-list-name is the name of the IP address-list specified at the [edit services web-filter]"
},
{
"name": "file-name file-name",
"desc": "Name of the file which contains the... | 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 (Juniper ATP Cloud) . | [
"URL Filtering"
] |
blackhole-action | blackhole-action (log-only | restart | offline | restart-then-offline); | [edit chassis fpc slot-number fabric] | Configure an FPC to take a specific action when fabric plane degradation reaches 100 percent. | [] | 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. | [
"Managing Bandwidth Degradation"
] |
block (Spanning Trees) | block; | [edit protocols mstp interface (all | interface-name) bpdu-timeout-action],
[edit protocols rstp interface (all | interface-name) bpdu-timeout-action],
[edit protocols stp interface (all | interface-name) bpdu-timeout-action],
[edit protocols vstp vlan vlan-id interface (all | interface-name) bpdu-timeout-action] | Configures loop protection on a specific interface. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support. | [
"Understanding Loop Protection for STP, RSTP, VSTP, and MSTP",
"Understanding VSTP",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Configuring Faster Convergence and Improving Network Stability with RSTP",
"Example: Faster Convergence and Improved Network Stability with R... |
block | block block-name {
address;
global-micro-sid{
maximum-sids maximum-sids;
maximum-static-sids maximum-static-sids
}
local-micro-sid{
maximum-static-sids maximum-static-sids
}
} | [edit logical-systems name routing-instances name routing-options source-packet-routing srv6],
[edit logical-systems name routing-options source-packet-routing srv6],
[edit logical-systems name tenants name routing-instances name routing-options source-packet-
routing srv6],
[edit routing-instances name routing-options... | Specify an SRv6 prefix that defines a micro SID block. Configure micro SID block parameters such as
global and local micro SIDs. In segment routing domain, a global micro SID. identifies a shortest-path to
a node. A local micro SID identifies a cross connect to a direct neighbor over a specific interface.
name
Specify ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.2R1 and Junos OS 23.4R1. | [
"No Link Title"
] |
block-allocation (Source NAT Next Gen Services) | block-allocation {
active-block-timeout timeout-interval;
block-size block-size;
interim-logging-interval timeout-interval;
maximum-blocks-per-host maximum-block-number
log disable | enable
} | [edit services nat source pool nat-pool-name port] | Allocate a block of ports for each subscriber to use for source NAT with port translation, except for
deterministic NAT. New requests for NAT ports for the subscriber are served from the active block.
With port block allocation, we generate one syslog log per set of ports allocated for a subscriber. This
reduces the nu... | [
{
"name": "active-block-timeout timeout-",
"desc": ""
},
{
"name": "interval",
"desc": "The interval, in seconds, for which the block is active. After the timeout, a new block is allocated, even if ports are available in the active block. If you set the timeout to 0, port blocks are filled compl... | 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. | [] |
block-command | block-command protocol-command-list; | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name] | Apply protocol block command custom-objects to the content-filtering profile. | [] | 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. | [] |
block-content-type | block-content-type (activex | exe | http-cookie | java-applet | zip); | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name] | Apply blocks to other available content such as exe, http-cookie, java-applet. This is for HTTP only. | [
{
"name": "activex",
"desc": "Block ActiveX."
},
{
"name": "exe",
"desc": "Block EXE files."
},
{
"name": "http-cookie",
"desc": "Block cookies."
},
{
"name": "java-applet",
"desc": "Block Java applets."
},
{
"name": "zip",
"desc": "Block ZIP files."
}
] | 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. | [] |
block-extension | block-extension extension-list; | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name] | Apply block extensions to the content-filtering profile. | [] | 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. | [] |
block-frag (IDS Screen Next Gen Services) | block-frag; | [edit services screen ids-option screen-name ip] | Identify and drop fragmented IP packets. IP fragments might contain an attacker's attempt to exploit the
vulnerabilities in the packet reassembly code of specific IP stack implementations. When the target
receives these packets, the results can range from processing the 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"
] |
block-message (Application Firewall) | block-message type {
custom-text content custom-html-text;
custom-redirect-url content custom-redirect-url;
} | [edit security application-firewall profile profile-name] | Defines the profile of the notification to be sent to clients when HTTP or HTTPS traffic is blocked by a
reject or deny action from an application firewall.
NOTE: The block message option is not supported for non-HTTP traffic such as FTP,
SSH, Telnet, and so on. In these instances, if the action is drop or reject, the ... | [
{
"name": "type",
"desc": "(Optional) The message type to be displayed after a reject or deny action."
},
{
"name": "custom-text",
"desc": "Text message in HTML to be added to the default text. If custom-text is specified, the"
},
{
"name": "custom-redirect-url",
"desc": "URL redirec... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [
"Example: Configuring AppQoS"
] |
block-message (Security Content Security) | block-message {
type {
custom-redirect-url;
}
url url;
} | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name] | Configure Juniper enhanced block message settings. | [
{
"name": "type",
"desc": "Specify the following type of the block message:"
},
{
"name": "custom-redirect-url",
"desc": "Specify Custom redirect URL server."
},
{
"name": "url url",
"desc": "Specify an URL of the block message."
}
] | 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. | [] |
block-mime | block-mime {
exception list-name;
list list-name;
} | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name] | Apply MIME pattern list custom-objects to the content-filtering profile for blocking MIME types. | [] | 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. | [] |
blocklists (Security IKE) | blocklists {
blocklist-name {
description text-description;
rule rule-name {
match {
role (initiator | responder);
id-type (inet | inet6 | hostname | distinguished-name | user-at-hostname |
key-id);
id-pattern v... | [edit security ike] | Defines the remote peer IKE identity blocklist(s) configuration.
In the configuration hierarchy, you can configure different blocklists for blocking IKE IDs during IKE SA
negotiation authentication phase. Once you configure the blockslists, you can use a blocklist in the
corresponding IKE policy at the [edit security i... | [
{
"name": "blocklists blocklist-name",
"desc": "Specify the blocklist name. Value: Up to 32 characters Max allowed: Up to 1000 blocklists"
},
{
"name": "rule rule-name",
"desc": "Specify the rule name. Value: Up to 32 characters Max allowed: Up to 1000 rules per blocklist"
},
{
"name... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | blocklists statement introduced in Junos OS Release 23.4R1. | [
"IKE Protection from DDoS Attacks"
] |
bmp | bmp {
authentication-algorithm algorithm;
authentication-key key;
authentication-key-chain authentication-key-chain;
connection-mode (active | passive);
hold-down {
seconds;
flaps flaps;
period seconds;
}
initiation-message text;
local-address address;
local-p... | [edit routing-options],
[edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit proto... | 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": "authentication-algorithm",
"desc": ""
},
{
"name": "algorithm",
"desc": "Configure an authentication algorithm. Values: Specify one of the following types of authentication algorithms:"
},
{
"name": "aes-128-cmac-96",
"desc": "Cipher-based message authentication code (AES... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Statement introduced for BMP in Junos OS Release 13.2X51-D15 for the QFX Series.
Support for BMP version 3 introduced in Junos OS Release 13.3.
initiation-message, local-address, local-port, monitor, priority, route-monitoring, station, station-address, station-
port, and s... | [
"Example: Configuring the BGP Monitoring Protocol",
"Example: Configuring Router Authentication for BGP",
"Configuring BGP Monitoring Protocol Version 3",
"Management Interface in a Non-Default Instance",
"Configuring BGP Monitoring Protocol to Run Over a Different Routing Instance"
] |
boot-loader-authentication | boot-loader-authentication {
(encrypted-password password | plain-text-password);
} | [edit system] | Set the boot-loader password for accessing the U-Boot CLI during the boot process. The password can
be entered either as a plain-text password or as an encrypted password.
Encrypted passwords must be entered in Message Digest 5 (MD5) format. Plain-text passwords are
encrypted by using MD5 by default. The encryption fo... | [
{
"name": "encrypted-password password",
"desc": "Enter a password that has already been encrypted. You can specify only one"
},
{
"name": "plain-text-password",
"desc": "Enter a plain-text password. The CLI prompts you for the password and then"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D20. | [
"Using Unattended Mode for U-Boot to Prevent Unauthorized Access"
] |
boot-server (DHCP) | boot-server (address | hostname); | [edit system services dhcp],
[edit system services dhcp pool],
[edit system services dhcp static-binding] | Configure the name of the boot server advertised to DHCP clients. The client uses a boot file located on
the boot server to complete DHCP setup. | [
{
"name": "address",
"desc": "IP address of a DHCP boot server."
},
{
"name": "hostname",
"desc": "Hostname of a DHCP boot server."
}
] | 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. | [
"boot-file"
] |
bootp (System Processes) | bootp {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify the booting process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the booting process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds,"
},
{
"name"... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
bootp | bootp {
client-response-ttl number;
description text-description;
interface (interface-name | interface-group) {
client-response-ttl number;
description text-description;
maximum-hop-count number;
minimum-wait-time seconds;
no-listen;
server address {
... | [edit forwarding-options helpers] | Configures a router, switch, or interface to act as a Dynamic Host Configuration Protocol (DHCP) or
bootstrap protocol (BOOTP) relay agent. For MX Series (MX80, MX240, MX480 and MX960) routers
connected via IRB, see Configuring Routers, Switches, and Interfaces as DHCP and
BOOTP Relay Agents for information on how to p... | [] | 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 Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents"
] |
bootstrap | bootstrap {
family (inet | inet6) {
export [ policy-names ];
import [ policy-names ];
priority number;
}
} | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure parameters to control bootstrap routers and messages.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring PIM Bootstrap Properties for IPv4",
"Configuring PIM Bootstrap Properties for IPv4 or IPv6"
] |
bootstrap-export | bootstrap-export [ policy-names ]; | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Apply one or more export policies to control outgoing PIM bootstrap messages. | [
{
"name": "policy-names",
"desc": "Name of one or more import policies."
}
] | 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 PIM Bootstrap Properties for IPv4",
"Configuring PIM Bootstrap Properties for IPv4 or IPv6"
] |
bootstrap-import | bootstrap-import [ policy-names ]; | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Apply one or more import policies to control incoming PIM bootstrap messages. | [
{
"name": "policy-names",
"desc": "Name of one or more import policies."
}
] | 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 PIM Bootstrap Properties for IPv4",
"Configuring PIM Bootstrap Properties for IPv4 or IPv6"
] |
bootstrap-priority | bootstrap-priority number; | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure whether this routing device is eligible to be a bootstrap router. In the case of a tie, the routing
device with the highest IP address is elected to be the bootstrap router. | [
{
"name": "number",
"desc": "Priority for becoming the bootstrap router. A value of 0 means that the routing device is not"
}
] | 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 PIM Bootstrap Properties for IPv4"
] |
bounded-delay | bounded-delay; | [edit security macsec connectivity-association connectivity-association-name mka (MX Series)] | Configure bounded delay to ensure that a Media Access Control Security (MACsec) frame will not be
delivered after a delay of two seconds or more. This ensures that a delay of MACsec frames resulting
from a man-in-the-middle attack will not go undetected.
When you configure bounded delay, you must also configure replay ... | [] | security | Statement introduced in Junos OS Release 21.1R1. | [] |
bpdu-block | bpdu-block {
interface (interface-name disable | all);
disable-timeout seconds;
} | [edit protocols layer2-control ]
[edit ethernet-switching-options] | Configures bridge protocol data unit (BPDU) protection on a specified interface or on all interfaces. If
the interface receives incompatible BPDUs, it is disabled.
If the disable-timeout statement is included in the BPDU configuration, the interface is automatically
reenabled after the timer expires. Otherwise, you mus... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Understanding BPDU Protection for Spanning-Tree Instance Interfaces",
"Configuring BPDU Protection for Individual Spanning-Tree Instance Interfaces",
"Understanding BPDU Protection for STP, RSTP, and MSTP",
"Example: Configuring BPDU Protection on Interfaces to Prevent STP Miscalculations on EX Series",
"S... |
bpdu-block-on-edge | bpdu-block-on-edge; | [edit logical-systems logical-system-name protocols (mstp | rstp | vstp)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp | vstp)],
[edit protocols ( mstp | rstp| vstp )],
[edit routing-instances routing-instance-name protocols (mstp | rstp | vstp)] | Configure bridge protocol data unit (BPDU) protection on all edge ports of a switch. When the bpdu-
block-on-edge statement is configured and the interface encounters an incompatible BPDU, the interface
shuts down.
If the disable-timeout statement is included in the BPDU configuration, the interface is automatically
r... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support. Statement
updated in Junos OS Release 11.1 for EX Series switches to change blocking behavior to port shutdown.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding BPDU Protection for Spanning-Tree Instance Interfaces",
"Understanding BPDU Protection for STP, RSTP, and MSTP",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Faster Convergence and Improved Network Stability with RSTP on EX Series Switches"
] |
bpdu-destination-mac-address (Spanning Tree) | bpdu-destination-mac-address provider-bridge-group; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit protocols (mstp | rstp)],
[edit routing-instances routing-instance-name protocols (mstp | rstp)] | Enable MX Series router to participate in the provider Rapid Spanning Tree Protocol (RSTP) instance or a
provider Multiple Spanning Tree Protocol (MSTP) instance.
Default
If the bpdu-destination-mac-address statement is not configured, the bridge participates in the customer
RSTP instance, transmitting and receiving st... | [
{
"name": "provider-bridge-group",
"desc": "The destination MAC address of the BPDU packets transmitted is the provider"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding BPDUs Used for Exchanging Information Among Bridges",
"Understanding Provider Bridge Participation in RSTP or MSTP Instances",
"Configuring Rapid Spanning Tree Protocol",
"Configuring Multiple Spanning Tree Protocol"
] |
bpdu-destination-mac-address | bpdu-destination-mac-address provider-bridge-group; | [edit protocols mvrp],
[edit routing-instances routing-instance-name protocols mvrp] | For Multiple VLAN Registration Protocol (MVRP) configurations, specifies the multicast address for
MVRP. If configured, the provider MVRP multicast MAC address is used; otherwise, the Junos OS uses
the customer MVRP multicast MAC address.
Default
By default, the provider MVRP multicast MAC address is used (if configure... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Example: Configuring Automatic VLAN Administration Using MVRP on MX Series Routers",
"Configuring Multiple VLAN Registration Protocol (MVRP) to Manage Dynamic VLAN Registration",
"Configuring Multiple VLAN Registration Protocol (MVRP) to Manage Dynamic VLAN Registration on",
"Security Devices",
"Verifying ... |
bridge-domain (Analyzer) | bridge-domain bridge-domain-name; | [edit forwarding-options analyzer analyzer-name input egress],
[edit forwarding-options analyzer analyzer-name input egress routing-instance instance-name],
[edit forwarding-options analyzer analyzer-name input ingress],
[edit forwarding-options analyzer analyzer-name input ingress routing-instance instance-name],
[edi... | Configure the bridge domain to monitor outgoing traffic. | [
{
"name": "bridge-domain-name",
"desc": "Name of the bridge domain that monitors outgoing traffic."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Example: Configuring Port Mirroring for Remote Monitoring of Employee Resource Use",
"Example: Configuring Mirroring to Multiple Interfaces for Remote Monitoring of Employee Resource",
"Use on EX9200 Switches"
] |
bridge-domain | bridge-domain name;
vlan-id [ vlan-identifiers ];
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain maintenance-domain-
name],
[edit protocols oam ethernet connectivity-fault-management maintenance-domain maintenance-domain-
name virtual-switch virtual-switch-name] | (MX Series routers only) Specify the OAM Ethernet CFM maintenance domain bridge domain. | [
{
"name": "name",
"desc": "Specify the name of the bridge domain."
},
{
"name": "vlan-identifiers",
"desc": "Specify one or more VLAN identifiers."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring Maintenance Intermediate Points (MIPs)"
] |
bridge-domains | bridge-domains {
bridge-domain-name {
bridge-options {
...bridge-options-configuration...
}
domain-type bridge;
interface interface-name;
no-irb-layer-2-copy;
no-local-switching;
routing-interface routing-interface-name;
vlan-id (all | non... | [edit],
[edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | (MX Series routers only) Configure a domain that includes a set of logical ports that share the same
flooding or broadcast characteristics in order to perform Layer 2 bridging. | [
{
"name": "bridge-domain-name",
"desc": "Name of the bridge domain."
}
] | 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 the no-irb-layer-2-copy statement added in Junos OS Release 10.2. | [
"Configuring a Bridge Domain",
"Configuring a Layer 2 Virtual Switch"
] |
bridge-options | bridge-options {
interface interface-name;
static-mac static-mac-address;
}
global-mac-ip-limit limit;
interface-mac-ip-limit limit;
interface-mac-limit limit;
packet-action drop;
}
mac-pinning
mac-statistics;
mac-ip-table-size limit;
mac-table-size limit;
m... | [edit bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name] | (MX Series routers only) Configure Layer 2 learning and forwarding properties for a bridge domain or a
virtual switch.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for logical systems added in Junos OS Release 9.6.
Statment (mac-pinning) introduced in Junos OS Release 16.2.
global-mac-ip limit, interface-mac-ip-limit, and mac-ip-table-size statements introduced in Junos OS Release
17.4R1. | [
"Understanding Layer 2 Learning and Forwarding for Bridge Domains"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.