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 |
|---|---|---|---|---|---|---|---|
icmp-code (Applications) | icmp-code value; | [edit applications application application-name ]
[edit applications application application-name term term-name] | Specify the Internet Control Message Protocol (ICMP) code value. | [
{
"name": "value",
"desc": "Specify the Internet Control Message Protocol (ICMP) code value such as host-unreachable or host-unreachable-for-tos."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. | [
"Security Policy Application Sets Overview"
] |
icmp-code | icmp-code value; | [edit applications application application-name] | Internet Control Message Protocol (ICMP) code value. | [
{
"name": "value",
"desc": "The ICMP code value. For a complete list, see Configuring the ICMP Code and Type."
}
] | 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. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring the ICMP Code and Type",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
icmp-fragment-check (IDS MS-MPC) | icmp-fragment-check; | [edit services ids rule rule-name term term-name then] | Identify and drop ICMP packets that are IP fragments. This statement can only be used in IDS rules
assigned to a service set on an MS-MPC. | [] | 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 Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
icmp-large-packet-check (IDS MS-MPC) | icmp-large-packet-check; | [edit services ids rule rule-name term term-name then] | Identify and drop ICMP packets that are larger than 1024. This statement can only be used in IDS rules
assigned to a service set on an MS-MPC. | [] | 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 Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
icmp-mapping (Application Identification) | icmp-mapping {
code icmp-code;
order order;
order-priority (high | low);
type icmp-type;
} | [edit services application-identification application application-name] | Match Internet Control Message Protocol (ICMP) messages identified by unique code and type. This
classification is intended to identify and differentiate various types of ICMP messages.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax se... | [] | 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"
] |
icmp-type (Applications) | icmp-type value; | [edit applications application application-name ]
[edit applications application application-name term term-name] | Specify the ICMP packet type value. | [
{
"name": "value",
"desc": "ICMP type value, such as echo or echo-reply."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. | [
"Security Policy Application Sets Overview"
] |
icmp-type | icmp-type value; | [edit applications application application-name] | ICMP packet type value. | [
{
"name": "value",
"desc": "The ICMP type value, such as echo or echo-reply. For a complete list, see Configuring the ICMP"
}
] | 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. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring the ICMP Code and Type",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
icmpv6 (Security IDP Custom Attack) | icmpv6 {
checksum-validate {
match (equal | greater-than | less-than | not-equal);
value checksum-value;
}
code {
match (equal | greater-than | less-than | not-equal);
value code-value;
}
data-length {
match (equal | greater-than | less-than | not-equal);
... | [edit security idp custom-attack attack-name attack-type signature protocol] | Allow IDP to match the attack for the specified ICMPv6. | [] | 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. | [] |
icmpv6 (Security IDP) | icmpv6; | [edit security idp custom-attack attack-name attack-type chain protocol-binding]
[edit security idp custom-attack attack-name attack-type signature protocol-binding] | Specify that the attack is for ICMPv6 packets only. | [] | 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. | [] |
icmpv6-malformed (IDS Screen Next Gen Services) | icmpv6-malformed; | [edit services screen ids-option screen-name icmp] | Identify and drop malformed ICMPv6 packets, which might cause damage to the device and network.
Examples of malformed IPv6 packets are packets that are too big (message type 2), that have the next
header set to routing (43), or that have a routing header set to hop-by hop. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
icmpv6-malformed | icmpv6-malformed; | [edit security screen ids-option screen-name icmp] | Enable the ICMPv6 malformed intrusion detection service (IDS) option. | [] | 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"
] |
id (MACsec for MX Series) | id {
mac-address mac-address;
port-id port-id-number;
} | [edit security macsec connectivity-association connectivity-association-name secure-channel
secure-channel-name] | Specify a MAC address and a port that traffic on the link must be from to be accepted by the interface
when MACsec is enabled using static secure association key (SAK) security mode. | [] | 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. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
id (Protocols OpenFlow) | id id; | [edit protocols openflow switch switch-name controller] | Specify an optional numeric identifier for the OpenFlow controller. | [
{
"name": "id",
"desc": "Numeric identifier for the OpenFlow controller."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Understanding Support for OpenFlow on Devices Running Junos OS"
] |
id | id id; | [edit virtual-chassis] | Configure the alphanumeric string that identifies a Virtual Chassis or Virtual Chassis Fabric (VCF)
configuration. | [
{
"name": "id",
"desc": "Virtual Chassis ID (VCID), which uses the ISO family address format—for example, 9622.6ac8.5345."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Example: Assigning the Virtual Chassis ID to Determine Precedence During an EX4200 Virtual",
"Chassis Merge",
"Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge",
"Configuring an EX4650 or a QFX Series Virtual Chassis",
"Autoprovisioning a Virtual Chassis Fabric",
"P... |
id-components | id-components {
use-class;
use-imsi;
use-msisdn;
use-nai;
use-nas-port;
use-nas-port-id;
use-realm;
use-username;
} | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber subscription-id
subscription-id-options entry-name] | Specify a method for constructing the Subscription-Id for the Diameter credit control request (CCR)
message that is sent from the TDF to the PCRF for IP-based subscribers belonging to the TDF domain.
You may specify more than one option, and the order of preference matches the order in which the
options appear. | [
{
"name": "use-class",
"desc": "Subscription-Id-Type is configurable and the Subscription-Id-Data is the entire Class attribute value by default. You can configure a regular expression to parse the Class attribute contents, specify characters to insert between the resulting regular expression groups, and sp... | 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"
] |
identification (Security ICMP Headers) | identification {
match (equal | greater-than | less-than | not-equal);
value identification-value;
} | [edit security idp custom-attack attack-name attack-type signature protocol icmp],
[edit security idp custom-attack attack-name attack-type signature protocol icmpv6] | Specify a unique value used by the destination system to associate requests and replies. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value identification-value",
"desc": "Match a decimal value."
}
] | 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. Statement modified in Junos OS Release 12.3X48-D25
to add ICMPv6 protocol support. | [] |
identification (Tunnel Profile) | identification name; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify the assignment ID of an L2TP tunnel. L2TP sessions with the same tunnel assignment
identification and destination are grouped into the same tunnel. | [
{
"name": "name",
"desc": "Tunnel assignment ID; string of up to 32 alphanumeric characters."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
identifier (VPLS Multihoming for FEC 129) | identifier identifier; | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing site site-name],
[edit routing-instances instance-name protocols vpls multi-homing site site-name] | Configure a Layer 2 VPN or VPLS multihoming identifier (MHID). An identifier needs to be configured
for each multihomed site. Multihoming site identifiers are specific to a VPLS domain. They need not be
unique on a provider edge (PE) router when multiple VPLS instances are present. The network layer
reachability inform... | [
{
"name": "identifier",
"desc": "Number that identifies the multihomed site. Range: 1 through 65535"
}
] | 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. | [
"Example: Configuring VPLS Multihoming (FEC 129)"
] |
identity | identity identity-name; | [edit security ike] | Define the identity of the remote certificate name if the identity cannot be learned through IKE (ID
payload or IP address). | [] | 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 an IKE Policy for Digital Certificates for an ES PIC"
] |
identity-context-profile | identity-context-profile profile-name profile-name {
domain-name domain-name {
attribute device-category {
string string-value;
}
attribute device-identity {
string string-value;
}
attribute device-os {
... | [edit services user-identification device-information] | Specify the name of the device identity profile, also referred to as the identity-context-profile, and either
one or more of its attributes or the name of the Active Directory domain to which the device belongs.
The device identity profile is a key component of the SRX Series firewall identity feature, which enables
yo... | [
{
"name": "profile-name profile-name",
"desc": "Name of the device identity profile; for example, marketing-west-coast. The profile is specified in the destination-identity-context-profile field of a security policy."
},
{
"name": "domain domain-name",
"desc": "Name of the domain to which the de... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
identity-management | identity-management {
authentication-entry-timeout minutes;
batch-query {
items-per-batch items-per-batch;
query-interval seconds;
}
connection {
connect-method (http | https);
port port;
primary {
address address;
ca-profile ca-profile;
... | [edit services user-identification] | 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": "authentication-entry-timeout",
"desc": "Authentication entry timeout number (0, 10-1440) (minutes) Default: 60"
},
{
"name": "invalid-authentication-entry-timeout",
"desc": "Invalid authentication entry timeout number (0, 10-1440) (minutes) Default: 30"
},
{
"name": "file",
... | system | Statement introduced in Junos OS Release 15.1X49-D100. | [
"Configure Juniper Identity Management Service to Obtain User Identity Information"
] |
identity-provider (SAML) | identity-provider identity-provider {
attribute-mapping {
address-pool assertion-attribute <mandatory | optional>;
firstname assertion-attribute <mandatory | optional>;
group assertion-attribute <mandatory | optional>;
lastname assertion-attribute <mandatory | optional>;
attr... | [edit access saml] | Describe Security Assertion Markup Language (SAML) identity provider (IdP) configuration details. You
can describe more than one identity providers. | [
{
"name": "identity-provider",
"desc": "Specify an IdP name."
},
{
"name": "attribute-mapping",
"desc": "Set the attribute mapping details for identity provider (IdP)."
},
{
"name": "metadata-id",
"desc": ""
},
{
"name": "metadata-id",
"desc": "Set the IdP configuration f... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
identity-provider attribute-mapping (SAML) | attribute-mapping {
address-pool assertion-attribute <mandatory | optional>;
firstname assertion-attribute <mandatory | optional>;
group assertion-attribute <mandatory | optional>;
lastname assertion-attribute <mandatory | optional>;
attribute-name assertion-attribute <mandatory | optional>;
use... | [edit access saml identity-provider identity-provider] | Map assertion response attributes to local attributes. | [
{
"name": "address-pool assertion-attribute",
"desc": "Specify the name of the address pool."
},
{
"name": "mandatory (default)",
"desc": ""
},
{
"name": "optional",
"desc": ""
},
{
"name": "firstname assertion-attribute",
"desc": "Specify the user's firstname."
},
{
... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
identity-provider settings (SAML) | settings {
entity-id entity-id;
idp-certificate idp-certificate;
single-logout-url single-logout-url;
single-signon-url single-signon-url;
} | [edit access saml identity-provider name] | Describe Security Assertion Markup Language (SAML) identity provider (IdP) settings. If you import IdP
metadata, you do not need to manually configure IdP settings. | [
{
"name": "entity-id entity-id",
"desc": "Specify IdP entity id. Example: http://www.example.com/1123zweqios."
},
{
"name": "idp-certificate idp-certificate",
"desc": "Specify the IdP's certificate."
},
{
"name": "single-logout-url single-logout-url",
"desc": "Specify the IdP's singl... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
idle-after-switch-over | idle-after-switch-over (forever | seconds); | [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 protocols bgp],
[edit protocols bgp group group-name],
[edit protocols bgp group group-na... | Configure the routing device so that it does not automatically reestablish BGP peer sessions after a
nonstop active routing (NSR) switchover. This feature is particularly useful if you are using dynamic
routing policies because the dynamic database is not synchronized with the backup Routing Engine
when NSR is enabled. | [
{
"name": "forever",
"desc": "Do not reestablish a BGP peer session after an non-stop routing switchover until the clear bgp"
},
{
"name": "seconds",
"desc": "Do not reestablish a BGP peer session after an non-stop routing switchover until after the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Preventing Automatic Reestablishment of BGP Peer Sessions After NSR Switchovers",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide",
"Junos OS High Availability User Guide"
] |
idle-standby-path-switchover-delay | idle-standby-path-switchover-delay <seconds>; | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Configure the time interval after which an ECMP join is moved to the standby path in the absence of
traffic on the path.
In the absence of this statement, ECMP joins are not moved to the standby path until traffic is detected
on the path. | [
{
"name": "<seconds>",
"desc": "Time interval after which an ECMP join is moved to the standby RPF path in the absence of traffic on the path."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring PIM Make-Before-Break Join Load Balancing",
"Configuring PIM Join Load Balancing"
] |
idle-timeout (Access) | idle-timeout seconds; | [edit access group-profile profile-name ppp ppp],
[edit access profile profile-name client client-name ppp] | Configure the idle timeout for a user. The router might consider a PPP session to be idle because of the
following reasons:
•
There is no ingress traffic on the PPP session.
•
There is no egress traffic.
•
There is neither ingress or egress traffic on the PPP session.
•
There is no ingress or egress PPP control traffic... | [
{
"name": "seconds",
"desc": "Number of seconds a user can remain idle before the session is terminated."
}
] | 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. | [
"Point-to-Point Protocol (PPP)",
"L2TP LNS Inline Service Interfaces"
] |
idle-timeout (L2TP) | idle-timeout seconds; | [edit services l2tp tunnel] | Specify how long a tunnel is active after its last session is terminated. The timer starts when the session
is terminated and the tunnel is disconnected when the timer expires.
BEST PRACTICE: Before you downgrade to a Junos OS Release that does not support
this statement, unconfigure the statement by issuing no service... | [
{
"name": "seconds",
"desc": "Length of the idle timeout. A value of 0 creates a persistent tunnel; that is, the tunnel remains"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"L2TP Tunnel Switching For Multiple-Domain Networks",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces"
] |
idle-timeout (System Services) | idle-timeout; | [edit system services web-management session] | Configure in minutes the idle-timeout parameter for web-management sessions. The idle-timeout
parameter, which applies to all sessions, specifies the length of time a session can be idle before it is
terminated. The web-management feature allows you to configure the device using the J-Web interface.
You can also config... | [
{
"name": "idle-timeout",
"desc": ""
},
{
"name": "minutes",
"desc": "Default: 30 Range: 1 to 1440"
}
] | system—To view this in the configuration.
system-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Firewall User Authentication Overview",
"Dynamic VPN Overview"
] |
idle-timeout (System) | idle-timeout idle-timeout; | For root users:
[edit system login]
For non-root users:
[edit system login class] | Configure the maximum time for which the C shell or CLI session can be idle. The root user is logged out
of the CLI session after the expiry of idle-timeout and is logged out of the C shell after the expiry of
another idle-timeout. For instance, if you configure idle-timeout as 5 minutes, the root user is logged out of... | [
{
"name": "idle-timeout",
"desc": "Maximum idle time for root users before logout. Range: 1 through 60 minutes NOTE: Although you can set the idle-timeout to 1 minute, it is recommended to set it to 2 minutes or more for proper operation. Maximum idle time out for non-root users before logout. Range: Any ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [] |
idle-timeout (Unified Edge) | idle-timeout idle-timeout; | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber] | Configure the idle timeout for the TDF IP-based subscriber session. The idle timeout is the duration that
the subscriber session waits to receive a data packet before timing out. After the idle timeout expires,
the TDF takes down the session. Setting the idle timeout ensures that if no data is being sent for the
durati... | [
{
"name": "idle-timeout",
"desc": "Number of minutes after which the TDF subscriber session times out. Range: 0 through 300."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
idle-timeout | idle-timeout seconds; | [edit services application-identification application application-name] | Define idle timeout for an application in seconds. When the timeout period expires, the session ends if
no packets have been received. | [
{
"name": "seconds",
"desc": "Idle timeout period."
}
] | 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. | [
"APPID Overview",
"Defining an Application Identification"
] |
idle-timeout | idle-timeout seconds; | [edit interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with ISDN interfaces, configure the number of seconds the link is idle
before losing connectivity. | [
{
"name": "seconds",
"desc": "Time for which the connection can remain idle. For interfaces configured to use a filter for"
}
] | 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. | [] |
idp (Application Services) | idp; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services] | Configure Intrusion Detection and Prevention (IDP) for application services. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
idp (logical-systems) | idp (default | off | on); | [edit logical-systems name security] | Configure IDP on primary and user logical systems. | [
{
"name": "default-policy",
"desc": "Set the active policy."
},
{
"name": "max-sessions",
"desc": "Maximum number of IDP sessions."
}
] | security | Statement introduced in Junos OS Release 11.4 | [
"IDP for Logical Systems",
"IDP for Logical Systems"
] |
idp (Security Alarms) | idp; | [edit security alarms potential-violation] | Configure alarms for IDP (intrusion, detection, and prevention) attack. | [] | 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. | [] |
idp (Security) | idp {
active-policy policy-name;
custom-attack attack-name {
attack-type (Security IDP) {
anomaly {
direction (any | client-to-server | server-to-client);
service service-name;
shellcode (all | intel | no-shellcode | sparc);
tes... | [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... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.3. The expression option added in Junos OS Release 11.4.
Starting in Junos OS Release 18.3R1, when an SRX Series Firewall is configured with unified policies,
you can configure multiple IDP policies and set one of those policies as the default IDP policy. If multiple
IDP policie... | [
"Intrusion Detection and Prevention Overview"
] |
idp (SNMP) | idp {
falling-threshold percentage;
interval seconds;
rising-threshold percentage;
} | [edit snmp health-monitor] | Configure health monitoring for Intrusion Detection and Prevention (IDP). | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configure Health Monitoring on Devices Running Junos OS"
] |
idp-policy (Application Services) | idp-policy idp-policy; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services] | Specify IDP policy name.
When you configure a unified policy with a dynamic application as one of the matching condition, the
configuration eliminates the additional steps involved in IDP policy configuration. IDP policy
configurations are simplified within a unified policy. Configuring source or destination address, s... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1
Starting in Junos OS Release 18.2R1, IDP policy is available within unified security policy.
Unified policies are supported on SRX Series Firewalls, allowing granular control and enforcement of
Dynamic Layer Applications within the traditional Security Policy. Layer 7 dyn... | [] |
idp-policy (Security) | idp-policy policy-name {
rulebase-exempt {
rule rule-name {
description text;
match {
attacks {
custom-attack-groups [attack-group-name];
custom-attacks [attack-name];
dynamic-attack-groups [attack-group-name... | [edit security idp]
[edit tenants tenant-name security idp] | Configure a security IDP policy. | [
{
"name": "policy-name",
"desc": "Name of the IDP policy."
}
] | 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.
Starting with Junos OS Release 18.2R1, IDP policy is directly assigned in the security policy rule. This is
to simplify IDP policy usage and to provide flexibility to have multiple policies active at the same time.
As a part of the session interest check, IDP is enabled if ... | [] |
idp-policy | idp-policy idp-policy; | [edit system security-profile] | Specify the IDP policy for the security profile. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Intrusion Detection and Prevention Overview"
] |
ids-option | ids-option screen-name {
alarm-without-drop;
description text;
icmp {
flood {
threshold number;
}
fragment;
icmpv6-malformed;
ip-sweep {
threshold number;
}
large;
... | [edit security screen],
[edit tenants tenant-name security screen] | Define screens for the intrusion detection service (IDS). An ids-option can be used for enabling the
screen protection on the SRX Series Firewalls. One ids-option can be associated with several zones.
However each zone can be linked with only one ids-option. | [
{
"name": "description text",
"desc": "Descriptive text about a screen."
},
{
"name": "alarm-without-drop",
"desc": "Direct the device to generate an alarm when detecting an attack but not block the"
},
{
"name": "icmp",
"desc": "Configure the ICMP ids options."
},
{
"name": ... | 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 for the description option added in Junos OS Release 12.1.
UDP supports port-scan option starting from Junos OS Release 12.1X47-D10.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
ids-rule-sets | (ids-rule-sets rule-set-name); | [edit services service-set service-set-name] | Specify the intrusion detection service (IDS) rule set included in this service set. You can configure only
one rule set for each service. If the service set is on an MS-MPC, only the first IDS input rule and the
first IDS output rule are used. | [
{
"name": "rule-set-name",
"desc": "Identifier for the set of rules to be included."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Service Rules",
"Configuring Protection Against Network Attacks on an MS-MPC"
] |
ids-rules | ids-rules [rule-name]; | [edit services service-set service-set-name] | Specify the intrusion detection service (IDS) rules included in this service set. You can configure multiple
rules. If the service set is on an MS-MPC, only the first IDS input rule and the first IDS output rule are
used. | [
{
"name": "rule-name",
"desc": "Identifier for the rule to be included."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Service Rules",
"Configuring Protection Against Network Attacks on an MS-MPC"
] |
ie-set | ie-set name {
ie ie-number;
} | [edit security gtp] | Specify a GTP IE set profile. This helps you to remove IEs of specific types from all messages for GTPv1
and GTPv2.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp] hierarchy level is replaced by [edit
security gtp]. | [
{
"name": "name",
"desc": "Name of the GTP IE set profile."
},
{
"name": "ie-number",
"desc": "IE number. Range: 1 to 255"
}
] | security—To view this statement in the configuration. | Statement introduced in Junos OS Release 20.2R1. | [
"Example: Configure IE removal for GTPv1 and GTPv2"
] |
ieee802.1p | ieee802.1p premium [ values ]; | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
input-priority-map]
[edit interfaces interface-name ether-options ethernet-switch-profile ethernet-policer-profile input-
priority-map] | For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, configure premium priority values for
IEEE 802.1p input traffic. | [
{
"name": "values",
"desc": "Define IEEE 802.1p priority values to be treated as premium."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos Release 7.4. | [] |
ieee-802.1 (Class of Service) | Rewrite Rule Configuration
ieee-802.1 rewrite-name {
import (rewrite-name | default);
forwarding-class class-name {
loss-priority level {
code-point [ aliases ] [ bit-patterns ];
}
}
} | [edit class-of-service rewrite-rules] | Configure an IEEE 802.1 classifier, configure an IEEE 802.1 code-point alias, apply a fixed IEEE 802.1
classifier to an interface, or apply an IEEE-802.1 rewrite rule. | [
{
"name": "classifier-name",
"desc": "Name of the classifier."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Configuring Unicast Classifiers",
"Defining CoS Code-Point Aliases",
"Defining CoS Rewrite Rules",
"Assigning CoS Components to Interfaces",
"Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces",
"Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces",
"Unde... |
ieee-802.1 (Classifier on Physical Interface) | ieee-802.1 (classifier-name | default) vlan-tag (inner | outer ); | [edit class-of-service interfaces interface-name classifiers] | For ACX Series Universal Metro routers and EX Series switches, map the ieee-802.1p field of the
incoming packet to the forwarding class and packet loss priority based on the specified 802.1p classifier.
In the case of double tagged packets, you can configure whether to use the 802.1p of the outer or inner
VLAN tag. | [
{
"name": "vlan-tag inner",
"desc": "In the case of double tagged packets, classify based on the 802.1p of the inner VLAN tag."
},
{
"name": "vlan-tag outer",
"desc": "Classify based on the 802.1p of the outermost VLAN tag."
},
{
"name": "classifier-name",
"desc": "Name of the previo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [] |
ieee-802.1 (Congestion Notification) | ieee-802.1 {
code-point up-bits pfc ;
} | [edit class-of-service congestion-notification-profile profile-name],
[edit class-of-service interfaces interface-name congestion-notification-profile profile-name] | Set an association between the traffic class and the congestion notification profile.
The remaining statement is explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Example: Configuring an FCoE Transit Switch",
"Configuring Priority-Based Flow Control for an EX Series Switch (CLI Procedure)"
] |
ieee-802.1 (Dynamic Classifiers) | ieee-802.1 (classifier-name | default) vlan-tag (inner | outer); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number classifiers] | Apply an IEEE-802.1 classifier to a subscriber interface in a dynamic profile. | [
{
"name": "classifier-name",
"desc": "Name of a classifier mapping configured at the [edit class-of-service classifiers"
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Classifier to a Subscriber Interface in a Dynamic Profile",
"classifiers (Definition)"
] |
ieee-802.1 (Dynamic Rewrite Rules) | ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number rewrite-rules] | Apply an IEEE-802.1 rewrite rule to a subscriber interface in a dynamic profile. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules"
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Rewrite Rule Definition to a Subscriber Interface in a Dynamic Profile",
"rewrite-rules"
] |
ieee-802.1 (Fibre Channel Interfaces) | ieee-802.1 {
code-point code-point-bits;
} | [edit class-of-service interfaces fibre-channel-interface-name rewrite-value input] | Configure the IEEE 802.1p code point value to which all traffic received from the Fibre Channel (FC)
network on the specified FC interface is rewritten. After the code point value is rewritten, the interface
forwards the traffic to the Ethernet (FCoE) network. This works in conjunction with configuring a fixed
classifi... | [] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Example: Configuring IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS Classifiers"
] | |
ieee-802.1 (Host Outbound Traffic) | ieee-802.1 {
default value;
rewrite-rules;
} | [edit class-of-service host-outbound-traffic] | Apply the IEEE 802.1p rewrite rules associated with the egress logical interface to the IEEE 802.1p PCP
field for all host outbound traffic on that interface.
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 12.3. | [
"Host Outbound Traffic IEEE802.1p Rewrite",
"Rewriting Packet Headers to Ensure Forwarding Behavior",
"Configuring Rewrite Rules"
] |
ieee-802.1 (Input Congestion Notification) | ieee-802.1 {
code-point [code-point-bits] {
pfc {
mru mru-value;
}
xon
}
} | [edit class-of-service congestion-notification-profile profile-name input] | Configure an IEEE 802.1 code point and apply priority-based flow control (PFC) to packets with that
code point. | [] | 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. | [
"Example: Configuring CoS PFC for FCoE Traffic",
"Configuring CoS PFC (Congestion Notification Profiles)",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)"
] |
ieee-802.1 (Output Congestion Notification) | ieee-802.1 {
code-point [ code-point-bits ] {
flow-control-queue [ queue | list-of-queues ];
}
} | [edit class-of-service congestion-notification-profile profile-name output] | Configure an IEEE 802.1 code point and apply priority-based flow control (PFC) to packets with that
code point on output queues. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit",
"Switch Interfaces",
"Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch",
"Interface",
"Example: Configuring ... |
ieee-802.1 (Rewrite Rules on Logical Interface) | ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner); | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Apply an IEEE-802.1 rewrite rule. For IQ PICs, you can only configure one IEEE 802.1 rewrite rule on a
physical port. All logical ports (units) on that physical port should apply the same IEEE 802.1 rewrite rule. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules"
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
vlan-tag statement introduced in Junos OS Release 8.1. | [
"Configuring Rewrite Rules"
] |
ieee-802.1 (Rewrite Rules on Physical Interface) | ieee-802.1 (rewrite-name | default) ; | [edit class-of-service interfaces interface-name rewrite-rules] | Apply an IEEE-802.1 rewrite rule. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules"
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [] |
ieee-802.1ad | ieee-802.1ad (rewrite-name | default) vlan-tag (outer | outer-and-inner); | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Apply a IEEE-802.1ad rewrite rule. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules"
},
{
"name": "default",
"desc": "The default rewrite bit mapping."
},
{
"name": "vlan-tag",
"desc": "The rewrite rule is applied to the outer or outer-and-inner ... | 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. | [
"Configuring Rewrite Rules"
] |
ieee-802-3az-eee | ieee-802-3az-eee; | [edit interfaces interface-name ether-options] | Configure Energy Efficient Ethernet (EEE) on an EEE-capable Base-T copper interface.
Default
EEE is disabled on EEE-capable interfaces. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Energy Efficient Ethernet on Interfaces"
] |
ietf-mode | ietf-mode | [edit protocols ancp neighbor ip-address] | Configure the ANCP agent to run in a mode that is not backward compatible with Internet draft-
wadhwa-gsmp-l2control-configuration-00.txt, GSMP extensions for layer2 control (L2C). Include this
statement when pre-ietf mode has been configured globally for the ANCP agent, but you want one or
more neighbors to run in the... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring the ANCP Agent",
"Configuring ANCP Neighbors"
] |
if-exceeding (EX) | if-exceeding {
bandwidth-limit bps;
bandwidth-percent percent
burst-size-limit bytes;
} | [edit firewall policer policer-name]
[edit logical-systems logical-system-name firewall policer policer-name] | Configure policer rate limits.
The bandwidth-percent statement is supported on routers only.
The remaining statements are explained separately. See CLI Explorer. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on EX Series Switches",
"Configuring Policers to Control Traffic Rates (CLI Procedure)",
"Understanding the Use of Policers in Firewall Filters",
"Basic Single-Rate Two-Color Policers"
] |
if-exceeding (Hierarchical Policer) | if-exceeding {
bandwidth-limit bps;
burst-size-limit bytes;
} | [edit dynamic-profiles profile-name firewall hierarchical-policer aggregate],
[edit dynamic-profiles profile-name firewall hierarchical-policer premium],
[edit firewall hierarchical-policer aggregate],
[edit firewall hierarchical-policer premium] | For M40e, M120, and M320 (with FFPC and SFPC) edge routers and T320, T640, and T1600 core
routers with Enhanced Intelligent Queuing (IQE) PICs, T4000 routers with Type 5 FPC and Enhanced
Scaling Type 4 FPC, specify bandwidth and burst limits for a premium or aggregate component of a
hierarchical policer.
The remaining ... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles ... aggregate] and [edit dynamic-profiles ... premium] hierarchy level
introduced in Junos OS Release 11.4. | [
"Hierarchical Policer Configuration Overview",
"Hierarchical Policers",
"bandwidth-limit (Hierarchical Policer)"
] |
if-exceeding (Policer) | if-exceeding {
(bandwidth-limit bps | bandwidth-percent number);
burst-size-limit bytes;
} | [edit dynamic-profiles profile-name firewall policer policer-name],
[edit firewall policer policer-name],
[edit logical-systems logical-system-name firewall policer policer-name] | Configure rate limits for a single-rate two-color policer.
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 before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... policer policer-name] hierarchy level introduced in Junos OS
Release 11.4. | [
"Two-Color Policer Configuration Overview",
"Hierarchical Policer Configuration Overview",
"Basic Single-Rate Two-Color Policers",
"Bandwidth Policers",
"Prefix-Specific Counting and Policing Actions",
"Multifield Classification",
"Policer Overhead to Account for Rate Shaping in the Traffic Manager",
... |
if-exceeding (QFX) | if-exceeding {
bandwidth-limit bps;
burst-size-limit bytes;
} | [edit firewall policer policer-name] | Configure policer rate limits.
The remaining statements are explained separately. See CLI Explorer. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Two-Color and Three-Color Policers to Control Traffic Rates",
"Overview of Policers"
] |
if-exceeding-pps (Hierarchical Policer) | if-exceeding-pps {
pps-limit pps;
packet-burst packets;
} | [edit dynamic-profiles profile-name firewall hierarchical-policer hierarchical-policer-name
aggregate],
[edit dynamic-profiles profile-name firewall hierarchical-policer hierarchical-policer-name premium],
[edit firewall hierarchical-policer hierarchical-policer-name aggregate],
[edit firewall hierarchical-policer hie... | For MX Series routers , if-exceeding-pps allows you to configure a packets-per-second (pps)-based trigger
for a premium or aggregate component of a hierarchical policer. When applied to the loopback interface
(lo0), this kind of trigger can help protect the Routing Engine from DDoS attacks. When applied in other
areas,... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.2. | [
"Hierarchical Policer Configuration Overview",
"Hierarchical Policers"
] |
if-exceeding-pps (Policer) | if-exceeding-pps {
pps-limit pps;
packet-burst packets;
} | [edit dynamic-profiles profile-name firewall policer policer-name],
[edit firewall policer policer-name],
[edit logical-systems logical-system-name firewall policer policer-name] | Configure rate limits in packets per second for a single-rate two-color policer when policing is desired on
a packets-per-second basis rather than a bits-per-second basis. This can help protect against distributed
denial of service (DDoS) attacks.
The remaining statements are explained separately. See CLI Explorer. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Two-Color Policer Configuration Overview",
"Hierarchical Policer Configuration Overview",
"Basic Single-Rate Two-Color Policers",
"Bandwidth Policers",
"Prefix-Specific Counting and Policing Actions",
"Multifield Classification",
"Policer Overhead to Account for Rate Shaping in the Traffic Manager",
... |
if-route-exists | if-route-exists {
address;
address-family {
inet {
address;
table table-name;
}
ccc {
interface-name;
standby;
peer-unit unit-number;
table table-name;
}
}
table table-name;
} | [edit logical-systems logical-system-name policy-options condition],
[edit policy-options condition] | Specify the route match conditions. | [
{
"name": "(Optional) address",
"desc": "Specify the IP address that the route must have to be considered a match."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario",
"Example: Configuring a Routing Policy for Conditional Advertisement Enabling Conditional",
"Installation of Prefixes in a Routing Table"
] |
ifl-subscriber | ifl-subscriber [subscriber-name] {
access-interfaces [interface-name];
apply-groups [group-names];
apply-groups-except [group-names];
} | [edit unified-edge gateways tdf gateway-name domains domain-name] | Specify the name of the IFL-based subscriber for traffic that is carried on a particular interface or
interfaces. You can configure up to 32 IFL-based subscribers in a TDF domain.
To configure a subscriber name, you must have set the subscriber-type to ifl at the [edit unified-edge
gateway tdf gateway-name domains doma... | [
{
"name": "subscriber-name",
"desc": "Name of the subscriber. You can configure up to 32 IFL-based subscribers in a TDF domain. Range: Up to 63 bytes. 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 IFL-Based TDF Subscribers and Properties with a TDF Domain",
"Understanding the Definition of a Set of IFL-Based Subscriber Properties with a TDF Domain"
] |
igmp (Dynamic Profiles) | igmp {
interface interface-name {
accounting;
disable;
group-limit policy-name;
group-policy;
group-threshold value;
immediate-leave;
log-interval seconds;
no-accounting;
oif-map map-name;
passive <allow-receive> <send-general-query> ... | [edit dynamic-profiles profile-name protocols] | Enable IGMP on the router. IGMP must be enabled for the router to receive multicast packets.
You can configure IGMP in a dynamic client profile or a dynamic service profile.
Default
IGMP is disabled on the router. IGMP is automatically enabled on all broadcast interfaces when you
configure Protocol Independent Multica... | [] | 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. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Understanding IGMP",
"Enabling IGMP"
] |
igmp | igmp {
accounting;
interface interface-name {
(accounting | no-accounting);
disable;
distributed;
group-limit limit;
group-policy [ policy-names ];
group-threshold
immediate-leave;
log-interval
oif-map map-name;
passive;
pro... | [edit logical-systems logical-system-name protocols],
[edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | 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. | [
"Enabling IGMP"
] |
igmp-querier (QFabric Systems only) | igmp-querier {
source-addresssource address;
} | [edit protocols igmp-snooping vlan vlan-name] | Configure a QFabric Node device to be an IGMP querier. If there are any multicast routers on the same
local network, make sure the source address for the IGMP querier is lower (a smaller number) than the
IP addresses for those routers on the network. This ensures that Node is always the IGMP querier on
the network. | [
{
"name": "source-address",
"desc": ""
},
{
"name": "source address",
"desc": "The address that the switch uses as the source address in the IGMP queries that it sends."
}
] | 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-D15. | [
"Example: Configuring IGMP Snooping on Switches",
"Configuring IGMP Snooping on Switches"
] |
igmp-snooping | igmp-snooping {
vlan (all | vlan-name) {
immediate-leave;
interface interface-name {
group-limit range;
host-only-interface;
multicast-router-interface;
immediate-leave;
static {
group multicast-ip-address {
... | [edit bridge-domains bridge-domain-name protocols],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols]
[edit routing-instances routing-instance-name protocols]
[edit protocols] | Configure IGMP snooping, which constrains multicast traffic to only the ports that have receivers
attached.
IGMP snooping enables the device to selectively send out multicast packets on only the ports that need
them. Without IGMP snooping, the device floods the packets on every port. The device listens for the
exchange... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"IGMP Snooping Overview",
"Overview of Multicast Forwarding with IGMP or MLD Snooping in an EVPN-MPLS Environment",
"Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN",
"Environment",
"IGMP Snooping in MC-LAG Active-Active Mode",
"Configuring IGMP Snooping on Switches",
... |
igmp-snooping-options | igmp-snooping-options {
snoop-pseudowires
use-p2mp-lsp
} | [edit logical-systems logical-system-name routing-instances routing-instance-name]
[edit routing-instances routing-instance-name ] | Supports the use-p2mp-lsp or snoop-pseudowires options for independent routing instances and those in a
logical system. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Example: Configuring IGMP Snooping"
] |
ignore (Event Policy) | ignore; | [edit event-options policy policy-name then] | Define a policy that ignores particular events. If one or more of the listed events occur, a system log
message for the event is not generated, and no further policies associated with this event are processed.
If you include the ignore statement in a policy configuration, you cannot configure any other actions in
the p... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configure Event Policies to Ignore an Event"
] |
ignore | [] | [] | |||||
ignore-all | ignore-all; | [edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options] | Ignore all control leads. You can include the ignore-all statement in the configuration only if you do not
explicitly enable other signal handling options at the dte-options hierarchy level. | [] | 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 Serial Signal Handling"
] |
ignore-attached-bit | ignore-attached-bit; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Ignore the attached bit on IS-IS Level 1 routers. Configuring this statement enables the routing device to
ignore the attached bit on incoming Level 1 link-state PDUs. If the attached bit is ignored, no default
route, which points to the routing device which has set the attached bit, is installed.
There might be times,... | [] | 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. | [] |
ignore-encapsulation-mismatch | ignore-encapsulation-mismatch; | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-grou... | Allow a Layer 2 circuit, VPLS, or EVPN to be established even though the encapsulation configured on
the CE device interface does not match the encapsulation configured on the Layer 2 circuit, VPLS, or
EVPN interface. | [] | 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.
Statement extended to support local switching in Junos OS Release 10.4.
Statement introduced for EVPNs in Junos OS Release 13.2 for MX 3D Series. | [
"Configuring EVPN Routing Instances",
"Enabling the Layer 2 Circuit When the Encapsulation Does Not Match"
] |
ignore-entry | [] | [] | |||||
ignore-errors | ignore-errors <alg> <tcp>; | [edit interfaces interface-name services-options] | Define settings for minimizing TCP packet drops during stateful firewall processing.
NOTE: ignore-errors option is not supported on adaptive services interfaces (sp-x/y/z). | [
{
"name": "alg",
"desc": "(Optional) Mediate ALG behavior that results in dropping malformed packets or random packets"
},
{
"name": "tcp",
"desc": "(Optional) Prevent software from dropping packets that fail TCP SYN checks."
}
] | 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. | [
"Defining an Application Identification"
] |
ignore-fan-speed-check | ignore-fan-speed-check; | [edit chassis alarm] | Ignore alarm messages about fan speed, such as FPC x Fan x Spinning Underspeed, FPC x Fan x Spinning
Overspeed, etc. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [] |
ignore-l3-incompletes | ignore-l3-incompletes; | [edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options] | Ignore the counting of Layer 3 incomplete errors on Fast Ethernet, Gigabit Ethernet, and 10-Gigabit
Ethernet interfaces. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"Ignoring Layer 3 Incomplete Errors"
] |
ignore-lsp-metrics | ignore-lsp-metrics; | [edit logical-systems logical-system-name protocols ospf traffic-engineering shortcuts],
[edit protocols ospf traffic-engineering shortcuts] | Cause OSPF to ignore the RSVP LSP metric.
Some other vendors use an OSPF metric of 1 for the loopback address. Juniper Networks routers use an
OSPF metric of 0 for the loopback address. This can cause interoperability problems when you configure
LDP tunneling over RSVP LSPs in heterogeneous networks. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Enabling LDP over RSVP-Established LSPs in Heterogeneous Networks"
] |
ignore-magic-number-mismatch (Access Group Profile) | ignore-magic-number-mismatch; | [edit access group-profile name ppp ppp-options] | Prevent the Packet Forwarding Engine from performing a validation check for magic numbers received in
LCP keepalive (Echo-Request/Echo-Reply) exchanges for a group of tunneled PPP subscribers at the
LNS.
A mismatch occurs when the PPP magic number received from a remote peer in the keepalive exchange
does not match the... | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"L2TP LNS Inline Service Interfaces",
"PPP Subscriber Access Networks Overview"
] |
ignore-magic-number-mismatch (Dynamic Profiles) | ignore-magic-number-mismatch; | [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] | Prevent the Packet Forwarding Engine from performing a validation check for magic numbers received in
LCP keepalive (Echo-Request/Echo-Reply) exchanges for dynamic PPP subscriber connections
terminated at the router or for dynamic tunneled PPP subscribers on LNS inline service interfaces.
A mismatch occurs when the PPP... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"PPP Subscriber Access Networks Overview",
"PPP Subscriber Access Networks Overview",
"L2TP LNS Inline Service Interfaces"
] |
ignore-memory-overflow | (ignore-memory-overflow | no-ignore-memory-overflow); | [edit security idp sensor-configuration re-assembler] | Enable the TCP reassembler to ignore the memory overflow to prevent the dropping of IDP custom
applications. By default this feature is enabled. | [] | 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. | [] |
ignore-mtu-mismatch | ignore-mtu-mismatch; | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn interfac... | Ignore the MTU configuration set for the physical interface associated with the local switching interface
or with the remote PE router. This allows a pseudowire to be brought up between two logical interfaces
that are defined on physical interfaces with different MTU values. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration | Statement introduced in Junos OS Release 8.5.
Support for remote PE routers added in Junos OS Release 9.2.
Support for Layer 2 VPNs and VPLS added in Junos OS Release 10.4. | [
"Enabling Local Interface Switching When the MTU Does Not Match",
"Configuring the MTU for Layer 2 Interfaces",
"ignore-reassembly-memory-overflow | no-ignore-reassembly-memory-"
] |
overflow | (ignore-reassembly-memory-overflow | no-ignore-reassembly-memory-overflow); | [edit security idp sensor-configuration re-assembler] | Reassembly memory overflow occurs when the memory allocated for the reassembly of TCP fragments
is exceeded. When the reassembly of TCP fragments exceeds the memory limit, defined with max-packet-
mem-ratio, you can define the system behavior to ignore or drop the offending packets. If the ignore-
reassembly-memory-ove... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"max-packet-mem-ratio"
] |
ignore-reassembly-overflow | ignore-reassembly-overflow | [edit security idp sensor-configuration re-assembler] | Enable the TCP reassembler to ignore the global reassembly overflow to prevent the dropping of
application traffic. This feature is enabled by default. | [] | 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. | [] |
ignore-server-validation (Application Identification) | ignore-server-validation; | [edit services application-identification download] | Disable server authentication for application signature package download. | [] | 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 on SRX Series Firewalls.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview",
"Downloading and Installing Predefined Junos OS Application Signature Packages"
] |
ignore-server-validation (Application Identification) | ignore-server-validation; | [edit services application-identification download] | Disable server authentication for application signature package download. | [] | 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 on SRX Series Firewalls.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview",
"Downloading and Installing Predefined Junos OS Application Signature Packages"
] |
ignore-stp-topology-change | ignore-stp-topology-change; | [edit bridge-domains bridge-domain-name multicast-snooping-options],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name multicast-snooping-
options] | Ignore messages about spanning tree topology changes. This statement is supported for the virtual-
switch routing instance type only. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Example: Configuring Multicast Snooping"
] |
igp-synchronization | igp-synchronization holddown-interval seconds; | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Configure the time the LDP waits before informing the IGP that the LDP neighbor and session for an
interface are operational. For large networks with numerous FECs, you might need to configure a longer
value to allow enough time for the LDP label databases to be exchanged. | [
{
"name": "holddown-interval seconds",
"desc": "Time the LDP waits before informing the IGP that the LDP neighbor and"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring LDP Synchronization with the IGP on the Router"
] |
ike (Access Profile) | ike {
allowed-proxy-pair {
remote remote-proxy-address local local-proxy-address;
}
dead-peer-detection{
interval seconds
threshold number
}
ike-policy policy-name;
initiate-dead-peer-detection;
interface-id string-value;
ipsec-policy ipsec-policy;
pre-shared-... | [edit access profile profile-name client client-name] | Configure an IKE access profile.
The remaining statements are explained below.
NOTE: This statement is not supported on MX Series routers. | [
{
"name": "allowed-proxy-pair",
"desc": "Specify the network address of the local and remote peer associated with an IKE access profile. Values:"
},
{
"name": "local local-proxy-address",
"desc": "Network address of the local peer. Default:"
},
{
"name": "0.0.0.0",
"desc": ""
},
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
ike-policy statement introduced in Junos OS Release 8.2. | [
"Configuring an IKE Access Profile",
"Configuring Services Interfaces"
] |
ike (High Availability) | ike {
gateway name {
ike-policy policy-name;
version (v1-only | v2-only);
}
policy name {
description description;
pre-shared-key (ascii-text ascii-text | hexadecimal hexadecimal);
proposals [ proposals ... ];
}
proposal name {
authentication-algorithm... | [edit security] | Define Internet Key Exchange (IKE) configuration for high availability feature. IKE is a key management
protocol that creates dynamic SAs; it negotiates SAs for IPsec. An IKE configuration defines the
algorithms and keys used to establish a secure connection with a peer security gateway. | [
{
"name": "gateway-name",
"desc": "Name of the gateway."
},
{
"name": "ike-policy",
"desc": "Specify the IKE policy to be used for the gateway."
},
{
"name": "version",
"desc": "Specify the IKE version to use to initiate the connection. Values:"
},
{
"name": "v2-only",
"... | 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"
] |
ike (Security Group VPN Member) | ike {
gateway gateway-name {
ike-policy policy-name;
local address ip-address;
local-identity {
(hostname hostname | inet ip-address | inet6 ipv6-address | user-at-hostname e-mail-
address);
}
remote-identity {
(hostname hostname | inet ip-address | us... | [edit security group-vpn member] | 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": "gateway gateway-name",
"desc": "Configure IKE gateway for group VPN member."
},
{
"name": "policy policy-name",
"desc": "Configure an IKE policy."
},
{
"name": "proposalproposal-name",
"desc": "Define an IKE proposal."
},
{
"name": "traceoptions",
"desc": "Conf... | 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"
] |
ike (Security Group VPN Server) | ike {
gateway gateway-name {
address ip-address;
dead-peer-detection {
always-send;
interval seconds;
threshold number;
}
dynamic {
(hostname hostname | inet ip-address | user-at-hostname e-mail-address);
}
ike-policy po... | [edit security group-vpn server] | Configure Phase 1 security association (SA) with a member on the group server. The gateway is 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": "gateway gateway-name",
"desc": "Configure IKE gateway for group VPN server."
},
{
"name": "policy policy-name",
"desc": "Configure an IKE policy."
},
{
"name": "proposal proposal-name",
"desc": "Define an IKE proposal."
}
] | 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"
] |
ike (Security IPsec VPN) | ike {
anti-replay-window-size anti-replay-window-size;
gateway gateway-name;
idle-time seconds;
install-interval seconds;
ipsec-policy ipsec-policy-name;
no-anti-replay;
proxy-identity {
local ip-prefix;
remote ip-prefix;
service (any | service-name);
}
} | [edit security ipsec vpn vpn-name] | Define an IKE-keyed IPsec VPN. | [
{
"name": "anti-replay-window-",
"desc": ""
},
{
"name": "size",
"desc": "To enable the anti-replay-window-size option, you first need to configure the option for each VPN object or at the global level. You can configure the anti-replay window size in the range of 64 to 8192 (power of 2). If 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. Support.
Statement anti-replay-window-size is introduced in Junos OS Release 19.2R1.
Support for idle-time and install-interval options with IPsec VPN running iked process is added in Junos
OS Release 23.4R1. | [
"IPsec Overview"
] |
ike (Security Services) | ike {
policy ike-peer-address {
description policy-description;
encoding (binary | pem);
identity identity-name;
local-certificate certificate-filename;
local-key-pair private-public-key-file;
mode (aggressive | main);
pre-shared-key (ascii-text key | hexadeci... | [edit security] | (Encryption interface on M Series and T Series routers only) Configure IKE. | [] | 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 an IKE Proposal for Dynamic SAs",
"Configuring an IKE Policy for Preshared Keys"
] |
ike (Security) | ike {
gateway (Security IKE) name {
( address | dynamic (Security) distinguished-name (Security) < container> < wildcard>
hostname inet inet6 user-at-hostname <connections-limit connections-limit> <ike-user-type
(group-ike-id | shared-ike-id)> <reject-duplicate-connection>);
aaa {
ac... | [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": "respond-bad-spi max-responses",
"desc": "(Optional) Number of times to respond to invalid SPI values per gateway."
},
{
"name": "traceoptions",
"desc": "Configure IKE tracing options to aid in troubleshooting the IKE issues. This helps"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5.
Support for IPv6 addresses added in Junos OS Release 11.1.
Support for inet6 option added in Junos OS Release 11.1.
Support for group15, group16, group21, ecdsa-signatures-521, and sha-512 options added in Junos OS Release
19.1R1 on SRX5000 line with junos-ike package install... | [
"IPsec Overview",
"ALG Overview",
"Understanding Logical Systems for SRX Series Services Gateways",
"Example: Configuring AutoVPN with Pre-Shared Key",
"Installing Junos IKE package",
"IKE Protection from DDoS Attacks",
"session (Security IKE)",
"blocklists (Security IKE)"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.