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 |
|---|---|---|---|---|---|---|---|
match (Security Source NAT) | match {
application {
[application];
any;
}
(destination-address <ip-address> | destination-address-name <address-name>);
destination-port (port-or-low <to high>);
protocol [protocol-name | protocol-number];
source-address [ip-address];
source-address-name [address-name];
... | [edit security nat source rule-set rule-set-name rule rule-name] | Specify the source rules to be used as match criteria.
NOTE: If the options source-port, destination-port, and protocol are configured as match
conditions, then you cannot also configure the application option as a match condition.
The reverse is also true: if you configure the application option as a match condition ... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X45-D10.
Statement modified in Junos OS Release 12.1X47-D10. | [] |
match (Security Static NAT) | match {
(destination-address <ip-address> | destination-address-name <address-name>);
destination-port (port-or-low | <to high>);
source-address [ip-address];
source-address-name [ip-address-name];
source-port (port-or-low <to high>);
} | [edit security nat static rule-set rule-set-name rule rule-name] | Specify the static rules to be used as match criteria. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X45-D10. | [] |
match (Services CoS Next Gen Services) | match {
application [ application-names ];
destination-address address;
destination-address-range low minimum-value high maximum-value;
destination-port port-number;
destination-prefix-list list-name;
source-address address;
source-address-range low minimum-value high maximum-value;
sour... | [edit services cos rule rule-name policy policy-name] | Configure the matching conditions for a policy in a services CoS rule. Matching conditions include
packet source and destination addresses and packet applications. Packets that are processed by a
service set and that match the conditions are assigned the Differentiated Services (DiffServ) code point
(DSCP) marking and ... | [
{
"name": "application [ application-names ]",
"desc": "One or more port-based applications."
},
{
"name": "destination-address address",
"desc": "Destination address of the packet."
},
{
"name": "destination-address-range low",
"desc": ""
},
{
"name": "minimum-value high",
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Class of Service for Services PICs (Next Gen Services)"
] |
match (Stateful Firewall Rule Next Gen Services) | match {
application [application-name];
destination-address (address | any);
destination-address-excluded address;
source-address (address | any);
source-address-excluded address;
} | [edit services policies stateful-firewall-rule rule-name policy policy-name] | Specify the matching properties for a stateful firewall rule policy. When a flow matches these properties,
the policy actions are applied to the flow. | [
{
"name": "application [application-name]",
"desc": "One or more application protocols of flows to which the stateful firewall policy applies. The application protocol definition is configured at the [edit applications] hierarchy level."
},
{
"name": "destination-address",
"desc": ""
},
{
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Stateful Firewalls for Next Gen Services"
] |
match (Syslog) | match "regular-expression"; | [edit logical-systems logical-system-name system syslog file filename],
[edit logical-systems logical-system-name system syslog user (username | *)],
[edit system syslog file filename],
[edit system syslog host hostname | other-routing-engine| scc-master)],
[edit system syslog user (username | *)] | Specify a text string that must (or must not) appear in a message for the message to be logged to a
destination.
If you configure both the match and match-strings statements for the same destination, Junos OS evaluates
the match-strings condition first, and if the condition is satisfied, then the message is logged and ... | [
{
"name": "regular-expression",
"desc": "Regular expression against which to match messages to log. The regular expressions must use the notation defined in POSIX Standard 1003.2 for extended (modern) UNIX regular expressions and must not contain a slash ( / ) or a percent sign ( % )."
}
] | 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. | [
"Using Strings and Regular Expressions to Refine the Set of Logged Messages"
] |
match-direction (IDS) | match-direction (input | output | input-output); | [edit services ids rule rule-name] | Specify the direction in which the rule match is applied. | [
{
"name": "input",
"desc": "Apply the rule match on input."
},
{
"name": "output",
"desc": "Apply the rule match on output."
},
{
"name": "input-output",
"desc": "Apply the rule match bidirectionally."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Match Conditions in IDS Rules",
"Configuring Protection Against Network Attacks on an MS-MPC"
] |
match-direction (IP Reassembly Rule) | match-direction direction | [edit services ip-reassemblyrulerule-name] | Configure the direction in which the IP reassembly rule matching is applied. The match direction is used
with respect to the traffic flow through the inline services interface. You must configure a match
direction for an IP reassembly rule. | [
{
"name": "direction",
"desc": "Match direction. For inline IP reassembly, input is the only match direction supported."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1.
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. | [
"Configuring IP Inline Reassembly for L2TP",
"IP Packet Fragment Reassembly for L2TP Overview"
] |
match-direction (ipsec-vpn) | match-direction (input | output); | [edit services ipsec-vpn rule rule-name] | Specify the direction in which the rule match is applied. | [
{
"name": "input",
"desc": "Apply the rule match on input."
},
{
"name": "output",
"desc": "Apply the rule match on output."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Rules"
] |
match-direction (NAT Next Gen Services) | [edit services nat source rule-set rule-set],
[edit services nat destination rule-set rule-set] | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] | ||
match-direction (PCP) | match-direction (input | output); | [edit services pcp rule rule-name] | Specify the direction in which the rule match is applied. A PCP rule assigns the PCP server that handles
selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. | [
{
"name": "input",
"desc": "Apply the rule match on input."
},
{
"name": "output",
"desc": "Apply the rule match on output."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
match-direction (Services CoS) | match-direction (input | output | input-output); | [edit services cos rule rule-name] | Specify the direction in which the rule match is applied. | [
{
"name": "input",
"desc": "Apply the rule match on the input side of the interface."
},
{
"name": "output",
"desc": "Apply the rule match on the output side of the interface."
},
{
"name": "input-output",
"desc": "Apply the rule match bidirectionally."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring CoS Rules on Services PICs"
] |
match-direction (Services NAT) | match-direction (input | output); | [edit services nat rule rule-name] | Specify the direction in which the rule match is applied. | [
{
"name": "input",
"desc": "Apply the rule match on input."
},
{
"name": "output",
"desc": "Apply the rule match on output."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Network Address Translation Rules Overview"
] |
match-direction (Services Stateful Firewall) | match-direction (input | output | input-output); | [edit services stateful-firewall rule rule-name] | Specify the direction in which the rule match is applied. | [
{
"name": "input",
"desc": "Apply the rule match on the input side of the interface."
},
{
"name": "output",
"desc": "Apply the rule match on the output side of the interface."
},
{
"name": "input-output",
"desc": "Apply the rule match bidirectionally."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Stateful Firewall Rules"
] |
match-direction | match-direction (input | output | input-output); | [edit services aacl rule rule-name] | Specify the direction in which the rule match is applied. | [
{
"name": "input",
"desc": "Apply the rule match on the input side of the interface."
},
{
"name": "output",
"desc": "Apply the rule match on the output side of the interface."
},
{
"name": "input-output",
"desc": "Apply the rule match bidirectionally."
}
] | 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 Match Direction for AACL Rules"
] |
match-list | match-list {
match-criteria {
(match-all | match-any);
}
prefix-list-name prefix-list-name;
source-ip-address-list address-list-name;
source-mac-address-list address-list-name;
} | [edit forwarding-options access-security router-advertisement-guard policy policy-name accept (Router
Advertisement Guard Policy)] | Configure one or more lists of IPv6 addresses, MAC addresses, or IPv6 address prefixes to be associated
with an IPv6 Router Advertisement (RA) guard accept policy.
RA guard protects against rogue RA messages generated either maliciously or unintentionally by
unauthorized or improperly configured routers connecting to t... | [
{
"name": "match-all",
"desc": "Configure the RA guard policy so that a received RA message is accepted only if it matches criteria in all of the lists configured under match-list; otherwise, the message is discarded."
},
{
"name": "match-any",
"desc": "Configure the RA guard policy so that a re... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
match-option | match-option {
hop-limit {
(maximum | minimum) value;
}
managed-config-flag;
other-config-flag;
router-preference maximum (high | low | medium);
} | [edit forwarding-options access-security router-advertisement-guard policy policy-name accept (Router
Advertisement Guard Policy)] | Configure one or more parameters such as hop-count limit, managed configuration flag, other
configuration flag, or router preference priority as the match condition to be associated with an IPv6
Router Advertisement (RA) guard accept policy.
RA guard protects against rogue RA messages generated either maliciously or un... | [
{
"name": "hop-limit",
"desc": "Configure the RA guard policy to verify the minimum or maximum hop count for an incoming RA message. Use maximum to set a maximum hop count, or minimum to set a minimum hop count."
},
{
"name": "managed-config-flag",
"desc": "Configure the RA guard policy to verif... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
match-order (Dynamic Firewalls) | match-order [match-order]; | [edit dynamic-profiles profile-name firewall family family fast-update-filter filter-name] | Specify the match conditions and the order in which the conditions are examined. Enclose a string of
multiple conditions in brackets. The router examines only the conditions you specify, and examines them
in the specified order. | [
{
"name": "match-order",
"desc": "One or more of the following conditions. Fast Update Filter Match Conditions describes the"
},
{
"name": "destination-address",
"desc": ""
},
{
"name": "destination-port",
"desc": ""
},
{
"name": "dscp (IPv4 only)",
"desc": ""
},
{
... | 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 Fast Update Filters",
"Configuring the Match Order for Fast Update Filters",
"Fast Update Filter Match Conditions"
] |
match-rules-on-reverse-flow (Next Gen Services) | match-rules-on-reverse-flow; | [edit services service-set service-set-name cos-options] | Configure the service set to create a CoS session even if a packet is first received in the reverse direction
of the matching direction of the CoS rule. The CoS rule values are then applied as soon as a packet in
the correct match direction is received. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2 on MX Series routers (MX240, MX480 and MX960)
running Next Gen Services with the MX-SPC3 services card. | [
"Class of Service for Services PICs (Next Gen Services)"
] |
match-rules-on-reverse-flow | match-rules-on-reverse-flow; | [edit services service-set service-set-name cos-options] | Configure the service set to create a CoS session even if a packet is first received in the reverse direction
of the matching direction of the CoS rule. The CoS rule values are then applied as soon as a packet in
the correct match direction is received. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R5 and 17.4R1. | [
"Configuring CoS Rules"
] |
match-strings | match-strings [match-strings];
match-strings [string1 string2]; | [edit system syslog file name],
[edit system syslog host name],
[edit system syslog user name] | Specify a text substring that must appear in a message that is logged to a destination. If multiple strings
are configured, the message is logged to the given destination if any of the substrings are matched.
The match-strings statement performs a simple string comparison, and as a result, it is less CPU-intensive
than... | [
{
"name": "string",
"desc": "String or list of strings against which to match messages to log. Range: 1 through 50 strings Range: 1 through 1020 characters per string"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Use Strings and Regular Expressions to Refine the Set of Logged Messages"
] |
matches (Event Policy) | event.attribute-name matches regular-expression; | [edit event-options policy policy-name attributes-match] | Configure an event policy to trigger only if the specified attribute of event matches the regular
expression. The referenced event must be either the trigger event or a correlating event included in the
event policy’s within statements.
An attributes-match statement can include multiple comparison statements. The syste... | [
{
"name": "event.attribute-name",
"desc": "Event attribute to compare to a regular expression."
},
{
"name": "regular-expression",
"desc": "Regular expression to compare."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Use Correlated Events to Trigger an Event Policy",
"Use Regular Expressions to Refine the Set of Events That Trigger a Policy"
] |
matches | matches {
apply-groups [group-names];
apply-groups-except [group-names];
value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from called-station-
id],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from calling-
station-id],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from class],
[edit unified-edge gate... | Specify the regular expression that the attribute must match.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
Table 71: Regular Expression Operators for the matches Statement
Operator
Matches... | [
{
"name": "value",
"desc": "Regular expression to match."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
max-advertisement-interval (Dynamic Router Advertisement) | max-advertisement-interval seconds; | [edit dynamic-profiles protocols router-advertisement interface interface-name] | Maximum interval between each router advertisement message. | [
{
"name": "seconds",
"desc": "Maximum 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. | [
"Configuring an Interval Range for Unsolicited Router Advertisements to IPv6 Neighbors",
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
max-advertisement-interval (Protocols IPv6 Neighbor Discovery) | max-advertisement-interval seconds; | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Set the maximum 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": "Maximum 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"
] |
max-advertisement-interval (Protocols Router Discovery) | max-advertisement-interval seconds; | [edit logical-systems logical-system-name protocols router-discovery interface interface-name],
[edit protocols router-discovery interface interface-name] | Specify the maximum time the router waits before sending periodic router advertisement packets out
the interface. These packets are broadcast or multicast, depending on how the address corresponding to
this physical interface is configured. | [
{
"name": "seconds",
"desc": "Maximum 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"
] |
max-age | max-age seconds; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-ins... | For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol
(VSTP), or Multiple Spanning Tree Protocol (MSTP), specifies the maximum expected arrival time of hello
BPDUs.
Default
20 seconds | [
{
"name": "seconds",
"desc": "(Optional) Number of seconds expected between hello BPDUs."
},
{
"name": "seconds",
"desc": "The maximum age of received protocol BPDUs."
}
] | 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 STP",
"Understanding MSTP",
"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 Stability with RSTP on EX Se... |
max-areas | max-areas number; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis]
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Modify the maximum number of IS-IS areas advertised.
This value is included in the Maximum Address Area field of the IS-IS common PDU header included in
all outgoing PDUs.
The maximum number of areas you can advertise is restricted to 36 to ensure that the IIH PDUs have
enough space to include other type, length, and v... | [
{
"name": "number",
"desc": "Maximum number of areas to include in the IS-IS hello (IIH) PDUs and link-state PDUs."
}
] | 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. | [
"Understanding IS-IS Areas to Divide an Autonomous System into Smaller Groups",
"Example: Configuring a Multi-Level IS-IS Topology to Control Interarea Flooding"
] |
max-burst-size | max-burst-size max-burst-size; | [edit class-of-service traffic-control-profiles traffic-control-profile-name],
[edit firewall atm-policer atm-policer-name] | (MX Series routers) Define ATM maximum burst size on ATM MICs in cells. | [
{
"name": "cells",
"desc": "ATM maximum burst size in cells."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"show class-of-service traffic-control-profile"
] |
max-bypasses | max-bypasses number; | [edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit protocols rsvp interface interface-name link-protection] | Specify the maximum number of dynamic bypass LSPs permitted for protecting this interface. When this
option is configured, multiple bypasses for link protection are enabled. Call admission control (CAC) is
also enabled. The limit on bypasses configured applies only to dynamically generated bypass LSPs. By
default, this... | [
{
"name": "number",
"desc": "Configure the maximum number of bypass LSPs. If you configure a value of 0, no dynamic bypass"
}
] | 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.
Range modified in Junos OS Release 9.3. | [
"Configuring the Maximum Number of Bypass LSPs"
] |
max-checked-bytes | max-checked-bytes bytes; | [edit services application-identification] | Specify the maximum number of bytes to be inspected. | [
{
"name": "bytes",
"desc": "Maximum 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"
] |
max-configurations-on-flash (System) | max-configurations-on-flash number; | [edit system] | Specify the number of configurations stored on the CompactFlash card. | [
{
"name": "number",
"desc": "The number of configurations stored on the CompactFlash card. Range: 0 through 49. The most recently saved configuration is number 0, and the oldest saved configuration is number 49."
}
] | 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. | [
"Using Junos OS to Specify the Number of Configurations Stored on the CompactFlash Card"
] |
max-connection-duration | max-connection-duration hours; | [edit services rpm twamp server] | Specify the maximum time a connection can exist between a client and the server. | [
{
"name": "hours",
"desc": "Number of hours a connection can exist between a client and the server. Default: 24 Range: 0-120"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
max-connections | max-connections max-connections; | [edit system services extension-service request-response grpc] | Number of simultaneous connections for request-response that can be attached to jsd. The higher the
number, the higher the impact on clients performance. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [] |
max-data-sessions-per-subscriber | max-data-sessions-per-subscriber {
limit max-sub-sessions;
exceed-action {
drop;
syslog;
}
} | [edit services service-set services-set-name subscriber-profile profile-name] | Specify the maximum number of sessions that are concurrently enabled for the named service. The
system randomly selects a number of sessions and enables the named service for them. To limit the
service’s use of resources, other sessions cannot access these named services.
The remaining statements are explained separate... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
max-datasize | max-datasize size; | [edit event-options event-script],
[edit system extension extension-service application],
[edit system scripts commit],
[edit system scripts op],
[edit system scripts snmp],
[edit system scripts translation] | Configure the maximum amount of memory allocated for the data segment during execution of a script
of the configured type. The device sets the maximum memory limit for the executing script to the
configured value irrespective of the total memory available on the system at the time of execution. If the
executing script ... | [
{
"name": "size",
"desc": "Maximum amount of memory allocated for the data segment during execution of a script of the given type. If you do not specify a unit of measure, the default is bytes. The listed limits apply to the following types of scripts: commit, event, op, SNMP, translation, and extension ser... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.3.
Support at the [edit system extension extension-service application] hierarchy level introduced in Junos OS
Release 16.1 for MX80, MX104, MX240, MX480, MX960, MX2010, MX2020, and vMX.
Support at the [edit system scripts translation] hierarchy level introduced in Junos OS R... | [
"Understanding Limits on Executed Event Policies and Memory Allocation for Scripts",
"Example: Configure Limits on Executed Event Policies and Memory Allocation for Scripts"
] |
max-db-size (Enhanced Subscriber Management) | max-db-size size; | [edit system configuration-database] | Specify the maximum amount of system shared memory that is available for the Junos OS configuration
database and the schema database, together. Starting in Junos OS Release 20.1R1, Junos OS uses a
single memory map for both the configuration and schema databases.
In Junos OS Release 19.4Rx and lower-numbered releases, ... | [
{
"name": "size",
"desc": "Specifies the portion of system shared memory, in megabytes (MB), that is allocated for the Junos configuration database. Syntax: size M to specify MB Default: 698,343,424 bytes, only when running Junos OS Release 17.4R1, enhanced IP network services and enhanced subscriber mana... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3. | [
"Configuring Junos OS Enhanced Subscriber Management",
"Junos OS Enhanced Subscriber Management Overview"
] |
max-drop-flows | max-drop-flows {
ingress ingress-flows;
egress egress-flows;
} | [edit services service-set service-set-name] | Configure the maximum drop flows allowed per ingress and egress direction. The configuration is per
service set. The configured limits indicate the maximum number of drop flows that can be created at a
given instance of time in both directions. If max drop flows ingress is 10 and egress is 5 then at a given
instance of... | [
{
"name": "ingress-flows",
"desc": "Maximum number of drop flows on the ingress interface."
},
{
"name": "egress-flows",
"desc": "Maximum number of drop flows on the egress interface."
}
] | 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 | [
"Configuring Service Set Limitations"
] |
max-duplicates | max-duplicates number; | [edit services dynamic-flow-capture capture-group client-name] | Specify the maximum number of content destinations to which the DFC PIC can send data from a single
input set of packets. Limiting the number of duplicates reduces the load on the PIC. This setting
overrides the globally applied g-max-duplicates setting.
Default
If no value is configured, a default setting of 3 is used... | [
{
"name": "number",
"desc": "Maximum number of content destinations."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Limiting the Number of Duplicates of a Packet"
] |
max-failures | max-failures max-failures; | [edit logical-systems name protocols ppp-service],
[edit protocols ppp-service] | The max-failures statement enables you to define the maximum number of failure attempts allowed while
establishing the Point-to-Point Protocol (PPP) service. | [
{
"name": "max-failures",
"desc": "Specify the maximum number of failure attempts allowed while establishing the PPP service. Range: 1 through 10 Default: 5"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [] |
max-flows | max-flows number; | [edit services service-set service-set-name] | Maximum number of flows allowed for the service set. | [
{
"name": "number",
"desc": "Maximum number of flows."
}
] | 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 Service Set Limitations"
] |
max-hops | max-hops hops; | [edit logical-systems logical-system-name protocols mstp],
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols mstp],
[edit protocols mstp],
[edit routing-instances routing-instance-name protocols mstp] | Configure the maximum number of hops a BPDU can be forwarded in the MSTP region. | [
{
"name": "hops",
"desc": "(Optional) Number of hops the BPDU can be forwarded."
},
{
"name": "20 hops",
"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.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding MSTP",
"Configuring Multiple Spanning Tree Protocol",
"Configuring MSTP on Switches",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Understanding MSTP"
] |
max-login-sessions | max-login-sessions max-login-sessions; | [edit fc-fabrics fc-fabric-name], [edit fc-fabrics fc-fabric-name interface interface-name] | Set the maximum number of FCoE initialization protocol (FIP) session logins permitted for an individual
NP_Port interface in an FCoE-FC gateway fabric (FC fabric) or for the entire FCoE-FC gateway fabric.
You can set a maximum FIP session limit for each NP_Port interface connected to an FC switch. You can
also set a ma... | [
{
"name": "max-login-sessions",
"desc": "Maximum number of FIP login sessions."
}
] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Setting the Maximum Number of FIP Login Sessions per FC Interface",
"Setting the Maximum Number of FIP Login Sessions per FC Fabric",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
max-login-sessions-per-node | max-login-sessions-per-node max-login-sessions-per-node; | [edit fc-options] | Set the maximum number of FCoE initialization protocol (FIP) session logins permitted on a Node device.
(This is the combined total of all VN2VF_Port and VN2VN_Port sessions on the Node device.)
On a QFX3500 switch, the max-login-sessions-per-node command sets the maximum FIP session login
limit for all of the FC fabri... | [
{
"name": "max-login-sessions-per-node",
"desc": "Maximum number of FIP login sessions."
}
] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Setting the Maximum Number of FIP Login Sessions per Node Device",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
max-lsp-size | max-lsp-size size; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis]
[edit logical-systems logical-system-name protocols isis level],
[edit logic... | Modify the maximum size of IS-IS link-state PDUs. IS-IS sends link-state PDUs out of IS-IS enabled
interfaces to distribute routing information between the IS-IS nodes. You can configure the maximum lsp
size per level or at the global level. If configured at both global and per level, the per level setting takes
preced... | [
{
"name": "size",
"desc": "Maximum size allocated for IS-IS link-state PDUs. Range: 512 through 9192 bytes Default: 1492 bytes"
}
] | 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.
Per Level statement introduced in Junos OS Release 23.1 | [
"Understanding IS-IS Configuration",
"Example: Configuring IS-IS"
] |
max-message-length | max-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 max-message-length option to set the maximum message payload length (in
bytes). The maximum GTP message length is 65,535 bytes. The message length range is from 1 through
65,535 bytes.
From... | [
{
"name": "number",
"desc": "To set the maximum 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"
] |
max-outstanding-requests (Diameter Applications) | max-outstanding-requests number; | [edit access gx-plus global],
[edit access ocs partition partition-name],
[edit access pcrf partition partition-name] | Limit the number of outstanding requests that the Diameter-based application (function) can retry to a
remote server when the requests are improperly answered. Too many requests risks overloading the
server and increases the chance of losing messages.
The gx-plus statement limits retries from the Gx-Plus function to th... | [
{
"name": "number",
"desc": "Number of outstanding requests from the function to the server that can exist at any time."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
Support for OCS and PCRF partitions introduced in Junos OS Release 16.2 for MX Series routers. | [
"Configuring Gx-Plus Global Attributes",
"Configuring Gx-Plus",
"Configuring the OCS Partition",
"Configuring the PCRF Partition",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Gy Interactions Between the Router and the OCS"
] |
max-packet-memory-ratio | max-packet-memory-ratio percentage-value; | [edit security idp sensor-configuration application-identification] | By default, the amount of IDP memory used for application identification packet memory is established
as a percentage of all IDP memory. In most cases, the default value is adequate.
If a deployment exhibits an excessive number of ignored IDP sessions due to application identification
memory allocation failures, use th... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D20. | [] |
max-packets-per-second (Sampling) | max-packets-per-second number; | [edit forwarding-options sampling input],
[edit forwarding-options sampling instance instance-name input] | Specify the traffic threshold that must be exceeded before packets are dropped. A value of 0 instructs
the Packet Forwarding Engine not to sample any traffic.
NOTE: The max-packets-per-second statement is not supported when you configure inline
flow monitoring (by including the inline-jflow statement at the [edit forwa... | [
{
"name": "number",
"desc": "Maximum number of packets per second."
}
] | 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 Traffic Sampling on MX, M and T Series Routers",
"Configuring Traffic Sampling"
] |
max-pending-accounting-stops (Access Profile) | max-pending-accounting-stops number; | [edit access accounting-backup-options] | Set the maximum number of pending accounting stop requests that the router backs up while all the
RADIUS accounting servers in the profile are offline. | [
{
"name": "number",
"desc": "Number of stops to hold. Range: 1 through 168,000 Default: 168,000"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"Configuring Back-up Options for RADIUS Accounting"
] |
max-policies (Event Policy) | max-policies policies; | [edit event-options] | Define the maximum number of event policies that can run concurrently on the device. | [
{
"name": "policies",
"desc": "Maximum number of event policies that can run concurrently. Range: 0 through 20 Default: 15"
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Understanding Limits on Executed Event Policies and Memory Allocation for Scripts",
"Example: Configure Limits on Executed Event Policies and Memory Allocation for Scripts"
] |
max-power | max-power watts; | [edit chassis psm] | For the PTX10001-36MR router— Override the maximum power value of a power supply module (PSM)
by specifying a lesser power value (in watts). You can use this configuration to monitor the power
consumed in real time against the configured value. The system raises a chassis alarm when the
consumption exceeds the configur... | [
{
"name": "watts",
"desc": "Specify power value (in watts) with which you want to override the default/maximum power."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | The max-power watts statement introduced in Junos OS Evolved Release 20.1R2 for PTX10008 routers.
The max-power watts statement introduced in Junos OS Evolved Release 20.2R1 for PTX10001-36MR
routers. | [] |
max-queues | max-queues queues-per-line-card; | [edit chassis fpc slot-number] | Configure the maximum number of queues allowed per line card in an MX240, MX480, MX960,
MX2008, MX2010, MX2020, MX10001, MX10002 router or fixed MIC with XFP in an MX5, MX10,
MX40, MX80, MX104, MX304 modular chassis router.
Reducing the number of queues allowed in a hierarchical scheduling environment in turn reduces t... | [
{
"name": "queues-per-line-",
"desc": ""
},
{
"name": "card",
"desc": "Maximum number of queues allowed for the line card. Only the following keywords are valid: 8k, 16k, 32k, 48k, 64k, 96k, 128k, 192k, 256k, 384k, 512k, 768k, 1M, 1536k, or 2M. Built-in 10-Gigabit Ethernet MICs and MPC1 Q line ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2.
Support for MPC7E, MPC8E, and MPC9E from Junos OS Release 15.1F4.
Starting with Junos OS Release 24.4R2, the configured max-queues value is divided by the maximum
number of PFEs supported on the FPC. For example on an MX304, which can have a maximum of six
PFEs, if you set... | [
"Jitter Reduction in Hierarchical CoS Queues",
"MPC1 Q",
"MPC2 Q",
"MPC2 EQ",
"MIC/MPC Compatibility",
"10-Gigabit Ethernet MICs with XFP"
] |
max-queues-per-interface | max-queues-per-interface (8 | 4); | [edit chassis fpc slot-number pic pic-number],
[edit chassis lcc number fpc slot-number pic pic-number] | On IQ, MPC, and DPC interfaces on M120, T320, T640, T1600, TX Matrix, and TX Matrix Plus routers,
or on MIC or MPC interfaces on MX Series routers, set the number of egress queues per port to four or
eight.
NOTE: If you include the max-queues-per-interface 8 statement, the configuration at the
[edit class-of-service] h... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for TX Matrix and TX Matrix Plus added in Junos OS Release 9.6. | [
"Configuring the Junos OS to Support Eight Queues on IQ Interfaces for T Series and M320 Routers",
"Configuring Up to 16 Custom Forwarding Classes",
"Enabling Eight Queues on ATM Interfaces",
"Configuring the Maximum Number of Queues for Trio MPC/MIC Interfaces",
"Example: Configuring CoS on SRX5000 Devices... |
max-reass-packet-memory-ratio | max-reass-packet-memory-ratio percentage-value; | [edit security idp sensor-configuration application-identification] | By default, the amount of IDP memory used for packet memory by the application identification
reassembler is established as a percentage of all IDP memory. In most cases, the default value is
adequate.
If a deployment exhibits an excessive number of ignored IDP sessions due to packet memory limitations
of the applicati... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D20. | [] |
max-retrans-time | max-retrans-time seconds; | [edit logical-systems logical-system-name protocols rip group group-name],
[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 pr... | RIP demand circuits send update messages every 5 seconds to an unresponsive peer. Configure the
retransmission timer to limit the number of times the demand circuit resends update messages to an
unresponsive peer. If the configured retransmission threshold is reached, routes from the next hop
router are marked as unrea... | [
{
"name": "seconds",
"desc": "The total amount of time the demand circuit resends update messages to an unresponsive"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Configuring RIP Demand Circuits",
"RIP Demand Circuits Overview"
] |
max-session-number | max-session-number number; | [edit security nat source rule-set ruleset rule rule then source-nat interface persistent-nat]
[edit security nat source rule-set ruleset rule rule then source-nat pool persistent-nat] | The maximum number of the sessions with which a persistent NAT binding can be associated. For
example, if the max-session-number of the persistent NAT rule is 65,536, then a 65,537th session cannot be
established if that session uses the persistent NAT binding created from the persistent NAT rule. | [
{
"name": "number",
"desc": "Maximum number of sessions."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration | Statement introduced in Junos OS Release 9.6. | [] |
max-session-setup-rate (Service Set) | max-session-setup-rate (number | numberk); | [edit services service-set service-set-name] | Set the maximum number of session setups allowed per second for the service set. After this setup rate
is reached, any additional session setup attempts are dropped. If you do not include the max-session-setup-
rate statement, the session setup rate is not limited. | [
{
"name": "max-session-setup-rate",
"desc": ""
},
{
"name": "number",
"desc": "Use the specified maximum number of session setups per second. Range: 1 through 429,496,729 Default: 0 (The session setup rate is not limited.)"
},
{
"name": "numberk",
"desc": "Maximum number of session... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1R1.
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. | [
"Configuring Service Set Limitations"
] |
max-sessions (Dynamic PPPoE) | max-sessions number; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit dynamic-profiles profile-name interfaces interface-set interface-set-name pppoe-underlying-
options]
[edit interface... | Configure the maximum number of dynamic PPPoE logical interfaces that the router can activate on the
underlying interface. The max-sessions value does not affect the maximum number of static PPPoE logical
interfaces that can be configured on the underlying interface.
NOTE: The [edit ... family pppoe] hierarchies and th... | [
{
"name": "number",
"desc": "Maximum number of dynamic PPPoE logical interfaces (sessions) that the router can activate on"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
Support for the [edit ... family pppoe] hierarchies introduced in Junos OS Release 11.2.
Support at the [edit dynamic-profiles ... interfaces interface-set ... pppoe-underlying-options] hierarchy level
introduced in Junos OS Release 12.2. | [
"Limiting the Maximum Number of PPPoE Sessions on the Underlying Interface",
"Defining ACI Interface Sets",
"PPPoE Maximum Session Limit Overview",
"Guidelines for Using PPPoE Maximum Session Limit from RADIUS",
"Juniper Networks VSAs Supported by the AAA Service Framework",
"Configuring an Interface Set ... |
max-sessions (PPPoE Service Name Tables) | max-sessions number; | [edit protocols pppoe service-name-tables table-name service service-name] | Configure the maximum number of active PPPoE sessions using either static or dynamic PPPoE
interfaces that the router can establish with the specified named service, empty service, or any service
entry in a PPPoE service name table. The router maintains a count of active PPPoE sessions for each
service entry to determi... | [
{
"name": "number",
"desc": "Maximum number of active PPPoE sessions that the router can establish with the specified"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name",
"Configuring PPPoE Service Name Tables",
"PPPoE Maximum Session Limit Overview",
"Configuring an Interface Set of Subscribers in a Dynamic Profile",
"Subscriber Interfaces and PPPoE Overview"
] |
max-sessions (Security Packet Log) | max-sessions <percentage>;
per-logical-domain <number> | [edit security idp sensor-configuration packet-log] | Configure the maximum number of sessions actively conducting pre-attack packet captures on a device
at one time. This value is expressed as a percentage of the maximum number of IDP sessions for the
device. | [
{
"name": "percentage",
"desc": "Maximum number of packet capture sessions expressed as a percentage of the IDP session"
}
] | 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. | [] |
max-sessions (Tunnel Profile) | max-sessions number; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify the maximum number of sessions allowed in the tunnel. | [
{
"name": "number",
"desc": "Maximum number of sessions allowed in the tunnel. A value of 0 means that the maximum"
}
] | 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"
] |
max-sessions-per-connection | max-sessions-per-connection number | [edit system services ssh] | Specify the maximum number of ssh sessions allowed per single SSH connection. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configure SSH Service for Remote Access to the Router or Switch",
"Security Services Administration Guide"
] |
max-sessions-per-enode | max-sessions-per-enode max-sessions-per-enode; | [edit fc-fabrics fc-fabric-name protocols fip] | Set the maximum number of FCoE login sessions (FLOGI plus FDISC) from a single ENode allowed on
the gateway FC fabric (the fabric configured on the QFabric system). The maximum number of logins per
ENode is 2000 sessions.
NOTE: A session is a FLOGI or FDISC login to the FC SAN fabric. Session does not refer
to end-to-e... | [
{
"name": "max-sessions-per-enode",
"desc": "Maximum number of FCoE sessions a single ENode can establish on the"
}
] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring FIP on an FCoE-FC Gateway",
"Understanding FIP Parameters on an FCoE-FC Gateway"
] |
max-sessions-per-subscriber (Service Set Next Gen Services) | max-sessions-per-subscriber session-number; | [edit services service-set service-set-name service-set-options] | Set the maximum number of sessions allowed from a single subscriber. | [
{
"name": "session-number",
"desc": "Maximum number of sessions. NOTE: There is no default value. You must configure a value for the configuration to take effect. Range: 1 through 32000"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
max-sessions-per-subscriber | max-sessions-per-subscriber session-number; | [edit services service-set service-set-name nat-options] | Set the maximum number of sessions from a single subscriber allowed for NAPT-44. This statement
does not apply to other types of NAT. The maximum number of sessions per subscriber is 32,000
sessions.
NOTE: If you do not configure this statement, there is no limit to the number of sessions
a subscriber can have. | [
{
"name": "session-number",
"desc": "Maximum number of sessions a single subscriber can establish for NAPT-44."
}
] | 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. | [
"Configuring Service Rules"
] |
max-sessions-vsa-ignore (Static and Dynamic Subscribers) | max-sessions-vsa-ignore; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number pppoe-
underlying-options],
[edit in... | Configure the router to ignore (clear) the value returned by RADIUS in the Max-Clients-Per-Interface
Juniper Networks vendor-specific attribute (VSA) [26-143], and restore the PPPoE maximum session
value on the underlying interface to the value configured in the CLI with the max-sessions statement. The
PPPoE maximum se... | [] | 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. | [
"Limiting the Maximum Number of PPPoE Sessions on the Underlying Interface",
"PPPoE Maximum Session Limit Overview",
"Guidelines for Using PPPoE Maximum Session Limit from RADIUS",
"Juniper Networks VSAs Supported by the AAA Service Framework",
"Configuring an Interface Set of Subscribers in a Dynamic Profi... |
max-snp-size | max-snp-size size; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Modify the maximum size of partial or complete IS-IS sequence number PDUs. IS-IS sends sequence
number packets out of IS-IS enabled interfaces to control the distribution of link-state PDUs between
the IS-IS nodes. Sequence number packets provide a mechanism to synchronize the link-state databases
of routers in the sam... | [
{
"name": "size",
"desc": "Maximum size allocated for sequence number of partial or complete IS-IS packets. Range: 512 through 1400 bytes Default: 1400 bytes"
}
] | 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 IS-IS Configuration",
"Example: Configuring IS-IS"
] |
max-tcp-session-packet-memory | max-tcp-session-packet-memory value; | [edit security idp sensor-configuration application-identification] | Specify the maximum number of TCP sessions that IDP maintains. If the sensor reaches the maximum, it
drops all new TCP sessions. | [
{
"name": "value",
"desc": "Maximum number of TCP sessions."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
max-time-report | max-time-report value; | [edit security idp sensor-configuration log suppression] | When log suppression is enabled, IDP maintains a count of multiple occurrences of the same event.
After the specified number of seconds has passed, IDP writes a single log entry containing the count of
occurrences. | [
{
"name": "value",
"desc": "Time after which IDP writes a single log entry containing the count of occurrences."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
max-transmit-quality-level | max-transmit-quality-level; | [edit chassis synchronization] | st4
Clock traceable to Stratum 4 free-run (option-2 only).
stu
Clock traceable to an unknown quality (option-2 only).
tnc
Clock traceable to a transit node clock (option-2 only). | [
{
"name": "quality-level",
"desc": "The available quality levels are as given in Table 73 on page 10926. Table 73: Quality Levels Quality Level"
}
] | 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. | [] |
max-udp-session-packet-memory | max-udp-session-packet-memory value; | [edit security idp sensor-configuration application-identification] | Specify the maximum number of UDP sessions that IDP maintains. If the sensor reaches the maximum,
it drops all new UDP sessions. | [
{
"name": "value",
"desc": "Maximum number of UDP sessions."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
max-unknown-messages | max-unknown-messages messages-per-minute; | [edit protocols pcep pce pce-id] | Specify the number of unknown messages per minute that the Path Computation Client (PCC) can
receive at maximum after which the PCEP session is closed. | [
{
"name": "messages-per-minute",
"desc": "Number of unknown messages per minute that the PCC can receive at maximum after which the PCEP session is closed. Recommended value is 5. If the number of unknown messages received by the PCC is greater than or equal to the maximum number, the PCEP session is closed... | 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 switches added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1. | [] |
max-unknown-requests | max-unknown-requests requests-per-minute; | [edit protocols pcep pce pce-id]
[edit protocols pcep pce-group group-id] | Specifies the number of unknown requests per minute that the Path Computation Client (PCC) can
receive at maximum after which the PCEP session is terminated. | [
{
"name": "requests-per-minute",
"desc": "Number of unknown requests per minute that the PCC can receive at maximum after which the PCEP session is terminated. Range: 0 through 16384 (0 disables this statement) Default: 5"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [] |
max-withhold-time (Access Profile) | max-withhold-time hold-time; | [edit access accounting-backup-options] | Set the timer that determines how long the router holds pending accounting stop requests. Any
remaining accounting stop messages are flushed when the timer expires, even if the accounting server is
again online. | [
{
"name": "hold-time",
"desc": "Number of minutes. Range: 1 through 1440 Default: 60"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"Configuring Back-up Options for RADIUS Accounting"
] |
maximize-idp-sessions | maximize-idp-sessions {
weight (Security) (equal | firewall | idp);
} | [edit security forwarding-process application-services] | If you are deploying IDP policies, you can tune the device to increase IDP session capacity. By using the
provided commands to change the way the system allocates resources, you can achieve a higher IDP
session capacity. See weight for information about the options provided.
This statement is supported on SRX1500, SRX ... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Understanding Traffic Processing on Security Devices"
] |
maximum (MSDP Active Source Messages) | maximum number; | [edit logical-systems logical-system-name protocols msdp active-source-limit],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols msdp
active-source-limit],
[edit protocols msdp active-source-limit],
[edit routing-instances routing-instance-name protocols msdp active-source-lim... | Configure the maximum number of MSDP active source messages the router accepts. | [
{
"name": "number",
"desc": "Maximum number of active source messages."
}
] | 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"
] |
maximum (PIM Entries) | maximum limit; | [edit logical-systems logical-system-name protocols pim sglimit],
[edit logical-systems logical-system-name protocols pim sglimit family],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
sglimit],
[edit logical-systems logical-system-name routing-instances routing-instan... | Configure the maximum number of specified PIM entries received by the device. If the device reaches
the configured limit, no new entries are received.
NOTE: The maximum limit settings that you configure with the maximum and the family
(inet | inet6) maximum statements are mutually exclusive. For example, if you config... | [
{
"name": "limit",
"desc": "Maximum number of PIM entries received by the device. If you configure both the log-interval and"
}
] | 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. | [] |
maximum | maximum number; | [edit interfaces interface-name services-options session-limit] | Specify the maximum number of sessions allowed simultaneously on services cards. If you specify the
maximum number of sessions to be zero, it indicates that the configuration is not effective. You must
specify a value higher than zero for the maximum number of sessions. | [
{
"name": "number",
"desc": "Maximum number of sessions. Range: 1 through 4,294,967,295"
}
] | 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.
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. | [] |
maximum-age | maximum-age minutes; | [edit services flow-collector transfer-log-archive] | Maximum age of transfer log file. | [
{
"name": "minutes",
"desc": "Transfer log file age."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Transfer Logs"
] |
maximum-allowed-contentions | maximum-allowed-contentions {
count integer;
duration seconds;
} | [edit forwarding-options access-security slaac-snooping interface (interface-name | all)] | Configure the maximum number of Duplicate Address Detection (DAD) contentions for an interface.
DAD is used by IPv6 clients to verify the uniqueness of addresses obtained through stateless address
auto-configuration (SLAAC). DAD sends a Neighbor Solicitation message destined to the new address. If
there is a reply, the... | [
{
"name": "count integer",
"desc": "Configure the number of DAD contentions permitted on the interface."
},
{
"name": "duration seconds",
"desc": "Configure the length of the interval during which the maximum allowed contentions can not be exceeded."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"IPv6 Stateless Address Auto-configuration (SLAAC) Snooping"
] |
maximum-backoff-duration | maximum-backoff-duration milliseconds; | [edit protocols ovsdb controller] | Specify (in milliseconds) how long a Juniper Networks device that supports the Open vSwitch Database
(OVSDB) management protocol waits before it tries again to connect with a software-defined
networking (SDN) controller after a previous attempt has failed. | [
{
"name": "milliseconds",
"desc": "Number of milliseconds a Juniper Networks device waits before it tries again to connect"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Understanding How to Set Up OVSDB Connections on a Juniper Networks Device"
] |
maximum-bandwidth (Protocols MPLS) | maximum-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] | Specify the maximum amount of bandwidth in bits per second (bps). | [
{
"name": "bps",
"desc": "Maximum amount of bandwidth."
}
] | 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"
] |
maximum-bandwidth | maximum-bandwidth bps; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast interface interface-name],
[edit logical-systems logical-system-name routing-options multicast interface interface-name],
[edit routing-instances routing-instance-name routing-options multicast interface interfa... | Configure the multicast bandwidth for the interface. | [
{
"name": "bps",
"desc": "Bandwidth rate, in bits per second, for the multicast interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Example: Defining Interface Bandwidth Maximums"
] |
maximum-bit-rate (Default Local Policy) | maximum-bit-rate uplink mbr-uplink-value downlink mbr-downlink-value; | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber default-local-
policy] | Configure the maximum bit rate (MBR) for a subscriber’s uplink and downlink traffic entering or exiting
the access interface of the TDF domain when a TDF IP-based subscriber session does not exist. Uplink
traffic originates from the subscriber towards the public data network (PDN), and downlink traffic comes
from the P... | [
{
"name": "mbr-uplink-value",
"desc": "MBR value for the uplink direction. Range: 0 through 6144000 Kbps."
},
{
"name": "mbr-downlink-value",
"desc": "MBR value for the downlink direction. Range: 0 through 6144000 Kbps."
}
] | 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-bit-rate (PCC Action Profiles) | maximum-bit-rate uplink mbr-uplink-value downlink mbr-downlink-value; | [edit unified-edge pcef pcc-action-profiles profile-name],
[edit services pcef pcc-action-profiles profile-name] | Specify the maximum bit rate (MBR) that you want a PCC action profile to use for uplink and downlink
traffic.
If you are using Junos OS Subscriber Aware, specify the MBR at the [edit unified-edge pcef pcc-action-
profiles profile-name hierarchy level.
If you are using Junos OS Broadband Subscriber Management, specify t... | [
{
"name": "mbr-uplink-value",
"desc": "MBR value for the uplink direction. Range: 1 through 6144000 Kbps."
},
{
"name": "mbr-downlink-value",
"desc": "MBR value for the downlink direction. Range: 1 through 6144000 Kbps."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Junos... | [
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Application-Aware Po... |
maximum-bit-rate (TDF Domain) | maximum-bit-rate {
apply-groups [group-names];
apply-groups-except [group-names];
downlink mbr-downlink-value;
uplink mbr-uplink-value;
} | [edit unified-edge gateways tdf gateway-name domains domain-name] | Configure the TDF domain’s default TDF subscriber maximum bit rate (MBR) for uplink and downlink
traffic. Uplink traffic originates from the subscriber towards the public data network (PDN), and
downlink traffic comes from the PDN and is destined for the subscriber. | [
{
"name": "mbr-downlink-value",
"desc": "MBR value for the downlink direction. Range: 0 through 1,048,000 Kbps."
},
{
"name": "mbr-uplink-value",
"desc": "MBR value for the uplink direction. Range: 0 through 6,144,000 Kbps."
}
] | 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",
"Configuring IFL-Based TDF Subscribers and Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based and IFL-Based TDF Subscribers Overview",
"IP-Based Sub... |
maximum-call-duration (Security) | maximum-call-duration value-in-minutes; | [edit security alg mgcp],
[edit security alg sip] | Specify the time at which the SIP call ends. The media session is released after the call has ended. | [
{
"name": "value-in-minutes",
"desc": "Maximum amount of time at which the call ends and releases the media sessions."
}
] | 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. | [] |
maximum-capture-size (Datapath Debug) | maximum-capture-size maximum-capture-size; | [edit security datapath-debug] | Specifies maximum packet capture length. | [
{
"name": "maximum-capture-size maximum-capture-size",
"desc": "Specify the maximum packet capture length."
}
] | 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. | [
"System Log Messages"
] |
maximum-certificates | maximum-certificates number; | [edit security certificates] | (Encryption interface on M Series and T Series routers and EX Series switches only) Configure the
maximum number of peer digital certificates to be cached. | [
{
"name": "number",
"desc": "Maximum number of peer digital certificates to be cached."
}
] | 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 the Maximum Number of Peer Certificates"
] |
maximum-connections | maximum-connections count; | [edit services rpm twamp server] | Configure the maximum number of allowed connections between the server and all control client hosts.
NOTE: The maximum number of connections between the server and all control client
hosts must be greater than or equal to the number of connections between the server
and a single controlled client host. | [
{
"name": "count",
"desc": "Maximum number of connections."
}
] | 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-connections-per-client | maximum-connections-per-client count; | [edit services rpm twamp server] | Configure the maximum number of allowed connections between the server and a single control client
host.
NOTE: The maximum number of connections between the server and all control client
hosts must be greater than or equal to the number of connections between the server
and a single controlled client host. | [
{
"name": "count",
"desc": "Maximum number of connections."
}
] | 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-contexts | maximum-contexts number <force>; | [edit interfaces interface-name unit logical-unit-number compression rtp],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
compression rtp] | Specify the maximum number of RTP contexts to accept during negotiation. | [
{
"name": "number",
"desc": "Maximum number of contexts."
},
{
"name": "force",
"desc": "(Optional) Requires the PIC to use the value specified for maximum RTP contexts, regardless of"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configuring Compression of Voice Traffic"
] |
maximum-discovery-table-entries | maximum-discovery-table-entries entry-number; | [edit protocols ancp],
[edit protocols ancp neighbor ip-address] | Specify the maximum number of discovery table entries accepted from all ANCP neighbors or from a
particular ANCP neighbor. The number of entries configured for an individual neighbor supersedes the
global value. The neighbor can continue to update previously created entries when the maximum has
been exceeded, but no ne... | [
{
"name": "entry-number",
"desc": "Maximum number of discovery table entries."
}
] | 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. | [
"Configuring the ANCP Agent",
"Configuring ANCP Neighbors"
] |
maximum-ecmp | maximum-ecmp next-hops; | [edit chassis] | (MX Series) Configure 16, 32, or 64, and 128 ECMP next hops for RSVP or LDP LSPs, or MPLS static
LSPs that are configured using set protocols mpls static-label-switched-path.
This command is used to control the maximum number of ECMP legs in an NH. This command applies to
all protocols, and the maximum configurable ECM... | [
{
"name": "next-hops",
"desc": "Specify the number of next hops (16, 32, 64, or 128) for RSVP or LDP LSPs, or MPLS static"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring ECMP Next Hops for RSVP and LDP LSPs for Load Balancing"
] |
maximum-helper-recovery-time | maximum-helper-recovery-time seconds; | [edit protocols rsvp graceful-restart],
[edit logical-systems logical-system-name protocols rsvp graceful-restart] | Specify the length of time the router or switch retains the state of its Resource Reservation Protocol
(RSVP) neighbors while they undergo a graceful restart. | [
{
"name": "seconds",
"desc": "Legnth of time that the router retains the state of its Resource Reservation Protocol (RSVP)"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Graceful Restart Options for RSVP, CCC, and TCC"
] |
maximum-helper-restart-time (RSVP) | maximum-helper-restart-time seconds; | [edit protocols rsvp graceful-restart],
[edit logical-systems logical-system-name protocols rsvp graceful-restart] | Specify the length of time the router or switch waits after it discovers that a neighboring router has
gone down before it declares the neighbor down. This value is applied to all RSVP neighbor routers and
should be based on the time that the slowest RSVP neighbor requires for restart. | [
{
"name": "seconds",
"desc": "The time the router or switch waits after it discovers that a neighboring router has gone down"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring Graceful Restart Options for RSVP, CCC, and TCC"
] |
maximum-helper-restart-time | maximum-helper-restart-time seconds; | [edit protocols ancp] | Specify how long other router processes wait for the ANCP agent to restart before considering it to be
down. | [
{
"name": "seconds",
"desc": "Number of seconds other processes wait for ANCP to restart."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring the ANCP Agent",
"Specifying How Long Processes Wait for the ANCP Agent Restart to Complete"
] |
maximum-hop-count | maximum-hop-count number; | [edit forwarding-options helpers bootp],
[edit forwarding-options helpers bootp interface (interface-name | interface-group)] | Set the maximum allowed number of hops. This value is compared against the hops field in the BOOTP
request message. BOOTP request messages that have a number in the hops field that exceeds maximum-
hop-count are not forwarded. If you omit the maximum-hop-count statement, the default value is four hops. | [
{
"name": "number",
"desc": "Maximum number of hops for BOOTP request messages."
}
] | 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"
] |
maximum-labels | maximum-labels maximum-labels; | [edit interfaces interface-name unit logical-unit-number family mpls],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family mpls] | On the logical interface, specify the maximum number of MPLS labels upon which MPLS can operate. | [
{
"name": "maximum-labels",
"desc": "Maximum number of labels for the protocol family."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring the Maximum Number of MPLS Labels",
"Junos OS VPNs Library for Routing Devices"
] |
maximum-lease-time (DHCP) | maximum-lease-time seconds; | [edit system services dhcp] | For J Series Services Routers and EX Series switches only. Specify the maximum length of time in
seconds for which a client can request and hold a lease on a DHCP server.
An exception is that the dynamic BOOTP lease length can exceed the maximum lease length specified. | [
{
"name": "seconds",
"desc": "The maximum number of seconds the lease can be held."
}
] | 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. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.