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 |
|---|---|---|---|---|---|---|---|
arp-enhanced-scale | arp-enhanced-scale; | [edit system] | Increases the number of ARP and neighbor discovery entries for MC-LAG configured with enhanced
convergence and Layer 3 VXLAN deployments.
NOTE: To increase the ARP and discovery entries for MC-LAG with enhanced
convergence, you also need to enable the enhanced-convergence statement at the [edit
system] hierarchy. For i... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [
"Understanding Multichassis Link Aggregation Groups"
] |
arp-inspection (MX Series) | arp-inspection; | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] | Perform dynamic ARP inspection (DAI).
DAI can only be configured for a specific bridge domain, not for a list or a range of bridge domain names.
DHCP snooping is automatically enabled on the specified VLAN or bridge domain.
Default
Disabled. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Applying CoS Forwarding Classes to Prioritize Inspected Packets",
"Example: Configuring IP Source Guard and Dynamic ARP Inspection on a Specified Bridge Domain to",
"Protect the Devices Against Attacks"
] |
arp-inspection | arp-inspection {
forwarding-class class-name;
} | For platforms with ELS:
[edit vlans vlan-name forwarding-options dhcp-security],
[edit forwarding-options dhcp-relay]
For platforms without ELS:
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name)],
[edit forwarding-options dhcp-relay] | Perform dynamic ARP inspection (DAI) on all VLANs or on the specified VLAN.
When DAI is enabled, the switch logs invalid ARP packets that it receives on each interface, along with
the sender’s IP and MAC addresses. ARP probe packets, which have the sender IP address 0.0.0.0, are
validated by DAI.
NOTE: If you configure... | [] | 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.
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.)
Starting in Junos OS Release 25.4R1, GBP tagging and enforcement works on ARP packets... | [
"Example: Protecting Against Address Spoofing and Layer 2 DoS Attacks",
"Example: Protecting Against ARP Spoofing Attacks",
"Example: Configuring IP Source Guard and Dynamic ARP Inspection to Protect the Switch from IP",
"Spoofing and ARP Spoofing",
"Example: Prioritizing Snooped and Inspected Packet",
"E... |
arp-l2-validate | arp-l2-validate | [edit interfaces irb] | Enables periodic checking of ARP Layer 3 addressing and MAC Layer 2 addressing tables, and fixes
entries if they become out of sync.
Normally, the ARP and MAC address tables stay synchronized. However, you can configure this option
on the irb interface of the switch to help avoid traffic loss in network conditions that... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R4. | [] |
arp-max-cache | arp-max-cache arp-max-cache; | [edit interfaces name unit name family inet] | The ARP cache limit for resolved next hops can be configured at an interface level. The benefit of
configuring the ARP cache limit is to protect the device from DoS attacks.
NOTE: After modifying the default ARP next-hop cache limit on an interface, you must
deactivate and then reactivate the interface for the newly co... | [
{
"name": "arp-max-cache",
"desc": "Indicates the maximum number of routes to be held in the ARP cache. Default: 20,000 (ACX Series routers, EX2200, EX2200-C, EX3200, and EX3300 switches, SRX Series Firewalls) 75,000 (EX4200, EX4300, EX4500, EX4550, and EX6210 switches, MX Series routers)"
},
{
"... | 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. | [
"Example: Configuring ARP Cache Protection",
"arp-inspection (MX Series)"
] |
arp-nd-probe-disable | arp-nd-probe-disable; | [edit protocols l2-learning] | Disable the default probing that happens when you provision static MAC-IP entries.
This statement ensures that probing is disabled, and the PE router acquires both the MAC address and
MAC-IP binding information from the network traffic and communicates the information using EVPN. | [] | [none specified] | Statement introduced in Junos OS Release 23.4R1. | [] |
arp-nd-probe-failed-log | arp-nd-probe-failed-log; | [edit protocols l2-learning] | Enable syslog when the IP address probe fails. | [] | [none specified] | Statement introduced in Junos OS Release 23.4R1. | [] |
arp-new-hold-limit | arp-new-hold-limit number; | [edit interfaces interface-name unit interface-unit-number family inet] | The ARP cache limit for unresolved next hops can be configured at an interface level. The benefit of
configuring the ARP cache limit is to protect the device from DoS attacks. | [
{
"name": "number",
"desc": "Indicates the new or maximum routes to be held, before getting added to the ARP cache."
}
] | 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. | [
"Example: Configuring ARP Cache Protection",
"arp-inspection (MX Series)"
] |
arp-prefix-limit (Host Fast Reroute) | arp-prefix-limit number; | [edit logical-systems logical-system-name routing-instances instance-name routing-options
interface interface-name],
[edit routing-instances instance-name routing-options interface interface-name] | Override the ARP prefix limit for the specified host fast-reroute (HFRR) profile.
When you configure HFRR, an optional ARP prefix limit sets a maximum for the number of ARP routes
and, therefore FRR routes created for each HFRR profile in the routing table. This limit prevents ARP
attacks from exhausting the virtual me... | [
{
"name": "number",
"desc": "Maximum number of ARP HFRR routes allowed. Range: 1 through 10,000 HFRR routes"
}
] | 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 Link Protection with Host Fast Reroute"
] |
arp-resp | arp-resp (restricted|unrestricted); | [edit interfaces interfaces-name unit logical-unit-number ] | Configure Address Resolution Protocol (ARP) response on the interface. | [
{
"name": "restricted",
"desc": "Enable restricted proxy ARP response on the interface. This is the default."
},
{
"name": "unrestricted",
"desc": "Enable unrestricted ARP response on the interface."
}
] | 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. | [] |
arp-system-cache-limit | arp-system-cache-limit number; | [edit system] | Specify the ARP cache next-hop limit at the system (global) level to restrict the number of next-hop
routes. To configure the limit at the interface level, use the "arp-max-cache" on page 2671 statement.
The default behavior of ARP is to remove the cache entry if it is not used within a certain period of time,
and not ... | [
{
"name": "number",
"desc": "Indicates the maximum number of routes to be held in the ARP cache. Default: 20,000 (ACX Series routers, EX2200, EX2200-C, EX3200, and EX3300 switches, SRX Series Firewalls) 75,000 (EX4200, EX4300, EX4500, EX4550, and EX6210 switches, MX Series routers)"
},
{
"name": ... | 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. | [
"Example: Configuring ARP Cache Protection",
"arp-inspection (MX Series)"
] |
arp-throttle | arp-throttle seconds; | [edit forwarding-options next-hop] | Define the time duration (in seconds) for Address Resolution Protocol (ARP) request throttling to remain
active when it is triggered.
When ARP throttling is triggered, it is active for a given logical interface. For the configured duration of
time, the ARP throttling remains active, and the traffic entering into the sp... | [
{
"name": "seconds",
"desc": "Time interval (in seconds) for Address Resolution Protocol (ARP) request throttling to remain"
}
] | 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-D65, Junos OS Release 15.1X49-D60, and Junos
OS Release 15.1X49-D130. | [] |
as-external | as-external; | [edit logical-systems name protocols ospf overload],
[edit logical-systems name routing-instances name protocols ospf overload],
[edit protocols ospf overload],
[edit routing-instances name protocols ospf overload],
[edit protocols ospf3 overload] | Advertise OSPF AS external prefixes with maximum usable 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"
] |
as-list | as-list name {
members [ members ... ];
} | [edit logical-systems name policy-options],
[edit policy-options] | Define a policy to specify a list of BGP autonomous systems (AS) to configure acceptable AS ranges for
EBGP groups that can be used for bringing up BGP peers while establishing a BGP session. BGP accepts
a peer request based on the specified AS range and rejects a peer request if the AS does not fall into the
specified... | [
{
"name": "name",
"desc": "Specify a name to identify a BGP as-list."
},
{
"name": "members",
"desc": "Specify a single autonomous system number or a range of autonomous system numbers in plain numbers."
}
] | routing | Statement introduced in Junos OS Release 20.2R1. | [] |
as-override | as-override; | [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
group group-name],
[edit logical-systems logical-system-... | Compare the AS path of an incoming route with the AS number of the BGP peer in the group, and
replace all occurrences of the peer AS number in the AS path with its own AS number before re-
advertising the route to the peer.
NOTE: The as-override statement is specific to a particular BGP group. This statement
does not a... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring a Layer 3 VPN with Route Reflection and AS Override",
"Junos OS VPNs Library for Routing Devices"
] |
as-path (Policy Options) | as-path name regular-expression; | [edit dynamic policy-options],
[edit logical-systems logical-system-name policy-options],
[edit policy-options] | Define an autonomous system (AS) path regular expression for use in a routing policy match condition. | [
{
"name": "name",
"desc": "Name that identifies the regular expression. The name can contain letters, numbers, and hyphens"
},
{
"name": "regular-expression",
"desc": "One or more regular expressions used to match the AS path."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5 for EX Series
switches. | [
"Understanding AS Path Regular Expressions for Use as Routing Policy Match Conditions"
] |
as-path (Routing Options) | as-path <as-path> <aggregator as-number ip-address> <atomic-aggregate> <origin (egp | igp |
incomplete)>; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options (aggregate | generate | static) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name (aggregate | generate | static) (defaults | ro... | Associate BGP autonomous system (AS) path information with a static, aggregate, or generated route.
In Junos OS Release 9.1 and later, the numeric range for the AS number is extended to provide BGP
support for 4-byte AS numbers as defined in RFC 4893, BGP Support for Four-octet AS Number Space.
RFC 4893 introduces two... | [
{
"name": "aggregator",
"desc": "(Optional) Attach the BGP aggregator path attribute to the aggregate route. You must"
},
{
"name": "as-path",
"desc": "(Optional) AS path to include with the route. It can include a combination of individual AS path"
},
{
"name": "atomic-aggregate",
"... | 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: Summarizing Static Routes Through Route Aggregation"
] |
as-path-compare | as-path-compare; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multipath],
[edit routing-instances routing-instance-name routing-options multipath] | Specify to have the algorithm that is used to determine the active path compare the AS numbers in the
AS path. In a VPN scenario with multiple BGP paths, the algorithm selects as the active path the route
whose AS numbers match. By default, the algorithm evaluates only the length and not the contents of
the AS path. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring the Algorithm That Determines the Active Route to Evaluate AS Numbers in AS Paths for",
"VPN Routes"
] |
as-path-group | as-path-group group-name {
as-path name regular-expression;
} | [edit dynamic policy-options],
[edit logical-systems logical-system-name policy-options],
[edit policy-options] | Define a group containing multiple AS path regular expressions for use in a routing policy match
condition. | [
{
"name": "group-name",
"desc": "Name that identifies the AS path group. One or more AS path regular expressions must be"
},
{
"name": "name",
"desc": "Name that identifies the regular expression. The name can contain letters, numbers, and hyphens"
},
{
"name": "regular-expression",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for dynamic database configuration introduced in Junos OS Release 9.5.
Support for dynamic database configuration introduced in Junos OS Release 9.5 for EX Series switches. | [
"Understanding AS Path Regular Expressions for Use as Routing Policy Match Conditions"
] |
asm-override-ssm | asm-override-ssm; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Enable the routing device to accept any-source multicast join messages (*,G) for group addresses that
are within the default or configured range of source-specific multicast groups. | [] | 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. | [
"Example: Configuring Source-Specific Multicast Groups with Any-Source Override"
] |
asregex-optimize | asregex-optimize (no-optimize | optimize); | [edit logical-systems name policy-options defaults],
[edit policy-options defaults] | The configuration statement refers to as-path-group under [edit policy-options defaults]. This
configuration enables more efficient AS-path processing by creating groups of AS-path patterns, which
network devices can match rapidly. This approach benefits large-scale networks where BGP policies
must handle complex AS-pa... | [
{
"name": "no-optimize",
"desc": "Disable AS-PATH regular expression optimizer"
},
{
"name": "optimize",
"desc": "Enable AS-PATH regular expression optimizer"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [
"Improve the Performance of AS Path Lookup in BGP Policy"
] |
assemble | assemble {
common-name common-name;
} | [edit access ldap-options],
[edit access profile profile-name ldap-options] | Specify that a user’s LDAP distinguished name (DN) is assembled through the use of a common name
identifier, the username, and base distinguished name. | [
{
"name": "common-name common-name",
"desc": "Common name identifier used as a prefix for the username during the assembly"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
assert-timeout | assert-timeout 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] | Multicast routing devices running PIM sparse mode often forward the same stream of multicast packets
onto the same LAN through the rendezvous-point tree (RPT) and shortest-path tree (SPT). PIM assert
messages help routing devices determine which routing device forwards the traffic and prunes the RPT
for this group. By ... | [
{
"name": "seconds",
"desc": "Time for routing device to wait before another assert message cycle."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring the PIM Assert Timeout"
] |
assignment-id-format (L2TP LAC) | assignment-id-format (assignment-id | client-server-id); | [edit services l2tp tunnel] | Set the format for the name used for a tunnel, the tunnel assignment ID.
NOTE: Before you downgrade to a Junos OS Release that does not support this
statement, unconfigure the statement by issuing no services l2tp tunnel assignment-id-
format.
Default
assignment-Id | [
{
"name": "assignment-Id",
"desc": "The tunnel name corresponds to RADIUS attribute Tunnel-Assignment-Id [82]."
},
{
"name": "client-server-id",
"desc": "The tunnel name is a combination of RADIUS attributes Tunnel-Client-Auth-Id [90], Tunnel-Server-Auth-Id [91], and Tunnel-Assignment-Id [82]."
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
assisted-replication (Deterministic AR Replicator Policy Actions) | assisted-replication {
(fallback-replicator-ip fallback-replicator-ip | strict);
replicator-ip replicator-ip;;
} | [edit policy-options policy-statement name then] | Configure routing policy actions in a routing policy for an assisted replication (AR) leaf device to
deterministically steer multicast flows to specific AR replicator devices in an EVPN network.
Assign the routing policy to an EVPN instance on the AR leaf device using the deterministic-ar-policy
statement at the [edit ... | [
{
"name": "replicator-ip",
"desc": ""
},
{
"name": "replicator-ip",
"desc": "(Required) Set a preferred AR replicator to which the AR leaf device directs the multicast flows that match the conditions in the policy statement's from clause. The replicator-ip parameter is the secondary loopback add... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R2. | [
"Deterministic Load Balancing and Traffic Steering to AR Replicators",
"Routing Policy Match Conditions",
"Actions in Routing Policy Terms"
] |
assisted-replication | assisted-replication {
leaf {
replicator-activation-delay seconds;
}
replicator {
inet ip;
vxlan-encapsulation-source-ip (assisted-replicator-ip | ingress-replication-ip | retain-
incoming-source-ip);
}
} | [edit logical-systems name routing-instances name protocols evpn],
[edit routing-instances name protocols evpn],
[edit protocols evpn] | Enable assisted replication (AR) in an EVPN network.
AR helps to optimize broadcast, unknown unicast, and multicast (BUM) traffic in EVPN networks. To
enable AR, you configure devices in the EVPN network to operate as AR replicator and AR leaf devices.
Use the statements in this hierarchy to define and set up AR repli... | [
{
"name": "leaf",
"desc": "Configure a device as an AR leaf device."
},
{
"name": "replicator",
"desc": "Configure a device as an AR replicator device. These statements and their options are explained in more detail separately."
}
] | routing | Statement introduced in Junos OS Release 18.4R2 and 19.4R1. | [
"Assisted Replication Multicast Optimization in EVPN Networks"
] |
associate-backup-pe-groups | associate-backup-pe-groups; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Enable an LSP to monitor the status of its destination PE router. You can configure multiple backup PE
router groups using the same router's address. Backup PE router groups provide ingress PE router
redundancy when point-to-multipoint LSPs are configured for multicast distribution. A failure of this LSP
indicates to a... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Enabling Point-to-Point LSPs to Monitor Egress PE Routers"
] |
associate-lsp | associate-lsp lsp-name {
from from-ip-address;
} | [edit protocols mpls label-switched-path lsp-name oam] | Configure associated bidirectional label-switched paths (LSPs) on the two ends of an LSP for sending
and receiving GAL and G-Ach OAM messages. | [
{
"name": "from from-ip-address",
"desc": "(Optional) Source address for the associated LSP configuration. If omitted, this is derived from the to address of the ingress LSP configuration."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring the MPLS Transport Profile for OAM"
] |
associate-profile | associate-profile {
dynamic-profile-name;
profile-variable-set profile-variable-set-name;
} | [edit routing-instances routing-instance-name protocols vpls],
[edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name],
[edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name neighbor
neighbor-id] | Associate a dynamic profile or a profile variable set with a VPLS instance. | [
{
"name": "dynamic-profile-name",
"desc": "Name of the dynamic profile to attach to this routing instance."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Attaching Dynamic Profiles to Routing Instances",
"Attaching Dynamic Profiles to Routing Instances for the Complex Configuration"
] |
association-timeout | association-timeout time-in-minutes; | [edit security sctp profile profile-name] | Use the association-timeout parameter to set the association timeout for Stream Control Transmission
Protocol (SCTP).
From Junos OS Release 20.4R1 onwards, the [edit security gprs sctp profile profile-name] hierarchy level
is replaced by [edit security sctp profile profile-name]. | [
{
"name": "time-in-minutes",
"desc": "Number of minutes of association time that elapse before the session is terminated. Range: 10 through 6000 (100 hours). Default: 300 minutes (5 hours)."
}
] | 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. The association timeout range increased in Junos OS
Release 12.1X45-D10. | [
"Understanding Stream Control Transmission Protocol",
"Understanding SCTP Behavior in Chassis Cluster"
] |
asymmetric-hold-time | asymmetric-hold-time; | [edit protocols vrrp] | Configure a VRRP primary to fail over to a backup immediately—without waiting for the priority hold
time to expire—when a tracked route goes down. Otherwise, the primary waits for the hold time to
expire before it initiates a failover when a tracked interface or route goes down.
When the tracked interface or route come... | [] | 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 Asymmetric Hold Time for VRRP Routers"
] |
asymmetric-lease-time (DHCP Overrides) | asymmetric-lease-time seconds; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit forwarding-options dhcp-relay group group-name interface interface-name overrides],
[edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name ov... | Set an asymmetric lease time for an address that is sent to the DHCP client instead of the actual lease
time granted by the DHCP local server. The asymmetric lease time is shorter than the granted lease.
Asymmetric leases require the DHCP client to renew the lease more frequently, at shorter intervals. If
the client do... | [
{
"name": "seconds",
"desc": "Length of the short lease duration for the DHCPv4 client. Range: 600 through 65,534"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 17.1. | [
"DHCP Asymmetric Leasing Overview",
"Configuring DHCP Asymmetric Leasing"
] |
asymmetric-prefix-lease-time (DHCP Overrides) | asymmetric-prefix-lease-time seconds; | [edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name interface interface-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6],
[edit logical-s... | Set an asymmetric lease time for an address that is sent to the DHCPv6 client instead of the actual lease
time granted by the DHCP local server. The asymmetric lease time is shorter than the granted lease.
Asymmetric leases require the DHCP client to renew the lease more frequently, at shorter intervals. If
the client ... | [
{
"name": "seconds",
"desc": "Length of the short lease duration for the DHCPv6 client. Range: 600 through 65,534"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 17.1. | [
"DHCP Asymmetric Leasing Overview",
"Configuring DHCP Asymmetric Leasing"
] |
asynchronous-notification | (asynchronous-notification | no-asynchronous-notification); | [edit interfaces ge-fpc/pic/port gigether-options] | The asynchronous-notification feature allows supported interfaces to generate and transfer link down
alarms. This feature triggers the laser off (LOS) signal on an interface based on specific events and
conditions and sends the LOS alarm to its peer (CE).
When you configure the asynchronous-notification knob on an inte... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Gigabit Ethernet Notification of Link Down Alarm Overview",
"Configuring Gigabit Ethernet Notification of Link Down Alarm"
] |
atm-options | atm-options {
cell-bundle-size cells;
ilmi;
linear-red-profiles profile-name {
high-plp-max-threshold percent;
low-plp-max-threshold percent;
queue-depth cells high-plp-threshold percent low-plp-threshold percent;
}
mpls {
pop-all-labels {
required-depth n... | [edit interfaces interface-name] | Configure ATM-specific physical interface properties.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details.
NOTE: Certain options apply only to specific platforms. | [] | 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 Encapsulations Overview",
"multipoint-destination",
"shaping"
] |
attach | attach {
zone zone-name;
} | [edit security address-book book-name] | Attach a security zone to an address book. You do not need to attach a security zone to the global
address book. The global address book is available by default. | [
{
"name": "zone zone-name",
"desc": "Name of a security zone to be attached to the address book."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Address Books",
"Understanding Address Sets"
] |
attack-threshold | attack-threshold number; | [edit security screen ids-option screen-name tcp syn-flood] | Define the number of SYN packets per second required to trigger the SYN proxy response. | [
{
"name": "number",
"desc": "Number of SYN packets per second required to trigger the SYN proxy response."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
attack-type (Security Anomaly) | attack-type {
anomaly {
direction (Security Custom Attack) (any | client-to-server | server-to-client);
service service-name;
shellcode (all | intel | no-shellcode | sparc);
test test-condition;
}
} | [edit security idp custom-attack attack-name] | Specify the type of attack. | [] | 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. | [] |
attack-type (Security Chain) | attack-type {
chain {
expression boolean-expression;
member (Security IDP) member-name {
attack-type {
(anomaly ...same statements as in [edit security idp custom-attack attack-name
attack-type anomaly] hierarchy level | signature ...same statements as in [edit security ... | [edit security idp custom-attack attack-name] | Specify the type of attack.
NOTE: In a chain attack, you can configure multiple member attacks.
In an attack, under protocol binding TCP/UDP, you can specify multiple ranges of ports. | [] | 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. | [] |
attack-type (Security IDP) | attack-type {
anomaly {
direction (Security Custom Attack) (any | client-to-server | server-to-client);
shellcode (all | intel |no-shellcode | sparc);
test-condition condition-name;
}
signature (Security IDP) {
context context-name;
direction (Security Custom Attack) (any | client-to-server | serve... | [edit security idp custom-attack attack-name attack-type chain member member-name] | Specify the type of attack. | [] | 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. | [] |
attack-type (Security Signature) | attack-type {
signature (Security IDP) {
context context-name;
direction (any | client-to-server | server-to-client);
negate;
pattern signature-pattern;
pattern-pcre signature-pattern-pcre;
protocol (Security IDP Signature Attack) {
icmp {
... | [edit security idp custom-attack attack-name] | Specify the type of attack. | [] | 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. | [] |
attacks (Security Exempt Rulebase) | attacks {
custom-attack-group [attack-group-name];
custom-attack [attack-name];
dynamic-attack-group [attack-group-name];
predefined-attack-groups [attack-group-name];
predefined-attacks [attack-name];
} | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match] | Specify the attacks that you do not want the device to match in the monitored network traffic. Each
attack is defined as an attack object, which represents a known pattern of attack. | [] | 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. | [] |
attacks (Security IPS Rulebase) | attacks {
custom-attack-group [attack-group-name];
custom-attacks [attack-name];
dynamic-attack-group [attack-group-name];
predefined-attack-groups [attack-group-name];
predefined-attacks [attack-name];
} | [edit security idp idp-policy policy-name rulebase-ips rule rule-name match] | Specify the attacks you want the device to match in the monitored network traffic. Each attack is
defined as an attack object, which represents a known pattern of attack. | [] | 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. | [] |
attempts (DHCP Local Server) | attempts attempt-count; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server reconfigure],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 reconfigure],
[edit logical-systems logical-system-name routing-i... | Configure how many attempts are made to reconfigure all DHCP clients or only the DHCP clients
serviced by the specified group of interfaces before reconfiguration is considered to have failed. A group
configuration takes precedence over a DHCP local server configuration. | [
{
"name": "attempt-count",
"desc": "Maximum number of attempts."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Support at the [edit ... dhcpv6 ...] hierarchy levels introduced in Junos OS Release 10.4. | [
"Configuring Dynamic Reconfiguration of Extended Local Server Clients Overview",
"Configuring Dynamic Reconfiguration Attempts for DHCP Clients"
] |
attribute | attribute name {
code numeric-code;
vendor-id vendor-id;
format {
integer {
equals {
value;
}
greater-than value;
less-than value;
}
string {
equals {
value;
}
has-pref... | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify a custom RADIUS attribute for the incoming RADIUS request from the subscriber. You can
configure up to five attributes.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected. | [
{
"name": "name",
"desc": "Name for the attribute. Range: 1 through 50 alphanumeric characters. Allowed characters are [a-z, A-Z, 0-9]"
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
attributes (Access-Line Rate Adjustment) | attributes {
preference (dsl | pon);
} | [edit system access-line] | Selects the set of access line attributes (TLVs) that is saved and processed when the router receives both
DSL TLVs and PON TLVs in ANCP port status messages or in PPPoE-IA tags. The default line type is
PON. You select the dsl options to prefer the DSL TLVs. For example, you might do this when the PON
TLVs are unrelia... | [
{
"name": "preference dsl",
"desc": "Specifies that the router saves and processes DSL TLVs from the DSL-Line-Attributes TLV 0x04. The router discards the PON-Access-Line-Attributes TLV (0x12) and the PON TLVs that it contains."
},
{
"name": "preference",
"desc": ""
},
{
"name": "pon",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R1. | [
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Neighbors and Operations"
] |
attributes (Diameter Gx Profiles) | attributes {
exclude {
an-gw-address;
default-eps-bearer-qos;
packet-filter-information;
packet-filter-operation;
rat-type;
}
include {
gx-capability-list;
rule-suggestion;
}
} | [edit unified-edge diameter-profiles gx-profile profile-name] | Configure attribute-value pairs (AVPs) that are excluded from or included in the credit control request
(CCR) messages between the MX Series router and the policy and charging enforcement function
(PCEF).
The remaining statements are explained separately. See CLI Explorer. | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
attributes (JSRC Attributes) | attributes {
exclude {
user-name [ authorization-request | provisioning-request ];
}
}
} | [edit access profile profile-name jsrc] | Specify how the router processes Diameter attributes.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 14.2. | [
"Excluding AVPs from Diameter Messages for JSRC",
"Understanding JSRC-SAE Interactions"
] |
attributes (RADIUS Attributes) | attributes {
exclude {
attribute-name packet-type;
standard-attribute number {
packet-type [ access-request | accounting-off | accounting-on | accounting-start |
accounting-stop ];
}
vendor-id id-number {
vendor-attribute vsa-number {
packet-... | [edit access profile profile-name radius] | Specify how the router or switch processes RADIUS attributes. | [
{
"name": "\"exclude\"",
"desc": ""
},
{
"name": "on page",
"desc": "Configure the router or switch to exclude the specified attributes from being sent in the specified type of RADIUS message. Exclusion can be useful, for example, for attributes that do not change values over the lifetime of a s... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"RADIUS Servers and Parameters for Subscriber Access",
"Standard and Vendor-Specific RADIUS Attributes"
] |
attributes-match (Event Policy) | attributes-match {
event1.attribute-name equals event2.attribute-name;
event.attribute-name matches regular-expression;
event1.attribute-name starts-with event2.attribute-name;
} | [edit event-options policy policy-name] | Execute an event policy only if the attributes of two events are correlated or if the attribute of one event
matches a regular expression. By configuring an event policy to take an event's attributes into account in
addition to the event itself, you can configure more precise event policy matching.
The events reference... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Use Correlated Events to Trigger an Event Policy",
"Use Regular Expressions to Refine the Set of Events That Trigger a Policy"
] |
audible (Security Alarms) | audible {
continuous;
} | [edit security alarms] | Configure alarm to beep when a new security alarm is enabled. | [
{
"name": "continuous",
"desc": "Specify alarm to keep beeping until all security alarms are cleared."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 11.2. | [
"Security Policies Overview"
] |
auth-entry | auth-entry {
maximum amount;
reserved amount;
} | [edit system security-profile] | Specify the number of firewall authentication entries that user logical system administrators and primary
logical system administrators can configure for their logical systems if the security profile is bound to the
logical systems.
The primary administrator:
•
uses security profiles to provision logical systems with r... | [
{
"name": "maximum amount",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its"
},
{
"name": "are available",
"desc": "that is, if they are not allocated to other logical systems. The maximum allowed quota"
},
{
"name": "reserved amount",
"desc... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems Security Profiles (Primary Administrators Only)"
] |
auth-only-browser | auth-only-browser <auth-user-agent [user-agent] >;
auth-only-browser; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication pass-through]
[edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication user-firewall] | Configure firewall authentication to ignore non-browser HTTP/HTTPS traffic. This feature allows you to
ensure that unauthenticated users issuing access requests through HTTP/HTTPS browsers are
presented with a captive portal interface to allow them to authenticate. By default, firewall
authentication responds to all HT... | [
{
"name": "auth-user-",
"desc": ""
},
{
"name": "agent",
"desc": ""
},
{
"name": "user-agent",
"desc": "Allow the SRX Series device to use the user-agent strings that you specify to verify that the browser traffic is HTTP/HTTPS traffic. Firewall authentication checks the strings agai... | 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-D90. | [
"Understanding SRX Series Assured Captive Portal Support for Unauthenticated Browser Users"
] |
auth-user-agent | auth-user-agent [user-agent]; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication pass-through]
[edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication pass-through auth-only-browser]
[edit security policies from-zone zone... | Specify a user-agent value to be used to verify that the user’s browser traffic is HTTP/HTTPS traffic.
Firewall authentication checks the value against the User-Agent field in the browser header. For
example, the auth-user-agent parameter might specify Opera1 to be verified against the brower’s User-
Agent field for a ... | [
{
"name": "user-agent",
"desc": "A string to be matched against values specified in the browser’s User-Agent header field that identifies the traffic as HTTP/HTTPS browser traffic. You can specify only one user-agent value for a security policy configuration. The value must not contain spaces. You do not ne... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | [
"Understanding SRX Series Assured Captive Portal Support for Unauthenticated Browser Users"
] | |
authentication (AAA Profile) | authentication {
network-element network-element-name;
} | [edit unified-edge aaa profiles aaa-profile-name radius] | Specify the network element providing policy management for TDF subscribers. The network element
must already be defined at the [edit access radius] hierarchy level.
The remaining statement is explained separately. See CLI Explorer. | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring an AAA Profile",
"Understanding AAA Profiles",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
authentication (BGP BFD Liveness Detection) | authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
} | [edit logical-systems name protocols bgp bfd-liveness-detection],
[edit logical-systems name protocols bgp group name bfd-liveness-detection],
[edit logical-systems name protocols bgp group name neighbor address bfd-liveness-detection],
[edit logical-systems name routing-instances name protocols bgp bfd-liveness-detect... | Specify the router and route authentication to mitigate the risk of being attacked by a machine or router
that has been configured to share incorrect routing information with another router. Router and route
authentication enables routers to share information only if they can verify that they are talking to a
trusted s... | [
{
"name": "authentication",
"desc": ""
},
{
"name": "algorithm-name",
"desc": "Configure the algorithm used to authenticate the specified BFD session. Values: Specify one of these algorithm names:"
},
{
"name": "simple-password",
"desc": "Plain-text password. One to 16 bytes of plai... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection",
"Example: Configuring BFD Authentication for Securing Static Routes",
"Example: Configuring Router Authentication for BGP",
"Example: Configuring BFD on Internal BGP Peer Sessions",
"Example: Configuring EBGP Multihop Session... |
authentication (Demux) | authentication {
password password-string;
username-include {
auth-server-realm realm-string;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
source-address;
user-prefix user-prefix-string;
}
} | [edit interfaces interface-name unit unit-number demux inet auto-configure address-ranges]
[edit interfaces interface-name unit unit-number demux inet6 auto-configure address-ranges] | Specify the authentication parameters for the demultiplexing (demux) interface options. The remaining
statement is explained separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview",
"Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles"
] |
authentication (DHCP Local Server) | authentication {
password password-string;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name-string;
interface-description (device-interface | logical-interface);
interface-name ;
logical-system-name;
... | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dual-stack-group dual-stack-group-name],
[edit system services dhcp-local-server dhcpv6],
[edit system services dhcp-local-server dhcpv6 group group-name],
[edit system services dhcp-local-server group group-name],
[edit logical-systems l... | Configure the parameters the router sends to the external AAA server. A group configuration takes
precedence over a global DHCP relay or DHCP local server configuration.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for detail... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
authentication (DHCP Relay Agent) | authentication {
password password-string;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name-string;
interface-description (device-interface | logical-interface);
interface-name;
logical-system-name;
... | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit forwarding-options dhcp-relay group group-name],
[edit logical-systems logical-system-name f... | Configure the parameters the router sends to the external AAA server. A group configuration takes
precedence over a global DHCP relay configuration. Use the statement at the [edit...dhcpv6] hierarchy
levels to configure DHCPv6 support.
The remaining statements are explained separately. Search for a statement in CLI Exp... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Specifying Authentication Support"
] |
authentication (LAG) | authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
} | [edit interfaces aex aggregated-ether-options bfd-liveness-detection] | Configure the authentication criteria of the BFD session for aggregated Ethernet interfaces. | [
{
"name": "algorithm",
"desc": ""
},
{
"name": "algorithm-name",
"desc": "Specify the algorithm to be used to authenticate the BFD session. You can use one of"
},
{
"name": "the following algorithms for authentication:",
"desc": ""
},
{
"name": "keyed-md5",
"desc": ""
}... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Configuring Micro BFD Sessions for LAG",
"Example: Configuring Independent Micro BFD Sessions for LAG",
"Understanding Independent Micro BFD Sessions for LAG"
] |
authentication (Protocols OSPF) | authentication {
md5 key-identifier {
key key-value;
start-time YYYY-MM-DD.hh:mm;
}
simple-password key;
multi-active-md5 key-identifier {
key key-value delete-if-not-inuse;
}
keychain keychain;} | [edit logical-systems logical-system-name protocols ospf area area-id interface interface-name],
[edit logical-systems logical-system-name protocols ospf area area-id virtual-link],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id interface interface-name],... | Configure an authentication key (password). Neighboring routers use the password to verify the
authenticity of packets sent from this interface.
All routers that are connected to the same IP subnet must use the same authentication scheme and
password.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "simple-password",
"desc": ""
},
{
"name": "key",
"desc": "Configures a simple authentication password string, defined by key."
},
{
"name": "md5",
"desc": "Configure an MD5 password."
},
{
"name": "key-identifier",
"desc": "MD5 key identifier. Range is from 0 t... | 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.
The option keychain keychain introduced in Junos OS and Junos OS Evolved Release 23.4R1. | [
"Understanding OSPFv2 Authentication",
"Example: Configuring MD5 Authentication for OSPFv2 Exchanges",
"Example: Configuring a Transition of MD5 Keys on an OSPFv2 Interface",
"Example: Configuring Simple Authentication for OSPFv2 Exchanges"
] |
authentication (Protocols PIM) | authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
} | [edit protocols pim interface interface-name family (inet | inet6) bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface family (inet | inet6)
interface-name bfd-liveness-detection] | Configure the algorithm, security keychain, and level of authentication for BFD sessions running on PIM
interfaces.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring BFD for PIM",
"Configuring BFD Authentication for PIM",
"Understanding Bidirectional Forwarding Detection Authentication for PIM"
] |
authentication (Security Alarms) | authentication failures; | [edit security alarms potential-violation] | Raise a security alarm when the device or switch detects a specified number of authentication failures
(bad password attempts) before an alarm is raised.
This value must be equal to or less than the tries-before-disconnect setting at the [edit system login retry-
options] hierarchy level; otherwise, the login session e... | [
{
"name": "failures",
"desc": "Number of authentication failures that causes an alarm to be raised."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Security Policies Overview"
] |
authentication (Security IPsec) | authentication {
algorithm (hmac-sha1-96 | hmac-sha2-256);
key (ascii-text key | hexadecimal key);
} | [edit security ipsec security-association sa-name manual direction (inbound | outbound | bi-
directional)] | Configure IP Security (IPsec) authentication parameters for manual security association (SA).
NOTE: The hexadecimal format must be used for the encryption key to be FIPS
compliant. The hexadecimal keys provide maximum key strength. | [
{
"name": "algorithm",
"desc": "Hash algorithm that authenticates packet data. It can be one of the following:"
},
{
"name": "hmac-md5-96",
"desc": "Produces a 128-bit digest."
},
{
"name": "hmac-sha1-96",
"desc": "Produces a 160-bit digest."
},
{
"name": "key",
"desc": "... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Manual IPsec Security Associations for an ES PIC"
] |
authentication (services) | authentication {
algorithm (hmac-md5-96 | hmac-sha1-96 | hmac-sha-256-128);
key (ascii-text key | hexadecimal key);
} | [edit services ipsec-vpn rule rule-name term term-name then manual direction direction] | Configure IPsec authentication parameters for a manual security association (SA). | [
{
"name": "algorithm",
"desc": "Hash algorithm that authenticates packet data. The algorithm can be one of the following:"
},
{
"name": "hmac-md5-96",
"desc": "Produces a 128-bit digest."
},
{
"name": "hmac-sha1-96",
"desc": "Produces a 160-bit digest."
},
{
"name": "hmac-sha... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Security Associations"
] |
authentication (Static and Dynamic PPP) | authentication [ authentication-protocols ]; | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit interfaces pp0 unit unit-number ppp-options] | Specify the order in which the router tries to negotiate PPP authentication protocols when verifying
that a PPP client can access the network. By default, the router tries to negotiate Challenge Handshake
Authentication Protocol (CHAP) authentication first, and then tries Password Authentication Protocol
(PAP) authenti... | [
{
"name": "authentication-protocols",
"desc": "One or both of the following PPP authentication protocols:"
},
{
"name": "chap",
"desc": "Challenge Handshake Authentication Protocol"
},
{
"name": "pap",
"desc": "Password Authentication Protocol"
}
] | 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. | [
"PPP Network Control Protocol Negotiation"
] |
authentication (Static Subscribers) | authentication {
password password-string;
username-include {
delimiter delimiter-character;
domain-name domain-name;
interface;
logical-system-name;
routing-instance-name;
user-prefix user-prefix-string;
vlan-tags;
}
} | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name],
[edit logical-systems logical-system-name system services sta... | Specify the authentication parameters that trigger the Access-Request message to AAA for all static
subscribers on interfaces configured at the [edit system services static-subscribers interface] hierarchy
level, or for the static subscribers in a specific group. The group version of this statement overrides the
global... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Configuring the Static Subscriber Global Authentication Password",
"Configuring the Static Subscriber Group Authentication Password"
] |
authentication | authentication {
packet-types [packet-types];
password password-string;
username-include {
circuit-id;
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-18;
option-37;
opti... | [edit interfaces interface-name auto-configure vlan-ranges],
[edit interfaces interface-name auto-configure stacked-vlan-ranges] | Specify the authentication parameters that trigger the Access-Request message to AAA for the
interface.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Subscribers over Static Interfaces Configuration Overview",
"Configuring the Static Subscriber Global Authentication Password",
"Configuring a Username for Authentication of Out-of-Band Triggered Dynamic VLANs",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] |
authentication-algorithm (Security IKE) | authentication-algorithm (md5 | sha1 | sha-256 | sha-384); | [edit security ike proposal ike-proposal-name] | Configure the Internet Key Exchange (IKE) authentication algorithm. | [
{
"name": "authentication-algorithm",
"desc": "Hash algorithm that authenticates packet data. It can be one of two algorithms:"
},
{
"name": "md5",
"desc": "Produces a 128-bit digest."
},
{
"name": "sha1",
"desc": "Produces a 160-bit digest."
},
{
"name": "sha256",
"desc"... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Authentication Algorithm for an IKE Proposal"
] |
authentication-algorithm (Security IPsec) | authentication-algorithm (hmac-md5-96 | hmac-sha1-96); | [edit security ipsec proposal ipsec-proposal-name] | Configure the IPsec authentication algorithm.
NOTE: Keep the following points in mind when you configure the authentication
algorithm in an IPsec proposal:
•
When both ends of an IPsec VPN tunnel contain the same IKE proposal but different
IPsec proposals, an error occurs and the tunnel is not established in this scena... | [
{
"name": "authentication-algorithm",
"desc": "Hash algorithm that authenticates packet data. It can be one of two algorithms:"
},
{
"name": "hmac-md5-96",
"desc": "Produces a 128-bit digest."
},
{
"name": "hmac-sha1-96",
"desc": "Produces a 160-bit digest."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Authentication Algorithm for an IPsec Proposal"
] |
authentication-algorithm (Services IKE) | authentication-algorithm (md5 | sha1 | sha-256); | [edit services ipsec-vpn ike proposal proposal-name] | Configure the Internet Key Exchange (IKE) hash algorithm that authenticates packet data. | [
{
"name": "md5",
"desc": "Produces a 128-bit digest."
},
{
"name": "sha1",
"desc": "Produces a 160-bit digest."
},
{
"name": "sha-256",
"desc": "Produces a 256-bit digest."
},
{
"name": "sha-384",
"desc": "Produces a 384-bit digest."
}
] | 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.
sha-256 option added in Junos OS Release 7.6. | [
"Configuring IKE Proposals"
] |
authentication-algorithm (Services IPsec) | authentication-algorithm (hmac-md5-96 | hmac-sha-256-128 | hmac-sha1-96); | [edit services ipsec-vpn ipsec proposal ipsec-proposal-name] | Configure the IPsec hash algorithm that authenticates packet data.
NOTE: Keep the following points in mind when you configure the authentication
algorithm in an IPsec proposal:
•
When both ends of an IPsec VPN tunnel contain the same IKE proposal but different
IPsec proposals, an error occurs and the tunnel is not esta... | [
{
"name": "hmac-md5-96",
"desc": "Produces a 128-bit digest."
},
{
"name": "hmac-sha-256-128",
"desc": "Produces a 256-bit digest."
},
{
"name": "hmac-sha1-96",
"desc": "Produces a 160-bit digest."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Proposals"
] |
authentication-algorithm | authentication-algorithm algorithm; | [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 protocols ldp session session-address],
[edit logical... | Configure an authentication algorithm type.
NOTE: Keep the following points in mind when you configure the authentication
algorithm in an IPsec proposal:
•
When both ends of an IPsec VPN tunnel contain the same IKE proposal but different
IPsec proposals, an error occurs and the tunnel is not established in this scenari... | [
{
"name": "algorithm",
"desc": "Specify one of the following types of authentication algorithms:"
},
{
"name": "aes-128-cmac-96",
"desc": "Cipher-based message authentication code (AES128, 96 bits)."
},
{
"name": "hmac-sha-1-96",
"desc": "Hash-based message authentication code (SHA1,... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Statement introduced for BGP in Junos OS Release 8.0.
Statement introduced for BMP in Junos OS Release 13.2X51-D15 for the QFX Series.
Statement introduced for BMP in Junos OS Release 13.3. | [
"Example: Configuring Router Authentication for BGP",
"Configuring BGP Monitoring Protocol Version 3"
] |
authentication-entry-timeout (Identity Management Advanced Query) | authentication-entry-timeout time-out-in-minutes; | [edit services user-identification identity-management] | Configure the time-out for the user identity authentication entries. You configure this parameter as part
of the advanced user identity query feature for SRX Series Firewalls.
The advanced user identity query feature for SRX Series Firewalls relies on the Juniper Identity
Management Service (JIMS), a centralized ident... | [
{
"name": "time-out-in-minutes",
"desc": "The amount of time after which a user identity authentication entry expires. Range: 0 or 10 through 1440 minutes. Specification of 0 indicates no time-out. Default: 60 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 Advanced Query Feature for Obtaining User Identity Information from JIMS"
] |
authentication-entry-timeout (Services User Identification) | authentication-entry-timeout minutes; | [edit services user-identification authentication-source (Services User Identification ClearPass)
aruba-clearpass] | Configure for the integrated ClearPass authentication and enforcement feature the timeout interval
after which idle entries in the ClearPass authentication table expire. | [
{
"name": "minutes",
"desc": "Timeout interval. The timeout interval begins from when the user authentication entry is added to the ClearPass authentication table. If a value of 0 is specified, the entries will never expire. Range: 10 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 12.3X48-D30. | [] |
authentication-key (ICCP) | authentication-key key; | [edit protocols iccp],
[edit protocols iccp peer peer-IP-address] | Specify the authentication key (password). The QFX3500 and MX Series devices use this password to
verify the authenticity of packets sent from the peers hosting a multichassis link aggregation group (MC-
LAG). Peer-level authentication takes precedence over global-level authentication.
Inter-Chassis Control Protocol (I... | [
{
"name": "key",
"desc": "Authentication password. It can be 1 through 16 contiguous digits or letters. Separate decimal"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
authentication-key (Protocols BGP and BMP) | authentication-key key; | [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... | Configure an MD5 authentication key (password). Neighboring routing devices use the same password
to verify the authenticity of BGP packets sent from this system. | [
{
"name": "key",
"desc": "Authentication password. It can be up to 126 characters. Characters can include any ASCII strings."
}
] | 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.
Statement introduced for BMP in Junos OS Release 13.2X51-D15 for the QFX Series.
Statement introduced for BMP version 3 in Junos OS Release 13.3. | [
"Example: Configuring Router Authentication for BGP",
"Configuring BGP Monitoring Protocol Version 3"
] |
authentication-key (Protocols LDP) | authentication-key md5-authentication-key; | [edit logical-systems logical-system-name protocols ldp session address]
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp
session address]
[edit protocols ldp session address]
[edit protocols ldp session-group address]
[edit routing-instances routing-instance-name protoc... | Configure the MD5 authentication signature. The maximum length of the authentication signature is 69
characters. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the TCP MD5 Signature for LDP Sessions"
] |
authentication-key (Protocols MSDP) | authentication-key peer-key; | [edit logical-systems logical-system-name protocols msdp group group-name peer address],
[edit logical-systems logical-system-name protocols msdp peer address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols msdp
group group-name peer address],
[edit logical-systems logical... | Associate a Message Digest 5 (MD5) signature option authentication key with an MSDP peering session.
Default
If you do not include this statement, the routing device accepts any valid MSDP messages from the peer
address. | [
{
"name": "peer-key",
"desc": "MD5 authentication key. The peer key can be a text string up to 16 letters and digits long."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring MSDP in a Routing Instance"
] |
authentication-key (Protocols RIP) | authentication-key password; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name routing-instances routin... | Require authentication for RIP route queries received on an interface. | [
{
"name": "password",
"desc": "Authentication password. If the password does not match, the packet is rejected. The password"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring Route Authentication for RIP using single MD5 key"
] |
authentication-key (Protocols RSVP) | authentication-key key; | [edit logical-systems logical-system-name protocols rsvp interface interface-name],
[edit logical-systems logical-system-name protocols rsvp peer-interface peer-interface-name],
[edit protocols rsvp],
[edit protocols rsvp interface interface-name],
[edit protocols rsvp peer-interface peer-interface-name] | Authentication key (password). Neighboring routers use the password to verify the authenticity of
packets sent from this interface or peer interface. To authenticate node hellos or remote messages
between the Point of Local Repair (PLR) to the Merge Point (MP), enable authentication-key at the [edit
protocols rsvp] hie... | [
{
"name": "key",
"desc": "Authentication password. It can be 1 through 16 contiguous digits or letters. Separate decimal digits"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring RSVP Authentication"
] |
authentication-key (SNMP) | authentication-key authentication-key; | [edit snmp v3 usm local-engine user username authentication-md5],
[edit snmp v3 usm local-engine user username authentication-sha],
[edit snmp v3 usm remote-engine engine-id user username authentication-md5],
[edit snmp v3 usm remote-engine engine-id user username authentication-sha] | Configure the key for user authentication, if you know it, instead of entering a cleartext password. The
encrypted version of a password is known as a key. | [
{
"name": "authentication-key",
"desc": "The encrypted version from the cleartext password."
}
] | 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. | [] |
authentication-key | authentication-key key; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address vrrp-group group-id] | Configure a Virtual Router Redundancy Protocol (VRRP) IPv4 authentication key. You also must specify a
VRRP authentication scheme by including the authentication-type statement.
All devices in the VRRP group must use the same authentication scheme and password.
NOTE: When VRRPv3 is enabled, the authentication-type and ... | [
{
"name": "key",
"desc": "Authentication password. For simple authentication, it can be 1 through 8 characters long. 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. | [
"Configuring VRRP Authentication (IPv4 Only)",
"version-3",
"Understanding VRRP on SRX Series Devices",
"Example: Configuring VRRP/VRRPv3 on Chassis Cluster Redundant Ethernet Interfaces"
] |
authentication-key-chain (Protocols BGP and BMP) | authentication-key-chain key-chain; | [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... | Apply and enable an authentication keychain to the routing device. Note that the referenced key chain
must be defined. When configuring the authentication key update feature for BGP, you cannot commit
the 0.0.0.0/allow statement with authentication keys or key chains. The CLI issues a warning and fails to
commit the co... | [
{
"name": "key-chain",
"desc": "Authentication keychain name. It can be up to 126 characters. Characters can include any"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0.
Statement introduced for BMP in Junos OS Release 13.2X51-D15 for the QFX Series.
Statement introduced for BMP in Junos OS Release 13.3. | [
"Example: Configuring Router Authentication for BGP",
"Example: Configuring BFD Authentication for Securing Static Routes",
"Configuring the Authentication Key Update Mechanism for BGP and LDP Routing Protocols",
"Configuring BGP Monitoring Protocol Version 3"
] |
authentication-key-chain (Protocols LDP) | authentication-key-chain key-chain; | [edit logical-systems name protocols ldp session address],
[edit logical-systems name routing-instances instance-name protocols ldp session address],
[edit protocols ldp session address],
[edit routing-instances instance-name protocols ldp session address] | Apply and enable an authentication keychain to the routing device. Note that the referenced key chain
must be defined. When configuring the authentication key update mechanism for LDP, you cannot
commit the 0.0.0.0/allow statement with authentication keys or key chains. The CLI issues a warning and
fails to commit such... | [
{
"name": "key-chain",
"desc": "Authentication keychain name. It can be up to 126 characters. Characters can include any"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring the Authentication Key Update Mechanism for BGP and LDP Routing Protocols",
"Configuring Miscellaneous LDP Properties"
] |
authentication-key-chain (TWAMP) | authentication-key-chain identifier {
key-id identifier {
secret password-string;
}
} | [edit services rpm twamp server] | Apply and enable an authentication key chain to the routing device. Note that the referenced key chain
must be defined. When configuring the authentication key update mechanism for TWAMP, you cannot
commit the 0.0.0.0/allow statement with authentication keys or key chains. The CLI issues a warning and
fails to commit s... | [
{
"name": "identifier",
"desc": "Authentication key chain name. It can be up to 126 characters. Characters can include any"
},
{
"name": "password-string",
"desc": "Authentication key, consisting of 1 through 8 ASCII characters. If the key contains"
}
] | 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. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
authentication-key-chains (TCP-AO) | authentication-key-chains {
key-chain keychain-name {
key key ID {
secret secretpassword;
start-time yyyy-mm-dd.hh:mm:ss;
algorithm ao;
ao-attribute {
send-id send ID;
recv-id receive ID;
cryptographic-al... | [edit security] | key-chain
Enter a unique name for the keychain. For example, new-auth-key.
key
Enter a unique key ID for each key. In a key-chain, keys are numbered sequentially, from
key0 through key63.
secret
Enter a unique secret key or password for each key. Use any alphanumeric characters
without any space. Once configured, it wi... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3R1. | [
"TCP Authentication Option (TCP-AO)"
] |
authentication-key-chains | authentication-key-chains {
key-chain key-chain-name {
description text-string;
key key {
algorithm (md5 | hmac-sha-1);
key-name authentication-key-name
algorithm (hmac-sha2-224 | hmac-sha2-256| hmac-sha2-384 | hmac-sha2-512);
options (basic | isis-enh... | [edit security]
[edit routing-instances vrf-name protocols bgp group group-name] | Configure authentication key updates for the Border Gateway Protocol (BGP) and the Label Distribution
Protocol (LDP) routing protocols, the Bidirectional Forwarding Detection (BFD) protocol, the
Intermediate System-to-Intermediate System (IS-IS) protocol, and the Open Shortest Path First (OSPF)
protocol. When the authe... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Support for the BFD protocol introduced in Junos OS Release 9.6.
Support for the BFD protocol introduced in Junos OS Release 9.6 for EX Series switches.
Support for IS-IS introduced in JUNOS OS Release 11.2.
Support for HMAC-SHA2 authentication algorithm that includes HMAC-... | [
"BGP Route Authentication",
"Configuring the Authentication Key Update Mechanism for BGP and LDP Routing Protocols",
"Example: Configuring BFD Authentication for Securing Static Routes",
"Example: Configuring Hitless Authentication Key Rollover for IS-IS",
"Configuring Media Access Control Security (MACsec)... |
authentication-md5 | authentication-md5 {
(authentication-key authentication-key | authentication-password authentication-password);
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure MD5 as the authentication type for the SNMPv3 user.
NOTE: You can only configure one authentication type for each SNMPv3 user.
For authentication, you can either enter a password in clear text, which is immediately encrypted, or, if
you already have the encrypted version (known as a key), enter the key direct... | [] | 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 MD5 Authentication"
] |
authentication-method (Interfaces) | authentication-method (pap | chap | none); | [edit interfaces interface-name cellular-options gsm-options profiles profile-name] | Specify the authentication method for connection to a Global System for Mobile Communications
(GSM) cellular network. | [
{
"name": "pap",
"desc": "Password Authentication Protocol."
},
{
"name": "chap",
"desc": "Challenge Handshake Authentication Protocol."
},
{
"name": "none",
"desc": "No authentication method is used."
}
] | 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. | [] |
authentication-method (services) | authentication-method (ecdsa-signatures-256 | ecdsa-signatures-384 | pre-shared-keys | rsa-
signatures); | [edit services ipsec-vpn ike proposal proposal-name] | Configure an IKE authentication method. | [
{
"name": "ecdsa-signatures-256",
"desc": "Elliptic Curve Digital Signature Algorithm (ECDSA) for 256-bit moduli. This can only be used on an MS-MPC or MS-MIC."
},
{
"name": "ecdsa-signatures-384",
"desc": "ECDSA for 384-bit moduli. This can only be used on an MS-MPC or MS-MIC."
},
{
"na... | 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.
ecdsa-signatures-256 and ecdsa-signatures-384 options added in Junos OS Release 17.3R1. | [
"Configuring IKE Proposals"
] |
authentication-method | authentication-method (dsa-signatures | pre-shared-keys | rsa-signatures); | [edit security ike proposal ike-proposal-name] | Configure the IKE authentication method. | [
{
"name": "dsa-signatures",
"desc": "Digital Signature Algorithm (DSA)"
},
{
"name": "rsa-signatures",
"desc": "A public key algorithm, which supports encryption and digital signatures"
},
{
"name": "pre-shared-keys",
"desc": "A key derived from an out-of-band mechanism; the key auth... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Manual IPsec Security Associations for an ES PIC"
] |
authentication-mode | authentication-mode (authenticated | encrypted | none); | [edit services rpm twamp server],
[edit services rpm twamp client control-connection control-client-name] | Specify the authentication or encryption mode support for the TWAMP test protocol. This statement is
required in the configuration; if no authentication or encryption is specified, you must set the value to
none. | [
{
"name": "authenticated",
"desc": "Authenticate all TWAMP packets. NOTE: This mode is supported only on TWAMP servers."
},
{
"name": "encrypted",
"desc": "Encrypt all TWAMP packets. NOTE: This mode is supported only on TWAMP servers."
},
{
"name": "none",
"desc": "Do not authenticat... | 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.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in Junos OS Release 15.1 for MX Series routers. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
authentication-none | authentication-none; | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure that there should be no authentication for the SNMPv3 user.
NOTE: You can configure only one authentication type for each SNMPv3 user. | [] | 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 No Authentication"
] |
authentication-order (Access Profile) | authentication-order [(none | ldap | password | radius | s6a | saml | secureid)]; | [edit access profile profile-name] | Configure the order of authentication, authorization, and accounting (AAA) methods to use while
sending authentication messages.
Default
Not enabled | [
{
"name": "none",
"desc": "No authentication for specified users."
},
{
"name": "ldap",
"desc": "Light weight directory access protocol."
},
{
"name": "password",
"desc": "Locally configured password in access profile."
},
{
"name": "radius",
"desc": "RADIUS authenticatio... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
none option introduced in Junos OS Release 20.3R1.
saml option added in Junos OS Release 24.4R1. | [
"Example: Connecting a RADIUS Server for 802.1X to an EX Series Switch",
"Configuring 802.1X RADIUS Accounting (CLI Procedure)",
"Example: Specifying RADIUS Server Connections on a Security Device",
"Ethernet Switching User Guide"
] |
authentication-order (Authenticator) | authentication-order [dot1x | mac-radius | captive-portal]; | [edit logical-systems name protocols dot1x authenticator
interface],
[edit protocols dot1x authenticator interface interface-name] | Configure the preferred order of authentication methods that the device will use when attempting to
authenticate a client. If multiple authentication methods are configured on a single interface, when one
authentication method fails, the device falls back to another method. You can configure the
authentication-order st... | [
{
"name": "captive-portal",
"desc": "Configure captive portal authentication in the order of authentication methods on the"
},
{
"name": "dot1x",
"desc": "Configure 802.1X authentication in the order of authentication methods on the interface."
},
{
"name": "mac-radius",
"desc": "Con... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3. | [
"Understanding Authentication on Switches",
"Configuring Flexible Authentication Order"
] |
authentication-order (System) | authentication-order [method1 method2...]; | [edit system] | Configure the order in which the software tries different user authentication methods when attempting
to authenticate a user. For each login attempt, the software tries the authentication methods in order,
starting with the first one, until the password matches.
Default
If you do not include the authentication-order st... | [
{
"name": "authentication-order [method1",
"desc": ""
},
{
"name": "method2...]",
"desc": "Specify the order in which the software tries different authentication methods when attempting to authenticate a user. Values: One or more of the following authentication methods listed in the order"
},... | 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. | [
"Junos OS User Authentication Methods"
] |
authentication-order | authentication-order [ authentication-methods ]; | [edit access profile profile-name] | Set the order in which AAA tries different authentication methods when verifying that a client can
access the router or switch. For each login attempt, AAA tries the authentication methods in order, from
first to last.
A given subscriber does not undergo both authentication and authorization as separate steps. When
bot... | [
{
"name": "authentication-methods",
"desc": "Ordered list of methods to use for authentication attempts. The list includes one or more of the following methods in any combination:"
},
{
"name": "nasreq",
"desc": "Verify subscribers using the Diameter-based Network Access Server"
},
{
"na... | 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.
none option added in Junos OS Release 11.2.
nasreq option added in Junos OS Release 16.1.
s6a option added in Junos OS Release 19.3R1. | [
"Example: Configuring CHAP Authentication with RADIUS",
"RADIUS Authentication and Accounting Basic Configuration",
"Example: Configure S6a Application"
] |
authentication-password | authentication-password authentication-password; | [edit snmp v3 usm local-engine user username authentication-md5],
[edit snmp v3 usm local-engine user username authentication-sha],
[edit snmp v3 usm remote-engine engine-id user username authentication-md5],
[edit snmp v3 usm remote-engine engine-id user username authentication-sha] | Configure the password for user authentication. | [
{
"name": "authentication-password",
"desc": "Password that a user enters. The password is then converted into a key that is"
}
] | 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 MD5 Authentication",
"Configuring SHA Authentication"
] |
authentication-protocol | authentication-protocol {
eap-md5;
eap-peap {
resume;
}
pap;
} | [edit logical-systems protocols dot1x authenticator interface interface-name mac-radius]
[edit protocols dot1x authenticator interface interface-name mac-radius] | Specify the protocol to be used by a supplicant to provide authentication credentials for MAC RADIUS
authentication. The protocols supported for MAC RADIUS authentication are EAP-MD5, which is the
default, Protected Extensible Authentication Protocol (EAP-PEAP), and Password Authentication
Protocol (PAP).
Default
If au... | [
{
"name": "eap-md5",
"desc": "Use the EAP-MD5 protocol for MAC RADIUS authentication. EAP-MD5 is an authentication method belonging to the Extensible Authentication Protocol (EAP) authentication framework. EAP-MD5 uses MD5 to hash the username and password. EAP-MD5 provides for a one-way client authenticati... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3.
eap-peap introduced in Junos OS Release 17.2R1. | [
"Understanding Authentication on Switches",
"Configuring 802.1X RADIUS Accounting (CLI Procedure)"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.