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 |
|---|---|---|---|---|---|---|---|
micro-srv6-sid | micro-srv6-sid {
micro-sid ipv6-address;
strict-adjacency;
} | [edit logical-systems name protocols source-packet-routing segment-list],
[edit protocols source-packet-routing segment-list] | Configure a micro Segment Routing over IPv6 (SRv6) Segment ID (SID) for use in an SR-TE segment list.
The micro-srv6-sid statement enables you to define compressed uSIDs (micro-SIDs) for TE paths using
SRv6 micro-segmentation.
This configuration is specifically for segment lists where all hops are micro-SID based. When... | [
{
"name": "micro-sid",
"desc": "Specifies the micro SID in IPv6 address format. This SID must match the format advertised by the IS-IS IGP (for example, <block>:<uN> or <block>:<uN>:<uA>)."
},
{
"name": "strict-adjacency",
"desc": "Indicates that this hop must be strictly adjacent to the previou... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
microloop-avoidance (Protocols OSPF) | microloop-avoidance {
post-convergence-path {
delay delay;
maximum-labels maximum-labels;
}
} | [edit logical-systems name protocols ospf spf-options],
[edit logical-systems name routing-instances name protocols ospf spf-options],
[edit logical-systems name tenants name routing-instances name protocols ospf spf-options],
[edit routing-instances name protocols ospf spf-options],
[edit tenants name routing-instance... | Configure microloop avoidance mechanisms that temporarily install a post-convergence path for routes
potentially affected by microloops. The temporary path is used for the specified delay time period and
reverts to the node SIDs of the destination after the delay timer expires.
NOTE: Micro-loop avoidance is not a repla... | [
{
"name": "post-convergence-path",
"desc": ""
},
{
"name": "delay delay;",
"desc": "Time in milliseconds after which temporary post-convergence paths are removed. Range: 500 through 60000 Default: 5000ms"
},
{
"name": "maximum-labels",
"desc": ""
},
{
"name": "maximum-label... | routing | Statement introduced in Junos OS Release 22.1R1. | [] |
microloop-avoidance | microloop-avoidance {
post-convergence-path {
delay milliseconds;
maximum-labels maximum-labels-value;
maximum-srv6-sids maximum-srv6-sids-value;
}
} | [edit logical-systems name protocols isis spf-options],
[edit logical-systems name routing-instances name protocols isis spf-options],
[edit logical-systems name tenants name routing-instances name protocols isis spf-options],
[edit protocols isis spf-options],
[edit routing-instances name protocols isis spf-options],
... | Configure microloop avoidance mechanisms that temporarily install a post-convergence path for routes
potentially affected by microloops. The temporary path is used for the specified delay time period and
reverts to the node SIDs of the destination after the delay timer expires.
NOTE: Micro-loop avoidance is not a repla... | [
{
"name": "post-convergence-path",
"desc": ""
},
{
"name": "delay milliseconds;",
"desc": "Time in milliseconds after which temporary post-convergence paths are removed. Range: 500 through 60000 Default: 5000ms"
},
{
"name": "maximum-labels (SR-MPLS)",
"desc": "Maximum number of la... | routing | Statement introduced in Junos OS Release 21.1R1.
maximum-labels and maximum-srv6-sids options introduced in Junos OS Release 21.3R1. | [
"IGP Microloop Avoidance"
] |
mif (TDF Interface) | mif {
mtu;
unit interface-unit-number {
family family-name {
service {
input service-set;
output service-set;
}
}
}
} | [edit interfaces] | Configure the TDF interfaces for the TDF domains. A TDF interface is distinct from other types of
interfaces and is used to associate a TDF domain’s subscribers with an access interface in a virtual
routing and forwarding table (VRF). You need to configure one TDF interface logical interface (unit) for
every TDF domain... | [] | 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"
] |
mime-pattern | mime-pattern object-name {
value [value];
} | [edit security utm default-configuration]
[edit security utm custom-objects] | The gateway device uses MIME (Multipurpose Internet Mail Extension) types to decide which traffic is
allowed to bypass various types of scanning. | [
{
"name": "object-name",
"desc": "Name of the MIME object."
},
{
"name": "value value",
"desc": "Value of the MIME object. You can configure multiple values separated by spaces and"
}
] | 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. | [] |
mime-whitelist | mime-whitelist {
exception listname;
list listname {
exception listname;
}
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus] | Configure the antivirus scanner to use MIME bypass lists and exception lists. You can use your own
custom object lists, or you can use the default list that ships with the device called junos-default-bypass-
mime.
WARNING: When you configure the MIME allowlist feature, be aware that, because
header information in HTTP ... | [] | 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. Statement updated.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
min-advertisement-interval (Dynamic Router Advertisement) | min-advertisement-interval seconds; | [edit dynamic-profiles protocols router-advertisement interface interface-name] | Minimum interval between each router advertisement message. | [
{
"name": "seconds",
"desc": "Minimum interval."
}
] | 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. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
min-advertisement-interval (Protocols IPv6 Neighbor Discovery) | min-advertisement-interval seconds; | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Set the minimum interval between each router advertisement message.
The router sends router advertisements on each interface configured to transmit messages. The
advertisements include route information and indicate to network hosts that the router is operational.
The router sends these messages periodically, with a ti... | [
{
"name": "seconds",
"desc": "Minimum interval."
}
] | 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 IPv6 Interfaces and Enabling Neighbor Discovery"
] |
min-advertisement-interval (Protocols Router Discovery) | min-advertisement-interval seconds; | [edit logical-systems logical-system-name protocols router-discovery interface interface-name],
[edit protocols router-discovery interface interface-name] | Specify the minimum time the router waits before sending router advertisement packets out the
interface in response to router solicitation packets it receives from a client. These packets are broadcast
or multicast, depending on how the address corresponding to this physical interface is configured. | [
{
"name": "seconds",
"desc": "Minimum time between router advertisement packets."
}
] | 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"
] |
min-checked-bytes | min-checked-bytes bytes; | [edit services application-identification] | Specify the minimum number of bytes to be inspected. | [
{
"name": "bytes",
"desc": "Minimum number of bytes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Global APPID Properties"
] |
min-message-length | min-message-length number; | [edit security gtp profile profile-name] | In the GPRS tunneling protocol (GTP) header, the message length field indicates the length, in octets, of
the GTP payload. Use the min-message-length option to set the minimum message payload length (in
bytes). The minimum GTP message length is 0 bytes. The message length range is from 1 through
65,535 bytes.
From Juno... | [
{
"name": "number",
"desc": "To set the minimum message payload length in bytes."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. Support. | [
"Understanding GTP Message Filtering",
"Example: Setting the GTP Message-Length Filtering"
] |
min-rate (source-active-advertisement) | min-rate bps | [edit logical-systems logical-system--name routing-instances instance-name protocols mvpn mvpn-
mode spt-only source-active-advertisement],
[edit routing-instances instance-name protocols mvpn mvpn-mode spt-only source-active-advertisement] | Minimum traffic rate required to advertise Source-Active route (1 to 1000000 bits per second), set on
the ingress PEs.
Use the command, for example, to ensure that the egress PEs only receive Source-Active A-D route
advertisements from ingress PEs that are receiving traffic at or above a minimum rate, regardless of how... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring SPT-Only Mode for Multiprotocol BGP-Based Multicast VPNs"
] |
min-rate | min-rate {
rate bps;
revert-delay seconds;
ipmsi-min-rate rate;
} | [edit routing-instances routing-instance-name protocols mvpn hot-root-standby] | Fast failover (that is, sub-50ms switch over for C-multicast streams as defined in Draft Morin L3VPN
Fast Failover 05, ) is supported for MPC cards operating in enhanced-ip mode that are running next
generation (NG) MVPNs with hot-root-standby enabled.
Live-live NG MVPN traffic is available by enabling both sender-base... | [
{
"name": "rate",
"desc": "Specify a rate to represent the typical flow rate of aggregate multicast traffic from the provider"
},
{
"name": "revert-delay seconds",
"desc": "Use the specified interval to allow time for the network to converge when and if the"
},
{
"name": "ipmsi-min-rate ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Non-revertive behavior introduced in Junos OS Release 22.4R3-S1.
ipmsi-min-rate introduced in Junos OS Release 24.2R1. | [
"Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels"
] |
mine-dhcp-client-options | mine-dhcp-client-options; | [edit vlans vlan-name forwarding-options dhcp-security] | Enables DHCP snooping to collect various DHCP client options for analytics.
Default
Disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1. | [] |
mine-dhcpv6-client-options | mine-dhcpv6-client-options; | [edit vlans vlan-name forwarding-options dhcp-security] | Enables DHCP snooping to collect various DHCPv6 client options for analytics.
Default
Disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1. | [] |
minimum-bandwidth (aggregated Ethernet) | minimum-bandwidth bw-unit unit bw-value value; | [edit interfaces aex aggregated-ether-options] | Configure the minimum bandwidth unit for an aggregated Ethernet bundle as bps, Gbps, Kbps, or Mbps
and the bandwidth value from 1 through 128,000.
(T Series, MX Series, PTX Series routers) You cannot configure the minimum number of links and the
minimum bandwidth for an aggregated Ethernet bundle at the same time. They... | [
{
"name": "unit",
"desc": "Minimum bandwidth unit for the aggregated Ethernet bundle as bps, Gbps, Kbps, or Mbps."
},
{
"name": "value",
"desc": "Minimum bandwidth value from 1 through 128,000."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 14.1R1 and 14.2. | [
"Aggregated Ethernet Interfaces Overview",
"Understanding Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles",
"Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles"
] |
minimum-bandwidth | minimum-bandwidth bps; | [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] | Set the minimum bandwidth in bps for an LSP with automatic bandwidth allocation enabled.
NOTE: For a label-swtiched path (LSP) that has both bandwidth and minimum-bandwidth for
autobandwidth configured under the [edit protocols mpls label-switched-path lsp-name]
hierarchy level, the LSP bandwidth is adjusted differentl... | [
{
"name": "bps",
"desc": "Miniminum bandwidth for the LSP."
}
] | 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 Maximum and Minimum Bounds of the LSP’s Bandwidth"
] |
minimum-bandwidth-adjust-interval | minimum-bandwidth-adjust-interval seconds; | [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] | Specify the duration (in seconds) for which minimum bandwidth is frozen. | [
{
"name": "seconds",
"desc": "Minimum bandwidth reallocation interval, in seconds."
}
] | 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. | [
"Configuring the Maximum and Minimum Bounds of the LSP’s Bandwidth"
] |
minimum-bandwidth-adjust-threshold-change | minimum-bandwidth-adjust-threshold-change percentage; | [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] | Specify the percentage change in maximum average bandwidth to freeze the minimum bandwidth. | [
{
"name": "percentage",
"desc": "Percentage change in maximum average bandwidth."
}
] | 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. | [
"Configuring the Maximum and Minimum Bounds of the LSP’s Bandwidth"
] |
minimum-bandwidth-adjust-threshold-value | minimum-bandwidth-adjust-threshold-value bps; | [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] | Specify the value in bits per second (bps) to freeze the minimum bandwidth if the maximum average
bandwidth falls below this value. | [
{
"name": "bps",
"desc": "Threshold value for minimum bandwidth if the maximum average bandwidth falls below the"
}
] | 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. | [
"Configuring the Maximum and Minimum Bounds of the LSP’s Bandwidth"
] |
minimum-effective-aigp | minimum-effective-aigp <metric-offset>; | [edit fabric protocols bgp group name metric-out],
[edit logical-systems name protocols bgp group name metric-out],
[edit logical-systems name routing-instances name protocols bgp group name metric-out],
[edit logical-systems name tenants name routing-instances name protocols bgp group name metric-out],
[edit protocols... | To track the minimum effective AIGP metric. Effective AIGP is the AIGP value advertised with the route
plus the IGP cost to reach the nexthop. You can configure a minimum-aigp to prevent unnecessary
updation of route when effective-aigp changes past the previously known lowest value. | [
{
"name": "metric-offset",
"desc": "Metric offset for MED."
}
] | routing | Statement introduced in Junos OS Release 20.2R1. | [
"Example: Configuring the Accumulated IGP Attribute for BGP"
] |
minimum-hold-time | minimum-hold-time time-in-seconds; | [edit protocols bgp],
[edit protocols bgp group group-name ],
[edit protocols bgp group group-name neighborip-address ] | Prevent BGP session establishment toward BGP peers that attempt to negotiate a lower BGP session
hold-time than the configured minimum-hold-time. Such BGP peers will be rejected. BGP session
establishment attempt will be dropped and a notification message with unacceptable hold time error will be
sent to the neighbor. ... | [
{
"name": "time-in-seconds",
"desc": "Specify hold time in seconds."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 19.3. | [
"hold-time (Protocols BGP)"
] |
minimum-interval (BFD Liveness Detection) | minimum-interval milliseconds; | [edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) oam bfd-liveness-
detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) neighbor neighbor-
id oam bfd-liveness-detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn |... | Configure the minimum interval after which the local routing device transmits hello packets and then
expects to receive a reply from a neighbor with which it has established a BFD session. Optionally,
instead of using this statement, you can specify the minimum transmit and receive intervals separately
using the minimu... | [
{
"name": "milliseconds",
"desc": "Specify the minimum interval value for BFD liveliness detection."
}
] | 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 BFD for Layer 2 VPN and VPLS",
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection"
] |
minimum-interval (Liveness Detection) | minimum-interval milliseconds; | [edit protocols iccp peer liveness-detection] | Configure simultaneously the minimum interval at which the peer transmits liveness detection requests
and the minimum interval at which the peer expects to receive a reply from a peer with which it has
established a Bidirectional Forwarding Detection (BFD) session. Optionally, instead of using this
statement, you can s... | [
{
"name": "milliseconds",
"desc": "Specify the minimum interval value for Bidirectional Forwarding Detection (BFD)."
}
] | 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. | [] |
minimum-interval (PIM BFD Liveness Detection) | minimum-interval milliseconds; | [edit protocols pim interface (Protocols PIM) interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface (Protocols PIM) interface-
name bfd-liveness-detection] | Configure the minimum interval after which the local routing device transmits hello packets and then
expects to receive a reply from a neighbor with which it has established a BFD session. Optionally,
instead of using this statement, you can specify the minimum transmit and receive intervals separately
using the transm... | [
{
"name": "milliseconds",
"desc": "Minimum transmit and receive interval."
}
] | 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. | [
"Configuring BFD for PIM"
] |
minimum-interval (PIM BFD Transmit Interval) | minimum-interval milliseconds; | [edit protocols pim interface interface-name bfd-liveness-detection transmit-interval],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-
liveness-detection transmit-interval] | Configure the minimum interval after which the local routing device transmits hello packets to a
neighbor with which it has established a BFD session. Optionally, instead of using this statement, you
can configure the minimum transmit interval using the minimum-interval statement at the [edit protocols pim
interface in... | [
{
"name": "milliseconds",
"desc": "Minimum transmit interval value."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Configuring BFD for PIM"
] |
minimum-interval | minimum-interval milliseconds; | [edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server liveness-detection method bfd transmit-interval],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd tr... | Configure the minimum intervals at which the local routing device transmits hello packets and then
expects to receive a reply from a neighbor with which it has established a BFD session. This value
represents the minimum interval at which the local routing device transmits hello packets as well as the
minimum interval ... | [
{
"name": "milliseconds",
"desc": "Specify the minimum interval value for BFD liveliness detection."
}
] | 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"
] |
minimum-links (candidate-uplink-port-profile) | minimum-links link-count; | [edit policy-options satellite-policies candidate-uplink-port-profile profile-name]
[edit policy-options satellite-policies candidate-uplink-port-profile profile-name term term-
name from] | Configures the minimum number of active uplink ports a satellite device must have. If a satellite device
has fewer than this number of active uplink ports, uplink failure detection shuts down its extended
ports.
Default
The default number of minimum links is 1. | [
{
"name": "link-count",
"desc": "Specifies the minimum number of active uplink ports a satellite device must have. Valid"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
minimum-links (Interfaces) | minimum-links number; | [edit interfaces interface-name redundant-ether-
options] | For redundant Ethernet interfaces configured as 802.3ad redundant Ethernet interface link aggregation
groups (LAGs) in a chassis cluster only, set the required minimum number of physical child links on the
primary node that must be working to prevent the interface from being down. Interfaces configured as
redundant Eth... | [
{
"name": "number",
"desc": "For redundant Ethernet interface link aggregation group links, specify the number of physical"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement added in Release 10.1 of Junos OS. | [] |
minimum-links | minimum-links number; | [edit interfaces aex aggregated-ether-options] | For aggregated Ethernet, SONET/SDH, multilink, link services, and voice services interfaces only, set the
minimum number of links that must be up for the bundle to be labeled up.
(T Series, MX Series, PTX Series routers) You cannot configure the minimum number of links and the
minimum bandwidth of an aggregated Ethern... | [
{
"name": "number",
"desc": "Number of links."
}
] | 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 Aggregated Ethernet Minimum Links",
"Configuring Aggregated SONET/SDH Interfaces",
"Configuring Aggregated Ethernet Links (CLI Procedure)",
"Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis",
"Access Switch and an EX4200 Virtual Chassis Distribution ... |
minimum-priority | minimum-priority value; | [edit services dynamic-flow-capture capture-group client-name control-source identifier] | Specify the minimum priority for the control source. | [
{
"name": "value",
"desc": "Minimum priority value; if not specified, defaults to 0."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring the Control Source"
] |
minimum-quality | minimum-quality; | [edit chassis synchronization output interfaces external],
[edit chassis synchronization output interfaces (external-0/0 | external-1/0)],
[edit chassis synchronization]
Hierarchy level [edit chassis synchronization] added for ACX710 in Junos OS Release 20.2R1. | prc
Timing quality of a primary reference clock (option-1 only).
prs
Clock traceable to a primary reference source (option-2 only).
sec
Timing quality of an SDH equipment clock (option-1 only).
smc
Clock traceable to a self-timed SONET (option-2 only).
ssu-a
Timing quality of a type I or IV timeReceiver clock (option-1... | [] | 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. | [] |
minimum-receive-interval (BFD Liveness Detection) | minimum-receive-interval milliseconds; | [edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) oam bfd-liveness-
detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) neighbor neighbor-
id oam bfd-liveness-detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn |... | Configure the minimum interval after which the local routing device must receive a reply from a
neighbor with which it has established a BFD session. Optionally, instead of using this statement, you
can configure the minimum receive interval using the minimum-interval statement. | [
{
"name": "milliseconds",
"desc": "Specify the minimum receive interval value."
}
] | 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.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Configuring BFD for Layer 2 VPN and VPLS",
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection"
] |
minimum-receive-interval (Liveness Detection) | minimum-receive-interval milliseconds; | [edit protocols iccp peer liveness-detection] | Configure the minimum interval at which the peer must receive a reply from a peer with which it has
established a Bidirectional Forwarding Detection (BFD) session. | [
{
"name": "milliseconds",
"desc": "Specify the minimum interval value."
}
] | 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. | [] |
minimum-receive-interval (Protocols PIM) | minimum-receive-interval milliseconds; | [edit protocols pim interface (Protocols PIM) interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface (Protocols PIM) interface-
name bfd-liveness-detection] | Configure the minimum interval after which the local routing device must receive a reply from a
neighbor with which it has established a BFD session. Optionally, instead of using this statement, you
can configure the minimum receive interval using the minimum-interval statement at the [edit protocols pim
interface inte... | [
{
"name": "milliseconds",
"desc": "Minimum receive interval."
}
] | 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. | [
"Configuring BFD for PIM"
] |
minimum-receive-interval | minimum-receive-interval milliseconds; | [edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd],
[edit forwarding-options dhcp-relay liveness-detection method bfd], [edit forwarding-options
dhcp-relay dhcpv6 liveness-detection method bfd],
[edit system services dhc... | Configure the minimum interval at which the local routing device (or switch) must receive a reply from a
neighbor with which it has established a BFD session. | [
{
"name": "milliseconds",
"desc": "Specify the minimum receive interval value."
}
] | 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"
] |
minimum-retransmission-timeout (L2TP Tunnel) | minimum-retransmission-timeout seconds; | [edit services l2tp tunnel] | Configure the minimum (initial) interval that the LAC or the LNS waits for a response after transmitting
an L2TP control message to a peer. If no response has been received by the time the period expires, the
message is retransmitted. The timeout period is doubled for each retransmission until the maximum of
16 seconds... | [
{
"name": "seconds",
"desc": "Minimum interval before initial retransmission."
}
] | 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. | [
"L2TP for Subscriber Access Overview",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces"
] |
minimum-wait-time | minimum-wait-time seconds; | [edit forwarding-options helpers bootp],
[edit forwarding-options helpers bootp interface (interface-name | interface-group)] | To set the minimum allowed number of seconds in the secs field of the BOOTP message, include the
minimum-wait-time statement. This setting configures a minimum number of seconds since the client
sent its first BOOTP request. BOOTP messages that have a smaller number in the secs field than the
allowed minimum are not fo... | [
{
"name": "seconds",
"desc": "Minimum wait time the BOOTP client has waited before packets are forwarded. Range: 0 to 30,000 Default: 0"
}
] | 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"
] |
minor | minor {
threshold threshold-value;
action (chassis error) {
alarm;
disable-pfe;
get-state;
log;
offline;
reset;
}
} | [edit chassis fpc slot-number error ],
[edit chassis] | Severity level of the error. An error that results in the loss of a single packet but is fully recoverable is a
minor error. The severity level of an error cannot be configured by a user.
The other statements are explained separately. | [] | interface
To view this statement in the configuration.
interface-control
To add this statement to the configuration. | Statement introduced for PTX Series routers in Junos OS Release 13.3.
Statement introduced for MX240, MX480, MX960, and MX2020 routers in Junos OS Release 14.2. | [
"Fabric Resiliency",
"Managing Errors"
] |
minor-event (Process) | minor-event {
threshold process name memory-limit value ;
action snmp-trap;
} | [edit system monitor memory process] | Indicates a non-critical event that, if left unchecked, may cause an interruption in service or degradation
in performance but does not significantly affect the device. You can specify the process threshold value
for specific processes and their memory limit. When the threshold is crossed, you can configure the
action ... | [
{
"name": "threshold",
"desc": "Specifies the process threshold level for a minor event. You must specify the process name and the memory limit for the process. memory-limit - Specifies the permissible memory limit for the process after which the minor event is triggered. Range: 1 through 65535 MB"
},
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.1. | [
"System Log Overview",
"System Log Explorer"
] |
minor-event (System) | minor-event {
threshold swap-usage value ;
action snmp-trap ;
} | [edit system monitor memory system] | Indicates a non-critical event that, if left unchecked, may cause an interruption in service or degradation
in performance but does not significantly affect the device. You can monitor the swap usage and specify
the threshold for swap space usage. Most devices have a swap partition that you can configure to
provide add... | [
{
"name": "threshold",
"desc": "Specifies the process threshold level for a minor event. You must specify the process name and the memory limit for the process."
},
{
"name": "swap-usage",
"desc": "Specifies the swap usage in percentage."
},
{
"name": "action",
"desc": "Specifies the... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.1. | [
"System Log Overview",
"System Log Explorer"
] |
mip-half-function | mip-half-function (none | default | explicit); | [edit protocols oam ethernet connectivity-fault-managementmaintenance-domain md-name],
[edit protocols oam ethernet connectivity-fault-managementmaintenance-association ma-name] | Specify the OAM Ethernet CFM maintenance domain MIP half functions.
NOTE: Whenever a MIP is configured and a bridge domain is mapped to multiple
maintenance domains or maintenance associations, it is essential that the mip-half-
function value for all maintenance domains and maintenance associations are the same. | [
{
"name": "none",
"desc": "Specify to not use the mip-half-function."
},
{
"name": "default",
"desc": "Specify to use the default mip-half-function."
},
{
"name": "explicit",
"desc": "Specify an explicit mip-half-function."
}
] | 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. | [
"Creating a Maintenance Domain"
] |
mirror-decrypt-traffic | mirror-decrypt-traffic {
interface interface-name;
only-after-secruity-policies-enforcement;
destination-mac-address mac-address;
} | [edit services ssl proxy profile profile-name] | Specify SSL decryption mirroring options to forward the copy of SSL decrypted traffic to an external
traffic collection device.
To use SSL decryption mirroring, configure the SSL decryption port mirroring interface on SRX Series
Firewall and MAC address of the of the external mirror traffic collector port in an SSL pro... | [
{
"name": "interface",
"desc": "SSL decryption port mirroring interface on SRX Series Firewall. This is an Ethernet interface on SRX Series Firewall through which the copy of the SSL decrypted traffic is forwarded to a mirror port."
},
{
"name": "only-after-secruity-",
"desc": ""
},
{
"n... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1 | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
mirror-filter (Security Forwarding Options) | mirror-filter filter-name {
destination-port port-number;
destination-prefix destination-prefix;
interface-in interface-name;
interface-out interface-name;
output (Security Forwarding Options) {
destination-mac mac-address;
interface interface-name;
}
protocol protocol;
s... | [edit security forwarding-options] | Configure a mirror filter for filtering X2 packets to be mirrored and sent to a packet analyzer.
As a network operator, you need a way to monitor X2 traffic to debug any handover issues across
eNodeBs. The mirror filter feature allows you to do that. Traffic coming out of an IPsec tunnel is
decrypted, mirrored and ana... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
mirror-flash-on-disk | mirror-flash-on-disk; | [edit system] | Configure the hard disk to automatically mirror the contents of the CompactFlash card. The hard disk
maintains a synchronized mirror copy of the CompactFlash card contents. Data written to the
CompactFlash card is simultaneously updated in the mirrored copy of the hard disk. If the CompactFlash
card fails to read data,... | [] | 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.
Statement deprecated for Junos OS with Upgraded FreeBSD in Junos OS Release 15.1.
NOTE: To determine which platforms run Junos OS with Upgraded FreeBSD, see the
table listing the platforms currently running Junos OS with upgraded FreeBSD in Release
Information for Juno... | [
"Configuring Automatic Mirroring of the CompactFlash Card on the Hard Drive"
] |
mirror-once | mirror-once; | [edit forwarding-options port-mirroring] | Configure the router to mirror packets only once. This feature is useful if you configure port mirroring on
both ingress and egress interfaces, which could result in the same packet being mirrored twice. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3 (MX Series routers only).
Support extended to M120 routers in Junos OS Release 9.5. | [
"Configuring Port Mirroring"
] |
mixed-rate-mode | mixed-rate-mode; | [edit chassis fpc slot-number pic pic-number mixed-rate-mode],
[edit chassis lcc number fpc slot-number pic pic-number mixed-rate-mode] | Configure the mixed-rate mode for the 24-port 10 Gigabit Ethernet PIC (PF-24XGE-SFPP) only. | [] | 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. | [
"Modes of Operation",
"Configuring Mixed-Rate Mode Operation"
] |
mka (MX Series) | mka {
bounded-delay;
key-server-priority priority-number;
must-secure;
should-secure;
transmit-interval interval;
eapol-address (pae | provider-bridge | lldp-multicast | destination unicast-address);
} | [edit security macsec connectivity-association connectivity-association-name] | Specify parameters for the MACsec Key Agreement (MKA) protocol. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
Option eapol-address introduced in Junos OS Release 18.3R1 for MX Series routers.
Option bounded-delay introduced in Junos OS Release 21.1R1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
mka | mka {
eapol-ethertype-profile eapol-profile-name;
key-server-priority priority-number;
must-secure;
transmit-interval interval;
} | [edit security macsec connectivity-association connectivity-association-name] | Specify parameters for the MACsec Key Agreement (MKA) protocol. You initially establish a MACsec-
secured link using a pre-shared key when you are using static CAK security mode to enable MACsec.
Once matching pre-shared keys are successfully exchanged, the MACsec Key Agreement (MKA)
protocol is enabled. The MKA protoc... | [
{
"name": "eapol-ethertype-profile eapol-profile-name",
"desc": "Apply the profile that sets a custom EtherType for Extensible Authentication Protocol over LAN (EAPoL) to MACsec packets."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced for SRX Series Firewalls in Junos OS Release 15.1X49-D60.
Option eapol-address introduced in Junos OS Release 18.3R1.
Option bounded-delay introduced in Junos OS Release 21.1R1.
Option eapol-ethertype-profile introduced in Junos OS Evolved Relea... | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)",
"Media Access Control Security (MACsec) over WAN"
] |
mld (Dynamic Profiles) | mld {
interfaceinterface-name {
(accounting | no-accounting);
disable;
group-limit limit;
group-policy;
group-threshold value;
immediate-leave;
log-interval seconds;
oif-map;
passive;
ssm-map ssm-map-name;
ssm-map-policy ssm-ma... | [edit dynamic-profiles profile-name protocols] | Configure interface-specific MLD values on dynamic interfaces.
You can configure MLD in a dynamic client profile or a dynamic service 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 10.1. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD"
] |
mld | mld {
accounting;
interface interface-name {
(accounting | no-accounting);
disable;
distributed;
group-limit limit;
group-policy [ policy-names ];
immediate-leave;
oif-map [ map-names ];
passive;
ssm-map ssm-map-name;
ssm-map-polic... | [edit logical-systems logical-system-name protocols],
[edit protocols] | Enable MLD on the router. MLD must be enabled for the router to receive multicast packets.
Default
MLD is disabled on the router. MLD is automatically enabled on all broadcast interfaces when you
configure Protocol Independent Multicast (PIM) or Distance Vector Multicast Routing Protocol
(DVMRP). | [] | 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 MLD"
] |
mld-snooping | mld-snooping {
vlan (vlan-name) {
evpn-ssm-reports-only;
immediate-leave;
interface (all | interface-name) {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group ip-a... | [edit bridge-domains bridge-domain-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols],
[edit routing-instances routing-instance-name protocols] | Enable and configure Multicast Listener Discovery (MLD) snooping. MLD snooping constrains IPv6
multicast traffic at Layer 2 by configuring Layer 2 LAN ports dynamically to forward IPv6 multicast
traffic only to those ports that want to receive it.
MLD is a protocol built on ICMPv6 and used by IPv6 routers and hosts to ... | [] | 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 MLD Snooping",
"Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN",
"Environment",
"Configuring MLD",
"Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)",
"Configuring MLD Snooping on a Switch VLAN with ELS Support (CLI Procedure)",
"C... |
mldp-inband-signalling (Protocols Multipoint LDP) | mldp-inband-signalling {
policy policy-name;
} | [edit logical-systems logical-system-name protocols pim],
[edit protocols pim] | Multipoint LDP (mLDP) in-band signalling lets you carry multicast traffic across an existing IP/MPLS
backbone, while avoiding the use of PIM in the provider core.
On the label-edge router (LER), enable PIM to use mLDP in-band signaling for the upstream neighbors
when the LER does not detect a PIM upstream neighbor. On ... | [] | 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.
Support added in Junos OS Release 18.2R1 for using this command in conjunction with distributed MLD
or distributed IGMP. | [
"No Link Title"
] |
mlfr-uni-nni-bundle-options | mlfr-uni-nni-bundle-options {
acknowledge-retries number;
acknowledge-timer milliseconds;
action-red-differential-delay (disable-tx | remove-link);
cisco-interoperability send-lip-remove-link-for-link-reject;
drop-timeout milliseconds;
fragment-threshold bytes;
hello-timer milliseconds;
... | [edit interfaces ls-fpc/pic/port:channel] | Configure link services interface management 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 Encapsulation for Link Services Physical Interfaces"
] |
mlfr-uni-nni-bundles-inline | mlfr-uni-nni-bundles-inline number; | [edit chassis fpc number pic number] | Specify the number of inline multilink frame relay user-to-network interface (UNI) and network-to-
network interface (NNI) bundles. | [
{
"name": "number",
"desc": "Specify the number of inline multilink frame relay UNI NNI bundles. Range: 1 through 255"
}
] | 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"
] |
mobile-edge session-scale | session-scale {
1m
250k
500k
750k
} | [edit services mobile-edge session-scale scale-option] | Set the session scaling profile for your mobile-edge configuration. | [
{
"name": "1m",
"desc": "Set the session scaling profile to 1 million sessions."
},
{
"name": "250k",
"desc": "Set the session scaling profile to 250,000 sessions."
},
{
"name": "500k",
"desc": "Set the session scaling profile to 500,000 sessions."
},
{
"name": "750k",
"d... | system | Statement introduced in Junos OS Release 23.4R1. | [
"Session Maintenance and Optimization"
] |
mobility | mobility {
user-plane;
sgw;
} | [edit chassis fpc fpc-slot pfe pfe-id forwarding-packages] | Specify the forwarding package that the Packet Forwarding Engines associated with mobility must use.
NOTE:
•
You must include every Packet Forwarding Engine configured with the user-plane
forwarding package at the [edit unified-edge gateways user-plane gateway-name system
anchor-pfes] hierarchy level on the broadband ... | [
{
"name": "user-plane",
"desc": "Configure the router as a gateway GPRS support node (GGSN) or as a Packet Data Network Gateway (P-GW) or as an SAEGW-U."
},
{
"name": "sgw",
"desc": "Configure the router as a Serving Gateway (S-GW)."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced for Junos Multi-Acess User Plane in Junos OS Release 19.4R1.
ggsn-pgw option deprecated and replaced with user-plane option in Junos OS Release 20.4R1. | [] |
mode (Dynamic Profiles) | mode loose; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family inet
rpf-check] | Check whether the packet has a source address with a corresponding prefix in the routing table. If a
corresponding prefix is not found, unicast reverse path forwarding (RPF) loose mode does not accept the
packet. Unlike strict mode, loose mode does not check whether the interface expects to receive a packet
with a spec... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Unicast RPF Strict Mode",
"Unicast RPF in Dynamic Profiles for Subscriber Interfaces"
] |
mode (ike) | mode (aggressive | main); | [edit services ipsec-vpn ike policy policy-name] | Define an IKE policy mode.
Default
main | [
{
"name": "aggressive",
"desc": "Takes half the number of messages of main mode, has less negotiation power, and does not"
},
{
"name": "main",
"desc": "Uses six messages, in three peer-to-peer exchanges, to establish the IKE SA. These three steps"
}
] | 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. | [
"Configuring IKE Policies"
] |
mode (IKE) | mode (aggressive | main); | [edit security ike policy ike-peer-address] | Define the IKE policy mode.
NOTE: IKEv2 protocol does not negotiate using mode configuration.
Default
main | [
{
"name": "aggressive",
"desc": "Take half the number of messages of main mode, has less negotiation power, and does not"
},
{
"name": "main",
"desc": "Use six messages, in three peer-to-peer exchanges, to establish the IKE SA. These three steps"
}
] | 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. | [
"Configuring an IKE Policy for Preshared Keys"
] |
mode (Interfaces) | mode (strict | loose); | [edit interfaces interface-name unit logical-unit-number family (inet | inet6) rpf-check],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family (inet | inet6) rpf-check] | Check whether the packet has a source address with a corresponding prefix in the routing table. If a
corresponding prefix is not found, unicast reverse path forwarding (RPF) loose mode does not accept the
packet. Unlike strict mode, loose mode does not check whether the interface expects to receive a packet
with a spec... | [] | 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 Unicast RPF Strict Mode"
] |
mode (IPsec) | mode (transport | tunnel); | [edit security ipsec security-association name] | Define the mode for the IPsec security association.
Default
tunnel | [
{
"name": "transport",
"desc": "Protect traffic when the communication endpoint and cryptographic endpoint are the same."
},
{
"name": "tunnel",
"desc": "Protect traffic using preshared keys with IKE to authenticate peers or digital certificates with"
}
] | 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. | [
"Example: Using IPsec to Protect BGP Traffic",
"Configuring IPsec Tunnel Mode"
] |
mode (Multicast VLAN Registration) | mode (proxy | transparent); | [edit protocols igmp-snooping vlan vlan-name data-forwarding receiver] | Configure the operating mode for a Multicast VLAN Registration (MVR) receiver VLAN.
A multicast VLAN (MVLAN) forwards multicast streams to interfaces on other VLANs that are
configured as MVR receiver VLANs for that MVLAN, and can operate in either of two modes,
transparent or proxy. The mode setting affects how IGMP r... | [
{
"name": "transparent",
"desc": "MVR operates in transparent mode if this option is configured (and is also the default if no mode is configured). In transparent mode, IGMP reports are sent out from the device in the context of the MVR receiver VLAN. IGMP join and leave messages received on MVR receiver VL... | 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.
Support added in Junos OS Release 18.4R1 for EX2300 and EX3400 switches. | [
"Understanding Multicast VLAN Registration",
"Configuring Multicast VLAN Registration on EX Series Switches"
] |
mode (Next Gen Services Service-Set System Logging) | mode {
event ;
stream stream-name;
} | [edit services services-set name syslog] | Mode in which the system message logger sends messages | [
{
"name": "event",
"desc": "Send messages to a file on the local routing engine"
},
{
"name": "stream",
"desc": "Send messages to one or more remote log servers. Each remote server requires its own stream."
},
{
"name": "stream-event",
"desc": "Process security logs in both forwardin... | system | Support introduced in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240,
MX480 and MX960 with the MX-SPC3 services card. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
mode (Protocols DVMRP) | mode (forwarding | unicast-routing); | [edit logical-systems logical-system-name protocols dvmrp interface interface-name],
[edit protocols dvmrp interface interface-name] | Configure DVMRP for multicast traffic forwarding or unicast routing. | [
{
"name": "forwarding",
"desc": "DVMRP performs unicast routing as well as multicast data forwarding."
},
{
"name": "unicast-routing",
"desc": "DVMRP performs unicast routing only. To forward multicast data, you must configure"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | NOTE: Distance Vector Multicast Routing Protocol (DVMRP) was deprecated in Junos
OS Release 16.1. Although DVMRP commands continue to be available and configurable
in the CLI, they are no longer visible and are scheduled for removal in a subsequent
release.
Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring DVMRP to Announce Unicast Routes"
] |
mode (Protocols MSDP) | mode (mesh-group | standard); | [edit logical-systems logical-system-name protocols msdp group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols msdp
group group-name],
[edit protocols msdp group group-name],
[edit routing-instances routing-instance-name protocols msdp group group-name] | Configure groups of peers in a full mesh topology to limit excessive flooding of source-active messages
to neighboring peers. The default flooding mode is standard.
Default
If you do not include this statement, default flooding is applied. | [
{
"name": "mesh-group",
"desc": "Group of peers that are mesh group members."
},
{
"name": "standard",
"desc": "Use standard MSDP source-active flooding rules."
}
] | 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 with Active Source Limits and Mesh Groups"
] |
mode (Protocols PIM) | mode (bidirectional-sparse | bidirectional-sparse-dense | dense | sparse | sparse-dense); | [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-i... | Configure the PIM mode on the interface. | [
{
"name": "bidirectional-sparse",
"desc": "Use if all multicast groups are operating in bidirectional, sparse, or SSM mode."
},
{
"name": "bidirectional-sparse-dense",
"desc": "Use if multicast groups, except those that are specified in the dense-groups"
},
{
"name": "dense",
"desc":... | 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.
bidirectional-sparse and bidirectional-sparse-dense options introduced in Junos OS Release 12.1. | [
"Configuring PIM Dense Mode Properties",
"Configuring PIM Sparse-Dense Mode Properties",
"Example: Configuring Bidirectional PIM"
] |
mode (QFX Series) | mode active-active ; | [edit interfaces aggregated-ether-options mc-ae] | Configure the multichassis link aggregation group (MC-LAG) to be in active-active mode. In active-active
mode, all of the members of the MC-LAG will be active on both routing or switching devices. Only
active-active mode is supported at this time. | [
{
"name": "active-active",
"desc": "Specify that all of the members of the MC-LAG will be active on both routing or switching devices."
}
] | 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. | [] |
mode (RFC 2544 Benchmarking Tests) | mode (initiate-and-terminate | reflect); | [edit services monitoring rfc2544 tests test-name test-name] | Specify the test mode for the packets that are sent during the benchmarking test. | [
{
"name": "initiate-and-terminate",
"desc": "(Most ACX routers, except for the ACX5448, ACX5048, and ACX5096) Initiate and terminate the test on the chosen service (IPv4 or Ethernet). The ACX7100, ACX7509, ACX7024, and ACX7024X devices support this mode only for an IPv4 service."
},
{
"name": "refle... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3.
Statement introduced in Junos OS Evolved Release 21.1R1 for reflect mode only.
initiate-and-terminate mode introduced in Junos OS Evolved Release 23.4R1. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"RFC 2544-Based Benchmarking Tests Overview"
] |
mode (Security Forwarding Options) | mode (drop | flow-based | packet-based); | [edit security forwarding-options family inet6] | Specify forwarding options for IPv6 traffic. | [
{
"name": "drop",
"desc": "Drop IPv6 packets. This is the default setting."
},
{
"name": "flow-based",
"desc": "Perform flow-based packet forwarding."
},
{
"name": "packet-based",
"desc": "Perform simple packet forwarding."
},
{
"name": "No",
"desc": ""
},
{
"name... | security—To view this in the configuration.
security-control—To add this to the configuration. | Support on SRX Series Firewalls for flow-based mode for family inet6 added in Junos OS Release 10.2. | [
"Understanding Traffic Processing on Security Devices"
] |
mode (Security Group VPN) | mode (aggressive | main); | [edit security group-vpn member ike policy policy-name]
[edit security group-vpn server ike policy policy-name] | Define the mode used for Internet Key Exchange (IKE) Phase 1 negotiations. Use aggressive mode only
when you need to initiate an IKE key exchange without ID protection, as when a peer unit has a
dynamically assigned IP address. Group VPNv2 is supported on SRX300, SRX320, SRX340, SRX345,
SRX550HM, SRX1500, SRX4100, SRX4... | [
{
"name": "aggressive",
"desc": "Aggressive mode."
},
{
"name": "main",
"desc": "Main mode. Main mode is the recommended key-exchange method because it conceals the"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. Support for group-vpn hierarchies added in Junos OS
Release 10.2. | [
"Group VPNv2 Overview"
] |
mode (Security Log) | mode (event | stream | stream-event) | [edit security log]
[edit logical-systems name security log]
[edit tenants tenant-name security log] | Set the mode of logging (event for traditional system logging or stream for streaming security logs
through a revenue port to a server). | [
{
"name": "event",
"desc": "Process security logs in the control plane."
},
{
"name": "stream",
"desc": "Process security logs directly in the forwarding plane."
},
{
"name": "stream-event",
"desc": "Process security logs in the control and forwarding plane."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
The [edit logical-systems name security log] hierarchy level introduced in Junos OS Release 18.2R1.
The [edit tenants tenant-name security log] hierarchy level introduced in Junos OS Release 18.3R1.
stream-event option is introduced in Junos OS Release 20.2R1 for SRX Serie... | [] |
mode (Traffic Manager) | mode traffic-manager-mode; | [edit chassis fpc slot-number pic pic-number traffic-manager],
[edit chassis lcc number fpc slot-number pic pic-number traffic-manager]
[edit chassis fpc slot-number pic pic-number port port-number traffic-manager], (MX80 and MX104
routers only) | Enable shaping on an L2TP session. | [
{
"name": "traffic-manager-mode",
"desc": "Configure CoS traffic manager mode of operation on this interface. This option has"
},
{
"name": "the following suboptions:",
"desc": ""
},
{
"name": "egress-only",
"desc": "Enable CoS queuing and scheduling on the egress side for the PIC th... | 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. | [
"Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces"
] |
mode | mode (p2p | shared); | [edit logical-systems logical-system-name protocols (mstp | rstp | vstp) interface interface-name],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp | vstp) interface... | For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol
(VSTP), or Multiple Spanning Tree Protocol (MSTP), configures the link mode to identify point-to-point
links.
NOTE: For EX4300 switches, the interfaces operate in full-duplex mode only.
Default
When the link is configured... | [
{
"name": "p2p",
"desc": "The link is point to point."
},
{
"name": "shared",
"desc": "The link is shared media."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding Spanning-Tree Instance Interfaces",
"Understanding STP",
"Understanding VSTP",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Configuring Faster Convergence and Network Stability on ELS Switches with RSTP",
"Example: Faster Convergence and Improved Network... |
modem-options | modem-options {
dialin (console | routable);
init-command-string initialization-command-string;
} | [edit interfaces umd0] | For J Series Services Routers, configure a USB port to act as a USB modem.
The remaining statement is explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [] |
modulation-format | modulation-format (qpsk | 8qam | 16qam); | [edit interfaces interface-name optics-options] | Specify the modulation format. | [
{
"name": "qpsk",
"desc": "Quadrature Phase Shift Keying modulation format."
},
{
"name": "8qam",
"desc": "8 quadrature amplitude modulation format."
},
{
"name": "16qam",
"desc": "16 quadrature amplitude modulation."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Configuring Link Down Notification for Optics Options Alarm or Warning",
"100-Gigabit Ethernet OTN Options Configuration Overview"
] |
moduli | moduli {
type name;
refresh frequency;
count count;
} | [edit system services ssh] | Defines the Diffie-Hellman prime moduli configuration for group exchange. The configuration
dynamically generates prime moduli for the existing DH group exchange algorithms such as group-
exchange-sha1 and group-exchange-sha2. The qbufd process is responsible for managing the moduli generation.
If you don't configure t... | [
{
"name": "moduli type name",
"desc": "Specify the name of the prime modulus. Values: designer or safe."
},
{
"name": "refresh frequency",
"desc": "Specify the refresh frequency for generating the moduli periodically. Values: monthly or weekly."
},
{
"name": "count count",
"desc": "(... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1. | [
"Quantum Buffer for SSH"
] |
mofrr-asm-starg (Multicast-Only Fast Reroute in a PIM Domain) | mofrr-asm-starg; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast stream-protection],
[edit logical-systems logical-system-name routing-options multicast stream-protection],
[edit routing-instances routing-instance-name routing-options multicast stream-protection],
[edit routi... | Enable mofrr-asm-starg to include any-source multicast (ASM) for (*,G) joins in the Multicast-only fast
reroute (MoFRR).
NOTE: mofrr-asm-starg applies to IP-PIM only. When enabled for group G, *,G will undergo
MoFRR as long as there is no S#,G for Group G. In other words, *,G MoFRR will cease
and any old states will b... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Multicast-Only Fast Reroute",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain on Switches",
"Example: Configuring Multicast-Only Fast Reroute in a Multipoint LDP Domain",
"mofrr-disjoint-upstream-only (Multi... |
Domain) | mofrr-disjoint-upstream-only; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast stream-protection],
[edit logical-systems logical-system-name routing-options multicast stream-protection],
[edit routing-instances routing-instance-name routing-options multicast stream-protection],
[edit routi... | When you configure multicast-only fast reroute (MoFRR) in a PIM domain, allow only a disjoint RPF (an
RPF on a separate plane) to be selected as the backup RPF path.
In a multipoint LDP MoFRR domain, the same label is shared between parallel links to the same
upstream neighbor. This is not the case in a PIM domain, whe... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Multicast-Only Fast Reroute",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain on Switches",
"Example: Configuring Multicast-Only Fast Reroute in a Multipoint LDP Domain"
] |
mofrr-no-backup-join (Multicast-Only Fast Reroute in a PIM Domain) | mofrr-no-backup-join; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast stream-protection],
[edit logical-systems logical-system-name routing-options multicast stream-protection],
[edit routing-instances routing-instance-name routing-options multicast stream-protection],
[edit routi... | When you configure multicast-only fast reroute (MoFRR) in a PIM domain, prevent sending join
messages on the backup path, but retain all other MoFRR functionality. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Multicast-Only Fast Reroute",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain on Switches",
"Example: Configuring Multicast-Only Fast Reroute in a Multipoint LDP Domain"
] |
mofrr-primary-path-selection-by-routing (Multicast-Only Fast Reroute) | mofrr-primary-path-selection-by-routing; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast stream-protection],
[edit logical-systems logical-system-name routing-options multicast stream-protection],
[edit routing-instances routing-instance-name routing-options multicast stream-protection],
[edit routi... | MoFRR is supported on both equal-cost multipath (ECMP) paths and non-ECMP paths. Unicast loop-
free alternate (LFA) routes need to be enabled to support MoFRR on non-ECMP paths. LFA routes are
enabled with the link-protection statement in the interior gateway protocol (IGP) configuration. When
you enable link protectio... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Multicast-Only Fast Reroute",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain on Switches",
"Example: Configuring Multicast-Only Fast Reroute in a Multipoint LDP Domain"
] |
monitor (Multinode High Availability) | monitor {
bfd-liveliness destination-ip-address {
interface interface-name;
routing-instance routing-instance-name;
session-type (multihop | singlehop);
src-ip src-ip;
}
interface name;
ip destination-ip-address {
routing-instan... | [edit chassis high-availability services-redundancy-group id-number] | Configure monitoring options for the Multinode High Availability setup. | [
{
"name": "bfd-liveliness",
"desc": "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 liveline... | interface | Statement introduced in Junos OS Release 20.4R1. | [
"Multinode High Availability Monitoring Options",
"Multinode High Availability"
] |
monitor ethernet delay-measurement | monitor ethernet delay-measurement
maintenance-domain md-name
maintenance-association ma-name
(one-way | two-way)
(remote-mac-address | mep remote-mep-id)
<count frame-count>
<local-mep mep-id>
<wait interval-seconds>
<priority 802.1p value>
<size>
<no-session-id-tlv>
<xml> | Start an ITU-T Y.1731 Ethernet frame delay measurement session between the specified local
connectivity fault management (CFM) maintenance association end point (MEP) and the specified
remote MEP, and display a summary of the frames exchanged in the measurement session. Frame delay
measurement statistics are stored at ... | [
{
"name": "maintenance-domain md-name",
"desc": "Name of an existing CFM maintenance domain."
},
{
"name": "maintenance-association ma-",
"desc": ""
},
{
"name": "name",
"desc": "Name of an existing CFM maintenance association."
},
{
"name": "one-way",
"desc": "Measuremen... | trace and maintenance
Output Fields
The monitor ethernet delay-measurement command displays different output at the CLI, depending on
whether you start a one-way or two-way frame delay measurement:
•
Table 82 on page 11292 lists the run-time output fields for the monitor ethernet delay-measurement one-
way command.
•
T... | Command introduced in Junos OS Release 9.5.
local-mep option introduced in Junos OS Release 15.1. | [] | |
monitor ethernet loss-measurement | monitor ethernet loss-measurement
maintenance-domain md-name
maintenance-association ma-name
(remote-mac-address | mep remote-mep-id)
<count frame-count>
<local-mep mep-id>
<wait interval-seconds>
<priority 802.1p value>
<no-session-id-tlv>
<xml> | Start an ITU-T Y.1731 Ethernet frame loss measurement session between the specified local
connectivity fault management (CFM) maintenance association end point (MEP) and the specified
remote MEP, and display a count of transmitted and received data frames between the pair of MEPs.
Frame loss measurement statistics are ... | [
{
"name": "maintenance-domain",
"desc": ""
},
{
"name": "md-name",
"desc": "Name of an existing CFM maintenance domain."
},
{
"name": "maintenance-association ma-name",
"desc": "Name of an existing CFM maintenance association."
},
{
"name": "mep remote-mep-id",
"desc": "N... | trace and maintenance
Output Fields
Table 84 on page 11298 lists the output fields for the monitor ethernet loss-measurement command and their
descriptions. Output fields are listed in the approximate order in which they appear.
Table 84: monitor ethernet loss-measurement output fields
Output Field Name
Output Field De... | Command introduced in Junos OS Release 11.1.
local-mep option introduced in Junos OS Release 15.1 | [
"ITU-T Y.1731 Ethernet Service OAM Overview",
"Junos OS Network Interfaces Library for Routing Devices",
"CLI Explorer"
] | |
monitor ethernet synthetic-loss-measurement | monitor ethernet synthetic-loss-measurement
maintenance-domain md-name
maintenance-association ma-name
(remote-mac-address | mep remote-mep-id)
<count frame-count>
<local-mep mep-id>
<wait interval-milliseconds>
<priority 802.1p value>
<size>
<xml> | (MX Series routers) Start an ITU-T Y.1731 Ethernet synthetic loss measurement (ETH-SLM) session
between the specified local connectivity fault management (CFM) maintenance association end point
(MEP) and the specified remote MEP, and display a summary of the frames exchanged in the
measurement session. ETH-SLM (also ca... | [
{
"name": "maintenance-domain md-name",
"desc": "Name of an existing CFM maintenance domain."
},
{
"name": "maintenance-association ma-",
"desc": ""
},
{
"name": "name",
"desc": "Name of an existing CFM maintenance association."
},
{
"name": "mep remote-mep-id",
"desc": "... | trace and maintenance
Output Fields
The monitor ethernet synthetic-loss-measurement command displays different output at the CLI, depending on
when you start a synthetic frame loss measurement:
•
Table 85 on page 11305 lists the run-time output fields for the monitor ethernet synthetic-loss-
measurement command.
Output... | Command introduced in Junos OS Release 13.2.
local-mep option introduced in Junos OS Release 15.1 | [] | |
monitor interface error | monitor interface error | You can use the monitor interface error command to display errors in packet headers that are transmitted
through all network interfaces. Use the following options at the end of the command for more specific
information. | [
{
"name": "interface-name",
"desc": "(Optional) Displays packet header errors for a specified interface or interfaces. If an interface is not specified, all interfaces are monitored."
}
] | view
Output Fields
Table 1 lists the output fields for the monitor interface error command.
Table 86: monitor interface error Output Fields
Field Name
Field Description
CRC Errors
Displays the number of CRC errors on the selected interfaces since you started
monitoring.
Corr errors
Displays the number of FEC corrected ... | Command introduced in Junos OS Evolved Release 22.2R1. | [
"Monitor Interfaces (overview)"
] | |
monitor interface | monitor interface
<interface-name | traffic <detail>> | With the traffic option, displays the interface description configured at
the [edit interfaces interface-name] hierarchy level.
detail
Input Errors
Sum of incoming frame aborts and FCS errors.
All levels
Input Drops
Number of packets dropped by the input queue of the I/O Manager
ASIC. If the interface is saturated, thi... | [
{
"name": "none",
"desc": "Display real-time statistics for all interfaces."
},
{
"name": "detail",
"desc": "(Optional) With traffic option only, display detailed output."
},
{
"name": "interface-name",
"desc": "(Optional) Display real-time statistics for the specified interface. In ... | trace
Output Fields
Table 89 on page 11313 describes the output fields for the monitor interface command. Output fields are
listed in the approximate order in which they appear.
Table 89: monitor interface Output Fields
Field Name
Field Description
Level of Output
router1
Hostname of the router.
All levels
Seconds
How ... | Command introduced before Junos OS Release 7.4. | [] | |
monitor label-switched-path | monitor label-switched-path lsp-name
<logical-system (logical-system-name)> | Display the real-time status of the specified RSVP label-switched path (LSP). You can also use this
command to monitor LSPs configured within logical systems. | [
{
"name": "logical-system ( logical-system-name)",
"desc": "(Optional) Perform this operation on all logical systems or on a particular logical system."
},
{
"name": "lsp-name",
"desc": "Name of the LSP. Additional Information You can track the amount of traffic traversing an RSVP LSP and observ... | trace
Output Fields
Table 91 on page 11331 describes the output fields for the monitor label-switched-path command. Output
fields are listed in the approximate order in which they appear.
Table 91: monitor label-switched-path Output Fields
Field Name
Field Description
(1)
Displays the following information:
•
hostname... | Command introduced before Junos OS Release 7.4.
Logical system support introduced in Junos OS Release 9.4. | [] | |
monitor list (JDM) | monitor list | Show status of monitored files. | [] | View
Output Fields
Sample Output
monitor list
user@jdm> monitor list | Command introduced in Junos OS Release 17.4R1. | [] | |
monitor list | monitor list | Display the status of monitored log and trace files. | [] | trace
Output Fields
Table 92 on page 11335 describes the output fields for the monitor list command. Output fields are
listed in the approximate order in which they appear.
Table 92: monitor list Output Fields
Field Name
Field Description
monitor start
Indicates the file is being monitored.
"filename"
Name of the file ... | Command introduced before Junos OS Release 7.4. | [] | |
monitor mpls delay rsvp | monitor mpls delay rsvp lsp-name
<detail>
<count count>
<interval seconds>
<padding-size padding-size>
<traffic-class traffic-class> | Perform an on-demand delay measurement and display the measured values for associated bidirectional
MPLS ultimate hop popping (UHP) point-to-point label-switched paths (LSPs). | [
{
"name": "lsp-name",
"desc": "Name of the associated bidirectional MPLS UHP LSP for which the delay measurement is performed."
},
{
"name": "detail",
"desc": "(Optional) Display detailed output of the LSP delay measurement."
},
{
"name": "count count",
"desc": "(Optional) Specify th... | view
Output Fields
Table 93 on page 11338 describes the output fields for the monitor mpls delay rsvp command. Output
fields are listed in the approximate order in which they appear.
Table 93: monitor mpls delay rsvp Output Fields
Field Name
Field Description
Level of Output
Current two-way
channel delay
Sum of packet ... | Command introduced in Junos OS Release 14.2. | [
"Example: Configuring On-Demand Loss and Delay Measurement"
] | |
monitor mpls loss rsvp | monitor mpls loss rsvp lsp-name
<detail>
<bytes>
<count count>
<interval seconds>
<traffic-class traffic-class> | Perform an on-demand loss measurement and display the measured values for associated bidirectional
MPLS ultimate hop popping (UHP) point-to-point label-switched paths (LSPs). | [
{
"name": "lsp-name",
"desc": "Name of the associated bidirectional MPLS UHP LSP for which the loss measurement is performed."
},
{
"name": "detail",
"desc": "(Optional) Display detailed output of the LSP loss measurement."
},
{
"name": "bytes",
"desc": "(Optional) Specify the measur... | view
Output Fields
Table 94 on page 11344 describes the output fields for the monitor mpls loss rsvp command. Output fields
are listed in the approximate order in which they appear.
Table 94: monitor mpls loss rsvp Output Fields
Field Name
Field Description
Level of Output
Current forward loss
Difference between the cu... | Command introduced in Junos OS Release 14.2. | [
"Example: Configuring On-Demand Loss and Delay Measurement"
] | |
monitor mpls loss-delay rsvp | monitor mpls loss-delay rsvp lsp-name
<detail>
<bytes>
<count count>
<interval seconds>
<padding-size padding-size>
<traffic-class traffic-class> | Perform a simultaneous on-demand loss and delay measurement using combined loss and delay
messages, and display the measured values for associated bidirectional MPLS ultimate hop popping
(UHP) point-to-point label-switched paths (LSPs). | [
{
"name": "lsp-name",
"desc": "Name of the associated bidirectional MPLS UHP LSP for which the delay measurement is performed."
},
{
"name": "detail",
"desc": "(Optional) Display detailed output of the LSP delay measurement."
},
{
"name": "bytes",
"desc": "(Optional) Specify the meas... | view
Output Fields
For output field descriptions, see the "monitor mpls loss rsvp" on page 11342 and "monitor mpls delay
rsvp" on page 11336 commands.
Sample Output
monitor mpls loss-delay rsvp count
user@host> monitor mpls loss-delay rsvp LSP-A count 2
(1)
Current forward loss : 0 packets
Current ... | Command introduced in Junos OS Release 14.2. | [
"Example: Configuring On-Demand Loss and Delay Measurement"
] | |
monitor pfe traffic interface | monitor pfe traffic interface interface-name
<absolute-sequence>
<brief | detail | extensive>
<byte-offset>
<count count>
<egress>
<egress-interface interface-name>
<ingress>
<inner-dmac | inner-dst-ipv4 | inner-smac | inner-src-ipv4>
<layer2-headers>
<no-domain-names>
<no-promiscuous>
<no-resolve>
<no-timestam... | Display packet headers or packets that are received and sent from the packet forwarding engine for
monitoring and verifying the functionality of on-box packet sniffing capabilities. | [
{
"name": "absolute-sequence",
"desc": "Display absolute TCP sequence numbers."
},
{
"name": "brief | detail | extensive",
"desc": "Display the specified level of output."
},
{
"name": "byte-offset",
"desc": "Display the specified level of output."
},
{
"name": "count count",... | interface—To view this statement in the configuration.
interface-control—To view this statement in the configuration.
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
monitor pfe traffic interface interface-name ingress outer-dmac destination MAC address... | Command introduced before Junos OS Release 24.4R1. | [] | |
monitor security flow file | monitor security flow file
<file-name>
<files number>
<match regular-expression>
<size maximum-file-size>
<(world-readable | no-world-readable)> | Configure options for the security flow monitoring output. | [
{
"name": "filename",
"desc": "Name of the file to receive the output of the monitoring operation. All output is saved in the /var/log/ directory."
},
{
"name": "files number",
"desc": "Maximum number of output files. If you specify a maximum number of files, you must also specify a maximum file... | trace
Output Fields
This command produces no output. | Command introduced in Junos OS Release 12.1X46-D10. | [
"Monitoring Security Flow Sessions Overview"
] | |
monitor security flow filter | monitor security flow filter filter-name
<conn-tag session-connection-tag>
<destination-port (port-range | protocol-name)>
<destination-prefix destination-prefix>
<interface interface-name>
<logical-system logical-system-name>
<protocol (protocol name | protocol number)>
<root-logical-system>
<source-port (port-range ... | Set security flow filters to define flow sessions that you want to monitor. A maximum of 64 filters is
supported at a time.
Defining the filters themselves does not trigger monitoring. You must explicitly use the monitor security
flow start command to enable monitoring. Once monitoring starts, any traffic that matches ... | [
{
"name": "filter filter-name",
"desc": "Specify a name for the filter. The filter name can contain letters, numbers, underscores (_) and hyphens (-) and can be up to 64 characters long."
},
{
"name": "conn-tag",
"desc": "Specify the session connection tag. The session connection tag uniquely id... | view | Command introduced in Junos OS Release 12.1X46-D10. The was updated in Junos OS Release
15.1X49-D70 with the addition of the conn-tag filter parameter. | [
"Monitoring Security Flow Sessions Overview"
] | |
monitor security flow start | monitor security flow start | Start the monitoring of security flow session. Once monitoring starts, any traffic that matches the
specified filters is saved in an output file in the var/log/ directory. At least one filter must be defined for
the monitoring to start.
Use the monitor security flow stop command to stop the monitoring of flow sessions. | [] | trace
Output Fields
This command produces no output. | Command introduced in Junos OS Release 12.1X46-D10. | [
"Monitoring Security Flow Sessions Overview"
] | |
monitor security flow stop | monitor security flow stop | Stop monitoring the security flow session. Use the monitor security flow start command to start the
monitoring of flow sessions. | [] | trace
Output Fields
This command produces no output. | Command introduced in Junos OS Release 12.1X46-D10. | [
"Monitoring Security Flow Sessions Overview"
] | |
monitor security packet-drop | monitor security packet-drop
<source-prefix>
<destination-prefix>
<source-port>
<destination-port>
<ingress-interface-name>
<protocol>
<logical-system-name>
<count-number> | Displays the packet-drop information without committing the configuration, which allows you to trace
and monitor the traffic flow. This command output is displayed on the screen until you press Ctrl+c or
until the security device collects the requested number of packet drops. The command includes various
filters to gen... | [
{
"name": "source-prefix",
"desc": "Display the packet drop information for the given source IP or source prefix address."
},
{
"name": "destination-prefix",
"desc": "Display the packet drop information for the given destination IP or source prefix address."
},
{
"name": "source-port",
... | view
Sample Output
monitor security packet-drop
When configuration is set to default IDP security policy, using the command set security idp idp-policy
IDP_Default rulebase-ips rule 1 then action drop-packet, the following type of output is displayed for monitor
security packet-drop command.
user@host> monitor security... | Command introduced in Junos OS Release 21.1R1.
Signature added to packet drop reason in Junos OS Release 21.2R2. | [] | |
monitor start (JDM) | monitor start file-name | Start displaying the system log or trace file and additional entries being added to those files.
Additional Information
Log files are generated by the routing protocol process or by system logging. | [] | View
Output Fields
Table 95 on page 11372 describes the output fields for the monitor start command. Output fields are
listed in the approximate order in which they appear.
Table 95: monitor start Output Fields
Field Name
Field Description
***filename ***
Name of the file from which entries are being displayed.
Date a... | Command introduced in Junos OS Release 17.4R1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.