How Junos OS Evolved Differs from Junos OS
In many ways, Junos OS Evolved is the same as Junos OS: Key applications such as the routing, bridging, and management software are the same in both and management plane interfaces and APIs, such as CLI, NETCONF, JET, JTI, AFI, and underlying data models, remain highly consistent. In both Junos OS and Junos OS Evolved, you can use remote authentication methods through the console port. There are, however, some differences in behavior, the CLI syntax, and CLI and XML output. These differences are indicated throughout the Junos OS documentation. However, this section outlines the differences in one place, for your convenience. If applicable, a link takes you to the place in the Junos OS documentation that covers the item.
For a more detailed overview of the top differences between Junos OS and Junos OS Evolved, see Top Differences Between Junos OS Evolved and Junos OS.
Behavioral Differences Between Junos OS Evolved and Junos OS
Behavioral differences between Junos OS Evolved and Junos OS are ways that the two operating systems act differently in certain circumstances. See Table 1.
Junos OS Evolved Behavior |
Junos OS Behavior |
Link to Documentation |
---|---|---|
Access and Authentication | ||
In Junos OS Evolved Release 20.4R1 and earlier releases, when you do not configure the password authentication method and the remote authentication servers reject the authentication request, the device still attempts local password authentication. Remote authentication methods are supported through the console port in 23.2R2-EVO and from 23.4R1-EVO onwards, and unsupported before 23.2R2-EVO and 23.3 EVO. |
In Junos OS, when you do not configure the password authentication method and the remote authentication servers reject the authentication request, the request ends with the rejection. |
Authentication Order for LDAPS, RADIUS, TACACS+, and Local Password |
Junos OS Evolved does not support the following options at the
|
In Junos OS, the backoff-threshold , backoff-factor lockout-period , maximum-time , minimum-time , and tries-before-disconnect options are supported at [edit system login retry-options] hierarchy. |
|
Interfaces | ||
The management interface name format changed to accommodate more than one management port per Routing Engine node. The names are re0:mgmt-0/re0:mgmt-1 and re1:mgmt-0/re1:mgmt-1. Both the management interfaces are configurable and displayed. |
The management interface name that you use depends on the type of device that you are setting up. Some devices use me0, some use fxp0, and some use em0. |
|
In an untagged link aggregation group (LAG), child logical interface (IFL) members are created. Requests are made per child IFL member. The results are aggregated and displayed in the CLI. In a VLAN-tagged LAG, extra child IFLs are not created as part of the aggregated Ethernet bundle. Link IFL statistics and marker statistics for child IFLs are not displayed. |
Child IFL members are created in untagged and VLAN-tagged LAGs. Requests are made per child IFL member. The results are aggregated and displayed in the CLI. |
|
When a new interface is added as a member to an aggregated Ethernet bundle, the new member interface flaps: the physical interface is deleted as a regular interface and then added back in as an aggregated Ethernet member and the statistics are reset. |
When a new interface is added as a member to an aggregated Ethernet bundle, that new interface is not first deleted as a lone interface and then added, but everything below it is. Because the interface is not deleted, it keeps all the statistics and other history associated with it. |
Aggregated Ethernet Interfaces and Understanding Aggregated Ethernet Interfaces and LACP for Switches |
Junos OS Evolved does not impose a limit on the maximum number of member (or child) interfaces in an aggregated interface. However, platform limits still apply. |
Junos OS imposes a limit of 64 member (or child) interfaces in an aggregated interface. |
Aggregated Ethernet Interfaces and Understanding Aggregated Ethernet Interfaces and LACP for Switches |
In Junos OS Evolved, when you configure a parent interface for Aggregated Ethernet with the [ |
In Junos OS, configurations for aggregated Ethernet interfaces and non-aggregated Ethernet interfaces at the |
|
In Junos OS Evolved, when you add a duplicate IP address or prefix to an existing configuration, the operating system will error out and prevent a commit. Instead, you must first delete the existing prefix and commit the new configuration. After you have done that, you can add the duplicate prefixes and commit. |
In Junos OS, you can add a duplicate IP address or prefix to an existing configuration without having your commit blocked. |
|
Starting from Junos OS Evolved Release 21.1R1, we changed the default forward error correction (FEC) for 25-Gigabit and 50-Gigabit interfaces to FEC91 from FEC74 because FEC91 has better performance. FEC mode is assigned by default. You must disable FEC mode if you do not want it assigned by default. |
In Junos OS, the default FEC for 25-Gigabit and 50-Gigabit interfaces is FEC74. You can configure FEC clauses CL74 on 25-Gigabit and 50-Gigabit interfaces, and CL91 on 100-Gigabit interfaces. Since the FEC clauses are applied by default on these interfaces, you must disable the FEC clauses if you do not want to apply them. |
|
High Availability | ||
On PTX10004 and PTX10008 platforms running Junos OS Evolved, graceful Routing Engine switchover (GRES) is enabled by default and cannot be disabled. |
GRES is disabled by default. |
Understand Graceful Routing Engine Switchover for Junos OS Evolved |
In Junos OS Evolved, the output for |
Junos OS output for Kernel database . |
|
(Only for QFX5220-32CD switches) In-Service Software Upgrade (ISSU) is performed by using the |
ISSU is performed by using the |
|
Junos XML API and Scripting | ||
You must set up the password-less login between two devices to use the |
You are not limited to password-less login. Junos OS supports both a supplied password and interactive password, for example, to execute RPCs on remote devices. |
|
The eventd process does not give any warning message if there are duplicate event policies. Instead eventd accepts the event policy on a first-come, first-served basis. |
The eventd process gives a warning message if you try to create duplicate event policies. |
|
For op scripts run with the |
For op scripts run with the |
|
If you execute the |
If you execute the |
|
Junos OS Evolved stores the trace data for all scripts under the |
Junos OS stores the trace data for each type of script in a different file. You can modify the default trace settings by configuring the |
|
Messaging | ||
TIP: You can compare syslog messages in a Junos OS release to a Junos OS Evolved release using the System Log Explorer. | ||
The messages file located under /var/log is only written on the primary Routing Engine. Backup Routing Engine messages are found in the messages file on the primary Routing Engine. |
The messages file is written on both the primary Routing Engine and the backup Routing Engine. |
|
Junos OS Evolved appends the node name to the hostname in system log messages. As of Junos OS Evolved Release 20.4R2, you can configure the |
Junos OS does not. |
|
Starting in Junos OS Evolved Release 20.1R1 and 19.4R2, if you are sending syslog messages to a remote host that is identified by its IP address at the |
Configure the mgmt_junos routing instance at the |
|
When a regular expression returns empty pattern matches, there is no error message. |
When a regular expression returns empty pattern matches, you get the following error: regex error: empty (sub)expression |
Junos System Log Regular Expression Operators for the match Statement |
Junos Evolved does not support a /var/log/inventory file. |
In Junos the /var/log/inventory log file stores hardware serial numbers. For Junos Evolved use the CLI show chassis hardware operational mode command to display hardware inventory. |
Note: The
/var/log/inventory logfile is deprecated functionality in Junos. |
Routing Policy and Firewall Filters | ||
When you issue the |
When you issue the |
|
Firewall filters applied to the loopback interface apply only to network control traffic. You must explicitly apply firewall filters to the management interface to filter management traffic. |
Firewall filters applied to the loopback interface apply to both network control traffic and management traffic. |
|
In Junos OS Evolved, if a match action term on your filter configuration fails on commit, the entire filter is not applied. This happens when a term you configured is not supported on your device. |
In Junos OS, if a match action term on your filter configuration fails on commit, the remainder of the filter is applied. |
|
When you use an IPv6 filter with packet length matching, the match parameter only considers the TCP header length and the data length. To configure the statement |
When you use an IPv6 filter with packet length matching, the match length parameter includes the IPv6 header size. |
|
In a filter with icmp match conditions, Junos OS Evolved supports configuration of a single icmp-type value along with an icmp-code value. Junos OS Evolved supports configuration of multiple icmp-type values only when an icmp-code value is not specified. |
Junos OS supports a configuration that contains multiple icmp-type values and an icmp-code value. |
|
Software Installation and Upgrade | ||
Multiple releases of the software can be installed on the device simultaneously as long as there is space. If there is no more space, you must delete an older image of the software before installing the new one. |
Only two versions of the software can be installed on the device: the current version and the previous version. |
Software Installation and Upgrade Overview (Junos OS Evolved) |
The |
The |
request system snapshot (Junos OS Evolved) Software Installation and Upgrade Overview (Junos OS Evolved) |
The |
The |
|
During the validation phase of a software upgrade, Junos OS Evolved installs the image in a temporary storage location until validation is complete. After validation is complete, Junos OS Evolved will attempt to uninstall the image and display a status message. |
Junos OS installs the software upgrade image in a standard storage location. No message is displayed following image validation. | Validate the Configuration against the Installation Image |
After you add a new software image, you must reboot the system to run the new software. If you have added the software image but have not yet rebooted, you can issue the |
If you have completed the installation of the software image but have not yet rebooted, issue the |
request system software delete (Junos OS Evolved) |
Junos OS Evolved supports one system log file that contains all system log messages for the Zero Touch Provisioning (ZTP) process: /var/log/ztp.log. |
Junos OS ZTP system log messages are spread out over several system log files:
|
Zero Touch Provisioning for Junos OS Evolved |
ZTP for Junos OS Evolved supports WAN interfaces as well as the management interface for Routing Engine 0. ZTP dynamically detects the port speed of WAN interfaces and uses this information to create ZTP server ports with the same speed. | ZTP for Junos OS supports management interfaces. | Zero Touch Provisioning for Junos OS Evolved |
For ZTP on Junos OS Evolved, if downloading a file fails, ZTP clears the DHCP client binding on that interface and restarts the state machine on other interfaces. If installation fails for any reason, ZTP retries on other interfaces. |
If downloading a file fails on Junos OS, the DHCP client attempts to fetch files from the DHCP server for up to six times, with ten to fifteen seconds elapsing between attempts. If the download fails, ZTP stops. ZTP then clears the DHCP client bindings and restarts the state machine on the DHCP-configured interfaces. If installation fails for any reason, ZTP restarts. | Zero Touch Provisioning for Junos OS Evolved |
ZTP for Junos OS Evolved accepts unsigned scripts in DHCP option 43, suboption 1. | ZTP for Junos OS with Enhanced Automation accepts unsigned scripts in DHCP option 43, suboption 1; otherwise, scripts must be signed. | Zero Touch Provisioning for Junos OS Evolved |
ZTP for Junos OS Evolved uses DHCP option 43, suboption 5 for the IP address of the FTP server and does not use option 8. | ZTP for Junos OS uses DHCP option 43, suboption 5 for the HTTP port and uses suboption 8 for the IP address of the HTTP proxy server. | Zero Touch Provisioning for Junos OS Evolved |
ZTP for Junos OS Evolved does not change the default route. | For Junos OS, after the lists of bound and unbound client interfaces are created, and a DHCP client gets selected for ZTP activity, any existing default route is deleted and the DHCP client interface that was selected adds a new default route. To add a new default route, only one ZTP instance can be active. |
Zero Touch Provisioning for Junos OS Evolved |
System Management | ||
In Junos OS Evolved, the To reboot a specific node, use the |
In Junos OS, by default, the request system reboot command reboots only the Routing Engine to which you are connected. |
request system reboot (Junos OS Evolved) |
After rebooting Junos OS Evolved, the system initializes time from the hardware clock. The ntpd command with the -g option runs to adjust the time if the initial offset is large (greater than 1000 seconds). In addition, the system synchronizes time with a valid NTP server. |
When you boot Junos OS, the system issues an ntpdate request, which polls a network server to determine the local date and time. You need to configure a server that the system can use to determine the time when the system boots. If an NTP boot server was configured when the system boots, the system immediately synchronizes with the NTP boot server. Synchronization occurs even when the NTP process is explicitly disabled or when the time difference between the client and the NTP boot server exceeds the threshold value of 1000 seconds. |
|
Troubleshooting | ||
Junos OS Evolved uses a new tracing infrastructure. For Junos OS Evolved, trace data from all applications on all nodes is collected on the Routing Engine. You use the |
Configure |
|
For Junos OS Evolved, a core file created during early bootup is stored in /var/core/re. However, a core file created later in the bootup, for example, after the Routing Engine slot number can be determined, is stored in /var/core/re0 or /var/core/re1. The command |
For Junos OS, core files are stored in /var/crash or /var/tmp. |
|
User Interface | ||
Junos OS Evolved does not support the |
The |
configuration-database |
The |
The show system reboot command has options to Execute this command, Show halt or reboot requests on both Routing Engines, or Pipe through a command. |
|
In Junos OS Evolved, enabling the command |
When NSR is configured and the command edit system switchover-on-routing-crash is enabled, Junos OS will immediately switch to the backup Routing Engine when rpd crashes. |
|
In Junos OS Evolved, when |
Junos OS triggers a switchover when edit system processes routing failover other-routing-engine is configured and certain commands such as restart routing and restart routing immediately are used many times in short succession. |
|
The menu used for root password recovery is the GRUB menu. *Primary ptx-fixed-19.1-16 Primary [Recover password] Primary-Rollback ptx-fixed-19.1-15 Primary-Rollback [Recover password] |
The menu used for root password recovery is the Junos Main Menu (the Recovery mode option). |
|
The |
When the FRU is offline, the cached firmware information of the FRU is not available to view. |
New CLI Statements and Commands (Junos OS Evolved)
The changes in infrastructure between Junos OS and Junos OS Evolved sometimes require different CLI configuration statements and operational commands. For more on these new statements and commands, see Table 2.
Statement or Command |
Description |
Link |
---|---|---|
New Statements | ||
|
You can configure how much fabric degradation is allowed before automatic recovery actions are taken by Junos OS Evolved. | reachability-fault |
|
You can use the configuration statement |
|
|
You can configure the TWAMP monitoring service on devices running Junos OS Evolved by using the hierarchy level
|
Understanding Two-Way Active Measurement Protocol on Routers and twamp |
|
Junos OS Evolved supports host IPsec in the control plane only (that is, IPsec between the router and external management devices), which is not available in Junos OS. These statements configure a host-to-host VPN type of IPsec connection. Use the |
|
|
You can configure the additional algorithms
|
|
|
Statements at this hierarchy level include |
|
|
Statement to support dead peer detection. The dead peer detection delay sends keepalives to find out if a peer has gone dead. |
|
|
Configure identity details for authenticating the remote device during IKE negotiations. |
|
[edit system auto-sw-sync] |
Automatically copy over all the images (software and configuration) from the primary Routing Engine of the system to the new Routing Engine and reboot the new Routing Engine so it runs the same software version and configuration as the primary Routing Engine. | |
[edit system configuration-database extend-size] |
Increase the memory space available for the configuration database. Note:
In some releases prior to Junos OS Evolved Release 22.1R1, the extend-size statement is available in the CLI and you can configure and commit it, but it has no operational effect. |
|
[edit system log alternate-format] | Attach the node name to the process name instead of the hostname. This alternate format allows monitoring systems to identify the hostname correctly. | syslog |
|
For Junos OS Evolved, trace data from all applications on all nodes is collected on the Routing Engine. See Top Differences Between Junos OS Evolved and Junos OS for information about tracing architecture. See also the |
|
New Commands | ||
|
Remove all pending node halt, reboot, and power-off requests. |
|
|
Clear host IPsec security association information. See also |
|
|
Clear connections established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients. |
|
|
Junos OS Evolved uses a new tracing infrastructure. This command deletes the trace data stored on the Routing Engine, enabling you to remove inactive tracing sessions. See also |
|
|
Request an operation on a specific node. | request node halt (Junos OS Evolved) request node (offline | online) (Junos OS Evolved) request node power-off (Junos OS Evolved) |
|
Start or stop a Two-Way Active Measurement Protocol (TWAMP) session. |
|
|
Stop and then start (restart) a specific process (for example, cmdd) on the node you specify. |
|
|
Collect debug information from Junos OS Evolved, such as logs. The logs are stored in the /var/tmp/debug_collector_timestamp directory. Use the |
|
|
Synchronize software and configurations from the primary Routing Engine to the other nodes and reboot the other nodes. | |
|
The command performs a dry run of the |
|
|
The following message is logged when you use the
|
|
|
Display the health of the hard disk with the |
|
|
Display any pending halt, reboot, or power-off requests on a node. |
|
|
Display the network statistics of a node. |
show node statistics |
|
Display host IPsec security association information for a specific security association or for all connections. See also |
|
|
Display the version of IPsec being used in the system. |
|
|
Display the results stored for the specified real-time performance monitoring (RPM) probes. |
|
|
Display the results of the most recent real-time performance monitoring (RPM) probes. |
|
|
Display standard information about the results of the last 50 probes for a Two-Way Active Measurement Protocol (TWAMP) control connection. |
|
|
Display the results of the most recent Two-Way Active Measurement Protocol (TWAMP) probes. |
|
|
Display information about the control connections established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients. |
|
|
Display information about the test sessions established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients. |
|
|
Display information about the control connections established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients for managed servers. |
|
|
Display information about the test sessions established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients. |
|
|
Display information about active applications on the system. |
|
|
Display information about faults in the system. Note:
For Junos OS Evolved, only the QFX5200 supports this command. For all other Junos OS Evolved platforms, use the show system errors active, show system errors count, show system errors error-id, or show system errors fru command. |
|
|
Display information about faults in the system that have been cleared. Note:
For Junos OS Evolved, only the QFX5200 supports this command. For all other Junos OS Evolved platforms, use the show system errors active, show system errors count, show system errors error-id, or show system errors fru command. |
|
show system nodes |
View a list of all nodes in the system. |
show system nodes |
|
Display all console messages from the last in-service software upgrade (ISSU). |
|
|
Display the installed versions on all nodes in the system. |
|
|
Displays system statistics options for the backup Routing Engine. The options provided are the same as the options for |
|
|
Displays system jtd statistics. |
|
|
Junos OS Evolved implements ZTP using the Linux dhcp client. Users can find out the interfaces chosen by ZTP, arguments returned by DHCP, and ZTP state machine states. |
|
|
Junos OS Evolved uses a new tracing infrastructure. This command shows the trace data from all nodes that are collected on the Routing Engine. |
|
|
Junos OS Evolved uses a new command to display the hashing algorithm to make hashing decisions. This command shows the data about which packet fields are used by the hashing algorithm. | |
|
Junos OS Evolved replaces the
|
Modified CLI Statements and Commands (Junos OS Evolved)
Some CLI statements and commands in Junos OS Evolved have a different set of options from Junos OS. For a list of these changes, see Table 3.
For the CLI commands that produce changed output, see Table 4.
Statement or Command |
Change in Junos OS Evolved |
Link |
---|---|---|
Modified Statements | ||
|
The |
|
|
Egress filters do not support
gre-key matches. |
|
|
The |
|
|
In Junos OS Evolved, |
|
|
In Junos OS Evolved, |
|
|
The following options are added to the
|
|
|
The following options for this command are not supported:
|
|
|
In Junos OS Evolved, the option
|
|
[edit system
internet-options] |
In Junos OS Evolved, the following options are not supported:
|
internet-options |
|
In Junos OS Evolved, the
|
Direct System Log Messages to a Remote Machine or the Other Routing Engine |
[edit
system commit] |
Junos OS Evolved does not support the following options:
|
commit (System) |
Modified Commands | ||
|
In Junos OS Evolved, issuing the |
|
monitor
traffic interface |
The write-file option for
the monitor traffic interface command takes
precedence over the extensive option when you
configure those two options simultaneously. If you try to configure
these options at the same time, Junos OS Evolved gives you a warning
message that the options are not compatible, and it only runs the
monitor traffic interface write-file command. |
monitor traffic |
|
Junos OS Evolved does not support the following
|
|
|
The default wait time on the PTX10008 between Routing Engine
switchovers when using the |
|
|
The following
|
|
|
The following
|
|
|
The following options are added to the
The following options are not applicable in Junos OS Evolved:
|
|
|
The following
|
|
|
Use the new
option The user is prompted to check the
list of files to be deleted by using the
The following options are not applicable in Junos OS Evolved:
|
|
|
The |
|
|
The |
|
|
This command displays output on each Routing Engine, instead of just the primary Routing Engine. |
|
|
More detailed information is provided. The following fields are introduced:
|
|
|
The |
|
|
The |
|
|
The |
|
|
The Junos OS Evolved does not support the following
|
|
|
The |
|
|
The error-id option is moved to the
|
|
|
The output for this command is moved to |
|
|
The |
show system memory |
|
The following
|
|
|
The The
|
|
|
The |
|
|
The |
|
ssh |
Junos OS Evolved does not support the following
|
ssh |
|
Junos OS Evolved does not support the following
|
|
|
Junos OS Evolved does not support the following
|
Changed CLI Command Output (Junos OS Evolved)
For changes in output for Junos OS Evolved, see Table 4.
Command |
Description of Change in Output |
Link |
---|---|---|
|
Clears not only LACP statistics but also the counters displayed in the |
|
monitor traffic interface interface-name |
When you use the command monitor traffic interface interface-name on a logical interface, the output displays all packets received or transmitted on that interface, including Layer 2 traffic. When you use this command on a physical interface, the output only displays packets received and transmitted on the physical interface and does not include traffic from the logical interface. |
monitor traffic |
|
When pinging a nonresponsive route, the display output of the |
|
|
Output displays the names of the directory and the individual files being copied instead of only the directory names. |
|
|
For Junos OS Evolved, this command has a built-in feature to not start an upgrade if a reboot is pending after an upgrade or rollback. | |
|
Output displays the version instead of the package. |
|
|
Output displays the version instead of the package. |
|
The |
Use the |
|
|
Displays different output. |
|
|
LACP packets and LAG links on the members of an aggregated Ethernet interface are not counted as part of the bundle input or output statistics in the |
|
|
Configuration of IPv6 over the re0:mgmt-* interfaces is supported. |
|
|
Output displays the |
|
|
Output does not display the Packet Forwarding Engine configuration and CoS default bandwidth allocation information. Output displays zero for all loopback interface (lo0) statistics. |
|
|
Junos OS Evolved does not display statistics for an interface if it is a child of an aggregated ethernet (AE) interface. |
|
|
Junos OS Evolved does not display statistics for an interface if it is a child of an aggregated ethernet (AE) interface. | |
show lldp local-information |
Output does not display "kernel JUNOS" in the system description field because Junos OS Evolved does not have a kernel. | show lldp local-information |
|
Output displays the |
|
|
Output displays the |
|
show policer |
Output doesn't display the default ARP policer because it isn't needed in Junos OS Evolved. Distributed denial of service (DDoS) protection replaces the functionality of the default ARP policer. | show policer |
|
Output for a Routing Engine displays the Routing Engine slot number, not the Routing Engine number. |
|
|
The |
|
|
Output displays status of FRUs including CB, chassis, fans, FPC, FPM, PDU, PICS, PSM, RE, and SIB, not just FPC. |
|
|
Output displays the information per node, and the |
show system memory |
|
Output displays the snapshot device and a list of snapshots. The list shows the names of the snapshots instead of the version of the operating system. Output does not display the date the snapshot was created. |
|
|
After running ping on an unreachable host, output shows that counts for |
|
|
Output for the |
|
|
In certain releases, the output displays only the |
|
|
Output displays the same state whether the command is run from the primary or the backup Routing Engine. |
|
|
Output of the Output of the |
|
|
Output of the |
Removed CLI Statements and Commands (Junos OS Evolved)
For a listing of which CLI statements and commands are removed from Junos OS Evolved, see Table 5. Where there is an alternative statement or command to use, it is noted in the table.
Statement or Command |
Description |
---|---|
Removed Statements | |
[ |
The |
[ [ |
On QFX5130 and QFX5700 devices, |
[ |
Junos OS Evolved does not support the notification service for JET applications. |
[ [ |
These commands are replaced by [ |
Removed Commands | |
|
The |
|
This command is removed from Junos OS Evolved. |
|
This command is removed from Junos OS Evolved. |
|
This command is removed from Junos OS Evolved. |
|
AI-Scripts and Service Now are not supported on Junos OS Evolved. |
|
This command is removed because the |
|
Junos OS Evolved bundles all packages into one single ISO file, so the |
|
Use the |
|
To set the current system to an installed software version, use the |
|
There are no satellite packages in Junos OS Evolved. |
|
The command |
|
See the |
|
The functionality for this command and all options under this command are moved to |
|
This command is not supported. |
|
This command has been replaced by |
|
The removed options include |
|
This command is not supported. |
|
The |
|
This command is not supported. |
|
This command has been replaced with |
|
This command is removed starting in Junos OS Evolved Releases 21.1R1 and 20.3R2. This command is not applicable in Junos OS Evolved because the command displays the status of kernel mbufs, which are not used in Linux-based systems like Junos OS Evolved. |
|
Use |
|
This command is removed from Junos OS Evolved. |
|
Junos OS Evolved removes the |
XML Differences Between Junos OS and Junos OS Evolved
This section lists the differences in XML output between Junos OS and Junos OS Evolved.
request system storage cleanup
In Junos OS, the XML output of request system storage cleanup
uses the <file-list>
XML tag for all file types in the list of files to be deleted. In Junos OS Evolved, the XML output groups different file types inside different XML tags, for example, <core-file-list>
and <log-file-list>
. Additionally, the command targets all nodes on Junos OS Evolved, so a <node>
element encloses the output for each node.
request system storage cleanup (Junos OS)
user@host> request system storage cleanup | display xml <rpc-reply xmlns:junos="http://xml.juniper.net/junos/18.4I0/junos"> <system-storage-cleanup-information> <file-list junos:style="normal"> <file> <file-name>/var/log/dfcd_enc.0.gz</file-name> <size junos:format="551B">551</size> <date>Nov 23 15:33</date> <file> </file-list> </system-storage-cleanup-information> </rpc-reply>
request system storage cleanup (Junos OS Evolved)
user@host> request system storage cleanup | display xml <rpc-reply xmlns:junos="http://xml.juniper.net/junos/19.1I0/junos"> <system-storage-cleanup-information> <node> <node-name> RE0 </node-name> <core-file-list> <description>List of all core files to be cleared: </description> <file> <file-name>/var/core/re0/auditd.re.re0.17130.2019_02_28.03_39_36.tar.gz</file-name> <size>3.8M</size> <date>Thu Feb 28 03:40</date> </file> </core-file-list> <core-local-host-file-list> </core-local-host-file-list> <core-subdir-file-list> </core-subdir-file-list> <fpc-file-list> </fpc-file-list> <logical-systems-file-list> </logical-systems-file-list> <log-file-list> <description>Clears all App logs, App traces and App SI traces under /var/log/*, /var/log/traces/* and /var/log/si_traces/* </description> </log-file-list> <iso-file-list> </iso-file-list> </node </system-storage-cleanup-information> </rpc-reply>
show system memory
In Junos OS Evolved, the show system memory
XML output is changed to better reflect the way Linux manages memory. The output comprises a top-level <multi-routing-engine-results>
element and one <multi-routing-engine-item>
child element for each node, which contains the node name and the <system-memory-information>
for that node. In Junos OS, the device only emits a <system-memory-information>
element. Additionally, the <system-memory-summary-information>
includes the following new child elements:
<system-memory-used>
and<system-memory-used-percent>
<system-memory-buffer>
and<system-memory-buffer-percent>
<system-memory-swap>
and<system-memory-swap-percent>
and omits the following elements:
<system-memory-reserved>
and<system-memory-reserved-percent>
<system-memory-wired>
and<system-memory-wired-percent>
<system-memory-cache>
and<system-memory-cache-percent>
user@host> show system memory | display xml <rpc-reply xmlns:junos="http://xml.juniper.net/junos/22.1R0/junos"> <multi-routing-engine-results> <multi-routing-engine-item> <re-name>fpc1</re-name> <system-memory-information> <system-memory-summary-information> <system-memory-total>16125892</system-memory-total> <system-memory-total-percent>100%</system-memory-total-percent> <system-memory-used>3885112</system-memory-used> <system-memory-used-percent>24%</system-memory-used-percent> <system-memory-active>2447796</system-memory-active> <system-memory-active-percent>15%</system-memory-active-percent> <system-memory-inactive>2101128</system-memory-inactive> <system-memory-inactive-percent>13%</system-memory-inactive-percent> <system-memory-free>9327316</system-memory-free> <system-memory-free-percent>57%</system-memory-free-percent> <system-memory-buffer>314516</system-memory-buffer> <system-memory-buffer-percent>1%</system-memory-buffer-percent> <system-memory-swap>2598948</system-memory-swap> <system-memory-swap-percent>16%</system-memory-swap-percent> </system-memory-summary-information> <pmap-terse-information xmlns="http://xml.juniper.net/fbsd10/14.2I0/junos-pmap"> <pmap-terse-summary junos:style="pmap-process-terse-summary"> <pid>1</pid> <process-name>/lib/systemd/systemd</process-name> <size>159116</size> <size-percent>0</size-percent> <resident>8408</resident> <resident-percent>0</resident-percent> </pmap-terse-summary> ... </pmap-terse-information> </system-memory-information> </multi-routing-engine-item> <multi-routing-engine-item> <re-name>re0</re-name> <system-memory-information> <system-memory-summary-information> <system-memory-total>16125576</system-memory-total> <system-memory-total-percent>100%</system-memory-total-percent> <system-memory-used>6912492</system-memory-used> <system-memory-used-percent>42%</system-memory-used-percent> <system-memory-active>4936580</system-memory-active> <system-memory-active-percent>30%</system-memory-active-percent> <system-memory-inactive>8939976</system-memory-inactive> <system-memory-inactive-percent>55%</system-memory-inactive-percent> <system-memory-free>170744</system-memory-free> <system-memory-free-percent>1%</system-memory-free-percent> <system-memory-buffer>524676</system-memory-buffer> <system-memory-buffer-percent>3%</system-memory-buffer-percent> <system-memory-swap>8517664</system-memory-swap> <system-memory-swap-percent>52%</system-memory-swap-percent> </system-memory-summary-information> <pmap-terse-information xmlns="http://xml.juniper.net/fbsd10/14.2I0/junos-pmap"> <pmap-terse-summary junos:style="pmap-process-terse-summary"> <pid>1</pid> <process-name>/sbin/init</process-name> <size>162220</size> <size-percent>0</size-percent> <resident>10780</resident> <resident-percent>0</resident-percent> </pmap-terse-summary> ... </pmap-terse-information> </system-memory-information> </multi-routing-engine-item> ... </multi-routing-engine-results>
show system processes
On certain platforms running Junos OS Evolved Release 20.3R1 or earlier, the XML output for the show system processes
command and the show system processes wide
command is the CLI output enclosed in an <output>
element. Starting in Junos OS Evolved Release 20.4R1, the XML output matches the Junos OS XML output.
show system processes (Junos OS)
user@host> show system processes | display xml | no-more <rpc-reply xmlns:junos="http://xml.juniper.net/junos/20.1R0/junos"> <system-process-information junos:style="brief"> <process-information> <process> <pid>0</pid> <terminal-name>- </terminal-name> <state>DLs</state> <cpu-time>8:39.74</cpu-time> <command>[kernel]</command> </process> <process> <pid>1</pid> <terminal-name>- </terminal-name> <state>ILs</state> <cpu-time>0:00.25</cpu-time> <command>/sbin/init --</command> </process> ... </process-information> </system-process-information> <cli> </banner> </cli> </rpc-reply>
show system processes (Junos OS Evolved)
user@host> show system processes | display xml | no-more <rpc-reply xmlns:junos="http://xml.juniper.net/junos/20.2I0/junos"> <output> ------------------------------- node: re0 ------------------------------- UID PID PPID C SZ RSS PSR STIME TTY TIME CMD root 1 0 0 9947 2732 1 Apr10 ? 00:00:22 /sbin/init --dump-core root 2 0 0 0 0 5 Apr10 ? 00:00:00 [kthreadd] root 3 2 0 0 0 0 Apr10 ? 00:00:20 [ksoftirqd/0] root 5 2 0 0 0 0 Apr10 ? 00:00:00 [kworker/0:0H] root 7 2 0 0 0 5 Apr10 ? 00:04:20 [rcu_preempt] ... </output> <cli> </banner> </cli> </rpc-reply>
show system processes wide (Junos OS)
user@host> show system processes wide | display xml | no-more <rpc-reply xmlns:junos="http://xml.juniper.net/junos/20.1R0/junos"> <system-process-information junos:style="brief"> <process-information> <process> <pid>0</pid> <terminal-name>- </terminal-name> <state>DLs</state> <cpu-time>8:39.86</cpu-time> <command>[kernel]</command> </process> <process> <pid>1</pid> <terminal-name>- </terminal-name> <state>ILs</state> <cpu-time>0:00.25</cpu-time> <command>/sbin/init --</command> </process> ... </process-information> </system-process-information> <cli> </banner> </cli> </rpc-reply>
show system processes wide (Junos OS Evolved)
user@host> show system processes wide | display xml | no-more <rpc-reply xmlns:junos="http://xml.juniper.net/junos/20.2I0/junos"> <output> ------------------------------- node: re0 ------------------------------- UID PID PPID C SZ RSS PSR STIME TTY TIME CMD root 1 0 0 9947 2732 0 Apr10 ? 00:00:22 /sbin/init --dump-core root 2 0 0 0 0 5 Apr10 ? 00:00:00 [kthreadd] root 3 2 0 0 0 0 Apr10 ? 00:00:20 [ksoftirqd/0] root 5 2 0 0 0 0 Apr10 ? 00:00:00 [kworker/0:0H] root 7 2 0 0 0 0 Apr10 ? 00:04:20 [rcu_preempt] ... </output> <cli> </banner> </cli> </rpc-reply>