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 |
|---|---|---|---|---|---|---|---|
distribution-profile | distribution-profile (fat-core | name) {
description description;
fpc fpc {
pic pic {
thread-id thread-id;
}
}
} | [edit security] | The distribution-profile option is introduced to give the administrator an option to define a profile to
handle tunnels associated with a certain VPN object. If the default profiles such as default-spc3-profile or
default-spc2-profile are not selected, a new user-defined profile can be created. In a profile, you should... | [
{
"name": "description",
"desc": "Text description of the distribution profile."
},
{
"name": "fpc",
"desc": "FPC slot number."
},
{
"name": "pic",
"desc": "PIC slot number."
},
{
"name": "thread-id",
"desc": "(Optional) Thread ID number. Only valid for SPC3."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [] |
dlb | dlb {
assigned-flow;
per-packet;
flowlet inactivity-interval;
ether-type (Dynamic Load Balancing) (ipv4|ipv6|mpls);
} | [edit interfaces aex aggregated-ether-options] | Configure dynamic load balancing (DLB) on LAG with specific mode type—assigned flow, per-packet, or
flowlet) and ether type—ipv4, ipv6, or mpls.
NOTE: Since ether-type is a global configuration and applicable to all LAGs in the system
with DLB enabled, the CLI for specifying ether-type for LAG is added in the global
f... | [
{
"name": "assigned-flow",
"desc": "Fixed link assignment."
},
{
"name": "per-packet",
"desc": "Per-packet link assignment."
},
{
"name": "flowlet inactivity-interval",
"desc": "Minimum inactivity interval for link re-assignment. Range: 16 through 65535 (in micro seconds)."
},
{... | interface - To view this statement in the configuration.
interface-control - To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Dynamic Load Balancing (DLB)"
] |
dlci | dlci dlci-identifier; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For Frame Relay and Multilink Frame Relay user-to-network interface (UNI) network-to-network
interface (NNI) encapsulation only, and for link services and point-to-point interfaces only, configure the
data-link connection identifier (DLCI) for a permanent virtual circuit (PVC) or a switched virtual circuit
(SVC).
To co... | [
{
"name": "dlci-identifier",
"desc": "Data-link connection identifier."
}
] | 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 DLCIs on Link Services Logical Interfaces",
"Junos OS Network Interfaces Library for Routing Devices",
"Data-Link Connection Identifiers on Channelized Interfaces",
"Configuring Frame Relay DLCIs",
"Junos OS Services Interfaces Library for Routing Devices",
"multicast-dlci",
"multipoint-des... |
dlv | dlv {
domain-name domain-name trusted-anchor trusted-anchor;
} | [edit system services dns dnssec] | Configure DNSSEC Lookaside Validation (DLV) (RFC 5074). | [
{
"name": "domain-name domain-name",
"desc": "Specify the secure domain server name."
},
{
"name": "trusted-anchor trusted-anchor",
"desc": "Specify the trusted DLV anchor."
}
] | 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. | [] |
dne-origin (Diameter Network Element) | dne-origin realm realm-name <host hostname>; | [edit diameter network-element element-name] | Specify values of Origin-Realm-AVP and Origin-Host-AVP used in messages sent for the specified
network element by the Diameter instance.
NOTE: Only the realm is mandatory for the DNE origin. | [
{
"name": "host hostname",
"desc": "(Optional) Name of the message origin host that is supplied as the value of the Origin-Host AVP for Diameter messages associated with the network element."
},
{
"name": "realm realm-name",
"desc": "Name of the message origin realm, that is supplied as the valu... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring Diameter Network Elements",
"Configuring Diameter"
] |
dns (System Services) | dns {
dns-proxy {
cache hostname inet ip-address;
default-domain domain-name {
forwarders ip-address;
}
interface interface-name;
propogate-setting (enable | disable);
view view-name {
domain domain-name {
... | [edit system services] | 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... | [] | 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. | [
"DNS Overview"
] |
dns | dns {
disable;
doctoring (none | sanity-check);
maximum-message-length bytes;
oversize-message-drop;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the DNS ALG. By default, the DNS ALG is enabled. You can enable or disable the"
},
{
"name": "doctoring",
"desc": "Configure DNS ALG doctoring."
},
{
"name": "none",
"desc": "Disable all DNS ALG doctoring."
},
{
"name": "sanity-check",
... | 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.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"DNS Overview"
] |
dns-alg-pool | dns-alg-pool dns-alg-pool; | [edit services nat rule rule-name term term-name then translated] | Specify the Network Address Translation (NAT) pool for destination translation. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Network Address Translation Rules Overview"
] |
dns-alg-prefix | dns-alg-prefix dns-alg-prefix; | [edit services nat rule rule-name term term-name then translated] | Set the Domain Name System (DNS) application-level gateway (ALG) 96-bit prefix for mapping IPv4
addresses to IPv6 addresses. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Network Address Translation Rules Overview"
] |
dns-cache | dns-cache {
error-response-delete-ip {
retry-interval seconds;
}
} | [edit logical-systems logical-system-name security policies],
[edit logical-systems logical-system-name tenants tenant-system-name security policies],
[edit security policies],
[edit tenants tenant-system-name security policies] | Define security policy DNS cache behaviors.
When you don’t configure this statement [edit security policies dns-cache]:
•
If all DNS servers time out, the system removes the IP address from the cache.
•
If none of the DNS servers return a valid IP and the last one times out, the IP address is removed
from the cache.
Wh... | [
{
"name": "error-response-delete-ip",
"desc": "Clear DNS cache entry IP on error DNS response Values:"
},
{
"name": "retry-interval",
"desc": "Interval between deleting IP and resending DNS requests Range: 5 through 86400 seconds. Default: 300 seconds."
}
] | security | Statement introduced in Junos OS Release 20.1R1. | [
"show security dns-cache",
"clear security dns-cache"
] |
dns-filter | dns-filter {
database-file filename;
dns-resp-ttl seconds;
dns-server [ ip-address ];
hash-key key-string;
hash-method hash-method-name;
statistics-log-timer minutes;
wildcarding-level level;
} | [edit services web-filter profile profile-name],
[edit services web-filter profile profile-name dns-filter-template template-name] | Configure the settings for filtering DNS requests for disallowed website domains. Filtering can result in
either:
•
Blocking access to the site by sending the client a DNS response that includes an IP address or
domain name of a sinkhole server instead of the disallowed domain.
•
Logging the DNS request and allowing ac... | [
{
"name": "database-file",
"desc": ""
},
{
"name": "filename",
"desc": "Name of the domain filter database file to use when filtering DNS requests."
},
{
"name": "dns-resp-ttl",
"desc": ""
},
{
"name": "seconds",
"desc": "Number of seconds to live while sending the DNS re... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1 on MX Series.
Support added for Next Gen Services on MX Series routers MX240, MX480 and MX960 with MX-SPC3
services cards in Junos OS Release 19.3R2. | [
"DNS Request Filtering for Disallowed Website Domains"
] |
dns-filter-template | dns-filter-template template-name {
client-interfaces [ client-interface-name ];
client-routing-instance client-routing-instance-name;
dns-filter {
database-file filename;
dns-resp-ttl seconds;
dns-server [ ip-address ];
hash-key key-string;
hash-method hash-method-na... | [edit services web-filter profile profile-name] | Configure filtering of DNS requests for disallowed website domains for requests on specific uplink and
downlink logical interfaces or routing instances, or for requests from specific source IP address prefixes.
The DNS filter template overrides the corresponding settings at the DNS profile level. You can configure
up t... | [
{
"name": "accept",
"desc": "Accept DNS requests for DNS filtering."
},
{
"name": "client-interfaces",
"desc": ""
},
{
"name": "[ client-interface-name ]",
"desc": "(Optional) Client-facing (uplink) logical interfaces on which the DNS filter template settings are applied."
},
{
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1 on MX Series.
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. | [
"DNS Request Filtering for Disallowed Website Domains"
] |
dns-filtering | dns-filtering {
sinkhole {
dns-resp-ttl seconds;
fqdn domain-name;
ipv4-address ipv4-address;
ipv6-address ipv4-address;
srv-resp-err-code (Noerror | Refused);
txt-resp-err-code (Noerror | Refused);
wildcarding-level value;
}
traceoptions {
fil... | [edit services] | 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": "dns-resp-ttl",
"desc": "Configure the time-to-live (TTL) value in seconds to send_IN_the DNS response after taking the DNS sinkhole action. The maximum value for DNS response TTL is 86400 (24 hour). Default value is 1800 (30 min)."
},
{
"name": "fqdn",
"desc": "Configure the fully qua... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Command introduced in Junos OS Release 20.4R1. | [] |
dns-name | dns-name domain-name {
ipv4-only;
ipv6-only;
dns-query-interval;
min-ttl-override;
} | [[edit security address-book name address name],
[edit security address-book global address name],
[edit security zones security-zone name address-book address name]] | DNS address name. You can define DNS name in an address book and then use it when configuring
different features, such as security policies and NAT. | [
{
"name": "domain-name",
"desc": "Fully qualified hostname."
},
{
"name": "ipv4 only",
"desc": "IPv4 address of the DNS name server."
},
{
"name": "ipv6 only",
"desc": "IPv6 address of the DNS name server."
},
{
"name": "dns-query-interval",
"desc": "Configure the interva... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Support for min-ttl-override is added in Junos OS Release 25.2R1 | [] |
dns-proxy | dns-proxy {
cache hostname inet ip-address;
default-domain domain-name {
forwarders ip-address;
}
interface interface-name;
propogate-setting (enable | disable);
view view-name {
domain domain-name {
forward-only;
forwarders ip-address;
}
... | [edit system services dns dns-proxy] | Configure the device as a DNS proxy server by enabling DNS proxy on a logical interface. This option is
supported on SRX300, SRX320, SRX340, SRX345, SRX380, and SRX550M devices. | [] | 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-D10. | [
"DNS Proxy Overview",
"Configuring the Device as a DNS Proxy"
] |
dns-server-address (Dynamic Profiles) | dns-server-address [dns-server-address | $junos-ipv6-dns-server-address] {
lifetime seconds;
} | [edit dynamic-profiles dynamic-profile-name protocols router-advertisement interface interface-
name] | Specify the address of the DNS server that is used to resolve IPv6 DNS names. You can use RADIUS to
provide the address dynamically in the $junos-ipv6-dns-server variable within Access-Accept messages,
or you can statically configure up to three IPv6 addresses.
You can also specify the maximum time in seconds for which... | [
{
"name": "$junos-ipv6-dns-server-",
"desc": ""
},
{
"name": "address",
"desc": "Dynamically receive the address of the DNS server from RADIUS in Access-Accept messages."
},
{
"name": "dns-server-address",
"desc": "IPv6 address of the DNS server. You can configure up to three DNS ser... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"DNS Resolver for IPv6 DNS Overview",
"Configuring a DNS Server Address for IPv6 Hosts"
] |
dns-server-address | dns-server-address address {
lifetime seconds;
} | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Specify the recursive DNS server address that the device must use to resolve DNS names. The recursive
DNS server address is the 128-bit IPv6 address of the recursive DNS server. You can configure a
maximum of three recursive DNS server addresses at the interface level.
The remaining statement is explained separately. S... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Example: Configuring Recursive DNS Server Addresses for IPv6 Hosts",
"Understanding Recursive DNS Servers for IPv6"
] |
dns-snooping (Application Servies) | dns-snooping; | [edit security policies from-zone name to-zone name application-services] | Enable DNS snooping for the current policy context. When you enable DNS snooping, the system
captures DNS response packets as they traverse the network, extracting the relevant DNS records and
build mapping of FQDN and IP address in a local cache.
This configuration restricts snooping for the traffic passing through ce... | [] | [none specified] | Statement introduced in Junos OS Release 25.2R1. | [] |
dns-snooping | dns-snooping {
global-enable;
report-interval seconds;
trusted-dns-server [ trusted-dns-server ... ];
} | [edit services] | Enable DNS-snooping on your firewall. The DNS snooping feature offers a mechanism for dynamically
inspecting and caching DNS responses in real time. | [
{
"name": "global-enable",
"desc": "Enable DNS snooping globally. When you enable globally,you don't have to configure this functionality as security policy level."
},
{
"name": "report-interval",
"desc": ""
},
{
"name": "seconds",
"desc": "Frequency of sending DNS-snooping data from... | [none specified] | Statement introduced in Junos OS Release 25.2R1. | [] |
dnssec | dnssec {
disable;
dlv {
domain-name domain-name trusted-anchor trusted-anchor;
}
secure-domains domain-name;
trusted-keys {
(key dns-key | load-key-file url);
} | [edit system services dns] | Configure domain name service security extensions (DNSSEC) in the DNS server. DNSSEC is an
extension of DNS that provides authentication and integrity verification of data by using public-key-
based signatures. | [
{
"name": "disable",
"desc": "Disable DNSSEC. Default: DNSSEC is enabled."
},
{
"name": "secure-domains",
"desc": ""
},
{
"name": "[domain-name]",
"desc": "Configure one or more secure domains in the DNS server. The server accepts only signed responses for this domain. For unsigned ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Release 10.2 of Junos OS. | [
"DNSSEC Overview",
"Example: Configuring Secure Domains and Trusted Keys for DNSSEC"
] |
do-not-fragment | do-not-fragment; | [edit interfaces gr-fpc/pic/port unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number
tunnel] | For a generic routing encapsulation (GRE) tunnel, disable fragmentation of GRE-encapsulated packets.
This sets the do-not-fragment (DF) bit in the outer IP header of the GRE-encapsulated packets so that
they do not get fragmented anywhere in the path. When the size of a GRE-encapsulated packet is
greater than the MTU o... | [] | 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.
Statement introduced in Junos OS Release 19.3 for MPC10E line card. | [
"Enabling Fragmentation and Reassembly on Packets After GRE-Encapsulation",
"Junos OS Services Interfaces Library for Routing Devices"
] |
dod-request-policy | dod-request-policy dod-request-policy-name; | [edit logical-systems logical-system-name protocols ldp],
[edit protocols ldp] | Specify the name of the LDP downstream on demand request policy. The dod-request-policy statement
performs exact match, as a result, LDP sends label request messages only for those FECs matching in
the downstream on demand request policy. | [
{
"name": "dod-request-polcy-name",
"desc": "Specify the name of the downstream on demand request policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring LDP Downstream on Demand"
] |
domain (DNS Forwarding Options) | domain {
description text-description;
interface interface-name {
broadcast;
description text-description;
no-listen;
server address <logical-system logical-system-name> <routing-instance routing-instance-
name>;
}
server address <logical-system logical-system-name> <rou... | [edit forwarding-options helpers] | Enable DNS request packet forwarding.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring DNS and TFTP Packet Forwarding"
] |
domain (Domain Map) | domain {
delimiter [delimiter-character];
map domain-map-name {
aaa-logical-system logical-system-name {
aaa-routing-instance routing-instance-name;
}
aaa-routing-instance routing-instance-name;
access-profile profile-name;
address-pool pool-name;
dyna... | [edit access] | Configure a domain map, which is used to map access options and session parameters for subscriber
sessions.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | 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. | [
"Configuring a Domain Map"
] |
domain (Precision Time Protocol) | domain domain-value; | [edit protocols ptp] | Configure multiple independent Precision Time Protocol (PTP) domains.
NOTE: Only one PTP domain is supported at any given point in time. | [
{
"name": "domain-value",
"desc": "The PTP domain value. The range depends on the selected profile type."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview"
] |
domain (TDF Domain Selection) | domain tdf-domain-name; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name then] | Specify the TDF domain to be selected when the criteria specified in the domain selection statement are
matched.
NOTE: This statement is required even if you have not specified any match criteria. | [
{
"name": "tdf-domain-name",
"desc": "Name of the TDF domain to use. NOTE: The TDF domain must have been previously configured at the [edit unified-edge gateways tdf gateway-name domains] hierarchy level."
}
] | 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"
... |
domain-name (Access Profile) | domain-name domain-name; | [edit access profile profile-name client-name-filter client-name] | Specify a domain name that must be in a client's name during the authentication process. | [
{
"name": "domain-name",
"desc": "Domain name that must be in a client name. The name must not exceed 128 characters."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Obtaining Username and Role Information Through Firewall Authentication"
] |
domain-name (DHCP Local Server) | domain-name domain-name-string; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication username-include],
[edit logic... | Specify the domain name that is concatenated with the username during the subscriber authentication
or DHCP client authentication process. | [
{
"name": "domain-name-string",
"desc": "Domain name formatted string."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
domain-name (DHCP Relay Agent) | domain-name domain-name-string; | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name auth... | Specify the domain name that is concatenated with the username during the subscriber authentication
or client authentication process. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure
DHCPv6 support. | [
{
"name": "domain-name-string",
"desc": "Domain name formatted string."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Specifying Authentication Support",
"Creating Unique Usernames for DHCP Clients"
] |
domain-name (DHCP) | domain-name domain-name; | [edit system services dhcp],
[edit system services dhcp pool],
[edit system services dhcp static-binding] | Configure the name of the domain in which clients search for a DHCP server host. This is the default
domain name that is appended to hostnames that are not fully qualified. | [
{
"name": "domain-name",
"desc": "Name of the domain."
}
] | 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 a DHCP Server on Switches"
] |
domain-name (Static Subscribers) | domain-name domain-name; | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name authentication username-inclu... | Specify the domain name that is included at the end of the username created for all static subscribers or
for the static subscribers in a specified group. The group version of the statement takes precedence over
the global version. | [
{
"name": "domain-name",
"desc": "Domain name that ends the username created for all static subscribers. The username is also"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Configuring the Static Subscriber Global Username",
"Configuring the Static Subscriber Group Username"
] |
domain-name (System) | domain-name domain-name; | [edit system] | Configure the name of the domain in which the router or switch is located. This is the default domain
name that is appended to hostnames that are not fully qualified. | [
{
"name": "domain-name",
"desc": "Name of the domain. NOTE: The length of the domain name cannot exceed 255 characters."
}
] | 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. | [] |
domain-name | domain-name domain-name-string; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication username-include] | Specify the domain name that is concatenated with the username during the subscriber authentication
process. | [
{
"name": "domain-name-string",
"desc": "The domain name formatted string."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring VLAN Interface Username Information for AAA Authentication"
] |
domain-name-server (Routing Instances and Access Profiles) | domain-name-server dns-address; | [edit access],
[edit access profile] | Configure an IPv4 address for a DNS name server. You can configure an address globally for a routing
instance at the [edit access] hierarchy level or for an access profile at the [edit access profile profile-name]
hierarchy level. You can configure more than one address by including the statement multiple times.
NOTE: ... | [
{
"name": "dns-address",
"desc": "IPv4 address of the DNS name server."
}
] | admin—To view this statement in the configuration
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring DNS Name Server Addresses for Subscriber Management",
"DNS Name Server Address Overview"
] |
domain-name-server-inet (Routing Instances and Access Profiles) | domain-name-server-inet dns-address; | [edit access],
[edit access profile] | Configure an IPv4 address for a DNS name server. You can configure an address globally for a routing
instance at the [edit access] hierarchy level or for an access profile at the [edit access profile profile-name]
hierarchy level. You can configure more than one address by including the statement multiple times.
NOTE: ... | [
{
"name": "dns-address",
"desc": "IPv4 address of the DNS name server."
}
] | admin—To view this statement in the configuration
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring DNS Name Server Addresses for Subscriber Management",
"DNS Name Server Address Overview"
] |
domain-name-server-inet6 (Routing Instances and Access Profiles) | domain-name-server-inet6 dns-address; | [edit access],
[edit access profile] | Configure an IPv6 address for a DNS name server. You can configure an address globally for a routing
instance at the [edit access] hierarchy level or for an access profile at the [edit access profile profile-name]
hierarchy level. You can configure more than one address by including the statement multiple times. | [
{
"name": "dns-address",
"desc": "IPv6 address of the DNS name server."
}
] | admin—To view this statement in the configuration
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring DNS Name Server Addresses for Subscriber Management",
"DNS Name Server Address Overview"
] |
domain-path-id (Protocols BGP) | domain-path-id {
receive;
send;
} | [edit protocols bgp],
[edit protocols bgp group group-name],
[edit protocols bgp group group-name neighbor neighbor-address],
[edit routing-instances instance-name protocols bgp],
[edit routing-instances instance-name protocols bgp group group-name],
[edit routing-instances instance-name protocols bgp group group-name ... | Use the domain-path-id statement to control whether the BGP Domain Path (D-PATH) attribute is sent
to or received from BGP peers. The D-PATH attribute identifies the sequence of administrative domains
that a route traverses. This helps prevent routing loops in EVPN and IPVPN deployments, and across
data centers for EVP... | [
{
"name": "receive",
"desc": "Allow receiving BGP domain path attribute"
},
{
"name": "send",
"desc": "Allow sending BGP domain path attribute"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | receive statement introduced in Junos OS and Junos OS Evolved Release 23.2R1.
send statement introduced in Junos OS and Junos OS Evolved Release 23.2R1. | [] |
domain-path-id (Protocols EVPN) | [edit routing-instances name protocols evpn interconnect] | Configure this statement in an EVPN data center interconnect (DCI) to prevent EVPN Type 5 routing
loops.
This statement is intended only for Type 5 routes in a DCI environment. Refer to the Related
Documentation section for other hierarchies where domain-path-id is available.
NOTE: To prevent looping, you must import a... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.2R1 | [
"Understanding EVPN Pure Type 5 Routes"
] | |
domain-path-id | [edit routing-options]
domain-path-id {
<domain-id-string>;
} | [edit routing-options] | NOTE: In Junos OS Release 22.2R1 and 22.3R1, and Junos OS Evolved Releases and
22.2R1 and 22.3R1, the dpath-domain-id statement was called uniform-propagation-mode with
a domain-id option. The uniform-propagation-mode statement with the domain-id option has the
same functionality as the dpath-domain-id statement.
Start... | [
{
"name": "domain-id-string",
"desc": "(Required) Specify the domain ID type and value."
},
{
"name": "domain-path-id {",
"desc": ""
},
{
"name": "6500:1:evpn;",
"desc": ""
},
{
"name": "6500:2:ipvpn;",
"desc": ""
},
{
"name": "}",
"desc": ""
}
] | 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. | [] |
domain-search | domain-search [domain-list ]; | [edit system],
[edit system services dhcp],
[edit system services dhcp pool],
[edit system services dhcp static-binding] | Configure a list of domains to search (in the case where you want to configure access to multiple DNS
servers for redundancy, and/or to resolve hosts that the previous server could not). | [
{
"name": "domain-list",
"desc": "List of domain servers to search. The list can contain up to six domain names, separated by a space, with a total of up to 256 characters. For example to search domain1.net, and if it fails to resolve the host, domain2.net, and if fails to resolve the host, domain3.net, you... | 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. | [] |
domain-selection | domain-selection {
term term-name {
from {
3gpp-imsi {
equals value;
has-prefix value;
has-suffix value;
matches value;
}
attribute name {
code numeric-code;
vendor-id vendor-... | [edit unified-edge gateways tdf gateway-name] | Specify the TDF domain to be used for an IP-based subscriber. You can configure multiple terms under
domain-selection, and each term is applied in the order in which it is configured. You can specify multiple
match conditions within a term and all of the conditions have to match. If the incoming RADIUS request
from the... | [] | 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"
] |
domain-type (Bridge Domains) | domain-type bridge; | [edit bridge-domains bridge-domain-name] | Define the domain type bridge for a Layer 2 bridge domain.
NOTE: There is only one domain type bridge, that can be configured on SRX Series
Firewalls. Domain type bridge is not enabled by default. An SRX Series Firewall operates
in the Layer 2 transparent mode when all physical bridge domains on the device are
partitio... | [] | 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 modified in Junos OS Release 9.5.
Support for logical systems added in Junos OS Release 9.6. | [
"Ethernet Switching and Layer 2 Transparent Mode Overview",
"Configuring a Bridge Domain",
"Configuring a Layer 2 Virtual Switch"
] |
domains | domains domain-name {
apply-groups [group-names];
apply-groups-except [group-names];
burst-size {
apply-groups [group-names];
apply-groups-except [group-names];
downlink downlink-burst-size;
uplink uplink-burst-size ;
}
ifl-subscriber [subscriber-name] {
acce... | [edit unified-edge gateways tdf gateway-name] | Configure a TDF domain, which specifies a set of properties for creating TDF subscriber sessions and for
handling subscriber traffic. | [
{
"name": "domain-name",
"desc": "Name of the TDF domain. Range: 1 through 50 alphanumeric characters."
}
] | 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",
"Understanding the Definition of a Set of IFL-Based Subscriber Pro... |
dont-help-shared-fate-bfd-down | dont-help-shared-fate-bfd-down | [edit protocols bgp graceful-restart] | When BFD is control plane dependent and the device detects a BFD down event and is not already
entering the graceful restart helper mode, this is treated as a regular BFD down event and the device
enters the graceful restart helper mode. This behavior makes the control plane dependent BFD unusable
in conjunction with g... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring Routing Protocols Graceful Restart",
"Understanding External BGP Peering Sessions"
] |
dot1p-priority | dot1p-priority number; | [edit protocols protection-group ethernet-ring ring-name] | Specify the IEEE 802.1p priority to be used in the transmitted RAPS protocol data units. | [
{
"name": "number",
"desc": "802.1p priority number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Ethernet Ring Protection Switching Overview",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)"
] |
dot1q-tunneling | dot1q-tunneling {
customer-vlans (id | native | range);
layer2-protocol-tunneling all | protocol-name {
drop-threshold number;
shutdown-threshold number;
}
} | [edit vlans vlan-name] | For Ethernet switching, sets a global value for the EtherType for Q-in-Q tunneling.
For VLANs, enables Q-in-Q tunneling on the specified VLAN.
NOTE:
•
The VLAN on which you enable Q-in-Q tunneling must be a tagged VLAN.
•
You cannot configure 802.1X user authentication on interfaces that have been
enabled for Q-in-Q t... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
Option native introduced in Junos OS Release 9.6 for EX Series switches.
Options layer2-protocol-tunneling, drop-threshold, and shutdown-threshold introduced in Junos OS
Release 10.0 for EX Series switches. | [
"Example: Setting Up Q-in-Q Tunneling on EX Series Switches",
"Configuring Q-in-Q Tunneling on EX Series Switches",
"Configuring Q-in-Q Tunneling on QFX Series Switches",
"Example: Setting Up Q-in-Q Tunneling on QFX Series Switches"
] |
dot1x (MX Series in Enhanced LAN Mode) | dot1x {
disable;
guest-vlan (vlan-id | vlan-name);
mac-radius {
flap-on-disconnect;
restrict;
}
maximum-requests number;
no-reauthentication;
server-fail (deny | permit | use-cache | vlan-id | vlan-name);
server-reject-vlan (vlan-id | vlan-name) {
eapol-block;
... | [edit protocols authentication-access-control interface (all | interface-names)] | Configure 802.1X authentication for Port-Based Network Access Control. 802.1X authentication is
supported on interfaces that are members of private VLANs (PVLANs).
The remaining statements are explained separately. See CLI Explorer.
Default
802.1X is disabled. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
dot1x | dot1x {
authenticator {
authentication-profile-name access-profile-name;
interface (all | [ interface-names ]) {
authentication-order (captive-portal | dot1x | mac-radius);
disable;
guest-bridge-domain guest-bridge-domain;
guest-vlan guest-vlan;
... | [edit logical-systems name protocols],
[edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "ssl-certificate-path",
"desc": ""
},
{
"name": "path-name",
"desc": "Specify the file path for SSL certificates if you are not using the default path. The default path for SSL certificates is /var/tmp. The remaining statements are explained separately. Search for a statement in CLI Ex... | 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.
ssl-certificate-path introduced in Junos OS Release 19.4.
ip-mac-session-binding introduced in Junos OS Release 20.2 | [
"Example: Setting Up 802.1X for Single-Supplicant or Multiple-Supplicant Configurations on an EX",
"Series Switch",
"Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors",
"on an EX Series Switch",
"Example: Setting Up VoIP with 802.1X and LLDP-MED on an EX Series ... |
downlink-dscp-to-egress-forwarding-class | downlink-dscp-to-egress-forwarding-class {
classifier classifier-name;
classifier classifier-name; {
routing-instance instance-name;
}
} | [edit services mobile-edge gateways saegw system class-of-service] | You will use these classifiers to map DiffServ code point (DSCP) values provided in Transport Level
Marking (TLM) to specific forwarding/egress classes on the WAN interface.
The Egress Forwarding Class will be assigned to the Service Data Flow (SDF). All packets matching that
SDF inherit the forwarding class. If the Eg... | [] | system | This statement was introduced in Junos OS Release 23.1R1. | [] |
downlink-dscp-to-forwarding-class | downlink-dscp-to-forwarding-class {
classifier classifier-name;
classifier classifier-name {
routing-instance instance-name;
}
} | [edit services mobile-edge gateways saegw system class-of-service] | Assign the classifiers to use for mapping the DiffServ code point (DSCP) value provided in the Transport
Level Marking to the forwarding queues.
The DSCP value is relevant in the context of the routing instance associated with the outgoing interface.
Therefore, you need to assign classifiers to peer routing instances. ... | [] | system | Juniper Networks introduced this statement in Junos OS Release 22.2R1. | [] |
download (Services) | download {
automatic {
interval hours;
minor-only;
start-time start-time;
}
ignore-server-validation;
proxy-profile proxy-profile;
routing-instance routing-instance-name;
source-address souce-ip-address; url url;
} | [edit services application-identification] | Configure automatic download for the application identification services application package.
The application package contains definitions for known applications, such as: DNS, Facebook, FTP,
Skype, and SNMP. The application package is located at https://signatures.juniper.net. If you do not
have access to the default... | [
{
"name": "automatic",
"desc": "Download the application package automatically at a certain time of day or at intervals."
},
{
"name": "interval",
"desc": "Download the application package at intervals."
},
{
"name": "minor-only",
"desc": "Specify signature package version type as mi... | For Routing Devices
•
interface—To view this statement in the configuration.
•
interface-control—To add this statement to the configuration.
For Security Devices
•
security—To view this statement in the configuration.
•
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5 for Routing Devices and Junos OS Release 10.2 for
Security Devices | [
"Example: Scheduling the Application Signature Package Updates"
] |
download-profile (Security Antivirus FTP) | download-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name anti-virus ftp] | Configure a Content Security policy for the antivirus FTP (download) protocol and attach this policy to a
security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
download-profile (Security Content Filtering FTP) | download-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name content-filtering ftp] | Configure a Content Security policy for the content-filtering FTP (download) protocol and attach this
policy to a security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Content Filtering Overview"
] |
downstream | downstream name; | [edit logical-systems name protocols router-advertisement interface],
[edit protocols router-advertisement interface] | Configure the list of downstream interfaces for RA proxy | [
{
"name": "name",
"desc": "Configure the downstream interface for RA proxy"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1 | [] |
downstream-mode | downstream-mode; | [edit logical-systems name protocols router-advertisement interface],
[edit protocols router-advertisement interface] | Configure the interface as downstream interface for RA proxy | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1 | [] |
downstream-on-demand | downstream-on-demand; | [edit logical-systems logical-system-name protocols ldp session session-address],
[edit protocols ldp session session-address] | Enable LDP downstream on demand on the LDP session. LDP is widely deployed in downstream
unsolicited advertisement mode. As service providers integrate the access and aggregation networks
into a single MPLS domain, LDP downstream on demand is needed to distribute the bindings between
access and aggregation networks to ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring LDP Downstream on Demand"
] |
downstream-rate (Traffic Shaping) | downstream-rate rate; | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit advisory-options],
[edit dynamic-profiles profile-name interfaces interface-set $junos-interface-set-name interface
$junos-interface-ifd-name advisory-options],
[edit interfaces demux0 unit logical-unit-number advisory... | Specify a recommended shaping rate to be applied to downstream traffic on an interface.
For ANCP interfaces, this configured rate is used as the default value for the Juniper VSA Downstream-
Calculated-Qos-Rate (26–141) when the router has not received and processed the attributes from the
access node.
For L2TP, the ra... | [
{
"name": "rate",
"desc": "Traffic rate in bits per second."
}
] | 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 at the [edit interfaces demux0 ...] hierarchy level introduced in Junos OS Release 12.2.
Support at the [edit dynamic-profiles ...] hierarchy level introduced in Junos OS Release 13.1. | [
"Setting a Recommended Shaping Rate for Traffic on ANCP Interfaces",
"Configuring the ANCP Agent",
"Configuring the Method to Derive the LAC Connection Speeds Sent to the LNS"
] |
dr-election-on-p2p | dr-election-on-p2p; | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Enable PIM designated router (DR) election on point-to-point (P2P) links.
Default
No PIM DR election is performed on point-to-point links. | [] | 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 PIM Designated Router Election on Point-to-Point Links"
] |
dr-register-policy | dr-register-policy [ policy-names ]; | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Apply one or more policies to control outgoing PIM register messages. | [
{
"name": "policy-names",
"desc": "Name of one or more import policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Register Message Filters on a PIM RP and DR"
] |
drain | drain; | [edit services l2tp],
[edit services l2tp destination address ip-address],
[edit services l2tp destination address ip-address routing-instance routing-instance-name],
[edit services l2tp destination name destination-name],
[edit services l2tp tunnel name name],
[edit services l2tp tunnel name name address ip-address],
... | Prevent the creation of new sessions, destinations, and tunnels globally at an L2TP access concentrator
(LAC) or an L2TP network server (LNS). Prevent the creation of new tunnels and sessions for a specific
destination. Prevent the creation of new sessions for a specific tunnel. | [] | 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. | [
"L2TP Tunnel Switching For Multiple-Domain Networks",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces"
] |
draining (Diameter Applications) | draining; | [edit access pcrf partition partition-name],
[edit access ocs partition partition-name] | Configure the Policy and Charging Rule Function (PCRF) or Online Charging System (OCS) partition to
the draining state to make substantial configuration changes quickly. To log out all subscribers quickly
and immediately, issue the clear network-access pcrf subscribers command.
After you set draining for either of the ... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interac... |
draining-response-timeout (Diameter Applications) | draining-response-timeout seconds; | [edit access pcrf partition partition-name],
[edit access ocs partition partition-name] | Configure the amount of time in seconds before a PCRF or an Online Charging System OCS partition
responds and begins to drain. Configuring this statement is optional if you set draining statement for
either of the Policy and Charging Rule Function (PCRF) or Online Charging System (OCS) partitions.
After you set drainin... | [
{
"name": "seconds",
"desc": "Number of seconds to wait before the partition begins to drain. Default: 400 Range: 0 through 86,400 seconds (24 hours)"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interac... |
drop (BPDU Block) | drop; | [edit ethernet-switching-options bpdu-block bpdu-block (all | [interface-name])] | Drop bridge protocol data units (BPDUs ) that enter any interface or a specified interface, but do not
disable the interface. Configure the drop statement only on interfaces on which no spanning-tree
protocol (STP, MSTP, or RSTP) is configured.
NOTE: Do not configure drop on any interface on which a spanning-tree proto... | [] | 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. | [
"Understanding BPDU Protection for STP, RSTP, and MSTP",
"Example: Configuring BPDU Protection on Edge Interfaces to Prevent STP Miscalculations on non-",
"ELS EX Series Switches",
"Example: Configuring BPDU Protection on Interfaces to Prevent STP Miscalculations on EX Series",
"Switches"
] |
drop (DHCP Relay Agent Option) | drop; | [edit forwarding-options dhcp-relay relay-option (default-action | equals | starts-with)],
[edit forwarding-options dhcp-relay dhcpv6 relay-option (default-action | equals | starts-with)],
[edit forwarding-options dhcp-relay group group-name relay-option (default-action | equals | starts-
with)],
[edit forwarding-optio... | Drop (discard) specified DHCP client packets when you use DHCP relay agent selective processing. You
can configure the drop operation globally or for a group of interfaces, and for either DHCP or DHCPv6
relay agent. | [] | 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. | [
"Using DHCP Option Information to Selectively Process DHCP Client Traffic"
] |
drop (PPPoE Service Name Tables) | drop; | [edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier aci
circuit-id-string ari remote-id-string] | Direct the router to drop (ignore) a PPPoE Active Discovery Initiation (PADI) control packet received
from a PPPoE client that contains the specified service name tag or agent circuit identifier/agent remote
identifier (ACI/ARI) information. This action effectively denies the client’s request to provide the
specified s... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Support at [edit protocols pppoe service-name-tables table-name service service-name agent-specifier aci
circuit-id-string ari remote-id-string] hierarchy level introduced in Junos OS Release 10.2. | [
"Configuring PPPoE Service Name Tables"
] |
drop (Security GTP) | drop {
aa-create-pdp 0;
aa-delete-pdp 0;
bearer-resource 2;
change-notification 2;
config-transfer 2;
context 2;
create-bearer 2;
create-data-forwarding 2;
create-pdp (0 | 1 | all);
create-session 2;
create-tnl-forwarding 2;
cs-paging 2;
data-record (0 | 1 | all);
... | [edit security gtp profile profile-name] | Use the parameters (0 | 1 | 2 | all) for the GTP release version number for a specific message type. The
possible versions are 0, 1, 2, or all. You can configure the device to drop packets that do not meet your
specified minimum or maximum message lengths. A GTP message type includes one or many messages.
When you drop... | [
{
"name": "aa-create-pdp",
"desc": "Represents Create AA PDP Context Request and Create AA PDP Context Response"
},
{
"name": "aa-delete-pdp",
"desc": "Represents Delete AA PDP Context Request and Delete AA PDP Context Response"
},
{
"name": "bearer-resource",
"desc": "Represents Bea... | 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. New GTP message types added in Junos OS Release
11.4. Support . | [
"Understanding GTP Message Filtering",
"Example: Filtering GTP Message Types",
"Understanding GTP APN Filtering"
] |
drop (Security SCTP) | drop {
m3ua-service {
isup;
sccp;
tup;
}
payload-protocol {
id;
all;
asap;
bicc;
ddp-segment;
ddp-stream;
diameter-dtls;
diameter-sctp;
dua;
enrp;
h248;
... | [edit security sctp profile profile-name] | Configure the drop SCTP message types to display information about the configuration of the current
Stream Control Transmission Protocol (SCTP) inspection.
From Junos OS Release 20.4R1 onwards, the [edit security gprs sctp profile profile-name] hierarchy level
is replaced by [edit security sctp profile profile-name]. | [
{
"name": "m3ua-services",
"desc": "M3UA data service indicator. The following values are supported:"
},
{
"name": "isup",
"desc": "ISDN Upper Part."
},
{
"name": "sccp",
"desc": "Signaling Connection Control Part."
},
{
"name": "tup",
"desc": "Telephone User Part."
},
... | 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. Support for the payload-protocol statement was modified
n Junos OS Release 12.1X46-D10. | [
"Understanding Stream Control Transmission Protocol",
"Understanding SCTP Multichunk Inspection"
] |
drop-congestion-notification | drop-congestion-notification {
forwarding-class forwarding-class;
udp-port udp-port;
} | [edit class-of-service] | Define Drop Congestion Notification (DCN) for all devices in the network using DCN. DCN is a
congestion management technique based on packet trimming. Rather than drop a packet when
congestion occurs, the device trims the packet’s payload, resulting in a smaller packet. The device then
transmits this smaller packet thr... | [
{
"name": "forwarding-class",
"desc": "Forwarding class for DCN-marked packets. This forwarding class should map to a strict-high priority queue, ideally used only for DCN-marked packet delivery. This better ensures delivery of DCN-marked packets to the receiver host."
},
{
"name": "udp-port",
"... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1. | [] |
drop-flow | drop-flow {
max-sessions percent;
timeout seconds;
} | [edit security flow] | To prevent the probable security attack, we introduce drop-flow configuration. Sessions in the drop-flow
is valid for 4 seconds by default. | [
{
"name": "max-sessions",
"desc": "Maximum Drop-flow Sessions (default 10%) (percent) Default: 10 Range: 0 through 30"
},
{
"name": "timeout",
"desc": "Timeout (default 4s) (seconds) Default: 4 Range: 2 through 300"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | This statement is introduced in Junos OS Release 23.3R1. | [] |
drop-member-traffic (Aggregated Multiservices) | drop-member-traffic {
rejoin-timeout rejoin-timeout;
} | [edit interfaces interface-name load-balancing-options member-failure-options] | Specify whether the broadband gateway should drop traffic to a services PIC when it fails.
For many-to-one (N:1) high availability (HA) for service applications like Network Address Translation
(NAT), this configuration is valid only when two or more services PICs have failed.
The remaining statement is explained separ... | [] | 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)"
] |
drop-policy (Subscriber Secure Policy) | drop-policy rule-name {
from {
apply-groups group-name;
apply-groups-except group-name;
destination-address address;
destination-port port-number;
dscp dscp-value;
protocol protocol;
source-address address;
source-port port-number;
}
} | [edit services radius-flow-tap policy policy-name inet| inet6] | Specify the drop-policy that is applied to mirrored packets sent to a mediation device. | [] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
drop-probability (Fill Level) | drop-probability percentage; | [edit class-of-service drop-profiles profile-name fill-level percentage] | Drop packets at the rate of the drop-probability value when the queue fills to the percentage configured
with the fill-level value. This way you can manage network congestion. | [
{
"name": "percentage",
"desc": "The probability (expressed in percentage) for a packet to be dropped from the queue."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS 11.4. | [
"Configuring CoS Tail Drop Profiles (CLI Procedure)",
"Understanding Junos OS CoS Components for EX Series Switches"
] |
drop-probability (Interpolated Value) | drop-probability [values]; | [edit class-of-service drop-profiles profile-name interpolate] | Define values for interpolated drop probabilities. The maximum number of drop probability values
supported per drop profile is based on the line card.
On EX Series switches, this statement is supported only on the EX9200 switch, EX8200 standalone
switches, and EX8200 Virtual Chassis. | [
{
"name": "percentage",
"desc": "The probability (expressed in percentage) for a packet to be dropped from the queue."
}
] | 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. | [
"Managing Congestion Using RED Drop Profiles and Packet Loss Priorities",
"Defining Packet Drop Behavior by Configuring RED Drop Profiles"
] |
drop-probability (Percentage) | drop-probability percentage; | [edit class-of-service drop-profiles profile-name] | Define drop probability percentages. The maximum number of drop probability values supported per
drop profile is based on the line card. | [
{
"name": "percentage",
"desc": "Probability that a packet is dropped, expressed as a percentage. A value of 0 means that a"
}
] | 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. | [
"Managing Congestion Using RED Drop Profiles and Packet Loss Priorities",
"Defining Packet Drop Behavior by Configuring RED Drop Profiles"
] |
drop-probability | [edit class-of-service drop-profiles profile-name interpolate] | When configuring WRED, map the packet drop-probability to the fullness of a queue ("fill-level" on page
7449). You configure the fill-level and drop-probability statements in related pairs. The pairs of fill level
and drop probability values set a probability of dropping packets at a specified queue fullness value.
On... | [
{
"name": "0 (switches that support only two fill level/drop probability pairs)",
"desc": "Probability that packets will drop at"
},
{
"name": "high-value (switches that support only two fill level/drop probability pairs)",
"desc": "The maximum probability"
},
{
"name": "percentage1 perc... | 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. | [] | |
drop-profile (Dynamic Schedulers) | drop-profile (profile-name | predefined-variable); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map loss-
priority (any | low | medium-low | medium-high | high) protocol (any | non-tcp | tcp)] | Within the drop-profile map, specify the name of the drop profile to use for random early detection
(RED) for a specific packet-loss priority (PLP) level and protocol type. A drop profile maps a fill level
(fullness of a queue) to a drop probability (probability that a packet will be dropped). When a packet
arrives, RE... | [
{
"name": "profile-name",
"desc": "Name of the drop profile."
},
{
"name": "predefined-variable",
"desc": "One of the following Junos predefined variable that is replaced with a value obtained"
},
{
"name": "profile is attached:",
"desc": ""
},
{
"name": "$junos-cos-scheduler... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
The $junos-cos-scheduler-dropfile-low, $junos-cos-scheduler-dropfile-medium-low, $junos-cos-scheduler-dropfile-
medium-high, $junos-cos-scheduler-dropfile-high, and $junos-cos-scheduler-dropfile-any predefined variable
introduced in Junos OS Release 9.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access",
"Determining Packet Drop Behavior by Configuring Drop Profile Maps for Schedulers"
] |
drop-profile (Schedulers) | drop-profile profile-name; | [edit class-of-service schedulers scheduler-name drop-profile-map loss-priority (any | low | medium-
low | medium-high | high) protocol (any | non-tcp | tcp)] | Define drop profiles for weighted random early detection (WRED). When a packet arrives, WRED
checks the queue fill level specified in the drop profile. If the fill level corresponds to a nonzero drop
probability, the WRED algorithm determines whether to drop the arriving packet. | [
{
"name": "profile-name",
"desc": "Name of the drop profile."
}
] | 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. | [
"Determining Packet Drop Behavior by Configuring Drop Profile Maps for Schedulers",
"Managing Congestion Using RED Drop Profiles and Packet Loss Priorities",
"Example: Configuring Drop Profile Maps"
] |
drop-profile-map (Dynamic Schedulers) | drop-profile-map loss-priority (any | low | medium-low | medium-high | high) protocol (any | non-
tcp | tcp) drop-profile (profile-name | predefined-variable); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] | Define loss priority value for drop profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
drop-profile-map (Schedulers) | drop-profile-map loss-priority (any | low | medium-low | medium-high | high) protocol (any | non-
tcp | tcp) drop-profile profile-name; | [edit class-of-service schedulers scheduler-name] | Map a drop profile to a loss priority and protocol for weighted random early detection (WRED). When a
packet arrives, WRED checks the queue fill level. If the fill level corresponds to a nonzero drop
probability, the WRED algorithm determines whether to drop the arriving packet.
The remaining statements are explained s... | [] | 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. | [
"Default Schedulers Overview",
"Determining Packet Drop Behavior by Configuring Drop Profile Maps for Schedulers",
"Example: Configuring Drop Profile Maps",
"Example: Configuring CoS on EX Series Switches",
"Defining CoS Schedulers and Scheduler Maps (CLI Procedure)",
"Defining CoS Schedulers (J-Web Proce... |
drop-profiles (Definition) | drop-profiles {
profile-name {
fill-level percentage drop-probability percentage;
interpolate {
drop-probability [values];
fill-level [values]
}
}
} | [edit class-of-service] | Define drop profiles for random early detection (RED).
For a packet to be dropped, it must match the drop profile. When a packet arrives, RED checks the
queue fill level. If the fill level corresponds to a nonzero drop probability, the RED algorithm determines
whether to drop the packet. | [
{
"name": "profile-name",
"desc": "Name of the drop profile."
}
] | 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. | [
"Defining Packet Drop Behavior by Configuring RED Drop Profiles"
] |
drop-threshold (Security GPRS) | drop-threshold {
forward number;
reverse number;
} | [edit security gtp profile profile-name path-rate-limit message-type (create-req | delete-req |
echo-req | other)] | Configure the drop-threshold parameter to drop traffic when the number of packets per second or per
minute exceeds the configured limit.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name path-rate-limit
message-type (create-req | delete-req | echo-req | other)] hierarchy-level is re... | [
{
"name": "number",
"desc": "Limit messages in forward or reverse direction."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [
"Example: Limiting the Message Rate and Path Rate for GTP Control Messages"
] |
drop-threshold | drop-threshold number; | [edit vlans vlan-name dot1q-tunneling layer2-protocol-tunneling (all | protocol-name vlan-name)],
[edit protocols layer2-control bpdu-block interface interface-name] | Specify the maximum number of Layer 2 PDUs of the specified protocol that can be received per second
on the interfaces in a specified VLAN before the switch begins dropping the Layer 2 PDUs. The drop
threshold value must be less than or equal to the shutdown threshold value.
L2PT processing is done by the CPU, and L2PT... | [
{
"name": "number",
"desc": "Maximum number of Layer 2 PDUs of the specified protocol that can be received per second"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Example: Configuring Layer 2 Protocol Tunneling on EX Series Switches Without ELS Support",
"Configuring Layer 2 Protocol Tunneling on EX Series Switches Without ELS Support"
] |
drop-timeout (Forwarding Class) | drop-timeout milliseconds; | [edit class-of-service fragmentation-map map-name forwarding-class class-name] | Disable or set the resequencing timeout interval for each forwarding class of a multiclass MLPPP.
Default
If you do not include this statement, the default sequencing timeouts for T1 speeds (500 ms) or lower
(1500 ms) apply. | [
{
"name": "milliseconds",
"desc": "Time to wait for fragments. A value of 0 disables the resequencing logic for that forwarding"
}
] | 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 Drop Timeout Interval for Fragmentation by Forwarding Class"
] |
drop-timeout | drop-timeout milliseconds; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options],
[edit interfaces (ls-fpc/pic/port | ml-fpc/pic/port) unit logical-unit-number],
[edit logical-systems logical-system-name interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-
options],
[edit logical-systems logical-system-name interfaces (ls-fpc/... | For multilink and link services interfaces only, configure the drop timeout period, in milliseconds. | [
{
"name": "milliseconds",
"desc": "Drop timeout period."
}
] | 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 Link and Multilink Services Logical Interfaces"
] |
drop-unknown-mac-ip | drop-unknown-mac-ip; | [edit logical-systems name routing-instances name protocols evpn],
[edit routing-instances name protocols evpn],
[edit logical-systems name routing-instances name bridge-domains name bridge-options],
[edit routing-instances name bridge-domains name bridge-options],
[edit routing-instances name vlans n... | Disable dynamic learning of MAC-IP entries. The ingress PE router drops all ARP requests and NS
messages directed to unknown IP addresses. | [] | [none specified] | Statement introduced in Junos OS Release 23.4R1. | [] |
ds-lite | ds-lite ds-lite-softwire-concentrator {
auto-update-mtu;
flow-limit flow-limit | session-limit-per-prefix session-limit-per-prefix;
mtu-v6 bytes;
softwire-address softwire-address;
}
} | [edit services softwire softwire-concentrator]
[edit services softwires softwire-types] | Configure settings for a DS-Lite concentrator used to process IPv4 packets encapsulated in IPv6.
The ds-lite statement is supported on MX Series routers with MS-DPCs and on M Series routers with
MS-100, MS-400, and MS-500 line Multiservices PICs. Starting in Junos OS release 17.4R1, DS-Lite is
supported on MX Series ro... | [
{
"name": "bytes",
"desc": "Maximum transmission unit (MTU), in bytes, for encapsulating IPv4 packets into IPv6. If the final"
},
{
"name": "ds-lite-softwire-concentrator",
"desc": "Name applied to a DS-Lite softwire concentrator."
},
{
"name": "auto-update-mtu",
"desc": "This option... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
auto-update-mtu option introduced in Junos OS Release 10.4.
copy-dscp option introduced in Junos OS Release 11.2.
mtu-v6 option introduced in Junos OS Release 10.4.
softwire-address option introduced in Junos OS Release 10.4.
Support for DS-Lite at the [edit services softw... | [
"Configuring a DS-Lite Softwire Concentrator"
] |
dscp (Class of Service) | dscp rewrite-name {
import (rewrite-name | default);
forwarding-class class-name {
loss-priority level {
code-point [ aliases ] [ bit-patterns ];
}
}
} | [edit class-of-service rewrite-rules] | Define the Differentiated Services code point (DSCP) mapping that is applied to the packets. | [
{
"name": "classifier-name",
"desc": "Name of the classifier."
}
] | interfaces—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 Unicast Classifiers",
"Example: Configuring Classifiers",
"Defining CoS Code-Point Aliases",
"Defining CoS Rewrite Rules",
"Assigning CoS Components to Interfaces",
"Understanding CoS Classifiers",
"Understanding CoS Classifiers",
"Understanding CoS Rewrite Rules",
"Understandi... |
dscp (CoS Classifiers) | dscp classifier-name {
import (classifier-name | default);
forwarding-class class-name {
loss-priority level ] {
code-points [ aliases ] [ bit-patterns;
}
}
} | [edit class-of-service classifiers] | Define the diffserv code point (DSCP) mapping to apply to incoming packets. | [
{
"name": "classifier-name",
"desc": "Name of the classifier."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic",
"Applying DSCP Classifiers to MPLS Traffic"
] |
dscp (CoS Interfaces) | dscp (classifier-name | default); | [edit class-of-service interfaces interface-name classifiers] | For ACX Series Universal Metro routers, map the DSCP field of the incoming packet to the forwarding
class and packet loss priority based on the specified DSCP classifier. | [
{
"name": "classifier-name",
"desc": "Name of the previously defined DSCP behavior aggregate classifier."
},
{
"name": "default",
"desc": "Default DSCP behavior aggregate classifier."
}
] | 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. | [] |
dscp (Dynamic Classifiers) | dscp (classifier-name | default); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number classifiers] | For IPv4 traffic, apply a Differentiated Services (DiffServ) code point (DSCP) classifier to a subscriber
interface in a dynamic profile. | [
{
"name": "classifier-name",
"desc": "Name of a classifier mapping configured at the [edit class-of-service classifiers dscp]"
},
{
"name": "default",
"desc": "The default mapping."
}
] | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Classifier to a Subscriber Interface in a Dynamic Profile",
"classifiers (Definition)"
] |
dscp (Dynamic Rewrite Rules) | dscp (rewrite-name | default); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number rewrite-rules] | For IPv4 traffic, apply a Differentiated Services (DiffServ) code point (DSCP) rewrite rule to a subscriber
interface in a dynamic profile. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules dscp]"
},
{
"name": "default",
"desc": "The default mapping."
}
] | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Rewrite Rule Definition to a Subscriber Interface in a Dynamic Profile",
"rewrite-rules"
] |
dscp (flow-server) | dscp dscp-value; | [edit forwarding-options sampling instance instance-name family (inet | inet6) output flow-
server hostname] | Specify the Differentiated Services Code Point (DSCP) mapping that is applied to exported packets for
inline active flow monitoring. This allows different levels of service to be assigned to sampled traffic. | [
{
"name": "dscp",
"desc": ""
},
{
"name": "dscp-value",
"desc": "Can be a value between 0 and 63 (the default is 0). When the same flow-server is configured under both the inet and inet6 families in a sampling instance, use the same dscp value for both flow-server appearances. The dscp-value is ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F4.
Statement introduced in Junos OS Release 16.1 for the MX Series. | [
"Configuring Flow Aggregation to Use IPFIX Flow Templates on PTX Series Routers",
"Configuring Sampling Instance on MX, M and T Series Routers or QFX Series Switches"
] |
dscp (Input Congestion Notification) | dscp {
code-point [code-point-bits] {
pfc {
mru mru-value;
}
xon (Input Congestion Notification)
}
} | [edit class-of-service congestion-notification-profile name input] | Configure a Differentiated Services code point (DSCP) value and apply priority-based flow control (PFC)
to packets with that code point.
When this statement is configured, DSCP-based PFC can be invoked for untagged traffic by matching
specified 6-bit DSCP values in the Layer 3 IP header of incoming packets instead of a... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"Understanding PFC Using DSCP at Layer 3 for Untagged Traffic",
"Configuring DSCP-based PFC for Layer 3 Untagged Traffic",
"Configuring CoS PFC (Congestion Notification Profiles)",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)"
] |
dscp (Multifield Classifier) | dscp [0 | value]; | [edit firewall family family-name filter filter-name term term-name then] | Set the IPv4 Differentiated Services code point (DSCP) bit. You can specify a numerical value from 0
through 63. To specify the value in hexadecimal form, include 0x as a prefix. To specify the value in binary
form, include b as a prefix.
The default DSCP value is be (best effort), or 0.
For M320 and T Series routers, ... | [
{
"name": "value",
"desc": "For MX Series routers with MPCs, specify the field of incoming or outgoing packets in the range"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring and Applying Tricolor Marking Policers",
"Firewall Filter Nonterminating Actions"
] |
dscp (Rewrite Rules on Interfaces) | dscp (rewrite-name | default) protocol (inet-both | inet-outer | mpls); | [edit class-of-service interfaces interface-name rewrite-rules],
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | For IPv4 traffic, apply a Differentiated Services (DiffServ) code point (DSCP) rewrite rule to an interface.
Supported interfaces for rewrite rules depend on the platform and software release.
Logical interfaces do not support multiple dscp rewrite rules for the same protocol. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules dscp] hierarchy level."
},
{
"name": "default",
"desc": "The default mapping."
},
{
"name": "protocol inet-both",
"desc": "Rewrite the DSCP CoS value to both the ... | 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 Rewrite Rules",
"Applying Rewrite Rules to Output Logical Interfaces",
"Rewriting MPLS and IPv4 Packet Headers"
] |
dscp (Services CoS) | dscp (alias | bits); | [edit services cos application-profile profile-name (ftp | sip) (data | video | voice)],
[edit services cos rule rule-name term term-name then],
[edit services cos rule rule-name term term-name then reverse] | Define the Differentiated Services code point (DSCP) mapping that is applied to the packets. Change the
DSCP (or TOS) on the packet to the specified value. Any conformant bit string can be specified, but only
the default alias can be used. | [
{
"name": "alias",
"desc": "Name assigned to a set of CoS markers."
},
{
"name": "bits",
"desc": "Mapping value in the packet header."
}
] | 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 Actions in CoS Rules",
"Configuring CoS Rules on Services PICs"
] |
dscp (Subscriber Secure Policy) | dscp value; | [edit services radius-flow-tap policy policy-name inet drop-policy rule-name from],
[edit services radius-flow-tap policy policy-name inet6 drop-policy rule-name from] | Specify the DSCP value for the radius-flow-tap policy. | [
{
"name": "dscp-value",
"desc": "IPv4 or IPv6 dscp value for the radius-flow-tap policy."
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
dscp-code-point (CoS Host Outbound Traffic) | dscp-code-point value; | [edit class-of-service host-outbound-traffic] | Specify the value of the DSCP bits in the type of service (ToS) field of host outbound traffic (packets
generated by the local Routing Engine) as they are placed in the default or specified output queue on all
egress interfaces. This statement does not affect transit traffic or incoming traffic.
If you use the ping ope... | [
{
"name": "code-point",
"desc": "Six-bit DSCP code point value."
}
] | 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.
Support for distributed protocol handler traffic introduced in Junos OS Release 13.2. | [
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic",
"Default DSCP and DSCP IPv6 Classifiers",
"Changing the Default Queuing and Marking of Host Outbound Traffic"
] |
dscp-code-points (RFC 2544 Benchmarking) | dscp-code-points dscp-bits; | [edit services monitoring rfc2544 tests test-name test-name] | Specify the value of the Differentiated Services (DiffServ) field within the IP header of the test frames.
The DiffServ code point (DSCP) bits value must be set to a valid 6-bit pattern. If you do not specify this
value, 0 is used in the DSCP fields in the IP header. | [
{
"name": "dscp-bits",
"desc": "A valid 6-bit pattern; for example, 001111, or one of the following configured DSCP aliases:"
},
{
"name": "af11",
"desc": "Default: 001010"
},
{
"name": "af12",
"desc": "Default: 001100"
},
{
"name": "af13",
"desc": "Default: 001110"
},
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved Release 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
dscp-code-points (RPM) | dscp-code-points dscp-bits; | [edit services monitoring rpm owner name test name] | Specify the value of the Differentiated Services (DiffServ) field within the IP header. The DiffServ code
point (DSCP) bits value must be set to a valid 6-bit pattern. | [
{
"name": "dscp-bits",
"desc": "A valid 6-bit pattern; for example, 001111, or one of the following configured DSCP aliases:"
},
{
"name": "af11",
"desc": "Default: 001010"
},
{
"name": "af12",
"desc": "Default: 001100"
},
{
"name": "af13",
"desc": "Default: 001110"
},
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.3 for EX Series switches.
Statement introduced in Junos OS Release for PTX Series Packet Transport routers.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in J... | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.