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 |
|---|---|---|---|---|---|---|---|
3gpp-imsi | 3gpp-imsi {
equals value;
has-prefix value;
has-suffix value;
matches value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP 3GPP-IMSI for the incoming RADIUS request from the subscriber.
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.
The remaining statements are explained separately. See CL... | [] | 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"
... |
802.3ad (EX and QFX Series) | 802.3ad ae{x;
lacp {
force-up;
(primary | backup);
}
port-priority;
} | [edit interfaces interface-name ether-options] | Specify the aggregated Ethernet logical interface number.
NOTE:
•
The "port-priority" on page 13405 statement is not supported on QFabric systems.
•
The "force-up" on page 7731 statement is not supported on QFX10002 switches. | [
{
"name": "aex",
"desc": "Name of the LAG. Aggregated Ethernet logical interface number."
},
{
"name": "backup",
"desc": "Designate the interface as the backup interface for link-protection mode."
},
{
"name": "primary",
"desc": "Designate the interface as the primary interface for l... | 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. | [
"Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis",
"Access Switch and an EX4200 Virtual Chassis Distribution Switch",
"Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between an EX4200",
"Virtual Chassis Access Switch and an EX4200 Virtual Ch... |
802.3ad | 802.3ad {
primary | backup;
ae interface-number ;
lacp {
port-priority priority-number;
}
link-index index-number
distribution-list distribution-list-number
} | [edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options] | Specify aggregated Ethernet logical interface number. | [
{
"name": "bundle",
"desc": "Join an aggregated Ethernet interface."
},
{
"name": "ae interface-number",
"desc": "Aggregated Ethernet logical interface number. For MX Series routers running Junos release 14.2R3 and later you can configure a maximum of 1000 aggregated interfaces. On MX2010 and MX... | 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.
primary and backup options added in Junos OS Release 8.3. | [
"Configuring an Aggregated Ethernet Interface",
"Configuring Aggregated Ethernet Link Protection"
] |
aaa clients (TDF) | aaa {
clients client-name;
apply-groups [group-names];
apply-groups-except [group-names];
} | [edit unified-edge gateways tdf gateway-name] | Specify the GGSN, PGW, or BNG RADIUS clients that can send RADIUS requests to a TDF gateway. | [
{
"name": "client-name",
"desc": "RADIUS client name that was previously configured at the [edit access radius clients] hierarchy level."
}
] | 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 RADIUS Clients That Send Accounting Requests for IP-Based Subscribers",
"Configuring a TDF Gateway"
] |
aaa | aaa {
access-profile access-profile {
config-payload-password config-payload-password;
}
client {
password;
username;
}
use-routing-instance-address;
no-push-to-identity-management;
} | [edit security ike gateway gateway-name] | Specify that extended authentication is performed in addition to IKE Phase 1 authentication for remote
users trying to access a VPN tunnel. This authentication can be through Extended Authentication
(XAuth) or Extensible Authentication Protocol (EAP). Include a previously created access profile,
configured with the ed... | [
{
"name": "access-profile",
"desc": ""
},
{
"name": "profile-name",
"desc": "Name of the previously created access profile to use for extended authentication for remote users trying to access a VPN."
},
{
"name": "config-payload-password",
"desc": "Specify common client password for ... | 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-D80.
config-payload-password option added in Junos OS Release 20.1R1.
no-push-to-identity-management option added in Junos OS Release 24.4R1. | [
"IPsec Overview"
] |
aaa-access-profile (L2TP LNS) | aaa-access-profile profile-name; | [edit services l2tp tunnel-group name],
[edit access profile profile-name client client-name l2tp] | Specify a AAA access profile that overrides the AAA access profile configured for the routing instance
with the access-profile statement. You can configure a profile to specify the RADIUS server settings for a
tunnel group or for a LAC client, or both. The AAA access profile configured for the client takes
precedence o... | [
{
"name": "profile-name",
"desc": "Name of the local access profile for the tunnel group or client."
}
] | 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.
Support at the [edit access profile profile-name client client-name l2tp] hierarchy level introduced in Junos
OS Release 12.1. | [
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
aaa-context (AAA Options) | aaa-context aaa-context-name; | [edit access aaa-options aaa-options-name] | Specify the logical-system:routing-instance (LS:RI) that the subscriber session uses for AAA (RADIUS)
interactions like authenticating and accounting. For example, this may correspond to the LS:RI for a
retail ISP that provides services to the subscriber.
NOTE: Only the default logical system is supported. | [
{
"name": "aaa-context-name",
"desc": "Name of the logical-system:routing-instance."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Understanding Session Options for Subscriber Access",
"Configuring Username Modification for Subscriber Sessions",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
aaa-logical-system (Domain Map) | aaa-logical-system logical-system-name {
aaa-routing-instance routing-instance-name;
} | [edit access domain map domain-map-name] | Configure a non-default logical system in which the authd daemon sends AAA requests for the domain
map.
NOTE: Subscriber management is supported in the default logical system only. The aaa-
logical-system statement is for future extensions of subscriber management and is not
supported in current Junos OS releases.
Def... | [
{
"name": "logical-system-name",
"desc": "Name of the logical system."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Specifying an AAA Logical System/Routing Instance in a Domain Map"
] |
aaa-options (Access Profile) | aaa-options aaa-options-name {
aaa-context aaa-context-name;
access-profile profile-name;
subscriber-context subscriber-context-name
} | [edit access] | Define a set of AAA options for authorizing and configuring a subscriber or set of subscribers with a
subscriber access profile. | [
{
"name": "aaa-options-name",
"desc": "Name of the set of options. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Understanding Session Options for Subscriber Access",
"Configuring Username Modification for Subscriber Sessions",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
aaa-options (PPP Profile) | aaa-options aaa-options-name; | [edit access group-profile profile-name ppp ppp-options],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options] | Specify a set of AAA options that is used for authentication of PPP subscribers. The set of options is
defined globally with the aaa-options aaa-options-name statement at the [edit access] hierarchy level.
You can specify the option set in a dynamic PPP profile or in a group profile.
•
In a dynamic PPP profile—In this ... | [
{
"name": "aaa-options-name",
"desc": "Name of the set of options."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Understanding Session Options for Subscriber Access",
"Configuring Username Modification for Subscriber Sessions",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
aaa-policy-control (PCEF Profile) | aaa-policy-control {
aaa-profile aaa-profile-name;
pcc-rulebases [rulebase-name];
user-password password;
} | [edit unified-edge pcef profiles profile-name] | Configure RADIUS-server-controlled policy management for a policy and charging enforcement function
(PCEF) profile.
The remaining statements are explained separately. | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Policies That a RADIUS Server Controls",
"Configuring an AAA Profile"
] |
aaa-profile (PCEF Profile) | aaa-profile aaa-profile-name; | [edit unified-edge pcef profiles profile-name aaa-policy-control] | Specify the AAA profile that identifies the RADIUS server policy control parameters for the policy and
charging enforcement function (PCEF) profile. The AAA profile must already be defined at the [edit
unified-edge aaa] hierarchy level. | [
{
"name": "aaa-profile-name",
"desc": "Name of the AAA profile."
}
] | 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 Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Policies That a RADIUS Server Controls",
"Configuring an AAA Profile"
] |
aaa-routing-instance (Domain Map) | aaa-routing-instance (routing-instance-name | default); | [edit access domain map domain-map-name],
[edit access domain map domain-map-name aaa-logical-system logical-system-name] | Configure the routing instance in which the authd daemon sends AAA requests for the domain map.
NOTE: Subscriber management is supported in the default logical system only. The aaa-
logical-system statement, which appears in the CLI, is not supported in current Junos OS
releases.
Default
Routing instance used for the s... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
},
{
"name": "default",
"desc": "The default routing instance."
}
] | 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.
default option added in Junos OS Release 13.3. | [
"Specifying an AAA Logical System/Routing Instance in a Domain Map",
"Domain Mapping Overview"
] |
aacl-fields (Obsolete) | aacl-fields {
field-name;
} | [edit system services local-policy-decision-function statistics aacl-statistics-profile profile-
name] | Define the statistics to collect in a data log file. | [
{
"name": "field-name",
"desc": "Name of the field:"
},
{
"name": "address",
"desc": "IPv4 address"
},
{
"name": "all-fields",
"desc": "All available fields"
},
{
"name": "application",
"desc": "Application name"
},
{
"name": "application-group",
"desc": "Appl... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
IPv6 support introduced in Junos OS Release 12.2. | [
"Configurng Statistics Profiles"
] |
aacl-statistics-profile | aacl-statistics-profile profile-name {
aacl-fields {
field-name;
}
file filename;
record-mode (interim-active-only | interim-full);
report-interval minutes;
} | [edit services service-set service-set-name],
[edit system services local-policy-decision-function statistics] | Create an AACL statistics profile, which configures the files to which statistics records are exported and
the format that is exported. | [
{
"name": "file filename",
"desc": "Name of the file to receive the statistics data output. Enclose the name within quotation"
},
{
"name": "profile-name",
"desc": "Identifier for the profile."
},
{
"name": "record-mode",
"desc": "Record mode for the reporting interval; possible valu... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
record-mode option introduced in Junos OS Release 10.2. | [
"Network Management and Monitoring Guide",
"Configuring Statistics Profiles"
] |
abstract-hop | abstract-hop abstract-hop-name {
constituent-list constituent-list-name (include-any-list | include-all-list | exclude-all-
list | exclude-any-list);
operators (AND | OR);
} | [edit logical-systems logical-systems-name protocols mpls],
[edit protocols mpls] | Define router clusters or groups, similar to the sequence of real-hop constraints (strict or loose), as a
sequence of abstract hops for setting up a label-switched path (LSP).
An abstract hop is a logical combination of the existing traffic engineering constraints, such as
administrative groups, extended administrative... | [
{
"name": "abstract-hop-name",
"desc": "Name of the abstract hop that is a logical combination of the existing traffic engineering constraints, such as administrative groups, extended administrative groups, and SRLGs, along with the ordering property of real hops."
},
{
"name": "constituent-list",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Example: Configuring Abstract Hops for MPLS LSPs",
"constituent-list",
"show mpls abstract-hop-membership",
"show mpls lsp abstract-computation"
] |
accept (Dynamic Profile) | accept (any | dhcp-v4 | dhcp-v6 | inet | inet6 | pppoe); | [edit interfaces interface-name auto-configure stacked-vlan-ranges dynamic-profile profile-name],
[edit interfaces interface-name auto-configure vlan-ranges dynamic-profile profile-name] | Specify the type of VLAN Ethernet packet accepted by an interface that is associated with a VLAN
dynamic profile or stacked VLAN dynamic profile. | [
{
"name": "any",
"desc": "Any packet type. Specifies that any incoming packets trigger the dynamic creation of a VLAN with"
},
{
"name": "dhcp-v4",
"desc": "IPv4 DHCP packet type. Specifies that incoming IPv4 DHCP discover packets trigger the"
},
{
"name": "stanza and associated profile ... | 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.
dhcp-v4 option added in Junos OS Release 10.0.
dhcp-v6, inet6 and pppoe options added in Junos OS Release 10.2.
any option added in Junos OS Release 10.4. | [
"Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs",
"Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs",
"Configuring VLAN Interfaces for the Layer 2 Wholesale Solution",
"Configuring Subscriber Packet Types to Trigger VLAN Authenti... |
accept (Router Advertisement Guard Policy) | accept {
match-list {
match-criteria {
(match-all | match-any);
}
prefix-list-name prefix-list-name;
source-ip-address-list address-list-name;
source-mac-address-list address-list-name;
}
match-option {
hop-limit {
(maximum | minimum) v... | [edit forwarding-options access-security router-advertisement-guard policy policy-name] | Configure the accept policy for an IPv6 Router Advertisement (RA) guard policy. RA guard protects
against rogue RA messages generated either maliciously or unintentionally by unauthorized or
improperly configured routers connecting to the network segment. An RA guard policy is used to
validate incoming RA messages on t... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
accept-data | (accept-data | no-accept-data); | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
fam... | In a Virtual Router Redundancy Protocol (VRRP) configuration, determine whether or not a router that is
acting as the primary router accepts all packets destined for the virtual IP address.
•
accept-data—Enable the primary router to accept all packets destined for the virtual IP address.
•
no-accept-data—Prevent the pr... | [] | 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 an Interface to Accept All Packets Destined for the Virtual IP Address of a VRRP Group"
] |
accept-join-always-from | accept-join-always-from [policy-name ... ]; | [edit protocols pim interface name],
[edit routing-instances name protocols pim interface name] | Configure an interface to accept PIM join or prune messages based on a specified policy.
A device might not accept PIM joins if the upstream neighbor address in the join packet is not that
device's address. This option enables the device to accept and to install PIM (S,G) join states that the
device would not normally ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1. | [
"Optimized Inter-Subnet Multicast in EVPN Networks"
] |
accept-max-tcp-connections (System Process) | accept-max-tcp-connections max-tcp-connections; | [edit system processes dhcp-service] | Specify the number of simultaneous TCP connections that DHCP can use for bulk leasequery
operations. This chassis-wide to enables the jdhcpd process to avoid exhaustion of TCP resources across
the chassis.
NOTE: Use the max-connections option of the "allow-bulk-leasequery" on page 2344
statement to set the number of TC... | [
{
"name": "max-tcp-connections",
"desc": "Number of connections. Range: 1 through 10 Default: 5"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring and Using DHCP Individual Leasequery",
"Configuring and Using DHCP Bulk Leasequery"
] |
accept-out-of-band | accept-out-of-band protocol; | [edit interfaces interface-name auto-configure vlan-ranges dynamic-profile profile-name] | Configure the protocol for which packets are accepted as out-of-band traffic to trigger instantiation or
deletion of autosensed dynamic VLANs.
NOTE: A given physical interface can support VLANs created by either conventional
packet-triggering or out-of-band triggering, but not both at the same time. | [
{
"name": "protocol",
"desc": "Out-of-band protocol. The following out-of-band protocol is supported:"
},
{
"name": "ancp",
"desc": "ANCP Port Up and Port Down messages trigger instantiation and deletion,"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring Out-of-Band ANCP Messages to Trigger Dynamic VLAN Instantiation",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] |
accept-own | accept-own; | [edit protocols bgp family inet-vpn unicast]
[edit protocols bgp family inet6-vpn unicast]
[edit protocols bgp group group family inetvpn unicast]
[edit protocols bgp group group family inet6-vpn unicast]
[edit protocols bgp group group neighbor address family inet-vpn unicast]
[edit protocols bgp group group neighbor ... | Enable processing of routes with own originator-id or nexthop.
NOTE: We support the accept-own configuration only for inet-vpn unicast and inet6-vpn
unicast address families. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1 | [] |
accept-prpd-connection | accept-prpd-connection; | [edit protocols bgp] | Used to initialize BGP to accept PRPD connections even if there are no BGP peers configured. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1. | [
"Controller-Based BGP Multicast Signaling"
] |
accept-remote-nexthop | accept-remote-nexthop; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Specify that a single-hop EBGP peer accepts a remote next hop with which it does not share a common
subnet. Configure a separate import policy on the EBGP peer to specify the remote next hop.
For Junos OS Release 13.3 and later releases, specify that a multihop EBGP peer accepts a remote next
hop with which it does not... | [] | 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. | [
"Example: Configuring Single-Hop EBGP Peers to Accept Remote Next Hops",
"Configuring Routing Policies to Control BGP Route Advertisements"
] |
accept-remote-source | accept-remote-source; | [edit logical-systems logical-system-name protocols pim interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface interface-name],
[edit protocols pim interface interface-name],
[edit routing-instances routing-instance-name protocols pim interf... | You can configure an incoming interface to accept multicast traffic from a remote source. A remote
source is a source that is not on the same subnet as the incoming interface. Figure 1 on page 1808
shows just such a topology – R2 connects to the R1 source on one subnet, and to the incoming interface
on R3 on another su... | [] | 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. | [
"Example: Allowing MBGP MVPN Remote Sources",
"Example: Allowing MBGP MVPN Remote Sources",
"Understanding Prepending AS Numbers to BGP AS Paths"
] |
accept-sdr (PCRF Partition) | accept-sdr; | [edit access pcrf partition partition-name] | Configure the service discovery requests for the vendor. If accept-sdr is configured for PCRF partition, the
application and the vendor ID is advertised in the diameter CER request. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
accept-source-mac (SRX) | accept-source-mac {
mac-address mac-address;
} | [edit interfaces interface-name unit logical-unit-number] | For Gigabit Ethernet (GE), Fast Ethernet (FE), or 10 Gigabit Ethernet (XE) interfaces, specify the MAC
addresses from which the interface can receive packets. Ensure that you update the MAC address if the
remote Ethernet card is replaced. Replacing the interface card changes the MAC address. If you do not
update the MA... | [
{
"name": "mac-address",
"desc": "MAC address filter. You can specify the MAC address as six hexadecimal bytes in one of the"
}
] | 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. | [
"Understanding Ethernet Interfaces"
] |
accept-source-mac | accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For Gigabit Ethernet intelligent queuing (IQ) interfaces only or for Gigabit Ethernet and aggregated
Ethernet interfaces on switches, accept traffic from and to the specified remote media access control
(MAC) address.
The accept-source-mac statement is equivalent to the source-address-filter statement, which is valid f... | [] | 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 Gigabit Ethernet Policers",
"Configuring MAC Address Filtering on PTX Series Packet Transport Routers"
] |
accept-srv6-service | accept-srv6-service; | [edit fabric protocols bgp family inet unicast],
[edit fabric protocols bgp family inet6 unicast],
[edit fabric protocols bgp group name family inet unicast],
[edit fabric protocols bgp group name family inet6 unicast],
[edit fabric protocols bgp group name neighbor name family inet unicast],
[edit fabric protocols bgp... | Configure the BGP ingress node to accept SRv6 service when you enable BGP services over the SRv6
data plane. Egress provider edge (PE) devices that support SRv6-based Layer 3 services advertise
overlay service prefixes along with a service SID. BGP ingress nodes receive the advertisements from
the egress provider edge ... | [] | routing | Statement introduced in Junos OS Release 20.4R1. | [
"Overview of SRv6 Network Programming and Layer 3 Services over SRv6 in BGP"
] |
accepted-prefix-limit | accepted-prefix-limit {
maximum number;
teardown <percentage-threshold> idle-timeout (forever | minutes);
drop-excess <percentage>;
hide-excess <percentage>;
} | [edit logical-systems logical-system-name protocols bgp family (inet | inet6) (any | flow |
labeled-unicast | multicast | unicast)],
[edit logical-systems logical-system-name protocols bgp family route-target],
[edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6)
(any | flow ... | Configure a limit to the number of prefixes that can be accepted in a BGP peer session. When that limit
is exceeded, a system log message is sent.
This statement provides the ability to log a message, reset the BGP session, or do both when the
number of prefixes received from the peer and accepted by policy exceeds a p... | [
{
"name": "maximum number",
"desc": "When you set the maximum number of prefixes, a message is logged when that number is exceeded. Range: 1 through 4,294,967,295 (232 – 1)"
},
{
"name": "teardown",
"desc": ""
},
{
"name": "<percentage>",
"desc": "(Optional) If you include the teard... | 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.
drop-excess <percentage> and hide-excess <percentage> options are introduced in Junos OS Release 21.2.
drop-excess <percentage> and hide-excess <percentage> options are introduced in Junos OS Evolved
Release 21.3R1. | [
"Understanding Multiprotocol BGP"
] |
access (Dynamic Access Routes) | access {
route prefix {
next-hop next-hop;
metric route-cost;
preference route-distance;
tag route-tag;
tag2 route-tag2;
} | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib
routing-table-name],
[edit dynamic-profiles profile-name routing-options] | 15.1
Starting in Junos OS Release 15.1, we recommend that you use only access routes for framed route
support. | [] | 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.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options]
and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib routing-
table-name] hierarchy levels introduced in Junos OS R... | [
"Configuring Dynamic Access Routes for Subscriber Management"
] |
access (SNMP) | access {
group group-name {
(default-context-prefix | context-prefix context-prefix) {
security-model (any | usm | v1 | v2c) {
security-level (authentication | none | privacy) {
notify-view view-name;
read-view view-name;
... | [edit snmp v3 vacm] | Set SNMP access limits.
The remaining statements are explained separately. See CLI Explorer. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
access (Static Framed Routes) | access {
route ip-prefix</prefix-length> {
metric route-cost;
next-hop next-hop;
preference route-distance;
qualified-next-hop next-hop;
tag tag-number
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Configure access routes under both non-default and default routing instances, Configure access route to
configure static framed route on Border Network Gateway.
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: ... | [] | 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. | [] |
access-concentrator | access-concentrator name; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit interfaces interface-name unit logical-unit-number family pppoe],
[edit interfaces interface-name unit logical-unit-n... | Configure an alternative access concentrator name in the AC-NAME tag in a PPPoE control packet for
use with a dynamic PPPoE subscriber interface. If you do not configure the access concentrator name,
the AC-NAME tag contains the system name.
NOTE: The [edit ... family pppoe] hierarchies are supported only on MX Series ... | [
{
"name": "name",
"desc": "Name of the access concentrator."
}
] | 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.
Support at the [edit interfaces interface-name unit logical-unit-number pppoe-underlying-options] and [edit
logical-systems logical-system-name interfaces interface-name unit logical-unit-number pppoe-underlying-options]
hierarchy levels introduced in Junos OS Release 1... | [
"Identifying the Access Concentrator",
"Configuring the PPPoE Family for an Underlying Interface",
"Configuring Dynamic PPPoE Subscriber Interfaces",
"PPPoE Overview"
] |
access-domain (Remote Device Management) | access-domain {
vlan-id-list [vlan-id-low-vlan-id-high vlan-id]
} | [edit routing-instances routing-instance-name system services remote-device-management service-
device device-name],
[edit system services remote-device-management service-device device-name] | Specify the Layer 2 domain that is served by the service device. The access domain represents the set of
subscriber-facing Layer 2 locations that map to the device. You define the domain when you map
subscribers to the device by configuring one or more non-overlapping outer VLAN ID ranges or discrete
VLAN IDs that are ... | [
{
"name": "vlan-id-low",
"desc": ""
},
{
"name": "(Optional) Lowest VLAN ID in the range,",
"desc": ""
},
{
"name": "vlan-id-high",
"desc": "(Optional) Highest VLAN ID in the range."
},
{
"name": "vlan-id",
"desc": "(Optional) Discrete VLAN ID that is not part of a range.... | system—To view this statement in the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring Remote Device Management for Service Provisioning",
"Remote Device Services Manager (RDSM) Overview"
] |
access-identifier | access-identifier identifier-string; | [edit protocols ancp interfaces interface-name],
[edit protocols ancp interfaces interface-set] | Associate an access-loop circuit identifier (ACI) with the VLAN or set of VLANs that carry traffic to the
subscriber using that access loop; identify a particular subscriber. This statement requires that the name
of the interface or interface set is statically configured or deterministic. This means that it can be used... | [
{
"name": "identifier-string",
"desc": "Unique identifier string for the access loop circuit; also configured on the access node."
}
] | 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. | [
"Configuring the ANCP Agent",
"Associating an Access Node with Subscribers for ANCP Agent Operations"
] |
access-interfaces (IFL Subscriber) | access-interfaces [interface-name]; | [edit unified-edge gateways tdf gateway-name domains domain-name ifl-subscriber subscriber-name] | Specify one or more interfaces that carry traffic for the subscriber. | [
{
"name": "interface-name",
"desc": "Name of the interface. You can assign only one IFL-based subscriber to an interface. You can specify the following types of interfaces: Physical Layer 3 Ethernet interface Layer 3 Aggregated Ethernet interface"
},
{
"name": "IRB interface",
"desc": "IRB tha... | 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"
] |
access-interfaces (IP Subscriber) | access-interfaces [interface-name]; | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber] | Specify at least one interface that faces the access network and that carries traffic for the TDF domain
for IP-based subscribers. You can specify multiple interfaces by including the access-interfaces statement
multiple times. | [
{
"name": "interface-name",
"desc": "Name of the interface. NOTE: The access-facing interface and the TDF interface (mif) in the TDF domain must be included in the same VRF routing instance."
}
] | 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"
] |
access-internal (Dynamic Access-Internal Routes) | access-internal {
route subscriber-ip-address {
qualified-next-hop underlying-interface {
mac-address address;
}
} | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib
routing-table-name],
[edit dynamic-profiles routing-options] | 15.1
Starting in Junos OS Release 15.1, we recommend that you use only access routes for framed route
support. | [] | 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.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options]
and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib routing-
table-name] hierarchy levels introduced in Junos OS R... | [
"Configuring Dynamic Access-Internal Routes for DHCP and PPP Subscribers"
] |
access-internal (Static Access-Internal Routes) | access-internal {
route ip-prefix</prefix-length> {
next-hop next-hop;
qualified-next-hop next-hop
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Configure parameters for internal access routes.
The remaining statements are explained separately.
NOTE: Starting in Junos OS Release 15.1R4, the router no longer supports a
configuration where a static route points to a next hop that is tied to a subscriber.
Typically, this might occur when RADIUS assigns the next h... | [] | 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 Dynamic Access-Internal Routes for DHCP and PPP Subscribers"
] |
access-line (Access-Line Rate Adjustment) | [edit system] | Configure values to adjust data rates by a percentage of the actual data rate, or adjust encapsulation
overhead by adding to or subtracting from the total cell or frame bytes a specified number of bytes.
Depending on the value, it may be reported to AAA, CoS, or both.
The actual (unadjusted) downstream and upstream dat... | [
{
"name": "adsl-overhead-bytes bytes",
"desc": "Number of bytes added to or subtracted from the actual downstream cell overhead for all subscribers on an ADSL access line to account for the traffic encapsulation overhead. The adjusted value is reported to CoS when you include the qos-adjust statement at the... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1.
The following options added in Junos OS 18.2R1:
gfast-bonded-overhead-adjust
vdsl2-annex-q-bonded-overhead-adjust
gfast-bonded-overhead-bytes
vdsl2-annex-q-bonded-overhead-bytes
gfast-bonded-total-adjust
vdsl2-annex-q-bonded-total-adjust
gfast-overhead-adjust
vdsl2-annex... | [
"Configuring the ANCP Agent to Report Traffic Rates to CoS",
"Traffic Rate Reporting and Adjustment by the ANCP Agent",
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Setting a Global Adjustment Factor per PON Subscriber Line for ANCP Agent-Reported Traffi... | |
access-line-information (L2TP) | access-line-information <connection-speed-update>; | [edit services l2tp],
[edit services l2tp destination ip-address] | Configure a LAC to forward subscriber line identification and other DSL attributes in ICRQ messages to
the LNS by means of L2TP AVPs for all tunnels to all LNSs or for only tunnels with the specified
endpoint for a particular LNS. Optionally, configure the LAC to send initial line rates in ICCN messages
and subsequent ... | [
{
"name": "connection-speed-update",
"desc": "(Optional) On the LAC, include the Connect Speed Update Enable AVP (98) in ICCN messages from the LAC to alert the LNS that the LAC might send CSUN messages that report speed changes originating with the ANCP agent. On the LNS, enable processing of CSUN updates.... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Support at the [edit services l2tp] hierarchy level introduced in Junos OS Release 14.2.
Support for the LNS introduced in Junos OS Release 17.4R1 on MX Series routers. | [
"L2TP Subscriber Access Lines and Connection Speeds"
] |
access-list | [edit snmp]
routing-instance-access {
access-list {
routing-instance;
routing-instance restrict;
}
} | [edit snmp routing-instance-access] | Create access lists to control SNMP agents in routing instances from accessing SNMP information. To
enable the SNMP agent on a routing instance to access SNMP information, specify the routing instance
name. To disable the SNMP agent on a routing instance from accessing SNMP information, include the
routing-instance na... | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [] |
access-point name | access-point-name apn; | [edit interfaces interface-name cellular-options gsm-options profiles profile-name] | Configure the access point name (APN) provided by the service provider for connection to a Global
System for Mobile Communications (GSM) cellular network. | [
{
"name": "apn",
"desc": "Access point name."
}
] | 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. | [] |
access-profile (AAA Options) | access-profile profile-name; | [edit access aaa-options aaa-options-name] | Specify the name of the access profile that includes the username stripping configuration. | [
{
"name": "profile-name",
"desc": "Name of the subscriber access profile that includes a subscriber username stripping configuration."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Understanding Session Options for Subscriber Access",
"Configuring Subscriber Session Timeout Options",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
access-profile (Domain Map) | access-profile profile-name; | [edit access domain map domain-map-name] | Access profile that defines the AAA services and options for subscribers associated with the domain
map. | [
{
"name": "profile-name",
"desc": "Name of access profile."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Specifying an Access Profile in a Domain Map"
] |
access-profile (Dynamic Stacked VLAN) | access-profile svlan-access-profile-name; | [edit interfaces interface-name auto-configure stacked-vlan-ranges dynamic-profile profile-name] | Access profiles contain subscriber access authentication, authorization and accounting (AAA)
configuration parameters. You can create an access profiles and then attach it at various configuration
levels. When you attach an access profile to an interface configured for dynamic VLAN or stacked VLAN,
all the VLANs and st... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs"
] |
access-profile (Dynamic VLAN) | access-profile vlan-access-profile-name; | [edit interfaces interface-name auto-configure vlan-ranges dynamic-profile profile-name] | Access profiles contain subscriber access authentication, authorization and accounting (AAA)
configuration parameters. You can create an access profiles and then attach it at various configuration
levels. When you attach an access profile to an interface configured for dynamic VLAN or stacked VLAN,
all the VLANs and st... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs"
] |
access-profile (Extensible Subscriber Services Manager) | access-profile access-profile-name; | [edit system services extensible-subscriber-services] | Define the access profile name for time accounting. In most cases, the information about the access
profile on the RADIUS server is the same as the information about the access profile of a control
session. This configuration is mandatory. | [
{
"name": "access-profile-name",
"desc": "Name of the access profile."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
access-profile (Static Subscribers) | access-profile profile-name; | [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 access profile that triggers AAA services 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 configuration. | [
{
"name": "profile-name",
"desc": "Name of the static subscriber access profile."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Specifying the Static Subscriber Global Access Profile",
"Specifying the Static Subscriber Group Access Profile"
] |
access-profile | access-profile name; | [edit interfaces interface-name ppp-options chap],
[edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name ... | For CHAP authentication, the mapping between peer names (or “clients” ) and the secrets associated
with their respective links. For PAP authentication, the peer's username and password.
For Asynchronous Transfer Mode 2 (ATM2) IQ interfaces only, you can configure a Challenge Handshake
Authentication Protocol (CHAP) acc... | [
{
"name": "name",
"desc": "Name of the access profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for PAP added in Junos OS Release 8.3.
Support for VLAN and stacked VLAN ranges added in Junos OS Release 10.0. | [
"Configuring the PPP Challenge Handshake Authentication Protocol",
"Configuring the PPP Password Authentication Protocol On a Physical Interface"
] |
access-profile-name (Duplicate Accounting) | access-profile-name [profile-name]; | [edit access profile profile-name accounting duplication-vrf] | Specify up to five access profiles, all in the same nondefault VRF (LS:RI combination), each of which lists
one or more RADIUS accounting servers to which duplication accounting information is sent. | [
{
"name": "profile-name",
"desc": "Name of an access profile that lists RADIUS accounting servers for duplicate reporting."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R3 and supported in later 12.3Rx releases.
Statement supported in Junos OS Release 13.2 and later releases. | [
"Understanding RADIUS Accounting Duplicate Reporting",
"Configuring Authentication and Accounting Parameters for Subscriber Access"
] |
access-security | access-security {
router-advertisement-guard {
interface interface-name {
mark-interface (trusted | block);
policy policy-name (stateful | stateless);
}
vlans (vlan-name | all) {
policy policy-name (stateful | stateless);
}
policy policy-na... | [edit forwarding-options] | Configure IPv6 access security options.
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 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
access-trunk | access-trunk; | [edit logical-systems logical-system-name protocols vstp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vstp],
[edit protocols vstp vlan vlan-identifier interface interface-name],
[edit routing-instances routing-instance-name instance-type (layer2-control | virtual-switc... | Enable untagged RTSP BDPUs to be sent and received on the interface. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [] | |
account-layer2-overhead (PIC Level) | account-layer2-overhead; | [edit chassis fpc slot-number pic pic-number] | Enable the automatic adjustment of Layer 2 overhead in bytes, which is the octet adjustment per packet,
based on the encapsulation on the logical interface for the total octet count for ingress and egress traffic
on all the interfaces in the PIC. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Accounting of the Layer 2 Overhead Attribute in Interface Statistics",
"Configuring Layer 2 Overhead Accounting in Interface Statistics",
"Verifying the Accounting of Layer 2 Overhead in Interface Statistics"
] |
accounting (AAA Profile) | accounting {
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. This statement is required if the
RADIUS servers cannot initiate a CoA request without an accounting record.
The remaining statement is explained separate... | [] | 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"
] |
accounting (Access Profile) | accounting {
accounting-stop-on-access-deny;
accounting-stop-on-failure;
address-change-immediate-update;
ancp-speed-change-immediate-update;
coa-immediate-update;
coa-no-override service-class-attribute;
duplication;
duplication-filter;
duplication-vrf {
access-profile-name ... | [edit access profile profile-name] | Configure RADIUS accounting parameters and enable RADIUS accounting for an access profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | 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 Accounting for Subscriber Access",
"RADIUS Authentication and Accounting Basic Configuration"
] |
accounting (Dynamic IGMP Interface) | (accounting | no-accounting); | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Enable or disable the collection of IGMP join and leave event statistics for dynamically created IGMP
interfaces. | [] | 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",
"Recording IGMP Join and Leave Events"
] |
accounting (Dynamic MLD Interface) | (accounting | no-accounting); | [edit dynamic-profiles profile-name protocols mld interface interface-name] | Enable or disable the collection of MLD join and leave event statistics for a dynamic interface. | [] | 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. | [
"Dynamic MLD Configuration Overview",
"Dynamic IGMP Configuration Overview",
"Example: Recording MLD Join and Leave Events"
] |
accounting (Forwarding Options) | accounting name {
output {
aggregate-export-interval seconds;
cflowd hostname {
aggregation {
autonomous-system;
destination-prefix;
protocol-port;
source-destination-prefix {
caida-compliant;
... | [edit forwarding-options] | Specify the discard accounting instance name and options.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Discard Accounting",
"Configuring Discard Accounting"
] |
accounting (interfaces) | accounting {
destination-class-usage;
source-class-usage {
direction;
}
} | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet] | Enable IP packet counters on an 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 before Junos OS Release 7.4. | [
"Enabling Source Class and Destination Class Usage"
] |
accounting (Protocols AMT Interface) | accounting; | [edit logical-systems logical-system-name protocols amt relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay],
[edit protocols amt relay],
[edit routing-instances routing-instance-name protocols amt relay] | Enable the collection of statistics for an Automatic Multicast Tunneling (AMT) interface.
Default
Disabled | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the AMT Protocol"
] |
accounting (Protocols IGMP AMT Interface) | (accounting | no-accounting); | [edit logical-systems logical-system-name protocols igmp amt relay defaults],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols igmp
amt relay defaults],
[edit protocols igmp amt relay defaults],
[edit routing-instances routing-instance-name protocols igmp amt relay defaults] | Enable or disable the collection of IGMP join and leave event statistics for an Automatic Multicast
Tunneling (AMT) interface.
Default
Disabled | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Default IGMP Parameters for AMT Interfaces"
] |
accounting (Protocols IGMP Interface) | (accounting | no-accounting); | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Enable or disable the collection of IGMP join and leave event statistics for an interface. | [] | 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. | [
"Recording IGMP Join and Leave Events"
] |
accounting (Protocols IGMP) | accounting; | [edit logical-systems logical-system-name protocols igmp],
[edit protocols igmp] | Enable the collection of IGMP join and leave event statistics on the system. | [] | 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. | [
"Recording IGMP Join and Leave Events"
] |
accounting (Protocols MLD Interface) | (accounting | no-accounting); | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Enable or disable the collection of MLD join and leave event statistics for an 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.1. | [
"Example: Recording MLD Join and Leave Events"
] |
accounting (Protocols MLD) | accounting; | [edit logical-systems logical-system-name protocols mld],
[edit protocols mld] | Enable the collection of MLD join and leave event statistics on the system. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Example: Recording MLD Join and Leave Events"
] |
accounting (RADIUS Client) | accounting {
secret password;
response-cache-timeout seconds;
} | [edit access radius clients client-name] | Specify a shared secret and response cache timeout to be used by the MX Series router and the RADIUS
client for accounting.
The remaining statements are explained separately. See CLI Explorer. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Clients That Send Accounting Requests for IP-Based Subscribers"
] |
accounting (Service Accounting) | accounting {
statistics (time | volume-time);
update-interval minutes;
} | [edit access profile profile-name service] | Define the service accounting configuration.
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 Release 14.2R1. | [
"Configuring Service Accounting",
"Configuring Per-Subscriber Session Accounting",
"Processing Cisco VSAs in RADIUS Messages for Service Provisioning"
] |
accounting (System) | accounting {
destination {
radius {
server {
server-address {
accounting-port port-number;
accounting-retry number;
accounting-timeout seconds;
dynamic-request-port number;
max-out... | [edit system] | Configure an audit of TACACS+ or RADIUS authentication events, configuration changes, and
interactive commands. Auditing these factors helps you track network usage for auditing and billing
purposes. | [
{
"name": "enhanced-avs-max",
"desc": "Configure the number of attribute-value pairs to be displayed, each of which can store a maximum of 250 bytes. Default: 7 pairs Range: 7 through 15 pairs"
},
{
"name": "events",
"desc": "(Required) Configure the types of events to log. Values:"
},
{
... | 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.
enhanced-avs-max statement introduced in Junos OS Release 14.1.
routing-instance introduced in Junos OS Release 18.1R1. | [
"Configuring RADIUS System Accounting",
"Configuring TACACS+ System Accounting"
] |
accounting-backup-options (Access Profile) | accounting-backup-options {
max-pending-accounting-stops number;
max-withhold-time hold-time;
} | [edit access] | Configure options for backing up RADIUS accounting stop requests when all RADIUS accounting
servers in the profile are offline.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"Configuring Back-up Options for RADIUS Accounting"
] |
accounting-options | accounting-options {
class-usage-profile profile-name {
file filename;
interval minutes;
destination-classes {
destination-class-name;
}
source-classes {
source-class-name;
}
}
cleanup-interval days;
file filename {
archive-... | [edit] | Configure options for accounting statistics collection. | [] | 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. | [
"Configuration Statements at the [edit accounting-options] Hierarchy Level",
"Accounting Options Configuration"
] |
accounting-order (Service Accounting) | accounting-order (activation-protocol | local | radius); | [edit access profile profile-name service] | Specify the method that is used for reporting subscriber service accounting.
When you specify the activation-protocol method, the service accounting statistics are reported
differently depending on how the service is activated:
•
When the service is activated by the RADIUS server, the statistics are reported to the RAD... | [
{
"name": "activation-protocol",
"desc": "Send service accounting reports by means of the application that activates services, such as JSRC, RADIUS, or the CLI."
},
{
"name": "local",
"desc": "Send service accounting information to a flat file stored locally on the router. This method requires y... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
local option added in Junos OS Release 17.1. | [
"Configuring Service Accounting with JSRC",
"Service Accounting with JSRC",
"Configuring Service Accounting in Local Flat Files"
] |
accounting-order | accounting-order (radius | [accounting-order-data-list]); | [edit access profile profile-name] | Specify the order in which accounting methods are used. | [
{
"name": "radius",
"desc": "Use the RADIUS accounting method."
},
{
"name": "[accounting-order-data-list]",
"desc": "Set of data listing the accounting order to be used, enclosed in brackets. This"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring RADIUS Authentication for L2TP"
] |
accounting-port (RADIUS Server) | accounting-port port-number; | [edit access radius-server address] | Specify the RADIUS server port number to which the device sends RADIUS accounting-start and
accounting-stop requests. RADIUS accounting-start and accounting-stop requests are used when the
RADIUS server is not able to initiate a change of authorization request without an accounting record. | [
{
"name": "port-number",
"desc": "Port number to which the RADIUS requests are sent."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules",
"External Authentication Servers"
] |
accounting-profile (firewall) | accounting-profile name; | [edit firewall family family-name filter filter-name] | Enable collection of accounting data for the specified filter. | [
{
"name": "name",
"desc": "Name assigned to the accounting profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Accounting for Firewall Filters Overview"
] |
accounting-profile | accounting-profile name; | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-range name] | Enable collection of accounting data for the specified physical or logical interface or interface range. | [
{
"name": "name",
"desc": "Name of the accounting profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Accounting for Physical Interfaces",
"Applying an Accounting Profile to the Logical Interface"
] |
accounting-secret (RADIUS Server) | accounting-secret password; | [edit access radius servers name] | Configure the secret password to be used when sending accounting-start requests to the RADIUS
server if the accounting secret password is different from the authentication secret password. RADIUS
accounting-start requests are used when the RADIUS server is not able to initiate a change of
authorization request without ... | [
{
"name": "password",
"desc": "Password for accounting requests. Range: 1 through 64 characters"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
accounting-server | accounting-server[server-addresses]; | [edit access profile profile-name radius] | Configure the Remote Authentication Dial-In User Service (RADIUS) server for authentication. To
configure multiple RADIUS servers, include multiple server addresses. The servers are tried in order and
in a round-robin fashion until a valid response is received from one of the servers or until all the
configured retry l... | [
{
"name": "server-addresses",
"desc": "One or more addresses of RADIUS authentication servers."
}
] | 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.
Statement introduced in Junos OS Release 14.1X53-D20 for OCX Series switches. | [
"show network-access aaa statistics authentication",
"Example: Connecting a RADIUS Server for 802.1X to an EX Series Switch",
"Understanding 802.1X and RADIUS Accounting on Switches",
"Understanding RADIUS Accounting"
] |
accounting-server-name | accounting-server-name hostname; | [edit access profile profile-name radius] | Configure the RADIUS accounting server for an access profile using a fully-qualified domain name
(FQDN). Use an FQDN if the server name can translate to more than one address.
The distribution of RADIUS requests among the resolved addresses is based on the configured client-
authentication-algorithm. You can configure ... | [
{
"name": "hostname",
"desc": "Configure the FQDN to identify the RADIUS server."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"Specifying RADIUS Server Connections on Switches (CLI Procedure)"
] |
accounting-stop-on-access-deny | accounting-stop-on-access-deny; | [edit access profile profile-name accounting] | Configure RADIUS accounting to send an Acct-Stop message when the AAA server refuses a client
request for access. | [] | 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 Authentication and Accounting Basic Configuration"
] |
accounting-stop-on-failure | accounting-stop-on-failure; | [edit access profile profile-name accounting] | Configure RADIUS accounting to send an Acct-Stop message when a subscriber session has been
successfully authenticated and authorized, but then fails before an Acct-Start message is sent. By
default, an Acct-Stop message is sent only if an Acct-Start message has been exchanged with the
accounting server.
Consider a si... | [] | 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 Authentication and Accounting Basic Configuration"
] |
acfc | acfc; | [edit interfaces interface-name ppp-options compression],
[edit interfaces interface-name unit logical-unit-number ppp-options compression],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options compression] | For interfaces with PPP encapsulation, configure compression of the Data Link Layer address and
control fields. The acfc option is not supported with frame-relay-ppp encapsulation.
On M320, M120, and T Series routers, address and control field compression (ACFC) is not supported
for any ISO family protocols. Do not inc... | [] | 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 PPP"
] |
ack-number | ack-number {
match (Security IDP Policy) (equal | greater-than | less-than | not-equal);
value acknowledgement-number;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the ACK number of the packet. This number identifies the next sequence number; the ACK flag
must be set to activate this field. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value acknowledgement-number",
"desc": "Match the ACK number of the packet."
}
] | 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. | [] |
acknowledge-retries | acknowledge-retries number; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, configure the number of retransmission attempts to be made for
consecutive hello or remove link messages following the expiration of the acknowledgment timer. | [
{
"name": "number",
"desc": "Number of retransmission attempts to be made following the expiration of the acknowledgment"
}
] | 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 Acknowledgment Timers on Link Services Physical Interfaces"
] |
acknowledge-timer | acknowledge-timer milliseconds; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, configure the maximum time, in milliseconds, to wait for an add link
acknowledgment, hello acknowledgment, or remove link acknowledgment message. | [
{
"name": "milliseconds",
"desc": "Time to wait for an add link acknowledgment, hello acknowledgment, or remove link"
}
] | 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 Acknowledgment Timers on Link Services Physical Interfaces"
] |
acquiring-state-announce-grandmaster | acquiring-state-announce-grandmaster {
default-ts;
} | [edit logical-systems name protocols ptp]
[edit protocols ptp] | Use grandmaster data set for announce messages when in acquiring state. | [
{
"name": "default-ts",
"desc": "Local data set for announce messages when in acquiring state."
}
] | routing | Statement introduced in Junos OS Release 20.4R1. | [
"IEEE 1588v2 Precision Timing Protocol (PTP)",
"Precision Time Protocol Overview"
] |
action (APN GTP) | action {
drop;
pass;
selection (ms|net|vrf);
} | [edit security gtp profile profile-name apn pattern-string imsi-prefiximsi-prefix] | Use the GPRS tunneling protocol (GTP) profile access point name (APN) action (pass |drop |selection) to
filter packets that helps you to allow or deny access to specific access points.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name apn pattern-string
imsi-prefix hierarchy-level i... | [
{
"name": "drop",
"desc": "Use drop to specify to deny GTP packets from all selection modes for the specified access"
},
{
"name": "pass",
"desc": "Use pass to specify to permit GTP packets from all selection modes for the access points."
},
{
"name": "selection",
"desc": "Use select... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Understanding GTP APN Filtering",
"Understanding GTPv2 IMSI Prefix and APN Filtering",
"Example: Setting a GTP APN and a Selection Mode"
] |
action (chassis error) | action {
alarm;
get-state;
log;
trap;
(reset | offline | reset-pfe | disable-pfe);
} | [edit chassis fpc slot-number error fatal],
[edit chassis fpc slot-number error major],
[edit chassis fpc slot-number error minor],
[edit chassis error fatal],
[edit chassis error major],
[edit chassis error minor] | Depending on the severity level of an error, you can configure one or more actions for the router to
perform. For example, if the severity level of an error is major, you can configure the system to raise an
alarm and restart the FPC. You can use offline-pfe and reset-pfe options to map errors belonging to pfe
category... | [
{
"name": "alarm",
"desc": "Raise an FPC alarm."
},
{
"name": "disable-pfe",
"desc": "(PTX routers) Disable Packet Forwarding Engine interfaces on an FPC. (MX240, MX480, MX960, MX2020 PTX10008 routers). Disables the interface associated with the ASIC that raised the error. Disables all PFE inter... | interface
To view this statement in the configuration.
interface-control
To add this statement to the configuration. | Statement introduced for PTX Series routers in Junos OS Release 13.3.
Statement introduced for MX240, MX480, MX960 routers in Junos OS Release 14.2. | [
"Configure FPC Error Levels and Actions"
] |
action (OAM LFM) | action {
syslog;
link-down;
} | [edit protocols oam ethernet link-fault-management] | Define the action or actions to be taken when the OAM link fault management (LFM) fault event occurs.
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.4. | [
"Configuring Ethernet OAM Link Fault Management"
] |
action (OAM) | action {
link-down;
send-critical-event;
syslog;
} | [edit protocols oam ethernet link-fault-management action-profile] | Define the action or actions to be taken when the OAM fault event occurs. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Specifying the Actions to Be Taken for Link-Fault Management Events"
] |
action (Policer) | action {
loss-priority high then discard;
} | [edit firewall three-color-policer policer-name] | This statement discards high loss priority traffic as part of a configuration using tricolor marking on a
logical interface. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Junos OS Class of Service User Guide for Routing Devices"
] |
action (QFX) | action {
loss-priority high then discard;
} | [edit firewall three-color-policer name] | Discard traffic on a logical interface using tricolor marking policing. | [] | 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. | [] |
action (Security Content Security Web Filtering) | action (block | log-and-permit | permit | quarantine); | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated profile profile-name
category customurl-last-name]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name category
customurl-last-name] | Enter an action to go with the customurl-list filter. | [
{
"name": "block",
"desc": "Log the error and deny the traffic."
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic."
},
{
"name": "permit",
"desc": "Permit the traffic."
},
{
"name": "quarantine",
"desc": "Show the warning message and permit/blo... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Surf-Control feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
action (Security Rulebase IPS) | action {
class-of-service {
dscp-code-point number;
forwarding-class forwarding-class;
}
(close-client | close-client-and-server | close-server |drop-connection | drop-packet |
ignore-connection | mark-diffserv value | no-action | recommended);
} | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then] | Specify the actions you want IDP to take when the monitored traffic matches the attack objects
specified in the rules. | [
{
"name": "no-action",
"desc": "No action is taken. Use this action when you want to only generate logs for some traffic."
},
{
"name": "ignore-connection",
"desc": "Stops scanning traffic for the rest of the connection if an attack match is found. IDP"
},
{
"name": "mark-diffserv 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.2. | [] |
action (Uplink Failure Detection) | action {
log;
} | [edit protocols uplink-failure-detection] | Define an action on uplink-failure-detection group state change. | [
{
"name": "log",
"desc": "Generate a system log message."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
action | action {
loss-priority high then discard;
} | [edit dynamic-profiles profile-name firewall three-color-policer name],
[edit firewall three-color-policer name],
[edit logical-systems logical-system-name firewall three-color-policer name] | Discard traffic on a logical interface using tricolor marking policing.
NOTE: This statement is supported only on IQ2 interfaces.
The remaining statement is explained separately. Search for a statement in CLI Explorer or click a linked
statement in the Syntax section for details. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... three-color-policer] hierarchy level introduced in Junos OS
Release 11.4. | [
"Three-Color Policer Configuration Overview",
"Basic Single-Rate Three-Color Policers",
"Basic Two-Rate Three-Color Policers",
"Two-Color and Three-Color Logical Interface Policers",
"Two-Color and Three-Color Physical Interface Policers",
"Two-Color and Three-Color Policers at Layer 2"
] |
action-priority (bridge domain) | action-priority number; | [edit bridge-domains bridge-domain-name bridge-options interface interface-name] | Configure the action priority value for an interface in a bridge domain on MAC move detection. This
priority value is used to determine which interface should be blocked when a throttled MAC move is
detected between two interfaces. The priority value can be between 0 and 7 inclusive. A higher value
means lower priority... | [] | 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. | [
"Configuring a Bridge Domain",
"Configuring a Layer 2 Virtual Switch"
] |
action-priority (Routing Instance) | action-priority value; | [edit routing-instances routing-instance-name protocols protocol-name interface interface-name] | Configure the priority for an interface on which the MAC move is applied. When a MAC move is
configured with a corresponding action, and that limit is exceeded, the action is applied to one of the
interfaces associated with that MAC address having the highest action priority. If the action configured
for the MAC move i... | [
{
"name": "value",
"desc": "Value assigned to an interface associated with a MAC address move. The value determines the priority with which an action is applied to the interface if the MAC address move limit is reached. The interface with the highest priority is the interface with the lowest value configure... | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Example: Configuring Loop Prevention in VPLS Network Due to MAC Moves"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.