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 |
|---|---|---|---|---|---|---|---|
interfaces (Class of Service) | interfaces {
interface-name {
classifiers {
dscp (classifier-name | default) {
}
ieee-802.1 (classifier-name | default) vlan-tag (inner | outer | classifier-name);
inet-precedence (rewrite-name | default);
}
congestion-notification-profile profil... | [edit class-of-service] | Associate class of service (CoS) configuration elements with an interface.
NOTE: Only devices that support direct port scheduling also support applying a
scheduler map directly to an interface. When using hierarchical port scheduling, you
cannot apply a scheduler map directly to an interface. Instead, you associate the... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Interface-set level added in Junos OS Release 8.5. | [
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic",
"Configuring Rewrite Rules",
"Assigning CoS Components to Interfaces",
"Interfaces Overview for Switches",
"Example: Configuring CoS on EX Series Switches",
"Defining CoS Classifiers (CLI Procedure)",
"Defining CoS Classifier... |
interfaces (Dynamic CoS Definition) | interfaces {
interface-name {
unit logical-unit-number {
classifiers {
dscp (classifier-name | default);
dscp-ipv6 (classifier-name | default);
ieee-802.1 (classifier-name | default) vlan-tag (inner | outer)
inet-precedence (classif... | [edit dynamic-profiles profile-name class-of-service] | Configure interface-specific CoS properties for incoming packets in a dynamic client profile or a dynamic
service profile. | [
{
"name": "interface-name",
"desc": "Either the specific name of the interface you want to assign to the dynamic profile 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.2. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile"
] |
interfaces (EX Series switches) | No Link Title
No Link Title
No Link Title
No Link Title
No Link Title
No Link Title
No Link Title
No Link Title
No Link Title
interfaces ae
aex {
accounting-profile name;
aggregated-ether-options {
(flow-control | no-flow-control);
lacp {... | [edit] | Supported Protocol Families
ccc
ethernet-
switching
inet
inet6
iso
mpls
interface-
range
Interface-range configuration
Supported protocol families are the ones supported by the
interface types that compose the range.
lo0
Loopback interface
✓
✓
✓
✓
me0
Management Ethernet
interface
✓
✓
✓
✓
✓
vlan
Routed VLAN 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. | [
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Configuring Aggregated Ethernet Links (CLI Procedure)",
"Configuring a Layer 3 Subinterface (CLI Procedure)",
"Configuring Routed VLAN Interfaces on Switches (CLI Procedure)",
"Configuring the Virtual Management Ethernet Interface for Global Manage... |
interfaces (Junos Node Slicing) | interfaces interface-name{
unit unit {
family (inet|inet6) {
address address;
}
}
} | [edit ] | Configure an IP address for the JDM management interface. | [
{
"name": "interface-name",
"desc": "Name of the interface."
},
{
"name": "unit unit",
"desc": "Interface unit number. This is a logical unit number. The only supported value is 0."
},
{
"name": "family (inet|inet6)",
"desc": "Protocol family."
},
{
"name": "inet",
"desc"... | root | Statement introduced in Junos OS Release 17.2. | [] |
interfaces (MACsec for MX Series) | interfaces interface-name {
connectivity-association connectivity-association-name;
unit unit-number {
connectivity-association connectivity-association-name;
}
} | [edit security macsec] | Applies the specified connectivity association to the specified interface to enable MACsec.
One connectivity association can be applied to multiple interfaces.
You must always use this statement to apply a connectivity association to an interface to enable
MACsec. You must complete this configuration step regardless of... | [
{
"name": "connectivity-association",
"desc": ""
},
{
"name": "connectivity-association-name",
"desc": "Specify the connectivity association to assign to the interface. A connectivity association is a set of MACsec attributes that are used by interfaces to create secure inbound and outbound chan... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
Support for unit option introduced in Junos OS Release 19.3 for MPC7E-10GE line cards. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
interfaces (MACsec) | interfaces interface-name {
connectivity-association connectivity-association-name;
} | [edit security macsec]
[edit security macsec cluster-data-port] | Applies the specified connectivity association to the specified interface to enable MACsec.
One connectivity association can be applied to multiple interfaces.
You must always use this statement to apply a connectivity association to an interface to enable
MACsec. You must complete this configuration step regardless of... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced for SRX Series Firewalls in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
interfaces (OVSDB) | interfaces interface-name; | [edit protocols ovsdb] | Specify the physical interfaces on a Juniper Networks device that you want the Open vSwitch Database
(OVSDB) protocol to manage. Typically, the only interfaces that need to be managed by OVSDB are
interfaces that are connected to physical servers. | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Setting Up the OVSDB Protocol on Juniper Networks Devices that Support Manual Configuration of",
"VXLANs",
"Setting Up OVSDB on Juniper Networks Devices That Support the Dynamic Configuration of",
"VXLANs"
] |
interfaces (Protocols OpenFlow) | interfaces {
interface-name port-id port;
} | [edit protocols openflow switch switch-name] | Configure a Layer 2 interface as an OpenFlow-enabled interface. | [
{
"name": "interface-name",
"desc": ""
},
{
"name": "Name of the interface, including the logical unit number",
"desc": "for example, ge-1/1/0.0."
},
{
"name": "port-id port",
"desc": "(Optional) Unique numeric value specifying the port ID associated with the OpenFlow interface. You ... | 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"
] |
interfaces (Q-in-Q Tunneling) | interfaces interface-name {
no-mac-learning;
} | [edit ethernet-switching-options] | Configure settings for interfaces that have been assigned to family ethernet-switching. | [] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Q-in-Q Tunneling and VLAN Translation"
] |
interfaces (QFX Series, EX Series) | interfaces {
aex {
disable;
aggregated-ether-options {
configured-flow-control {
rx-buffers (on | off);
tx-buffers (on | off);
}
(fcoe-lag | no-fcoe-lag);
flexible-vlan-tagging;
(flow-control | no-flow-co... | [edit] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "aex",
"desc": "Configure an aggregated Ethernet interface."
},
{
"name": "xe-0/0/port/",
"desc": "Configure a 10-Gigabit Ethernet interface."
},
{
"name": "ge-0/0/port/",
"desc": "Configure a Gigabit Ethernet interface."
},
{
"name": "fc-0/0/port/",
"desc": "Co... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Statement support for QFX series introduced in Junos OS EVO Release 21.3 | [
"Interfaces Overview for Switches",
"Gigabit Ethernet Interface",
"Configuring a Layer 3 Logical Interface",
"Understanding Interface Ranges for Switches",
"Configuring Link Aggregation"
] |
interfaces (Security Zones) | interfaces interface-name {
host-inbound-traffic {
protocols protocol-name {
except;
}
system-services service-name {
except;
}
}
} | [edit security zones functional-zone management],
[edit security zones security-zone zone-name] | Specify the set of interfaces that are part of the zone. | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | 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. | [] |
interfaces (Services Dynamic Flow Capture) | interfaces interface-name; | [edit services dynamic-flow-capture capture-group client-name] | Specify the DFC interface used with the control source configured in the same capture group. | [
{
"name": "interface-name",
"desc": "Name of the DFC interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the DFC PIC Interface"
] |
interfaces (sFlow) | [edit protocols sflow] | Configure sFlow network traffic monitoring on the specified interface on the device. You can configure
sFlow parameters such as polling interval and sampling rate with different values on different interfaces,
and you can also disable sFlow monitoring on individual interfaces.
The remaining statements are explained sep... | [
{
"name": "interface-name",
"desc": "Name of the interface on which to configure sFlow parameters."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring sFlow Technology for Network Monitoring (CLI Procedure)",
"Example: Monitoring Network Traffic Using sFlow Technology",
"Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series Switches",
"Configuring sFlow Technology for Network Monitoring (CLI Procedure)",
"Example: Conf... | |
interfaces (Static and Dynamic Subscribers) | interfaces {
interface-name {
unit logical-unit-number {
actual-transit-statistics;
auto-configure {
agent-circuit-identifier {
dynamic-profile profile-name;
}
line-identity {
includes {
... | [edit dynamic-profiles profile-name] | Define interfaces for dynamic client profiles. | [
{
"name": "interface-name",
"desc": "The interface variable ($junos-interface-ifd-name). The interface variable is dynamically"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles",
"Configuring Dynamic PPPoE Subscriber Interfaces",
"Configuring Dynamic VLANs Based on Agent Circuit Identifier Information",
"DHCP Subscriber Interface Overview",
"Subscribers over Static Interfaces Configuration Ove... |
interfaces (Video Monitoring) | interfaces {
interface-name {
family {
inet {
input-flows {
input-flow-name {
destination-address [ address ];
destination-port [ port ];
source-address [ address ];
... | [edit services video-monitoring] | Define video monitoring for specified input or output flows on selected interfaces. You can configure a
maximum of 256 flows for an interface. | [
{
"name": "destination-address address",
"desc": "Destination IPv4 or IPv6 address or prefix value of a flow that you want to monitor. You can use up to 32 addresses. For IPv4-over-MPLS flows, if you configure multiple addresses for both the destination and source, then either all the destination or all the... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
mpls option introduced in Junos OS Release 17.2.
payload-type ipv6 option introduced in Junos OS Release 17.4. | [
"Configuring Inline Video Monitoring on MX Series Routers"
] |
interfaces (VNF) | interfaces interface-name {
pci-address pci-address;
mac-address mac-address;
mtu size;
mapping {
hsxe0 {
virtual-function {
vlan-id vlan-id;
}
}
hsxe1 {
virtual-function {
vlan-id vlan-id;
... | [edit virtual-network-functions] | Configure Virtual Network Functions (VNF) interfaces on platforms running disaggregated Junos OS. | [
{
"name": "interface-name",
"desc": "Name of the VNF interfaces."
},
{
"name": "mac-address",
"desc": "MAC address of the VNF interfaces."
},
{
"name": "mtu",
"desc": "Maximum transfer unit (MTU) size of packets in bytes."
},
{
"name": "pci-address",
"desc": "Target PCI a... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D50. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
interfaces (Voice Services) | interfaces { ... } | [edit] | Configure interfaces on the router.
Default
The management and internal Ethernet interfaces are automatically configured. You must configure all
other interfaces. | [] | 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. | [
"Junos OS Network Interfaces Library for Routing Devices"
] |
interfaces external | interfaces {
external/external-0-0/external-1/0 {
e1-options {
framing (g704 | g704-no-crc4);
line-encoding (ami | hdb3);
sabit bit;
}
signal-type (1mhz | 5mhz | 10mhz | 2048khz | t1 | e1);
t1-options {
framing (esf | sf);
line-encoding (ami | b8zs);
}
... | [edit chassis synchronization] | Starting from Junos OS Release 12.3, configure options for the external clock source interface—external
—for SCBE.
Starting from Junos OS Release 13.3, configure options for the two external clock source interfaces—
external-0/0 and external-1/0—for SCBE2. | [] | 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. | [] |
interfaces | interfaces { ... } | [edit ] | Configure settings for interfaces that have been assigned to family ethernet-switching.
Default
The management and internal Ethernet interfaces are automatically configured. You must configure all
other interfaces. | [
{
"name": "interface-name",
"desc": "Name of an interface that is configured for family ethernet-switching."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Physical Interface Properties Overview",
"Configuring Aggregated Ethernet Link Protection"
] |
interim-logging-interval | interim-logging-interval timeout-inteval; | [edit security nat source pool port block-allocation] | Specify how often interim system logs are sent for active port blocks and for inactive port blocks with
live sessions. Because system logs are UDP-based, they can be lost in the network. For this reason,
configuring interim logging, which triggers re-sending system logs, increases reliability. In a chassis
cluster conf... | [
{
"name": "timeout-interval",
"desc": "Number of seconds between interim logging messages."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D60. | [] |
interim-rate (Access) | interim-rate rate; | [edit access radius-options] | Configure the rate at which RADIUS interim update requests are processed. | [
{
"name": "rate",
"desc": "Maximum number of RADIUS requests sent per second."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"RADIUS Servers and Parameters for Subscriber Access"
] |
interleave-fragments | interleave-fragments; | [edit interfaces ls-fpc/pic/port:channel unit logical-unit-number],
[edit logical-systems logical-system-name interfaces ls-fpc/pic/port unit logical-unit-number] | For link services and voice services interfaces only, interleave long packets with high-priority packets.
Allows small delay-sensitive packets, such as voice over IP (VoIP) packets, to interleave with long
fragmented packets. This minimizes the latency of delay-sensitive packets. | [] | 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 Delay-Sensitive Packet Interleaving on Link Services Logical Interfaces"
] |
internal (Security IPsec) | internal {
security-association {
manual {
encryption {
algorithm (3des-cbc | aes-128-cbc);
ike-ha-link-encryption enable;
key ascii-text;
}
}
}
} | [edit security ipsec] | Enable secure login and to prevent attackers from gaining privileged access through this control port by
configuring the internal IP security (IPsec) security association (SA).
When the internal IPsec is configured, IPsec-based rlogin and remote command (rcmd) are enforced, so an
attacker cannot gain unauthorized info... | [
{
"name": "security-association",
"desc": "Specify an IPsec SA. An SA is a simplex connection that allows two hosts to communicate with each other securely by means of IPsec."
},
{
"name": "manual encryption",
"desc": "Specify a manual SA. Manual SAs require no negotiation; all values, including... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10.
Support for ike-ha-link-encryption option added in Junos OS Release 12.1X47-D15.
Support for iked_encryption option added in Junos OS Release 12.1X47-D10.
Support for aes-128-cbc option added in Junos OS Release 19.1R1.
Support for ike-ha-link-encryption option adde... | [
"Example: Configuring an Active/Passive Chassis Cluster on SRX5800 Devices"
] |
internal | internal {
security-association {
manual {
direction (bidirectional | inbound | outbound) {
protocol esp;
spi spi-value;
encryption {
algorithm 3des-cbc;
key ascii-text ascii-text-string;
}
... | [edit security ipsec] | (Junos-FIPS only) Define an internal security association (SA) for internal Routing-Engine–to–Routing-
Engine communication. | [] | Crypto Officer—To view and add this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec for Enabling Internal Communications Between Routing Engines for Junos OS in",
"FIPS Mode"
] |
internal-forwarding-bandwidth | internal-forwarding-bandwidth <value>; | [edit system packet-forwarding-options] | You can configure the bandwidth of the recycle interface to enable equal distribution of the recycle
interface bandwidth at PFE level.
The recycle interface has a default 100Gbps per unit bandwidth allocation, which is used entirely in all
ingress-egress-multicast replication.
For example, you can configure each recycl... | [
{
"name": "value",
"desc": "Recycle interface bandwidth value in Gbps. Range: 1 through 100 Gbps Default: 100 Gbps"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.4R1. | [
"Ingress and Egress Multicast Replication using Recycle Replication Model"
] |
internal-node | internal-node; | [edit class-of-service interfaces interface-set interface-set-name] | The statement is used to raise the interface set without children to the same level as the other
configured interface sets with children, allowing them to compete for the same set of resources.
Default
If you do not include this statement, the node is internal only if its children have a traffic control profile
configu... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Internal Scheduler Nodes"
] |
internet-options | internet-options {
ipv6-duplicate-addr-detection-transmits ipv6-duplicate-addr-detection-transmits;
(path-mtu-discovery | no-path-mtu-discovery);
} | [edit system] | Configure system IP options to protect against certain types of DoS attacks. | [
{
"name": "gre-path-mtu-discovery",
"desc": "Configure path MTU discovery for outgoing GRE tunnel connections. By default, path MTU discovery is enabled."
},
{
"name": "no-gre-path-mtu-discovery",
"desc": "Path MTU discovery is disabled."
},
{
"name": "icmpv4-rate-limit",
"desc": "Co... | 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.
no-tcp-reset introduced in Junos OS Release 9.4.
no-tcp-reset introduced in Junos OS Release 11.1.
icmpv4-rate-limit and source-port introduced in Junos OS Release 11.1 and Junos OS Release 14.1X53-
D20.
path-mtu-discovery and no-path-mtu-discovery introduced in Junos O... | [
"Configure ICMP Features",
"Configure IPv6 Features",
"Configure Path MTU Discovery",
"Configure TCP Options",
"Configuring Junos OS to Extend the Default Port Address Range",
"Understanding Traffic Processing on Security Devices"
] |
interoperability | interoperability express5-enhanced; | [edit chassis] | (PTX devices with PTX10K-LC1301-36DD Line Card Only) Chassis PFE interoperability configuration.
By default, all line cards on the PTX device are active and interoperate. This command brings up the
PTX10K-LC1301-36DD line cards to support the Express5 ASIC capabilities on a supported PTX device.
All other line cards re... | [
{
"name": "express5-enhanced",
"desc": "Enable FPCs with express5 PFE features"
}
] | Statement introduced in Junos OS Evolved Release 25.4R1. | [] | |
interpolate (Drop Profiles) | interpolate {
drop-probability [values];
fill-level [values];
} | [edit class-of-service drop-profiles profile-name] | Specify values for interpolating relationship between queue fill level and drop probability.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Defining Packet Drop Behavior by Configuring RED Drop Profiles"
] |
interval (Accounting Options) | interval minutes; | [edit accounting-options class-usage-profile profile-name],
[edit accounting-options filter-profile profile-name],
[edit accounting-options interface-profile profile-name],
[edit accounting-options mib-profile profile-name],
[edit accounting-options routing-engine-profile profile-name] | Specify how often statistics are collected for the accounting profile. | [
{
"name": "minutes",
"desc": "Length of time between each collection of statistics."
}
] | 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.
The [edit accounting-options mib-profile profile-name] hierarchy level added in Junos OS Release 8.2. | [
"Configuring the Interface Profile",
"Configuring the Filter Profile",
"Configuring the MIB Profile",
"Configuring the Routing Engine Profile"
] |
interval (CFM MEP) | interval (1m | 1s); | [edit protocols oam ethernet connectivity-fault-management action-profile action-profile-name
action log-and-generate-ais] | Configure the interval between AIS messages that are to be received by the MEP as either 1 minute or
1 second. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Ethernet Alarm Indication Signal (ETH-AIS) Function Overview",
"Configuring ETH-AIS on a CFM MEP"
] |
interval (EX Series Switch Only) | interval (10m | 10s | 1m | 1s | 100ms | 10ms); | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Configure the time between continuity check messages. | [
{
"name": "10m",
"desc": "10 minutes."
},
{
"name": "10s",
"desc": "10 seconds."
},
{
"name": "1m",
"desc": "1 minute."
},
{
"name": "1s",
"desc": "1 second."
},
{
"name": "100ms",
"desc": "100 milliseconds."
},
{
"name": "10ms",
"desc": "10 millis... | 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 Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
interval (Flat-File Accounting Options) | interval minutes; | [edit accounting-options flat-file-profile profile-name] | Specify the interval in minutes at which the Packet Forwarding Engine associated with the interface is
polled to collect the statistics specified in the flat-file accounting profile. These interim accounting
results are recorded in the flat file.
NOTE: The value configured with this statement is superseded by the valu... | [
{
"name": "minutes",
"desc": "Polling interval. Range: 1 through 2880 minutes Default: 15 minutes"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Configuring Service Accounting in Local Flat Files",
"Flat-File Accounting Overview"
] |
interval (Health Monitor) | interval seconds; | [edit snmp health-monitor],
[edit snmp health-monitor idp] | Interval between samples. | [
{
"name": "seconds",
"desc": "Time between samples, in seconds."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring the Interval"
] |
interval (Interfaces) | interval seconds; | [edit interfaces interface-name unitlogical-unit-number radio-router credit] | Configure the frequency that the router generates credit announcement messages. | [
{
"name": "seconds",
"desc": "Interval between PADG credit announcements for each session."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 10.1 of Junos OS. | [
"Configuring PPPoE-Based Radio-to-Router Protocols"
] |
interval (OAM) | interval (100ms | 10m | 10ms | 10s | 1m | 1s| 3.3ms); | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Configure the interval between successive transmissions of continuity check messages (CCMs) as part of
the connectivity fault detection strategy. When the receiving maintenance association end point (MEP)
does not receive a CCM at the configured interval, the loss-threshold statement determines how many
CCMs can be los... | [
{
"name": "100ms",
"desc": "100 milliseconds."
},
{
"name": "10m",
"desc": "10 minutes."
},
{
"name": "10ms",
"desc": "10 milliseconds."
},
{
"name": "10s",
"desc": "10 seconds."
},
{
"name": "1m",
"desc": "1 minute."
},
{
"name": "1s",
"desc": "1 ... | 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.
Option 10ms introduced in Junos OS Release 9.1.
Third-party interoperability during a unified in-service software upgrade (ISSU) introduced in Junos OS
Release 17.1.
Option 3.3ms introduced in Junos OS Release 17.2. | [
"Continuity Check Protocol Parameters Overview",
"Configuring Continuity Check Protocol Parameters for Fault Detection",
"Configuring Connectivity Fault Management for Interoperability During Unified In-Service Software",
"Upgrades"
] |
interval (PoE) | interval minutes; | [edit poe interface (all | interface-name) telemetries] | Modifies the interval for logging telemetries if you are monitoring the per-port power consumption for
PoE interfaces. | [
{
"name": "minutes",
"desc": "Interval at which data is logged."
}
] | 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. | [
"Understanding Interfaces"
] |
interval (Power over Ethernet) | interval minutes; | [edit poe interface (all | interface-name) telemetries] | Modify the interval at which data is collected when you are monitoring the power consumption of a PoE
interface. | [
{
"name": "minutes",
"desc": "Frequency of data collection."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring PoE Interfaces on EX Series Switches",
"Configuring PoE (J-Web Procedure)"
] |
interval (Protocols PIM) | interval milliseconds; | [edit protocols pim interface (Protocols PIM) interface-name multiple-triggered-joins] | Specify the duration between the triggered joins of the PIM neighbors through the PIM interface. | [
{
"name": "milliseconds",
"desc": "Value for the interval between the triggered joins."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [] |
interval (RMON) | interval seconds; | [edit snmp rmon alarm index] | Interval between samples. | [
{
"name": "seconds",
"desc": "Time between samples, in seconds."
}
] | 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 Interval"
] |
interval (Security Antivirus) | interval value; | [edit security utm feature-profile anti-virus juniper-express-engine pattern-update]
[edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update]
[edit security utm feature-profile anti-virus sophos-engine pattern-update]
[edit security utm default-configuration anti-virus avira-engine pattern-upd... | Set the pattern data files auto-update interval. You can choose to leave the default interval value or you
can change it by using this command. You can also force a manual update, if necessary.
NOTE: The data files used with Sophos are not typical virus pattern files; they are small
files that help guide virus scanning... | [
{
"name": "value",
"desc": "Pattern data files auto-update interval in minutes."
},
{
"name": "minutes (every 24 hours)",
"desc": ""
}
] | 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 for Juniper Express
engine and Kaspersky Lab engine. Support for Sophos engine added in Junos OS Release 11.1.
The [edit security utm default-config... | [] |
interval (Security IDP) | interval hours; | [edit security idp security-package automatic] | Specify the amount of time that the device waits before updating the signature database. User should
insert a default value. | [
{
"name": "hours",
"desc": "Number of hours that the device waits."
}
] | 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. | [] |
interval (services) | interval seconds; | [edit services ipsec-vpn rule rule-name term term-name then dead-peer-detection] | Specify the amount of time that the peer waits for traffic from its destination peer before sending a
dead-peer-detection (DPD) request packet. The interval value is used for IKEv1 security associations
(SAs). Starting in Junos OS Release 17.2R1, the interval value is also applicable to IKEv2 SAs. In Junos
OS Release 1... | [
{
"name": "seconds",
"desc": "Number of seconds that the peer waits before sending a DPD request packet. Range: 1 through 180 seconds Default: 10 seconds"
}
] | 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.
IKEv2 support introduced in Junos OS Release 17.2. | [
"Configuring IPsec Rules"
] |
interval (Services) | interval seconds; | [edit services unified-access-control ] | Specify the value in seconds that the SRX Series Firewall should expect to receive a heartbeat signal
from the IC Series device (default 30). This configuration statement is used in conjunction with the
timeout statement to test active communications with the IC Series device. The value of the interval
statement must b... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [] |
interval (SNMP RMON) | interval seconds; | [edit snmp rmon alarm index],
[edit snmp rmon history] | Configure the interval over which data is to be sampled for the specified interface.
Default
60 sec for alarm sampling.
1800 sec for Ethernet packet history sampling. | [
{
"name": "seconds",
"desc": "Interval at which data is to be sampled for the specified interface."
}
] | snmp—To view this statement in the configuration.
snmp–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Understanding RMON",
"RMON MIB Event, Alarm, Log, and History Control Tables",
"Configuring RMON History Sampling",
"Monitoring RMON MIB Tables"
] |
interval | interval value; | [edit interfaces interface-name otn-options signal-degrade]
[edit interfaces interface-name otn-options odu-signal-degrade] | Specify the interval for which the BER must stay above the signal degradation threshold—as configured
in the ber-threshold-signal-degrade value statement—for the alarm to raised. After an alarm is raised, if the
BER returns below the clear threshold—as configured in the ber-threshold-clear value statement—for the
speci... | [
{
"name": "value",
"desc": "Time interval in milliseconds."
}
] | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
interval-length (Chassis) | interval-length (10s|30s|1min|5min|15min); | [edit chassis optics pm] | Configure the user configurable PM interval lengths to enhance your network's performance monitoring
capabilities.
Default
When the configuration is deleted, the interval length reverts back to the default 15-minute duration. | [
{
"name": "interval length",
"desc": ""
},
{
"name": "10 seconds",
"desc": ""
},
{
"name": "30 seconds",
"desc": ""
},
{
"name": "1 minute",
"desc": ""
},
{
"name": "5 minutes",
"desc": ""
},
{
"name": "15 minutes",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1 for PTX Series routers. | [] |
intra-area-prefix | intra-area-prefix; | [edit logical-systems name protocols ospf3 overload],
[edit protocols ospf3 overload] | Advertise intra-area Prefix with maximum metric. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2. | [
"Understanding OSPF Overload Function"
] |
intra-as | intra-as {
inclusive;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
family (inet | inet6) autodiscovery-only],
[edit routing-instances routing-instance-name protocols mvpn family (inet | inet6) autodiscovery-
only] | For Rosen 7, enable the MVPN control plane for autodiscovery only, using intra-AS autodiscovery
routes. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement moved to [..protocols mvpn family inet] from [.. protocols mvpn] in Junos OS Release 13.3.
Support for IPv6 added in Junos OS Release 17.3R1. | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs",
"invalid-authentication-entry-timeout (Services User Identification Active"
] |
Directory and ClearPass) | invalid-authentication-entry-timeout timeout-value-in-minutes; | [edit services user-identification active-directory-access]
[edit services user-identification authentication-source (Services User Identification ClearPass)
aruba-clearpass] | Configure an independent timeout value to be assigned to invalid user authentication entries in the SRX
Series authentication table for either Windows active directory or Aruba ClearPass. The invalid
authentication entry timeout setting is different from the general authentication entry timeout setting. It
allows you t... | [
{
"name": "timeout-value-in-minutes",
"desc": "Expiration time in minutes to be applied to invalid authentication entries in the SRX Series authentication table for either Windows active directory or Aruba ClearPass authentication sources. Range: 0 through 1440 minutes. Default: 30 minutes"
}
] | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D100. | [
"Understanding the Invalid Authentication Table Entry Timeout Setting",
"Understanding the Forced Timeout Setting Assigned to Active Directory Authentication Entries for",
"Users Authenticated Through Captive Portal",
"firewall-authentication-forced-timeout"
] |
ioc-npc-connectivity | ioc-npc-connectivity {
ioc name {
npc(none | npc-slot);
}
} | [edit chassis] | Connectivity between IOC and NPC | [] | [none specified] | Statement introduced in Junos OS Release 10.4R1. | [] |
ip (IDS Screen Next Gen Services) | ip {
bad-option;
block-frag;
ipv6-extension-header {
AH-header;
ESP-header;
fragment-header;
hop-by-hop-header {
CALIPSO-option;
jumbo-payload-option;
quick-start-option;
router-alert-option;
RPL-option;
... | [edit services screen ids-option screen-name] | Configure protection against suspicious IP packet attacks.
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 19.3R1. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
ip (Security IDP Custom Attack) | ip {
protocol-number transport-layer-protocol-number;
} | [edit security idp custom-attack attack-name attack-type chain protocol-binding],
[edit security idp custom-attack attack-name attack-type signature protocol-binding] | Allow IDP to match the attack for a specified IP protocol type. | [
{
"name": "protocol-number transport-layer-protocol-number",
"desc": "Transport Layer protocol number."
}
] | 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. | [] |
ip (Security Screen) | ip {
bad-option;
block-frag {
white-list name;
}
ipv6-extension-header {
AH-header;
ESP-header;
HIP-header;
destination-header {
ILNP-nonce-option;
home-address-option;
line-identification-option;
tunnel-encapsul... | [edit security screen ids-option screen-name] | Configure IP layer IDS options. | [
{
"name": "bad-option",
"desc": "Detect and drop any packet with an incorrectly formatted IP option in the IP packet"
},
{
"name": "block-frag",
"desc": "Enable IP packet fragmentation blocking."
},
{
"name": "loose-source-route-option",
"desc": "Detect packets where the IP option is... | 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. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
ip | ip address</prefix-length>; | [edit services application-identification rule rule-name address destination],
[edit services application-identification rule rule-name address source] | Define an IP address and netmask for identifying the traffic destination or source. | [
{
"name": "address</prefix-length>",
"desc": "IP address and netmask."
}
] | 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"
] |
ip-action (Security IDP Rulebase IPS) | ip-action {
(ip-block | ip-close | ip-notify | ip-connection-rate-limit);
log;
log-create;
refresh-timeout;
target (destination-address (Security IDP Policy) | service | source-address | source-zone |
source-zone-address | zone-service);
timeout seconds;
} | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then] | Specify the actions you want IDP to take against future connections that use the same IP address. | [
{
"name": "ip-block",
"desc": "Block future connections of any session that matches the IP action. If there is an IP action match with multiple rules, then the most severe IP action of all the matched rules is applied. The highest IP action priority (that is, the most severe action) is Drop/ Block, then Clo... | 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.
Option log-create and refresh-timeout, and ip-connection-rate-limit introduced in Junos OS Release 10.2.
NOTE: For ICMP flows, the destination port is 0; therefore, any ICMP flow matching
source port, source address, and destination address is blocked. | [] |
ip-address (Access Profile) | ip-address address; | [edit access profile name client name xauth] | Specify the IP address for the client. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 10.4 of Junos OS. | [
"Firewall User Authentication Overview"
] |
ip-address (Port Mirroring) | ip-address ip-address; | [edit forwarding-options] analyzer name output]
[edit forwarding-options port-mirroring [instance name] family ethernet-switching output interface
name] | Specify the IP address to which traffic should be mirrored (the IP address of the analyzer system). The
device can be on a remote network. The analyzer device must be able to de-encapsulate GRE-
encapsulated packets, or the GRE-encapsulated packets must be de-encapsulated before reaching the
analyzer device. (You can u... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53. | [] |
ip-address-first | ip-address-first; | [edit logical-systems logical-system-name system services dhcp-local-server pool-match-order],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server pool-match-order],
[edit routing-instances routing-instance-name system services dhcp-local-server pool-matc... | Configure the extended DHCP local server to use the IP address method to determine which address-
assignment pool to use. The local server uses the IP address in the gateway IP address if one is present
in the DHCP client PDU. If no gateway IP address is present, the local server uses the IP address of the
receiving in... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring How the Extended DHCP Local Server Determines Which Address-Assignment Pool to",
"Use",
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Address-Assignment Pools Overview"
] |
ip-address-owner | ip-address-owner owner; | [edit interfaces interface-name unit logical-unit-number] | Define the owner for IP addresses hosted on an ms- interface. This statement is used to specify that the
steering of control plane packets to the Multiservices PIC be preserved. The provider of your application
or its user documentation will tell you when you need to set this configuration. | [
{
"name": "owner",
"desc": "Owner of the IP address for the interface. There are two options: Values:"
},
{
"name": "routing-engine",
"desc": "IP address defined on the interface is hosted by the Routing Engine. This option is not used."
},
{
"name": "service-plane",
"desc": "IP add... | view | Statement introduced in Junos OS Release 13.2R1. | [] |
ip-can-type (PCRF Partition) | ip-can-type number; | [edit access pcrf partition partition-name] | Configure an IP connectivity access network (IP-CAN) value according to what best fits your operating
environment and access network. The Policy and Charging Rules Function (PCRF) partition requires that
you configure this statement. The Policy Control and Charging (PCC) enables a centralized control to
ensure that the... | [
{
"name": "number",
"desc": "Identifier of the IP-CAN value used for your operating environment and access network. Default: 77"
}
] | 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... |
ip-in-udp | ip-in-udp {
teredo;
} | [edit security screen ids-option ids-option-name ip tunnel] | Configure IP tunnel IPinUDP IDS option. | [
{
"name": "teredo",
"desc": "Enable IP tunnel IPinUDP Teredo IDS option."
}
] | 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-D10. | [
"Attack Detection and Prevention Overview"
] |
ip-monitoring (Services) | ip-monitoring {
policy policy-name {
match {
rpm-probe [probe-name];
}
no-preempt ;
then {
interface interface-name (disable | enable);
preferred-route {
withdraw;
route destination-address {
dir... | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "withdraw",
"desc": "Remove the primary routes when RPM fails to probe the destination. So, the traffic can choose"
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support added for the discard option starting from Junos OS Release 15.1X49-D60.
Support added for the withdraw option starting from Junos OS Release 20.3R1.
direct-next-hop is introduced in Junos OS Release 20.4R1. | [] |
ip-monitoring | ip-monitoring {
family {
inet {
ipv4-address {
interface {
logical-interface-name;
secondary-ip-address ip-address;
}
weight number;
}
}
}
global-threshold number;
global-weigh... | [edit chassis cluster redundancy-group group-number] | Specify a global IP address monitoring threshold and weight, and the interval between pings (retry-
interval) and the number of consecutive ping failures (retry-count) permitted before an IP address is
considered unreachable for all IP addresses monitored by the redundancy group. Also specify IP
addresses, a monitoring... | [
{
"name": "IPv4 address",
"desc": "The address to be continually monitored for reachability. You also set up a secondary IP address to allow testing from the secondary node. NOTE: All monitored object failures, including IP monitoring, are deducted from the redundancy group threshold priority. Other monitor... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement updated in Junos OS Release 10.1. | [
"Example: Configuring Chassis Cluster Redundancy Group IP Address Monitoring"
] |
ip-options-protocol-queue | ip-options-protocol-queue protocol-name {
protocol-id protocol-id;
queue-depth queue-depth;
} | [edit forwarding-options] | Configure logical queue-depth in the PFE for ip-options packets for a given protocol such as TCP, UDP,
ICMP, and so on, except IGMP. The queue-depth indicates the number of ip-options packets that can be
enqueued in the PFE logical queue, beyond which it will start dropping the packets. Currently, IGMP has
a default qu... | [
{
"name": "protocol-id protocol-id",
"desc": "Identify the protocol. Range: 1 through 254"
},
{
"name": "queue-depth queue-depth",
"desc": "Size of the protocol logical options queue for a given protocol. Range: 1 through 807 packets"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [] |
ip-prefix-routes | ip-prefix-routes {
advertise (direct-nexthop | gateway-address);
donot-advertise-community;
encapsulation (mpls | srv6 | vxlan);
export routing-policy-name;
gateway-interface interface-name;
import routing-policy-name;
reject-asymmetric-vni;
route-attributes {
as-path {
... | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
evpn],
[edit routing-instances routing-instance-name protocols evpn] | In an Ethernet VPN (EVPN) environment, enable the device to advertise the IP prefix associated with a
specified customer domain as a Type 5 route to remote data centers. You might also enable IP prefix
routes in a metro transport network. You use this feature when the Layer 2 domain does not exist at the
remote data ce... | [
{
"name": "advertise direct-nexthop",
"desc": "Enable the switch to send IP prefix information using an EVPN pure Type 5 route, which includes a router MAC extended community used to send the MAC address of the switch. This router MAC extended community provides next-hop reachability without requiring an ov... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D60 and Junos OS Release 17.2R1.
Support for logical systems on MX Series routers added in Junos OS Release 17.4R1.
reject-asymmetric-vni option introduced in Junos OS Release 22.2R1 and Junos OS Evolved Release
22.1R1
Support for SRX and vSRX Virtual Firewall Series fir... | [
"Understanding EVPN Pure Type-5 Routes",
"EVPN Type 2 and Type 5 Route Coexistence with EVPN-VXLAN",
"EVPN Type 5 Route with VXLAN Encapsulation for EVPN-VXLAN",
"EVPN Overview for Switches",
"policy-statement"
] |
ip-prefix-support | ip-prefix-support {
encapsulation vxlan;
<export routing-policy-name>;
forwarding-mode symmetric;
vni number;
} | [edit routing-instances routing-instance-name protocols evpn] | In an Ethernet VPN (EVPN) Virtual Extensible LAN (VXLAN) environment, enable the provider edge (PE)
switch to forward the IP prefix associated with a specified customer domain in scenarios where the
Layer 2 domain does not extend across data centers. Such routes are referred to as EVPN pure type-5
routes. On QFX switch... | [
{
"name": "encapsulation",
"desc": ""
},
{
"name": "vxlan",
"desc": "Specify to encapsulate forwarded traffic in VXLAN for transmission to the other data center."
},
{
"name": "export routing-policy-name",
"desc": "(Optional) Specify the name of the routing policy configured at the [... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1x53-D30. | [
"Understanding EVPN Pure Type-5 Routes",
"policy-statement"
] |
ip-protocol-mapping (Application Identification) | ip-protocol-mapping {
order order;
order-priority (high | low);
protocol (http | ssl | tcp | udp)
} | [edit services application-identification application application-name] | For IP traffic, identify an application by matching the IP protocol. This parameter is used to identify an
application based on IP and is intended only for IP traffic. | [
{
"name": "protocol-number",
"desc": "Industry-standard numeric protocol value. Range: 0 through 254 You can find a complete list of industry standard protocol numbers at the IANA website. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement ... | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
ip-query (Identity Management Advanced Query) | ip-query {
no-ip-query;
query-delay-time seconds;
} | [edit services user-identification identity-management] | Configure the parameters to be used for the IP query function. When this feature is enabled, the SRX
Series Firewall queries the Juniper Identity Management Service (JIMS) server for user identity
information based on the IP address of a user’s device.
For example, if information for a user is missing from a flow, the ... | [
{
"name": "no-ip-query",
"desc": "Disable IP query. IP query is enabled by default."
},
{
"name": "query-delay-time",
"desc": "Time after which the SRX Series Firewall sends the query. Rather than allow the SRX Series Firewall to respond automatically by sending a user query immediately, you can... | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D100. | [
"Understanding Advanced Query Feature for Obtaining User Identity Information from JIMS"
] |
ip-reassembly (L2TP) | ip-reassembly {
service-set service-set-name;
} | [edit services l2tp] | Associate the reassembly service-set with the L2TP service.
NOTE: The service set must be defined at the [edit services] hierarchy level. | [
{
"name": "service-set service-set-name",
"desc": "Identifies the service set to be associated with the L2TP service."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"IP Packet Fragment Reassembly for L2TP Overview",
"Configuring IP Inline Reassembly for L2TP"
] |
ip-reassembly | ip-reassembly {
profile profile-name
rule rule-name{
match-direction direction
};
} | [edit services] | Configure the IP reassembly parameters to be applied to the L2TP server.
NOTE: Inline IP reassembly configuration does not require you to configure the profile
statement. The profile configuration is used when IP reassembly is configured on
services PICs. | [
{
"name": "profile profile-name",
"desc": "Name of the IP reassembly 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 13.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring IP Inline Reassembly for L2TP",
"IP Packet Fragment Reassembly for L2TP Overview"
] |
ip-reassembly-rules (Service Set) | ip-reassembly-rules rule-name; | [edit services service-setservice-set-name] | Specify one or more previously configured IP reassembly rules to associate with the service set.
NOTE: The IP reassembly rule must be defined at the [edit services ip-reassembly rule]
hierarchy level. | [
{
"name": "rule-name",
"desc": "Name of an IP reassembly 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.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring IP Inline Reassembly for L2TP",
"IP Packet Fragment Reassembly for L2TP Overview"
] |
ip-source-guard (MX Series) | ip-source-guard; | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] | Perform IP source guard checking on packets sent from access interfaces. Validate source IP addresses
and source MAC addresses on all bridge domains or on the specified bridge domain or bridge domain
range. Forward packets with valid addresses and drop those with invalid addresses.
•
ip-source-guard—Enable IP source gu... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Hierarchy level [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] introduced in Junos
OS Release 14.1 for the MX Series. | [
"Configuring IP Source Guard (non-ELS)",
"Example: Configuring IP Source Guard and Dynamic ARP Inspection on a Specified Bridge Domain to",
"Protect the Devices Against Attacks"
] |
ip-source-guard | ip-source-guard; | For platforms with ELS:
[edit vlans vlan-name forwarding-options dhcp-security]
For platforms without ELS:
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] | Perform IP source guard checking on packets sent from access interfaces. Validate source IP addresses
and source MAC addresses on all VLANs or on the specified VLAN or VLAN range. Forward packets
with valid addresses and drop those with invalid addresses.
•
ip-source-guard—Enable IP source guard checking.
•
no-ip-sourc... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Hierarchy level [edit vlans vlan-name forwarding-options dhcp-security] introduced in Junos OS Release
13.2X50-D10. (See Using the Enhanced Layer 2 Software CLI for information about ELS.) | [
"Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN",
"Example: Configuring IP Source Guard with Other EX Series Switch Features to Mitigate Address-",
"Spoofing Attacks on Untrusted Access Interfaces",
"Example: Configuring IP Source Guard and Dynamic ARP Inspectio... |
ip-subscriber | ip-subscriber {
access-interfaces interface-name [interface-name];
default-local-policy {
flow-action (drop | forward);
maximum-bit-rate {
uplink mbr-uplink-value ;
downlink mbr-downlink-value;
}
burst-size {
uplink uplink-burst-size;
... | [edit unified-edge gateways tdf gateway-name domains domain-name] | Configure TDF domain features that are unique to IP-based subscribers.
The remaining statements are described separately. | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a 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"
] |
ip-swap | ip-swap; | [edit services monitoring rfc2544 tests test-name test-name] | Swaps source and destination IPv4 addresses. This statement is applicable only for family bridge or
family ethernet-switching. | [] | 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"
] |
ip-sweep | ip-sweep {
threshold number;
} | [edit security screen ids-option screen-name icmp] | Configure the device to detect and prevent an IP Sweep attack. An IP Sweep attack occurs when an
attacker sends ICMP echo requests (pings) to multiple destination addresses. If a target host replies, the
reply reveals the target’s IP address to the attacker. If the device receives 10 ICMP echo requests within
the numbe... | [
{
"name": "threshold number",
"desc": "Maximum number of microseconds during which up to 10 ICMP echo requests from the"
}
] | 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. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
ip-tunnel-rpf-check | ip-tunnel-rpf-check {
mode (strict | loose);
fail-filter filter-name;
} | [edit routing-instances routing-instance-name routing-options forwarding-table] | Configure the system to enable anti-spoofing protection for next-hop-based dynamic tunnels, where
reverse path forwarding checks are placed to ensure that the tunnel traffic is received from a legitimate
source through designated IP tunnel, where the source is reachable on the same tunnel on which the
packet was receiv... | [
{
"name": "mode",
"desc": ""
},
{
"name": "(strict |",
"desc": ""
},
{
"name": "loose)",
"desc": "(Optional) Specify the mode of the reverse path forwarding check to enable anti-spoofing protection for next-hop-based dynamic tunnels. In the strict mode (default), the reverse path for... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Anti-Spoofing Protection for Next-Hop-Based Dynamic Tunnels Overview",
"Example: Configuring Anti-Spoofing Protection for Next-Hop-Based Dynamic Tunnels"
] |
ip-user-mapping | ip-user-mapping {
discovery-method {
wmi {
event-log-scanning-interval seconds;
initial-event-log-timespan hours;
}
}
} | [edit services user-identification active-directory domain] | Control how the SRX Series Firewall accesses a domain controller in order to monitor and scan security
event logs on the domain controller. By parsing the event log, the SRX Series gets IP address-to-user
mappings. This process is part of the integrated user firewall feature. The ip-user-mapping statement is
optional b... | [
{
"name": "discovery-method",
"desc": "Method of discover IP address-to-user mappings."
},
{
"name": "wmi",
"desc": "Windows Management Instrumentation (WMI) is the discovery method used to access the domain controller."
},
{
"name": "event-log-scanning-",
"desc": ""
},
{
"na... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [] |
ip-version (Family MPLS) | ip-version {
ipv4;
ipv6;
} | [edit firewall family mpls filter name term name from] | Specify inner IP version to enable IP-based filtering of MPLS family filter.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"Understanding IP-Based Filtering and Selective Port Mirroring of MPLS Traffic"
] |
ip-version | ip-version ip-version {
match-conditions;
protocol (tcp | udp) {
match conditions;
}
} | [edit firewall family family-name filter filter-name term term-name from] | Configure the IP version for the firewall filter. | [
{
"name": "ip-version",
"desc": "Version of the IP addressing."
},
{
"name": "ipv4",
"desc": "IP version 4"
},
{
"name": "ipv6",
"desc": "IP version 6"
}
] | 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.
Option ipv6 introduced in Junos OS Release 12.2R1.
Statement became independent and can stand alone starting in Junos OS Release 25.2R1. In releases
prior to that, this statement was incomplete by itself and required accompanying qualifiers such as
match-conditions. | [
"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"
] |
ipc | ipc {
traceoptions flag flag;
} | [edit security utm default-configuration]
[edit security utm] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "flag",
"desc": "Trace operation to perform. To specify more than one trace operation, include multiple flag"
},
{
"name": "all",
"desc": "Enable trace for all IPC trace options."
},
{
"name": "basic",
"desc": "Trace basic IPC related information."
},
{
"name": "con... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
ipcp-suggest-dns-option | ipcp-suggest-dns-option; | [edit access group-profile group-profile-name ppp ppp-options],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit ppp-options],
[edit interfaces pp0 unit logical-unit-number ppp... | Configure the router to prompt Customer Premises Equipment (CPE) to negotiate both primary and
secondary DNS addresses during IPCP negotiation for terminated PPPoE and LNS subscribers. You can
configure this for dynamic or static PPPoE subscribers, dynamic or static LNS subscribers, and in an LNS
group profile. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Ensuring IPCP Negotiation for Primary and Secondary DNS Addresses",
"Configuring the PPP Attributes for a Group Profile",
"Applying PPP Attributes to L2TP LNS Subscribers with a User Group Profile",
"Configuring Dynamic Authentication for PPP Subscribers",
"Applying PPP Attributes to L2TP LNS Subscribers p... |
ipfix-sw-mode | ipfix-sw-mode; | [edit system packet-forwarding-options] | (QFX5120 only) Enable software-based IPFIX, used to enable flow-based telemetry for VXLANs. You
must reboot the device after you commit this statement to the configuration. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [
"Flow-Based Telemetry for VXLANs"
] |
ipip (Ids-option) | ipip {
ipip-4in4;
ipip-4in6;
ipip-6in4;
ipip-6in6;
ipip-6over4;
ipip-6to4relay;
isatap;
dslite;
} | [edit security screen ids-option ids-option-name ip tunnel] | Configure IP tunnel IP-IP IDS options. | [
{
"name": "dslite",
"desc": "Enable IP tunnel IP-IP DS-Lite IDS option."
},
{
"name": "ipip-4in4",
"desc": "Enable IP tunnel IP-IP 4in4 IDS option."
},
{
"name": "ipip-4in6",
"desc": "Enable IP tunnel IP-IP 4in6 IDS option."
},
{
"name": "ipip-6in4",
"desc": "Enable IP tu... | 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-D10. | [
"Attack Detection and Prevention Overview"
] |
ipip | ipip {
destination {
address address;
}
source {
address address;
}
} | [edit dynamic-profiles name interfaces name unit name tunnel encapsulation
(interfaces-fti)],
[edit dynamic-profiles name logical-systems name interfaces name unit name tunnel encapsulation
(interfaces-fti)],
[edit interfaces name unit name tunnel encapsulation
(interfaces-fti)] | Configure IP-in-IP tunnel.
The remaining statements are explained separately. See CLI Explorer. | [] | interface | Statement introduced in Junos OS Release 20.3R1. | [] |
ips | ips {
content-decompression-max-memory-kb content-decompression-max-memory-kb;
content-decompression-max-ratio content-decompression-max-ratio;
(detect-shellcode | no-detect-shellcode);
fifo-max-size fifo-max-size;
(ignore-regular-expressionignore-regular-expression | no-ignore-regular-expression);
... | [edit security idp sensor-configuration] | Configure IPS security policy sensor settings. The IPS sensor contains filters, signature entries, or both.
These specify which signatures are included in the IPS sensor. You need to create an IPS sensor before
specific signatures or filters can be chosen. The signatures can be added to a new sensor before it is
saved.... | [
{
"name": "content-decompression-max-",
"desc": ""
},
{
"name": "memory-kb",
"desc": "Set the maximum memory allocation in kilobytes for content decompression. The default memory allocation provides 33 KB per session for an average number of sessions requiring decompression at the same time. To ... | 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. | [
"IDP Sensor Configuration"
] |
ipsec (High Availability) | ipsec {
vpn vpn-name {
ha-link-encryption;
ike {
gateway gateway-name;
ipsec-policy ipsec-policy-name;
}
}
proposal proposal-name {
description description;
encryption-algorithm (aes-256-gcm);
lifetime-seconds seconds;
protoc... | [edit security] | Define IPsec configuration for the multinode high availability feature. A VPN connection can link two
LANs (site-to-site VPN) or a remote dial-up user and a LAN. The traffic that flows between these two
points passes through shared resources such as routers, switches, and other network equipment that
make up the public... | [
{
"name": "vpn-name",
"desc": "Configure an IPsec VPN. A VPN provides a means by which remote computers communicate securely across a public WAN such as the Internet. You must mention the same VPN name for vpn-profile in set chassis high-availability peer-id peer-id vpn-profile profile-name configuration."
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"High-Availability (Chassis)",
"Multinode High Availability",
"services-redundancy-group",
"local-id",
"peer-id",
"traceoptions"
] |
ipsec (Security Group VPN Member) | ipsec {
vpn vpn-name {
df-bit (clear | copy | set);
exclude rule rule-name {
source-address ip-address/mask;
destination-address ip-address/mask;
application application;
}
fail-open rule rule-name {
source-address ip-address/mask;
... | [edit security group-vpn member] | Configure IPsec for Phase 2 exchange on the group member. Group VPNv2 is supported on SRX300,
SRX320, SRX340, SRX345, SRX550HM, SRX1500, SRX4100, SRX4200, and SRX4600 devices and
vSRX Virtual Firewall instances. | [
{
"name": "vpn vpn-name",
"desc": "Name of the VPN."
},
{
"name": "df-bit",
"desc": "Specifies pre-fragmentation and post-fragmentation of IPsec traffic on the group member. One of the following options can be configured:"
},
{
"name": "clear",
"desc": "Sets the outer IP do not fragm... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. df-bit, exclude rule, fail-open rule, and recovery-probe
options added in Junos OS Release 15.1X49-D30 for vSRX Virtual Firewall. | [
"Group VPNv2 Overview"
] |
ipsec (Security Group VPN Server) | ipsec {
proposal proposal-name {
authentication-algorithm (hmac-sha-256-128);
description description;
encryption-algorithm (aes-128-cbc | aes-192-cbc | aes-256-cbc);
lifetime-seconds seconds;
}
} | [edit security group-vpn server] | Configure IPsec proposal for Phase 2 exchange on the group server. Group VPNv2 is supported on
SRX300, SRX320, SRX340, SRX345, SRX550HM, SRX1500, SRX4100, SRX4200, and SRX4600 devices
and vSRX Virtual Firewall instances. | [
{
"name": "proposal proposal-name",
"desc": "Name of the proposal. The proposal name can be up to 32 alphanumeric"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Group VPNv2 Overview"
] |
ipsec (Security Interfaces) | ipsec {
security-association {
manual {
direction (bidirectional | inbound | outbound) {
protocol esp;
spi spi-value;
encryption {
algorithm 3des-cbc;
key (ascii-text ascii-text-string | hexadecimal hexadec... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Security Associations for IPsec on an ES PIC"
] |
ipsec (Security) | ipsec {
anti-replay-window-size anti-replay-window-size;
hw-offload-disable;
internal;
policy;
proposal
security-association sa-name;
traceoptions;
vpn vpn-name {
bind-interface bind-interface;
}
vpn-monitor-options {
interval seconds;
threshold number; ... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "anti-replay-window-size",
"desc": "Anti-replay window size. Range: 64 through 8192 bytes Default: 64 bytes"
},
{
"name": "hw-offload-disable",
"desc": "Disable hardware offloading of IPsec tunnel processing in the Packet Forwarding Engine ASIC for all VPN tunnels."
},
{
"nam... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | hw-offload-disable option added in Junos OS Release 25.2R1.
group15, group16, group21, hmac-sha-512 and hmac-sha-384 options introduced in Junos OS Release 19.1R1 on
SRX Series Firewalls.
Statement modified in Junos OS Release 8.5. | [
"IPsec Overview"
] |
ipsec | ipsec {
proposal proposal-name {
authentication-algorithm (hmac-sha-256);
description description;
encryption-algorithm algorithm;
lifetime-seconds seconds;
protocol (esp | bundle);
}
policy policy-name {
description description;
perfect-forward-secrec... | [edit services ipsec-vpn] | Configure IPsec.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Security Associations"
] |
ipsec-group-vpn (Security Policies) | ipsec-group-vpn group-vpn; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
tunnel] | Specify group VPN tunnel for the traffic configured by the scope policy on a group member. | [
{
"name": "group-vpn",
"desc": "Name of the group VPN tunnel configured on the group member."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Security Policies Overview",
"Group VPNv2 Overview",
"Security Basics Overview"
] |
ipsec-inside-interface | ipsec-inside-interface interface-name; | [edit services ipsec-vpn rule rule-name term term-name from] | Specify the interface name for next-hop-style service sets. This value is also implicitly generated in
dynamic endpoint tunneling. | [
{
"name": "interface-name",
"desc": "Service interface for internal network."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring IPsec Rules",
"Configuring Dynamic Endpoints for IPsec Tunnels"
] |
ipsec-policy | ipsec-policy from-zone zone-name to-zone zone-name ipsec-group-vpn vpn-name; | [edit security] | Specifies that matching traffic is checked against rules associated with the specified Group VPN. Exclude
and fail-open rules are configured at the [edit security group-vpn member ipsec vpn vpn-name] hierarchy level. | [
{
"name": "from-zone zone-name",
"desc": "Specify the incoming zone for Group VPN traffic."
},
{
"name": "to-zone zone-name",
"desc": "Specify the outgoing zone for Group VPN traffic. The to-zone zone must include the interface configured with the group-vpn-external-interface option at the [edit... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D30. | [
"Group VPNv2 Overview"
] |
ipsec-sa (Protocols BGP) | ipsec-sa ipsec-sa; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Specify a security association to BGP peers. You can apply the security association globally for all BGP
peers, to a group of peers, or to an individual peer. | [
{
"name": "ipsec-sa",
"desc": "Security association name."
}
] | 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: Using IPsec to Protect BGP Traffic"
] |
ipsec-sa (Security Group VPN) | ipsec-sa name {
match-policy policy-name {
destination ip-address/netmask;
destination-port number;
protocol number;
source ip-address/netmask;
source-port number;
}
proposal proposal-name;
} | [edit security group-vpn server group name] | Configure the group SAs to be downloaded to members. There can be multiple group SAs downloaded
to group members. | [
{
"name": "ipsec-sa name",
"desc": "Define the group SAs to be downloaded to members."
},
{
"name": "match-policy policy-name",
"desc": "Configure the group policy with source address, source port, destination"
},
{
"name": "destination ip-address/netmask",
"desc": "Specify the desti... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Group VPNv2 Overview"
] |
ipsec-sa | ipsec-sa sa-name; | [edit interfaces es-fpc/pic/port unit logical-unit-number family inet] | Specify the IP Security (IPsec) SA name associated with the interface. | [
{
"name": "sa-name",
"desc": "IPsec SA name."
}
] | 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 Encryption Interfaces",
"Junos OS Administration Library for Routing Devices"
] |
ipsec-traffic-selector | ipsec-traffic-selector preference pref-value; | [edit protocols] | Configure the global preference value for the ARI-TS (Auto route insertion for traffic selectors) routes
added when a IPsec traffic selector based IPsec VPN has been established.
A new category ipsec-traffic-selector for Auto route insertion traffic selectors (ARI-TS) route is added in
[edit protocols] hierarchy for se... | [
{
"name": "preference pref-value",
"desc": "Specify the preferential selection of routes for the same remote IP address or prefix added by different protocols (static, BGP, OSPF, and so on). Range: 1-4294967295. Default: 5."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.