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 |
|---|---|---|---|---|---|---|---|
history-size | history-size size; | [edit services monitoring rpm owner name test name] | Specify the number of stored history entries. | [
{
"name": "size",
"desc": "Value from 0 to 255."
}
] | 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.
Statement at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in Junos OS Release 15.1 for MX Series routers.
Statement introduced in Junos OS Evolved Release 20.1R1. | [
"Configuring BGP Neighbor Discovery Through RPM",
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
hold off time | hold-off-time time; | [edit chassis synchronization source interfaces] | Enable hold-off time for Synchronous Ethernet interfaces and external clock source interfaces. If an
interface goes down, hold-off time delays short signal failures from being sent to the clock selection
process to prevent rapid successive switching. | [
{
"name": "time",
"desc": "Amount of time in milliseconds that a signal is held before being passed to the clock selection process. Range: 300–1800 milliseconds Default: 1000 milliseconds"
}
] | 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 Clock Synchronization Interface on MX Series Routers",
"Ethernet Synchronization Message Channel Overview"
] |
hold-down | hold-down {
seconds;
flaps number;
period seconds;
} | [edit logical-systems logical-system-name routing-options bmp],
[edit logical-systems logical-system-name routing-options bmp station station-name],
[edit routing-options bmp],
[edit routing-options bmp station station-name] | If the connection to a BMP station flaps and the hold-down statement is configured, the station is
prevented from reconnecting to the device for the specified period of time. A flap is when the TCP
session unexpectedly switches from established to non-established. If you alter the configuration of the
hold-down stateme... | [
{
"name": "seconds",
"desc": "Specify the time in seconds to wait before allowing the BMP station to reconnect to the device. Default: 600 seconds Range: 30 through 65,535 seconds"
},
{
"name": "flaps",
"desc": ""
},
{
"name": "number",
"desc": "Specify the number of BMP station fl... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15. | [
"Configuring BGP Monitoring Protocol Version 3"
] |
hold-down-interval | hold-down-interval number; | [edit chassis cluster redundancy-group group-number] | Set the minimum interval to be allowed between back-to-back failovers for the specified redundancy
group (affects manual failovers, as well as automatic failovers associated with monitoring failures).
For redundancy group 0, this setting prevents back-to-back failovers from occurring less than 5 minutes
(300 seconds) a... | [
{
"name": "number",
"desc": "Number of seconds specified for the interval."
}
] | 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. | [] |
hold-interval (Clock Synchronization) | hold-interval {
configuration-change seconds;
restart seconds;
switchover seconds;
} | [edit chassis synchronization] | Configure the wait time for clock selection after a change in configuration and after a reboot of the
router, and configure the switchover wait time after clock recovery. | [
{
"name": "configuration-change",
"desc": "Set the wait time for clock selection after a change in configuration. Range: 15 seconds through 60 seconds"
},
{
"name": "restart",
"desc": "Set the wait time for clock selection after reboot of the router. Range: 60 seconds through 180 seconds Defa... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2R4. | [] |
hold-interval (OAM CFM, for EX Series Switch Only) | hold-interval minutes; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Configure the time to wait before flushing the maintenance association end point (MEP) database, if no
updates occur. | [
{
"name": "minutes",
"desc": "Time to wait, in minutes."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
hold-interval (OAM) | hold-interval minutes; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | The time to wait in minutes before flushing the maintenance association end point (MEP) database, if no
updates occur. The configurable range is 1 minute through 30240 minutes.The default value is 10
minutes.
NOTE: Hold timer based flushing is applicable only for auto discovered remote MEPs
and not for statically confi... | [
{
"name": "minutes",
"desc": "Time to wait, in minutes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Continuity Check Protocol Parameters Overview",
"Configuring Continuity Check Protocol Parameters for Fault Detection"
] |
hold-interval (Protection Group) | hold-interval number; | [edit protocols protection-group ethernet-ring name] | Specify the hold-off timer interval for all rings in 100 millisecond (ms) increments. | [
{
"name": "number",
"desc": "Hold-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. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS"
] |
hold-interval | hold-interval seconds; | [edit security dynamic-address session-scan] | If you enable the session-scan option at the [edit security dynamic-address address-name name] hierarchy level,
the security device initiates session scan when:
•
You add a new address into the dynamic-address entry.
•
The system reaches the configured hold-interval time. | [
{
"name": "seconds",
"desc": "Time interval before the session scan requests in seconds. Range: 1 thru 3600 seconds Default: 10 seconds"
}
] | security | Statement introduced in Junos OS Release 20.4R1. | [] |
hold-time (ae interface) | hold-time up milliseconds down milliseconds; | [edit interfaces interface-name],
[edit interfaces interface-range interface-range-name]
Hierarchy Level (ae- interfaces) (PTX5000, PTX1000, PTX10002, PTX10008,
PTX10016, and MX Series routers)
[edit interfaces ae{x}] | Specify the hold-time value to use to damp shorter interface transitions milliseconds. The hold timer
enables interface damping by not advertising interface transitions until the hold timer duration has
passed. When a hold-down timer is configured and the interface goes from up to down, the down hold-
time timer is tri... | [
{
"name": "down milliseconds",
"desc": "Hold time to use when an interface transitions from up to down. Junos OS advertises"
},
{
"name": "up milliseconds",
"desc": "Hold time to use when an interface transitions from down to up. Junos OS advertises"
}
] | 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.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"advertise-interval",
"Physical Interface Damping Overview",
"Damping Shorter Physical Interface Transitions",
"Damping Longer Physical Interface Transitions"
] |
hold-time (OAM) | hold-time seconds; | [edit protocols oam],
[edit protocols oam gre-tunnel interface interface-name] | Length of time the originating end of a GRE tunnel waits for keepalive packets from the other end of the
tunnel before marking the tunnel as operationally down. | [
{
"name": "seconds",
"desc": "Hold-time value."
}
] | 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. | [
"Configuring Tunnel Interfaces on an MX Series Router with a 16x10GE 3D MPC",
"Configuring GRE Keepalive Time"
] |
hold-time (Protocols BGP) | hold-time seconds; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Specify the hold-time value to use when negotiating a connection with the peer. The hold time is three
times the interval at which keepalive messages are sent. For the default hold time of 90 seconds, the
keepalive interval is 30 seconds. If a BGP speaker does not receive a keepalive, update, or notification
message fr... | [
{
"name": "seconds",
"desc": "Hold time."
}
] | 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. | [
"BGP Messages Overview"
] |
hold-time (Protocols DVMRP) | hold-time seconds; | [edit logical-systems logical-system-name protocols dvmrp interface interface-name],
[edit protocols dvmrp interface interface-name] | Specify the time period for which a neighbor is to consider the sending router (this router) to be
operative (up). | [
{
"name": "seconds",
"desc": "Hold time."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | NOTE: Distance Vector Multicast Routing Protocol (DVMRP) was deprecated in Junos
OS Release 16.1. Although DVMRP commands continue to be available and configurable
in the CLI, they are no longer visible and are scheduled for removal in a subsequent
release.
Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring DVMRP"
] |
hold-time (Protocols IS-IS) | hold-time seconds; | [edit logical-systems logical-system-name protocols isis interface interface-name level level-
number],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name level level-number],
[edit protocols isis interface interface-name level level-number],
[edit... | Set the length of time a neighbor considers this router to be operative (up) after receiving a hello packet.
If the neighbor does not receive another hello packet within the specified time, it marks this routing
device as inoperative (down). The hold time itself is advertised in the hello packets.
The hold time specifi... | [
{
"name": "seconds",
"desc": "Hold-time value, in seconds."
},
{
"name": "solutions:",
"desc": "Set the hello and hold time interval for LAN adjacencies to 30 seconds and 90 seconds respectively on both the DIS router and a neighboring router. Convert the LAN interfaces to point-to-point IS-IS ... | 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 Graceful Routing Engine Switchover",
"Example: Configuring IS-IS",
"Example: Configuring IS-IS for GRES with Graceful Restart",
"Understanding IS-IS Configuration",
"hello-interval"
] |
hold-time (Protocols LDP) | hold-time 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... | Specify how long an LDP node should wait for a hello message before declaring a neighbor to be down.
This value is sent as part of a hello message so that each LDP node tells its neighbors how long to wait.
You can specify times for both link hello messages and targeted hello messages depending on the
hierarchy level a... | [
{
"name": "seconds",
"desc": "Hold-time value."
}
] | 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 Delay Before LDP Neighbors Are Considered Down"
] |
hold-time (Protocols MSDP) | hold-time seconds; | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name protocols msdp group group-name peer address],
[edit logical-systems logical-system-name protocols msdp peer address],
[edit logical-systems logical-system-name routing-instances instance-name protocols msdp],
[edit log... | Specify the hold-time period to use when maintaining a connection with the MSDP peer. If a keepalive
message is not received for the hold-time period, the MSDP peer connection is terminated. According to
the RFC 3618, Multicast Source Discovery Protocol (MSDP), the recommended value for the hold-time
period is 75 secon... | [
{
"name": "seconds",
"desc": "Hold time."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Examples: Configuring MSDP"
] |
hold-time (Protocols PIM) | hold-time seconds; | [edit logical-systems logical-system-name protocols pim rp bidirectional address address],
[edit logical-systems logical-system-name routing-instances instance-name protocols pim rp
bidirectional address address],
[edit protocols pim rp bidirectional address address],
[edit protocols pim rp local family (inet | inet6)... | Specify the time period for which a neighbor is to consider the sending routing device (this routing
device) to be operative (up). | [
{
"name": "seconds",
"desc": "Hold time."
}
] | 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",
"Example: Configuring Bidirectional PIM"
] |
hold-time (Redundant Ethernet Interfaces) | hold-time (up | down) timer | [edit interfaces interface-name ] | The hold timer enables interface damping by not advertising interface transitions until the hold timer
duration has passed. When a hold-down timer is configured for a parent RETH interface and the primary
child interface goes from up to down, the down hold-time timer is triggered. Every interface transition
that occurs... | [
{
"name": "down seconds",
"desc": "Hold time to use when an interface transitions from up to down."
},
{
"name": "up seconds",
"desc": "Hold time to use when an interface transitions from down to up."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"Physical Interface Damping Overview"
] |
hold-time (VRRP) | hold-time seconds; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id preempt],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id preempt],
[edit logical-systems logical-system-name interfaces interface-name unit logical-... | In a Virtual Router Redundancy Protocol (VRRP) configuration, set the hold time before a higher-priority
backup router preempts the primary router.
Default
VRRP preemption is not timed. | [
{
"name": "seconds",
"desc": "Hold-time period."
}
] | 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 a Backup Router to Preempt the VRRP Primary Router",
"Configuring VRRP Preemption and Hold Time"
] |
hold-time up | hold-time up timer-value; | [edit interfaces aex aggregated-ether-options lacp] | Specifies the time period for which the Link Aggregation Control Protocol (LACP) maintains the state of
a child (member) link as expired or default.
When a child link goes from the current state to the expired state, the LACP monitors the reception of
protocol data units (PDUs) on the child link for the configured hold... | [
{
"name": "timer-value",
"desc": "Hold-up interval in seconds."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring LACP for Aggregated Ethernet Interfaces",
"Configuring Aggregated Ethernet LACP (CLI Procedure)"
] |
hold-time | hold-time seconds; | [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id preempt] | Configure the time in seconds after which a backup router with the highest priority preempts the
primary router. | [
{
"name": "seconds",
"desc": "Hold-time period."
}
] | 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. | [
"Configuring VRRP for IPv6 (CLI Procedure)"
] |
holddown (candidate-uplink-port-profile) | holddown interval; | [edit policy-options satellite-policies candidate-uplink-port-profileprofile-name]
[edit policy-options satellite-policies candidate-uplink-port-profile profile-name term term-
name from] | Configures the interval of time uplink failure detection waits before trying to try re-enable a satellite
device’s extended ports after shutting them down due to an uplink port failure. It is intended to avoid
port flapping on the extended ports when uplink port connectivity is unstable.
Default
The default holddown in... | [
{
"name": "interval",
"desc": "The holddown interval, in seconds. Valid values are 1-600 seconds."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
holddown (Protocols RIP) | holddown seconds; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit protocols rip],
[edit routing-instances routing-instance-name protocols rip] | Configure how long the expired route is retained in the routing table before being removed.
When the hold-down timer runs on RIP demand circuits, routes are advertised as unreachable on other
interfaces. When the hold-down timer expires, the route is removed from the routing table if all
destinations detect that the ro... | [
{
"name": "seconds",
"desc": "Estimated time to wait before making updates to the routing table."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring RIP Timers",
"RIP Demand Circuits Overview"
] |
holddown (Protocols RIPng) | holddown seconds; | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng],
[edit protocols ripng],
[edit routing-instances routing-instance-name protocols ripng] | Configure how long the expired route is retained in the routing table before being removed. | [
{
"name": "seconds",
"desc": "Estimated time to wait before removing expired routes from the routing table."
}
] | 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 routing instances introduced in Junos OS Release 9.0. | [
"Example: Configuring RIPng Update Interval"
] |
holddown-interval (protocols ldp) | holddown-interval holddown-interval; | [edit logical-systems logical-system-name protocols ldp oam bfd-livenesss-detection],
[edit logical-systems logical-system-name protocols ldp oam fec address bfd-livenesss-detection],
[edit protocols ldp oam bfd-livenesss-detection],
[edit protocols ldp oam fec address bfd-livenesss-detection] | Specify how long the BFD session should be up before adding the route or next hop. Specifying a time
of 0 seconds causes the route or next hop to be added as soon as the BFD session comes back up. | [
{
"name": "holddown-interval",
"desc": "Number of seconds the BFD session should remain up before adding the route or next"
}
] | 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 Holddown Interval for the BFD Session"
] |
holddown-interval | holddown-interval milliseconds; | [edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd],
[edit forwarding-options dhcp-relay liveness-detection method bfd], [edit forwarding-options
dhcp-relay dhcpv6 liveness-detection method bfd],
[edit system services dhc... | Configure the time (in milliseconds) for which Bidirectional Forwarding Detection (BFD) holds a session
up notification. | [
{
"name": "milliseconds",
"desc": "Interval specifying how long a BFD session must remain up before a state change"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients"
] |
holdover-mode-disable | holdover-mode-disable; | [edit chassis synchronization output interfaces external],
[edit chassis synchronization output interfaces (external-0/0 | external-1/0)] | Disable the holdover mode on the external output interface—external—on SCBE or on the external
output interfaces—external-0/0 and external-1/0—on SCBE2. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
holdover-time-error-budget | holdover-time-error-budget holdover-time-error-budget; | [edit logical-systems name protocols ptp]
[edit protocols ptp] | Configure the PTP clock hold-over-in-specification time error budget. The range supported is 0 to
10000 nano seconds.
Default
400 nanoseconds | [] | routing | Statement introduced in Junos OS Release 20.4R1. | [
"IEEE 1588v2 Precision Timing Protocol (PTP)",
"Precision Time Protocol Overview"
] |
home-address | home-address {
match (equal | greater-than | less-than | not-equal);
value value;
} | [edit set security idp custom-attack attack-name attack-type signature protocol ipv6 extension-
header destination-option] | Specify the IPv6 home address of the mobile node. | [
{
"name": "value",
"desc": "Match a decimal value."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
hop-by-hop-header | hop-by-hop-header {
CALIPSO-option;
RPL-option;
SFM-DPD-option;
jumbo-payload-option;
quick-start-option;
router-alert-option;
user-defined-option-type low | <to high>;
} | [edit security screen ids-option screen-name ip ipv6-extension-header] | Define the IPv6 hop-by-hop screen option. | [
{
"name": "CALIPSO-option",
"desc": "Enable the Common Architecture Label IPv6 Security Option."
},
{
"name": "RPL-option",
"desc": "Enable the Routing Protocol for Low-Power and Lossy Networks screen option."
},
{
"name": "SMF-DPD-option",
"desc": "Enable the Simplified Muliticast F... | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"Understanding IPv6 Support for Screens"
] |
hop-limit | hop-limit number; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name fast-
reroute],
secondary) path-name],
[edit logical-systems logical-system-name proto... | Specify the maximum number of routers that an LSP can traverse. This limit can be applied to any of the
following:
•
LSPs—The configured hop limit includes the ingress and egress routers. You can specify a hop limit
for an LSP and for both primary and secondary paths.
•
Fast reroute detour—Specify the number of additio... | [
{
"name": "number",
"desc": "Maximum number of hops."
}
] | 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 Fast Reroute",
"Limiting the Number of Hops in LSPs",
"Configuring the Hop Limit for Bypass LSPs"
] |
host (Address-Assignment Pools) | host hostname {
hardware-address mac-address;
ip-address ip-address;
} | [edit access address-assignment pool pool-name family (inet | inet6)] | Configure a static binding for the specified client. | [
{
"name": "hostname",
"desc": "Name of the client."
},
{
"name": "hardware-address mac-address",
"desc": "Specify the MAC address of the client. This is the hardware address that identifies the client on the network."
},
{
"name": "mac-address",
"desc": "MAC address of the client."
... | 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. | [
"Address-Assignment Pools for Subscriber Management"
] |
host (Diameter Origin) | host hostname; | [edit access diameter origin] | Specify the name of the host that originates the Diameter message. | [
{
"name": "hostname",
"desc": "Name of the message origin host. Supplied as the value of the Origin-Host AVP for all messages sent by the Diameter instance."
}
] | 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. | [] |
host (Interfaces) | host hostname {
services severity-level;
facility-override facility-name;
log-prefix prefix-value;
port port-number;
} | [edit interfaces interface-name services-options syslog] | Specify the hostname for the system logging utility.
Starting with Junos OS release 17.4R1, you can configure up to a maximum of four system log servers
(combination of local system log hosts and remote system log collectors) for each service set for ms
interface under [edit interfaces interface-name services-options]... | [
{
"name": "hostname",
"desc": "Name of the system logging utility host machine. This can be the local Routing Engine or an"
}
] | 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.
You can configure multiple system log hosts from Junos OS Release 17.4R1 onwards. | [
"Applying Filters and Services to Interfaces"
] |
host (L2TP) | host hostname {
services severity-level;
facility-override facility-name;
log-prefix prefix-value;
} | [edit services l2tp tunnel-group group-name syslog] | Specify the hostname for the system logging utility. | [
{
"name": "hostname",
"desc": "Name of the system logging utility host machine. This can be the local Routing Engine or an"
}
] | 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 System Logging of L2TP Tunnel Activity"
] |
host (Next Gen Services Service-Set Remote System Logging) | host host-ip-address;
host log-tag log-tag;
host port port-number;
host routing-instance routing-instance; | edit services service-set name syslog stream stream-name | Specify the IP address of syslog server to receive log messages. | [
{
"name": "log-tag",
"desc": "Tag included in logs to this host."
},
{
"name": "port",
"desc": "Port number of the host."
},
{
"name": "routing-instance",
"desc": "Name of the routing-instance."
}
] | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
host (Security IDP Sensor Configuration) | host ip-address <port number>; | [edit security idp sensor-configuration packet-log] | Configure the IP address and port number of the server where the packet capture object will be sent. | [
{
"name": "host ip-address",
"desc": "The IP address of the server where the packet capture object will be sent."
},
{
"name": "port number",
"desc": "The port number of the server where the packet capture object will be sent."
}
] | 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. | [] |
host (Security Log) | host {
ip-address;
port port-number;
routing-instance instance-name;
} | [edit security log stream stream-name]
[edit logical-systems name security log stream stream-name]
[edit tenants tenant-name security log stream stream-name] | You can specify the IP address of the server to which the security logs are streamed. | [
{
"name": "ip-address",
"desc": "Specify IP address of the host."
},
{
"name": "port port-number",
"desc": "Specify host port number."
},
{
"name": "routing-instance instance name",
"desc": "Specify the routing instance name that is used to send security logs to"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
The [edit logical-systems name security log stream stream-name] hierarchy level introduced in Junos OS
Release 18.2R1.
The [edit tenants tenant-name security log stream stream-name] hierarchy levels introduced in Junos OS
Release 18.3R1.
The routing-instance option introduc... | [] |
host (Security Web Filtering) | host host-name; | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated server]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name server]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name server] | Set server host parameters by entering the server name or IP address. | [] | 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. | [] |
host (service-set) | host hostname {
class {
alg-logs;
deterministic-nat-configuration-log;
ids-logs;
nat-logs;
packet-logs;
pcp-logurlf-logs;
session-logs <open | close>;
stateful-firewall-logs;
urlf-logs;
}
facility-override facility-name;
interface-s... | [edit services service-set service-set-name syslog] | Specify the hostname for the system logging utility.
Starting in Junos OS Release 17.4R1, you can configure up to a maximum of four system log servers
(combination of local system log hosts and remote system log collectors) for each service set at the [edit
services service-set service-set-name] hierarchy level.
NOTE:... | [
{
"name": "hostname",
"desc": "Name of the system logging utility host machine."
}
] | 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.
class option introduced in Junos OS Release 13.2.
You can configure multiple system log hosts from Junos OS Release 17.4R1 onwards. | [
"Configuring System Logging for Service Sets"
] |
host (System) | host (hostname | other-routing-engine) {
facility severity;
exclude-hostname
explicit-priority;
facility-override facility;
log-prefix string;
match "regular-expression";
match-strings string-name;
source-address source-address
structured-data {
brief;
}
transport (Sy... | [edit logical-systems logical-system-name system syslog],
[edit system syslog] | Configure the logging of system messages to a remote destination. | [
{
"name": "facility",
"desc": "Class of messages to log. To specify multiple classes, include multiple facility severity"
},
{
"name": "hostname",
"desc": "IPv4 address, IPv6 address, or fully qualified hostname of the remote machine to which to"
},
{
"name": "other-routing-engine",
... | 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. | [
"Directing System Log Messages to a Remote Machine or the Other Routing Engine",
"Directing Messages to a Remote Destination from the Routing Matrix Based on the TX Matrix Router",
"Directing Messages to a Remote Destination from the Routing Matrix Based on a TX Matrix Plus",
"Router"
] |
host-address-base (Source NAT Next Gen Services) | host-address-base ip-address; | [edit services nat source pool nat-pool-name] | Configure static mapping of the source address.
For static NAT that is performed on the services card, configure a one-to-one static shifting of a range of
original source addresses to the range of addresses in the source pool by specifying the base address of
the original source address range.
For example, if the hos... | [
{
"name": "host-address-base ip-address",
"desc": "The IP address used as the host address base."
}
] | 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. | [] |
host-address-base | host-address-base ip-address; | [edit security nat source pool pool-name] | Specify the base address of the original source IP address range. This is used for IP shifting. | [
{
"name": "ip-address",
"desc": "IP address."
}
] | 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. | [] |
host-fast-reroute | host-fast-reroute {
global-arp-prefix-limit number;
global-supplementary-blackout-timer minutes;
} | [edit logical-systems logical-system-name routing-options],
[edit routing-options] | Configure global settings for all host fast reroute (HFRR) profiles configured on a routing device.
The remaining statements are described separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring Link Protection with Host Fast Reroute"
] |
host-inbound-traffic | host-inbound-traffic {
protocols protocol-name {
except;
}
system-services service-name {
except;
}
} | [edit security zones functional-zone management],
[edit security zones functional-zone management interfaces interface-name],
[edit security zones security-zone zone-name],
[edit security zones security-zone zone-name interfaces interface-name] | Control the type of traffic that can reach the device from interfaces bound to the zone. | [] | 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. | [
"Understanding How to Control Inbound Traffic Based on Traffic Types",
"Understanding How to Control Inbound Traffic Based on Protocols"
] |
host-name (DHCP Relay Agent) | host-name name; | [edit forwarding-options dhcp-relay relay-option-82],
[edit forwarding-options dhcp-relay group group-name relay-option-82] | Supports the addition of vendor-specific hostname in the option 82, suboption 9 field of DHCPv4
control messages on server-facing interfaces. The hostname can be a string of characters such as
Juniper-AB-1.
Junos OS automatically adds the remaining vendor-specific information as per RFC 4243, Vendor-
Specific Informati... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 16.2. | [] |
host-name (DHCPv6 Relay Agent) | host-name name; | [edit forwarding-options dhcp-relay dhcpv6 relay-option-vendor-specific],
[edit forwarding-options dhcp-relaygroup group-name dhcpv6 relay-option-vendor-specific] | Supports the addition of vendor-specific hostname in the vendor-specific option (17) of DHCPv6 control
messages on server-facing interfaces. The hostname can be a string of characters such as Juniper-AB-1.
Junos automatically adds the remaining vendor-specific information as per RFC 4243, Vendor-Specific
Information Su... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 16.2. | [] |
host-name (System) | host-name hostname; | [edit system] | Set the hostname of the router or switch.
On Junos OS Evolved, when you specify the host-name statement, the Routing Engine name where the
configuration is committed is appended to the hostname you specify. For example, on Routing Engine 0,
set system host-name my-host sets the hostname to my-host-re0. You can also use... | [
{
"name": "hostname",
"desc": "Name of the router or switch."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Hostname of a Router or Switch by Using a Configuration Group"
] |
host-name | host-name host-name; | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security remote-id option-82] | Use the hostname of the switching device as the remote-id suboption of DHCP option 82 (also known as
the DHCP relay agent information option) in DHCP request packet headers before forwarding or
relaying requests to a DHCP server. This suboption provides a trusted identifier for the host system that
has forwarded or rel... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Setting Up DHCP Option 82 on the Switch with No Relay (ELS)",
"Configuring DHCP Option 82 on a Router with Bridge Domain",
"http://tools.ietf.org/html/rfc3046"
] |
host-only-interface | host-only-interface; | [edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id interface interface-
name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping interface interface... | Configure an interface as a host-facing interface. IGMP queries received on these interfaces are
dropped.
Default
The interface can either be a host-side or multicast-router 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. | [
"Example: Configuring IGMP Snooping"
] |
host-os forwarding-options analyzer | forwarding-options {
analyzer analyzer-instance-name {
input {
ingress {
virtual-network-function vnf-name {
interface interface-name;
}
}
egress {
virtual-network-function vnf-name {
... | [edit] | Configures an analyzer for port mirroring and configures port mirroring for either ingress or egress traffic
of a VNF interface to an analyzer VNF. | [
{
"name": "virtual-network-functions vnf-name",
"desc": "Name of the VNF instance."
},
{
"name": "analyzer-instance-name",
"desc": "Name of the analyzer."
},
{
"name": "ingress",
"desc": "Traffic that enters the port."
},
{
"name": "egress",
"desc": "Traffic that leaves t... | set host-os—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [] |
host-outbound media-interface | host-outbound media-interface; | [edit chassis] | Enable Layer 2 port mirroring of host-generated outbound packets only on MPCs on MX Series 5G
Universal Routing Platforms.
This statement enables all Routing Engine-generated Layer 2 injections to execute egress logical
interface filters. | [] | 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. | [
"Examples: Layer 2 Port Mirroring at Multiple Levels of the Chassis",
"Configuring Port Mirroring",
"Understanding Layer 2 Port Mirroring"
] |
host-outbound-traffic (Class-of-Service) | host-outbound-traffic {
forwarding-class class-name;
dscp-code-point code-point;
} | [edit class-of-service] | Allow queue selection for traffic generated by the Routing Engine (host). The selected queue must be
configured properly. You can also configure specific DSCP code point bits for the type of service (ToS)
field of the generated packets. This configuration does not affect transit packets or incoming packets.
This is a g... | [
{
"name": "forwarding-class class-name",
"desc": "Set the forwarding class name for outbound host traffic (traffic generated by"
},
{
"name": "dscp-code-point code-point",
"desc": "Set the six-bit DSCP code point value in the type of service (ToS) field 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.3. | [
"Changing the Host Outbound Traffic Default Queue Mapping",
"Understanding Host Routing Engine Outbound Traffic Queues and Defaults"
] |
host-outbound-traffic (Class-of-Service) | host-outbound-traffic {
dscp-code-point value;
forwarding-class class-name;
ieee-802.1 {
default value;
rewrite-rules;
override-firewall;
protocol {
isis-over-gre {
dscp-code-point dscp-code-point;
}
}
} | [edit class-of-service] | Classify and mark host outbound traffic. This statement does not affect transit traffic or incoming traffic.
Default
If you do not specify a forwarding class or DSCP value, the router uses the default queue and DSCP bit
assignments for host outbound traffic. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for ieee-802.1 statement introduced in Junos OS Release 12.3.
Support for distributed protocol handler traffic introduced in Junos OS Release 13.2.
Support for protocol statement introduced in Junos OS Release 17.3.
Support for override-firewall statement introduced... | [
"Default Routing Engine Protocol Queue Assignments",
"Default DSCP and DSCP IPv6 Classifiers",
"Changing the Default Queuing and Marking of Host Outbound Traffic",
"Configuring a Global Default IEEE 802.1p Value for All Host Outbound Traffic",
"Applying Egress Interface Rewrite Rules to the IEEE 802.1p Fiel... |
host-outbound-traffic (Multicast Snooping) | host-outbound-traffic {
forwarding-class class-name;
dot1p number;
} | [edit multicast-snooping-options],
[edit bridge-domains bridge-domain-name multicast-snooping-options],
[edit routing-instances routing-instance-name multicast-snooping-options],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name] | On an MX Series router in a network enabled for CET service and IGMP snooping, configure multicast
forwarding class and IEEE 802.1p value to rewrite of IGMP self generated packets. | [
{
"name": "class-name",
"desc": "Name of the forwarding class."
},
{
"name": "number",
"desc": "802.1p priority number."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring Multicast Snooping",
"Configuring IGMP Snooping"
] |
host-prefix-only | host-prefix-only; | [edit dynamic-profiles interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfac... | (MPC5 and MPC6 cards) Improve datapath performance by allowing only DHCPv4 subscribers that
negotiate a 32-bit prefix to come up on the underlying VLAN interface. All DHCP subscribers on the
underlying interface must negotiate a 32-bit prefix. Subscribers that negotiate a subnet prefix are not
brought up. You can confi... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface"
] |
host-vpn | host-vpn {
connections {
connection-name {
children {
child-name {
esp-proposal esp-proposal;
local-traffic-selector {
(ipv4-prefix ipv4-prefix | ipv6-prefix ipv6-prefix);
port port;
... | [edit security] | Configure a host-to-host VPN type of IPsec connection.
The remaining statements are explained separately. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1 Evolved. | [
"show security host-vpn version"
] |
hosted-service-identifier | hosted-service-identifier identifier; | [edit services hosted-services server-profile server-profile-name] | Configure the identifier for the service performed on the remote server | [
{
"name": "identifier",
"desc": "Identifer for the service performed on the remote server."
}
] | 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. | [
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] |
hosted-services | hosted-services {
server-profile server-profile-name {
client-address ipv4-address;
server-address ipv4-address;
}
} | [edit services] | Configure services performed on the remote server. | [] | 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. | [
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] |
hostkey-algorithm | hostkey-algorithm-list (ecdsa-sha2-nistp256 | ecdsa-sha2-nistp384 | ecdsa-sha2-nistp521 |
ed25519 | rsa) | [edit system services ssh] | Allow or disallow a host-key algorithm to authenticate another host through the SSH protocol. The host-
key uses RSA, ECDSA, ED25519, and DSS algorithms.
The following are the behaviors when the hostkey-algorithm option is configured with SSH client and SSH
server:
•
On the SSH client, the host-key algorithms that are ... | [
{
"name": "ecdsa-sha2-nistp256",
"desc": "Allow generation of ECDSA host-key with NIST P-256 curve."
},
{
"name": "ecdsa-sha2-nistp384",
"desc": "Allow generation of ECDSA host-key with NIST P-384 curve."
},
{
"name": "ecdsa-sha2-nistp521",
"desc": "Allow generation of ECDSA host-key... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
hostkey-algorithm-list option added in Junos OS Release 22.3R1.
hostkey-algorithm option removed in Junos OS Release 24.2R1. | [
"Generating SSL Certificates for Secure Web Access (SRX Series Devices)",
"Generating a Self-Signed SSL Certificate Automatically"
] |
hostkey-algorithm-list | hostkey-algorithm-list {
ecdsa-sha2-nistp256;
ecdsa-sha2-nistp384;
ecdsa-sha2-nistp521;
ed25519;
rsa;
rsa-sha2-256;
rsa-sha2-512;
} | [edit system services ssh] | Configure the specified SSH hostkey algorithms. The system automatically disables the remaining
unspecified hostkey algorithms.
NOTE: This configuration statement replaces the system services ssh hostkey-algorithm
statement starting in Junos OS Release 22.3R1.
Default
All hostkey algorithms are enabled by default. | [
{
"name": "ecdsa-sha2-nistp256",
"desc": "Allow generation of ECDSA host-key with NIST P-256 curve."
},
{
"name": "ecdsa-sha2-nistp384",
"desc": "Allow generation of ECDSA host-key with NIST P-384 curve."
},
{
"name": "ecdsa-sha2-nistp521",
"desc": "Allow generation of ECDSA host-key... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [
"Generating SSL Certificates for Secure Web Access (SRX Series Devices)",
"Generating a Self-Signed SSL Certificate Automatically"
] |
hot-root-standby (MBGP MVPN) | hot-root-standby {
min-rate <rate>;
source-tree;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
mvpn],
[edit routing-instances routing-instance-name protocols mvpn] | In a BGP multicast VPN (MVPN) with either RSVP-TE point-to-multipoint or MLDP point-to-multipoint
provider tunnels, configure hot-root standby, as defined in Multicast VPN fast upstream failover, draft-
morin-l3vpn-mvpn-fast-failover-05.
Starting in Junos OS Release 21.1R1, you can configure MLDP point-to-multipoint pr... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support for MLDP point-to-multipoint provider tunnel is introduced in Junos OS Release 21.1R1 for MX
Series router. | [
"Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with MLDP Point-to-Multipoint Provider",
"Tu... |
hot-standby (Protocols Layer 2 Circuit) | hot-standby; | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name end-interface interface interface-name backup-neighbor address],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name backup-neighbor address],
[edit logical-system... | Configure the pseudowire to the specified backup neighbor as the hot-standby. When you configure this
statement, traffic flows over both the active and hot-standby pseudowires to the backup device (either a
CE device or PE router). The backup device drops the traffic from the hot-standby pseudowire, unless
the active p... | [] | 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.
Hierarchy levels associated with the backup-neighbor statement added in Junos OS Release 9.2. | [
"Configuring Layer 2 Circuits over Both RSVP and LDP LSPs",
"Configuring Pseudowire Redundancy on the PE Router",
"Example: Configuring Layer 2 Circuit Switching Protection"
] |
hot-standby (Routing Instance) | hot-standby; | [edit routing-instances routing-instance-name protocols l2vpn site site-name] | Turn on the protector behavior for the site. This keeps backup pseudowire in continuous standby mode
and ready for traffic forwarding. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Example: Configuring MPLS Egress Protection Service Mirroring for BGP Signaled Layer 2 Services"
] |
hot-standby | hot-standby; | [edit interfaces rlsqnumber redundancy-options],
[edit interfaces rlsqnumber:number redundancy-options]
[edit interfaces rspnumber redundancy-options]
[edit interfaces rmsnumber redundancy-options] | For one-to-one AS, rsp, or rms redundancy configurations, specify that the failure detection and
recovery must take place in less than 5 seconds. For FRF.15 (MLFR) and FRF.16 (MFR) configuration,
specify the switch over time of 5 seconds and less for FRF.15 and a maximum of 10 seconds for FRF.16. | [] | 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. | [
"Configuring LSQ Interface Redundancy in a Single Router Using Virtual Interfaces",
"Configuring AS or Multiservices PIC Redundancy"
] |
hot-standby-vc-on (Protocols Layer 2 Circuit) | hot-standby-vc-on; | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name pseudowire-status-tlv],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-name neighbor address pseudowire-status-tlv],
[edit protocols l2circuit... | On provider edge (PE) aggregation routers, configure the hot-standby-vc-on statement to indicate that a
hot-standby pseudowire is desired upon arrival of a PW_FWD_STDBY status-tlv. This flag indicates the
standby state. Configure in conjunction with the hot-standby statement on routers that have both active
and standby... | [] | 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.
Support for VPLS routing instances added in Junos OS Release 15.1R2. | [
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
http (Access) | http {
banner {
fail string;
login string;
success string;
}
} | [edit access firewall-authentication pass-through] | Configure banners for the HTTP login prompt, successful authentication, and failed authentication. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"SRX Firewall Users",
"Obtaining Username and Role Information Through Firewall Authentication"
] |
http (icap-redirect profile) | http {
redirect-request;
redirect-response;
} | [edit services icap-redirect profile name],
[edit logical-systems logical-system-name services icap-redirect profile name] | Enable the redirect request and the redirect response for the HTTP traffic.
You can forward HTTP requests and HTTP responses to a Internet Content Adaptation Protocol (ICAP)
server before sending a request to a Web server or returning a response to the client system.
The SRX Series Firewall decrypts the HTTPS traffic a... | [
{
"name": "redirect-request",
"desc": "Enable the redirect service on HTTP request"
},
{
"name": "redirect-response",
"desc": "Enable the redirect service on HTTP response"
}
] | system | Statement introduced in Junos OS Release 18.1R1.
The logical system option is introduced in Junos OS Release 18.3R1. | [
"ICAP Service Redirect"
] |
http (REST API) | http {
addresses [ address-list ];
port port-number;
} | [edit system services rest] | Specify unencrypted HTTP connection settings, including addresses for incoming connections and the
port number.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
http (System Services) | http {
servers {
server name {
grpc [service1 service2 ... ];
listen-address address;
max-connections max-connections;
port port;
routing-instance routing-instance;
tls {
local-certificate certificate-id;
... | [edit system services] | Configure HTTP services.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1 and Junos OS Evolved Release 25.2R1. | [] |
http (Web API) | http {
port port;
} | [edit system services webapi] | Specify HTTP as the communication protocol for the Web API function of the SRX Series integrated
ClearPass authentication and enforcement feature.
The SRX Series Firewall exposes to the ClearPass Policy Manager (CPPM) the Web API for it to use to
initiate a connection and then use that connection to send to the SRX Ser... | [
{
"name": "port",
"desc": "Port for HTTP to use for the Web API function. Default: 8080 Range: 1 through 65535"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
http (Web Management) | http {
interface [ interface-names ];
port port;
} | [edit system services web-management] | Configure the port and interfaces for the HTTP service, which is unencrypted. | [
{
"name": "interface [ interface-names ]",
"desc": "Specify the name of one or more interfaces on which to accept access through the HTTP service. By default, HTTP access is allowed through built-in Fast Ethernet or Gigabit Ethernet interfaces only."
},
{
"name": "port port-number",
"desc": "Con... | 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.
Statement introduced in Junos OS Release 8.5 for SRX Series.
vSRX Virtual Firewall 3.0 on Hyper-V does not support the web management https configuration. | [
"Configuring Management Access for the EX Series Switch (J-Web Procedure)",
"Secure Management Access Configuration Summary",
"Firewall User Authentication Overview"
] |
http-log-multiple-transactions (LRF Profile) | http-log-multiple-transactions; | [edit services lrf profile profile-name] | Configure HTTP transaction logging to generate and send HTTP metadata for each transaction of a data
session. This option is only relevant if the template specified in an LRF rule includes http in the template-
type.
By default, HTTP transaction logging is disabled, and the HTTP transaction records for a TCP session ar... | [] | 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 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
http-persist | http-persist; | [edit security utm default-configuration web-filtering]
[edit security utm feature-profile web-filtering] | Checks all HTTP requests in a connection. By default, Web filtering first checks the HTTP request
method (for example, GET or PUT) in the same session. If there are multiple HTTP request methods in
the subsequent HTTP request of the same session, then Web filtering checks are not performed on
these methods. If http-per... | [] | view | Statement introduced in Junos OS Release 12.3X48-D25.
The [edit security utm default-configuration web-filtering] hierarchy level is introduced in Junos OS Release
18.2R1. | [
"Example: Configuring Enhanced Web Filtering"
] |
http-profile (Security Antivirus) | http-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name anti-virus] | Configure a Content Security policy for the antivirus HTTP protocol and attach this policy to a security
profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
http-profile (Security Content Filtering) | http-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name content-filtering] | Configure a Content Security policy for the content-filtering HTTP protocol and attach this policy to a
security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Content Filtering Overview"
] |
http-profile (Security Web Filtering) | http-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name web-filtering] | Configure a Content Security policy for the Web-filtering HTTP protocol and attach this policy to a
security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Web Filtering Overview"
] |
http-reassemble | http-reassemble; | [edit security utm default-configuration web-filtering]
[edit security utm feature-profile web-filtering] | Reassembles HTTP requests segments. When the http-reassemble option is enabled the requested
fragment is reassembled. By default, Web filtering checks only HTTP requests in the first HTTP request
packet. If HTTP request methods and URLs are fragmented in different packets, then these URLs are not
checked. If http-reass... | [] | view | Statement introduced in Junos OS Release 12.3X48-D25.
The [edit security utm default-configuration web-filtering] hierarchy level is introduced in Junos OS Release
18.2R1. | [
"Example: Configuring Enhanced Web Filtering"
] |
https (REST API) | https {
addresses [ address-list ];
cipher-list [cipher-1 cipher-2 cipher-3 ... ];
mutual-authentication {
certificate-authority certificate-authority-profile-name;
}
port port-number;
server-certificate local-certificate-identifier;
} | [edit system services rest] | Specify encrypted HTTPS connection settings, including addresses for incoming connections, the port
number, preferred cipher suites, and server certificate.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
https (Web API) | https {
certificate certificate;
certificate-key certificate-key;
default-certificate;
pki-local-certificate pki-local-certificate;
port port;
} | [edit system services webapi] | Specify HTTPS as the communication protocol for the Web API function of the SRX Series integrated
ClearPass authentication and enforcement feature. When you configure HTTPS, you specify the service
certificate and certificate key. You can also specify the port to be used.
The Web API process, acting as an HTTPS server,... | [
{
"name": "certificate",
"desc": "Configures the Web API process to use the specified, custom certificate file."
},
{
"name": "certificate-key",
"desc": "Configures the Web API process service certificate key. This parameter is required if a custom service certificate file is configured."
},
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
https (Web Management) | https {
interface [ interface-names ];
( local-certificate name | pki-local-certificate name | system-generated-certificate );
port port;
virtual-domain virtual-domain-name {
pki-local-certificate pki-local-certificate-name;;
}
} | [edit system services web-management] | Configure the secure version of the HTTP service, HTTPS, which is encrypted. | [
{
"name": "interface",
"desc": ""
},
{
"name": "[ interface-names ]",
"desc": "Specify the name of one or more interfaces on which to accept access through the HTTPS service. By default, HTTPS access is allowed through any ingress interface, but HTTP access is allowed through built-in Fast Ether... | 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.
pki-local-certificate introduced in Junos OS Release 9.1 for SRX Series.
system-generated-certificate introduced in Junos OS Release 11.1 for EX Series.
Statement introduced on the SRX5400, SRX5600, and SRX5800 devices starting from Junos OS Release
12.1X44-D10 and on ... | [
"Configuring Management Access for the EX Series Switch (J-Web Procedure)",
"Basic Elements of PKI in Junos OS",
"Enabling HTTPS and XNM-SSL Services on Switches Using Self-Signed Certificates (CLI Procedure)"
] |
hub-assist | hub-assist weight; | [edit interfaces interface-name unit logical-unit-number radio-router] | Configure the weight of the resource factor when calculating an effective interface bandwidth. | [
{
"name": "weight",
"desc": "Factor used to calculate interface bandwidth."
}
] | 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. | [
"Configuring PPPoE-Based Radio-to-Router Protocols"
] |
hugepages | hugepages; | [edit virtual-network-functions] | An option to support of 2 MB and 1 GB size memory pages. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
hw-db-profile | hw-db-profile
{
(lean-edge | cloud-metro);
} | [edit system packet-forwarding-options] | Use this configuration to configure various database profiles to allocate tables with different sizes in the
hardware. PFE restarts automatically once you change the configuration and commit. Profiles under this
configuration support the below databases:
•
Large Exact Match (LEM)—This table stores Mac table entries, LS... | [
{
"name": "lean-edge",
"desc": "Configures lean-edge profile for Border Network Gateways (BNGs)."
},
{
"name": "bng",
"desc": "Selects BNG DB profile and restarts PFE"
},
{
"name": "carrier-ethernet",
"desc": "Selects carrier Ethernet high scale MAC DB profile and restarts PFE. Alloc... | Statement introduced in Junos OS Evolved Release 23.4R1 for ACX7024, ACX7024X, ACX7100-32C,
ACX7100-48L, ACX7348, and ACX7509 routers. | [] | |
hw-profile | hw-profile | [edit system packet-forwarding-options] | Make a custom hardware profile as the active hardware profile. Setting this configuration will trigger a
PFE restart.
Default
default-hw-profile | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.3R1 for ACX7100-32C, ACX7100-48L,
ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X | [] |
hw-profiles | system {
packet-forwarding-options {
custom-profiles {
hw-profiles <hw-profile-name> {
counter-profile <counter-profile>
}
}
}
} | [edit system packet-forwarding-option custom-profiles hw-profiles hw-profile-name] | A custom hardware profile is a grouping of multiple custom profiles. You can create tailored custom
hardware profiles based on application needs. This approach allows dynamic allocation of resources
rather than allocating resources statically. For example, you can create a custom counter profile and then
group them und... | [
{
"name": "counter-profile <counter-profile>",
"desc": "Specify the name of the custom counter profile if you want to"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.3R1 | [] |
hybrid | hybrid {
synchronous-ethernet-mapping {
clock-source ip-address {
interface interface1-name;
interface interface2-name;
}
}
} | [edit protocols ptp slave] | Configure hybrid mode.
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 12.2R2. | [
"Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Example: Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Understanding Hybrid Mode",
"Precision Time Protocol Overview",
"Synchronous Ethernet Overview"
] |
hyper-mode (forwarding-options) | (hyper-mode | no-hyper-mode); | [edit forwarding-options] | Configure the hyper mode feature to increase the rate at which a data packet is processed. This
configuration results in the optimization of the lifetime of a data packet, which further enables the
network device (a router or a switch) to provide better performance and throughput. This feature is
supported on enhanced ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3R4. | [
"Configuring Hyper Mode on Enhanced MPCs to Speed Up Packet Processing",
"Understanding the Hyper Mode Feature on Enhanced MPCs for MX Series Routers and EX9200",
"Switches",
"I"
] |
icap-redirect | icap-redirect {
profile name {
fallback-option {
connectivity (block | log-permit | permit);
default-action (block | log-permit | permit);
timeout (block | log-permit | permit);
}
http {
redirect-request redirect-request;
redirect-r... | [edit services],
[edit logical-systems logical-system-name services],
[edit tenants tenants_name services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1 R1.
Support at the [edit logical-system logical-system-name services] hierarchy level introduced in Junos OS
Release 18.3R1.
Support at the [edit tenants tenants_name services] hierarchy level introduced in Junos OS Release 20.1R1. | [
"ICAP Service Redirect"
] |
iccp (Traceoptions) | iccp {
traceoptions; {
file <filename> <files number> <match regular-expression> <microsecond-stamp>
<size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
local-ip-address ip address;
session-establishment-hold-time value;
authentication-key string;... | [edit protocols iccp]
[edit logical-systems logical-system-name protocols iccp] | 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": "traceoptions",
"desc": "Set Interchassis Control Protocol (ICCP) tracing options."
},
{
"name": "local-ip-address",
"desc": "Specify the source address where the ICCP packet is routed."
},
{
"name": "session-establishment-hold-time",
"desc": "Specify if the chassis takes o... | 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.
Support for logical systems introduced in Junos OS Release 14.1. | [
"Configuring ICCP for MC-LAG"
] |
iccp | iccp {
authentication-key string;
local-ip-addr local-ip-addr;
peer ip-address{
authentication-key string;
backup-liveness-detection {
backup-peer-ip ip-address;
}
liveness-detection {
detection-time {
threshold milliseconds;
... | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
icl-down-delay | icl-down-delay seconds; | [edit interfaces name multi-chassis-protection IP address of MC-LAG peer]
[edit multi-chassis multi-chassis-protection IP address of MC-LAG peer] | The number of seconds that elapse between when the interchassis link (ICL) goes down and the
multichassis aggregated Ethernet interfaces (MCAEs) change to standby mode. Configuring the icl-
down-delay time results in better convergence during a MC-LAG peer reboot when the status control of
the peer is active. | [
{
"name": "icl-down-delay seconds",
"desc": "The number of seconds that elapse between when the interchassis link (ICL) goes"
}
] | interface | Statement introduced in Junos OS Release 19.4R3. | [] |
icmp (Error Message Rate Limit) | icmp {
rate-limit rate-limit;
} | [edit chassis] | Configure the rate at which ICMP messages are generated for IPv4 packet errors for non-ttl-expired
packets. Although you configure the rate limit at the [edit chassis] hierarchy level, it is not a chassis-wide
limit. Instead, the rate limit applies per interface family. This means, for example, that multiple physical
i... | [
{
"name": "rate-limit rate-limit",
"desc": "Rate in packets per second (pps). Starting in Junos OS Release 18.4R1, the"
}
] | 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. | [
"Rate Limit ICMPv4 and ICMPv6 Error Messages"
] |
icmp (IDS Screen Next Gen Services) | icmp {
fragment;
icmpv6-malformed;
large;
ping-death;
} | [edit services screen ids-option screen-name] | Configure ICMP intrusion detection service 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 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
icmp (Security IDP Custom Attack) | icmp; | [edit security idp custom-attack attack-name attack-type chain protocol-binding],
[edit security idp custom-attack attack-name attack-type signature protocol-binding] | Allow IDP to match the attack for the specified ICMP. | [] | 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. | [] |
icmp (Security IDP Signature Attack) | icmp {
code {
match (equal | greater-than | less-than | not-equal);
value code-value;
}
data-length {
match (equal | greater-than | less-than | not-equal);
value data-length;
}
identification (Security ICMP Headers) {
match (equal | greater-than | less-than | ... | [edit security idp custom-attack attack-name attack-type signature protocol] | Allow IDP to match the ICMP header information for the signature attack. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
icmp (Security Screen) | icmp {
flood {
threshold number;
}
fragment;
icmpv6-malformed;
ip-sweep {
threshold number;
}
large;
ping-death;
} | [edit security screen ids-option screen-name] | Configure ICMP intrusion detection service (IDS) options. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
icmp (System) | icmp {
ttl-expired-source-address ttl-expired-source-address;
} | [edit system] | Configure Internet Control Message Protocol (ICMP) features at the system level. | [
{
"name": "ttl-expired-source-address",
"desc": "Use an IPv4 address as the source address for ICMP time-to-live (TTL) expiry error messages."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1. | [
"Configure ICMP Features"
] |
icmp6 (Error Message Rate Limit) | icmp6 {
rate-limit rate-limit;
} | [edit chassis] | Configure the rate at which ICMP messages are generated for IPv6 packet errors for non-ttl-expired
packets. Although you configure the rate limit at the [edit chassis] hierarchy level, it is not a chassis-wide
limit. Instead, the rate limit applies per interface family. This means, for example, that multiple physical
i... | [
{
"name": "rate-limit rate-limit",
"desc": "Rate in packets per second (pps). Starting in Junos OS Release 18.4R1, the"
}
] | 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. | [
"Rate Limit ICMPv4 and ICMPv6 Error Messages"
] |
icmp | [edit services monitoring rpm probe-server] | (Required for Junos OS Evolved and for J Series routers running Junos OS) Enable ICMP requests for the
RPM probe server. ICMP requests are enabled by default on Junos OS (except for J Series routers); you
do not need to explicitly configure them.
The remaining statements are explained separately. Search for a statement... | [] | 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.
Statement introduced in Junos OS Evolved Release 20.1R1. | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.