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 |
|---|---|---|---|---|---|---|---|
group-policy (Protocols MLD) | group-policy [ policy-names ]; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | When a routing device running MLD version 1 or version 2 (MLDv1 or MLDv2), receives an MLD report,
the routing device compares the group against the specified group policy and performs the action
configured in that policy (for example, rejects the report). | [] | 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. | [
"Filtering Unwanted MLD Reports at the MLD Interface Level"
] |
group-profile (Access) | group-profile profile-name {
ppp {
cell-overhead;
encapsulated-overhead;
framed-pool address-pool-name;
idle-timeout seconds;
interface-id interface-identifier;
keepalive seconds;
primary-dns IP address;
primary-wins IP address;
secondary-dns I... | [edit access] | Configure a group profile to define Point-to-Point Protocol (PPP) and L2TP attributes. Any client
referencing the configured group profile inherits all the group profile attributes. | [
{
"name": "ppp",
"desc": "Configure Point-to-Point Protocol (PPP) attributes."
},
{
"name": "cell-overhead",
"desc": "Configure the session to use Asynchronous Transfer Mode (ATM)-aware egress"
},
{
"name": "framed-pool pool-name",
"desc": "Configure a framed-pool."
},
{
"nam... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 10.4 of Junos OS. | [
"Firewall User Authentication Overview"
] |
group-profile (Group Profile) | group-profile profile-name {
l2tp {
interface-id interface-id;
lcp-renegotiation;
local-chap;
maximum-sessions-per-tunnel number;
}
ppp {
cell-overhead;
encapsulation-overhead bytes;
framed-pool pool-id;
idle-timeout seconds;
interface-... | [edit access] | Configure the group profile.
NOTE: Subordinate statement support depends on the platform. See individual
statement topics for more detailed support information. | [
{
"name": "profile-name",
"desc": "Name assigned to the group profile."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Point-to-Point Protocol (PPP)",
"Layer 2 Tunneling Protocol (L2TP)",
"L2TP LNS Inline Service Interfaces"
] |
group-range (Data MDTs) | group-range multicast-prefix; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family inet | inet6 mdt],
[edit routing-instances routing-instance-name provider-tunnel family inet | inet6 mdt] | Establish the group range to use for data MDTs created in this VRF instance. Only IPv4 address are valid
for group range. This address range cannot overlap the default MDT addresses of any other VPNs on the
router, nor can the group range specified under the inet and inet6 hierarchies overlap. If you configure
overlapp... | [
{
"name": "multicast-prefix",
"desc": "Multicast address range to identify data MDTs."
}
] | 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. In Junos OS Release 17.3R1, the mdt hierarchy was
moved from provider-tunnel to the provider-tunnel family inet and provider-tunnel family inet6 hierarchies as
part of an upgrade to add IPv6 support for default MDT in Rosen 7, and data MDT for Rosen 6 and
Rosen 7. The p... | [
"Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode",
"Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode"
] |
group-range (MBGP MVPN Tunnel) | group-range multicast-prefix; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group group-address source source-address pim-ssm],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group group-address wildcard-source pim-ssm],
[edi... | Establish the multicast group address range to use for creating MBGP MVPN source-specific multicast
selective PMSI tunnels. | [
{
"name": "multicast-prefix",
"desc": "Multicast group address range to be used to create MBGP MVPN source-specific"
}
] | 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. | [] |
group-ranges | group-ranges {
destination-ip-prefix</prefix-length>;
} | [edit logical-systems logical-system-name protocols pim rp bidirectional address address],
[edit logical-systems logical-system-name protocols pim rp embedded-rp],
[edit logical-systems logical-system-name routing-instances instance-name protocols pim rp
bidirectional address address],
[edit logical-systems logical-sy... | Configure the address ranges of the multicast groups for which this routing device can be a rendezvous
point (RP).
Default
The routing device is eligible to be the RP for all IPv4 or IPv6 groups (224.0.0.0/4 or FF70::/12 to
FFF0::/12). | [
{
"name": "destination-ip-prefix</prefix-length>",
"desc": "Addresses or address ranges for which this routing device can be an"
}
] | 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 bidirectional RP addresses introduced in Junos OS Release 12.1. | [
"Configuring Local PIM RPs",
"Configuring PIM Embedded RP for IPv6",
"Example: Configuring Bidirectional PIM"
] |
group-rp-mapping | group-rp-mapping {
family (inet | inet6) {
log-interval seconds;
maximum limit;
threshold value;
}
log-interval seconds;
maximum limit;
threshold value;
} | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure a limit for the number of incoming group-to-RP mappings.
NOTE: The maximum limit settings that you configure with the maximum and the family
(inet | inet6) maximum statements are mutually exclusive. For example, if you configure a
global maximum group-to-RP mapping limit, you cannot configure a limit at the f... | [
{
"name": "family (inet | inet6)",
"desc": "(Optional) Specify either IPv4 or IPv6 messages to be counted towards the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring PIM State Limits"
] |
group-threshold (Protocols IGMP Interface) | group-threshold value; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Specify the threshold at which a warning message is logged for the multicast groups received on a
logical interface. The threshold is a percentage of the maximum number of multicast groups allowed on
a logical interface.
For example, if you configure a maximum number of 1,000 incoming multicast groups, and you configur... | [
{
"name": "value",
"desc": "Percentage of the maximum number of multicast groups allowed on the interface that starts"
}
] | 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. | [
"Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces"
] |
group-threshold (Protocols MLD Interface) | group-threshold value; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Specify the threshold at which a warning message is logged for the multicast groups received on a
logical interface. The threshold is a percentage of the maximum number of multicast groups allowed on
a logical interface.
For example, if you configure a maximum number of 1,000 incoming multicast groups, and you configur... | [
{
"name": "value",
"desc": "Percentage of the maximum number of multicast groups allowed on the interface that starts"
}
] | 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. | [
"Configuring the Number of MLD Multicast Group Joins on Logical Interfaces"
] |
group-type (Unknown Unicast Forwarding) | group-type (none | layer-2) | [edit forwarding-options next-hop-group] | Configure the type of addresses to be used in the next-hop group. | [
{
"name": "none",
"desc": "Next-hop group uses Layer 2 addresses."
},
{
"name": "layer-2",
"desc": "Specify a next-hop group that uses Layer 2 addresses."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Configuring Unknown Unicast Forwarding (ELS)",
"Configuring Mirroring on EX9200 Switches to Analyze Traffic (CLI Procedure)"
] |
group-vpn | group-vpn {
member {
ike {
gateway gateway-name;
policy;
proposal;
traceoptions;
}
ipsec {
vpn vpn-name {
df-bit (clear | copy | set);
exclude rule rule-name {
sour... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "member",
"desc": "Configure group VPN member."
},
{
"name": "ike",
"desc": "Configure IPsec group VPN on the group member."
},
{
"name": "policy",
"desc": "Configure an IKE policy."
},
{
"name": "proposal",
"desc": "Define an IKE proposal. You can configure one... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Group VPNv2 Overview"
] |
grouped-ie-profile | grouped-ie-profile name {
ie ie-number {
instance inst-number {
grouped-ie-profile grpie-prf-name;
}
}
} | [edit security gtp] | Specify a GTP grouped IE filter profile. A grouped IE is a group of IEs or a group of grouped IEs. A
grouped-ie-profile is defined and linked to the IE when a Must-IE check is expected to go deep into a
grouped IE.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp] hierarchy level is replaced by [edit
s... | [
{
"name": "name",
"desc": "Name of the GTP grouped IE filter profile."
},
{
"name": "ie-number",
"desc": "IE number. Range: 1 to 255"
},
{
"name": "inst-number",
"desc": "instance number. Range: 0 to 11 Default: 0"
},
{
"name": "grpie-prf-name",
"desc": "GTP grouped IE... | security—To view this statement in the configuration. | Statement introduced in Junos OS Release 20.2R1. | [
"Example: Configure Must-IE check for GTPv1 and GTPv2"
] |
groups | groups {
group-name {
configuration-data;
when {
chassis chassis-id;
member member-id;
model model-id;
node node-id;
peers [ names-of-peers ]
routing-engine routing-engine-id;
time <start-time> [to <end-time>];
... | [edit] | Create a configuration group.
NOTE: Junos OS does not support configuring statements corresponding to third-party
YANG data models, for example, OpenConfig or custom data models, under the [edit
groups] hierarchy. | [
{
"name": "group-name",
"desc": "Name of the configuration group. To configure multiple groups, specify more than one group name."
},
{
"name": "configuration-data",
"desc": "The configuration statements that are to be applied elsewhere in the configuration with the apply-groups statement, to ha... | configure—To enter configuration mode. | Statement introduced before Junos OS Release 7.4. | [
"Creating a Configuration Group"
] |
grpc | grpc {
max-connections max-connections;
routing-instance routing-instance;
ssl {
address ip-address;
hot-reloading;
local-certificate (System) local-certificate;
mutual-authentication {
certificate-authority certificate-authority-profile-name;
client-c... | [edit system services extension-service request-response] | Configure the type of connections the gRPC service accepts for API applications. | [
{
"name": "routing-instance routing-instance",
"desc": "Name of routing instance for grpc."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [] |
grpc-replay | grpc-replay <last minute|facility facility|priority priority> | [edit system syslog] | Configure this configuration statement to replay the events. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1. | [] |
grpc-tunnel | grpc-tunnel {
servers {
retry-interval interval;
server server-name {
address ip-address;
port port-number;
credentials {
tls {
certificate-id local-certificate in pki
ca-profiles [ specific ca-profile... | [edit system services] | Configure gRPC tunnel settings. | [
{
"name": "retry-interval",
"desc": "Optional. Specify the time after which the target retries to connect again if the tunnel-server is not reachable. There is no limit on the number of times the target retries to connect to the server. Range: 10-300 Default: 30 seconds"
},
{
"name": "server",
... | system— To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 22.4R1.
routing-instance routing-instance and source-address ip-address options introduced in Junos OS and Junos OS
Evolved Release 23.2R1. | [
"Using gRPC Dial-Out for Secure Telemetry Collection"
] |
gsm-options | gsm-options {
select-profile profile-name;
profiles {
profile-name {
sip-user-id simple-ip-user-id;
sip-password simple-ip-password;
access-point-name apn;
authentication-method (pap | chap | none);
}
}
} | [edit interfaces interface-name cellular-options] | Configure the 3G wireless modem interface to establish a data call with a Global System for Mobile
Communications (GSM) cellular network. | [] | 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. | [] |
gsmp-syn-timeout (ANCP) | gsmp-syn-timeout seconds; | [edit protocols ancp] | Configure the maximum period that the ANCP agent waits before sending a SYN message to an ANCP
neighbor to negotiate the adjacency. If the neighbor sends a SYN message during this period, the ANCP
agent uses the partition information in the neighbor’s message when generating its own initial SYN
message to the neighbor.... | [
{
"name": "seconds",
"desc": "Number of seconds the ANCP agent waits."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Configuring the ANCP Agent",
"Configuring the ANCP Agent to Learn ANCP Partition IDs"
] |
gsmp-syn-wait (ANCP) | gsmp-syn-wait; | [edit protocols ancp] | Enable the ANCP agent to learn partition ID information from neighbors, in support of nonzero ANCP
partition IDs. This statement forces the ANCP agent to delay sending a SYN message during adjacency
negotiation for a configurable period. When the neighbor sends a SYN message to the ANCP agent
during that period, the ag... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3 | [
"Configuring the ANCP Agent",
"Configuring the ANCP Agent to Learn ANCP Partition IDs"
] |
gtp | gtp {
grouped-ie-profile name {
ie name {
instance name {
grouped-ie-profile grpie-prf-name;
}
}
}
handover-default {
deny;
}
ie-set name {
ie name;
}
ip-group name {
address-book name {
address-set ... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [] | 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. The restart-path option added in Junos OS Release 11.4.
New GPRS tunneling protocol (GTP) message types added in Junos OS Release 11.4. Support for GTPv2
added in Junos OS Release 11.4. Statement modified in Junos OS Release 15.1X49-D40. Support for
handover-default and ha... | [
"GPRS Overview",
"Understanding GTP Support for Central Point Architecture",
"Enabling GTP Interoperability between 2G and 3G Networks"
] |
gtp-header-offset | gtp-header-offset offset-value | [edit forwarding-options enhanced-hash-key hash-mode] | You must only provide a decimal value for gtp-header-offset command. As per standards, 0x32 is the
default header offset value. But, due to some special patterns in the header, offset may vary like, 0x30,
0x28, and so on. In this case, you need to convert it to a proper offset value as follows:
For Example:
•
If the of... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R3. | [] |
gtp-tunnel-endpoint-identifier | gtp-tunnel-endpoint-identifier; | [edit forwarding-options enhanced-hash-key family inet],
[edit forwarding-options enhanced-hash-key family inet6] | When you configure gtp-tunnel-endpoint-identifier, the hash calculation of IPv4 or IPv6 packets are
included in the GPRS tunneling protocol–tunnel endpoint ID (GTP-TEID) field hash calculations.
NOTE: The gtp-tunnel-endpoint-identifier configuration statement is supported on PTX
Series routers only when network service... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F3 and 16.1R2. | [
"Understanding Per-Packet Load Balancing",
"Configuring Per-Packet Load Balancing"
] |
guaranteed-rate (Dynamic Traffic Shaping) | guaranteed-rate (rate | $junos-cos-guaranteed-rate) <burst-size [ bytes | $junos-cos-guaranteed-
rate-burst]>; | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | Configure a guaranteed minimum rate for a logical interface and optionally a burst size for the
guaranteed rate.
NOTE: The guaranteed-rate burst size must not exceed the shaping-rate burst size.
Default
If you do not include this statement and you do not include the delay-buffer-rate statement, the logical
interface r... | [
{
"name": "rate",
"desc": "Guaranteed rate in bits per second (bps). You can specify a value in bits per second either as a"
},
{
"name": "$junos-cos-guaranteed-rate",
"desc": "Junos predefined variable that is replaced with the guaranteed rate obtained"
},
{
"name": "burst-size bytes",
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
The $junos-cos-guaranteed-rate variable introduced in Junos OS Release 9.4.
Option burst-size introduced in Junos OS Release 11.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Traffic Scheduling and Shaping for Subscriber Access"
] |
guaranteed-rate (Traffic Control Profiles) | guaranteed-rate (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name] | Configure a guaranteed minimum rate of transmission for a traffic control profile. The sum of the
guaranteed rates of all of the forwarding class sets (priority groups) on a port should not exceed the total
port bandwidth. The guaranteed rate also determines the amount of excess (extra) port bandwidth that
the priorit... | [
{
"name": "percent",
"desc": ""
},
{
"name": "percentage",
"desc": "Minimum percentage of transmission capacity allocated to the forwarding class set or logical interface. Range: 1 through 100 percent"
},
{
"name": "rate",
"desc": "Minimum transmission rate allocated to the forwardi... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Option burst-size introduced in Junos OS Release 9.4. | [
"Providing a Guaranteed Minimum Rate",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping",
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Example: Configuring Traffic Control Profiles (Priority Group Scheduling)",
"Example: Configuring Minimum Guaranteed Output Bandwid... |
guard-band (PoE) | guard-band watts; | [edit poe] | Reserves the specified amount of power for the SRX Series Firewall in case of a spike in PoE
consumption. | [
{
"name": "watts",
"desc": "Amount of power to be reserved for the SRX Series Firewall in case of a spike in PoE"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Power over Ethernet"
] |
guard-band | guard-band watts; | [edit poe],
[edit poe (all | fpc slot-number)] | Reserve a specified amount of power from the PoE power budget for the switch, line card, or satellite
device in case of a spike in PoE consumption. | [
{
"name": "watts",
"desc": "Amount of power to be reserved in case of a spike in PoE consumption."
}
] | 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.
Statement introduced in Junos OS Release 12.2 for ACX2000 Universal Metro Routers.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge. | [
"Configuring PoE Interfaces on EX Series Switches",
"Configuring Power over Ethernet in a Junos Fusion"
] |
guard-interval | guard-interval number; | [edit protocols protection-group ethernet-ring ring-name] | When a link goes down, the ring protection link (RPL) activates. When the downed link comes back up,
the RPL link receives notification, restores the link, and waits for the restore interval before issuing
another block on the same link. This configuration is a global configuration and applies to all Ethernet
rings if ... | [
{
"name": "number",
"desc": "Guard timer interval, in milliseconds."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS",
"Configuring Ethernet Ring Protection Switching on Switches (CLI P... |
guest-network-functions | guest-network-functions {
gnf id {
control-plane-bandwidth-percent percent;
description description;
fpcs fpcs;
af-name
}
} | [edit chassis network-slices] | Configure a guest network function for Junos node slicing.
Junos node slicing enables a single MX Series router to be partitioned to appear as multiple,
independent routers. Each partition has its own Junos control plane, which runs as a virtual machine
(VM), and a dedicated set of line cards. Each partition is called ... | [] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Setting Up Junos Node Slicing"
] |
gw-interface | gw-interface interface-name.logical-unit-number; | [edit services service-set service-set-name ipsec-vpn-options local-gateway address] | Enable the cleanup of IKE triggers and IKE and IPsec SAs when an IPsec tunnel’s local gateway IP
address goes down or the MS-MIC or MS-MPC being used in the tunnel’s service set goes down. If the
local gateway IP address for an IPsec tunnel’s service set goes down or the MS-MIC or MS-MPC that is
being used in the servi... | [
{
"name": "interface-name",
"desc": "Name of the interface of the IPsec local gateway."
},
{
"name": "logical-unit-numer",
"desc": "Number of the logical unit of the IPsec local gateway interface. You must include the logical unit number."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Configuring IPsec Service Sets"
] |
gx-plus (Gx-Plus) | gx-plus {
global {
include-ipv6;
max-outstanding-requests number;
}
partition partition-name {
diameter-instance instance-name;
destination-host hostname;
destination-realm realm;
}
} | [edit access] | Configure the Gx-Plus application to interact with a PCRF to authorize and provision subscribers.
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 11.2. | [
"Configuring Gx-Plus"
] |
gx-profile | gx-profile profile-name {
<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] | Configure the Diameter profile used for Gx applications. | [
{
"name": "profile-name",
"desc": "Name of the Diameter 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. | [
"Diameter Profiles Overview",
"H"
] |
h323 | h323 {
application-screen {
message-flood {
gatekeeper {
threshold rate;
}
}
unknown-message {
permit-nat-applied;
permit-routed;
}
}
disable;
dscp-rewrite {
code-point string;
}
endpoint-reg... | [edit security alg]
[edit tenants tenant-name security alg] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the H.323 ALG. By default, H.323 ALG is enabled."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
The tenant option is introduced in Junos OS Release 18.3R1. | [] |
halt-on-prefix-down (RFC 2544 Benchmarking) | halt-on-prefix-down; | [edit services monitoring rfc2544 tests test-name test-name] | By default, the RFC 2544-based benchmarking test ignores a prefix-down event (when the prefix
associated with the test goes down) and continues to run. If you configure this parameter, a prefix that
moves to the down state causes the corresponding tests to be stopped. The show command output for
the test displays that ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved Release 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
handover-default | handover-default {
deny;
} | [edit security gtp] | A GPRS tunneling protocol (GTP) handover group is a set of SGSNs or serving gateway (SGW) with a
common address-book library. You can configure the handover group using the “handover-group”
command. If there is no handover group defined in the GTP profile, and if the traffic reaches the policy
configured with this prof... | [
{
"name": "deny",
"desc": "To deny default handover."
}
] | security—To view this statement in the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"GTP Handover Group Overview",
"Understanding GTP Handover Messages"
] |
handover-group | handover-group group-name; | [edit security gtp profile profile-name] | A GPRS tunneling protocol (GTP) handover group is a set of SGSNs or serving gateway (SGW) with a
common address-book library. You can configure a GTP profile and associate an GTP handover group to
the GTP profile. When a GTP handover group name is referenced by a GTP profile, the device checks to
see if the current SGS... | [
{
"name": "name",
"desc": "To specify the handover group on the GTP profile."
},
{
"name": "address-book",
"desc": "To specify the common address-book name."
},
{
"name": "address-set",
"desc": "To specify the address set for the handover group."
}
] | security—To view this statement in the configuration. | Statement introduced in Junos OS Release 17.4R1. | [] |
handshake-timeout | handshake-timeout time-in-seconds; | [edit security sctp profile profile-name] | Use the handshake-timeout function to set the handshake time 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-seconds",
"desc": "Number of seconds of handshake time that elapse before the session is terminated."
}
] | 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. | [
"Understanding Stream Control Transmission Protocol",
"SCTP Packet Structure Overview"
] |
hard-limit | hard-limit bandwidth; | [edit services dynamic-flow-capture capture-group client-name content-destination identifier] | Specify a bandwidth threshold at which the dynamic flow capture application begins deleting criteria,
until the bandwidth falls below the hard-limit-target value. | [
{
"name": "bandwidth",
"desc": "Hard limit threshold, in bits per second."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring the Content Destination"
] |
hard-limit-target | hard-limit-target bandwidth; | [edit services dynamic-flow-capture capture-group client-name content-destination identifier] | Specify a bandwidth threshold at which the dynamic flow capture application stops deleting criteria. | [
{
"name": "bandwidth",
"desc": "Target value, in bits per second."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring the Content Destination"
] |
hardware-assisted-keepalives | hardware-assisted-keepalives [enable | disable]; | [edit protocols oam ethernet connectivity-fault-management performance-monitoring] | For Ethernet interfaces on Modular Port Concentrators (MPCs) in MX Series routers only, delegate the
transmission of the continuity check messages (CCMs) to the forwarding ASIC (that is, to the hardware)
by enabling inline transmission of CCMs. Inline transmission of CCMs is also known as Inline-KA.
By default, CCMs ar... | [
{
"name": "enable",
"desc": "Enable inline transmission of CCMs. NOTE: Inline transmission of CCMs is not enabled when there is a CFM session already established. To enable inline transmission, you must first deactivate the CFM session using the deactivate command and then reactivate the CFM session using t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R1. | [
"Enabling Inline Transmission of Continuity Check Messages for Maximum Scaling",
"Configuring Connectivity Fault Management for Interoperability During Unified In-Service Software",
"Upgrades"
] |
hardware-assisted-timestamping | hardware-assisted-timestamping; | [edit protocols oam ethernet connectivity-fault-management performance-monitoring] | For Ethernet interfaces on Enhanced and Enhanced Queuing Dense Port Concentrators (DPCs) in MX
Series routers only, enable hardware-assisted timestamping support for Ethernet frame delay
measurement.
By default, the ETH-DM feature calculates frame delays using software-based timestamping of the ETH-
DM PDU frames sent ... | [] | 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. | [
"Ethernet Frame Delay Measurements Overview",
"Guidelines for Configuring Routers to Support an ETH-DM Session",
"Enabling the Hardware-Assisted Timestamping Option"
] |
hardware-timestamp | hardware-timestamp; | [edit services rpm probe owner test test-name] | Enable timestamping of RPM probe messages in the Packet Forwarding Engine host processor. This
feature is supported only with icmp-ping, icmp-ping-timestamp, udp-ping, and udp-ping-timestamp probe types. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
Statement applied to MX Series routers in Junos OS Release 10.0.
Statement introduced in Junos OS Release 19.1 for PTX Series routers. | [] |
hardware-upgrade | hardware-upgrade | [edit chassis high-availability] | Install an additional SPC3 card in a Multinode High Availability statement. Use this statement when you
insert an additional SPC3 on an SRX5000-line device in Multinode High Availability and has an
interchassis link (ICL) in encryption mode. You must run the command on both nodes in Multinode High
Availability before y... | [] | interface | Statement introduced in Junos OS Release 22.2R1. | [
"Hardware Upgrade for SRX5000-Line SPC3 in a Multinode High Availability Setup"
] |
has-prefix (Unified Edge Gateways) | has-prefix {
value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from class],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from 3gpp-imsi],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format string] | Specify the prefix that the attribute must have.
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": "value",
"desc": "Prefix string. Range: 1 through 254 alphanumeric characters."
}
] | 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"
... |
has-suffix | has-suffix {
value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from class],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from 3gpp-imsi],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format string] | Specify the suffix that the attribute must have.
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": "value",
"desc": "Suffix string. Range: 1 through 254 alphanumeric characters."
}
] | 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"
... |
hash-based-rpf-selection | hash-based-rpf-selection; | [edit dynamic-profiles name protocols pim],
[edit logical-systems name protocols pim],
[edit logical-systems name routing-instances name protocols pim],
[edit protocols pim],
[edit routing-instances name protocols pim] | Configure PIM hash-based RPF selection to ensure that multicast traffic for a specific source and group
(S,G) is routed consistently through the same upstream node.
On enabling this feature, the (S,G) pair’s RPF is updated with the output of the hashing algorithm. This
update of the RPF happens in Make-before-break (MB... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [
"Hash-based PIM RPF Selection"
] |
hash-key (Chassis LAG) | hash-key {
family {
inet {
layer-3;
layer-4;
symmetric-hash {
complement;
}
}
multiservice {
source-mac;
destination-mac;
payload {
ip {
layer-3 (source-ip... | [edit chassis fpc slot-number pic pic-number] | (MX Series 5G Universal Routing Platforms only) Configure data used in a hash key for a PIC for
symmetrical load balancing on an 802.3ad Link Aggregation Group. | [
{
"name": "family",
"desc": "Configure data used in a hash key for a protocol family. This statement has the following"
},
{
"name": "suboptions:",
"desc": ""
},
{
"name": "inet",
"desc": "Configure data used in a hash key for the inet protocol family."
},
{
"name": "multiser... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring PIC-Level Symmetrical Hashing for Load Balancing on 802.3ad LAGs for MX Series",
"Routers"
] |
hash-key (Chassis) | hash-key (layer-3 | layer-4); | [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-
provider data-flow-affinity] | Set the hashing distribution of flow affinity. This is an optional setting. Once the data-flow-affinity
statement is enabled, you may need to choose the hashing distribution. Modifying this statement causes
the PIC to reboot.
Default
If you do not configure the hash-key statement, the hashing distribution is 5-tuple ha... | [
{
"name": "layer-3",
"desc": "3-tuple hashing (source IP address, destination IP address, and IP protocol)."
},
{
"name": "layer-4",
"desc": "5-tuple hashing (3-tuple plus source and destination TCP or UDP ports)."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [] |
hash-key (Forwarding Options) | hash-key {
family inet {
layer-3;
layer-4;
inner-vlan-id;
outer-vlan-id;
session-id;
symmetric-hash {
complement;
}
}
family inet6 {
layer-3 {
destination-address;
incoming-interface-index;
... | [edit forwarding-options]
[edit chassis fpc slot-number pic pic-number] | Select which packet header data to use for per-flow load balancing.
The options are explained separately.
NOTE: You can configure either Layer 3 or Layer 4 load balancing, or both at the same
time
NOTE: On I chip platforms, an unknown Layer 4 header is excluded from load-balance
hashing to avoid undesired packet reorde... | [
{
"name": "outer-vlan-id",
"desc": "Include outer VLAN ID information in the hash key."
},
{
"name": "inner-vlan-id",
"desc": "Include inner VLAN ID information in the hash key.s"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
family multiservice and no-label-1-exp options introduced in Junos OS Release 8.0.
label-3 and no-labels options introduced in Junos OS Release 8.1.
ether-pseudowire statement introduced in Junos OS Release 9.1 (M320 and T Series routers only); support
extended to M120 ... | [
"Configuring Per-Packet Load Balancing",
"Configuring Load Balancing Based on MPLS Labels",
"Configuring Load Balancing Based on MAC Addresses"
] |
hash-key (Forwarding Options-QFX Series) | hash-key {
family {
inet {
layer-3;
layer-4;
inner-vlan-id;
outer-vlan-id;
}
}
multiservice {
source-mac;
destination-mac;
payload {
ip {
layer3-only;
layer-3 (source-ip-only |... | [edit forwarding-options]
[edit chassis fpc slot-number pic pic-number] | (QFX10000 switches only) Select which packet header data to use for per-flow load balancing.
NOTE: You can configure either Layer 3 or Layer 4 load balancing, or both at the same
time.
NOTE: On I chip platforms, an unknown Layer 4 header is excluded from load-balance
hashing to avoid undesired packet reordering. | [
{
"name": "inet",
"desc": "IPv4 address family."
},
{
"name": "layer-3",
"desc": "Incorporate Layer 3 data into the hash key."
},
{
"name": "layer-4",
"desc": "Incorporate Layer 4 data into the hash key."
},
{
"name": "outer-vlan-id",
"desc": "Include outer VLAN ID inform... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D10. | [] |
hash-keys (Aggregated Multiservices) | hash-keys {
egress-key (destination-ip | source-ip);
ingress-key (destination-ip | source-ip);
} | [edit services service-set service-set-name interface-service load-balancing-options] | Configure the hash keys used for load balancing in aggregated multiservices (AMS) for service
applications (Network Address Translation [NAT], stateful firewall, application-level gateway [ALG],
HTTP header enrichment, and mobility). The hash keys supported in the ingress and egress direction are
the source IP address ... | [
{
"name": "ingress-key",
"desc": ""
},
{
"name": "destination-ip",
"desc": "Use the destination IP address of the flow to compute the hash used in load balancing in the ingress flow direction."
},
{
"name": "ingress-key",
"desc": ""
},
{
"name": "source-ip",
"desc": "Use ... | 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. | [] |
hash-keys (Interfaces) | hash-keys {
egress-key (source-ip | destination-ip);
ingress-key (source-ip | destination-ip);
ipv6-source-prefix-length ipv6-source-prefix-length;
} | [edit interfaces unit unit-name load-balancing-options] | Configure the hash keys used for load balancing in aggregated multiservices (AMS) for next-hop style
services. The hash keys supported in the ingress and egress direction are the source IP address and
destination IP address.
Hash keys are used to define the load-balancing behavior among the various members in the AMS. ... | [
{
"name": "egress-key",
"desc": ""
},
{
"name": "destination-ip",
"desc": "Use the destination IP address of the flow to compute the hash used in load balancing. Configure the hash keys to be used in the egress flow direction."
},
{
"name": "egress-key source-ip",
"desc": "Use the so... | 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.
ipv6-source-prefix-length option introduced in Junos OS Release 18.2R1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. The ipv6-source-prefix-length option is not supported for
Next... | [
"Configuring Load Balancing on AMS Infrastructure"
] |
hash-mode | hash-mode {
layer2-header;
layer2-payload;
gtp-header-offset offset-value;
} | [edit forwarding-options enhanced-hash-key] | Select the mode for the hashing algorithm.
The hashing algorithm is used to make traffic-forwarding decisions for traffic entering a LAG bundle or
for traffic exiting a switch when ECMP is enabled.
For LAG bundles, the hashing algorithm determines how traffic entering a LAG bundle is placed onto the
bundle’s member lin... | [
{
"name": "layer-2-payload",
"desc": "Set the hashing algorithm to use fields in the Layer 2 payload to make hashing decisions."
},
{
"name": "layer-2-header",
"desc": "Set the hashing algorithm to use fields in the Layer 2 header to make hashing decisions."
},
{
"name": "gtp-header-offs... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15.
Statement is not supported on QFX10002 and QFX 10008 switches.
Hash mode option gtp-header-offset introduced in Junos OS Release 17.3R3 for QFX5000 line of
switches. | [
"Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic (CLI Procedure)",
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic"
] |
hash-parameters | hash-parameters {
ecmp {
function {
(crc16-bisync | crc16-ccitt | crc32-hi | crc32-lo);
}
offset offset;
preprocess;
}
lag {
function {
(crc16-bisync | crc16-ccitt | crc32-hi | crc32-lo);
}
offset offset;
preprocess;
... | [edit forwarding-options enhanced-hash-key],
[edit routing-instances name forwarding-options enhanced-hash-key] | Set traffic hashing parameters for ECMP or LAG traffic. | [
{
"name": "ecmp",
"desc": "Set hashing parameters for ECMP traffic."
},
{
"name": "function (crc16-bisync | crc16-ccitt",
"desc": ""
},
{
"name": "| crc32-hi | crc32-lo)",
"desc": "Set the hash functions for ECMP traffic or LAG traffic. Values:"
},
{
"name": "crc16-bisync",
... | interface | Statement introduced in Junos OS Release 19.1R1. | [
"Aggregated Ethernet Interfaces"
] |
hash-seed (profile) | hash-seed seed-value | [edit forwarding-options enhanced-hash-key profile1/profile2] | Configure a hash seed for load-balancing functions for the given load balancing profile (profile1 or
profile2). | [] | •
interface—To view this statement in the configuration.
•
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2 | [
"enhanced-hash-key profile1/profile2",
"load-balance profile1/profile2"
] |
hash-seed | hash-seed seed-value; | [edit forwarding-options enhanced-hash-key ] | Configure a hash seed for load-balancing functions.
By default, the QFX10002, QFX10008, QFX5220, QFX5130, and QFX5700 switches use the system
MAC address to generate a hash seed value. You can configure the hash seed value using the hash-seed
statement at the [edit forwarding-options enhanced-hash-key] hierarchy. Set ... | [
{
"name": "hash-seed seed-value",
"desc": "A hash seed value, in the range from 0 to 4294967295."
}
] | 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-D30. | [
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic (QFX",
"10002 and QFX 10008 Switches)"
] |
hcm (HTTP Header Enrichment) | hcm {
tag-attribute [tag-attr-name];
tag-rule rule-name {
term term-number {
from {
destination-address {
(any-ipv4 | any-ipv4 except);
(any-ipv6 | any-ipv6 except);
(any-unicast | any-unicast except);
... | [edit services] | Configure the parameters required to support subscriber-aware HTTP header enrichment.
You can add content to the HTTP headers sent back and forth as part of the client-server exchange for
subscribers accessing Web-based services. You configure HTTP header enrichment as a service for a
subscriber.
The remaining statemen... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support for Next Gen Services introduced in Junos OS Release 20.2R1 on MX Series routers MX240,
MX480 and MX960. | [
"Configuring HTTP Header Enrichment Overview"
] |
hcm-profile (HTTP Header Enrichment) | hcm-profile hcm-profile-name; | [edit services service-set] | Specify the HTTP header enrichment profile that was configured at the [edit services hcm] hierarchy
level. This placeholder profile has no configuration options, but it must be specified to enable HTTP
header enrichment functionality on the services plane. | [
{
"name": "hcm-profile-name",
"desc": "Name of the HCM profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 20.2R1 on MX Series routers MX240,
MX480 and MX960. | [
"Configuring HTTP Header Enrichment Overview"
] |
hcm-profile (PCC Action Profiles) | hcm-profile hcm-profile-name; | [edit unified-edge pcef pcc-action-profiles profile-name] | Specify the HCM profile that you want a PCC action profile to use for determining which HTTP header
enrichment rules to apply.
NOTE: This PCC action profile can be used in a PCC rule that only includes applications or
application-groups statements in the from statement, and these statements must identify
HTTP-based app... | [
{
"name": "hcm-profile-name",
"desc": "Name of the HCM 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 16.1.
Support added in Junos 20.2R1 for Next Gen Services on MX240, MX480, and MX960 routers. | [
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment"
] |
header-integrity-check (Next Gen Services) | header-integrity-check {
enable-all;
} | [edit services service-set service-set service-set-options] | Drop packets that have packet header anomalies. These anomalies include:
•
Not an IP packet
•
Not an IPv4 packet or an IPv6 packet
•
TTL error (TTL is 0)
•
Bad source/destination IP
•
IP checksum error
•
Protocol error
•
TCP port zero
•
TCP header length error (less than 20 bytes)
•
TCP SEQNUM is zero and no flags are ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
header-integrity-check | header-integrity-check {
enable-all;
} | [edit services service-set service-set service-set-options] | Configure Junos OS to verify the packet header for anomalies in IP, TCP, UDP, and ICMP information
and to flag such anomalies and errors.
Starting in Junos OS release 17.1R1, the header integrity check on the MS-MPC or MS-MIC drops any
packets with header anomalies and includes the following checks:
•
ICMP ping of dea... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 13.2. | [
"Configuring Protection Against Network Attacks on an MS-MPC"
] |
header-length | header-length {
match (equal | greater-than | less-than | not-equal);
value header-length;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the number of bytes in the TCP header. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value header-length",
"desc": "Match the number of bytes in the TCP header."
}
] | 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. | [] |
header-type | header-type {
match (equal | greater-than | less-than | not-equal);
value header-value;
} | [edit set security idp custom-attack attack-name attack-type signature protocol ipv6 extension-
header routing-header] | Specify the IPv6 routing header type. | [
{
"name": "value",
"desc": "Match a decimal value. Range: 0 through 255"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
health-monitor (KHMS) | health-monitor {
ifstate-clients {
(peer-stuck | non-peer-stuck | all-clients-stuck);
}
threshold-level {
(low | medium | high);
}
action {
(alarm | alarm-with-cores | restart);
}
} | [edit system] | Configure the kernel health monitoring system (KHMS). The KHMS is used to detect and take action on
stuck ifstate clients. Stuck ifstate clients can affect system performance. With this configuration
statement you can configure a time interval in which the system can detect a stuck ifstate client. You
also can configur... | [
{
"name": "ifstate-clients",
"desc": "Configure which ifstate clients you want to monitor and manage. There are three options:"
},
{
"name": "peer-stuck",
"desc": "Monitor and manage stuck peers."
},
{
"name": "non-peer-stuck",
"desc": "Monitor and manage stuck processes."
},
{
... | admin | Statement introduced in Junos OS Release 16.1R1. | [] |
health-monitor | health-monitor {
falling-threshold percentage;
interval seconds;
rising-threshold percentage;
idp {
falling-threshold percentage;
interval seconds;
rising-threshold percentage;
}
} | [edit snmp] | Configure health monitoring.
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 8.0.
Option idp introduced in Junos OS Release 9.3 for all supported platforms. | [
"Configuring Health Monitoring on Devices Running Junos OS"
] |
heartbeat-address (MX Series Virtual Chassis) | heartbeat-address (ip-address | ipv6-address); | [edit virtual-chassis] | Configure an IPv4 address or IPv6 address used to create an IP-based packet connection, known as a
heartbeat connection, between the primary router and backup router in an MX Series Virtual Chassis. To
ensure consistent access to the primary Routing Engine in the Virtual Chassis primary router (VC-Pp)
regardless of whi... | [
{
"name": "ip-address",
"desc": "IPv4 master-only address for the fxp0 management interface."
},
{
"name": "ipv6-address",
"desc": "IPv6 master-only address for the fxp0 management interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection",
"with Member Routers in the Same Subnet",
"Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection",
"with Member Routers in Different Subnets"
] |
heartbeat-interval | heartbeat-interval milliseconds; | [edit chassis cluster] | Set the interval between the periodic signals broadcast to the devices in a chassis cluster to indicate that
the active node is operational.
The heartbeat-interval option works in combination with the heartbeat-threshold option to define the wait
time before failover is triggered in a chassis cluster. The default value... | [
{
"name": "milliseconds",
"desc": "Time interval between any two heartbeat messages."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. Statement updated in Junos OS Release 10.4. | [] |
heartbeat-threshold | heartbeat-threshold number; | [edit chassis cluster] | Set the number of consecutive missed heartbeat signals that a device in a chassis cluster must exceed to
trigger failover of the active node.
The heartbeat-threshold option works in combination with the heartbeat-interval option to define the wait
time before failover is triggered in a chassis cluster. The default valu... | [
{
"name": "number",
"desc": "Number of consecutive missed heartbeats."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. Statement updated in Junos OS Release 10.4. | [] |
heartbeat-timeout (MX Series Virtual Chassis) | heartbeat-timeout seconds; | [edit virtual-chassis] | Configure the maximum time period within which a Virtual Chassis member router must respond to a
heartbeat packet sent by the other member router. When an adjacency disruption or split is detected in
the Virtual Chassis configuration, each member router sends a single heartbeat packet to the other
member router to dete... | [
{
"name": "seconds",
"desc": "Number of seconds within which a Virtual Chassis member router must respond to a heartbeat"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection",
"with Member Routers in the Same Subnet",
"Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection",
"with Member Routers in Different Subnets"
] |
heartbeat-tos (MX Series Virtual Chassis) | heartbeat-tos value; | [edit virtual-chassis] | Configure a network-specific value for the header field that defines either the type of service (ToS),
traffic class (TC), or differential services (DS) octet that is transmitted in the header of a heartbeat
packet.. This field is a single octet that ensures preferential delivery of heartbeat packets between
Virtual Ch... | [
{
"name": "value",
"desc": "Network-specific value of the ToS, TC, or DS octet transmitted in Virtual Chassis heartbeat"
},
{
"name": "must conform to the following RFC standards:",
"desc": "IPv4 ToS as defined in RFC 791, INTERNET PROTOCOL - DARPA INTERNET PROGRAM"
},
{
"name": "PROTOCO... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection",
"with Member Routers in the Same Subnet",
"Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection",
"with Member Routers in Different Subnets",
"Configuring a Virtual Chassis Hea... |
hello-acknowledgements | hello-acknowledgements; | [edit logical-systems logical-systems-name protocols rsvp],
[edit protocols rsvp] | Enable hello messages from nonsession neighbors to be acknowledged with a hello acknowledgment
message. Once hello acknowledgments are enabled, the router continues to acknowledge hello
messages from any nonsession RSVP neighbors unless the interface itself goes down or the
configuration is changed by an administrator.... | [] | 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 Hello Acknowledgments for Nonsession RSVP Neighbors"
] |
hello-dead-interval | hello-dead-interval milliseconds; | [edit logical-systems logical-system-name protocols link-management peer peer-name lmp-protocol],
[edit protocols link-management peer peer-name lmp-protocol] | Specify how long the Link Management Protocol (LMP) waits before declaring the control channel to be
dead. This is an interval during which the router receives no LMP hello packets from the neighbor on a
control that is active or up. | [
{
"name": "milliseconds",
"desc": "Interval to wait before declaring the control channel to be dead."
}
] | 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 Hello Message Intervals for LMP Control Channels"
] |
hello-interval (L2TP) | hello-interval seconds; | [edit services l2tp tunnel-group name] | Specify the keepalive timer for L2TP tunnels. | [
{
"name": "seconds",
"desc": "Interval, in seconds, after which the server sends a hello message if no messages are received. A"
}
] | 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 Timers for L2TP Tunnels",
"Configuring an L2TP Tunnel Group for LNS Sessions with Inline Services Interfaces"
] |
hello-interval (LMP) | hello-interval milliseconds; | [edit logical-systems logical-system-name protocols link-management peer peer-name lmp-protocol],
[edit protocols link-management peer peer-name lmp-protocol] | Specify how often the router sends Link Management Protocol (LMP) hello packets. | [
{
"name": "milliseconds",
"desc": "Length of time between hello packets."
}
] | 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. | [
"Configuring Hello Message Intervals for LMP Control Channels"
] |
hello-interval (Protocols LDP) | hello-interval seconds; | [edit logical-systems logical-system-name protocols ldp interface interface-name],
[edit logical-systems logical-system-name protocols ldp targeted-hello],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp
interface interface-name],
[edit logical-systems logical-system-nam... | Control the LDP timer that regulates how often hello messages are sent. You can control the rate both
link hello messages and targeted hello messages are sent depending on the hierarchy level at which you
configure the hello-interval statement. | [
{
"name": "seconds",
"desc": "Length of time between transmission of hello packets."
}
] | 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 LDP targeted hellos added in Junos OS Release 9.5. | [
"Configuring the LDP Timer for Hello Messages"
] |
hello-interval (Protocols RSVP) | hello-interval seconds; | [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 interface interface-name],
[edit protocols rsvp peer-interface peer-interface-name] | Enable the sending of hello packets on the interface. | [
{
"name": "seconds",
"desc": "Length of time between hello packets. A value of 0 disables the sending of hello packets on the"
}
] | 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 RSVP Hello Interval"
] |
hello-interval | hello-interval seconds; | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name],
[edit protocols pim interface (Protocols PIM) interface-name],
[edit routing-i... | Specify how often the routing device sends PIM hello packets out of an interface. | [
{
"name": "seconds",
"desc": "Length of time between PIM hello packets."
}
] | 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. | [
"Modifying the PIM Hello Interval"
] |
hello-message (NETCONF) | hello-message {
yang-module-capabilities {
advertise-native-yang-modules;
advertise-custom-yang-modules;
advertise-standard-yang-modules;
}
} | [edit system services netconf] | Configure the NETCONF server to advertise additional capabilities in the NETCONF capabilities
exchange. The NETCONF server emits the <hello> element and the <capabilities> child element with the
list of capabilities at the start of the NETCONF session.
Default
If you do not include the hello-message statement, the NETC... | [
{
"name": "yang-module-capabilities",
"desc": "Configure the YANG modules that the NETCONF server advertises in the NETCONF capabilities exchange. The following statements are supported:"
},
{
"name": "advertise-custom-yang-modules",
"desc": "Advertise third-party YANG modules installed on the"
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1 and Junos OS Evolved Release 21.1R1. | [
"Starting the NETCONF Session"
] |
hello-time | hello-time seconds; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-ins... | For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol
(VSTP), or Multiple Spanning Tree Protocol (MSTP), specifies the number of seconds between
transmissions of configuration BPDUs by the root bridge.
Default
2 seconds | [
{
"name": "seconds",
"desc": "(Optional) Number of seconds between transmissions of configuration BPDUs."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding MSTP",
"Understanding VSTP",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Configuring Faster Convergence and Network Stability on ELS Switches with RSTP",
"Example: Faster Convergence and Improved Network Stability with RSTP on EX Series Switches"
] |
hello-timer | hello-timer milliseconds; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, configure the rate at which hello messages are sent. A hello message is
transmitted after a period defined in milliseconds has elapsed. | [
{
"name": "milliseconds",
"desc": "The rate at which hello messages are sent."
}
] | 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"
] |
help | help < (apropos string | reference statement-name| syslog syslog-tag| tip cli number | topic
word)> | Display help about available operational commands, configuration statements, or general information
about getting help. Entering the help command without an option provides introductory information
about how to use the help and ? commands. | [
{
"name": "apropos string",
"desc": "(Optional) Display command names and help text that matches the string specified. If the"
},
{
"name": "reference statement-name",
"desc": "(Optional) Display summary information for a configuration statement. This"
},
{
"name": "syslog syslog-tag",
... | None | Command introduced before Junos OS Release 7.4.
The apropos option was added in Junos OS Release 8.0. | [
"Getting Online Help from the Junos OS Command-Line Interface"
] | |
helper-disable (LDP) | helper-disable; | [edit logical-systems logical-system-name protocols ldp graceful-restart],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp
graceful-restart],
[edit protocols ldp graceful-restart],
[edit routing-instances routing-instance-name protocols ldp graceful-restart] | Disable helper mode for LDP graceful restart. When helper mode is disabled, a router cannot help a
neighboring router that is attempting to restart LDP.
Default
Helper mode is enabled by default on all routing protocols (including LDP) that support graceful restart. | [] | 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 LDP Graceful Restart"
] |
helper-disable (Multiple Protocols) | helper-disable; | [edit logical-systems logical-system-name protocols (isis | ldp | ospf | ospf3 | rsvp) graceful-
restart],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ldp
| ospf | ospf3) graceful-restart],
[edit protocols (isis | ldp | ospf | ospf3 | rsvp) graceful-restart],
[edit rout... | Disable helper mode for graceful restart. When helper mode is disabled, a router or switch cannot help a
neighboring router that is attempting to restart.
Default
Helper mode is enabled by default for these supported protocols: IS-IS, LDP, OSPF/OSPFv3, and RSVP. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Routing Protocols Graceful Restart",
"Configuring Graceful Restart for MPLS-Related Protocols"
] |
helpers | helpers {
bootp {
client-response-ttl number;
description text-description;
interface interface-group {
client-response-ttl number;
description text-description;
maximum-hop-count number;
minimum-wait-time seconds;
no-listen;
... | [edit forwarding-options] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring DNS and TFTP Packet Forwarding",
"Configuring Port-based LAN Broadcast Packet Forwarding",
"Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents"
] |
hide-avps | hide-avps; | [edit services l2tp tunnel-group name] | Hide L2TP attribute-value pairs if the secret shared between the two ends of the tunnel is known.
NOTE: This statement is not supported for L2TP LNS on MX Series routers.
Default
Attribute-value pairs that can be hidden are exposed, even if the secret information is known. | [] | 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. | [
"Hiding Attribute-Value Pairs for L2TP Tunnels"
] |
hide-via-headers | hide-via-headers disable; | [edit security alg sip ] | The configuration set security alg sip hide-via-header disable controls the stripping of via headers in SIP
request messages. By default, the via headers are stripped. If the configuration is set to enable, only the
first via header will receive NAT translation from the SIP ALG. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [] |
hierarchical-policer (aggregate or premium) | hierarchical-policer hierarchical-policer-name | uid {
aggregate {
if-exceeding {
bandwidth-limit bps;
burst-size-limit bytes;
}
then {
discard;
}
}
premium {
if-exceeding {
bandwidth-limit bps;
burst-size-li... | [edit dynamic-profiles profile-name firewall],
[edit firewall] | Use a hierarchical policer to rate-limit ingress Layer 2 traffic at a physical or logical interface and apply
different policing actions based on whether the packets are classified as premium for expedited forwarding
(EF) or aggregate for a lower priority. The two policers defined within the hierarchical policer are ag... | [
{
"name": "hierarchical-policer-name",
"desc": "Name that identifies the policer. The name can contain letters, numbers, and"
},
{
"name": "uid",
"desc": "When you configure a hierarchical policer at the [edit dynamic-profiles profile name firewall] hierarchy"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles profile-name firewall] hierarchy level introduced in Junos OS Release
11.4.
Support for if-exceeding-pps statement on MX Series routers with MPCs introduced in Junos OS Release
15.2. | [
"Hierarchical Policer Configuration Overview",
"Hierarchical Policers",
"bandwidth-limit (Hierarchical Policer)",
"pps-limit (Hierarchical Policer)",
"packet-burst (Hierarchical Policer)",
"if-exceeding-pps (Hierarchical Policer)"
] |
hierarchical-policer | hierarchical-policer name {
aggregate {
if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
then {
discard;
}
}
premium {
if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
then {
discard;
}
} | [edit firewall] | For M40e, M120, and M320 (with FFPC and SFPC) edge routers and T320, T640, and T1600 core
routers with Enhanced Intelligent Queuing (IQE) PICs, specify a hierarchical policer. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Applying Policers",
"Junos OS Class of Service User Guide for Routing Devices"
] |
hierarchical-scheduler (Subscriber Interfaces on MX Series Routers) | hierarchical-scheduler {
implicit-hierarchy;
maximum-hierarchy-levels number;
} | [edit interfaces interface-name] | Configure hierarchical scheduling options on the interface.
The statement is supported on the following interfaces:
•
MIC and MPC interfaces in MX Series routers
•
GRE tunnel interfaces configured on physical interfaces hosted on MIC or MPC line cards in MX
Series routers
To enable hierarchical scheduling on MX Series ... | [
{
"name": "implicit-hierarchy",
"desc": "Configure four-level hierarchical scheduling. When you include the implicit-hierarchy option, a hierarchical relationship is formed between the CoS scheduler nodes at level 1, level 2, level 3, and level 4. The implicit-hierarchy option is supported only on MPC/MIC s... | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
implicit-hierarchy option added in Junos OS Release 13.1.
Support on GRE tunnel interfaces configured on physical interfaces on MICs or MPCs in MX Series
routers added in Junos OS Release 13.3.
Support for up to four hierarchy levels added in Junos OS Release 16.1. | [
"Understanding Hierarchical CoS for Subscriber Interfaces",
"Configuring Hierarchical CoS for a Subscriber Interface of Aggregated Ethernet Links",
"Configuring Hierarchical Schedulers for CoS",
"Configuring Hierarchical CoS on a Static PPPoE Subscriber Interface",
"Hierarchical CoS on MPLS Pseudowire Subsc... |
hierarchical-scheduler | hierarchical-scheduler {
implicit-hierarchy;
maximum-hierarchy-levels number;
} | [edit interfaces]
[edit dynamic-profiles name interfaces],
[edit dynamic-profiles name logical-systems name interfaces] | Enable the use of hierarchical schedulers. If you do not include this statement, the interfaces on the
router cannot use hierarchical interfaces.
NOTE: When configuring hierarchical scheduling for network slices on an interface, you
do not need to enable vlan-tagging on that interface.
NOTE: To enable hierarchical sche... | [
{
"name": "implicit-hierarchy",
"desc": "For MPC/MIC subscriber interfaces and interface sets running over aggregated Ethernet on MX Series routers, form a hierarchical relationship between the CoS scheduler nodes at level 1, level 2, and level 3."
},
{
"name": "maximum-hierarchy-levels",
"desc"... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Hierarchical Schedulers for CoS",
"Understanding Hierarchical CoS for Subscriber Interfaces"
] |
high-availability (Chassis) | high-availability {
grid-id id;
hardware-upgrade;
local-domain-id id <domain-size domain-size>;
local-id id <local-forwarding-ip loopback-address> <local-ip local-ip>;
peer-domain-id name {
domain-size domain-size;
peer-id name {
desc desc;
interface inter... | [edit chassis] | Configure Multinode High Availability options on SRX Series Firewalls. | [
{
"name": "grid-id",
"desc": "Grid identifier number. Range:1 through 15"
},
{
"name": "hardware-upgrade",
"desc": "Enable hardware upgrade state. \"local-domain-id\" on page 10358 Local domain identifier for four-Node multinode high availability setup."
},
{
"name": "\"local-id\" on pa... | interface | Statement introduced in Junos OS Release 20.4R1. | [
"Multinode High Availability",
"Example: Configure Multinode High Availability in a Layer 3 Network",
"Example: Configure Multinode High Availability in a Default Gateway Deployment",
"Example: Configure Multinode High Availability in a Default Gateway Deployment"
] |
high-availability (security cloud) | high-availability {
aws {
eip-based;
peer-liveliness {
probe-ip {
destination-ip-address;
source-ip source-ip-address;
}
}
azure {
... | [edit security cloud] | Configure vSRX Virtual Firewall instances to work in Multinode High Availability mode with Amazon
Web Services (AWS) or Microsoft Azure Cloud or Google Cloud Platform (GCP). | [
{
"name": "aws",
"desc": "Define deployment type as AWS."
},
{
"name": "EIP-based",
"desc": "Deployment type based on EIP."
},
{
"name": "peer-liveliness",
"desc": "Configure activeness probe options."
},
{
"name": "probe-ip destination-ip",
"desc": "IP address for active... | interface | Statement introduced in Junos OS Release 24.4R1. | [
"Multinode High Availability Support for vSRX Instances"
] |
high-availability (Security IDP) | high-availability {
no-policy-cold-synchronization;
} | [edit security idp sensor-configuration] | Configures high availability (chassis cluster) for IDP. | [] | 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. | [] |
high-availability-options (Aggregated Multiservices) | high-availability-options {
(many-to-one | one-to-one) {
preferred-backup preferred-backup;
}
} | [edit interfaces interface-name load-balancing-options] | Configure the high availability options for the aggregated multiservices (AMS) interface. For service
applications, if only the load-balancing feature is being used, then this configuration is optional.
For many-to-one (N:1) high availability support for service applications like Network Address Translation
(NAT), 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.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
high-cos-queue-threshold | high-cos-queue-threshold number; | [edit system services resource-monitor] | Configure the class-of-service (CoS) queue threshold by percentage.
NOTE: This feature is only available when you enable subscriber management. For more
information on enabling subscriber management, see Configuring Junos OS Enhanced
Subscriber Management.
This CoS resource monitoring feature bases admission decisions ... | [
{
"name": "number",
"desc": "High-threshold percentage for CoS queue utilization per scheduler. When CoS queue utilization on a given FPC reaches that FPC's configured threshold level, further subscriber logins on that FPC are not allowed. This resource monitoring mechanism provides adjustable safety margin... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"Resource Monitoring for Subscriber Management and Services Overview"
] |
high-polarization | high-polarization; | [edit interfaces interface-name optics-options] | Enable the physical port to rapidly track the state of polarization changes. Enabling this statement
reduces the optical signal to noise ratio (OSNR) by few tenths of dB.
Default
By default, the high-polarization statement is disabled. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1 for ACX6360 routers. | [
"Supported Optics Options on ACX6360 and ACX5448-D Routers"
] |
high-power | high-power; | [edit poe interface (all | interface-name)] | Configure a four-pair PoE port to deliver up to 60 W of power. The four-pair PoE standard allows for
power to be delivered over all four pairs of wires in a standard CAT5/6 RJ-45 Ethernet cable.
When you configure the four-pair PoE port with the high-power option, the port provides up to 60 W of
power, even if the powe... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Configuring PoE Interfaces on EX Series Switches"
] |
high-threshold (Resource Monitor) | high-threshold number; | [edit system services resource-monitor] | Configure the high threshold value, exceeding which warnings or error logs are generated, for all the
regions of memory, such as heap or ukernel, next-hop and encapsulation, and firewall filter memory. You
can configure the resource-monitoring capability on MX80, MX104, MX240, MX480, MX960, MX2010,
and MX2020 routers w... | [
{
"name": "number",
"desc": "High threshold percentage for memory resource utilization Range: 1 through 100"
}
] | 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. | [] |
high-watermark | high-watermark percent; | [edit security flow aging] | Sets the point at which the aggressive aging-out process begins. | [
{
"name": "percent",
"desc": "Percentage of session-table capacity at which aggressive aging-out starts."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
hint | hint [ hint-strings ]; | [edit services nat pool nat-pool-name pgcp] | Configure a hint that enables the border gateway function (BGF) to choose a NAT pool by direction
rather than by virtual interface. The BGF matches the configured hint with a termination hint located in
the Direction field of a nonstandard termination ID.
Default
When no hint is configured, the BGF can choose any NAT p... | [
{
"name": "hint-string",
"desc": "Alphanumeric string of up to three characters that the BGF uses to match with a"
}
] | 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. | [] |
history | history history-index {
bucket-size number;
interface interface-name;
interval seconds;
owner owner-name;
} | [edit snmp rmon] | Configure RMON history group entries. This RMON feature can be used with the Simple Network
Management Protocol (SNMP) agent in the switch to monitor all the traffic flowing among switches on
all connected LAN segments. The RMON history feature collects statistics in accordance with user-
configurable parameters.
The h... | [
{
"name": "history-index",
"desc": "Tag the history entries with a number."
}
] | snmp—To view this statement in the configuration.
snmp–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Understanding RMON",
"RMON MIB Event, Alarm, Log, and History Control Tables",
"Configuring RMON History Sampling",
"Monitoring RMON MIB Tables",
"Junos OS Network Management Configuration Guide"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.