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 |
|---|---|---|---|---|---|---|---|
monitor start | monitor start filename | CAUTION: Running monitoring can adversely impact scale and performance and may
increase security risk. We strongly recommend using these commands only under the
guidance of a JTAC support engineer. After collecting the debug information,
immediately stop monitoring to minimize risk and restore normal system performance... | [
{
"name": "filename",
"desc": "Specific log or trace file. Additional Information Log files are generated by the routing protocol process or by system logging. The log files generated by system logging are configured with the syslog statement at the [edit system] hierarchy level and the options statement at... | trace
Output Fields
Table 96 on page 11375 describes the output fields for the monitor start command. Output fields are
listed in the approximate order in which they appear.
Table 96: monitor start Output Fields
Field Name
Field Description
***filename ***
Name of the file from which entries are being displayed. This ... | Command introduced before Junos OS Release 7.4. | [
"monitor list"
] | |
monitor stop (JDM) | monitor stop file-name | Stop displaying the system log or trace file.
Additional Information
Log files are generated by the routing protocol process or by system logging. | [] | View
Output Fields
This command produces no output. | Command introduced in Junos OS Release 17.4R1. | [] | |
monitor stop | monitor stop filename | Stop displaying the system log or trace file. | [
{
"name": "filename",
"desc": "Specific log or trace file. Additional Information Log files are generated by the routing protocol process or by system logging. The log files generated by system logging are those configured with the syslog statement at the [edit system] hierarchy level and the options statem... | trace
Output Fields
This command produces no output.
Sample Output
monitor stop
user@host> monitor stop | Command introduced before Junos OS Release 7.4. | [
"monitor list"
] | |
monitor traffic | monitor traffic
<brief | detail | extensive>
<absolute-sequence>
<count count>
<interface interface-name>
<layer2-headers>
<matching matching>
<no-domain-names>
<no-promiscuous>
<no-resolve>
<no-timestamp>
<print-ascii>
<print-hex>
<read-file filename>
<resolve-timeout>
<size size>
<write-file filename> | /
Division operator.
&
Bitwise AND.
*
Bitwise exclusive OR.
|
Bitwise inclusive OR.
Relational Operator (Highest to Lowest Precedence)
<=
If the first expression is less than or equal to the second, the packet matches.
>=
If the first expression is greater than or equal to the second, the packet
matches.
<
If the first... | [
{
"name": "none",
"desc": "(Optional) Display packet headers transmitted through fxp0. On a TX Matrix Plus router, display packet headers transmitted through em0."
},
{
"name": "brief | detail | extensive",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "absolut... | trace
maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
monitor traffic count
user@host> monitor traffic count 2
listening on fxp0
04:35:49.814125 In my-server.home.net.1295 > my-server.work.net.telnet: . ack
4122529478 win 16798 (DF)
04:35:4... | Command introduced before Junos OS Release 7.4.
Options read-file and write-file introduced in Junos OS Release 19.1R1. | [] | |
monitor-bandwidth | monitor-bandwidth; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name auto-
bandwidth],
[edit protocols mpls label-switched-path lsp-name auto-bandwidth] | Do not automatically adjust bandwidth allocation. However, the maximum average bandwidth utilization
is monitored on the LSP, and the information is recorded in the MPLS statistics file. | [] | 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 Passive Bandwidth Utilization Monitoring"
] |
monitor-end-point | (monitor-end-point | no-monitor-end-point); | [edit interfaces interface-name otn-options odu-delay-management] | Originate or do not originate the connection monitor end point.
Default
By default, do not originate the connection monitor end point. | [
{
"name": "monitor-end-point",
"desc": "Originate the connection monitor end point."
},
{
"name": "no-monitor-end-point",
"desc": "Do not originate the connection monitor end point."
}
] | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
monitor-object | monitor-object name {
bfd-liveliness {
destination-ip name {
interface interface;
routing-instance routing-instance;
session-type(multihop | singlehop);
src-ip src-ip;
weight weight;
}
threshold threshold;
}
interface {
interface-name name {
weight wei... | [edit chassis high-availability services-redundancy-group name monitor] | SRG monitoring object | [
{
"name": "name",
"desc": "SRG monitoring object name. Range - 1 through 32."
},
{
"name": "bfd-liveliness",
"desc": "Configure BFD monitoring for the specific monitoring object."
},
{
"name": "interface",
"desc": "Interface to monitor for the specific monitoring object."
},
{
... | 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. | [
"Multinode High Availability Monitoring Options",
"Multinode High Availability"
] |
monitor-profile | monitor-profile monitor-profile-name {
lower-threshold lower-threshold;
notification-type(alarm | none | syslog);
upper-threshold upper-threshold;
} | [edit system packet-forwarding-options hw-resource-monitor] | Map a monitor profile to a configured resource list (optional) to monitor hardware resource utilization
and set thresholds to trigger notifications as well as the type of notification you would like to receive
when a resource breach occurs. Monitoring resource utilization for a hardware resource as it nears or
crosses ... | [
{
"name": "monitor-profile-name",
"desc": "The hardware resource monitor profile name."
},
{
"name": "lower-threshold",
"desc": "The lower threshold, by percent. A lower threshold breach raises a minor"
},
{
"name": "notification",
"desc": "Range: 1 through 100 percent Default: 50 p... | Edit | Statement introduced in Junos OS Release 24.2R1. | [
"No Link Title"
] |
monitor-session | monitor-session (interface-name | all); | [edit protocols ppp] | Monitor PPP packet exchanges. When monitoring is enabled, packets exchanged during a session are
logged to the default log of /var/log/pppd.
Default
If you do not include this statement, no PPPD-specific monitoring operations are performed. | [
{
"name": "all",
"desc": "Monitor PPP packet exchanges on all sessions."
},
{
"name": "interface-name",
"desc": "Logical interface name on which to enable session monitoring."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configuring PPP"
] |
monitor-timer | monitor-timer {
time seconds;
} | [edit services pfe traffic] | Configure timer for Packet Forwarding engine traffic to uninstall the filter and to increase the default
timer expiry from 300 seconds. This setting configures a maximum number of 3600 seconds and delete
the trace log entries upon timer expiry. | [
{
"name": "time",
"desc": "Default is 5 mins, max configurable time is 60 mins (seconds). Default: 300 seconds Range: 300 through 3600 seconds"
}
] | interface—To view this statement in the configuration.
interface-control—To view this statement in the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
monitoring (Forwarding Options) | monitoring name {
family inet {
output {
cflowd hostname port-number;
export-format cflowd-version-5;
flow-active-timeout seconds;
flow-export-destination {
(cflowd-collector | collector-pic);
}
flow-inactive-timeout sec... | [edit forwarding-options] | Specify the flow monitoring instance name and properties.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Flow Monitoring"
] |
monitoring (Services) | monitoring {
rfc2544 {
test-profile profile-name {
bandwidth bandwidth;
packet-size size;
step-percent percent;
test-type (throughput | latency | frame-loss | back-back-frames);
}
tests{
test-name test-name {
destination-ipv4-address address;
... | [edit services] | Configure monitoring services.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 20.1R1.
twamp statement introduced in Junos OS Evolved Release 20.3R1.
rfc2544 statement introduced in Junos OS Evolved Release 21.1R1.
traps option for RPM introduced in Junos OS Evolved Release 21.2R1.
traps option for TWAMP added in Junos OS Evolved Release 21.3R1.
T... | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
monitoring | monitoring group-name {
family inet {
output {
cflowd hostname {
port port-number;
}
export-format cflowd-version-5;
flow-active-timeout seconds;
flow-export-destination {
(cflowd-collector | collector-pic);
... | [edit forwarding-options] | Specify flow monitoring instance name and properties.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Passive Flow Monitoring"
] |
monitoring-key (PCC Action Profile) | monitoring-key key_string | [edit unified-edge pcef pcc-action-profiles profile-name] | Specify the monitoring key that controls TDF subscriber usage monitoring for traffic that matches the
data flows or applications identified in the predefined PCC rules containing the PCC action profile. The
monitoring key is defined by the PCRF. | [
{
"name": "key_string",
"desc": "Identifier for the monitoring key."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring TDF Subscriber Usage Monitoring for Traffic That Matches Predefined PCC Rules",
"Understanding Usage Monitoring for TDF Subscribers"
] |
monitoring-profile | monitoring-profile profile-name {
export-filters filter-name {
peak-queue-length {
percent percent;
}
queue [queue(s)];
}
} | [edit class-of-service],
[edit dynamic-profiles name class-of-service] | Define a queue-length monitor to measure peak queue occupancy of a virtual output queue (VOQ).
In a typical deployment scenario that uses strict-priority scheduling, a HIGH priority queue can starve LOW
priority queues. Thus the packets in such LOW priority queues can remain longer than desired. Use this
VOQ queue-leng... | [
{
"name": "monitoring-profile",
"desc": "(Required) Name of the monitoring profile. Use the monitoring profile name to attach the monitoring profile to one or more interfaces. Each monitoring profile contains one or more export filters."
},
{
"name": "export-filters",
"desc": "(Required) Name of... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 22.2R1. | [
"VOQ Queue-depth Monitoring"
] |
most-fill | [] | [] | |||||
moving-average-size | moving-average-size number; | [edit services monitoring rpm owner name test name] | Enable statistical calculation operations to be performed across a configurable number of the most
recent samples. | [
{
"name": "number",
"desc": "Number of samples to be used in calculations."
}
] | 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.
Statement at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in Junos OS Release 15.1 for MX Series routers.
Statement introduced in Junos OS Evolved Release 20.1R1. | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
mpls (forwarding-options) | mpls port-number | [edit security forwarding-options tunnel udp payload-port-profile profile-name] | Enable the forwarding of MPLS traffic.
Default
If port number is not configured for MPLS, the default value of the port number is 6635. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos Evolved Release 21.4R1 for the PTX Series routers. | [
"MPLS Overview"
] |
mpls (packet-forwarding-options) | mpls {
lsp-ingress-stats-enable;
lsp-transit-stats-enable;
} | [edit system packet-forwarding-options] | Enable or disable MPLS LSP statistics at PFE level. When you enable or disable MPLS LSP statistics at
PFE level, the PFE automatically restarts.
Default
By default, LSP statistics are disabled. | [
{
"name": "lsp-ingress-stats-enable",
"desc": "Enable ingress LSP statistics."
},
{
"name": "lsp-transit-stats-enable",
"desc": "Enable transit LSP statistics."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Options lsp-ingress-stats-enable and lsp-transit-stats-enable are introduced in Junos OS Evolved Release
22.4R1 for ACX7100-32C, ACX7100-48L, ACX7024, and ACX7509 routers. | [] |
mpls (Protocols) | mpls { ... } | [edit logical-systems logical-system-name protocols],
[edit protocols] | Enable MPLS on the router. | [] | 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 MPLS"
] |
mpls (Security Forwarding Options) | mpls {
mode packet-based;
} | [edit security forwarding-options family] | Enable the forwarding of MPLS traffic. By default, the device drops MPLS traffic.
CAUTION: Because MPLS operates in packet mode, security services are not available.
NOTE: Packet-based processing is not supported on the following SRX Series Firewalls:
SRX1500, SRX5600, and SRX5800. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"MPLS Overview"
] |
mpls (security) | mpls {
mode(drop | packet-based);
} | [edit security forwarding-options family] | The mpls has two modes, drop and packet mode. The default mode for mpls is drop.
Family MPLS | [
{
"name": "mode",
"desc": "Forwarding mode"
},
{
"name": "drop",
"desc": "Disable forwarding"
},
{
"name": "packet-based",
"desc": "Enable packet-based forwarding"
}
] | [none specified] | Statement supported in Junos 24.2R1 for SRX Series Firewalls | [] |
mpls | mpls {
disable;
class-of-service cos-value;
no-cspf;
no-decrement-ttl;
advertisement-hold-time seconds;
explicit-null;
icmp-tunneling;
interface (interface-name | all) {
disable;
}
ipv6-tunneling;
no-propagate-ttl;
path path-name {
(address | hostname) <l... | [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 9.5. | [
"Example: Configuring MPLS on EX8200 and EX4500 Switches",
"Configuring CoS on an MPLS Provider Edge Switch Using IP Over MPLS",
"Configuring CoS on an MPLS Provider Edge Switch Using Circuit Cross-Connect",
"Configuring MPLS on EX8200 and EX4500 Provider Switches",
"Junos OS MPLS Applications Configuration... |
mpls-ecn-map | mpls-ecn-map {
ecn-capable-exp ecn-capable-exp-value {
congestion-experienced-exp-value congestion-experienced-exp-value;
}
} | [edit class-of-service],
[edit dynamic-profiles name class-of-service] | Map MPLS ECN capable and congestion experienced EXP code points. For example, set class-of-service
mpls-ecn-map ecn-capable-exp 6 congestion-experienced-exp 7 specifies if a packet with EXP 6 (110) is received
on an LSR and if it experiences congestion, then the outgoing EXP will be 7 (111). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
mpls-flow-table-size | mpls-flow-table-size units; | [edit chassis fpc slot-number inline-services flow-table-size] | Configure the size of the MPLS flow table in units of 256,000 entries.
NOTE: Starting with Junos OS Release 17.3R1, the maximum number of 256K flow
entries that you can configure for IPv4 flow tables and IPv6 flow tables is 256 on
MPC5Es and MPC6Es with with 4 GB DDR3 memory or higher. The maximum number
of 256K flow ... | [
{
"name": "units",
"desc": "Number of 256,000 flow entries available for the MPLS flow table. Range: 1 through 245 Default: 15 (3,840,000)"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] |
mpls-inet6 | mpls-inet6; | [edit routing-instances name protocols evpn encapsulation] | Enables the use of the EVPN-VXLAN and point-to-point (P2P) services over an MPLS-based IPv6
underlay on the PE routers using Segment Routing with Multiprotocol Label Switching (SR-MPLS). The
services also operate on the segment routing–traffic engineering (SR-TE) addresses that are responsible
for the path calculation ... | [] | routing | Statement introduced in Junos OS Release 21.2. | [] |
mpls-internet-multicast | mpls-internet-multicast; | [edit routing-instances routing-instance-name instance-type]
[edit protocols pim] | A nonforwarding routing instance type that supports Internet multicast over an MPLS network for the
default master instance. No interfaces can be configured for it. Only one mpls-internet-multicast instance
can be configured for each logical system.
The mpls-internet-multicast configuration statement is also explicitly... | [] | 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: Configuring Ingress Replication for IP Multicast Using MBGP MVPNs"
] |
mpls-ipv4-template | mpls-ipv4-template {
label-position [ positions ];
} | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Specify the flow aggregation version 9 or IPFIX properties for templates that combine IPv4 and MPLS
records. The remaining statement is explained separately.
Starting in Junos OS Release 18.4R1, use mpls-template instead of mpls-ipv4-template for inline flow
monitoring of MPLS-IPv4 flows on the MX Series. You must also... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level introduced
in Junos OS Release 16.1. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers",
"Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers"
] |
mpls-ipvx-template | mpls-ipvx-template; | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | In Junos OS Release 18.1, specify the version 9 or IPFIX template for inline monitoring an MPLS-over-
UDP flow that is encapsulated in an RSVP-TE LSP on PTX Series routers. This monitoring looks past the
tunnel header to report the inner payload of the packets. To use the template for MPLS-over-UDP
flows, you must also... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers"
] |
mpls-template | mpls-template {
label-position [positions ];
} | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Specify the flow aggregation IPFIX or version 9 properties for templates used only for MPLS records.
Starting in Junos OS Release 18.2R1, you can also use mpls-template to specify the version 9 or IPFIX
template for inline monitoring an MPLS-over-UDP flow that is encapsulated in an RSVP-TE LSP on PTX
Series routers. (I... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level introduced
in Junos OS Release 16.1.
Statement introduced in Junos OS Release 18.2R1 on PTX Series routers. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates"
] |
mpls-tp-mode | mpls-tp-mode;
lsping-channel-type; | [edit protocols mpls label-switched-path lsp-name oam],
[edit protocols mpls oam] | Enable GAL or G-Ach OAM operation without IP encapsulation on a label-switched path (LSP).
Include this statement at the [edit protocols mpls oam] hierarchy level to enable GAL or G-Ach OAM
operation without IP encapsulation on all LSPs in the MPLS network. Include this statement at the [edit
protocols mpls label-switc... | [] | 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.
lsping-channel-type statement introduced in Junos OS Release 16.1. | [
"Example: Configuring the MPLS Transport Profile for OAM"
] |
mrru | mrru bytes; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options],
[edit interfaces (ml-fpc/pic/port| ls-fpc/pic/port) unit logical-unit-number],
[edit logical-systems logical-system-name interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-
options],
[edit logical-systems logical-system-name interfaces (ml-fpc/p... | For multilink or link services interfaces only, set the maximum received reconstructed unit (MRRU). The
MRRU is similar to the maximum transmission unit (MTU), but is specific to multilink interfaces. | [
{
"name": "bytes",
"desc": "MRRU size."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring MRRU on Multilink and Link Services Logical Interfaces"
] |
mru (Congestion Notification Profiles) | mru mru-value; | [edit class-of-service congestion-notification-profile profile-name input dscp code-point code-point-
bits pfc],
[edit class-of-service congestion-notification-profile profile-name input ieee-802.1 code-point
code-point-bits pfc] | Configure the maximum receive unit (MRU) of the interface in bytes. The system uses the MRU and the
cable length to calculate the amount of buffer headroom reserved to support priority-based flow control
(PFC). The lower the MRU and the shorter the cable length, the less headroom buffer space is required
for PFC.
NOTE... | [
{
"name": "mru-value",
"desc": "Value of the maximum packet receive unit size in bytes (generally from 1500 to 9216 bytes,"
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support added in dscp statement hierarchy in Junos OS Release 17.4R1 for the QFX Series. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit",
"Switch Interfaces",
"Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch",
"Interface",
"Example: Configuring ... |
mru (Dynamic and Static PPPoE) | mru size; | [edit access group-profile group-profile-name ppp ppp-options],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit ppp-options],
[edit interfaces pp0 unit unit-number ppp-options... | Specify the size of maximum receive unit (MRU) that the router uses during link control protocol (LCP)
negotiation for dynamic and static PPP subscribers and L2TP tunneled subscribers. | [
{
"name": "size",
"desc": "MRU size in bytes that is used during LCP negotiation. Range: 64–65,535"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Configuring MTU and MRU for PPP Subscribers",
"Understanding MTU and MRU Configuration for PPP Subscribers"
] |
mru (Gigabit Ethernet Options) | mru mru; | [edit dynamic-profiles name interfaces name gigether-options],
[edit dynamic-profiles name logical-systems name interfaces name gigether-options],
[edit interfaces name gigether-options]
Hierarchy Level: SRX Series
[edit interfaces name gigether-options] | Configure the maximum receive unit (MRU) of the interface in bytes. The maximum receive unit of an
interface indicates the largest size of a packet that the interface can accept. You can configure the
parameters so that the value of MRU equals the value of MTU. You can also configure different values
for MRU and MTU. W... | [
{
"name": "mru",
"desc": "MRU size in bytes. Range: 256 through 16008 bytes. Range (SRX Series) : 256 through 9200 bytes."
}
] | interface | Statement introduced in Junos OS Release 19.1R1. | [
"Ethernet Interfaces Overview"
] |
msdp | msdp {
disable;
active-source-limit {
log-interval seconds;
log-warning value;
maximum number;
threshold number;
}
data-encapsulation (disable | enable);
export [ policy-names ];
group group-name {
... group-configuration ...
}
hold-time seconds;
... | [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... | [] | 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. | [
"Example: Configuring MSDP in a Routing Instance"
] |
msrpc | msrpc {
disable;
map-entry-timeout map-entry-timeout;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the MS-RPC ALG. By default, the MS-RPC ALG is enabled."
},
{
"name": "map-entry-timeout map-entry-timeout",
"desc": "Specify the MS-RPC ALG mapping entry timeout value in hours."
},
{
"name": "traceoptions",
"desc": "Configure MS-RPC ALG tracing ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding Microsoft RPC ALGs"
] |
mss (IDS MS-DPC) | mss value; | [edit services ids rule rule-name term term-name then syn-cookie] | Specify the maximum segment size (MSS) value used in Transmission Control Protocol (TCP) delayed
binding when using the MS-DPC. | [
{
"name": "value",
"desc": "MSS value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Actions in IDS Rules"
] |
mss (Security IDP) | mss {
match (equal | greater-than | less-than | not-equal);
value maximum-segment-size;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the maximum segment size (MSS) in the TCP header. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value maximum-segment-size",
"desc": "Match the maximum segment size value."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
msti | msti msti-id {
vlan (vlan-id | vlan-name);
interface interface-name {
disable-timeout;
cost cost;
priority priority;
}
} | [edit logical-systems logical-system-name protocols mstp],
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols mstp],
[edit protocols mstp],
[edit routing-instances routing-instance-name protocols mstp] | Configures the Multiple Spanning Tree Instance (MSTI) identifier for Multiple Spanning Tree Protocol
(MSTP). MSTI IDs are local to each region, so you can reuse the same MSTI ID in different regions.
Default
MSTI is disabled. | [
{
"name": "msti-id",
"desc": "MSTI instance identifier."
}
] | 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.
Statement updated in Junos OS Release 15.1 for EX Series switches to support configuration of
spanning tree parameters globally on all interfaces.
NOTE: You cannot disable spanning tree parameters globally on all in... | [
"Understanding MSTP",
"Configuring Multiple Spanning Tree Protocol",
"Configuring MSTP on Switches",
"Configuring MSTP Instances on a Physical Interface",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Understanding MSTP"
] |
mstp | [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] | Configures Multiple Spanning Tree Protocol (MSTP). MSTP is defined in the IEEE 802.1Q-2003
specification and is used to create a loop-free topology in networks with multiple spanning tree regions.
NOTE: MX Series routers and QFX5100 switches do not support the interface all
statement to enable MSTP on all interfaces wi... | [] | 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.
bpdu-block-on-edge statement added in Junos OS Release 9.4.
bpdu-timeout-action statement added in Junos OS Release 9.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding MSTP",
"Configuring Multiple Spanning Tree Protocol",
"Configuring MSTP on Switches",
"Example: Configuring Network Regions for VLANs with MSTP on Switches"
] | |
mtls-profile | mtls-profile profile-name; | [edit security firewall-authentication] | Enable passwordless user authentication based on client/server certificate validation using a public/
private key. | [
{
"name": "profile name",
"desc": "Maximum length of the profile subject is 250 characters. Supports maximum of 10"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [
"Example: Configure Mutual-TLS (mTLS) Authentication",
"[edit security firewall-authentication]"
] |
mtls-profile-fallback-password | mtls-profile-fallback-password; | [edit security firewall-authentication] | Enable user authentication with mTLS and fallback to standard login when it fails. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [
"Example: Configure Mutual-TLS (mTLS) Authentication",
"[edit security firewall-authentication]"
] |
mtrace from-source | mtrace from-source source source
<brief | detail>
<extra-hops extra-hops>
<group group>
<interval interval>
<loop>
<max-hops max-hops>
<max-queries max-queries>
<multicast-response | unicast-response>
<no-resolve>
<no-router-alert>
<response response>
<routing-inst... | Display trace information about an IP multicast path from a source to this router or switch. If you specify
a group address with this command, Junos OS returns additional information, such as packet rates and
losses. | [
{
"name": "brief | detail",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "extra-hops extra-hops",
"desc": "(Optional) Number of hops to take after reaching a nonresponsive router. You can specify a number between 0 and 255."
},
{
"name": "group group",
"de... | view
Output Fields
Table 100 on page 11469 describes the output fields for the mtrace from-source command. Output fields
are listed in the approximate order in which they appear.
Table 100: mtrace from-source Output Fields
Field Name
Field Description
Mtrace from
IP address of the receiver.
to
IP address of the source.... | Command introduced before Junos OS Release 7.4. | [] | |
mtrace monitor | mtrace monitor | Listen passively for IP multicast responses. To exit the mtrace monitor command, type Ctrl+c. | [
{
"name": "none",
"desc": "Trace the master instance."
}
] | view
Output Fields
Table 101 on page 11472 describes the output fields for the mtrace monitor command. Output fields are
listed in the approximate order in which they appear.
Table 101: mtrace monitor Output Fields
Field Name
Field Description
Mtrace query at
Date and time of the query.
by
Address of the host issuing t... | Command introduced before Junos OS Release 7.4. | [] | |
mtrace to-gateway | mtrace to-gateway gateway gateway
<brief | detail>
<extra-hops extra-hops>
<group group>
<interface interface-name>
<interval interval>
<loop>
<max-hops max-hops>
<max-queries max-queries>
<multicast-response | unicast-response>
<no-resolve>
<no-router-alert>
<response response>
<... | Display trace information about a multicast path from this router or switch to a gateway router or
switch. | [
{
"name": "gateway gateway",
"desc": "Send the trace query to a gateway multicast address."
},
{
"name": "brief | detail",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "extra-hops extra-hops",
"desc": "(Optional) Number of hops to take after reaching a non... | view
Output Fields
Table 102 on page 11476 describes the output fields for the mtrace to-gateway command. Output fields
are listed in the approximate order in which they appear.
Table 102: mtrace to-gateway Output Fields
Field Name
Field Description
Mtrace from
IP address of the receiver.
to
IP address of the source.
... | Command introduced before Junos OS Release 7.4. | [] | |
mtrace | mtrace source
<logical-system logical-system-name>
<routing-instance routing-instance-name> | Display trace information about an IP multicast path. | [
{
"name": "source",
"desc": "Source hostname or address."
},
{
"name": "logical-system (logical-system-name)",
"desc": "(Optional) Perform this operation on a logical system."
},
{
"name": "routing-instance routing-instance-name",
"desc": "(Optional) Trace a particular routing instan... | view
Output Fields
Table 103 on page 11478 describes the output fields for the mtrace command. Output fields are listed in
the approximate order in which they appear.
Table 103: mtrace Output Fields
Field Name
Field Description
Mtrace from
IP address of the receiver.
to
IP address of the source.
via group
IP address of... | Command introduced before Junos OS Release 7.4. | [] | |
mtu (Dynamic and Static PPPoE) | mtu (size | use-lower-layer); | [edit access group-profile group-profile-name ppp ppp-options],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit ppp-options],
[edit interfaces pp0 unit unit-number ppp-options... | Specify the size of maximum transmission unit (MTU) for the PPP connection. For a PPP connection, the
MTU size defines the largest data unit that can be forwarded without fragmentation. This size does not
include the overhead of the lower layers. | [
{
"name": "size",
"desc": "MTU size in bytes for a PPP connection. Range: 64–65,535"
},
{
"name": "use-lower-layer",
"desc": "Set the PPP MTU size to the interface MTU size excluding the overhead of the lower layers."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Configuring MTU and MRU for PPP Subscribers",
"Understanding MTU and MRU Configuration for PPP Subscribers"
] |
mtu (Dynamic Profiles) | mtu mtu; | [edit dynamic-profiles name interfaces name unit name family inet ],
[edit dynamic-profiles name logical-systems name interfaces name unit name family inet ],
[edit interfaces name unit name family inet ] | Configure a per-subscriber maximum transmission unit (MTU) on a logical interface. A subscriber logical
interface can specify MTU through its dynamic profile for the same underlying physical interfaces. The
dynamic logical interface MTU must be no greater than the physical interface MTU minus the dynamic
VLAN header si... | [
{
"name": "mtu",
"desc": "MTU for the subscriber logical interface. You can specify a static value or the predefined variable, $junos-interface-mtu."
}
] | interface | Statement introduced in Junos OS Release 18.1R1 on MX Series routers. | [
"Understanding Per-subscriber Support of Maximum Transmission Unit for Dynamic Profiles"
] |
mtu (interfaces) | mtu bytes; | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number family family],
[edit interfaces interface-range name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family],
[edit logical-systems logical-system-name protocols l2circuit ... | Specify the maximum transmission unit (MTU) size for the media or protocol. The default MTU size
depends on the device type. Changing the media MTU or protocol MTU causes an interface to be
deleted and added again.
If a packet whose size is larger than the configured MTU size is received on the receiving interface, the... | [
{
"name": "bytes",
"desc": "MTU size."
},
{
"name": "EX Series switch interfaces: 256 through 9216",
"desc": ""
},
{
"name": "MX Series routers: 256 through 9500 bytes",
"desc": ""
},
{
"name": "PTX Series routers: 256 through 9500 bytes",
"desc": "Starting in Junos OS Ev... | 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.
Support for Layer 2 VPNs introduced in Junos OS Release 10.4.
Support at the[set interfaces interface-name unit logical-unit-number family ccc] hierarchy level introduced
in Junos OS Release 12.3R3 for MX Series routers. | [
"Configure the Media MTU",
"Protocol MTU",
"Configuring the MTU for Layer 2 Interfaces"
] |
mtu (Multilink and Link Services Logical Interface) | mtu bytes; | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family] | Maximum transmission unit (MTU) size for the media or protocol. The default MTU size depends on the
device type. Not all devices allow you to set an MTU value, and some devices have restrictions on the
range of allowable MTU values. | [
{
"name": "bytes",
"desc": "MTU size."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring MRRU on Multilink and Link Services Logical Interfaces",
"Junos OS Network Interfaces Library for Routing Devices"
] |
mtu (QFX Series) | mtu bytes; | [edit interfaces interface-name],
[edit interfaces interface-range interface-name] | Specify the maximum transmission unit (MTU) size for the media. Changing the media MTU size causes
an interface to be deleted and added again. On QFX3500, QFX3600, QFX5100, and OCX Series
switches, either standalone or as part of the QFabric system, the maximum MTU value on an untagged
packet transiting through an ingr... | [
{
"name": "bytes",
"desc": "MTU size."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Junos OS Network Interfaces Library for Routing Devices"
] |
mtu (TDF Interface) | mtu mtu-size; | [edit interfaces mif] | Configure the maximum transmission unit (MTU) size for the TDF interface. | [
{
"name": "mtu-size",
"desc": "MTU size. Range: 256 through 9192 bytes Default: 500 bytes (inet, inet6, and ISO families), 1448 bytes (MPLS)"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a TDF Logical Interface"
] |
mtu | mtu size; | [edit interfaces interface-name] | Specify the maximum transmission unit (MTU) size for the media in bytes. MTU size can be either 1500
bytes or 2048 bytes. | [
{
"name": "size",
"desc": "Size of the MTU"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D47. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
mtu-discovery | mtu-discovery; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Configure TCP path maximum transmission unit (MTU) discovery.
TCP path MTU discovery enables BGP to automatically discover the best TCP path MTU for each BGP
session. In Junos OS, TCP path MTU discovery is disabled by default for all BGP neighbor sessions.
When MTU discovery is disabled, TCP sessions that are not direc... | [] | 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. | [
"Example: Limiting TCP Segment Size for BGP",
"Configure Path MTU Discovery"
] |
mtu-signaling | mtu-signaling; | [edit logical-systems logical-system-name protocols mpls path-mtu rsvp],
[edit protocols mpls path-mtu rsvp] | Enable MTU signaling in RSVP. | [] | 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. | [
"Enabling MTU Signaling in RSVP"
] |
multi-address-embedded-option-response (DHCP Local Server) | multi-address-embedded-option-response; | [edit system services dhcp-local-server dhcpv6 overrides],
[edit system services dhcp-local-server dhcpv6 group group-name overrides],
[edit system services dhcp-local-server dhcpv6 group group-name interface interface-name
overrides],
[edit logical-systems logical-system-name routing-instances routing-instance-name s... | Configure DHCPv6 local server to return the DNS server address (DHCPv6 attribute 23) as a suboption
in the respective IA_NA or IA_PD headers.
Default
DHCPv6 local server returns the DNS server address as a global DHCPv6 option. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R3 and supported in later 12.3Rx releases.
Statement supported in Junos OS Release 13.3 and later releases. (Not supported in Junos OS Release
13.1 and Release 13.2.) | [
"Overriding How the DNS Server Address Is Returned in a DHCPv6 Multiple Address Environment",
"Overriding the Default DHCP Local Server Configuration Settings"
] |
multi-bgp-path | multi-bgp-path; | [edit services flow-monitoring version-ipfix template template-name]
[edit services flow-monitoring version9 template template-name] | (Junos OS only) Enable multiple BGP path support for reporting an accurate BGP next-hop address for
traffic load-balanced over multiple BGP peers in the ingress direction only. Without this statement, we
report only the first in a list of next hops. To contain this accurate BGP next-hop address, we use the
IPv4 BGP Nex... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
multi-bgp-path | multi-bgp-path; | [edit services flow-monitoring version-ipfix template template-name]
[edit services flow-monitoring version9 template template-name] | (Junos OS only) Enable multiple BGP path support for reporting an accurate BGP next-hop address for
traffic load-balanced over multiple BGP peers in the ingress direction only. Without this statement, we
report only the first in a list of next hops. To contain this accurate BGP next-hop address, we use the
IPv4 BGP Nex... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
multi-chassis | multi-chassis {
multi-chassis-protection peer-ip-address {
interface interface-name;
}
mc-lag consistency-check;
} | [edit] | Configure an interchassis link-protection link (ICL-PL) between the two peers that host a multichassis
link aggregation group (MC-LAG). You can configure either an aggregated Ethernet interface or a 10-
Gigabit Ethernet interface to be an ICL-PL.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
multi-chassis-protection (Interfaces) | multi-chassis-protection {
peer a.b.c.d {
interface interface-name;
}
} | [edit interfaces interface-name] | For MX Series routers with multichassis aggregated Ethernet (MC-AE) interfaces, you can use this
statement under the physical interface level to reduce the configuration at the logical interface level if
the following assumption exists:
If there are n +1 logical interfaces under ae0, from ae0.0 through ae0.n, there wil... | [
{
"name": "interface interface-name",
"desc": "Specify the interface: interface interface-name-fpc/pic/port"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation on MX",
"Series Routers and QFX Series Switches",
"Configuring Aggregated Ethernet Link Protection",
"Example: Configuring Aggregated Ethernet Link Protection"
] |
multi-chassis-protection | multi-chassis-protection peer-ip-address {
interface interface-name;
} | [edit multi-chassis] | Configure multichassis link protection between the two peers that host a multichassis link aggregation
group (MC-LAG). If the Interchassis Control Protocol (ICCP) connection is up and the interchassis link
(ICL) comes up, the peer configured as standby brings up the multichassis aggregated Ethernet
interfaces shared wi... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
multi-destination (Class of Service) | multi-destination {
classifiers {
(dscp | dscp-ipv6 | ieee-802.1 | inet-precedence) classifier-name;
}
} | [edit class-of-service]
[edit class-of-service interfaces interface-name] | Define a CoS behavior aggregate (BA) classifier for multi-destination, or BUM (broadcast, unknown
unicast, and multicast), traffic.
There is no default multi-destination classifier. Without explicit multi-destination classifier configuration,
all BUM traffic is sent to the default multicast queue (queue 8), which recei... | [] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Defining CoS BA Classifiers (DSCP, DSCP IPv6, IEEE 802.1p)",
"Example: Configuring Multidestination (Multicast, Broadcast, DLF) Classifiers",
"Assigning CoS Components to Interfaces",
"Understanding CoS Classifiers"
] |
multi-domain | multi-domain {
max-data-session max-data-sessions;
packet-action (drop-and-log | shutdown);
recovery-timeout seconds;
} | [edit logical-systems name protocols dot1x authenticator
interface],
[edit protocols dot1x authenticator interface] | Configure multi-domain authentication to restrict the number of authenticated data and VoIP sessions
on the port. Multi-domain authentication is an extension of multiple supplicant mode for 802.1X
authentication, and is designed to support VoIP and data clients on the same interface. The interface is
divided into two d... | [
{
"name": "max-data-session max-",
"desc": ""
},
{
"name": "data-sessions",
"desc": "The maximum number of authenticated data sessions allowed in the data domain on the 802.1X-enabled interface. Range: 1 through 1,000 sessions Default: 1"
},
{
"name": "packet-action",
"desc": ""
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [] |
multi-homing (VPLS Multihoming for BGP VPLS) | multi-homing; | [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] | Configuration of this statement tracks BGP peers, such as to prevent isolation of the PE router from the
core or split brain.. If no BGP peer is available, all active interfaces for a site are deactivated.
When identical site IDs are used without configuring multihoming, a collision log message is generated
at each sig... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configuring Multihoming on the PE Router"
] |
multi-homing (VPLS Multihoming for FEC 129) | multi-homing {
peer-active;
site site-name {
active-interface interface-name {
any;
primary interface-name;
}
identifier identifier;
interface interface-name {
preference preference-value;
}
peer-active;
preference (pre... | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls],
[edit routing-instances instance-name protocols vpls] | For VPLS autodiscovery (FEC 129), specify the parameters for multihoming to two or more provider
edge (PE) routers.
NOTE: In the VPLS documentation, the word router in terms such as PE router is used to
refer to any device that provides routing functions.
The remaining statements are explained separately. See CLI Explo... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Example: Configuring VPLS Multihoming (FEC 129)"
] |
multi-link-layer-2-inline | multi-link-layer-2-inline; | [edit chassis fpc number pic number] | Enable inline Layer 2 bundling services. | [] | 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. | [
"Inline MLPPP for WAN Interfaces Overview",
"Example: Configuring Inline MLPPP and Multilink Frame Relay End-to-End (FRF.15) for WAN",
"Interfaces",
"Example: Configuring Inline Multilink Frame Relay (FRF.16) for WAN Interfaces"
] |
multi-sa | multi-sa {
forwarding-class expedited-forwarding | assured-forwarding | best-effort | network-control;
} | [edit security ipsec vpn] | Negotiate multiple security association (SAs) based on configuration choice. Multiple SAs negotiates
with the same traffic selector on the same IKE SA. By negotiating multiple SAs, the peer gateways have
more replay windows. If the peer gateways create separate multiple SAs for the configured Forwarding-
Classes (FC),... | [
{
"name": "forwarding-class",
"desc": "Forwarding classes (FCs) allow you to group packets for transmission and to assign packets to output queues. Values:"
},
{
"name": "expedited-forwarding",
"desc": "Provides a low-loss, low-latency, low-jitter, assured-bandwidth, end-to-end service."
},
... | security | Statement introduced in Junos OS Release 18.2R1. | [
"Understanding CoS-Based IPsec VPNs with Multiple IPsec SAs",
"Example: Configuring CoS-Based IPsec VPNs"
] |
multi-tenant-hash | multi-tenant-hash {
file-hash-key {
ascii-text;
hexa-decimal;
}
hash-method {
ascii-text;
hexa-decimal;
}
} | [edit services web-filter] | Configure the hash key and hash method to validate the file-hash present at the end of the hashed
indicator file.
When multi-tenant-hash is configured, It indicates that the global DNS feed file consists of only encrypted
feeds. When multi-tenant-hash is not configured, it indicates that the feeds present in the globa... | [
{
"name": "file-hash-key",
"desc": "Define the web-filter global file key."
},
{
"name": "hash-method",
"desc": "Define the authentication algorithm."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1.
Support added in Junos OS Release 21.1R1 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"DNS Request Filtering for Disallowed Website Domains"
] |
multi-tenant-support | multi-tenant-support | [edit services service-set service-set-name web-filter | Configure domain-names and actions for multiple tenants such that domain feeds can be managed per
tenant basis. Thus, you can achieve hierarchical management of the domain feeds per customer (Profile),
partitioning the customer into multiple entities (Templates), and further partitioning IP-addresses within
that entity... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1.
Support added in Junos OS Release 21.1R1 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"DNS Request Filtering for Disallowed Website Domains"
] |
multicast (Dynamic Routing Options) | multicast {
interface interface-name {
no-qos-adjust;
}
} | [edit dynamic-profiles profile-name routing-options],
[edit dynamic-profiles profile-name routing-instances routing-instance-name routing-options]
NOTE: You cannot apply a scope policy to a specific routing instance. That is, all scoping
policies are applied to all routing instances. However, the scope statement does a... | Dynamically configure interface-specific multicast routing options properties in a dynamic client profile.
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 9.6. | [
"Example: Configuring the Multicast Forwarding Cache",
"Example: Configuring a Multicast Flow Map",
"Example: Configuring Source-Specific Multicast Groups with Any-Source Override"
] |
multicast (Protocols Router Discovery) | (multicast | broadcast); | [edit logical-systems logical-system-name protocols router-discovery address address],
[edit protocols router-discovery address address] | Specify when the server should include the IP addresses in router advertisement packets. On the same
physical interfaces, some addresses might be included only in multicast packets, while others might be
included only in broadcast packets.
If you specify multicast, the server includes the addresses in router advertisem... | [] | 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. | [
"Understanding the ICMP Protocol for Discovering Gateways to Other Networks",
"Example: Configuring the ICMP Protocol for Discovering Gateways to Other Networks"
] |
multicast (QFabric Routing Options) | multicast {
fabric-optimized-distribution
no-make-before-break;
} | [edit fabric routing-options] | (QFabric systems only) Set multicast routing options in a QFabric system, such as "no-make-before-
break" on page 11991. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Understanding the QFabric System Data Plane"
] |
multicast (routing-options) | multicast {
asm-override-ssm;
backup-pe-group group-name {
backups [ addresses ];
local-address address;
}
cont-stats-collection-interval interval;
flow-map flow-map-name {
bandwidth (bps | adaptive);
forwarding-cache {
timeout (never non-discard-entry-onl... | [edit dynamic-profiles profile-name routing-options],
[edit dynamic-profiles profile-name routing-instances routing-instance-name routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routi... | 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 before Junos OS Release 7.4.
interface and maximum-bandwidth statements introduced in Junos OS Release 8.3.
interface and maximum-bandwidth statements introduced in Junos OS Release 9.0 for EX Series
switches.
Statement added to [edit dynamic-profiles routing-options] and [edit dynamic-profiles pro... | [
"Examples: Configuring Administrative Scoping",
"Example: Configuring the Multicast Forwarding Cache",
"Example: Configuring a Multicast Flow Map",
"Example: Configuring Source-Specific Multicast Groups with Any-Source Override",
"indirect-next-hop"
] |
multicast (Tunnel Services) | multicast; | [edit chassis feb slot slot-number pfe number core number channel number tunnel-services],
[edit chassis fpc slot-number pfe number core number channel number tunnel-services] | For ACX7K Series routers, you can create a multicast tunnel (mt) interface and reserve bandwidth for
multicast tunnel services using this configuration statement.
For example:
set chassis fpc 0 pfe 0 core 0 channel 3 tunnel-services multicast bandwidth 10g
This configuration will create multicast tunnel interface mt-0... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1EVO. | [
"Configure Multicast Tunnel Interfaces on ACX7K Series Routers"
] |
multicast (Virtual Tunnel in Routing Instances) | multicast; | [edit logical-systems logical-system-name routing-instances routing-instance-name interface vt-
fpc/pic/port.unit-number],
[edit routing-instances routing-instance-name interface vt-fpc/pic/port.unit-number] | In a multiprotocol BGP (MBGP) multicast VPN (MVPN), configure the virtual tunnel (VT) interface to be
used for multicast traffic only.
Default
If you omit this statement, the VT interface can be used for both multicast and unicast traffic. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Example: Configuring Redundant Virtual Tunnel Interfaces in MBGP MVPNs",
"Example: Configuring MBGP MVPN Extranets"
] |
multicast | multicast; | [edit ethernet-switching-options storm-control (switch) interface (all | interface-name)] | Enable storm control for all multicast traffic (both registered multicast and unregistered multicast) for
the specified interface or for all interfaces.
Default
•
On EX2200, EX3200, and EX4200 switches—Storm control does not apply to multicast traffic by
default.
•
On EX4500 and EX8200 switches—Storm control is enabled... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Enabling and Disabling Storm Control (non-ELS)"
] |
multicast-dlci | multicast-dlci dlci-identifier; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For point-to-multipoint link services interfaces only, enable multicast support on the interface. You can
configure multicast support on the interface if the Frame Relay switch performs multicast replication. | [
{
"name": "dlci-identifier",
"desc": "DLCI identifier, a number from 16 through 1022 that defines the Frame Relay DLCI over"
}
] | 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 Multicast-Capable DLCIs for MLFR FRF.16 Bundles",
"Configuring a Multicast-Capable Frame Relay Connection",
"dlci",
"multipoint-destination",
"Junos OS Services Interfaces Library for Routing Devices"
] |
multicast-group | multicast-group address; | [edit vlans vlan-name vxlan] | Assign a multicast group address to a Virtual Extensible LAN (VXLAN). All members of a VXLAN must
use the same multicast group address. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Understanding VXLANs",
"Manually Configuring VXLANs on QFX Series and EX4600 Switches",
"Examples: Manually Configuring VXLANs on QFX Series and EX4600 Switches"
] |
multicast-ipv4 | multicast-ipv4 {
source-ip source-ip-address;
dest-ip-multicast-group ipv4-mcast-address;
} | [edit protocols oam fabric flow-specs flow-specification-name] | Configure multicast parameters for the IPv4 Ethernet protocol type in the internal fabric monitoring
flow specifications. | [
{
"name": "dest-ip-multicast-group ipv4-mcast-",
"desc": ""
},
{
"name": "address",
"desc": "IPv4 multicast group address of the destination fabric maintenance endpoint (FMEP) that is configured in the flow specification. Configuration of this parameter is mandatory. Syntax: Dotted decimal nota... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
multicast-loadbalance | multicast-loadbalance {
disable (Multicast Load Balancing);
hash-mode mode;
} | [edit chassis] | (EX8200 switches only) Enable multicast load balancing to evenly distribute the Layer 3 routed multicast
traffic on aggregated 10-gigabit Ethernet interfaces. When multicast load balancing is enabled on the
EX8200 switch, it takes effect on aggregated 10-gigabit Ethernet interfaces that are currently
configured as well... | [
{
"name": "hash-mode mode",
"desc": "Specify one of these hashing algorithms:"
},
{
"name": "balanced",
"desc": "Use a round-robin method to determine the aggregated Ethernet links with the least amount of traffic."
},
{
"name": "crc-gip",
"desc": "Use multicast packets’ group IP add... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2 for EX Series switches. | [
"Example: Configuring Multicast Load Balancing for Use with Aggregated 10-Gigabit Ethernet",
"Interfaces on EX8200 Switches",
"Configuring Multicast Load Balancing for Use with Aggregated 10-Gigabit Ethernet Links on EX8200",
"Switches (CLI Procedure)"
] |
multicast-mode (EVPN) | multicast-mode client | ingress-replication; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols evpn],
[edit routing-instances routing-instance-name protocols evpn] | Configure the multicast server mode for delivering traffic and packets for Ethernet VPN (EVPN). This
statement is required for a VXLAN EVPN instance.
NOTE: If you configure the multicast-mode statement, then you must also configure the
encapsulation (protocols evpn) vxlan statement. | [
{
"name": "client",
"desc": "Use the client as the multicast mode for delivering traffic and multicast packets across routers and switches."
},
{
"name": "ingress-replication",
"desc": "Use ingress replication as the multicast mode for delivering broadcast, unknown unicast, and multicast (BUM) t... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D30.
Support for logical systems on MX Series routers added in Junos OS Release 17.4R1.
Support for primary and secondary asymmetry on MX Series routers added in Junos OS Release 23.1R1. | [
"Understanding EVPN with VXLAN Data Plane Encapsulation",
"EVPN Over VXLAN Encapsulation Configuration Overview for QFX Series and EX4600 Switches",
"Using a Default Layer 3 Gateway to Route Traffic in an EVPN-VXLAN Overlay Network",
"Example: Configuring an EVPN Control Plane and VXLAN Data Plane"
] |
multicast-only | multicast-only; | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet] | Configure the unit and family so that the interface can transmit and receive multicast traffic only. You
can configure this property on the IP family only. | [] | 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. | [
"Restricting Tunnels to Multicast Traffic"
] |
multicast-replication | multicast-replication {
evpn {
irb (local-only | local-remote | oism | enhanced-oism);
smet-forwarding;
smet-nexthop-limit smet-nexthop-limit;
}
ingress;
local-latency-fairness;
} | [edit forwarding-options] | Configure the mode of multicast replication that helps to optimize multicast latency.
NOTE: The multicast-replication statement is supported only on platforms with the
enhanced-ip mode enabled.
Default
This statement is disabled by default. | [
{
"name": "ingress",
"desc": "Complete ingress replication of the multicast data packets where all the egress Packet Forwarding Engines receive packets from the ingress Packet Forwarding Engines directly."
},
{
"name": "local-latency-fairness",
"desc": "Complete parallel replication of the multi... | 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.
evpn stanza introduced in Junos OS Release 17.3R3 for QFX Series switches.
oism option in evpn irb stanza introduced in Junos OS Release 21.2R1.
smet-forwarding option in evpn stanza introduced in Junos OS Evolved Release 24.4R1. | [
"Inter-VLAN Multicast Forwarding Modes for EVPN-VXLAN Overlay Networks",
"Optimized Inter-Subnet Multicast in EVPN Networks",
"Overview of Selective Multicast Forwarding",
"Configuring the number of SMET Nexthops"
] |
multicast-router-interface (IGMP Snooping) | multicast-router-interface; | [edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id interface interface-
name],
[edit protocols igmp-snooping vlan (all | vlan-name) interface (all | interface-name)],
[edit routing-instances routing-inst... | Statically configure the interface as an IGMP snooping multicast-router interface—that is, an interface
that faces toward a multicast router or other IGMP querier.
NOTE: If the specified interface is a trunk port, the interface becomes a multicast-
routing device interface for all VLANs configured on the trunk port. In... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring IGMP Snooping",
"IGMP Snooping in MC-LAG Active-Active Mode"
] |
multicast-router-interface (MLD Snooping) | multicast-router-interface; | [edit protocols mld-snooping vlan (all | vlan-name) interface (all | interface-name)],
[edit routing-instances instance-name protocols mld-snooping vlan vlan-name interface interface-
name] | Statically configure the interface as a multicast-router interface—that is, an interface that faces towards
a multicast router or other MLD querier.
NOTE: If the specified interface is a trunk port, the interface becomes a multicast-router
interface for all VLANs configured on the trunk port. In addition, all unregiste... | [] | 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.
Support at the [edit routing-instances instance-name protocols mld-snooping vlan vlan-name interface interface-
name] hierarchy level introduced in Junos OS Release 13.3 for EX Series switches. | [
"Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)"
] |
multicast-snooping-options | multicast-snooping-options {
flood-groups [ ip-addresses ];
forwarding-cache {
threshold suppress value <reuse value>;
}
host-outbound-traffic (Multicast Snooping) {
forwarding-class class-name;
dot1p number;
}
graceful-restart <restart-duration seconds>;
ignore-stp-... | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Multicast Snooping",
"Enabling Bulk Updates for Multicast Snooping",
"Example: Configuring Multicast Snooping"
] |
multicast-statistics (packet-forwarding-options) | multicast-statistics; | [edit system packet-forwarding-options] | Counts packets and checks the bandwidth of IPv4 and IPv6 multicast traffic received from a host and
group in a routing instance by using firewall filters.
With multicast-statistics enabled, route statistics are updated by a firewall counter for the next 512
multicast routes. Statistics are attached and collected on a f... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"Firewall Filters for EX Series Switches Overview"
] |
multicast-statistics | multicast-statistics; | [edit interfaces interface-name] | For Ethernet, SONET, aggregated Ethernet, and aggregated SONET interfaces in T Series or TX Matrix
routers, specify support for multicast statistics on a physical interface to enable multicast accounting for
all the logical interfaces below the physical interface.
Default
not enabled—must be configured to enable | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 10.2. | [
"Configuring Multicast Statistics Collection on Aggregated Ethernet Interfaces",
"Configuring Multicast Statistics Collection on Aggregated SONET Interfaces",
"Configuring Multicast Statistics Collection on Ethernet Interfaces",
"Configuring Multicast Statistics Collection on SONET Interfaces"
] |
multicast-vlan-flood | multicast-vlan-flood | [edit protocols oam fabric flow-specs flow-specification-name] | Configure parameters of the multicast VLAN flood protocol type in the internal fabric monitoring flow
specification. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
multichassis-lag-replicate-state | multichassis-lag-replicate-state; | [edit multicast-snooping-options] | Provide multicast snooping for multichassis link aggregation group interfaces. Replicate IGMP join and
leave messages from the active link to the standby link of a dual-link multichassis link aggregation group
interface, enabling faster recovery of membership information after failover.
This command is configured globa... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Multicast Snooping",
"multicast-snooping-options"
] |
multichunk-inspection | multichunk-inspection (enable | disable); | [edit security sctp] | The Stream Control Transmission Protocol (SCTP) firewall checks all chunks in a message and then
permits or drops the packet based on the policy. Use the multichunk-inspection enable command to
enable SCTP multichunk inspection. It checks all the chunks in a message. Use the multichunk-
inspection disable command to di... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [
"Understanding SCTP Multichunk Inspection"
] |
multihop | multihop {
no-nexthop-change;
ttl ttl-value;
} | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Configure an EBGP multihop session.
For Layer 3 VPNs, you configure the EBGP multihop session between the PE and CE routing devices.
This allows you to configure one or more routing devices between the PE and CE routing devices.
An external confederation peer is a special case that allows unconnected third-party next ... | [
{
"name": "no-nexthop-",
"desc": ""
},
{
"name": "change",
"desc": "Specify that the BGP next-hop value not be changed. An external confederation peer is a special case that allows unconnected third-party next hops. You do not need to configure multihop sessions explicitly in this particular cas... | 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.
Support for setting the TTL on single-hop external BGP (EBGP) peers introduced in Junos OS Release
13.3. | [
"Example: Configuring EBGP Multihop Sessions",
"Configuring EBGP Multihop Sessions Between PE and CE Routers in Layer 3 VPNs",
"accept-remote-nexthop",
"https://forums.juniper.net/t5/Automation/Scripting-How-To-Use-the-ttl-security-script-to-turn-on-",
"TTL/ta-p/279358"
] |
multilink | multilink {
drop-timeout milliseconds;
fragment-threshold bytes;
} | [edit access profile profile-name client client-name l2tp] | Configure Multilink PPP for Layer 2 Tunneling Protocol (L2TP).
NOTE: This statement is not supported for L2TP LNS on MX Series routers. | [
{
"name": "drop-timeout",
"desc": "(M Series, MX Series, PTX Series, T Series only) Configure the drop timeout for a multilink bundle. Values:"
},
{
"name": "milliseconds",
"desc": "Number of milliseconds for the timeout that is associated with the"
},
{
"name": "reassembly queue has be... | 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. | [
"Layer 2 Tunneling Protocol (L2TP)"
] |
multilink-class | multilink-class number; | [edit class-of-service fragmentation-maps map-name forwarding-class class-name] | For link services IQ (lsq) interfaces only, map a forwarding class into a multiclass MLPPP (MCML).
The multilink-class statement and no-fragmentation statements are mutually exclusive. | [
{
"name": "number",
"desc": "The multilink class assigned to this forwarding class."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring CoS Fragmentation by Forwarding Class on LSQ Interfaces",
"Configuring Fragmentation by Forwarding Class",
"Junos OS Services Interfaces Library for Routing Devices"
] |
multilink-max-classes | multilink-max-classes number; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For link services IQ (lsq) interfaces only, configure the number of multilink classes to be negotiated when
a link joins the bundle. | [
{
"name": "number",
"desc": "The number of multilink classes to be negotiated when a link joins the bundle."
}
] | 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. | [] |
multipath (OSPF SPF Options) | multipath [
weighted {
one-hop;
}
} | [edit protocols ospf spf-options] | Enable weighted equal-cost multipath (ECMP) for load-sharing data based on the bandwidth for
incoming traffic destined to OSPFv2 neighbors that are at a one-hop distance. The OSPFv2 protocol
gets the logical interface bandwidth information associated with the gateways of ECMP next hop and
shares this information with t... | [
{
"name": "weighted",
"desc": "Enable weighted ECMP for efficient load sharing."
},
{
"name": "one-hop",
"desc": "Enable weighted ECMP load balancing on IOSPFv2 neighbors that are just one hop away based on the interface bandwidth."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 24.2R1. | [] |
multipath (Protocols BGP) | multipath {
allow-external-internal;
allow-protection;
disable;
list-nexthop
multiple-as;
prioritization;
starving-age 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]
[edit logical-systems logical-system-name protocols bgp multipath allow-external-internal]
[edit logical-s... | Allow load sharing among multiple EBGP paths and multiple IBGP paths. A path is considered a BGP
equal-cost path (and will be used for forwarding) if a tie-break is performed. The tie-break is performed
after the BGP route path selection step that chooses the next-hop path that is resolved through the IGP
route with th... | [
{
"name": "allow-external-internal",
"desc": "Allows IBGP paths to coexist with EBGP paths, and considers both EBGP and IBGP paths equal when path selection between them reaches a point where EBGP paths are preferred."
},
{
"name": "allow-protection",
"desc": "Allows BGP multipath and protection... | 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.
disable option introduced in Junos OS Release 18.1R1.
allow-protection option introduced in Junos OS Release 18.4R1.
allow-external-internal option introduced in Junos OS Release 23.4R1.
starving-age option introduced in Junos OS Release 25.2R1. | [
"Understanding BGP Path Selection",
"Example: Load Balancing BGP Traffic"
] |
multipath (Routing Options) | multipath {
vpn-unequal-cost equal-external-internal;
as-path-compare;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name],
[edit routing-instances routing-instance-name routing-options],
[edit routing-instances routing... | Enable protocol-independent load balancing for Layer 3 VPNs. This allows the forwarding next hops for
both the active route and alternative paths to be used for load balancing. For IPv6, you must configure
the multipath statement at both the [edit routing-instances routing-instance-name routing-options] hierarchy
level... | [] | 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.
equal-external-internal option added in Junos OS Release 8.4.
as-path-compare option introduced in Junos OS Release 10.1 | [
"Configuring Protocol-Independent Load Balancing in Layer 3 VPNs"
] |
multipath (SPF Options) | multipath [
weighted {
one-hop;
}
} | [edit protocols isis spf-options] | Enable weighted equal-cost multipath (WECMP) routing to load-balance traffic in proportion to the
changing aggregated ethernet link bandwidth on an equal cost path (ECMP) between directly connected
routers. Distributing traffic equally on all equal cost path (ECMP) might lead to imbalanced link
utilization if a change ... | [
{
"name": "weighted",
"desc": "Enable weighted ECMP for efficient load sharing."
},
{
"name": "one-hop",
"desc": "Enable weighted ECMP load balancing on IS-IS neighbors that are just one hop away based on the interface bandwidth."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F4. | [
"Example: Weighted ECMP Traffic Distribution on One-Hop IS-IS Neighbors",
"Understanding Weighted ECMP Traffic Distribution on One-Hop IS-IS Neighbors"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.