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 |
|---|---|---|---|---|---|---|---|
clear services ssl proxy statistics | clear services ssl proxy statistics | Clear services SSL proxy statistics. An SSL proxy profile defines SSL behavior for the SRX Series Firewall. | [
{
"name": "logical-system",
"desc": "Clear the ssl proxy statistics."
}
] | clear
Output Fields
This command produces no output. | Command introduced in Junos OS Release 12.1.
The logical system option is introduced in Junos OS Release 19.1R1. | [] | |
clear services stateful-firewall flows | clear services stateful-firewall flows
<application-protocol protocol>
<destination-port destination-port>
<destination-prefix destination-prefix>
<interface interface-name>
<protocol protocol>
<service-set service-set>
<source-port source-port>
<source-prefix source-prefix> | Clear stateful firewall flows. Issue this command to clear the stateful firewall flows for the specified
option. The default option is "none", that is, to close all stateful firewall flows unless another option is
specified.
Starting in Junos Release 14.1, the method for closing flows has changed. With the change, even... | [
{
"name": "none",
"desc": "Clear all stateful firewall flows."
},
{
"name": "destination-port",
"desc": ""
},
{
"name": "destination-port",
"desc": "(Optional) Clear stateful firewall flows for a particular destination port. The range of values is 0 to 65535."
},
{
"name": "d... | view
Output Fields
Table 22 on page 4393 lists the output fields for the clear services stateful-firewall flows command.
Output fields are listed in the approximate order in which they appear.
Table 22: clear services stateful-firewall flows Output Fields
Field Name
Field Description
Interface
Name of an adaptive servi... | Command introduced before Junos OS Release 7.4. | [] | |
clear services stateful-firewall sip-call | clear services stateful-firewall sip-call
<application-protocol protocol>
<destination-port destination-port>
<destination-prefix destination-prefix>
<interface interface-name>
<protocol protocol>
<service-set service-set>
<source-port source-port>
<source-prefix source-prefix> | Clear Session Initiation Protocol (SIP) call information in stateful firewall flows. | [
{
"name": "none",
"desc": "Clear stateful firewall statistics for all interfaces and all service sets."
},
{
"name": "application-protocol",
"desc": "(Optional) Clear information about one of the following application protocols:"
},
{
"name": "bootp",
"desc": "(SIP only) Bootstrap pr... | view
Output Fields
Table 23 on page 4397 lists the output fields for the clear services stateful-firewall sip-call command.
Output fields are listed in the approximate order in which they appear.
Table 23: clear services stateful-firewall sip-call Output Fields
Field Name
Field Description
Interface
Name of an adaptive... | Command introduced in Junos OS Release 7.4. | [] | |
clear services stateful-firewall sip-register | clear services stateful-firewall sip-register
<application-protocol protocol>
<destination-port destination-port>
<destination-prefix destination-prefix>
<interface interface-name>
<protocol protocol>
<service-set service-set>
<source-port source-port>
<source-prefix source-prefix> | Clear Session Initiation Protocol (SIP) register information in stateful firewall flows. | [
{
"name": "application-protocol",
"desc": "(Optional) Clear information about one of the following application protocols:"
},
{
"name": "bootp",
"desc": "(SIP only) Bootstrap protocol"
},
{
"name": "dce-rpc",
"desc": "(SIP only) Distributed Computing Environment-Remote Procedure Call... | view
Output Fields
Table 24 on page 4401 lists the output fields for the clear services stateful-firewall sip-register
command. Output fields are listed in the approximate order in which they appear.
Table 24: clear services stateful-firewall sip-register Output Fields
Field Name
Field Description
Interface
Name of an ... | Command introduced in Junos OS Release 7.4. | [] | |
clear services stateful-firewall statistics | clear services stateful-firewall statistics
<interface interface-name>
<service-set service-set> | Clear stateful firewall statistics. | [
{
"name": "none",
"desc": "Clear stateful firewall statistics for all interfaces and all service sets."
},
{
"name": "interface interface-name",
"desc": "(Optional) Clear stateful firewall statistics for the specified interface. On M Series and T Series routers, the interface-name can be ms-fpc/... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear services stateful-firewall statistics
user@host> clear services stateful-firewall statistics | Command introduced before Junos OS Release 7.4. | [] | |
clear services subscriber analysis | clear services subscriber analysis | Clear information about the number of active subscribers on the services PIC. | [
{
"name": "interface interface-name",
"desc": "(Optional) Display information about a particular interface."
}
] | view | Statement introduced in Junos OS Release 17.1.
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. | [] | |
clear services unified-access-control authentication-table | clear services unified-access-control authentication-table | Clears the Unified Access Control (UAC) authentication table entries content. | [] | clear
Output Fields
If there are entries in the UAC authentication table, no messages are displayed after you enter the clear
command.
Sample Output
clear services unified-access-control authentication-table
user@host> clear services unified-access-control authentication-table | Command introduced in Junos OS Release 25.4R1. | [
"Unified Access Control (UAC)",
"Configure Unified Access Control (UAC)"
] | |
clear services user-identification active-directory-access | clear services user-identification active-directory-access (active-directory-authentication-
table |
statistics (ip-user-mapping | ip-user-probe | user-group-mapping)) | Delete entries from the Active Directory authentication table or statistics related to integrated user
firewall mappings. | [
{
"name": "active-directory-authentication-table",
"desc": "Remove all entries from the Active Directory authentication"
},
{
"name": "statistics",
"desc": "Remove the specified type of statistics:"
},
{
"name": "ip-user-mapping",
"desc": "IP address-to-user mappings"
},
{
"n... | clear
Output Fields
This command produces no output. | Command introduced in Junos OS Release 12.1X47-D10. | [] | |
clear services user-identification authentication-table | clear services user-identification authentication-table authentication-source authentication-
source (all | active-directory | aruba-clearpass | identity-management) | Clears the user identity and authentication entries content of the specified authentication source’s
authentication table. | [
{
"name": "authentication-source",
"desc": "Active Directoy, Aruba ClearPass, or the identity management server, which could be the Juniper Identity Management Service (JIMS) or any third-party authentication source. Additional Information"
}
] | clear
Output Fields
For Aruba ClearPass, if there are no entries in the ClearPass authentication table, the following warning
message is displayed after you enter the clear command.
There is no authentication-table entry.
If there are entries in the ClearPass authentication table, no messages are displayed after you en... | Command introduced in Junos OS Release 12.1X47-D10.
Support added for Aruba ClearPass as an authentication source in Junos OS release 12.3X48-D30.
Support added for identity-management as an authentication source in Junos OS Release 15.1X49-
D100.
clear services user-identification logical-domain-identity-management | [] | |
counters | clear services user-identification logical-domain-identity-management counters | Clears logical domain identity management information. | [
{
"name": "counters",
"desc": "Clears logical domain identity management query counters."
}
] | clear
Sample Output
clear services user-identification logical-domain-identity-management counters
user@host> clear services user-identification logical-domain-identity-management counters
node0:
--------------------------------------------------------------------------
warning: "There is no logical-domain-identity-man... | Command introduced in Junos OS Release 19.3R1. | [] | |
clear services video-monitoring mdi errors fpc-slot | clear services video-monitoring mdi errors <fpc-slot fpc-slot> | Clear all media delivery index error counters for the specified FPC slot or for all FPC slots. | [
{
"name": "none",
"desc": "Clear error counters for all FPC slots."
},
{
"name": "fpc-slot",
"desc": "(Optional) Clear error counters for the specified FPC slot."
}
] | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear services video-monitoring mdi errors
user@host> clear services video-monitoring mdi errors
Errors counters cleared | Command introduced in Junos OS Release 14.1. | [] | |
clear services video-monitoring mdi statistics fpc-slot | clear services video-monitoring mdi statistics fpc-slot fpc-slot | Clear all media delivery index statistics counters except for active flows. | [
{
"name": "fpc-slot",
"desc": "Number of the FPC slot."
}
] | clear | Command introduced in Junos OS Release 14.1. | [] | |
clear services web-filter statistics profile | clear services web-filter statistics profile profile-name
<dns-filter-template template-name>
<fpc-slot fpc-slot pic-slot pic-slot>
<url-filter-template template-name> | Clear statistics for DNS request filtering or URL filtering for the specified filter profile. | [
{
"name": "dns-filter-template template-name",
"desc": "(Optional) Name of the DNS filter template for which statistics are cleared."
},
{
"name": "fpc-slot fpc-slot pic-slot pic-slot",
"desc": "(Optional) Location of the services PIC for which statistics are cleared."
},
{
"name": "prof... | clear
Output Fields
When you enter this command, the statistics for DNS request filtering are cleared. There is no specific
output.
Sample Output
clear services web-filter statistics profile
user@host> clear services web-filter statistics profile profile1 | Command introduced in Junos OS Release 18.3R1. | [
"DNS Request Filtering for Disallowed Website Domains",
"Configuring URL Filtering"
] | |
clear services web-proxy transparent-proxy statistics | clear services web-proxy transparent-proxy statistics | Clears transparent web proxy statistics details. | [] | clear
Output Fields
This command produces no output. | Statement introduced in Junos OS Release 25.2R1. | [] | |
clear sflow collector statistics (QFX Series) | clear sflow collector statistics | Clear the sample counters for all sFlow collectors. | [] | view
Sample Output
clear sflow collector statistics
The following example shows two output examples for the show sflow collector command, one before and
one after the clear sflow collector statistics command was issued.
user@host> show sflow collector
Collector Udp-port No. of samples
address
10.1.1.1 ... | Command introduced in Junos OS Release 11.3. | [
"show sflow collector"
] | |
clear sflow collectors statistics | clear sflow collectors statistics | Clear the sFlow collector’s statistics. | [] | clear
Sample Output
clear sflow collectors statistics | Command introduced in JUNOS Release 9.5 . | [] | |
clear snmp history | clear snmp history (index | all) | Delete the history record of collected samples of SNMP Ethernet statistics. | [
{
"name": "all",
"desc": "Clear all the entries in the history index."
},
{
"name": "index",
"desc": "Clear the contents of the specified entry in the history index."
}
] | clear | Command introduced before Junos OS Release 7.4. | [] | |
clear snmp statistics | clear snmp statistics | Clear Simple Network Management Protocol (SNMP) statistics. | [] | clear
Output Fields
See "show snmp statistics" on page 27504 for an explanation of output fields.
Sample Output
clear snmp statistics
In the following example, SNMP statistics are displayed before and after the clear snmp statistics
command is issued:
user@host> show snmp statistics
SNMP statistics:
Inp... | Command introduced before Junos OS Release 7.4. | [] | |
clear spanning-tree protocol-migration | clear spanning-tree protocol-migration
<interface interface-name>
<routing-instance routing-instance-name> | Revert from the original IEEE 802.1D Spanning Tree Protocol (STP) back to the Rapid Spanning Tree
Protocol after the force-version statement has been removed from the configuration. | [
{
"name": "none",
"desc": "Reset the STP protocol for all interfaces and all routing instances."
},
{
"name": "interface interface-name",
"desc": "(Optional) Reset the STP protocol for the specified interface only."
},
{
"name": "routing-instance routing-instance-name",
"desc": "(Opt... | clear
Sample Output
clear spanning-tree protocol-migration
user@host> clear spanning-tree protocol-migration | Command introduced in Junos OS Release 9.0. | [] | |
clear spanning-tree statistics bridge | clear spanning-tree statistics bridge | Clear the statistics of the bridge. | [] | clear
Sample Output
clear spanning-tree statistics bridge (MX Series)
command-name
user@host> clear spanning-tree statistics bridge | Command introduced in Junos OS Release 14.1. | [] | |
clear spanning-tree statistics | clear spanning-tree statistics
<interface interface-name> | Clear Spanning Tree Protocol statistics for all interfaces or a specified interface. | [
{
"name": "none",
"desc": "Reset STP counters for all interfaces for all routing instances."
},
{
"name": "interface interface-name",
"desc": "(Optional) Clear STP statistics for the specified interface only."
},
{
"name": "logical-system logical-system-name",
"desc": "(Optional) Cle... | clear
Output Fields
This command produces no output.
Sample Output
clear spanning-tree statistics
user@switch> clear spanning—tree statistics | Command introduced in Junos OS Release 8.4. | [
"Understanding STP"
] | |
clear spanning-tree stp-buffer | clear spanning-tree stp-buffer | Clear the stp-buffer. | [] | clear
Sample Output
clear spanning-tree stp-buffer (MX Series)
command-name
user@host> clear spanning-tree stp-buffer | Command introduced in Junos OS Release 14.1. | [] | |
clear subscribers interfaces | clear subscribers interfaces
<statistics> | Clear subscribers interface sets | [
{
"name": "statistics",
"desc": "Clear the statistics counters associated with subscriber interface sets"
}
] | view | The statistics statement introduced in Junos OS Evolved Release 25.4R1 | [] | |
clear subscribers | clear subscribers
<firewall (counter counter | filter filter)> | Clear subscribers firewall counters | [
{
"name": "firewall",
"desc": "Clear subscribers firewall counters"
},
{
"name": "counter counter",
"desc": ""
},
{
"name": "(Optional) Counter name",
"desc": ""
},
{
"name": "filter filter",
"desc": ""
},
{
"name": "(Optional) Filter name",
"desc": ""
}
] | view | Statement introduced in Junos OS Evolved Release 25.4R1 | [] | |
clear synchronous-ethernet esmc statistics | clear synchronous-ethernet esmc statistics <interface-name> | Clear the ESMC statistics for all the interfaces. | [
{
"name": "interface-name",
"desc": "(Optional) Clear ESMC statistics for the specified interface."
}
] | clear
Sample Output
clear synchronous-ethernet esmc statistics
The following example displays the message after the clear synchronous-ethernet esmc statistics command
is entered:
user@host> clear synchronous-ethernet esmc statistics
Cleared ESMC statistics for all interfaces | Command introduced before Junos OS Release 10.4. | [
"Example: Configuring Synchronous Ethernet on MX Series Routers",
"Synchronous Ethernet Overview"
] | |
clear synchronous-ethernet wait-to-restore | clear synchronous-ethernet wait-to-restore
<interface interface-name> | Clear the wait-to-restore timer for all the interfaces in an MX Series router.
NOTE: When you perform GRES on MX Series routers, you must execute the clear
synchronous-ethernet wait-to-restore operational mode command on the new primary
Routing Engine to clear the wait-to-restore timer on it. This is because the clear
... | [
{
"name": "interface interface-name",
"desc": "(Optional) Clear wait to restore timer for the specified interface."
}
] | clear
Sample Output
clear synchronous-ethernet wait-to-restore interface <interface-name>
The following example displays the message after the clear synchronous-ethernet wait-to-restore interface
ge-2/1/6 command is entered in operational mode command:
user@host> clear synchronous-ethernet wait-to-restore interface ge... | Command introduced in Junos OS Release 14.2. | [
"Example: Configuring Synchronous Ethernet on MX Series Routers",
"Synchronous Ethernet Overview"
] | |
clear system commit prepared | clear system commit prepared | Clear the prepared commit. This initiates cleanup of the saved database data structures and the
necessary files that are generated as a result of the commit preparation stage and unlinks the pending
activation file. A log message is generated upon successful clearing of the pending commit. | [] | Maintenance (or the actual user who scheduled the commit)
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear system commit prepared
user@host> clear system commit prepared
Prepared commit cleared.
clear system commit prepared (None Prepar... | Command introduced in Junos OS Release 17.3. | [] | |
clear system commit | clear system commit
<synchronize-server pending-jobs> | Clear pending commit operations. | [
{
"name": "none",
"desc": "Clear pending commit operations on the static configuration database."
},
{
"name": "synchronize-server",
"desc": ""
},
{
"name": "pending-jobs",
"desc": "(Optional) Clear pending commit synchronize operations for all instances of the ephemeral configuratio... | maintenance (or the actual user who scheduled the commit)
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear system commit
user@host> clear system commit
Pending commit cleared.
clear system commit (None Pending)
user@host> clear system c... | Command introduced before Junos OS Release 7.4.
Option synchronize-server introduced in Junos OS Release 17.2R1 and Junos OS Evolved Release 22.1R1. | [] | |
clear system errors | clear system errors fpc fpc-slot fpc-slot
<all>
<error-id error-id-uri> | Clear system errors associated with J-Insight fault monitoring. | [
{
"name": "all",
"desc": "(Optional) Clear all systems errors."
},
{
"name": "error-id error-id-uri",
"desc": "(Optional) Clear system errors for a specified error ID URI."
},
{
"name": "fpc-slot fpc-slot",
"desc": "Clear system errors for a specified FPC."
}
] | clear
Output Fields
This command produces no output. | Command introduced in Junos OS Release 18.2R1. | [
"J-Insight Device Monitor Basic Configuration"
] | |
clear system login lockout | clear system login lockout
<all>
<user username> | Use this command to unlock the locked user account. | [
{
"name": "all",
"desc": "Clear all locked user accounts."
},
{
"name": "user username",
"desc": "Clear the specified locked user account."
}
] | clear
Output Fields
This command produces no output. | Command introduced in Junos OS Release 11.2. | [
"retry-options"
] | |
clear system reboot | clear system reboot
<infrastructure name>
<interconnect-device name>
<node-group name> | Clear any pending system software reboots or halts. When issued on a TX Matrix router without any
options, the default behavior clears all pending system software reboots or halts on all T640 routers
connected to the TX Matrix router. When issued on a TX Matrix Plus router without any options, the
default behavior clea... | [
{
"name": "none",
"desc": "Clear all pending system software reboots or halts."
},
{
"name": "all-chassis",
"desc": "(TX Matrix routers and TX Matrix Plus routers only) (Optional) Clear all halt or reboot requests for all the Routing Engines in the chassis."
},
{
"name": "all-lcc",
"... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear system reboot
user@host> clear system reboot
reboot requested by root at Sat Dec 12 19:37:34 1998
[process id 17855]
Terminating...
clear system reboot (TX Matrix Router)
user... | Command introduced before Junos OS Release 7.4.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6. | [
"Routing Matrix with a TX Matrix Plus Router Solutions Page"
] | |
clear system services dhcp binding | clear system services dhcp binding
<address> | (EX Series switches only) Remove obsolete IP address bindings on a Dynamic Host Configuration
Protocol (DHCP) server and return them to the IP address pool. | [
{
"name": "address",
"desc": "(Optional) Remove a specific IP address binding and return it to the address pool."
}
] | view and system
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear system services dhcp binding
user@host> clear system services dhcp binding | Command introduced before Junos OS Release 7.4. | [] | |
clear system services dhcp conflict | clear system services dhcp conflict
<address> | (J Series routers and EX Series switches only) Remove IP addresses from the Dynamic Host
Configuration Protocol (DHCP) server conflict list and return them to the IP address pool. | [
{
"name": "address",
"desc": "(Optional) Remove a specific IP address from the conflict list and return it to the address pool."
}
] | view and system
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear system services dhcp conflict
user@host> clear system services dhcp conflict | Command introduced before Junos OS Release 7.4. | [] | |
clear system services dhcp statistics | clear system services dhcp statistics | (J Series routers and EX Series switches only) Clear Dynamic Host Configuration Protocol (DHCP) server
statistics. | [] | view and system
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear system services dhcp statistics
user@host> clear system services dhcp statistics | Command introduced before Junos OS Release 7.4. | [] | |
clear system services dns dns-proxy | clear system services dns dns-proxy | Clear DNS proxy cache information. This option is supported on the SRX300, SRX320, SRX340,
SRX345, SRX380, and SRX550M devices. | [
{
"name": "cache",
"desc": "Clear DNS proxy cache information."
},
{
"name": "statistics",
"desc": "Clear DNS proxy statistics."
},
{
"name": "none",
"desc": "Clear all DNS proxy cache information."
},
{
"name": "hostname",
"desc": "(Optional) Clear DNS proxy cache inform... | clear
Output Fields
When you enter this command no output is produced. | Command introduced in Junos OS Release 12.1X44-D10. | [] | |
clear system subscriber-management statistics | clear system subscriber-management statistics | Clear subscriber-management statistics. | [] | view and system
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear subscriber-management statistics
user@host> clear subscriber-management statistics | Command introduced in Junos OS Release 15.1. | [
"clear system subscriber-management arp",
"clear system subscriber-management ipv6 neighbors"
] | |
clear tcp-forwarding connections | clear tcp-forwarding connections
listening-port listening-port-number listening-address ipv4-listening-address
source-address source-ipv4-address source-port source-port-number
routing-instance routing-instance-name | Clear all TCP connections, all connections associated with a specific listening port/listening address
combination, or a single connection pair represented by a specific source address/source port
combination. For either combination, you can optionally specify a routing instance. If you do not specify
a routing instanc... | [
{
"name": "listening-address",
"desc": ""
},
{
"name": "ipv4-listening-address",
"desc": "IPv4 address that is part of a listening port/listening address combination. The listening address is one on the BNG that external management systems or remote devices must use when attempting to trigger co... | view
Output Fields
When you enter this command, you are not provided feedback on the status of your request.
Sample Output
clear tcp-forwarding connections
user@host> clear tcp-forwarding connections
clear tcp-forwarding connections (Listening Port and Address)
The following sample output displays the TCP connection st... | Command introduced in Junos OS Release 18.3R1. | [
"TCP Port Forwarding for Remote Device Management"
] | |
clear tcp-forwarding statistics | clear tcp-forwarding statistics
listening-port listening-port-number listening-address ipv4-listening-address
source-address source-ipv4-address source-port source-port-number
routing-instance routing-instance-name | Clear the statistics displayed by the show tcp-forwarding status command. You can clear statistic for all TCP
mappings, for all connections associated with a specific listening port/listening address combination, or
for only a single connection pair represented by a specific source address/source port combination. For
... | [
{
"name": "listening-address",
"desc": ""
},
{
"name": "ipv4-listening-address",
"desc": "IPv4 address that is part of a listening port/listening address combination. The listening address is one on the BNG that external management systems or remote devices must use when attempting to trigger co... | view
Output Fields
When you enter this command, you are not provided feedback on the status of your request.
Sample Output
clear tcp-forwarding statistics (Listening Port and Address)
The following sample output displays the TCP connection status for a specific listening port/address
combination before and after the c... | Command introduced in Junos OS Release 18.3R1. | [
"TCP Port Forwarding for Remote Device Management"
] | |
clear trace | clear trace
<all-traces | application application-name | node node-name> | 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": "all-traces",
"desc": "(Optional) Remove all traces."
},
{
"name": "application application-name",
"desc": "(Optional) Remove all traces for the specified application."
},
{
"name": "node node-name",
"desc": "(Optional) Remove all traces for the specified node."
}
] | view
Sample Output
clear trace
user@host> clear trace | Command introduced in Junos OS Evolved Release 18.3R1.
Options all-traces, application, and node introduced in Junos OS Evolved Release 19.1R1. | [] | |
clear unified-edge tdf aaa radius client statistics | clear unified-edge tdf aaa radius client statistics
<all>
<client name>
<fpc-slot fpc-slot>
<gateway gateway>
<pic-slot pic-slot> | Clear statistics for the accounting requests and responses transmitted and received by the RADIUS
client for one or more TDF gateways. If a TDF gateway is not specified, then information for all TDF
gateways is cleared. | [
{
"name": "none",
"desc": "(Same as all) Clear statistics for all clients on all TDF gateways."
},
{
"name": "all",
"desc": "(Optional) Clear statistics for all the clients."
},
{
"name": "client name",
"desc": "(Optional) Clear statistics for the specified client."
},
{
"nam... | clear, unified-edge
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear unified-edge tdf aaa radius client statistics all
user@host> clear unified-edge tdf aaa radius client statistics all
Cleared all RADIUS statistics | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf aaa radius network-element statistics | clear unified-edge tdf aaa radius network-element statistics
<fpc-slot fpc-slot>
<gateway gateway>
<pic-slot pic-slot>
<name name> | Clear all the statistics for the specified network element. | [
{
"name": "none",
"desc": "Clear statistics for all network elements for all TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear statistics for the specified Flexible PIC Concentrator (FPC)."
},
{
"name": "gateway gateway",
"desc": "(Optional) Clear statistics ... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise, an error message is
displayed.
Sample Output
clear unified-edge tdf aaa radius network-element statistics
user@host> clear unified-edge tdf aaa radius network-element statistics | Statement introduced in Junos OS Release 17.1. | [
"Understanding Network Elements"
] | |
clear unified-edge tdf aaa radius server statistics | clear unified-edge tdf aaa radius server statistics
<fpc-slot fpc-slot>
<gateway gateway>
<pic-slot pic-slot>
<name name> | Clear all the statistics for the specified RADIUS server. | [
{
"name": "none",
"desc": "Clear statistics for all RADIUS servers for all TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear statistics for the specified Flexible PIC Concentrator (FPC)."
},
{
"name": "gateway gateway",
"desc": "(Optional) Clear statistics fo... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise, an error message is
displayed.
Sample Output
clear unified-edge tdf aaa radius server statistics
user@host> clear unified-edge tdf aaa radius server statistics | Statement introduced in Junos OS Release 17.1. | [
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] | |
clear unified-edge tdf aaa radius snoop-segment statistics | clear unified-edge tdf aaa radius snoop-segment statistics
<fpc-slot fpc-slot>
<gateway gateway>
<pic-slot pic-slot>
<segment snoop-segment-name> | Clear all snoop segment statistics for FPCs, PICs, TDF gateways, or snoop segments that you specify. | [
{
"name": "none",
"desc": "Clear all snoop-segment statistics for all TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear statistics for the specified Flexible PIC Concentrator (FPC)."
},
{
"name": "gateway gateway",
"desc": "(Optional) Clear statistics for the... | clear, unified-edge
Output Fields
A message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf aaa radius snoop-segment statistics
user@host> clear unified-edge tdf aaa radius snoop-segment statistics
Cleared Radius snoop-segment Statisti... | Statement introduced in Junos OS Release 17.1. | [
"Snooping RADIUS Accounting Requests for IP-Based Subscribers Overview"
] | |
clear unified-edge tdf aaa statistics | clear unified-edge tdf aaa statistics
<all>
<fpc-slot fpc-slot>
<gateway gateway>
<pic-slot pic-slot> | Clear global authentication, authorization, and accounting (AAA) statistics for one or more TDF
gateways. If a TDF gateway is not specified, then information for all TDF gateways is cleared. | [
{
"name": "none",
"desc": "(Same as all) Clear AAA statistics for all TDF gateways."
},
{
"name": "all",
"desc": "(Optional) Clear AAA statistics for all the TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear AAA statistics for the specified Flexible PIC Conce... | clear, unified-edge
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear unified-edge tdf aaa statistics all
user@host> clear unified-edge tdf aaa statistics all
Cleared all AAA statistics | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf address-assignment pool | clear unified-edge tdf address-assignment pool name pool-name
<gateway gateway>
<routing-instance routing-instance> | Clear the sessions that have been assigned addresses from the specified mobile pool for one or more
TDF gateways. If a TDF gateway is not specified, then the sessions for all TDF gateways are cleared. | [
{
"name": "none",
"desc": "Clear the sessions for all TDF gateways associated with the specified mobile pool."
},
{
"name": "name pool-name",
"desc": "Clear the sessions for the specified mobile pool."
},
{
"name": "gateway gateway",
"desc": "(Optional) Clear the sessions on the spec... | clear, unified-edge
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear unified-edge tdf address-assignment pool name
user@host> clear unified-edge tdf address-assignment pool name pool-1
Initiated clearing of sessions in the pool | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf address-assignment statistics | clear unified-edge tdf address-assignment statistics
<fpc-slot fpc-slot>
<gateway gateway>
<pic-slot pic-slot> | Clear the global address assignment statistics for one or more TDF gateways. If a TDF gateway is not
specified, then the statistics for all TDF gateways are cleared. | [
{
"name": "none",
"desc": "Clear statistics for all TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear the statistics for the session PIC in the specified FPC slot."
},
{
"name": "gateway gateway",
"desc": "(Optional) Clear the statistics for the specified TDF... | clear, unified-edge
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear unified-edge tdf address-assignment statistics
user@host> clear unified-edge tdf address-assignment statistics
Cleared address-assignment statistics | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf call-admission-control statistics | clear unified-edge tdf call-admission-control statistics gateway gateway-name
<fpc-slot fpc-slot>
<pic-slot pic-slot> | Clear call admission control (CAC) statistics for the specified TDF gateway. | [
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear statistics for the session PIC in the specified FPC slot."
},
{
"name": "gateway gateway-name",
"desc": "Clear CAC statistics for the specified TDF gateway."
},
{
"name": "pic-slot pic-slot",
"desc": "(Optional) Clear statistic... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf call-admission-control statistics gateway
user@host> clear unified-edge tdf call-admission-control statistics gateway TDF | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf diameter network-element statistics | clear unified-edge tdf diameter network-element statistics
<fpc-slot fpc-slot>
<gateway gateway-name>
<network-element-name network-element-name>
<pic-slot pic-slot> | Clear the statistics for network elements for one or more TDF gateways. If a network element is not
specified, then statistics for all network elements are cleared. If a TDF gateway is not specified, then
statistics for all TDF gateways are cleared. | [
{
"name": "none",
"desc": "Clear statistics for all network elements and TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear statistics for the specified Flexible PIC Concentrator (FPC)."
},
{
"name": "gateway gateway-name",
"desc": "(Optional) Clear statistics... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf diameter network-element statistics
user@host> clear unified-edge tdf diameter network-element statistics | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf diameter pcc-gx statistics | clear unified-edge tdf diameter pcc-gx statistics
<fpc-slot fpc-slot>
<gateway gateway-name>
<pic-slot pic-slot> | Clear all statistics for the Gx application for one or more TDF gateways. If a TDF gateway is not
specified, then statistics for all TDF gateways are cleared. | [
{
"name": "none",
"desc": "Clear Gx application statistics for all TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear statistics for the specified Flexible PIC Concentrator (FPC)."
},
{
"name": "gateway gateway-name",
"desc": "(Optional) Clear statistics for t... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf diameter pcc-gx statistics
user@host> clear unified-edge tdf diameter pcc-gx statistics | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf diameter peer statistics | clear unified-edge tdf diameter peer statistics
<fpc-slot fpc-slot>
<gateway gateway-name>
<peer-name peer-name>
<pic-slot pic-slot> | Clear statistics for Diameter peers for one or more TDF gateways. If a peer is not specified, then
statistics for all peers are cleared. If a TDF gateway is not specified, then statistics for all TDF gateways
are cleared. | [
{
"name": "none",
"desc": "Clear Diameter peer statistics for all TDF gateways."
},
{
"name": "fpc-slot fpc-slot",
"desc": "(Optional) Clear statistics for the specified Flexible PIC Concentrator (FPC)."
},
{
"name": "gateway gateway-name",
"desc": "(Optional) Clear statistics for th... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf diameter peer statistics
user@host> clear unified-edge tdf diameter peer statistics | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf statistics | clear unified-edge tdf statistics
<data-plane>
<gateway gateway-name>
<domain domain-name | Clear all the statistics for the specified TDF gateway, domain, or control plane. | [
{
"name": "none",
"desc": "Clear statistics for all TDF control planes, domains, and gateways."
},
{
"name": "data-plane",
"desc": "(Optional) Clear statistics for the data plane."
},
{
"name": "domain domain-name",
"desc": "(Optional) Clear statistics for the specified TDF domain."
... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf statistics gateway
user@host> clear unified-edge tdf statistics gateway TDF | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf subscribers peer | clear unified-edge tdf subscribers peer
<gateway gateway>
<remote-addr remote-addr>
<nas-id nas-id
<routing-instance routing-instance> | Clear the information for IP-based subscribers anchored on the specified RADIUS client, TDF gateway,
or both, or for IP-based subscribers matching the specified routing instance. | [
{
"name": "none",
"desc": "Clear information for all IP-based subscribers."
},
{
"name": "gateway gateway",
"desc": "(Optional) Clear IP-based subscriber information for the TDF gateway."
},
{
"name": "nas-id nas-id",
"desc": "(Optional) Clear IP-based subscriber information for the ... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf subscribers peer gateway remote-addr
user@host> clear unified-edge tdf subscribers peer gateway TDF remote-addr 198.0.2.2 | Statement introduced in Junos OS Release 17.1. | [] | |
clear unified-edge tdf subscribers | clear unified-edge tdf subscribers [option] | Clear the subscribers identified by the option values. You must include at least one option. For IFL-based
subscribers, use the revert option to re-create the cleared subscribers identified by the option values. | [
{
"name": "option",
"desc": "One or more of the following options:"
},
{
"name": "domain domain-name",
"desc": "Clear the subscribers for the specified TDF domain."
},
{
"name": "gateway gateway-name",
"desc": "Clear the subscribers for the specified TDF gateway."
},
{
"name"... | clear, unified-edge
Output Fields
No message is displayed on successful execution of this command; otherwise an error message is
displayed.
Sample Output
clear unified-edge tdf subscribers gateway tdf
user@host> clear unified-edge tdf subscribers gateway tdf | Statement introduced in Junos OS Release 17.1. | [
"IP-Based and IFL-Based TDF Subscribers Overview",
"Understanding IFL-Based Subscriber Setup"
] | |
clear validation database | clear validation database
<name database-name>
<instance instance-name>
<logical-system logical-system-name> | Clear the route validation database. | [
{
"name": "none",
"desc": "Clear the route validation database for all routing instances."
},
{
"name": "name database-name",
"desc": "(Optional) Display the records of the specified database in that routing-instance or logical-system. If unspecified, the records of all databases are displayed."... | clear
Sample Output
clear validation database
user@host> clear validation database
Clearing database | Command introduced in Junos OS Release 12.2. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] | |
clear validation session | clear validation session
<destination session-ip-address>
<instance instance-name>
<logical-system logical-system-name>
<soft-inbound> | Clear the route validation session to the cache server. | [
{
"name": "none",
"desc": "Clear all route validation sessions for all routing instances."
},
{
"name": "destination session-ip-address",
"desc": "(Optional) Clear the specified route validation session."
},
{
"name": "instance instance-name",
"desc": "(Optional) Clear the route vali... | clear
Sample Output
clear validation session
user@host> clear validation session
Cleared 3 sessions | Command introduced in Junos OS Release 12.2. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] | |
clear validation statistics | clear validation statistics
<instance instance-name>
<logical-system logical-system-name> | Clear the route validation statistics. | [
{
"name": "none",
"desc": "Clear the route validation statistics for all routing instances."
},
{
"name": "instance instance-name",
"desc": "(Optional) Clear the route validation statistics for the specified instance."
},
{
"name": "logical-system logical-system-name",
"desc": "(Opti... | clear
Sample Output
clear validation statistics
user@host> clear validation statistics
Statistics cleared | Command introduced in Junos OS Release 12.2. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] | |
clear virtual-chassis heartbeat (MX Series Virtual Chassis) | clear virtual-chassis heartbeat
<(all-members | local | member member-id)> | Clear statistics counter and timestamp fields associated with a heartbeat packet connection on both
member routers in an MX Series Virtual Chassis. You can issue the clear virtual-chassis heartbeat
command from the console of either member router in the Virtual Chassis.
NOTE: When you clear heartbeat statistics, the co... | [
{
"name": "none",
"desc": "Clear heartbeat statistics for both member routers in an MX Series Virtual Chassis."
},
{
"name": "all-members",
"desc": "(Optional) Clear heartbeat statistics for both member routers in an MX Series Virtual Chassis. This is the default behavior if no options are speci... | clear
Output Fields
Table 25 on page 4493 lists the output fields for the clear virtual-chassis heartbeat command. Output
fields are listed in the approximate order in which they appear.
Table 25: clear virtual-chassis heartbeat Output Fields
Field Name
Field Description
membern
Member ID of the Virtual Chassis member... | Command introduced in Junos OS Release 14.1. | [
"Verifying and Managing the Virtual Chassis Heartbeat Connection",
"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 Membe... | |
clear virtual-chassis protocol statistics | clear virtual-chassis protocol statistics
<all-members>
<local>
<member member-id> | Clear—reset to zero (0)—all Virtual Chassis Control Protocol (VCCP) traffic counters for the Virtual
Chassis. | [
{
"name": "none",
"desc": "Clear VCCP counters for all members of the Virtual Chassis."
},
{
"name": "all-members",
"desc": "(Optional) Clear VCCP traffic counters for all members of the Virtual Chassis."
},
{
"name": "local",
"desc": "(Optional) Clear VCCP traffic counters on the sw... | clear
Sample Output
clear virtual-chassis protocol statistics
user@switch> clear virtual-chassis protocol statistics
member0:
--------------------------------------------------------------------------
Statistics cleared
member1:
--------------------------------------------------------------------------
Statistics clear... | Command introduced in Junos OS Release 10.4. | [
"Understanding the Virtual Chassis Control Protocol in an EX8200 Virtual Chassis"
] | |
clear virtual-chassis vc-port statistics | clear virtual-chassis vc-port statistics
<all-members>
<interface-name>
<local>
<member member-id> | Clear—reset to zero (0)—the traffic statistics counters on Virtual Chassis ports (VCPs). | [
{
"name": "none",
"desc": "Clear traffic statistics for VCPs of all members of a Virtual Chassis or VCF."
},
{
"name": "all-members",
"desc": "(Optional) Clear traffic statistics for VCPs of all members of a Virtual Chassis or VCF."
},
{
"name": "interface-name",
"desc": "(Optional) ... | clear
Sample Output
clear virtual-chassis vc-port statistics (EX4200 Virtual Chassis)
user@switch> clear virtual-chassis vc-port statistics
fpc0:
--------------------------------------------------------------------------
Statistics cleared
clear virtual-chassis vc-port statistics (EX8200 Virtual Chassis)
user@external-... | Command introduced in Junos OS Release 9.0.
The options all-members and local were added in Junos OS Release 9.3 for EX Series switches. | [
"Monitoring the Virtual Chassis Status and Statistics on EX Series Virtual Chassis"
] | |
clear vpls mac-address | clear vpls mac-address
<instance instance-name>
<logical-system (all | logical-system-name)>
<mac-address> | (T Series and M Series routers, except for the M160 router) Clear media access control (MAC) address
entries from the virtual private LAN service (VPLS) table. | [
{
"name": "none",
"desc": "Clear all MAC address entries from the VPLS table for all routing instances."
},
{
"name": "instance instance-name",
"desc": "(Optional) Clear all MAC address entries for a VPLS instance from the VPLS table."
},
{
"name": "logical-system (all | logical-system-n... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear vpls mac-address
user@host> clear vpls mac-address | Command introduced before Junos OS Release 7.4. | [] | |
clear vpls mac-move-action | clear vpls mac-move-action
<interface ifl-name.unit> | Clear the learning interfaces (IFLs) disabled due to a MAC move. | [
{
"name": "none",
"desc": "Clear all the IFLs disabled due to a MAC move."
},
{
"name": "interface ifl-name.unit",
"desc": "(Optional) Clear the VPLS interface disabled due to a MAC move."
}
] | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear vpls mac-move-action (MX Series)
user@host> clear vpls mac-move-action
clear vpls mac-move-action interface ifl-name.unit (MX Series)
user@host> clear vpls mac-move-action interface xe-1/0/0.1 | Command introduced in Junos OS Release 14.2. | [] | |
clear vpls mac-table | clear vpls mac-table
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
<mac-address>
<vlan-id> | (MX Series routers) Clear media access control (MAC) addresses from the virtual private LAN service
(VPLS) MAC table. | [
{
"name": "none",
"desc": "Clear all MAC addresses from the VPLS table for all routing instances."
},
{
"name": "instance instance-name",
"desc": "(Optional) Clear all MAC addresses for a VPLS instance from the VPLS table."
},
{
"name": "interface interface-name",
"desc": "(Optional)... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear vpls mac-table
user@host> clear vpls mac-table | Command introduced before Junos OS Release 9.5. | [] | |
clear vrrp | clear vrrp (all | interface interface-name) | Set Virtual Router Redundancy Protocol (VRRP) interface statistics to zero. | [
{
"name": "all",
"desc": "Clear statistics on all interfaces."
},
{
"name": "interface interface-name",
"desc": "Clear statistics on the specified interface only."
}
] | clear
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear vrrp all
user@host> clear vrrp all | Command introduced before Junos OS Release 7.4. | [] | |
clear | request protection-group ethernet-aps clear md <md> ma <ma> | [edit protocols protection-group ethernet-aps] | Clears the lockout, force switch, manual switch, exercise, and wait-to-restore (WTR) states. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Ethernet Automatic Protection Switching Overview"
] | |
clear-action (CFM) | clear-action {
interface-down peer-interface;
} | [edit protocols oam ethernet connectivity-fault-management action-profile profile-name] | Clear the action or actions to be taken when the connectivity fault management event occurs. You
cannot configure multiple actions at this time. Only one action can be configured. This limitation affects
both the action and clear-action statements. | [
{
"name": "peer-interface",
"desc": "Name of the peer interface."
}
] | 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. | [
"Configuring a CFM Action Profile to Specify CFM Actions for CFM Events"
] |
clear-dont-fragment-bit (fti) | clear-dont-fragment-bit; | [edit interfaces fti number unit logical-unit-number family inet address] | Clear the Don’t Fragment (DF) bit on all IP version 4 (IPv4) packets entering the (UDP/GRE/IP-in-IP)
tunnel on FTI interfaces. If the encapsulated packet size exceeds the tunnel maximum transmission unit
(MTU), the packet is fragmented before encapsulation.
When the option is not configured and the DF bit is set, the p... | [] | interface | Statement introduced in Junos OS Evolved Release 23.2R1. | [
"encapsulation"
] |
clear-dont-fragment-bit (Interfaces GRE Tunnels) | clear-dont-fragment-bit; | [edit interfaces gr-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number] | Clear the Don’t Fragment (DF) bit on all IP version 4 (IPv4) packets entering the generic routing
encapsulation (GRE) tunnel on Adaptive Services (AS) or Multiservices interfaces. If the encapsulated
packet size exceeds the tunnel maximum transmission unit (MTU), the packet is fragmented before
encapsulation.
When you ... | [] | 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 10.2 for MPC1 and MPC1Q.
NOTE: On SRX platforms the clearing of the DF bit on a GRE tunnel is supported only
when the device is in packet or selective packet mode; This feature is not supported in
flow mode. As a result, when in ... | [
"Enabling Fragmentation on GRE Tunnels"
] |
clear-dont-fragment-bit (NAT Next Gen Services) | set clear-dont-fragment-bit; | [edit services nat natv6v4] | Specify that the don’t fragment (DF) bit for IPv4 packet headers is cleared when the packet length is less
than 1280 bytes. Use this statement when configuring stateful NAT64, deterministic NAPT64, and
464XLAT. This prevents unnecessary creation of an IPv6 fragmentation header when translating IPv4
packets that are les... | [] | 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. | [] |
clear-dont-fragment-bit (Services IPsec VPN) | clear-dont-fragment-bit; | [edit services ipsec-vpn rule rule-name term term-name then] | Clear the do not fragment (DF) bit on all IP version 4 (IPv4) packets entering the IPsec tunnel. If the
encapsulated packet size exceeds the tunnel maximum transmission unit (MTU), the packet is
fragmented before encapsulation.
By default, this statement is disabled (the DF bit value is not cleared on the inner header ... | [] | 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 IPsec Rules"
] |
clear-dont-fragment-bit (Services NAT Options) | clear-dont-fragment-bit; | [edit services service-set service-set-name nat-options stateful-nat64] | Clear the DF (don't fragment) bit in a translated IPv4 packet if its packet size is less than 1280 bytes. If
the packet is greater than or equal to 1280 bytes, the DF bit is not cleared. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced with Junos OS Release 12.1. | [
"Configuring Service Rules"
] |
clear-dont-fragment-bit (Services Service Set) | clear-dont-fragment-bit; | [edit services service-set service-set-name ipsec-vpn-options] | Clear the Don’t Fragment (DF) bit on all IP version 4 (IPv4) packets entering the IPsec tunnel. If the
encapsulated packet size exceeds the tunnel maximum transmission unit (MTU), the packet is
fragmented before encapsulation. This statement is useful for dynamic endpoint tunnels, for which you
cannot configure the cle... | [] | 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 IPsec Service Sets",
"Configuring IPsec Rules"
] |
clear-ike-sas-on-pic-restart | clear-ike-sas-on-pic-restart; | [edit services ipsec-vpn] | Clear IKE security associations (SAs) when the corresponding PIC restarts or is taken offline. | [] | 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 Security Associations"
] |
clear-ipsec-sas-on-pic-restart | clear-ipsec-sas-on-pic-restart; | [edit services ipsec-vpn] | Clear IPsec security associations (SAs) when the corresponding PIC restarts or is taken offline. | [] | 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 Security Associations"
] |
clear-on-abort (DHCP Local Server) | clear-on-abort; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server reconfigure],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 reconfigure],
[edit logical-systems logical-system-name routing-i... | Delete all DHCP clients or only the DHCP clients serviced by the specified group of interfaces when
reconfiguration fails; that is, when the maximum number of retry attempts have been made without
success. A group configuration takes precedence over a DHCP local server configuration.
Default
Restores the original clien... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Support at the [edit ... dhcpv6 ...] hierarchy levels introduced in Junos OS Release 10.4. | [
"Configuring Dynamic Reconfiguration of Extended Local Server Clients Overview",
"Configuring Deletion of the Client When Dynamic Reconfiguration Fails"
] |
clear-services-web-filter-dns-feed-statistics-feed-name | clear services web-filter dns-feed-statistics feed-name feed-name | Clear statistics for DNS request filtering for the specified feed-name. | [] | clear | Command introduced in Junos OS Release 21.1R1. | [
"DNS Request Filtering for Disallowed Website Domains",
"Configuring URL Filtering"
] | |
clear-threshold | clear-threshold value; | [edit logical-systems name security nat source pool name pool-utilization-alarm],
[edit logical-systems name security nat source pool-utilization-alarm],
[edit logical-systems name tenants name security nat source pool name pool-utilization-
alarm],
[edit logical-systems name tenants name security nat sourc... | Configure the lower threshold at which an SNMP trap is triggered when pool utilization for a source
pool without Port Address Translation (PAT) falls below the threshold. | [
{
"name": "clear-threshold value",
"desc": "Threshold at which an SNMP trap is triggered. Range: 40 through 100"
}
] | security–To view this statement in the configuration.
security-control–To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [] |
client (interfaces) | client; | [edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number pppoe-options] | Configure the router to operate in the PPPoE client mode. | [] | 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 the PPPoE Client Mode"
] |
client (System Services) | client name; | [edit system services webapi (System Services)] | Configures the IP address of the client. For the Integrated ClearPass Authentication and Enforcement
feature Web API process configuration, the client is the ClearPass Policy Manager (CPPM).
The SRX Series Web API process acts as an HTTP(S) server. The CPPM client sends POST request
messages containing user authenticat... | [
{
"name": "name",
"desc": "IP Address of the client."
}
] | 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. | [] |
client (TWAMP) | client {
control-connection control-client-name {
control-type (managed | light);
destination-port destination-port;
routing-instance routing-instance-name;
source-address source-address;
source-routing {
forward (srmpls-nodes <label hop1...n> | srv6-nodes <IPv6... | [edit services monitoring twamp] | Defines the Two-Way Active Measurement Protocol (TWAMP) client configuration. A client opens a
TCP connection to the server on well-known port 862. The host that initiates the TCP connection takes
on the roles of control client and session sender. The host that acknowledges the TCP connection
accepts the roles of serve... | [] | 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.
Statement introduced in Junos OS Evolved Release 20.3R1.
control-type option introduced in Junos OS Release 21.1R1 and Junos OS Evolved Release 20.3R1.
traps option introduced in Junos OS Evolved Release 21.3R1.
source-address option and the local-link sub-option of the ta... | [
"Understand Two-Way Active Measurement Protocol"
] |
client (Unified Edge) | client client-name; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS client for the incoming RADIUS request from an IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected. | [
{
"name": "client-name",
"desc": "Name of the RADIUS client. NOTE: The RADIUS client must have been previously configured at the [edit access radius] hierarchy level, and specified as the aaa-client at the [edit unified-edge gateways tdf gateway-name] hierarchy level."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring 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",... |
client | client client-name {
chap-secret chap-secret;
group-profile profile-name;
ike {
allowed-proxy-pair {
remote remote-proxy-address local local-proxy-address;
}
pre-shared-key (ascii-text character-string | hexadecimal hexadecimal-digits);
ike-policy policy-name;
... | [edit access profile profile-name] | Configure the peer identity.
NOTE: Subordinate statement support depends on the platform. See individual
statement topics for more detailed support information. | [
{
"name": "client-name",
"desc": "A peer identity. For L2TP clients, you can use a special name to configure a default client. This client enables the LNS to accept any LAC to establish the session. On M Series routers, use * for the default client configuration. On MX Series routers, use default."
},
{... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the PPP Challenge Handshake Authentication Protocol",
"Point-to-Point Protocol (PPP)",
"Layer 2 Tunneling Protocol (L2TP)",
"L2TP LNS Inline Service Interfaces"
] |
client-address | client-address ipv4-address; | [edit services hosted-services server-profile server-profile-name] | Configure the source address to include in the header of each sampled packet. You must specify an IPv4
address. You can also specify the loopback address or the management interface address as the client
address. | [
{
"name": "ipv4-address",
"desc": "IPv4 address of the client."
}
] | 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"
] |
client-config (Juniper Secure Connect) | client-config name {
application-bypass {
term name {
description description;
protocol protocol;
domain-name domain-name;
}
}
biometric-authentication;
domain-name domain-name;
certificate { no-expiry-warning;
no-pin-request-per-connection;... | [edit security remote-access] | Define Juniper Secure Connect remote client configuration parameters. The parameters define how
Juniper Secure Connect client establishes VPN tunnel with your security device. | [
{
"name": "name",
"desc": "Name of configuration object name."
},
{
"name": "application-bypass",
"desc": "Define application-bypass configuration."
},
{
"name": "biometric-authentication",
"desc": "Enable biometric authentication."
},
{
"name": "domain-name",
"desc": "De... | security | Statement introduced in Junos OS Release 20.3R1.
Support for domain-name option at the [edit security remote-access client-config name] hierarchy level added in
Junos OS Release 22.1R1.
Support for application-bypass option added in Junos OS Release 23.1R1. | [
"Juniper Secure Connect Administrator Guide"
] |
client-delegate-probes | rpm client-delegate-probes; | [edit interfaces interface-name unit logical-unit-number] | Generate real-time performance monitoring (RPM) probes on an MS-MPC or MS-MIC services interface,
which increases the number of RPM probes that can run at the same time.
The destination-interface statement must be configured at the [edit services rpm probe owner test test-name]
hierarchy level to point to the interface... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
client-discover-match (DHCP Local Server) | client-discover-match <option60-and-option82 | incoming-interface>; | [edit system services dhcp-local-server overrides],
[edit system services dhcp-local-server group group-name overrides],
[edit system services dhcp-local-server group group-name interface interface-name overrides]
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-lo... | Configure the match criteria DHCP local server uses to uniquely identify DHCP subscribers or clients
when primary identification fails. The options are mutually exclusive.
Default
By default, DHCP uses the option60-and-option82 option. | [
{
"name": "incoming-interface",
"desc": "(Optional) Allow only one client device to connect on the interface. If the client device changes, the router deletes the existing client binding and creates a binding for the newly connected device. NOTE: The overrides client-discover-match incoming-interface config... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
incoming-interface option added in Junos OS Release 13.3. | [
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Overriding the Default DHCP Local Server Configuration Settings",
"DHCP Auto Logout Overview",
"Allowing Only One DHCP Client Per Interface"
] |
client-discover-match (DHCP Relay Agent) | client-discover-match <option60-and-option82 | incoming-interface>; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit forwarding-options dhcp-relay group group-name interface interface-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ... overrides],
[edit logical-systems logical... | Configure the match criteria DHCP relay uses to uniquely identify DHCP subscribers or clients when
primary identification fails. The options are mutually exclusive.
Default
By default, DHCP uses the option60-and-option82 option. | [
{
"name": "incoming-interface",
"desc": "(Optional) Allow only one client device to connect on the interface. If the client device changes, the router deletes the existing client binding and creates a binding for the newly connected device. NOTE: The overrides client-discover-match incoming-interface config... | 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.
incoming-interface option added in Junos OS Release 13.3. | [
"Extended DHCP Relay Agent Overview",
"Overriding the Default DHCP Relay Configuration Settings",
"DHCP Auto Logout Overview",
"Allowing Only One DHCP Client Per Interface"
] |
client-group | client-group [ group-names ]; | [edit access profile profile-name client client-name]
[edit access profile profile-name session-options] | Specify a list of client groups that the client belongs to. If the group list is not defined as part of the
client profile, the client group configured at the [edit access profile session-options] hierarchy level is
used. | [
{
"name": "group-names",
"desc": "Names of one or more groups the client belongs to, separated by spaces—for example g1,"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
client-ia-type | client-ia-type {
ia-na;
ia-pd;
} | [edit interfaces interface-name unit logical-unit-number family inet6 dhcpv6-client]
[edit logical-systems logical -system-name interfaces interface-name unit logical-unit-number
family inet6 dhcpv6-client]
[edit tenants tenant-name interfaces interface-name unit logical-unit-number family inet6 dhcpv6-
client] | Configure the DHCPv6 client identity association type. | [
{
"name": "ia-na",
"desc": "Identity association for nontemporary address"
},
{
"name": "ia-pd",
"desc": "Identity association for prefix delegation"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10.
The logical-systems and tenants options are introduced in Junos OS Release 18.4R1. | [
"DHCPv6 Client Overview"
] |
client-id (DHCP Local Server) | client-id <exclude-headers> <use-automatic-ascii-hex-encoding>; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 group group-name authentication user... | Specify that the client identifier (DHCP option 61) is concatenated with the username during the
subscriber authentication or client authentication process. | [
{
"name": "exclude-headers",
"desc": "By default, all headers that are part of the client identifier format in option 61 are included in the username string used for RADIUS authentication. Configure the exclude-headers option to exclude the use of headers in the username string."
},
{
"name": "use-a... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Creating Unique Usernames for DHCP Clients"
] |
client-id (DHCP Relay Agent) | client-id <exclude-headers> <use-automatic-ascii-hex-encoding>; | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay group group-name authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 authentication username-in... | Specify that the client identifier (DHCP option 61) is concatenated with the username during the
subscriber authentication or client authentication process. | [
{
"name": "exclude-headers",
"desc": "By default, all headers that are part of the client identifier format in option 61 are included in the username string used for RADIUS authentication. Configure the exclude-headers option to exclude the use of headers in the username string."
},
{
"name": "use-a... | 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. | [
"Specifying Authentication Support",
"Creating Unique Usernames for DHCP Clients"
] |
client-identifier (DHCP Client) | client-identifier {
hardware-type type-number
user-id {ascii ascii hexadecimal hexadecimal;
use-interface-description {logical |device};
prefix [host-name routing-instance-name];
} | [edit interfaces name unit name family inet dhcp],
[edit interfaces interface-range name unit name family inet dhcp] | The DHCP server identifies a client by a client-identifier value. | [
{
"name": "hardware-type",
"desc": "Specify the type of hardware used for the interface on which the client access. Ethernet is the common hardware type and the value for Ethernet is 1. Default: Zero Range: Zero through 255"
},
{
"name": "ascii",
"desc": "Client identifier as an ASCII string"
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
Starting with Junos OS Release 17.3R1, on all SRX Series Firewalls and vSRX Virtual Firewall instances,
the CLI option dhcp-client at [edit interfaces interface-name unit logical-unit-number family inet] hierarchy is
changed to dhcp to keep consistent with other Jun... | [
"DHCPv6 Client Overview"
] |
client-identifier (DHCPv6 Client) | client-identifier duid-type (duid-ll | duid-llt | vendor); | [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
[edit logical-systems logical -system-name interfaces interface-name unit logical-unit-number
family inet6 dhcpv6-client]
[edit tenants tenant-name interfaces interface-name unit logical-unit-number family inet6 dhcpv6-
client] | The DHCPv6 server identifies a client by a client-identifier value. | [
{
"name": "duid-type",
"desc": "The DHCPv6 client is identified by a DHCP unique identifier (DUID)."
},
{
"name": "duid-ll",
"desc": "Link Layer address."
},
{
"name": "duid-llt",
"desc": "Link Layer address plus time."
},
{
"name": "vendor",
"desc": "Vendor-assigned uniq... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10.
The logical-systems and tenants options are introduced in Junos OS Release 18.4R1. | [
"DHCPv6 Client Overview"
] |
client-identifier (Interfaces) | client-identifier {
(ascii string | hexadecimal string);
} | [edit interfaces interface-name unit logical-unit-number family family-name dhcp] | Specify an ASCII or hexadecimal identifier for the Dynamic Host Configuration Protocol (DHCP) client.
The DHCP server identifies a client by a client-identifier value. | [
{
"name": "ascii ascii",
"desc": "Identifier consisting of ASCII characters."
},
{
"name": "hexadecimal hexadecimal",
"desc": "Identifier consisting of hexadecimal characters."
}
] | 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. | [
"Understanding Interfaces"
] |
client-identity (NETCONF TLS) | client-identity client-id {
fingerprint fingerprint;
map-type (san-dirname-cn | specified);
username username;
} | [edit system services netconf tls] | For NETCONF sessions over Transport Layer Security (TLS), configure the method to derive the
NETCONF username for a given client certificate.
Each configured client must include a client’s certificate fingerprint and a map type. If the fingerprint of a
client’s presented certificate matches the fingerprint for a config... | [
{
"name": "client-id",
"desc": "User-defined name that uniquely identifies the client."
},
{
"name": "fingerprint",
"desc": ""
},
{
"name": "fingerprint",
"desc": "Client’s certificate fingerprint, which is a cryptographic hash of an X.509 certificate in x509c2n:tls-fingerprint forma... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1.
Statement introduced in Junos OS Evolved Release 21.4R1. | [] |
client-idle-timeout (Access Profile) | client-idle-timeout minutes; | [edit access profile profile-name session-options] | Specify the grace period that begins after an authenticated user terminates all sessions and connections.
Authentication is not required if a new connection is initiated during the grace period by the same user. | [
{
"name": "minutes",
"desc": "Number of minutes of idle time that elapse before the session is terminated."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
client-list (SNMP) | client-list client-list-name {
ip-addresses;
} | [edit snmp] | Define a list of SNMP clients. | [
{
"name": "client-list-name",
"desc": "Name of the client list."
},
{
"name": "ip-addresses",
"desc": "IP addresses of the SNMP clients to be added to the client list,"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Adding a Group of Clients to an SNMP Community"
] |
client-list | client-list list-name {
address address;
} | [edit services monitoring twamp server] | Specify the list of allowed control client hosts that can connect to this server. Each entry is a Classless
Interdomain Routing (CIDR) address (IP address plus mask) that represents a network of allowed hosts.
You can configure more than one list, but you must configure at least one client address to enable
TWAMP. Each... | [
{
"name": "list-name",
"desc": "Name of client address list."
},
{
"name": "address",
"desc": "Address and mask for an allowed client."
}
] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
Statement introduced in Junos OS Evolved 20.3R1.
IPv6 address support introduced in Junos OS Evolved Release 21.4R1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
client-list-name | client-list-name client-list-name; | [edit snmp community community-name] | Add a client list or prefix list to an SNMP community. | [
{
"name": "client-list-name",
"desc": "Name of the client list or prefix list."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Adding a Group of Clients to an SNMP Community"
] |
client-name-filter | client-name-filter client-name {
count number;
domain-name domain-name;
separator special-character;
} | [edit access profile profile-name] | Define client-name-related restrictions. Clients whose names follow these restrictions are authenticated
on the server. | [
{
"name": "client-name",
"desc": "Name of the client."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Obtaining Username and Role Information Through Firewall Authentication"
] |
client-negotiation-match (DHCPv6 Local Server) | client-negotiation-match incoming-interface; | [edit system services dhcp-local-server dhcpv6 overrides],
[edit system services dhcp-local-server dhcpv6 group group-name overrides],
[edit system services dhcp-local-server dhcpv6 group group-name interface interface-name
overrides] | Configure the match criteria the DHCPv6 local server uses to uniquely identify IPv6 subscribers or
clients. | [
{
"name": "incoming-interface",
"desc": "Allow only one client device to connect on the interface. If the client device changes, the router deletes the existing client binding and creates a binding for the newly connected device."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Automatically Logging Out DHCPv6 Clients",
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Allowing Only One DHCP Client Per Interface"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.