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 |
|---|---|---|---|---|---|---|---|
decompress-layer | decompress-layer (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | The Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, decompress layer error is the error returned by the scan engine when the scanned file
has too many compression layers. The default action is block.
The [edit security utm default-configuration] hierarchy l... | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | [
"Full Antivirus Configuration Overview"
] | |
decompress-layer-limit | decompress-layer-limit decompress-layer-limit; | [edit security utm default-configuration anti-virus scan-options] | When an antivirus scan engine scans a file for viruses, the scan engine decompresses the layers of
nested compressed files and files with embedded extractable objects. Embedded extractable objects
include files such as archive files (tar), MS Word, and PowerPoint files. For example, if a message
contains a compressed .... | [
{
"name": "decompress-layer-limit",
"desc": "Specify the number of decompression layer limit. Default: 3 Range: 0 through 10"
}
] | 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 Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10 onwards.
Support at the [edit security utm default-configuration] hierarchy level introduced in Junos OS Release
18.2R1.
The [edit anti-virus scan-options] hierarchy level is deprecated in Ju... | [
"On-Device Avira Antivirus",
"Full Antivirus Configuration Overview"
] |
decryption-failures | decryption-failures {
threshold value;
} | [edit security alarms potential-violation] | Raise a security alarm after exceeding a specified number of decryption failures.
Default
Multiple decryption failures do not cause an alarm to be raised. | [
{
"name": "failures",
"desc": "Number of decryption failures up to which an alarm is not raised. When the configured number"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"IPsec Overview",
"Monitoring VPN Traffic"
] |
dedicated-buffer | dedicated-buffer {
egress {
percent percent;
}
ingress {
percent percent;
}
} | [edit class-of-service] | Set the global dedicated buffer pool of the device as a percent of its default. This, in effect, increases the
shared buffer pool.
NOTE: You can descrease the dedicated-buffer (thereby increasing the shared buffer pool),
or decrease the shared-buffer (thereby increasing the dedicated buffer pool), but not both. | [
{
"name": "egress percent percent",
"desc": "Set the global egress dedicated buffer size as a percentage of its default. Range: 15-100 percent Default: 100 percent"
},
{
"name": "ingress percent percent",
"desc": "Set the global ingress dedicated buffer size as a percentage of its default. Range... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.2R1. | [
"Configuring Ingress and Egress Dedicated Buffers"
] |
dedicated-buffer-profile | dedicated-buffer-profile name {
egress {
buffer-size {
( cells | none);
}
}
ingress {
buffer-size {
( cells | none);
}
}
} | [edit class-of-service] | Dedicated buffer profile configuration.
By default, the operating system calculates port level dedicated buffers internally. Therefore, even ports
that are down or unused also get an equal amount of dedicated buffer space that is then unavailable to
any traffic burst. dedicated-buffer-profile provides the ability to in... | [
{
"name": "name",
"desc": "Name the buffer profile. You apply a dedicated buffer profile to a physical interface by this name."
},
{
"name": "egress buffer-size cells",
"desc": "Set the egress dedicated buffer size for a port as a number of cells or none for no dedicated buffer. Range: 20-100,00... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.2R1. | [
"Configuring Ingress and Egress Dedicated Buffers"
] |
dedicated-ukern-cpu (BFD) | dedicated-ukern-cpu; | [edit chassis] | Enable the dedicated Bidirectional Forwarding Detection (BFD) protocol. One dedicated CPU core is
allocated for the flowd ukernel thread to handle the dedicated BFD. This ensures that the BFD packet
processing does not compete with the Routing Engine daemons. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D100. | [
"Enabling Dedicated and Real-Time BFD"
] |
deep-vlan-qualified-learning | deep-vlan-qualified-learning vlan_tag_number; | [edit interfaces interface-name unit logical_unit_number] | Enable qualified MAC learning on the third VLAN tag (innermost) of an ingress 3-tagged packet, without
any kind of implicit VLAN manipulation. If the packet has 2 tags, MAC learning happens on the second
VLAN. If the ingress packet has more than 3 tags, all tags beyond the third tag are treated as part of data
and not... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Command introduced in Junos OS Release 17.4R1. | [
"Understanding Qualified MAC Learning"
] |
default (CoS Host Outbound Traffic) | default value; | [edit class-of-service host-outbound-traffic ieee-802.1] | Apply a global default value to the IEEE 802.1p—priority code point (PCP)—field in the Ethernet frame
header for all host outbound traffic. | [
{
"name": "value",
"desc": "Three-bit binary number or code point alias. Range: 000 through 111"
}
] | 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. | [
"Host Outbound Traffic IEEE802.1p Rewrite",
"Rewriting Packet Headers to Ensure Forwarding Behavior"
] |
default (CoS) | default; | [edit class-of-service virtual-channel-groups group-name virtual-channel-name] | Specify the default channel. You must configure one of the virtual channels in the group to be the
default. Any traffic not explicitly directed to a virtual channel is transmitted by way of this default. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
default (Security Antivirus Sophos Engine) | default (block | log-and-permit | permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name fallback-
options] | All errors other than those specifically listed fall into this category. This could include either unhandled
system exceptions (internal errors) or other unknown errors. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
},
{
"name": "permit",
"desc": "Permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
default (Security Antivirus) | default (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
fallback-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | All errors other than those specifically listed fall into this category. This could include either unhandled
system exceptions (internal errors) or other unknown errors. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
default (Security Content Security) | default (block |log-and-permit | permit); | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name] | Specify the default action to take for a URL. | [
{
"name": "block",
"desc": "Log the error and deny the traffic."
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic."
},
{
"name": "permit",
"desc": "Permit the traffic."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
default (Security Web Filtering) | default (block | log-and-permit | permit | quarantine); | [edit security utm default-configuration],
[edit security utm feature-profile web-filtering surf-control-integrated profile profile-name
fallback-settings],
[edit security utm feature-profile web-filtering websense-redirect profile profile-name fallback-
settings],
[edit security utm feature-profile web-filtering jun... | Specify an action for the profile, for requests that experience internal errors in the Web-filtering module. | [
{
"name": "block",
"desc": "Log the error and deny the traffic."
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic."
},
{
"name": "permit",
"desc": "Permit the traffic."
},
{
"name": "quarantine",
"desc": "Show the warning message and permit/blo... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Surf-Control feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 11.4.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
default-action (DHCP Relay Agent Option) | default-action {
drop;
forward-only;
local-server-group local-server-group;
relay-server-group relay-server-group;
} | [edit forwarding-options dhcp-relay relay-option],
[edit forwarding-options dhcp-relay dhcpv6 relay-option],
[edit forwarding-options dhcp-relay group group-name relay-option],
[edit forwarding-options dhcp-relay dhcpv6 group group-name relay-option],
[edit logical-systems logical-system-name forwarding-options dhcp-re... | Specify the action DHCP relay agent takes when the option string in client traffic does not satisfy any
match criteria or when no match criteria are configured.
The default-action statement is optional. If the match criteria are not satisfied or not configured and no
default-action is specified, DHCP relay processes th... | [] | 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",
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
default-action (Protocols OpenFlow) | default-action (drop | packet-in); | [edit protocols openflow switch switch-name] | Specify the default action that is executed when an OpenFlow packet does not match an existing flow
entry. The default action is specific to the OpenFlow virtual switch and is the same across all filters
associated with that virtual switch.
Default
If you do not include the default-action statement, the default action ... | [
{
"name": "drop",
"desc": "Drop packets that do not match an existing flow entry."
},
{
"name": "packet-in",
"desc": "Accept packets that do not match an existing flow entry, and forward the packet to the controller."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Understanding Support for OpenFlow on Devices Running Junos OS",
"Understanding OpenFlow Flows and Filters on Devices Running Junos OS"
] |
default-actions | default-actions {
interface-down;
} | [edit protocols oam ethernet connectivity-fault-management action-profile profile-name] | Define the action to be taken when connectivity to the remote MEP is lost.
Default
If no action is configured, no action is taken. | [
{
"name": "interface-down",
"desc": "When a remote MEP connectivity failure is detected, bring the interface down."
}
] | 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. | [
"Configuring a CFM Action Profile to Specify CFM Actions for CFM Events"
] |
default-address-selection | default-address-selection; | [edit system] | Use the loopback interface, lo0, as the source address for all locally generated IP packets when the
packet is sent through a routed interface, and also when the packet is sent through a local interface such
as fxp0. The lo0 interface is the interface to the router's or switch's Routing Engine.
The default address is u... | [] | 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. | [
"Configure TCP Options",
"Select a Fixed Source Address for Locally Generated TCP/IP Packets",
"Configure Default, Primary, and Preferred Addresses and Interfaces"
] |
default-chap-secret | default-chap-secret name; | [edit interfaces interface-name ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options chap] | Define the default CHAP secret to be used when no matching CHAP access profile exists.
For ATM2 IQ interfaces only, you can configure a default CHAP secret on the logical interface unit if the
logical interface is configured with one of the following PPP over ATM encapsulation types:
•
atm-ppp-llc—PPP over AAL5 LLC en... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring a Default CHAP Secret",
"access-profile"
] |
default-client-identity (NETCONF TLS) | default-client-identity {
map-type (san-dirname-cn | specified);
username username;
} | [edit system services netconf tls] | For NETCONF sessions over Transport Layer Security (TLS), configure the default method to derive the
NETCONF username for clients that do not match any configured clients.
If the fingerprint of a client’s presented certificate does not match the fingerprint for any client
configured at the [edit system services netconf... | [
{
"name": "map-type",
"desc": ""
},
{
"name": "type",
"desc": "Map type that defines how to derive the NETCONF username. Values:"
},
{
"name": "san-dirname-cn",
"desc": "Use the common name (CN) defined for the SubjectAltName’s (SAN)"
},
{
"name": "specified",
"desc": "U... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1.
Statement introduced in Junos OS Evolved Release 21.4R1. | [] |
default-gateway | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
evpn],
[edit protocols evpn],
[edit routing-instances routing-instance-name protocols evpn] | Specify the behavior for IRB interfaces defined as default gateways in an EVPN fabric.
We require that you configure the no-gateway-community option if you configure a virtual gateway address
on an IRB interface in the EVPN routing instance for IPv4 or IPv6 using the following commands:
•
set interfaces irb unit unit-n... | [
{
"name": "advertise",
"desc": "Advertise the default gateway MAC address. This is the default behavior."
},
{
"name": "do-not-advertise",
"desc": "Don't advertise the default gateway MAC address."
},
{
"name": "no-gateway-community",
"desc": "Advertise virtual gateway addresses and ... | [
"Anycast Gateways"
] | |||
default-isid | default-isid isid-number; | [edit routing-instances routing-instance-name service-groups service-group-name pbb-service-options] | For IEEE 802.1ah provider backbone bridge (PBB) configurations, configure the default service identifier
(I-SID) for all unmapped service VLANs (S-VLANs ) for the customer routing instance (I-component)
service group. | [
{
"name": "default-isid",
"desc": "Default service identifier. Enter an I-SID in the range from 256 through 16777214."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.0. | [
"Example: Configuring E-LINE and E-LAN Services for a PBB Network on MX Series Routers"
] |
default-lifetime (Dynamic Router Advertisement) | default-lifetime seconds; | [edit protocols router-advertisement interface interface-name] | Lifetime associated with a default router. | [
{
"name": "seconds",
"desc": "Default lifetime. A value of 0 means this router is not the default router."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
default-lifetime | default-lifetime seconds; | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Configure the lifetime associated with a default router. | [
{
"name": "seconds",
"desc": "Default lifetime. A value of 0 means this router is not the default router."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery"
] |
default-local-policy | default-local-policy {
flow-action (drop | forward);
maximum-bit-rate uplink mbr-uplink-value downlink mbr-downlink-value;
burst-size uplink uplink-burst-size downlink downlink-burst-size;
} | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber] | Specify the default local policy, which is applied to the IP-based subscriber’s data packets entering the
access interface of the TDF domain when a TDF subscriber session does not exist.
The remaining statements are explained separately. See CLI Explorer. | [] | 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"
] |
default-lsa | default-lsa {
default-metric metric;
metric-type type;
type-7;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast) area area-id nssa],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf ... | On area border routers only, for a not-so-stubby area (NSSA), inject a default link-state advertisement
(LSA) with a specified metric value into the area. The default route matches any destination that is not
explicitly reachable from within the area.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "default-metric",
"desc": ""
},
{
"name": "metric",
"desc": "Metric value, ranging from 1 through 16,777,215."
},
{
"name": "metric-type type",
"desc": "Metric type 1 or 2. The configured metric determines the method used to compute the cost"
},
{
"name": "to a dest... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches. | [
"Understanding OSPF Areas",
"Example: Configuring OSPF Not-So-Stubby Areas"
] |
default-pap-password | default-pap-password password; | [edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options pap] | For PAP authentication, the default PAP password. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring the PPP Password Authentication Protocol",
"access-profile"
] |
default-peer | default-peer; | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name protocols msdp group group-name],
[edit logical-systems logical-system-name protocols msdp group group-name peer address],
[edit logical-systems logical-system-name protocols msdp peer address],
[edit logical-systems lo... | Establish this peer as the default MSDP peer and accept source-active messages from the peer without
the usual peer-reverse-path-forwarding (peer-RPF) check. | [] | 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"
] |
default-policy (IDP) | default-policy default-policy; | [edit security idp] | Specify which policy among the configured policies to be configured as the default IDP policy.
When you have multiple IDP policies configured and when policy conflict occurs, then the policy
configured as default the IDP policy will be applied for a given session. | [
{
"name": "default-policy",
"desc": "Name of the default policy."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1.
An IDP policy is directly assigned in the security policy rule. This is to simplify IDP policy usage. As a
part of session interest check, IDP is enabled if an IDP policy is present in any of the matched rules. An
IDP policy is activated in security policies by permittin... | [] |
default-policy | default-policy (deny-all | permit-all); | [edit security policies] | Configure the default security policy that defines the actions the device takes on a packet that does not
match any user-defined policy. | [
{
"name": "deny-all",
"desc": "Deny all traffic. Packets are dropped. This is the default."
},
{
"name": "permit-all",
"desc": "Permit all traffic that does not match a policy."
}
] | 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. | [
"Security Policies Overview"
] |
default-pool (Address Pools) | default-pool; | [edit access address-assignment address-pools name] | Configure the address pool as a default pool. A TDF domain uses the default address pool to specify the
source IP addresses of packets that undergo TDF processing when an address pool is not specified for
the TDF domain. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Understanding Source IP Filtering with Address Pools in TDF Domains for IP-Based Subscribers",
"Configuring Address Pools for Source-IP Filtering of IP-Based Subscribers",
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain"
] |
default-prefixes (Protocols RIFT) | default-prefixes {
family {
(inet sets-of-ipv4-address | inet6 sets-of-ipv6-address);
}
} | [edit protocols rift] | Explicitly specify default prefixes generated in southbound direction.
This is helpful in cases where you have an internet default route and you want to inject the route from a
leaf node without overlays. If the IP fabric originates default routes, you cannot differentiate between
them and this might cause a null route... | [
{
"name": "family",
"desc": "Specify the family type for the default prefixes to be generated in the southbound direction."
},
{
"name": "inet ipv4-address",
"desc": "Specify the IPv4 IP addresses for the default prefixes to be generated in the southbound direction."
},
{
"name": "inet6 ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Implementation of Routing in Fat Tree (RIFT) Protocol"
] |
default-profile (Juniper Secure Connect) | default-profile default-profile; | [edit security remote-access] | Configure default profile. On your security device, you must specify one of the remote-access profiles as
the default profile.
NOTE: Starting in Junos OS Release 23.1R1, we’ve hidden the default-profile option at
the [edit security remote-access] hierarchy level. In releases before Junos OS Release
23.1R1, you use this... | [] | security | Statement introduced in Junos OS Release 20.3R1
The default-profile option is not available in SRX Series Firewalls starting Junos OS Release 23.1R1. | [
"Juniper Secure Connect Administrator Guide"
] |
default-profile | default-profile profile-name; | [edit access firewall-authentication pass-through],
[edit access firewall-authentication web-authentication] | Specify the authentication profile to use if no profile is specified in a policy. | [
{
"name": "profile-name",
"desc": "Name of the profile."
}
] | 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. | [
"SRX Firewall Users",
"[edit access firewall-authentication]",
"Captive Portal with Junos OS Enforcer"
] |
default-rule | default-rule {
(deny [block-message] | permit | reject [block-message]);
} | [edit security application-firewall rule-sets rule-set-name] | Configure the default rule that defines the actions to be performed on a packet that does not match any
defined rule.
An application firewall permits, rejects, or denies traffic based on the application of the traffic. The
firewall consists of one or more rule sets with rules that specify match criteria, including dyna... | [
{
"name": "deny",
"desc": "Block the traffic at the firewall. The device drops the packet. No message is returned to the"
},
{
"name": "block-message",
"desc": "(Optional) In application firewall rules, provide information to the user regarding"
},
{
"name": "permit",
"desc": "Permit... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. Statement updated in Junos OS Release 12.1X44-D10
with the reject option. The block-message option added in Junos OS Release 12.1X45-D10. | [
"Example: Configuring Application Firewall Rule Sets Within a Security Policy"
] |
default-ssl-termination-profile (Access) | default-ssl-termination-profile default-ssl-termination-profile; | [edit access firewall-authentication user-firewall] | Specify the default ssl termination profile used for firewall authentication. | [
{
"name": "default-ssl-termination-profile",
"desc": "Name of default SSL termination profile to use"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [
"[edit access firewall-authentication]",
"user-firewall",
"SAML Authentication in Juniper Secure Connect"
] |
default-trusted-ca-certs (Security) | default-trusted-ca-certs {
automatic-download {
deactivate;
interval {
hours value;
}
url value;
routing-instance value;
}
} | [edit security pki] | Dynamic update of trusted CA bundle requires -
•
Downloading of trusted CA bundle from Juniper Networks security website, https://
signatures.juniper.net/cacert or a custom URL.
•
Uploading trusted CA bundle to PKI.
•
Periodic polling of trusted CA bundle.
This functionality is configured using the statement default-t... | [
{
"name": "automatic-download",
"desc": "Sets automatic download of CA certs configuration."
},
{
"name": "deactivate",
"desc": "Disables automatic download of default CA certs. Use this option when automatic download is configured and you plan to disable it."
},
{
"name": "interval",
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1. | [
"pki",
"Dynamic Updated of CA Bundle"
] |
default-value | default-value default-value; | [edit dynamic-profiles profile-name variables variable-name] | Configure a default value for a user-defined variable in a dynamic profile. The values that the system
uses for these variables are applied when the subscriber authenticates. | [
{
"name": "default-value",
"desc": "Default value for the variable."
}
] | 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. | [
"User-Defined Variables",
"Using Variable Expressions in User-Defined Variables",
"Configuring User-Defined Dynamic Variables in Dynamic Profiles"
] |
default-vpn-source | default-vpn-source {
interface-name interface-name;
} | [edit logical-systems logical-system-name protocols pim],
[edit protocols pim] | Enable the router to use the primary loopback address configured in the default routing instance as the
source address when PIM hello messages, join messages, and prune messages are sent over multicast
tunnel interfaces for interoperability with other vendors’ routers.
The remaining statements are explained separately.... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
defaults (ACX series, JRR200, MX204, PTX5000, and VRR) | defaults {
ebgp {
no-policy {
advertise (accept | reject | reject-always);
receive (accept | reject | reject-always);
}
}
} | [edit fabric protocols bgp],
[edit logical-systems name protocols bgp],
[edit logical-systems name routing-instances name protocols bgp],
[edit logical-systems name tenants name routing-instances name protocols bgp],
[edit protocols bgp],
[edit routing-instances name protocols bgp],
[edit tenants name routing-instances... | You can specify the route propagation of EBGP speakers when no explicit policy is configured. | [] | routing | Hierarchy defaults ebgp no-policy introduced at protocols bgp in Junos OS Release 20.3R1. | [
"Implicit filter for Default EBGP Route Propagation Behavior without Policies"
] |
defaults (early-aging) | defaults {
cutoff-time {
(percent percent | seconds seconds);
}
} | [edit security flow aging early-aging] | It is the default cutoff time of early-ageout, it is not configured using the options like protocol or
application. | [
{
"name": "seconds",
"desc": "Amount of time that elapses before the device aggressively ages out a session."
}
] | 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.4R1. | [] |
defaults (Policy Options) | defaults {
asregex-optimize (no-optimize | optimize);
route-filter (no-walkup | walkup);
} | [edit logical-systems logical-system-name policy-options],
[edit logical-systems logical-system-name policy-options policy-statement policy-statement-name],
[edit policy-options],
[edit policy-options policy-statement policy-statement-name] | Establish defaults for a particular policy statement or globally. Defaults include the walkup feature,
which examines more than the longest match route filters in a policy statement term with more than
one route filter, allowing consolidation of terms and a potential performance enhancement. | [] | 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. | [
"Walkup for Route Filters Overview",
"Configuring Walkup for Route Filters to Improve Operational Efficiency",
"Example: Configuring Walkup for Route Filters Globally to Improve Operational Efficiency",
"Example: Configuring Walkup for Route Filters Locally to Improve Operational Efficiency"
] |
defaults | defaults {
(accounting | no-accounting);
group-policy [ policy-names ];
query-interval seconds;
query-response-interval seconds;
robust-count number;
ssm-map ssm-map-name;
version version;
} | [edit logical-systems logical-system-name statement-name protocols igmp amt relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name statement-name
protocols igmp amt relay],
[edit protocols igmp amt relay],
[edit routing-instances routing-instance-name statement-name protocols igmp am... | Configure default IGMP attributes for all Automatic Multicast Tunneling (AMT) interfaces.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the AMT Protocol"
] |
defer-initial-multipath-build | defer-initial-multipath-build {
maximum-delay maximum-delay;
} | [edit logical-systems name protocols bgp family inet unicast],
[edit logical-systems name protocols bgp family inet inet6 unicast],
[edit logical-systems name protocols bgp group name family inet unicast],
[edit logical-systems name protocols bgp group name family inet inet6 unicast],
[edit logical-systems name protoco... | Defer initial multipath calculation until all BGP routes are received. When multipath is enabled, BGP
inserts the route into the multipath queue each time a new route is added or whenever an existing route
changes. When multiple paths are received through BGP add-path feature, BGP might calculate one
multipath route mu... | [
{
"name": "maximum-delay",
"desc": "Specify a value in seconds to indicate the maximum time that a device must delay the multipath calculation after a peer is up. Range: 1 through 3600 seconds"
}
] | routing | Statement introduced in Junos OS Release 18.1R1. | [
"Understanding BGP Multipath"
] |
definition (Protocols OSPF) | definition {
(spf | strict-spf);
metric-type (igp-metric | te-metric);
priority priority;
} | [edit logical-systems name routing-instances name routing-options flex-algorithm],
[edit logical-systems name routing-options flex-algorithm],
[edit logical-systems name tenants name routing-instances name routing-options flex-algorithm],
[edit routing-instances name routing-options flex-algorithm],
[edit routing-optio... | Configure the flex-algorithm definition (FAD) and specify the parameters of the definition. OSPFv2
calculates the path based on these specified parameters of the FAD. We recommend configuring flexible
algorithm on only a couple of routers to provide redundancy and to avoid conflicts. | [
{
"name": "spf",
"desc": "Normal SPF of type 0"
},
{
"name": "strict-spf",
"desc": "Strict SPF"
},
{
"name": "metric-type",
"desc": "Specify the metric type that you would like to use in your network. Values:"
},
{
"name": "igp-metric",
"desc": "Specify this option to us... | routing | Statement introduced in Junos OS Release 21.1R1. | [
"Understanding OSPF Flexible Algorithm for Segment Routing",
"Example: OSPF Flexible Algorithm",
"flex-algorithm (Protocols OSPF)",
"definition (Protocols OSPF)"
] |
definition | definition {
admin-group (exclude | include-all | include-any)
(spf | strict-spf);
exclude-srlg (test1 test2)
metric-type (delay-metric | igp-metric | te-metric);
priority priority;
use-flex-algorithm-prefix-metric;
} | [edit logical-systems name routing-instances name routing-options flex-algorithm],
[edit logical-systems name routing-options flex-algorithm],
[edit logical-systems name tenants name routing-instances name routing-options flex-algorithm],
[edit routing-instances name routing-options flex-algorithm],
[edit routing-optio... | Configure the flex-algorithm definition (FAD) and specify the parameters of the definition. IS-IS
calculates the path based on these specified parameters of the FAD. We recommend configuring flexible
algorithm on only a couple of routers to provide redundancy and to avoid conflicts. | [
{
"name": "admin-group",
"desc": "Specify the administrative groups to include or exclude along a specified path. Values:"
},
{
"name": "exclude",
"desc": "Specify this option to exclude an admin-group, all of which must be"
},
{
"name": "include-all",
"desc": "Specify this option t... | routing | Statement introduced in Junos OS Release 19.4R1. | [
"Configuring Flexible Algorithm for Segment Routing",
"How to Configure Flexible Algorithms in IS-IS for Segment Routing Traffic Engineering"
] |
degraded | degraded {
action-fpc-restart-disable;
degraded-fabric-detection-enable;
degraded-fpc-bad-plane-threshold number-of-bad-planes;
} | [edit chassis fabric] | Configure options that apply to degraded chassis fabric conditions.
In Junos OS Evolved, for the fabric planes to be available for the Packet Forwarding Engines, the
following conditions must be met:
•
The associated SIBs are in online state.
•
The fabric ASICs are initialized.
•
The links between the Packet Forwarding... | [
{
"name": "action-fpc-restart-disable",
"desc": "Allow the user to disable restarting of the FPCs during healing from a"
},
{
"name": "degraded-fabric-detection-enable",
"desc": "Enable detection of an FPC with degraded fabric."
},
{
"name": "degraded-fpc-bad-plane-threshold number-of-ba... | 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.
Statement “action-fpc-restart-disable” introduced in Junos OS Release 12.1. | [
"Fabric Resiliency and Degradation",
"Disabling Line Card Restart to Limit Recovery Actions from Degraded Fabric Conditions"
] |
delay (PPPoE Service Name Tables) | delay seconds; | [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] | Configure the PPPoE underlying interface on the router to wait a specified number of seconds after
receiving a PPPoE Active Discovery Initiation (PADI) control packet from a PPPoE client before sending a
PPPoE Active Discovery Offer (PADO) packet to indicate that it can service the client request
The router (PPPoE serv... | [
{
"name": "seconds",
"desc": "Number of seconds that the PPPoE underlying interface waits after receiving a PADI packet"
}
] | 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"
] |
delay (querier) | delay {
traffic-class tc-value {
average-sample-size sample size;
padding-size size;
query-interval milliseconds;
rtt-delay-threshold rtt threshold value;
twcd-delay-threshold twcd threshold value;
}
} | [edit protocols mpls oam performance-monitoring querier],
[edit protocols mpls label-switched-path lsp-name oam performance-monitoring querier],
[edit protocols mpls label-switched-path lsp-name primary path-name oam performance-monitoring
querier],
[edit protocols mpls label-switched-path lsp-name secondary path-name... | Configure delay measurement options.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Pro-Active Loss and Delay Measurements",
"On-Demand Packet Loss and Delay Measurement for UHP LSPs Overview"
] |
delay (responder) | delay {
min-query-interval milliseconds;
} | [edit protocols mpls oam performance-monitoring responder],
[edit protocols mpls label-switched-path lsp-name oam performance-monitoring responder],
[edit protocols mpls label-switched-path lsp-name primary path-name oam performance-monitoring
responder],
[edit protocols mpls label-switched-path lsp-name secondary pat... | Configure delay measurement options. | [
{
"name": "min-query-interval",
"desc": ""
},
{
"name": "milliseconds",
"desc": "(Optional) Specify the minimum query interval that the responder supports. If the minimum query interval of the responder is greater than the query interval configured at querier, the effective message query rate wi... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Pro-Active Loss and Delay Measurements",
"On-Demand Packet Loss and Delay Measurement for UHP LSPs Overview"
] |
delay | delay delay-value; | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name calculation-weight] | Configure the calculation weight for delay. | [
{
"name": "delay-value",
"desc": "Calculation weight for delay."
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
delay-advertise (DHCPv6) | delay-advertise {
based-on (option-15 | option-16 | option-18 | option-37) {
equals {
ascii ascii-string;
hexadecimal hexadecimal-string;
}
not-equals {
ascii ascii-string;
hexadecimal hexadecimal-string;
}
starts-with {
... | [edit logical-systems name routing-instances name system services dhcp-local-server dhcpv6 group
group-name interface interface-name overrides]
[edit logical-systems name routing-instances name system services dhcp-local-server dhcpv6 group
group-name overrides]
[edit logical-systems name routing-instances name syste... | Delay sending a DHCPv6-advertise message to specified clients. The configured server sends the
advertise message when the delay timer expires. If the client is already bound to another server when it
receives this advertise message, the DHCPv6 server that delayed the message releases the client. You
can change the dela... | [
{
"name": "ascii-string",
"desc": "Value of the option expressed as an ASCII string."
},
{
"name": "based-on",
"desc": "Specify the DHCPv6 option received in the solicit message that is compared with the configured value on the local server."
},
{
"name": "option-15",
"desc": "DHCPv6... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Delaying DHCP Offer and Advertise Responses to Load Balance DHCP Servers"
] |
delay-authentication (DHCP Relay Agent) | delay-authentication; | [edit forwarding-options dhcp-relay ... overrides],
[edit forwarding-options dhcp-relay dhcpv6 ... overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ... overrides],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay ... over... | Delay authentication of subscribers until the DHCP client sends a Request packet. This conserves
managed resources by delaying the authorization process and the creation of an entry in the subscriber
database until the DHCP request processing phase. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Extended DHCP Relay Agent Overview",
"Overriding the Default DHCP Relay Configuration Settings"
] |
delay-buffer-rate (Dynamic Traffic Shaping) | delay-buffer-rate (percent percentage | rate | $junos-cos-delay-buffer-rate); | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | Base the delay-buffer calculation on a delay-buffer rate.
Default
If you do not include this statement, the delay-buffer calculation is based on the guaranteed rate if one
is configured, or the shaping rate if no guaranteed rate is configured. | [
{
"name": "rate",
"desc": "Delay-buffer rate, in bits per second (bps). You can specify a value in bits per second either as a"
},
{
"name": "$junos-cos-delay-buffer-rate",
"desc": "Junos predefined variable that is replaced with the delay-buffer rate"
}
] | 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.
The $junos-cos-delay-buffer-rate variable introduced in Junos OS Release 9.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Traffic Scheduling and Shaping for Subscriber Access"
] |
delay-buffer-rate | delay-buffer-rate (percent percentage | rate); | [edit class-of-service traffic-control-profiles profile-name] | For Gigabit Ethernet IQ, Channelized IQ PICs, and FRF.15 and FRF.16 LSQ interfaces only, base the
delay-buffer calculation on a delay-buffer rate.
Default
If you do not include this statement, the delay-buffer calculation is based on the guaranteed rate if one
is configured, or the shaping rate if no guaranteed rate i... | [
{
"name": "percent",
"desc": ""
},
{
"name": "percentage",
"desc": "For LSQ interfaces, delay-buffer rate as a percentage of the available interface bandwidth. Range: 1 through 100 percent"
},
{
"name": "rate",
"desc": "Delay-buffer rate, in bits per second (bps). You can specify a ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Oversubscribing Interface Bandwidth",
"Providing a Guaranteed Minimum Rate",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping"
] |
delay-comp | delay-comp{
interface ifd-name
{
transmit tx-comp-in-nsec;
receive rx-comp-in-nsec;
}
} | [edit protocols ptp] | Configure Precision Time Protocol (PTP) delay compensation values. | [
{
"name": "interfaces",
"desc": "The interface that you configure PTP delay compensation for."
},
{
"name": "transmit",
"desc": "PTP delay compensation for transmit direction."
},
{
"name": "receive",
"desc": "PTP delay compensation for receive direction."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.4R2 | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"IEEE 1588v2 Precision Timing Protocol (PTP)",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] |
delay-factor | delay-factor {
no-syslog-generation;
generate-snmp-traps;
storm-control {
count number;
interval number;
}
alarm-mode {
mdi-records-count number;
average;
}
} | [edit services] | Configure the maximum observed time difference between the arrival of media data and the drain of
media data. The delay factor suggests the minimum size of the buffer required at the next downstream
node. As a stream progresses, the variation of the delay factor indicates packet bunching or packet gaps
(jitter). Great... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Inline Video Monitoring on MX Series Routers"
] |
delay-measurement (Protocols IS-IS) | delay-measurement {
advertisement (Delay Measurement);normalize {
interval value
offset value
}
probe-count seconds;
probe-interval seconds;
threshold;
} | [edit protocols isis interface name] | Enable delay measurement. | [
{
"name": "normalize",
"desc": "Normalize Measured Link Delay interval valueThe value of the normalized interval in microseconds. Range: 1 through 5000000 microseconds) offset valueThe value of the normalized offset in microseconds (Must be < normalized interval). Range: 1 through 5000000 microseconds)"
... | routing | [
"Understanding Link Delay Measurement and Advertising in IS-IS"
] | |
delay-measurement (Protocols OSPF) | delay-measurement {
advertisement {
accelerated {
threshold percentage;
}
periodic {
interval seconds;
threshold percentage;
... | [edit protocols ospf area areainterface name] | Enable delay measurement. | [
{
"name": "advertisement",
"desc": ""
},
{
"name": "delay advertisement",
"desc": ""
},
{
"name": "probe-count",
"desc": "Probe count (seconds) Range: 1 through 15 Values:"
},
{
"name": "normalize",
"desc": "Enable you to configure delay normalization. interval-The val... | routing | Statement introduced in Junos OS Release 21.4R1 | [] |
delay-measurement (Source Packet Routing) | delay-measurement {
advertisement {
accelerated {
threshold percentage;
}
periodic {
interval seconds;
threshold percentage;
}
}
probe-count seconds;
probe-interval seconds;
} | [edit protocols source-packet-routing source-routing-path candidate-path-name] | Enable delay measurement for the specified segment routing candidate path. The protocol initiates
delay measurement for all segment-lists configured for the candidate path. Note that the candiddate
path must not be delegated and at least one configured primary or secondary path must have a
configured return path.
Make ... | [
{
"name": "advertisement",
"desc": "Enable advertising of link latency information to devices configured with SR-TE. accelerated: Enable accelerated advertisement of delay measurement data to devices. By Default, accelerated advertisement is disabled and advertisement occurs periodically. threshold: Speci... | routing | Statement introduced in Junos OS Evolved Release 24.4R1. | [] |
delay-metric (Protocols OSPF) | delay-metric microseconds; | [edit protocols ospf interface name] | Delay metric (microseconds)
Range:
•
0 through 16777215 | [] | routing | Statement introduced in Junos OS Release 21.4R1 | [] |
delay-metric | delay-metric microseconds; | [edit protocols isis interface name] | Delay metric (microseconds) | [] | routing | [] | |
delay-offer (DHCPv4) | delay-offer {
based-on (option-60 | option-77 | option-82) {
equals {
ascii ascii-string;
hexadecimal hexadecimal-string;
}
not-equals {
ascii ascii-string;
hexadecimal hexadecimal-string;
}
starts-with {
ascii ascii... | [edit logical-systems name routing-instances name system services dhcp-local-server group group-
name interface interface-name overrides]
[edit logical-systems name routing-instances name system services dhcp-local-server group group-
name overrides]
[edit logical-systems name routing-instances name system services dhc... | Delay sending a DHCP-offer message to specified clients. The configured server sends the offer
message when the delay timer expires. If the client is already bound to another server when it receives
this offer message, the DHCPv4 server that delayed the message releases the client. You can change the
delay value at any... | [
{
"name": "ascii ascii-string",
"desc": "Value of the option expressed as an ASCII string."
},
{
"name": "based-on",
"desc": "Specify the DHCPv4 option received in the discover message that is compared with the configured value on the local server."
},
{
"name": "option-60",
"desc": ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Delaying DHCP Offer and Advertise Responses to Load Balance DHCP Servers"
] |
delay-route-advertisements | delay-route-advertisements {
minimum-delay {
routing-uptime routing-uptime;
inbound-convergence inbound-convergence;
}
maximum-delay {
route-age routing-age;
routing-uptime routing-uptime;
}
always-wait-for-krt-drain;
} | [edit logical-systems name protocols bgp family name],
[edit logical-systems name protocols bgp group name family name],
[edit logical-systems name protocols bgp group name neighbor ip-address family name],
[edit logical-systems name routing-instances name protocols bgp family name],
[edit logical-systems name rout... | Configure this option to delay route updates for a specified family until the forwarding table is
synchronized. When a device starts up, BGP establishes peering sessions with its neighbors and receives
route updates. These route updates are then readvertised as more specific BGP routes or less specific
aggregates. Adve... | [
{
"name": "minimum-delay",
"desc": "(Optional) Specify a minimum delay, in seconds, in advertising the routes."
},
{
"name": "inbound-convergence",
"desc": ""
},
{
"name": "inbound-convergence",
"desc": "(Optional) Specify a minimum delay in route advertisement after the source peer ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F6. | [] |
delay-variation | delay-variation delay-variation-value; | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name calculation-weight] | Configure the calculation weight for delay variation. | [
{
"name": "delay-variation-value",
"desc": "Calculation weight for delay variation."
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
delegate-probes | delegate-probes; | [edit services rpm probe owner] | Generate real-time performance monitoring (RPM) probes on an MS-MPC or MS-MIC card, which
increases the number of RPM probes that can run at the same time.
To use the delegate-probes statement, you must first configure the destination-interface statement at the
[edit services rpm probe owner test test-name] hierarchy l... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
delegate-processing (VRRP) | delegate-processing {
ae-irb;
} | [edit protocols vrrp] | Configure the distributed periodic packet management process (ppmd) to send Virtual Router
Redundancy Protocol (VRRP) advertisements .
Using a hash logic based on iflIndex, the vrrp group ID, and the IP version, select one of the Flexible OIC
Concentrators (FPCs) for distribution. The selected FPC is called the anchor ... | [
{
"name": "ae-irb",
"desc": "Enable distributed ppmd for VRRP over aggregated Ethernet and integrated routing and bridging (IRB) interfaces. Using the ae-irb option is only for MPC line cards. ae-irb is not supported on small MX Series routing devices with built-in MPCs such as the MX104 and below. Using th... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
ae-irb option introduced in Junos OS Release 15.1. | [
"Enabling the Distributed Periodic Packet Management Process for VRRP"
] |
delegate-server-processing | delegate-server-processing; | [edit protocols oam ethernet connectivity-fault-management performance-monitoring] | For Ethernet interfaces on MX Series routers , enable server-side processing for two-way delay
measurement and loss measurement.
By default, the processing is done by the Routing Engine. | [] | trace—To view this statement in the configuration.
trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Ethernet Frame Delay Measurements Overview"
] |
delegated-pool (DHCP Local Server) | delegated-pool pool-name; | [edit system services dhcp-local-server dhcpv6 overrides],
[edit system services dhcp-local-server dhcpv6 group group-name overrides],
[edit system services dhcp-local-server dhcpv6 group group-name interface interface-name
overrides],
[edit logical-systems logical-system-name routing-instances routing-instance-name s... | Specify the address pool that assigns the IA_PD address. A pool specified by RADIUS VSA 26-161 takes
precedence over the pool specified by this delegated-pool statement. | [
{
"name": "pool-name",
"desc": "Name of the address-assignment pool."
}
] | 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. | [
"Specifying the Delegated Address-Assignment Pool to Be Used for DHCPv6 Prefix Delegation",
"Overriding the Default DHCP Local Server Configuration Settings"
] |
delegation-cleanup-timeout | delegation-cleanup-timeout seconds; | [edit protocols pcep pce pce-id] | Specify the amount of time (in seconds) that a Path Computation Client (PCC) must wait before
returning control of all LSPs to the routing protocol process after a PCEP session with the main active
stateful Path Computation Element (PCE) is disconnected.
NOTE: In compliance with draft-ietf-pce-stateful-pce-09, revoking... | [
{
"name": "seconds",
"desc": "Time (in seconds) that a PCC must wait before returning control of all LSPs to the routing protocol process after a PCEP session with the main active stateful PCE is disconnected. A value of 0 indicates immediate delegation cleanup. Range: 0 through 2,147,483,647 seconds Prior... | 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. | [] |
delegation-priority | delegation-priority priority-number; | [edit protocols pcep pce pce-id] | Specify the priority number of the active stateful Path Computation Element (PCE). This value is used by
the Path Computation Client (PCC) to elect a PCE to delegate LSPs. No two PCEs can have the same
delegation-priority value. The PCC elects the PCE with a lower priority as the main active stateful PCE
to delegate LS... | [
{
"name": "priority-number",
"desc": "Priority number of the active stateful PCE. Range: 1 through 65535 Default: 0 (no priority is set)"
}
] | 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. | [] |
DELETE (DTCP) | DELETE DTCP/0.7
Csource-ID: user-name
CRITERIA-ID: criteria-id
Cdest-ID: variable
Flags: flag
Seq: sequence-number
Authentication-Info:ssh-authentication-string | Remove traffic mirroring for a subscriber. Mirroring of the existing subscriber is stopped. This DTCP
message is supported for both FlowTapLite and radius-flow-tap services.
NOTE: Consult the documentation for your mediation device to learn how to configure
DTCP messages on the device. | [
{
"name": "CRITERIA-ID: criteria-id",
"desc": "ID that DTCP assigns for the mirrored session when you create a DTCP ADD message. Use this ID in your DELETE messages to remove the intercept for a specific subscriber. To view the ID, use the DTCP LIST message. The CRITERIA-ID and the Cdest-ID are mutually exc... | Not applicable.
Sample Output
The following sample shows how to remove mirroring for a specific subscriber by using the CRITERIA-
ID.
DELETE DTCP
DELETE DTCP/0.7
Csource-ID: dtcp1
CRITERIA-ID: 2
Flags: STATIC
Seq: 10
Authentication-Info: 7e84ae871b12f2da023b038774115bb8d955f17e
DTCP/0.7 200 OK
SEQ: 10
CRITERIA-COUNT: 1... | [
"DTCP Messages Used for Subscriber Secure Policy",
"DTCP-Initiated Subscriber Secure Policy Overview"
] | ||
delete chassis fpc | delete chassis fpc fpc_id no-vlan-tagging | (PTX Series routers) Disable no VLAN tagging for a specific FPC. | [
{
"name": "fpc fpc_id",
"desc": "For PTX devices, fpc_id value is 0 to 15. Usage Use set chassis fpc <fpc_id> no-vlan-tagging command to re-enable no-vlan-tagging on a specific FPC."
}
] | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
delete chassis fpc (PTX)
user@host> delete chassis fpc 1 no-vlan-tagging | Command introduced in Junos OS Release 21.3R1. | [] | |
delete services jinsightd subscribe health-monitor | delete services jinsightd subscribe health-monitor | Disables the J-Insight health monitor. Starting in Junos OS Release 18.2R1, J-Insight provides health
monitoring capabilities for FPC FRUs on the MX series routers. The health monitor is disabled by
default. | [] | system | Command introduced in Junos OS Release 18.2R1. | [
"J-Insight Device Monitor Basic Configuration"
] | |
delete | delete <statement-path> <identifier> | Delete a statement or identifier. All subordinate statements and identifiers contained within the
specified statement path are deleted with it.
Deleting a statement or an identifier effectively “unconfigures” or disables the functionality associated
with that statement or identifier.
If you do not specify statement-pat... | [
{
"name": "statement-path",
"desc": "(Optional) Path to an existing statement or identifier. Include this if the statement or identifier to be deleted is not at the current hierarchy level."
},
{
"name": "identifier",
"desc": "(Optional) Name of the statement or identifier to delete."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy.
Sample Output
delete (Junos OS Evolved)
[edit]
user@host# delete
This will delete the entire configuration
Delete everything under this level? [yes,no] (no) yes
If you ... | Command introduced before Junos OS Release 7.4. | [
"Deleting a Statement from a Device Configuration"
] | |
delete-after-commit (JNU Satellites) | delete-after-commit; | [edit system autoinstallation] | Specify that during the subsequent commit operation of configuration settings (after the autoinstallation
process successfully retrieves, installs, and commits the configuration), the autoinstallation configuration
parameters be removed from the router. Removal of the autoinstallation parameters and statements
from the... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Autoinstallation of Satellite Devices in a Junos Node Unifier Group",
"Autoinstallation Process on Satellite Devices in a Junos Node Unifier Group",
"Configuring Autoinstallation of Configuration Files",
"Configuring Autoinstallation of Configuration Files"
] |
delete-binding-on-renegotiation (DHCP Local Server and Relay Agent) | delete-binding-on-renegotiation; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit logical-systems logical-system-name ...],
[edit logical-systems logical-sy... | Configure DHCP to override the default behavior when the local server or relay agent receives a
DHCPv4 Discover or DHCPv6 Solicit message while in a bound state. In this case, DHCP drops the
message and it is not processed. On a DHCP relay agent, the agent sends a Release message to the local
server. DHCP cleans up the... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"DHCP Behavior When Renegotiating While in Bound State"
] |
delete-req | delete-req {
alarm-threshold (Security GPRS) {
forward number;
reverse number;
}
drop-threshold (Security GPRS) {
forward number;
reverse number;
}
} | [edit security gtp profile profile-name path-rate-limit message-type] | Configure the delete-req parameter to limit the number of packets per second for the GPRS tunneling
protocol (GTP) delete request.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name path-rate-limit
message-type] hierarchy level is replaced by [edit security gtp profile profile-name p... | [
{
"name": "alarm-threshold",
"desc": "To set alarm threshold for path rate limiting."
},
{
"name": "drop-threshold",
"desc": "To set drop threshold for path rate limiting."
}
] | 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. | [
"Understanding Path Rate Limiting for GTP Control Messages",
"Example: Limiting the Message Rate and Path Rate for GTP Control Messages"
] |
delimiter (Access Profile) | delimiter delimiter; | [edit access profile profile-name session-options strip-user-name] | Specify up to eight characters that the router uses to determine which part of the subscriber login string
to discard—leaving the remainder for use as a modified username—when subscriber username stripping
is configured in a subscriber access profile. The characters to the right of the delimiter are discarded
along wit... | [
{
"name": "delimiter",
"desc": "Character that specifies the boundary between the part of the original username that is kept and the part that is discarded."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Understanding Session Options for Subscriber Access",
"Configuring Username Modification for Subscriber Sessions",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
delimiter (DHCP Local Server) | delimiter delimiter-character; | [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 character used as the delimiter between the concatenated components of the username. | [
{
"name": "delimiter-character",
"desc": "Character that separates components that make up the concatenated username. You"
}
] | 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"
] |
delimiter (DHCP Relay Agent) | delimiter delimiter-character; | [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 character used as the delimiter between the concatenated components of the username.
Use the statement at the [edit ... dhcpv6] hierarchy levels to configure DHCPv6 support. | [
{
"name": "delimiter-character",
"desc": "Character that separates components that make up the concatenated username. You"
}
] | 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"
] |
delimiter (Domain Map) | delimiter [delimiter-character]; | [edit access domain] | Specify the characters that the router uses to separate usernames from domain names.
Default
The @ character. | [
{
"name": "delimiter-character",
"desc": "One or more characters used as delimiters. You can specify a maximum of eight"
}
] | 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. | [
"Specifying Domain and Realm Name Delimiters",
"Configuring Domain and Realm Name Usage for Domain Maps"
] |
delimiter (Subscriber Interfaces) | delimiter delimiter-character; | [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 character used as the delimiter between the concatenated components of the username.
You cannot use the semicolon (;) as a delimiter. | [] | 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"
] |
demand-circuit (Protocols RIP) | demand-circuit; | [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... | Configure a neighboring interface to act as a RIP demand circuit. To complete the demand circuit, you
must configure both ends of the pair as demand circuits. When configured, the device sends RIP
information only when changes occur in the routing database.
Default
Disabled. You must explicitly configure two neighborin... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Release 11.1 of Junos OS. | [
"Example: Configuring RIP Demand Circuits",
"RIP Demand Circuits Overview"
] |
demux (Interfaces) | demux {
inet {
address source;
auto-configure {
address-ranges {
authentication {
password password-string;
username-include {
auth-server-realm realm-string;
delimiter delimiter-chara... | [edit interfaces interface-name unit unit-number] | Configure demultiplexing (demux) interface options. The remaining statement is explained separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview",
"Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles"
] |
demux0 (Dynamic Interface) | demux0 {
unit logical-unit-number {
demux-options {
underlying-interface interface-name
}
family family {
access-concentrator name;
address address;
demux-source {
source-prefix;
}
direct-connect;
... | [edit dynamic-profiles profile-name interfaces] | Configure the logical demultiplexing (demux) interface in a dynamic profile.
Logical IP demux interfaces do not support IPv4 and IPv6 dual stack.
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. | [
"Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles",
"Demultiplexing Interface Overview"
] |
demux0 (Static Interface) | demux0 {
unit logical-unit-number {
demux-options {
underlying-interface interface-name
}
family family {
access-concentrator name;
{
destination-prefix;
}
direct-connect;
duplicate-protection;
... | [edit interfaces],
[edit logical-systems logical-system-name interfaces] | Configure the logical demultiplexing (demux) interface.
Logical IP demux interfaces do not support IPv4 and IPv6 dual stack.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface"
] |
demux-destination (Demux Interface) | demux-destination {
destination-prefix;
} | [edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
interface-name unit logical-unit-number fam... | Configure one or more logical demultiplexing (demux) destination prefixes. The prefixes are matched
against the destination address of packets that the underlying interface receives. When a match occurs,
the packet is processed as if it was received on the demux interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for aggregated Ethernet added in Junos OS Release 9.4. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface"
] |
demux-destination (Underlying Interface) | demux-destination family; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
interface-name unit logical-unit-number] | Configure the logical demultiplexing (demux) destination family type on the IP demux underlying
interface.
NOTE: The IP demux interface feature currently supports only Fast Ethernet, Gigabit
Ethernet, 10-Gigabit Ethernet, or aggregated Ethernet underlying interfaces. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for aggregated Ethernet added in Junos OS Release 9.4. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface"
] |
demux-options (All Demux Interfaces) | demux-options {
use-underlying-interface-mac {
} | [edit system] | Configure demultiplexing (demux) interface options for all demux interfaces.
The remaining statement is 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 17.3R1. | [
"Configuring the IPv6 Link-Local Address for Dynamic Demux Interfaces over Static Demux VLAN",
"Interfaces"
] |
demux-options (Dynamic Interface) | demux–options {
underlying-interface interface-name
} | [edit dynamic-profiles profile-name interfaces demux0 interface-name unit logical-unit-number] | Configure logical demultiplexing (demux) interface options in a dynamic 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. | [
"Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles",
"Demultiplexing Interface Overview"
] |
demux-options (Static Interface) | demux–options {
underlying-interface interface-name
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure logical demultiplexing (demux) interface options.
The remaining statement is explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface"
] |
demux-source (Demux Interface) | demux-source {
source-prefix;
} | [edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
interface-name unit logical-unit-number fam... | Configure one or more logical demultiplexing (demux) source prefixes. The prefixes are matched against
the source address of packets that the underlying interface receives. When a match occurs, the packet is
processed as if it was received on the demux interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for aggregated Ethernet added in Junos OS Release 9.4. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface"
] |
demux-source (Dynamic IP Demux Interface) | demux-source {
source-address;
} | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family] | Configure a logical demultiplexing (demux) source address for a subscriber in a dynamic profile. | [
{
"name": "source-address",
"desc": "Either the specific source address you want to assign to the subscriber interface or the"
}
] | 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. | [
"Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles",
"Demultiplexing Interface Overview"
] |
demux-source (Dynamic Underlying Interface) | demux-source family; | [edit dynamic-profiles interfaces interface-name unit logical-unit-number] | Configure the logical demultiplexing (demux) source family type on the IP demux underlying interface
within a dynamic profile.
NOTE: The IP demux interface feature currently supports only Fast Ethernet, Gigabit
Ethernet, 10-Gigabit Ethernet, or aggregated Ethernet underlying interfaces. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "inet",
"desc": "Internet Protocol version 4 suite"
},
{
"name": "inet6",
"desc": "Internet Protocol version 6 suite"
}
] | 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. | [] |
demux-source (Underlying Interface) | demux-source family; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
interface-name unit logical-unit-number] | Configure the logical demultiplexing (demux) source family type on the IP demux underlying interface.
NOTE: The IP demux interface feature currently supports only Fast Ethernet, Gigabit
Ethernet, 10-Gigabit Ethernet, or aggregated Ethernet underlying interfaces. | [
{
"name": "family",
"desc": "Protocol family:"
},
{
"name": "inet",
"desc": "Internet Protocol version 4 suite"
},
{
"name": "inet6",
"desc": "Internet Protocol version 6 suite"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for aggregated Ethernet added in Junos OS Release 9.4. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface"
] |
dense-groups | dense-groups {
addresses;
} | [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] | Configure which groups are operating in dense mode. | [
{
"name": "addresses",
"desc": "Address of groups operating in dense mode."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring PIM Sparse-Dense Mode Properties"
] |
deny (Security Policies) | deny; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then] | Block the service at the firewall. The device drops the packets. | [] | 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. | [
"Security Policies Overview"
] |
deny (Security SIP) | deny {
all {
timeout value-in-seconds;
}
destination-ip address;
timeout value-in-seconds;
} | [edit logical-systems name security alg sip application-screen protect],
[edit logical-systems name tenants name security alg sip application-screen protect],
[edit security alg sip application-screen protect],
[edit services alg sip application-screen protect],
[edit tenants name security alg sip application-screen pr... | Protect servers against INVITE attacks. | [
{
"name": "all",
"desc": "Configure the Session Initiation Protocol (SIP) application screen to protect servers at all"
},
{
"name": "destination-ip address",
"desc": "Configure the SIP application screen to protect the server at this destination IP"
},
{
"name": "timeout value-in-second... | 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. | [] |
depth-threshold | depth-threshold {
high number;
low number;
} | [edit services analytics interfaces]
[edit services analytics resource-profiles] | If network analytics queue statistics monitoring is enabled, specify the high and low values (in bytes) of
the queue depth (buffer) threshold. If you configure a depth threshold, you cannot configure the latency
threshold. You can configure the depth threshold for one interface or all interfaces. Specify the high and
l... | [
{
"name": "high number",
"desc": "Specify the maximum value for the depth threshold. Range: 1 to 1,250,000,000 bytes Default:"
},
{
"name": "Junos OS Release 13.2X51-D10 or later",
"desc": "0 bytes"
},
{
"name": "Junos OS Release 13.2X50-D15",
"desc": "14,680,064 bytes (14 MB)"
}... | 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.
Statement in the [edit services analytics resource-profiles] hierarchy level introduced in Junos OS Release
13.2X51-D15. | [
"Network Analytics Overview"
] |
description (Abstracted Fabric) | description description; | [edit chassis network-slices guest-network-functions gnf af-name] | Provide a description string for the specified abstracted fabric (af) interface. | [
{
"name": "description",
"desc": "A description string for the specified abstracted fabric (af) interface."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"Setting Up Junos Node Slicing"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.