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 |
|---|---|---|---|---|---|---|---|
description (Application Identification) | description description | [edit services application-identification application application-name] | Provide a description of the application. | [
{
"name": "description",
"desc": "Textual description of the application. Range: 1 through 255 characters"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
description (Applications) | description text; | [edit applications application application-name],
[edit applications application-set application-set-name] | Specify descriptive text for an application or an application set.
NOTE: The descriptive text should not include characters “<”, “>”, “&”, or “\n”. | [
{
"name": "text",
"desc": "Descriptive text about an application or an application set."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Security Policy Application Sets Overview"
] |
description (Chassis Redundancy) | description description; | [edit chassis redundancy feb redundancy-group group-name] | Provide a description of the FEB redundancy group. | [
{
"name": "description",
"desc": "Provide a description for the FEB redundancy group."
}
] | 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 FEB Redundancy on the M120 Router"
] |
description (Fibre Channel Fabrics) | description description | [edit fc-fabrics fabric-name] | Text string that describes the Fibre Channel fabric. The text string has no effect on the operation of the
fabric. | [
{
"name": "description",
"desc": "Text that describes the fabric. Text can include letters, numbers, and hyphens (-) and can be up to 255 characters in length. If the text includes spaces, enclose the entire text string in quotation marks."
}
] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | [] | |
description (Forwarding Options) | description text-description; | [edit forwarding-options helpers bootp],
[edit forwarding-options helpers bootp interface (interface-name | interface-group)],
[edit forwarding-options helpers domain],
[edit forwarding-options helpers domain interface interface-name],
[edit forwarding-options helpers port port-number],
[edit forwarding-options helpers... | Describe a BOOTP, DHCP, Domain Name System (DNS), Trivial File Transfer Protocol (TFTP), or port-
based LAN broadcast packet forwarding service, or an interface that is configured for the service. | [] | 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",
"Configuring Port-based LAN Broadcast Packet Forwarding",
"Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents"
] |
description (GNF) | description description; | [edit chassis network-slices guest-network-functions gnf] | Provide a description string for the specified guest network function (GNF). | [
{
"name": "description",
"desc": "A description string for the specified guest network function (GNF)."
}
] | 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.2. | [] |
description (IKE policy) | description description; | [edit security ike policy ike-peer-address],
[edit security ike proposal ike-proposal-name],
[edit security ipsec policy ipsec-policy-name],
[edit security ipsec proposal ipsec-proposal-name],
[edit security ipsec security-association sa-name] | Specify a text description for an IKE proposal or policy, or an IPsec proposal, policy, or SA. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | [
"Configuring Security Associations for IPsec on an ES PIC",
"Configuring the Description for an IKE Proposal",
"Configuring an IKE Policy for Preshared Keys",
"Configuring an IPsec Proposal for an ES PIC",
"Configuring the IPsec Policy for an ES PIC"
] | |
description (Interfaces) | description text; | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Provide a textual description of the interface or the logical unit. Any descriptive text you include is
displayed in the output of the show interfaces commands, and is also exposed in the ifAlias Management
Information Base (MIB) object. It has no effect on the operation of the interface on the router or switch.
The te... | [
{
"name": "text",
"desc": "Text to describe the interface. If the text includes spaces, enclose the entire text in quotation"
}
] | 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.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"Configuring Interface Description",
"Adding a Logical Unit Description to the Configuration",
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for OCX Series Switches",
"Configuring Gigabit Ethernet Interfaces for EX Series Switches with ELS... |
description (Junos Fusion Satellite Device Cluster) | description description; | [edit chassis satellite-management cluster cluster-name fpc slot-id ] | Configure a description for the satellite device in the satellite device cluster.
The description is optional and used for information purposes only.
Default
Satellite devices in satellite device clusters do not have descriptions, by default. | [
{
"name": "description",
"desc": "A text description of the satellite device in the satellite device cluster."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Configuring or Expanding a Junos Fusion Enterprise"
] |
description (Junos Fusion) | description description; | [edit chassis satellite-management fpc slot-id] | Configure a description for the satellite device.
The description is optional and used for information purposes only.
Default
Satellite devices do not have descriptions, by default. | [
{
"name": "description",
"desc": "A text description of the satellite device."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
description (Op Scripts) | description description; | [edit system scripts op file filename]
[edit system scripts op file filename arguments argument-name] | Provide help text to describe an op script or its command-line arguments. The help text is included in
the context-sensitive help in the command-line interface (CLI). | [
{
"name": "description",
"desc": "At the script hierarchy level, specify the purpose of the script. At the arguments hierarchy level, provide a description for the command-line argument."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Help Text for Op Scripts",
"Declaring and Using Command-Line Arguments in Op Scripts"
] |
description (Protocols BGP) | description text-description; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Provide a description of the global, group, or neighbor configuration. If the text includes one or more
spaces, enclose it in quotation marks (“ “ ). The test is displayed in the output of the show command and
has no effect on the configuration. | [
{
"name": "text-description",
"desc": "Text description of the configuration. It is limited to 255 characters."
}
] | 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. | [
"BGP User Guide"
] |
description (Protocols Layer 2 Circuit Neighbor) | description text; | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit protocols l2circuit neighbor address interface interface-name] | Provide a text description for the Layer 2 circuit. If the text includes one or more spaces, enclose the
entire text string in quotation marks (" "). | [] | 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 Routing Instances on PE Routers in VPNs"
] |
description (Protocols Layer 2 VPN) | description text; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn site site-name interface interface-name],
[edit routing-instances routing-instance-name protocols l2vpn site site-name interface interface-
name] | Describe the VPN or virtual private LAN service (VPLS) routing instance. | [
{
"name": "text",
"desc": "Provide a text description. If the text includes one or more spaces, enclose it in quotation marks (\""
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Site",
"Configuring an MPLS-Based Layer 2 VPN (CLI Procedure)"
] |
description (Protocols MPLS) | description text; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
bypass],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit logical-systems log... | Provides a textual description of the LSP. Enclose any descriptive text that includes spaces in quotation
marks (" "). Any descriptive text you include is displayed in the output of the show mpls lsp detail
command and has no effect on the operation of the LSP. | [
{
"name": "text",
"desc": "Provide a textual description of the LSP. The description text can be no more than 80 characters in"
}
] | 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 a Text Description for LSPs"
] |
description (RMON) | description description; | [edit snmp rmon alarm index],
[edit snmp rmon event index] | Text description of alarm or event. | [
{
"name": "description",
"desc": "Text description of an alarm or event entry. If the description includes spaces, enclose it in"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Description",
"Configuring an RMON Event Entry and Its Attributes"
] |
description (Routing Instances) | description text; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Provide a text description for the routing instance. If the text includes one or more spaces, enclose it in
quotation marks (" "). Any descriptive text you include is displayed in the output of the show route instance
detail command and has no effect on the operation of the routing instance. | [] | 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. | [] |
description (Security Address Book) | description text; | [edit security address-book book-name] | Specify descriptive text for an address book.
NOTE: The descriptive text should not include characters “<”, “>”, “&”, or “\n”. | [
{
"name": "text",
"desc": "Descriptive text about an address book."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding Address Books",
"Understanding Address Sets"
] |
description (Security IDP Policy) | description text; | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name]
[edit security idp idp-policy policy-name rulebase-ips rule rule-name] | Specify descriptive text for an exempt rule, or IPS rule. | [
{
"name": "text",
"desc": "Descriptive text about an exempt rule, or IPS rule."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [] |
description (Security NAT Pool) | description text; | [edit security nat destination pool pool-name]
[edit security nat source pool pool-name] | Specify descriptive text for a source or destination NAT pool.
NOTE: The descriptive text should not include characters, such as “<”, “>”, “&”, or “\n”. | [
{
"name": "text",
"desc": "Descriptive text about a source or destination NAT pool."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
description (Security NAT Rule Set) | description text; | [edit security nat destination rule-set rule-set-name]
[edit security nat source rule-set rule-set-name]
[edit security nat static rule-set rule-set-name] | Specify descriptive text for a source, destination, or static NAT rule set.
NOTE: The descriptive text should not include characters, such as “<”, “>”, “&”, or “\n”. | [
{
"name": "text",
"desc": "Descriptive text about a source, destination, or static NAT rule set."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
description (Security NAT Rule) | description text; | [edit security nat destination rule-set rule-set-name rule rule-name]
[edit security nat source rule-set rule-set-name rule rule-name]
[edit security nat static rule-set rule-set-name rule rule-name] | Specify descriptive text for a source, destination, or static NAT rule.
NOTE: The descriptive text should not include characters, such as “<”, “>”, “&”, or “\n”. | [
{
"name": "text",
"desc": "Descriptive text about a source, destination, or static NAT rule."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
description (Security Policies Next Gen Services) | description description; | [edit security ike policy policy-name],
[edit security ike proposal proposal-name],
[edit security ipsec policy policy-name],
[edit security ipsec proposal proposal-name] | Enter descriptive text for an IKE policy, an IPsec policy, an IKE proposal, or an IPsec proposal. | [
{
"name": "description",
"desc": "Descriptive text."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
description (Security Screen) | description text; | [edit security screen ids-option screen-name] | Specify descriptive text for a screen.
NOTE: The descriptive text should not include characters, such as “<”, “>”, “&”, or “\n”. | [
{
"name": "text",
"desc": "Descriptive text about a screen."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
description (Security Zone) | description text; | [edit security zones functional-zone management]
[edit security zones security-zone zone-name] | Specify descriptive text for a security zone.
NOTE: The descriptive text should not include characters as “<”, “>”, “&”, or “\n”. | [
{
"name": "text",
"desc": "Descriptive text about a security zone."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
description (Services IPsec VPN) | description description; | [edit services ipsec-vpn ike policy policy-name],
[edit services ipsec-vpn ike proposal proposal-name],
[edit services ipsec-vpn ipsec policy policy-name],
[edit services ipsec-vpn ipsec proposal proposal-name] | Specify the text description for an IKE or IPsec policy or proposal. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Proposals",
"Configuring IPsec Policies"
] |
description (SNMP) | description description; | [edit snmp] | Define the value of the MIB II sysDescription object, which is the description of the system being
managed. | [
{
"name": "description",
"desc": "System description. If the name includes spaces, enclose it in quotation marks (\" \")."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the System Description on a Device Running Junos OS"
] |
description (VLAN) | description text-description; | [edit vlans vlan-name] | Provide a textual description for the VLAN. The text has no effect on the operation of the VLAN or
switch. | [
{
"name": "text-description",
"desc": "Text to describe the interface. It can contain letters, numbers, and hyphens (-) and can"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Option text-description enhanced from supporting up to 128 characters to supporting up to 256
characters in Junos OS Release 10.2 for EX Series switches. | [
"Understanding Bridging and VLANs on Switches",
"Understanding Bridging and VLANs on Switches",
"Example: Setting Up Basic Bridging and a VLAN on Switches",
"Example: Setting Up Basic Bridging and a VLAN for an EX Series Switch",
"Example: Setting Up Basic Bridging and a VLAN for an EX Series Switch with EL... |
deselect-on-bandwidth-failure | deselect-on-bandwidth-failure {
tear-lsp;
} | [edit protocols mpls],
[edit protocols mpls label-switched-path path-name] | Deselect an active path if it does not meet the auto-bandwidth criteria required for path selection.
Traffic flows on LSP are periodically measured which are configured with auto-bandwidth. The LSP path
bandwidth is adjusted by increasing or decreasing the bandwidth based on the traffic flow. For example,
let's say the... | [
{
"name": "tear-lsp",
"desc": "Bring down an active path if none of the paths are able to reserve the required bandwidth."
}
] | 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. | [] |
designated-forwarder-election-hold-time | designated-forwarder-election-hold-time seconds; | [edit protocols evpn],
[edit routing-instances protocols evpn] | Set the time that the device waits before electing a designated forwarder (DF).
Customer edge (CE) devices require a DF when they are multihomed to more than one provider edge
(PE) device. Without a designated forwarder, multihomed hosts would receive duplicate packets. The
connections between a multihomed CE device an... | [
{
"name": "seconds",
"desc": "Time in seconds that a multihomed CE device waits before electing a DF based on the EVPN Type 4 routes it receives. Range: 1 through 1800"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D15. | [
"EVPN Multihoming Overview"
] |
destination (Accounting) | destination {
radius {
server {
server-address {
accounting-port port-number;
accounting-retry number;
accounting-timeout seconds;
dynamic-request-port number;
max-outstanding-requests value;
port num... | [edit system accounting] | Configure the authentication server. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
radius statement added in Junos OS Release 7.4. | [
"Configuring RADIUS System Accounting",
"Configuring TACACS+ System Accounting"
] |
destination (Application Identification) | destination ip ip-address-prefix; | [edit services application-identification application application-name address-mapping] | Specify the destination IP address for address mapping-based application identification. | [
{
"name": "ip-address-prefix",
"desc": "IP address and prefix for matching."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
destination (Chassis) | destination destination; | [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-
provider syslog facility] | Configure where log messages go. By default, all messages go to the /var/log directory on the Routing
Engine. Enhancements to the existing infrastructure make debugging on the Multiservices PIC easier by
giving the user the option of redirecting log messages. When the syslog destination statement is
configured to redir... | [
{
"name": "destination",
"desc": "Choose one of the following options:"
},
{
"name": "routing-engine",
"desc": "Forward log messages to the Routing Engine."
},
{
"name": "pic-console",
"desc": "Forward log messages to the console of the PIC."
}
] | 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. | [] |
destination (Diameter Network Element) | destination realm realm-name <host hostname>; | [edit diameter network-element element-name forwarding route dne-route-name] | Associate the route with all hosts of the specified realm or with a specific host of the specified realm.
Together with the function and metric, defines a route reachable through a Diameter network element. | [
{
"name": "host hostname",
"desc": "(Optional) Name of the destination host associated with the route."
},
{
"name": "realm realm-name",
"desc": "Name of the destination realm associated with the route."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
destination (Event Policy) | destination destination-name {
retry-count count retry-interval seconds;
transfer-delay seconds;
} | [edit event-options policy policy-name then event-script filename],
[edit event-options policy policy-name then execute-commands] | Assign a location to which to upload command or script output for the specified event policy. | [
{
"name": "destination-name",
"desc": "Name of a destination defined in the destinations statement at the [edit event-options] hierarchy level."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5.
Support at the [edit event-options policy policy-name then event-script filename] hierarchy level introduced in
Junos OS Release 7.6. | [
"Configure an Event Policy to Execute Operational Mode Commands",
"Execute Event Scripts in an Event Policy"
] |
destination (Interfaces) | destination address; | [edit interfaces interface-name unit logical-unit-number tunnel],
[edit interfaces interface-name unit logical-unit-number family inet address address],
[edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family ... | For point-to-point interfaces only, specify the address of the interface at the remote end of the
connection.
For tunnel and encryption interfaces, specify the remote address of the tunnel. | [
{
"name": "address",
"desc": "Address of the remote side of the connection."
}
] | 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",
"Configuring Encryption Interfaces",
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Configuring Flow Monitoring",
"Configuring Unicast Tunnels"
] |
destination (IPCP) | destination address destination-profile profile-name; | [edit interfaces interface-name unit logical-unit-number family inet unnumbered-address
interface-name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet unnumbered-address interface-name] | For unnumbered interfaces with PPP encapsulation, specify the IP address of the remote interface. | [
{
"name": "address",
"desc": "IP address of the remote interface."
}
] | 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 IPCP Options for Interfaces with PPP Encapsulation",
"Junos OS Administration Library for Routing Devices"
] |
destination (L2TP) | destination {
address ip-address {
access-line-information <connection-speed-update>;
drain;
routing-instance routing-instance-name {
drain;
}
}
lockout-timeout seconds;
name destination-name {
drain;
}
} | [edit services l2tp] | Configure attributes for all L2TP destinations or a specified L2TP destination.
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 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks",
"L2TP LNS Inline Service Interfaces",
"L2TP Subscriber Access Lines and Connection Speeds"
] |
destination (LRF Profile) | destination {
address collector-address;
port collector-port-number;
} | [edit services lrf profile profile-name collector collector-name] | Specify the destination IP address and port number of the collector.
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 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
destination (Protocols OSPF) | destination prefix {
interface (interface-name |all) {
admin-group {
exclude [ group-name ];
include-all [ group-name ];
include-any [ group-name ];
preference [ group-name ];
}
bandwidth-greater-equal-primary;
dest-metric (highest... | [edit logical-systems logical-system-name routing-options backup-selection],
[edit logical-systems logical-system-name routing-instances instance-name routing-options backup-
selection],
[edit routing-instances instance-name routing-options backup-selection],
[edit routing-options backup-selection] | Define the backup selection policy for a particular destination prefix or for all the prefixes. | [
{
"name": "prefix",
"desc": "Destination prefix name and prefix length. You can specify 0/0 for the IPv4 least-specific prefix or 0::0/0 for the IPv6 least-specific prefix."
}
] | 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. | [] |
destination (Routing Instance) | destination routing-instance-name; | [edit interfaces interface-name unit logical-unit-number tunnel routing-instance] | Specify the destination routing instance that points to the routing table containing the tunnel
destination address.
Default
The default Internet routing table inet.0. | [
{
"name": "routing-instance-name",
"desc": "Name of the destination routing instance."
}
] | 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 Tunnel Interfaces for Routing Table Lookup"
] |
destination (saegw system) | destination {
peer-address address;
port port-number;
routing-instance instance-name;
source-address address;
} | [edit services mobile-edge gateways saegw system] | Configure the destination address of the IPsec peer or content of communication point of aggregation
(CC-PAG) peer on the user plane for lawful intercept data. The control plane provides the address of the
Mediation and Delivery Function (MDF), but it might not provide the address of the IPsec peer, which
you need to c... | [
{
"name": "peer-address address",
"desc": "Address of the IPsec peer."
},
{
"name": "port port-number",
"desc": "TCP/UDP port number of the IPsec peer."
},
{
"name": "routing-instance instance-name",
"desc": "Name of the routing instance."
},
{
"name": "source-address address... | system | Juniper Networks introduced this statement in Junos OS Release 22.2R1 | [
"Lawful Intercept on Junos Multi-Access User Plane"
] |
destination (Security Destination NAT) | destination {
pool pool-name {
address <ip-address> {
(port port-number | to ip-address);
}
description text;
routing-instance (routing-instance-name | default);
}
rule-set rule-set-name {
description text;
from {
interface [interface-n... | [edit security nat] | Configure destination NAT, which allows you to configure the following:
•
Translate destination IP address or addresses to a specific IP address.
•
Translate destination IP address or addresses and port number(s) to a specific IP address and one
port number.
•
Translate a range of destination IP addresses to another ra... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. The description option added in Junos OS Release 12.1.
Statement modified in Junos OS Release 12.1X45-D10. Statement modified in Junos OS Release
12.1X47-D10. | [] |
destination (Security IP Headers Attack) | destination {
match (equal | greater-than | less-than | not-equal);
value ip-address-or-hostname;
} | [edit security idp custom-attack attack-name attack-type signature protocol ipv4],
[edit security idp custom-attack attack-name attack-type signature protocol ipv6] | Specify the IP address of the attack target. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value ip-address-or-hostname",
"desc": "Match an IP address or a hostname."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
destination (Services) | destination {
ip address</prefix-length>;
port-range {
tcp [ ports-and-port-ranges ];
udp [ ports-and-port-ranges ];
}
} | [edit services application-identification rule rule-name address address-name] | Define destination properties for application-identification rule processing.
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.5. | [
"Configuring APPID Rules"
] |
destination (Tunnel Remote End) | destination destination-address; | [edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel] | For tunnel interfaces, specify the remote address of the tunnel. | [
{
"name": "destination-address",
"desc": "Address of the remote side of the connection."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Unicast Tunnels",
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Configuring Flow Monitoring"
] |
destination (Tunnels) | destination address; | [edit interfaces interface-name unit logical-unit-number family inet address address],
[edit interfaces interface-name unit logical-unit-number family inet unnumbered-address interface-
name],
[edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interfac... | For encrypted, PPP-encapsulated, and tunnel interfaces, specify the remote address of the connection. | [
{
"name": "address",
"desc": "Address of the remote side of the connection."
}
] | 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 the Interface Address",
"Configuring Generic Routing Encapsulation Tunneling",
"Junos OS Services Interfaces Library for Routing Devices"
] |
destination | destination {
address address;
} | [edit interfaces fti number unit logical-unit-number tunnel encapsulation (gre | ipip | udp )] | Interface address prefix of the destination where the tunnel terminates. Configuring this interface is
mandatory.
NOTE: Starting in Junos OS Evolved Release 20.3R1, for GRE tunnels, configure the
address for the tunnel encapsulation destination address.
When you do not configure "tunnel-termination" on page 31418, you ... | [
{
"name": "address",
"desc": "You can configure the destination address with an optional destination mask. The mask range is from 0 to 32 for IPv4, and 0 to 128 for IPv6 addresses. /32 is the default mask for IPv4, and /128 is the default mask for IPv6. NOTE: Starting in Junos OS Evolved Release 20.3R1, for... | interface | Statement introduced in Junos OS Evolved Release 20.2R1.
Statement introduced for IPIP tunnels in Junos OS Evolved Release 20.4R1.
Statement introduced for UDP tunnels in Junos OS Evolved Release 21.1R1. | [] |
destination-address (Firewall) | destination-address address; | [edit firewall family family-name filter filter-name term term-name from],
[edit firewall family family-name filter filter-name term term-name from ip-version ip-version] | IP destination address field, which is the address of the destination node for the packet. You cannot
specify the destination-address and address match conditions in the same term.
For IPv4, the destination-address field is 32 bits in length. The filter description syntax supports either a
mask value that can be nonco... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1R1. | [
"Firewall Filter Match Conditions Based on Address Fields",
"Firewall Filter Match Conditions for IPv4 Traffic",
"Firewall Filter Match Conditions for IPv6 Traffic",
"Firewall Filter Match Conditions for MPLS-Tagged IPv4 or IPv6 Traffic",
"Guidelines for Configuring Simple Filters"
] |
destination-address (Flow Monitoring Logs for NAT) | destination-address address; | [edit services jflow-log collector collector-name] | Specify the destination IP address or identifier of the host or external device that functions as the
collector for receiving the generated flow monitoring logs that are sent from the exporter. You can
configure an IPv4 address, or an identifier of the host system (the workstation either running the Jflow
utility or co... | [
{
"name": "address",
"desc": "Destination hostname, or IPv4 or IPv6 address of the collector."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
destination-address (HTTP Header Enrichment) | destination-address {
(any-ipv4 | any-ipv4 except);
(any-ipv6 | any-ipv6 except);
(any-unicast | any-unicast except);
(prefix | prefix except);
} | [edit services hcm tag-rule rule-name term term-number from] | Specify the prefix or address type that the HTTP request destination IP address must match. You can
specify multiple prefixes or address types by including the destination-address statement multiple times.
After this criterion and the other match criteria specified for the term are matched, the HTTP header
enrichment a... | [
{
"name": "any-ipv4",
"desc": "Match any IPv4 address."
},
{
"name": "any-ipv4",
"desc": ""
},
{
"name": "except",
"desc": "Exclude IPv4 addresses from addresses that are in a destination-address, destination-address-range, or destination-prefix-list statement configured at the [edit... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
destination-address (IDS MS-DPC) | destination-address (address | any-unicast) <except>; | [edit services ids rule rule-name term term-name from] | Specify the destination address for rule matching when using the MS-DPC. | [
{
"name": "address",
"desc": "Destination IPv4 or IPv6 address or prefix value."
},
{
"name": "any-unicast",
"desc": "Any unicast packet."
},
{
"name": "except",
"desc": "(Optional) Exempt the specified address, prefix, or unicast packets from rule matching."
}
] | 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.
address option enhanced to support IPv4 and IPv6 addresses in Junos OS Release 8.5. | [
"Configuring Match Conditions in IDS Rules"
] |
destination-address (IPsec-VPN) | destination-address address; | [edit services ipsec-vpn rule rule-name term term-name from] | Specify the destination address for rule matching. | [
{
"name": "address",
"desc": "Destination IP address."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Rules"
] |
destination-address (NAT Next Gen Services) | destination-address (address | any | any-ipv4 | any-ipv6); | [edit services nat destination rule-set rule-set rule rule-name match],
[edit services nat source rule-set rule-set rule rule-name match] | Specify the destination address that the packet must match for the NAT rule to take effect. | [
{
"name": "address",
"desc": "A specific address that must be matched."
},
{
"name": "any",
"desc": "Any unicast destination address results in a match."
},
{
"name": "any-ipv4",
"desc": "Any IPv4 destination address results in a match."
},
{
"name": "any-ipv6",
"desc": "... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
destination-address (PCP) | destination-address address <except>; | [edit services pcp rule rule-name term term-name from] | Specify the destination address that must be matched for the PCP rule. A PCP rule assigns the PCP
server that handles selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. | [
{
"name": "address",
"desc": "Destination address or prefix value."
},
{
"name": "minimum-value",
"desc": "Lower boundary for the address range."
},
{
"name": "except",
"desc": "(Optional) Prevent the specified address range from matching the PCP rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
destination-address (Security Destination NAT) | destination-address <ip-address>; | [edit security nat destination rule-set rule-set-name rule rule-name match] | Specify a destination address to match the rule. You can configure one address or a subnet.
NOTE:
•
If the destination address is IPv4 and the pool is an IPv6 prefix, the length of the IPv6
prefix must be 96.
•
If the destination address is an IPv6 prefix and the pool is an IPv6 prefix, their length
must be the same. | [
{
"name": "ip-address",
"desc": "Destination address or a subnet."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
destination-address (Security IDP Policy) | destination-address ([address-name] | any | any-ipv4 | any-ipv6); | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match]
[edit security idp idp-policy policy-name rulebase-ips rule rule-name match] | Specify a destination IP address or IP address set object to be used as the match destination address
object. The default value is any. | [
{
"name": "address-name",
"desc": "IP address or IP address set object."
},
{
"name": "any",
"desc": "Specify any IPv4 or IPv6 address."
},
{
"name": "any-ipv4",
"desc": "Specify any IPv4 address."
},
{
"name": "any-ipv6",
"desc": "Specify any IPv6 address."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
destination-address (Security Policies Flag) | destination-address {
drop-translated;
drop-untranslated;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit] | Specify whether the traffic permitted by the security policy is limited to packets where the destination
IP address has been translated by means of a destination NAT rule or to packets where the destination
IP address has not been translated.
On Juniper Networks security devices, destination NAT rules are processed bef... | [
{
"name": "drop-translated",
"desc": "Drop packets with translated destination IP addresses. Traffic permitted by the"
},
{
"name": "drop-untranslated",
"desc": "Drop packets without translated destination IP addresses. Traffic permitted by the"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Security Policies Overview"
] |
destination-address (Security Policies) | destination-address {
[address];
any;
any-ipv4;
any-ipv6;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name match]
[edit security policies global policy policy-name match] | Define the matching criteria. You can specify one or more IP addresses, address sets, or wildcard
addresses. You can specify wildcards any, any-ipv4, or any-ipv6. | [
{
"name": "address",
"desc": "IP address (any, any-ipv4, any-ipv6), IP address set, or address book entry, or wildcard address"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. Support. | [
"Security Policies Overview"
] |
destination-address (Security Source NAT) | destination-address <ip-address>; | [edit security nat source rule-set rule-set-name rule rule-name match] | Specify a destination address to match the rule. You can configure multiple addresses or subnets. | [
{
"name": "ip-address",
"desc": "Destination address or a subnet."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
destination-address (Security Static NAT) | destination-address <ip-address>; | [edit security nat static rule-set rule-set-name rule rule-name match] | Specify a destination address to match the rule. You can configure one address or a subnet. | [
{
"name": "ip-address",
"desc": "Destination address or a subnet."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
destination-address (Services CoS) | destination-address (address | any-unicast) <except>; | [edit services cos rule rule-name term term-name from] | Specify the destination address for rule matching. | [
{
"name": "address",
"desc": "Destination IPv4 or IPv6 address or prefix 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.1.
address option enhanced to support IPv4 and IPv6 addresses in Junos OS Release 8.5. | [
"Configuring CoS Rules on Services PICs",
"Configuring Match Conditions In CoS Rules"
] |
destination-address (Services NAT) | destination-address (address | any-unicast) <except>; | [edit services nat rule rule-name term term-name from] | Specify the destination address for rule matching. | [
{
"name": "address",
"desc": "Destination IPv4 or IPv6 address or prefix value."
},
{
"name": "any-unicast",
"desc": "Any unicast packet."
},
{
"name": "except",
"desc": "(Optional) Prevent the specified address, prefix, or unicast packets from being translated."
}
] | 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.
any-unicast and except options introduced in Junos OS Release 7.6.
address option enhanced to support IPv6 and addresses in Junos OS Release 8.5. | [
"Network Address Translation Rules Overview"
] |
destination-address (Services Stateful Firewall) | destination-address (address | any-ipv4 | any-ipv6 | any-unicast) <except>; | [edit services stateful-firewall rule rule-name term term-name from] | Specify the destination address for rule matching. | [
{
"name": "address",
"desc": "Destination IPv4 or IPv6 address or prefix value. Using a value of 0::0/0 with IPv6 is not allowed"
},
{
"name": "any-ipv4",
"desc": "Any IPv4 packet."
},
{
"name": "any-ipv6",
"desc": "Any IPv6 packet."
},
{
"name": "any-unicast",
"desc": "M... | 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.
any-unicast and except options introduced in Junos OS Release 7.6.
address option enhanced to support IPv4 and IPv6 addresses in Junos OS Release 8.5. | [
"Configuring Match Conditions in Stateful Firewall Rules"
] |
destination-address (Subscriber Secure Policy) | destination-address address; | [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 destination IP address or prefix value for radius-flow-tap policy rule mapping. | [
{
"name": "address",
"desc": "IPv4 or IPv6 address 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"
] |
destination-address | destination-address address; | [edit services aacl rule rule-name term term-name from] | Specify the destination address for rule matching. | [
{
"name": "address",
"desc": "Destination IPv4 or IPv6 address or prefix value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
IPv6 support introduced in Junos OS Release 12.2. | [
"Configuring Match Conditions in AACL Rules"
] |
destination-address-excluded | destination-address-excluded; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name match] | Exclude the destination address(es) from the policy.
NOTE: IPv6 does not support address-excluded in security policies match. | [] | 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. | [
"Security Policies Overview"
] |
destination-address-name (NAT Next Gen Services) | destination-address-name address-name; | [edit services nat destination rule-set rule-set rule rule-name match],
[edit services nat source rule-set rule-set rule rule-name match] | Specify the name of the range of destination addresses that the packet must match for the NAT rule to
take effect. The range of addresses is configured with the address statement at the [edit services address-
book global] hierarchy level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
destination-address-name (Security Destination NAT) | destination-address-name <address-name>; | [edit security nat destination rule-set rule-set-name rule rule-name match] | Specify a destination address name to match the rule. You can configure multiple address names. | [
{
"name": "address-name",
"desc": "Destination address name."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
destination-address-name (Security Source NAT) | destination-address-name <address-name>; | [edit security nat source rule-set rule-set-name rule rule-name match] | Specify a destination address name to match the rule. You can configure multiple address names. | [
{
"name": "address-name",
"desc": "Destination address name."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
destination-address-name (Security Static NAT) | destination-address-name <address-name>; | [edit security nat static rule-set rule-set-name rule rule-name match] | Specify a destination address name to match the rule. | [
{
"name": "destination-address-name",
"desc": "Name of the destination address."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
destination-address-range (HTTP Header Enrichment) | destination-address-range {
high address low address <except>;
} | [edit services hcm tag-rule rule-name term term-number from] | Specify an IP address range that the HTTP request destination IP address must match. You can specify
multiple address ranges by including the destination-address-range statement multiple times.
After this criterion and the other match criteria specified for the term are matched, the HTTP header
enrichment actions speci... | [
{
"name": "except",
"desc": "(Optional) Exclude addresses in the specified address range from addresses that are in a destination-address, destination-address-range, or destination-prefix-list statement configured at the [edit services hcm tag-rule rule-name term term-number from] hierarchy level. You canno... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
destination-address-range (IDS MS-DPC)) | destination-address-range low minimum-value high maximum-value <except>; | [edit services ids rule rule-name term term-name from] | Specify the destination address range for rule matching when using the MS-DPC. | [
{
"name": "minimum-value",
"desc": "Lower boundary for the IPv4 or IPv6 address range."
},
{
"name": "maximum-value",
"desc": "Upper boundary for the IPv4 or IPv6 address range."
},
{
"name": "except",
"desc": "(Optional) Exempt the specified address range from rule matching."
}
] | 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.
minimum-value and maximum-value options enhanced to support IPv4 and IPv6 addresses in Junos OS
Release 8.5. | [
"Configuring Match Conditions in IDS Rules"
] |
destination-address-range (PCP) | destination-address-range high maximum-value low minimum-value <except>; | [edit services pcp rule rule-name term term-name from] | Specify the destination address range that must be matched for the PCP rule. A PCP rule assigns the
PCP server that handles selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. | [
{
"name": "maximum-value",
"desc": "Upper boundary for the address range."
},
{
"name": "minimum-value",
"desc": "Lower boundary for the address range."
},
{
"name": "except",
"desc": "(Optional) Prevent the specified address range from matching the PCP rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
destination-address-range (Services NAT) | destination-address-range low minimum-value high maximum-value <except>; | [edit services nat rule rule-name term term-name from] | Specify the destination address range for rule matching.
If the translation-type statement in the then statement of the nat rule is set to stateful-nat-64, the
destination address range for rule matching must be within the range specified by the destination-prefix
statement in the then statement. | [
{
"name": "minimum-value",
"desc": "Lower boundary for the IPv4 or IPv6 address range."
},
{
"name": "maximum-value",
"desc": "Upper boundary for the IPv4 or IPv6 address range."
},
{
"name": "except",
"desc": "(Optional) Prevent the specified address range from being translated."
... | 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.
minimum-value and maximum-value options enhanced to support IPv6 addresses in Junos OS
Release 8.5. | [
"Network Address Translation Rules Overview"
] |
destination-address-range (Services Stateful Firewall) | destination-address-range low minimum-value high maximum-value <except>; | [edit services stateful-firewall rule rule-name term term-name from] | Specify the destination address range for rule matching. | [
{
"name": "minimum-value",
"desc": "Lower boundary for the IPv4 or IPv6 address range."
},
{
"name": "maximum-value",
"desc": "Upper boundary for the IPv4 or IPv6 address range."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified address range from rule matching."
}
] | 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.
minimum-value and maximum-value options enhanced to support IPv4 and IPv6 addresses in Junos OS
Release 8.5. | [
"Configuring Match Conditions in Stateful Firewall Rules"
] |
destination-address-range | destination-address-range low minimum-value high maximum-value; | [edit services aacl rule rule-name term term-name from] | Specify the destination address range for rule matching. | [
{
"name": "minimum-value",
"desc": "Lower boundary for the IPv4 or IPv6 address range."
},
{
"name": "maximum-value",
"desc": "Upper boundary for the IPv4 or IPv6 address range."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
IPv6 support introduced in Junos OS Release 12.2. | [
"Configuring Match Conditions in AACL Rules"
] |
destination-class-usage | destination-class-usage; | [edit interfaces interface-name unit logical-unit-number family inet accounting],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet accounting] | Enable packet counters on an interface that count packets that arrive from specific customers and are
destined for specific prefixes on the provider core router. | [] | 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. | [
"Enabling Source Class and Destination Class Usage"
] |
destination-classes | destination-classes {
destination-class-name;
} | [edit accounting-options class-usage-profile profile-name] | Specify the destination classes for which statistics are collected. | [
{
"name": "destination-class-name",
"desc": "Name of the destination class to include in the source class usage 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. | [
"Configuring a Class Usage Profile"
] |
destination-equal-load-balancing (L2TP LAC) | destination-equal-load-balancing; | [edit services l2tp] | Enable the LAC to balance the L2TP session load equally across multiple LNSs by selecting tunnels
according to how many sessions currently exist for the destination and tunnel.
Disabled by default. By default, tunnel selection within a preference level is strictly random. The
weighted-load-balancing statement must be d... | [] | 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 LAC Tunneling for Subscribers",
"L2TP LAC Tunneling for Subscribers",
"L2TP LAC Tunneling for Subscribers"
] |
destination-except | destination-except [address-name]; | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match]
[edit security idp idp-policy policy-name rulebase-ips rule rule-name match] | Specify a destination IP address or IP address set object to specify all destination address objects except
the specified address objects. The default value is any. | [
{
"name": "address-name",
"desc": "IP address or IP address set object."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
destination-header | destination-header {
ILNP-nonce-option;
home-address-option;
line-identification-option;
tunnel-encapsulation-limit-option;
user-defined-option-type low | <to high>;
} | [edit security screen ids-option screen-name ip ipv6-extension-header] | Define the IPv6 destination header screen option. | [
{
"name": "ILNP-nonce-option",
"desc": "Enable the Identifier-Locator Network Protocol nonce screen option."
},
{
"name": "home-address-option",
"desc": "Enable the home address screen option."
},
{
"name": "line-identification-option",
"desc": "Enable the line identification screen ... | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"Understanding IPv6 Support for Screens"
] |
destination-host (Gx-Plus) | destination-host hostname; | [edit access gx-plus partition partition-name] | Configure the host on which the PCRF application resides. | [
{
"name": "hostname",
"desc": "Host on which the PCRF is installed."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Gx-Plus",
"Configuring the Gx-Plus Partition"
] |
destination-host (OCS Partition) | destination-host ocs-hostname; | [edit access ocs partition partition-name] | Configure the Destination-Host AVP value used in the CCR-GY-I message. | [
{
"name": "ocs-hostname",
"desc": "Value of the Destination-Host AVP to be used in the CCR-GY-I message."
}
] | 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",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
destination-host (PCRF Partition) | destination-host pcrf-hostname; | [edit access pcrf partition partition-name] | Configure the Destination-Host AVP value used in the CCR-GX-I message. | [
{
"name": "pcrf-hostname",
"desc": "(Optional) Value of the Destination-Host AVP to be used in the CCR-GX-I message."
}
] | 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 PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
destination-host | destination-host hostname | [edit jsrc partition partition-name] | Configure the host on which the SAE application resides. | [
{
"name": "hostname",
"desc": "Host on which the SAE is installed."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"JSRC Configuration Overview",
"Configuring the JSRC Partition"
] |
destination-hostname | destination-hostname destination-hostname; | [edit interfaces name unit name tunnel] | Define the hostname of the tunnel destination for the IP tunnel interface.
After the DNS resolves the IP address for the hostname, the resolved address is used as tunnel
destination address. The ipip interface (IFL) is not created unless the hostname is resolved. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 for SRX Series Firewalls (SRX1500, SRX4100,
SRX4200, SRX5400, SRX5600, SRX5800, and vSRX3.0)
Statement introduced in Junos OS Release 23.4R1 for SRX Series Firewalls (SRX38, SRX300, SRX320,
SRX340, and SRX345) | [
"Tunnel Services Overview"
] |
destination-identity-context | destination-identity-context {
[user-or-role-name];
any;
identity-context-authenticated;
identity-context-unauthenticated;
identity-context-unavailable;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name] | Identifies users and roles to be used as match criteria for a policy. If a value other than any is specified as
match criteria for a policy within a zone pair, the traffic is matched to table entries to retrieve associated
user and roles before policy lookup occurs. Users and roles are retrieved from the local authenti... | [
{
"name": "user-or-role-name",
"desc": "A list of specific users and roles. Range: 0 through 39 characters. SRX Series firewall truncate imported roles to 39 characters. You need to ensure that all of your roles are 39 characters or less."
},
{
"name": "any",
"desc": "Any user or role, as well ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
destination-identity-context-profile | destination-identity-context-profile device-identity-profile-name; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name] | The destination-identity-context-profile field in a security policy enables you to specify a device identity
profile. The device identity feature allows you to use the identity of a device and its attributes to control
access to network resources instead of the identity of the user of that device. | [
{
"name": "device-identity-profile-name",
"desc": "Device identity profile that specifies characteristics that can apply to one or more devices."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
destination-interface | destination-interface interface-name; | [edit services rpm probe owner test test-name],
[edit services rpm probe-server (tcp | udp)],
[edit services rpm twamp client control-connection control-client-name] | On M Series and T Series routers, specify a services (sp-) interface that adds a timestamp to RPM probe
messages. This feature is supported only with icmp-ping, icmp-ping-timestamp, udp-ping, and udp-ping-timestamp
probe types. You must also configure the rpm statement on the sp- interface and include the unit 0 family... | [
{
"name": "interface-name",
"desc": "Name of the adaptive services interface."
}
] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in Junos OS Release 15.1 for MX Series routers. | [
"Configuring RPM Timestamping on MX, M, T, and PTX Series Routers and EX Series Switches",
"Configuring RPM Receiver Servers",
"Configuring RPM Timestamping on MX, M, T, and PTX Series Routers and EX Series Switches",
"Enabling RPM on MX, M and T Series Routers and SRX Firewalls for the Services SDK"
] |
destination-ip (Security Alarms) | destination-ip {
duration interval;
size count;
threshold value;
} | [edit security alarms potential-violation policy] | Configure alarms for a number of policy violations to a destination network identifier within a specified
time period. | [
{
"name": "duration interval",
"desc": "Indicate the duration of counters."
},
{
"name": "size count",
"desc": "Indicate the number of destination IP addresses for which policy violation checks can be"
},
{
"name": "threshold value",
"desc": "Indicate the maximum number of destinatio... | 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. | [
"Security Policies Overview"
] |
destination-ip-address (RADIUS Snoop Segment) | destination-ip-address destination-address; | [edit access radius snoop-segments segment-name] | Specify the destination IP address for accounting messages to snoop. | [
{
"name": "destination-address",
"desc": "Destination IPv4 address of accounting messages."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Snooping of RADIUS Accounting Requests for IP-Based Subscribers",
"Snooping RADIUS Accounting Requests for IP-Based Subscribers Overview",
"IP-Based Subscriber Setup Overview"
] |
destination-ip-based | destination-ip-based number; | [edit security screen ids-option screen-name limit-session] | Limit the number of concurrent sessions the device can direct to a single destination IP address. | [
{
"name": "number",
"desc": "Maximum number of concurrent sessions that can be directed to a destination IP address."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
destination-ipv4-address (RFC 2544 Benchmarking Tests) | destination-ipv4-address address; | [edit services monitoring rfc2544 tests test-name test-name] | Specify the destination IPv4 address to be used in generated test frames. You must configure this option
if you specify inet as the family. This option is not required if you specify ccc as the family. | [
{
"name": "address",
"desc": "(Required if you specify inet as the family.) Valid IPv4 address. Default: When you specify ccc as the family, if you do not configure the destination IPv4 address, the default value of 192.168.1.20 is used."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X52.
Statement introduced in Junos OS Evolved Release 21.1R1. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers"
] |
destination-ipv4-address | destination-ipv4-address ipv4-address; | [edit protocols pcep pce pce-id] | Specify the IPv4 address of the Path Computation Element (PCE) to which the Path Computation Client
(PCC) should connect. | [
{
"name": "ipv4-address",
"desc": "IPv4 address of the PCE."
}
] | 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. | [] |
destination-ipv6-address | destination-ipv6-address destination-ipv6-address; | [edit logical-systems name protocols pcep pce],
[edit protocols pcep pce] | Specify the IPv6 address of the Path Computation Element (PCE) to which the Path Computation Client
(PCC) should connect. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1. | [] |
destination-mac-address | destination-mac-address mac-address; | [edit services monitoring rfc2544 tests test-name test-name] | Specify the destination MAC address used in the generated test frames. This is a mandatory parameter
for family bridge and vpls and optional for family ccc. | [
{
"name": "mac-address",
"desc": "Specify the MAC address as six hexadecimal bytes in one of the following formats:"
},
{
"name": "nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn",
"desc": "for example, 0000:5e00:5355 or 00:00:5e:00:53:55."
}
] | 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 22.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"Configuring an RFC 2544-Based Benchmarking Test"
] |
destination-nat | destination-nat (off | pool pool-name | rule-session-count-alarm (clear-threshold value | raise-
threshold value)); | [edit security nat destination rule-set rule-set-name rule rule-name then] | Specify the action of the destination NAT rule. | [
{
"name": "off",
"desc": "Do not perform destination NAT operation."
},
{
"name": "pool",
"desc": "Use user-defined destination NAT pool to perform destination NAT."
},
{
"name": "rule-session-count-alarm",
"desc": "Define session count alarm thresholds for a specific destination NAT... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. The rule-session-count-alarm option added in Junos OS
Release 12.1X45-D10. | [] |
destination-networks | destination-networks prefix; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
dynamic-tunnels tunnel-name],
[edit logical-systems logical-system-name routing-options dynamic-tunnels tunnel-name rsvp-te
entry],
[edit logical-systems logical-system-name routing-options dynamic-tunnels tunnel-name],
... | Specify the IPv4 prefix range for the destination network. Only tunnels within the specified IPv4 prefix
range can be created. | [
{
"name": "prefix",
"desc": "Destination prefix of the network."
}
] | 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 GRE Tunnels for Layer 3 VPNs",
"Dynamic Tunnels Overview",
"Configuring RSVP Automatic Mesh"
] |
destination-option | destination-option {
home-address {
match (equal | greater-than | less-than | not-equal);
value header-value;
}
option-type {
match (equal | greater-than | less-than | not-equal);
value header-value;
}
} | [edit set security idp custom-attack attack-name attack-type signature protocol ipv6 extension-
header] | Specify the IPv6 destination option for the extension header. The destination-option option inspects the
header option type of home-address field in the extension header and reports a custom attack if a match is
found. The destination-option supports the home-address field type of inspection. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.