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 |
|---|---|---|---|---|---|---|---|
maximum-length (Origin Validation for BGP) | maximum-length prefix-length {
origin-autonomous-system as-number {
validation-state (invalid | valid);
}
} | [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation static record destination],
[edit logical-systems logical-system-name routing-options validation static record destination],
[edit routing-instances instance-name routing-options validation static record destination],
... | Configure the maximum prefix-length for a route validation (RV) record. This is a required statement. | [
{
"name": "prefix-length",
"desc": "Maximum prefix-length range for a given RV entry."
}
] | 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. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
maximum-links | maximum-links maximum-links-limit; | [edit chassis aggregated-devices] | Configure the maximum links limit for aggregated devices. Note that for MX Series routers, to set a
range of 32 or 64 the router must be running in Enhanced IP mode, which is only supported for Trio-
based MPCs and multiservice DPCs (MS-DPCs). For more information on Enhanced IP mode, Network
Services Mode Overview.
Th... | [
{
"name": "maximum-links-limit",
"desc": "Maximum links limit for aggregated devices. Range: 16, 32, 64 default: 16"
}
] | 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. | [
"Network Services Mode Overview",
"Configuring Junos OS for Supporting Aggregated Devices",
"Configuring an Aggregated Ethernet Interface"
] |
maximum-message-length | maximum-message-length number; | [edit logical-systems name security alg dns],
[edit logical-systems name tenants name security alg dns],
[edit security alg dns],
[edit services alg dns],
[edit tenants name security alg dns] | Configure the maximum-message-length parameter to specify the maximum DNS message length. | [
{
"name": "number",
"desc": "Maximum length in bytes of a single DNS message."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
maximum-neighbor-reconnect-time | maximum-neighbor-reconnect-time seconds; | [edit protocols ldp graceful-restart],
[edit logical-systems logical-system-name protocols ldp graceful-restart],
[edit routing-instances routing-instance-name protocols ldp graceful-restart] | Specify the maximum length of time allowed to reestablish connection from a restarting neighbor. | [
{
"name": "seconds",
"desc": "Maximum time allowed for reconnection."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Configuring Graceful Restart Options for LDP"
] |
maximum-neighbor-recovery-time | maximum-neighbor-recovery-time seconds; | [edit logical-systems logical-system-name protocols ldp graceful-restart],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ldp graceful-restart],
[edit protocols ldp graceful-restart],
[edit routing-instances routing-instance-name protocols ldp graceful-restart] | Specify the maximum amount of time to wait before giving up an attempt to gracefully restart. | [
{
"name": "seconds",
"desc": "Configure the maximum recovery 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 7.4. Statement changed from maximum-recovery-time to
maximum-neighbor-recovery-time in Junos OS Release 9.1. | [
"Configuring Recovery Time and Maximum Recovery Time",
"Configuring Graceful Restart Options for LDP"
] |
maximum-packet-length | maximum-packet-length bytes; | [edit forwarding-options analyzer analyzer-name input],
[edit forwarding-options port-mirroring input],
[edit forwarding-options port-mirroring instance instance-name input],
[edit forwarding-options sampling input],
[edit forwarding-options sampling instance instance-name input] | Set the maximum packet length to be used for port mirroring or traffic sampling. Packets longer than the
maximum are truncated. This statement cannot be used with inline flow monitoring ([edit forwarding-
options sampling instance instance-name family (inet | inet6) output inline-jflow] .
NOTE: For MX Series routers wi... | [
{
"name": "bytes",
"desc": "Maximum length (in bytes) of the mirrored packet or the sampled packet."
}
] | 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.
For MX Series routers except the MX 80, support at the [edit forwarding-options analyzer analyzer-name
input] hierarchy level was introduced in Junos OS Release 14.1 | [
"Configuring Port Mirroring",
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
maximum-paths | maximum-paths path-limit <log-interval seconds> <log-only | threshold value>; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Configure a limit for the number of routes installed in a routing table based upon the route path.
NOTE: The maximum-paths statement is similar to the maximum-prefixes statement. The
maximum-prefixes statement limits the number of unique destinations in a routing instance.
For example, suppose a routing instance has th... | [
{
"name": "log-interval seconds",
"desc": "(Optional) Minimum time interval (in seconds) between log messages."
},
{
"name": "log-only",
"desc": "(Optional) Sets the route limit as an advisory limit. An advisory limit triggers only a warning, and"
},
{
"name": "path-limit",
"desc": "... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Limiting the Number of Paths and Prefixes Accepted from CE Routers in Layer 3 VPNs"
] |
maximum-pending-reqs-limit | maximum-pending-reqs-limit number; | [edit access radius network-element name] | Configure the maximum number of requests that can be queued to the network element. When the
pending-request queue is full, any additional requests are dropped. | [
{
"name": "number",
"desc": "Maximum number of pending requests. Range: 512 through 8192"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Network Elements",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
maximum-pending-requests (Diameter) | maximum-pending-requests requests; | [edit access diameter applications pcc-gx] | Configure the maximum number of pending requests parameter for the Diameter application. | [
{
"name": "requests",
"desc": "Maximum number of pending requests. Range: 1000 through 65,535 Default: 20,000"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
maximum-power (Interface) | maximum-power watts; | [edit poe interface (all | all-extended | interface-name)] | Configure the maximum amount of power that the switch can supply to the PoE port. The maximum
power configuration is valid when the PoE power management is in static mode. If PoE power
management is in class mode, which is the default, the maximum power configuration will have no effect
on the power allocation. For mor... | [
{
"name": "watts",
"desc": "The maximum power in watts that can be supplied to the ports."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring PoE Interfaces on EX Series Switches",
"Configuring Power over Ethernet in a Junos Fusion"
] |
maximum-power (PoE) | maximum-power watts; | [edit poe interface (all | interface-name)] | Maximum amount of power that can be supplied to the port.
Default
15.4 W | [
{
"name": "Watts",
"desc": "The maximum number of watts that can be supplied to the port."
},
{
"name": "Range",
"desc": "0 through 15.4"
},
{
"name": "Default",
"desc": "15.4 W"
}
] | 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. | [] |
maximum-prefixes | maximum-prefixes prefix-limit <log-interval seconds> <log-only | threshold percentage>; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Configure a limit for the number of routes installed in a routing table based upon the route prefix.
Using a prefix limit, you can curtail the number of prefixes received from a CE router in a VPN. Prefix
limits apply only to dynamic routing protocols and are not applicable to static, programmed, or interface
routes.
... | [
{
"name": "log-interval seconds",
"desc": "(Optional) Minimum time interval (in seconds) between log messages."
},
{
"name": "log-only",
"desc": "(Optional) Sets the prefix limit as an advisory limit. An advisory limit triggers only a warning,"
},
{
"name": "prefix-limit",
"desc": "M... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Limiting the Number of Paths and Prefixes Accepted from CE Routers in Layer 3 VPNs"
] |
maximum-rps | maximum-rps limit; | [edit logical-systems logical-system-name protocols pim rp embedded-rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp embedded-rp],
[edit protocols pim rp embedded-rp],
[edit routing-instances routing-instance-name protocols pim rp embedded-rp] | Limit the number of RPs that the routing device acknowledges. | [
{
"name": "limit",
"desc": "Number of RPs."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring PIM Embedded RP for IPv6"
] |
maximum-send-window | maximum-send-window packets; | [edit services l2tp tunnel-group name] | Specify the size of the send window for L2TP tunnels, which limits the remote end’s receive window
size.
NOTE: This statement is not supported for L2TP LNS on MX Series routers. | [
{
"name": "packets",
"desc": "Maximum number of packets the send window can hold at one time."
}
] | 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 Window Size for L2TP Tunnels"
] |
maximum-sessions (L2TP) | maximum-sessions number; | [edit access profile profile-name client client-name],
[edit services l2tp],
[edit services l2tp sessions-limit-group],
[edit services l2tp tunnel],
[edit services l2tp tunnel-group group-name] | Specify the maximum number of L2TP sessions for the chassis, all tunnels, a tunnel group, a session limit
group, or a client. | [
{
"name": "number",
"desc": "Number of sessions allowed."
},
{
"name": "limit",
"desc": "Range: (Tunnel) 1 through 65,536"
}
] | 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. | [
"L2TP LAC Tunneling for Subscribers",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces",
"L2TP for Subscriber Access Overview"
] |
maximum-sessions (TDF Gateway) | maximum-sessions max-sessions; | [edit unified-edge gateways tdf gateway-name cac] | Configure the maximum number of TDF subscriber sessions that may be running. | [
{
"name": "max-sessions",
"desc": "Maximum number of TDF subscriber sessions, expressed in thousands. Range: 10 thousands through 5000 thousands"
}
] | 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 a TDF Gateway"
] |
maximum-sessions | maximum-sessions count; | [edit services rpm twamp server] | Configure the maximum number of allowed test sessions the server can have running at one time.
NOTE: The maximum number of test sessions running on the server at one time must be
greater than or equal to the maximum number of sessions the server can open on a
single client connection. | [
{
"name": "count",
"desc": "Maximum number of sessions."
}
] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
maximum-sessions-per-connection | maximum-sessions-per-connection count; | [edit services rpm twamp server] | Configure the maximum number of allowed sessions the server can open on a single client connection.
NOTE: The maximum number of test sessions running on the server at one time must be
greater than or equal to the maximum number of sessions the server can open on a
single client connection. | [
{
"name": "count",
"desc": "Maximum number of sessions."
}
] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
maximum-sessions-per-tunnel | maximum-sessions-per-tunnel number; | [edit access group-profile l2tp],
[edit access profile profile-name client client-name l2tp] | Configure the maximum sessions for a Layer 2 tunnel.
NOTE: This statement is not supported at the [edit access group-profile l2tp] hierarchy
level for L2TP LNS on MX Series routers. | [
{
"name": "number",
"desc": "Maximum number of sessions for a Layer 2 tunnel."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Layer 2 Tunneling Protocol (L2TP)",
"L2TP LNS Inline Service Interfaces"
] |
maximum-sessions-trap-percentage (TDF Gateway) | maximum-sessions-trap-percentage max-sessions-pct; | [edit unified-edge gateways tdf gateway-name cac] | Configure the trap threshold for the number of TDF subscriber sessions as a percentage of the
maximum number of sessions (maximum-sessions) that was configured at the [edit unified-edge gateways tdf
gateway-name cac] hierarchy level. If the number of subscriber sessions reaches the threshold, the SNMP
trap jnxScgSMSess... | [
{
"name": "max-sessions-pct",
"desc": "Percentage of the maximum number of TDF subscriber sessions. Range: 1 through 90"
}
] | 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 a TDF Gateway"
] |
maximum-subscribers | maximum-subscribers number; | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber] | Specify the maximum number of IP-based subscriber sessions that the TDF domain can support. | [
{
"name": "number",
"desc": "Maximum number of subscriber sessions allowed. Range: 100 thousands through 5000 thousands."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
maximum-subscribers | maximum-subscribers limit; | [edit system services extensible-subscriber-services] | Configure the maximum number of subscriber sessions supported at a time. | [
{
"name": "limit",
"desc": "Maximum number of subscribers. Range: 1 through 2000 Default: 1000"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
maximum-transactions | maximum-transactions number; | [edit services application-identification nested-application name signature name] | Set the maximum number of transactions required before a match is made. | [
{
"name": "number",
"desc": "Maximum number of transactions."
}
] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Application Identification for Nested Applications"
] |
maximum-transactions | maximum-transactions transactions-number; | [edit services application-identification] | Configure the maximum number of transactions matched by application identification for finalizing the
application.
Application classification does not terminate for applications that are transaction based such as
Facebook applications. To terminate the application classifications for such applications, you can choose
t... | [
{
"name": "maximum-transactions",
"desc": ""
},
{
"name": "transactions-number",
"desc": "Number of transaction results that can be considered before concluding the final result for application identification. Range: 0 through 25 Default: 5"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1 | [
"Application Identification"
] |
maximum-transmit-rate (Protocols IGMP) | maximum-transmit-rate packets-per-second; | [edit logical-systems logical-system-name protocols igmp],
[edit protocols igmp] | Limit the transmission rate of IGMP packets | [
{
"name": "packets-per-second",
"desc": "Maximum number of IGMP packets transmitted in one second by the routing"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Limiting the Maximum IGMP Message Rate"
] |
maximum-transmit-rate (Protocols MLD) | maximum-transmit-rate packets-per-second; | [edit logical-systems logical-system-name protocols mld],
[edit protocols mld] | Limit the transmission rate of MLD packets. | [
{
"name": "packets-per-second",
"desc": "Maximum number of MLD packets transmitted in one second by the routing"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Limiting the Maximum MLD Message Rate"
] |
mc-ae | mc-ae {
chassis-id chassis-id;
events {
iccp-peer-down;
force-icl-down;
prefer-status-control-active;
}
init-delay-time seconds;
mc-ae-id mc-ae-id;
mode (active-active | active-standby);
redundancy-group gro... | [edit interfaces aeX aggregated-ether-options],
[edit logical-systems logical-system-name interfaces aeX aggregated-ether-options] | Enable multichassis link aggregation groups (MC-LAG), which enables one device to form a logical LAG
interface with two or more other devices. | [
{
"name": "chassis-id",
"desc": "Specify the chassis ID for Link Aggregation Control Protocol (LACP) to calculate the port number of MC-LAG physical member links. Each MC-LAG peer should have a unique chassis ID. Values: 0 or 1"
},
{
"name": "events",
"desc": "Specify an action if a specific MC... | 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.
events statement introduced in Junos OS Release 11.4R4 for MX Series routers.
prefer-status-control-active statement introduced in Junos OS Release 13.2R1 for EX Series switches.
init-delay-time seconds statement introduced in Junos OS Release 13.2R3 for EX Series switches... | [] |
mc-ae-id | mc-ae-id mc-ae-id; | [edit interfaces aggregated-ether-options mc-ae] | Specify the multichassis aggregated Ethernet (MC-AE) identification number of the MC-AE that a given
aggregated Ethernet interface belongs to. The two peers that host a given multichassis link aggregation
group (MC-LAG) must have the same multichassis aggregated Ethernet ID. | [] | 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. | [] |
mcast stats-enable | mcast {
stats-enable;
} | [edit system packet-forwarding-options] | Enable L3 Multicast Statistics to track the total number of packets and bytes that hit a multicast route.
Statistics are attached and collected on a FCFS (first-come, first-served) basis for the first 16K (S,G)
routes that require statistics. The routes can be a combination of IPv4 and IPv6 (S,G) routes. Both ASM
and S... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.2R1. | [] |
mclag | mclag {
bgp-peer ip-address;
} | [edit routing-instances name protocols evpn] | Configure parameters that enable the interworking of Ethernet VPN-MPLS (EVPN-MPLS) with a Junos
Fusion Enterprise or a multichassis link aggregation group (MC-LAG) topology.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"Understanding EVPN-MPLS Interworking with Junos Fusion Enterprise and MC-LAG"
] |
mclag-arp-nd-sync | mclag-arp-nd-sync; | [edit logical-systems name protocols l2-learning],
[edit protocols l2-learning] | When MC-LAG peers power up or reboot, Address Resolution Protocol (ARP) and Neighbor Discovery
(ND) entries are learned and synchronized by the peers. Because the MC-LAG peers synchronize and
learn each other’s ARP and ND entries, relearning these entries is not needed on the device. Only the
ARP and ND entries that a... | [] | routing | Statement introduced in Junos OS Release 14.2. | [
"Understanding Multichassis Link Aggregation Groups"
] |
mclag-arpreq-sync | mclag-arpreq-sync; | [edit logical-systems name protocols l2-learning],
[edit protocols l2-learning] | In an active-active MC-LAG configuration, Address Resolution Protocol (ARP) requests are synchronized
between the MC-LAG peers. | [] | routing | Statement introduced in Junos OS Release 12.3. | [
"Understanding Multichassis Link Aggregation Groups"
] |
mdi-mode | mdi-mode mode; | [edit interfaces interface-name ether-options],
[edit interfaces interface-range range ether-options] | You must configure media dependent interface (MDI) properties for a 10-Gigabit Ethernet interface on a
copper network port of an EX4550 switch to ensure that both sides of the link are compatible.
MDI refers to the IEEE standard for the interface to an unshielded twisted pair (UTP) cable. Twisted-pair
Ethernet standard... | [
{
"name": "auto",
"desc": "Set the MDI properties to automatic. This setting should not be used with 10-Gigabit Ethernet interfaces on a copper network port of an EX4550 switch."
},
{
"name": "mdi",
"desc": "Set the MDI properties of the interface to straight through mode. The selection of the m... | 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.
Support for SRX Series Firewalls introduced in Junos OS Release 15.1x49.D80. | [
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Interfaces Overview for Switches",
"Junos OS Ethernet Interfaces Configuration Guide",
"Interfaces User Guide for Security Devices"
] |
mdt | mdt {
data-mdt-reuse;
group-range multicast-prefix;
threshold {
group group-address {
source source-address {
rate threshold-rate;
}
}
tunnel-limit limit;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family inet | inet6],
[edit routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instanc... | Establish the group address range for data MDTs, the threshold for the creation of data MDTs, and
tunnel limits for a multicast group and source. A multicast group can have more than one source of
traffic.
The remaining statements are explained separately. . | [] | 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. In Junos OS Release 17.3R1, the mdt hierarchy was
moved from provider-tunnel to the provider-tunnel family inet and provider-tunnel family inet6 hierarchies as
part of an upgrade to add IPv6 support for default MDT in Rosen 7, and data MDT for Rosen 6 and
Rosen 7. The p... | [
"Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode",
"Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode"
] |
measurement-interval | measurement-interval (5|15|30|60) | [edit protocols oam ethernet cfm performance-monitoring],
[edit protocols oam ethernet cfm performance-monitoring sla-iterator-profiles profile-name] | Configure measurement interval to be used for a performance monitoring session. You must configure
the measurement-interval at the [edit protocols oam ethernet cfm performance-monitoring] hierarchy level,
which is a global level parameter. You can override the configured value by specifying a measurement-
interval for ... | [] | configure—To enter configuration mode.
control—To modify any configuration. | [
"IEEE 802.1ag OAM Connectivity Fault Management Overview",
"Junos OS Support for Performance Monitoring Compliant with Technical Specification MEF 36"
] | |
measurement-type | measurement-type (loss | statistical-loss-measurement | two-way-delay); | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name] | Configure the measurement type for the service level agreement (SLA) frames. An SLA frame is a type of
packet used to measure frame loss in Ethernet connections. | [
{
"name": "loss",
"desc": "Use Y.1731-compliant line module (LM) frames to measure frame loss."
},
{
"name": "statistical-loss-measurement",
"desc": "Use Y.1731-compliant two-way data module (DM) frames to statistically"
},
{
"name": "two-way-delay",
"desc": "Use Y.1731-compliant two... | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1.
The statistical-loss-measurement option introduced in Junos OS Release 11.2. | [
"Configuring an Iterator Profile"
] |
med-igp-update-interval | med-igp-update-interval minutes; | [edit routing-options] | Configure a timer for how long to delay updates for the multiple exit discriminator (MED) path attribute
for BGP groups and peers configured with the metric-out igp offset delay-med-update statement. The timer
delays MED updates for the interval configured unless the MED is lower than the previously advertised
attribut... | [
{
"name": "minutes",
"desc": "Interval to delay MED updates."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0 | [
"Example: Associating the MED Path Attribute with the IGP Metric and Delaying MED Updates"
] |
media-loss-rate | media-loss-rate {
no-syslog-generation;
generate-snmp-traps;
storm-control {
count number;
interval number;
}
alarm-mode {
immediate;
}
} | [edit services] | Configure the media loss rate. The media loss rate is the number of media packets lost over a
configurable time interval (interval-duration) where the flow packets are packets carrying streaming
application information. A single IP packet can contain zero or more streaming packets.
The remaining statements are explaine... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Inline Video Monitoring on MX Series Routers"
] |
media-rate-variation | media-rate-variation {
no-syslog-generation;
generate-snmp-traps;
storm-control {
count number;
interval number;
}
alarm-mode {
mdi-records-count number;
average;
}
} | [edit services] | Configure the media rate variation. The media rate variation is the difference between the expected
packet rate and actual packet rate expressed as a percentage of the expected packet rate.
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 15.1. | [
"Understanding Inline Video Monitoring on MX Series Routers"
] |
media-source-port-any | media-source-port-any; | [edit logical-systems name security alg h323],
[edit logical-systems name tenants name security alg h323],
[edit security alg h323],
[edit services alg h323],
[edit tenants name security alg h323] | Configure media-source-port-any to allow media traffic from any port number. By default, this feature is
disabled, which allows a temporary opening in the firewall (pinhole) to open media traffic. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
media-type (Dual-Purpose Uplink Ports) | media-type (copper | fiber); | [edit interfaces interface-name] | (EX2200-C switch only) Configure the media type for a dual-purpose uplink port (one RJ-45 port and
one SFP port) on an EX2200 switch. If you use the media-type for a dual-purpose uplink port, the
alternate media type cannot be used with the port.
(ACX1000 routers only) Select the media type (copper or fiber) for the 1-... | [
{
"name": "copper",
"desc": "The dual-purpose uplink port accepts only a 10/100/1000BASE-T copper connection."
},
{
"name": "fiber",
"desc": "The dual-purpose uplink port accepts only an SFP fiber connection."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [
"Configuring the Media Type on Dual-Purpose Uplink Ports"
] |
media-type (Interfaces) | media-type | [edit interfaces interface-name media-type] | Configure the operating modes for the 2-Port 10 Gigabit Ethernet XPIM. | [
{
"name": "copper",
"desc": ""
},
{
"name": "fiber",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 10.2. | [
"Understanding Interfaces"
] |
medium (Tunnel Profile) | medium type; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify the medium type for the tunnel.
Default
ipv4 | [
{
"name": "type",
"desc": "Medium type for the tunnel. The only value currently available is ipv4."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
mef-forwarding-profile | mef-forwarding-profile; | [edit system packet-forwarding-options] | Configure the MEF standard forwarding profile for L2CP packets. This command configures the system
to handle L2CP packets in compliance with MEF standards. Configuring this command restarts the
management process (mgd). | [] | 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.4R1. | [] |
member (Application Identification) | [member member-name]; | [edit services application-identification application application-name over protocol-type
signature l4-l7-signature-name] | Define a member name for a custom application definition. Custom definitions can contain multiple
members that define attributes for an application. You can define a maximum of four member names. | [
{
"name": "member-name",
"desc": "Name of a member for a custom application definition. You can define a maximum of four member names."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
member (MX Series Virtual Chassis) | member member-id {
role (routing-engine | line-card);
serial-number serial-number;
} | [edit virtual-chassis] | Configure an MX Series router as a member of a Virtual Chassis configuration. You can configure a
maximum of two member routers in an MX Series Virtual Chassis. | [
{
"name": "member-id",
"desc": "Numeric value that identifies a member router in a Virtual Chassis configuration."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Preprovisioned Member Information for a Virtual Chassis",
"Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a",
"Virtual Chassis"
] |
member (NSSU Upgrade Groups) | member member-id {
fpcs (slot-number | [list-of-slot-numbers]);
} | [edit chassis nssu upgrade-group group-name] | Specify the Virtual Chassis member whose line-card slot numbers you are assigning to an NSSU upgrade
group.
NOTE: This statement is not applicable to Virtual Chassis or VCF member switches that
do not support separate line cards. To configure Virtual Chassis or VCF member switches
that do not have separate line cards i... | [
{
"name": "member-id",
"desc": "The ID of the Virtual Chassis or VCF member switch containing one or more line cards to include in an NSSU upgrade group. 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 11.1. | [
"Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on EX Series",
"Switches",
"Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade"
] |
member (Redundant Power System) | member vc-member-number {
priority (0|1|2|3|4|5|6);
} | [edit redundant-power-system] | Specify the Virtual Chassis member ID of a switch connected to the Redundant Power System (RPS) for
backup power supply. The member ID is required only for switches that can be configured in a Virtual
Chassis. If the switch has never been configured in a Virtual Chassis, the value is always 0. | [
{
"name": "member-number",
"desc": "Member ID of a switch that has Virtual Chassis capability that is connected to the"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Determining and Setting Priority for Switches Connected to an EX Series RPS"
] |
member (Security Group VPN) | member {
ike {
gateway gateway-name;
policy;
proposal;
traceoptions;
}
ipsec {
vpn vpn-name {
df-bit (clear | copy | set);
exclude rule rule-name {
source-address ip-address/mask;
destination-addr... | [edit security group-vpn] | 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": "ikegateway-name",
"desc": "Configure IKE gateway for group VPN member."
},
{
"name": "policy policy-name",
"desc": "Configure an IKE policy."
},
{
"name": "proposalproposal-name",
"desc": "Define an IKE proposal."
},
{
"name": "traceoptions",
"desc": "Configure... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Group VPNv2 Overview"
] |
member (Security IDP) | member member-name {
attack-type (Security Anomaly) {
(anomaly ...same statements as in [edit security idp custom-attack attack-name attack-
type anomaly] hierarchy level | signature ...same statements as in [edit security idp custom-
attack attack-name attack-type signature] hierarchy level);
}
} | [edit security idp custom-attack attack-name attack-type chain] | Create the list of member attacks. | [
{
"name": "member-name",
"desc": "Name of the member list."
}
] | 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. | [] |
member | member name; | [edit services application-identification nested-application name signature name] | Define a member name for a custom nested application signature definition. Custom definitions can
contain multiple members that define attributes for an application. | [
{
"name": "name",
"desc": "Name of member for a custom nested application signature definition."
}
] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Application Identification for Nested Applications"
] |
member | member member-id {
fabric-tree-root;
location location;
mastership-priority number;
no-management-vlan;
serial-number serial-number;
role role;
} | [edit virtual-chassis] | Configure a switch or an XRE200 External Routing Engine as a member of a Virtual Chassis or a Virtual
Chassis Fabric (VCF) with characteristics specified by the available options.
Default
When an EX Series switch or a QFX Series devices configured in standalone mode is powered on but
not interconnected through its Virt... | [
{
"name": "member-id",
"desc": "Identifies a specific member switch of a Virtual Chassis or VCF configuration."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Preprovisioning a Virtual Chassis Fabric",
"Adding a Device to a Virtual Chassis Fabric",
"Configuring an EX4650 or a QFX Series Virtual Chassis",
"Configuring an EX2300, EX3400, or EX4300 Virtual Chassis",
"Configuring EX4600 Switches in a Mixed or Non-Mixed ... |
member-failure-options (Aggregated Multiservices) | member-failure-options {
drop-member-traffic {
rejoin-timeout rejoin-timeout;
}
redistribute-all-traffic {
enable-rejoin;
}
} | [edit interfaces interface-name load-balancing-options] | Configure the possible behavior for the aggregated Multiservices (AMS) interface in case of failure of
more than one active member.
NOTE: The drop-member-traffic configuration and the redistribute-all-traffic configuration
are mutually exclusive.
Table 74 on page 11059 displays the behavior of the member interface aft... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support added 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 Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
member-id (Junos Fusion Satellite Device Cluster) | member-id member-ID-number; | [edit chassis satellite-management cluster cluster-name fpc slot-id ] | Assign a member ID number to a satellite device in a satellite device cluster.
The member ID is used to identify the satellite device within the satellite device cluster.
Default
Member ID numbers are not assigned in a satellite device cluster, by default. | [
{
"name": "member-ID-number",
"desc": "Specifies the member ID of the satellite device in the satellite device cluster."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Configuring or Expanding a Junos Fusion Enterprise"
] |
member-interface (Aggregated Multiservices) | member-interface interface-name; | [edit interfaces interface-name load-balancing-options] | Specify the member interfaces for the aggregated multiservices (AMS) interface. You can configure
multiple interfaces by specifying each interface in a separate statement.
Starting with Junos OS Release 16.2, an AMS interface can have up to 32 member interfaces. In Junos
OS Release 16.1 and earlier, an AMS interface ca... | [
{
"name": "interface-name",
"desc": "Name of the member interface. The member interface format is mams-a/b/0, where a is the FPC slot number and b is the PIC slot number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support added 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 Aggregated Multiservices Interfaces for Next Gen Services",
"Configuring Aggregated Multiservices Interfaces"
] |
member-link-scheduler | member-link-scheduler (replicate | scale); | [edit class-of-service interfaces interface-name],
[edit logical-systems logical-system-name class-of-service interfaces interface-name],
[edit routing-instances routing-instance-name class-of-service interfaces interface-name] | Determines whether scheduler parameters for aggregated interface member links are applied in a
replicated or scaled manner.
Default
By default, scheduler parameters are scaled (in “equal division mode”) among aggregated interface
member links. | [
{
"name": "replicate",
"desc": "Scheduler parameters are copied to each level of the aggregated interface member links."
},
{
"name": "scale",
"desc": "Scheduler parameters are scaled based on number of member links and applied each level of the"
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Hierarchical Schedulers for CoS"
] |
member-range | member-range starting-interface-name ending-interface-name; | [edit interfaces interface-range interface-range-name] | Specify the names of the first and last members of a sequence of interfaces belonging to an interface
range. | [
{
"name": "starting interface-name ending interface-name",
"desc": "Name of the first member and the name of the last"
}
] | 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. | [
"Understanding Interface Ranges for Switches",
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for OCX Series Switches",
"Interfaces Overview for Switches",
"Interfaces Overview for Switches",
"Junos OS Ne... |
members | members [(all | names | vlan-ids)]; | [edit interfaces interface-name unit 0 family ethernet-switching vlan] | For trunk interfaces, configure the VLANs for which the interface can carry traffic.
TIP: To display a list of all configured VLANs on the system, including VLANs that are
configured but not committed, type ? after vlan or vlans in your configuration mode
command line. Note that only one VLAN is displayed for a VLAN ra... | [
{
"name": "all",
"desc": "Specifies that this trunk interface is a member of all VLANs that are configured on this switch. When"
},
{
"name": "names",
"desc": "Name of one or more VLANs. VLAN IDs are applied automatically in this case."
},
{
"name": "vlan-ids",
"desc": "Numeric ident... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Statement updated with enhanced ? (CLI completion feature) functionality in Junos OS Release 9.5 for
EX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series. | [
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Configuring Gigabit Ethernet Interfaces for EX Series Switches with ELS support",
"Configuring Gigabit Ethernet Interfaces (J-Web Procedure)",
"Configuring VLANs for EX Series Switches",
"Configuring VLANs for EX Series Switches with ELS Support (C... |
memory (System) | memory {
system {
alarm;
frequency (minutes | hours| days) <value>;
minor event {
threshold swap usage <value in percentage>;
action snmp-trap;
}
major event {
threshold swap usage <value in percentage>;
action [snmp-trap | live... | [edit system monitor] | Configure the memory monitoring system on your device. The memory monitoring system on your
device monitors anomalies with respect to the memory utilization of Junos applications and overall
system in the control plane of your device. Apart from monitoring the system memory, you can also
configure the device to monitor... | [
{
"name": "alarm",
"desc": "Enable system monitor alarm. The alarm is raised when the device is running low on memory."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.1R1.
The alarm option is introduced in Junos OS Release 23.1R1. | [
"System Log Overview"
] |
memory (TDF Gateway) | memory memory-pct; | [edit unified-edge gateways tdf gateway-name cac] | Configure the threshold for the maximum amount of memory that the TDF gateway may use. If the
amount of memory that the TDF gateway uses reaches the threshold, the SNMP trap
jnxScgSMMemoryThreshHigh is generated. | [
{
"name": "memory-pct",
"desc": "Maximum percentage of memory that can be used. Range: 1 through 90."
}
] | 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 a TDF Gateway"
] |
memory | memory {
size size;
features {
hugepages;
}
} | [edit virtual-network-functions] | Configure memory parameters for VNFs on a platform that is running a disaggregated Junos OS. | [
{
"name": "memory size",
"desc": "Amount of memory allocated to a VNF in kilobytes. The default size is 1 GB."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
memory-enhanced | memory-enhanced {
filter;
route;
vpn-label;
} | [edit chassis] | Allocate more jtree memory for routing tables and Layer 3 VPNs.
NOTE: The memory-enhanced statement supports MX Series routers with DPC (I-chip based)
line cards only.
The remaining statements are explained separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement added in Junos OS Release 10.4. | [
"Allocating More Memory for Routing Tables, Firewall Filters, and Layer 3 VPN Labels"
] |
memory-log-disable (clksyncd) | memory-log-disable; | [edit logical-systems name protocols clock-synchronization memory-logging clksyncd],
[edit protocols clock-synchronization memory-logging clksyncd] | Disable memory logging for clksyncd process. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
memory-log-disable (clksyncm) | memory-log-disable; | [edit logical-systems name protocols clock-synchronization memory-logging lc-clocking],
[edit protocols clock-synchronization memory-logging lc-clocking] | Disable memory logging for clksyncm process. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
menu-item | menu-item (menu-name | menu-option) <disable>; | [edit chassis lcd-menu],
[edit chassis lcd-menu fpc slot-number] | Disable or enable the Maintenance menu, the Status menu, or an individual option in one of those
menus in the LCD panel.
On EX3200, EX3300, EX4200, and EX4500 switches, you use menu-item at the [edit chassis lcd-menu
fpc slot-number] hierarchy level.
On EX6200 and EX8200 switches, and on XRE200 External Routing Engines... | [
{
"name": "menu-name",
"desc": "Name of the LCD menu:"
},
{
"name": "maintenance-menu",
"desc": ""
},
{
"name": "status-menu",
"desc": ""
},
{
"name": "menu-option",
"desc": "Specific option on one of the LCD menus. You must include the quotation marks when"
},
{
... | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the LCD Panel on EX Series Switches (CLI Procedure)",
"LCD Panel in EX3200 Switches",
"LCD Panel in EX3300 Switches",
"LCD Panel in EX4200 Switches",
"LCD Panel in EX4500 Switches",
"LCD Panel in EX4550 Switches",
"LCD Panel in an EX6200 Switch",
"LCD Panel in an EX8200 Switch",
"LCD Pa... |
mep | mep mep-id {
action-profile action-profile-name
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
i... | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-
association ma-name] | The numeric identifier of the maintenance association end point (MEP) within the maintenance
association. | [
{
"name": "mep mep-id",
"desc": "Specify the numeric identifier of the MEP."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Ethernet Alarm Indication Signal (ETH-AIS) Function Overview",
"Configuring ETH-AIS on a CFM MEP",
"Configuring a MEP to Generate and Respond to CFM Protocol Messages"
] |
mesh-group (Protocols VPLS) | mesh-group mesh-group-name {
interface interface-name;
l2vpn-id (as-number:id | ip-address:id);
local-switching;
mac-flush [ explicit-mac-flush-message-options ];
neighbor address {...};
peer-as all;
pseudowire-status-tlv hot-standby-vc-on;
route-distinguisher (as-number:id | ip-address:... | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
site site-name],
[edit routing-instances routing-instance-name protocols vpls],
[edit routing-instances routing-instance-n... | Specify the virtual private LAN service (VPLS) mesh group. The statement options allow you to specify
each provider edge (PE) device that is a member of the mesh group. This statement is also used in the
configuration of inter-autonomous system (AS) VPLS with media access control (MAC) operations.
When you configure me... | [
{
"name": "mesh-group-name",
"desc": "Name of the VPLS mesh group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
local-switching, mac-tlv-receive, mac-tlv-send, and peer-as options introduced in Junos OS Release 9.3.
pseudowire-status-tlv and mac-flush options introduced in Junos OS Release 10.0.
route-distinguisher, vrf-export, vrf-import, and vrf-target options introduced in Junos O... | [
"Configuring VPLS Routing Instances",
"Configuring Interoperability Between BGP Signaling and LDP Signaling in VPLS"
] |
message-flood (Security H323) | message-flood {
gatekeeper {
threshold rate;
}
} | [edit logical-systems name security alg h323 application-screen],
[edit logical-systems name tenants name security alg h323 application-screen],
[edit security alg h323 application-screen],
[edit services alg h323 application-screen],
[edit tenants name security alg h323 application-screen] | Configure the message-flood parameter to limit the number of message requests allowed per second
from Remote Access Server (RAS) to the gatekeeper. Messages exceeding the threshold are dropped. | [
{
"name": "gatekeeper threshold rate",
"desc": "Maximum number of RAS connection requests per second allowed per gateway."
}
] | 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. | [] |
message-flood (Security MGCP) | message-flood {
threshold rate;
} | [edit logical-systems name security alg mgcp application-screen],
[edit logical-systems name tenants name security alg mgcp application-screen],
[edit security alg mgcp application-screen],
[edit services alg mgcp application-screen],
[edit tenants name security alg mgcp application-screen] | Configure the message-flood parameter to limit the number of Media Gateway messages processed per
second. Messages exceeding the threshold are dropped by the Media Gateway Control Protocol (MGCP)
Application Layer Gateway (ALG). This feature is disabled by default. | [
{
"name": "threshold rate",
"desc": "Number of connection requests per second allowed per Media Gateway."
}
] | 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. | [] |
message-ie-profile-v1 | message-ie-profile-v1 name {
message msg-type {
ie ie-number;
}
} | [edit security gtp] | Specify a GTPv1 message IE profile. You can implement Must-IE check for GTPv1 using message profile
configurations, which helps you to define must IEs of interested messages. Along with appropriate
message profile configurations, Must-IE check can easily accommodate any GTP releases, message
format, or IE status.
From ... | [
{
"name": "name",
"desc": "Name of the GTPv1 message IE profile."
},
{
"name": "msg-type",
"desc": "Message type. Range: 1 to 255"
},
{
"name": "ie-number",
"desc": "IE number. Range: 1 to 255"
}
] | security—To view this statement in the configuration. | Statement introduced in Junos OS Release 20.2R1. | [
"Example: Configure Must-IE check for GTPv1 and GTPv2"
] |
message-ie-profile-v2 | message-ie-profile-v2 name {
message msg-type {
ie ie-number {
instance inst-number {
grouped-ie-profile grpie-prf-name;
}
}
}
} | [edit security gtp] | Specify a GTPv2 message IE profile. You can implement Must-IE check for GTPv2 using message profile
configurations, which helps you to define must IEs of interested messages. Along with appropriate
message profile configurations, Must-IE check can easily accommodate any GTP releases, message
format, or IE status.
From ... | [
{
"name": "name",
"desc": "Name of the message IE filter profile."
},
{
"name": "msg-type",
"desc": "Message type. Range: 1 to 255"
},
{
"name": "ie-number",
"desc": "IE number. Range: 1 to 255"
},
{
"name": "inst-number",
"desc": "Instance number. Range: 0 to 11 Defa... | security—To view this statement in the configuration. | Statement introduced in Junos OS Release 20.2R1. | [
"Example: Configure Must-IE check for GTPv1 and GTPv2"
] |
message-list | message-list msg-list-name {
message msg-number;
} | [edit security gtp] | Use the message-list function to configure a list of messages. | [
{
"name": "msg-list-name",
"desc": "Specifies the message list name."
},
{
"name": "msg-number",
"desc": "Specifies the message type. Range 1 to 255"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"show security gtp message-list"
] |
message-processing-model | message-processing-model (v1 | v2c | v3); | [edit snmp v3 target-parameters target-parameter-name parameters] | Configure the message processing model to be used when generating SNMP notifications. | [
{
"name": "v1",
"desc": "SNMPv1 message process model."
},
{
"name": "v2c",
"desc": "SNMPv2c message process model."
},
{
"name": "v3",
"desc": "SNMPv3 message process model."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Message Processing Model"
] |
message-rate-limit (Flow Monitoring Logs for NAT) | message-rate-limit messages-per-second | [edit interfaces interface-name services-options jflow-log] | Define the maximum number of logs or template records in flow monitoring format to be generated for
NAT error events per second from the specified interface. These records for NAT error events are
generated when addresses for allocation from the NAT pool are not available, when ports for allocation
to a subscriber are ... | [
{
"name": "messages-per-second",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
message-rate-limit (interfaces) | message-rate-limit messages-per-second | interfaces interface-name {
services-options {
cgn-pic;
disable-global-timeout-override;
ignore-errors <alg> <tcp>;
inactivity-non-tcp-timeout seconds;
inactivity-tcp-timeout seconds;
inactivity-timeout seconds;
open-timeout seconds;
session-limit {
... | Maximum system log messages per second allowed from this interface.
NOTE: The message-rate-limit command can be configured only for physical service
interfaces (sp-x/x/x) and not for redundancy services PIC interfaces (rspx). | [
{
"name": "messages-per-second",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced Junos OS Release 11.1. | [
"Configuring System Logging for Service Sets"
] |
message-rate-limit | message-rate-limit messages-per-minute; | [edit protocols pcep] | Specify the number of messages per minute that the Path Computation Client (PCC) can receive at
maximum. | [
{
"name": "messages-per-minute",
"desc": "Number of messages per minute that the PCC can receive at maximum. Range: 1 through 16384 Default: 0 (disabled or no limit)"
}
] | 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.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFX Series added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1. | [] |
message-size | message-size number; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name routing-instances routin... | Specify the number of route entries to be included in every RIP update message. To ensure
interoperability with other vendors’ equipment, use the standard of 25 route entries per message. | [
{
"name": "number",
"desc": "Number of route entries per update message."
}
] | 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. | [] |
message-type | message-type {
create-req {
alarm-threshold (Security GPRS) {
forward number;
reverse number;
}
drop-threshold (Security GPRS) {
forward number;
reverse number;
}
}
delete-req {
drop-threshold (Security GPRS) {
... | [edit security gtp profile profile-name path-rate-limit] | Use the message-type function to specify the group of control messages.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name path-rate-limit]
hierarchy level is replaced by [edit security gtp profile profile-name path-rate-limit]. | [
{
"name": "create-req",
"desc": "To limit packet-per-second of GTP create request."
},
{
"name": "delete-req",
"desc": "To limit packet-per-second of GTP delete request."
},
{
"name": "echo-req",
"desc": "To limit packet-per-minute of GTP echo request."
},
{
"name": "other",
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [
"GTPv1 Message Filtering"
] |
method | method {
bfd {
version (0 | 1 | automatic);
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
det... | [edit forwarding-options dhcp-relay dhcpv6 group group-name liveness-detection],
[edit forwarding-options dhcp-relay dhcpv6 liveness-detection],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name liveness-detection],
[edit forwarding-options dhcp-relay group group-name liveness-detection],
[edit... | Configure the liveness detection method.
NOTE: The "bfd" on page 3117 stanza is not available at the [edit forwarding-options dhcp-
relay dual-stack-group dual-stack-group-name liveness-detection method] or [edit system services
dhcp-local-server dual-stack-group dual-stack-group-name liveness-detection hierarchy level... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"DHCP Liveness Detection Overview",
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients",
"DHCP Liveness Detection Using ARP and Neighbor Discovery Packets"
] |
metric (Aggregate, Generated, or Static Route) | (metric | metric2 | metric3 | metric4) metric <type type>; | [edit logical-systems logical-system-name routing-options (aggregate | generate | static)
(defaults | route)],
[edit routing-options (aggregate | generate | static) (defaults | route)] | Specify the metric value for an aggregate, generated, or static route. You can specify up to four metric
values, starting with metric (for the first metric value) and continuing with metric2, metric3, and metric4. | [
{
"name": "metric",
"desc": "Metric value."
},
{
"name": "type type",
"desc": "(Optional) Type of route."
}
] | 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: Summarizing Static Routes Through Route Aggregation",
"Understanding Route Aggregation"
] |
metric (Diameter Route) | metric route-metric; | [edit diameter network-statement element-name forwarding route dne-route-name] | Specify the metric associated with a destination and function. Together, these three elements define a
route reachable through a Diameter network element. A lower metric makes a route more preferred. | [
{
"name": "route-metric",
"desc": "Metric assigned to the route."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
metric (Dynamic Access-Internal Routes) | metric route-cost; | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access route prefix],
[edit dynamic-profiles profile-name routing-options access rout... | Dynamically configure the cost for an access route. | [
{
"name": "route-cost",
"desc": "Either the specific cost you want to assign to the access route or either of the following cost"
},
{
"name": "variables:",
"desc": ""
},
{
"name": "$junos-framed-route-cost",
"desc": "Cost of an IPv4 access route; the variable is dynamically replaced... | 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.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-
options rib routing-table-name access route prefix] h... | [
"Routes for DHCP and PPP Subscriber Access Networks"
] |
metric (Policy Action) | metric (add add | aigp | expression expression | igp metric_offset | minimum-igp metric_offset
| subtract subtract) | [edit policy-options policy-statement policy-name term term-name then ],
[edit policy-options policy-statement policy-name then ] | Specify this CLI policy action in an import or export policy to set the metric value to one of the following
options as per your network requirement. | [
{
"name": "add add",
"desc": "Specify a constant that should be added to the metric value. Use this option if you want to increase the metric of a route."
},
{
"name": "expression",
"desc": "Calculate the metric value based on the route metric and metric2."
},
{
"name": "igp metric_offse... | 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. | [] |
metric (Protocols DVMRP) | metric metric; | [edit logical-systems logical-system-name protocols dvmrp interface interface-name],
[edit protocols dvmrp interface interface-name] | Define the DVMRP metric value. | [
{
"name": "metric",
"desc": "Metric value."
}
] | 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"
] |
metric (Protocols IS-IS) | metric metric; | [edit logical-systems logical-system-name protocols isis interface interface-name level level-
number],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name level level-number],
[edit protocols isis interface interface-name level level-number],
[edit... | Specify the IPv4 unicast topology metric value for the level. The IS-IS interface metrics for the IPv6
topology can be configured independently of the IPv4 metrics.
All IS-IS routes have a cost, which is a routing metric that is used in the IS-IS link-state calculation. The
cost is an arbitrary, dimensionless integer t... | [
{
"name": "metric",
"desc": "Metric value."
}
] | 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: Enabling Wide IS-IS Metrics for Traffic Engineering",
"Understanding Wide IS-IS Metrics for Traffic Engineering"
] |
metric (Protocols MPLS) | metric metric; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit protocols mpls label-switched-path lsp-name],
[edit protocols mpls static-label-switched-path lsp-name ingress] | Compare against another LSP or against an IGP route. To disable dynamic metric tracking, assign a fixed
metric value to an LSP. If no metric is assigned, the LSP metric is dynamic and automatically tracks
underlying IGP metrics. | [
{
"name": "metric",
"desc": "LSP metric value."
}
] | 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 Static LSP Metrics"
] |
metric (Protocols OSPF Sham Link) | metric number; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id sham-link-remote address],
[edit routing-instances routing-instance-name protocols ospf area area-id sham-link-remote
address] | Specify the cost of using the OSPF sham link.
Default
number—1 | [
{
"name": "number",
"desc": "1 through 65,535"
}
] | 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: Giving VPN Backbones Priority with OSPFv2 Sham Links for Layer 3 VPNs"
] |
metric (Qualified Next Hop on Static Route) | metric metric; | [edit logical-systems logical-system-name routing-options static route destination-prefix
qualified-next-hop],
[edit routing-options static route destination-prefix qualified-next-hop] | Metric value for a static route. | [
{
"name": "metric",
"desc": "Metric value."
}
] | 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. | [] |
metric | metric route-cost; | [edit routing-options access route ip-prefix</prefix-length>] | Configure the cost for an access route. | [
{
"name": "route-cost",
"desc": "Specific cost you want to assign to the access route."
}
] | 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. | [] |
metric-in (Protocols RIP) | metric-in metric; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name routing-instances routin... | Specify the metric to add to incoming routes when the routing device advertises into RIP routes that
were learned from other protocols. Use this statement to configure the routing device to prefer RIP
routes learned through a specific neighbor. | [
{
"name": "metric",
"desc": "Metric value."
}
] | 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 the Metric Value Added to Imported RIP Routes"
] |
metric-in (Protocols RIPng) | metric-in metric; | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-
name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng],
[edit logical-systems logical-system-name routing-instance... | Specify the metric to add to incoming routes when advertising into RIPng routes that were learned from
other protocols. Use this statement to configure the routing device to prefer RIPng routes learned
through a specific neighbor. | [
{
"name": "metric",
"desc": "Metric value."
}
] | 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 routing instances introduced in Junos OS Release 9.0. | [
"Example: Configuring the Metric Value Added to Imported RIPng Routes to Control the Route",
"Selection Process"
] |
metric-out (Protocols RIP) | metric-out metric; | [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip
group group-name neighbor neighbor-name],
[edit protocols rip group group-name neighbor neighbor-name],
[edit routing-instanc... | Specify the metric value to add to routes transmitted to the neighbor. Use this statement to control how
other routing devices prefer RIP routes sent from this neighbor. | [
{
"name": "metric",
"desc": "Metric value."
}
] | 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. | [] |
metric-out (Protocols RIPng) | metric-out metric; | [edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-
name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng group group-name neighbor neighbor-name],
[edit protocols ripng group group-name neighbor neighbor-name],
[edit routing-... | Specify the metric value to add to routes transmitted to the neighbor. Use this statement to control how
other routing devices prefer RIPng routes sent from this neighbor.
When an export policy is configured, RIPng exports all learned routes to neighbors configured with the
neighbor statement.
If a route being exported... | [
{
"name": "metric",
"desc": "Metric value."
}
] | 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 routing instances introduced in Junos OS Release 9.0. | [
"Example: Configuring the Metric Value Added to Imported RIPng Routes to Control the Route",
"Selection Process",
"Understanding RIPng Traffic Control with Metrics for Optimizing the Path Cost"
] |
metric-out | metric-out (metric | minimum-igp offset | igp (delay-med-update | offset); | [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... | Specify the metric for all routes sent using the multiple exit discriminator (MED, or MULTI_EXIT_DISC)
path attribute in update messages. This path attribute is used to discriminate among multiple exit points
to a neighboring AS. If all other factors are equal, the exit point with the lowest metric is preferred.
You ca... | [
{
"name": "delay-med-update",
"desc": "Specify that a BGP group or peer configured with the metric-out igp statement not"
},
{
"name": "igp",
"desc": "Set the metric to the most recent metric value calculated in the IGP to get to the BGP next hop."
},
{
"name": "metric",
"desc": "Pri... | 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.
Option delay-med-update introduced in Junos OS Release 9.0. | [
"Example: Associating the MED Path Attribute with the IGP Metric and Delaying MED Updates",
"Examples: Configuring BGP MED",
"Example: Configuring the MED Attribute That Determines the Exit Point in an AS",
"Understanding the MED Attribute That Determines the Exit Point in an AS"
] |
metrics-profile | metrics-profile metrics-profile-name {
sla-threshold {
delay-round-trip {
delay-value;
}
jitter {
jitter-value;
}
jitter-type {
egress-jitter ;
ingress-jitter;
two-way-jitter;
}
match {
... | [edit security advance-policy-based-routing] | Create a set of metrics, which can be used by AppQoE to evaluate the SLA of the link.
A metrics profile defines the performance metrics for delay round trip, one-way jitter or two-way jitter,
and packet loss.
To ensure compliance with the SLA, metrics are required to measure and monitor the network
performance. This me... | [
{
"name": "metrics-profile-name",
"desc": "Metrics profile name."
},
{
"name": "delay-round-trip delay-",
"desc": ""
},
{
"name": "value",
"desc": "Sets the total round-trip time (in microseconds), from the device to the remote server, that triggers a probe failure."
},
{
"na... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Application Quality of Experience",
"Advanced Policy-Based Routing"
] |
mgcp | mgcp {
application-screen {
connection-flood {
threshold rate;
}
message-flood {
threshold rate;
}
unknown-message {
permit-nat-applied;
permit-routed;
}
}
disable;
dscp-rewrite {
code-point string;... | [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 MGCP ALG. By default, the MGCP ALG is enabled."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding the MGCP ALG"
] |
mib-profile | mib-profile profile-name {
file filename;
interval minutes;
start-time time;
object-names {
mib-object-name;
}
operation operation-name;
} | [edit accounting-options] | Create a MIB profile to collect selected MIB statistics and write them to a file in the /var/log directory.
NOTE: Do not configure MIB objects related to interface octets or packets for a MIB
profile, because it can cause the SNMP walk or a CLI show command to time out. | [
{
"name": "profile-name",
"desc": "Name of the MIB statistics profile."
},
{
"name": "start-time",
"desc": ""
},
{
"name": "time",
"desc": "(Optional) Specify the start time in yyyy-mm-dd.hh:mm local time format for the accounting profile. Sometimes, if the time at which the records ... | 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. | [
"Configuring the MIB Profile"
] |
micro-dx2v-sid | micro-dx2v-sid micro-sid-value; | [edit logical-systems name routing-instances name protocols evpn source-packet-routing srv6
locator],
[edit logical-systems name routing-instances name protocols l2vpn source-packet-routing srv6
locator],
[edit logical-systems name routing-instances name protocols vpls source-packet-routing srv6
locator],
[edit logi... | Micro-segment END.DX2V SID. | [
{
"name": "micro-sid-value",
"desc": "Static SID 16-bit or 32-bit value."
}
] | [none specified] | Statement introduced in Junos OS Evolved Release 25.2R1. | [
"Configuring EVPN VPWS over SRv6 with Traffic Engineering"
] |
micro-sid | micro-sid {
anycast
block-name block-name
flavor {
none;
psp;
usd;
usp;
}
} | [edit logical-systems name routing-instances name routing-options source-packet-routing srv6
locator],
[edit logical-systems name routing-options source-packet-routing srv6 locator],
[edit logical-systems name tenants name routing-instances name routing-options source-packet-
routing srv6 locator],
[edit routing-insta... | Enable compression of SIDs for the specified locator and configure parameters for the micro SID locator.
All micro-SIDs derived from this locator take the default micro-SID-length of 16. If you need to include
more than six SRv6 SIDs, micro-SIDs help with compressing multiple IPv6 addresses. Compression of
the SID list... | [
{
"name": "anycast",
"desc": "Indicates that SIDs derived from this locator are anycast SIDs. SRv6 advertises the locator as anycast locator in IGP advertisements."
},
{
"name": "block-name",
"desc": "Specify a block name for this micro-SID locator."
},
{
"name": "flavor",
"desc": "S... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.2R1 and Junos OS 23.4R1. | [
"Understanding SRv6 Network Programming in IS-IS Networks"
] |
micro-srv6-binding-sid | micro-srv6-binding-sid {
locator name {
static-sid;
no-reduced-srh;
}
} | [edit logical-systems name protocols source-packet-routing source-routing-path source-routing-
path-name],
[edit protocols source-packet-routing source-routing-path source-routing-path-name] | Configure Micro SRv6 binding SID.
NOTE: Make sure to configure the micro SRv6 "locator" on page 10418 at the [edit
routing-options] hierarchy level. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1. | [
"Binding SID (BSID) for Static SRv6 TE Tunnels"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.