Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

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. 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.

Table 1: How Junos OS Evolved Behavior Differs from Junos OS

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.

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

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.

Understanding Management Ethernet Interfaces

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.

Aggregated Ethernet Interfaces

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 set interfaces interface ether-options 802.3ad aex at the same time as you apply a second configuration to the same interface at the [edit interfaces interface] hierarchy, the second configuration will not take effect until the interface joins the aggregated Ethernet interface aex. This is also true for gigether-options, when supported.

In Junos OS, configurations for aggregated Ethernet interfaces and non-aggregated Ethernet interfaces at the [edit interfaces interface] hierarchy are independent of configurations at the [edit interfaces interface ether-options] and [edit interfaces interface gigether-options] hierarchies and will be effective when applied.

ether-options, gigether-options

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.

fec (ether)

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

(Only for QFX5220-32CD switches) In-Service Software Upgrade (ISSU) is performed by using the request system software add restart command.

ISSU is performed by using the request system software in-service-upgrade command.

request system software add restart

Junos XML API and Scripting

You must set up the password-less login between two devices to use the jcs:open function in SLAX or XSLT scripts to open a connection to the local or remote device.

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.

open() Function (SLAX and XSLT)

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.

Event Policies and Event Notifications Overview

For op scripts run with the max-datasize configuration statement configured for the minimum memory, an error occurs. In Junos OS Evolved, the error is "Out of memory."

For op scripts run with the max-datasize configuration statement configured for the minimum memory, an error occurs. In Junos OS, the error is "Memory allocation failed."

max-datasize

Junos OS Evolved stores the trace data for all scripts under the cscript application. The trace log includes data for commit, event, op, and SNMP scripts; YANG action and translation scripts; and Juniper Extension Toolkit scripts. You can modify the default trace settings for all scripts by configuring statements at the [edit system trace application cscript] hierarchy.

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 traceoptions statement at the hierarchy level for that script type.

Trace Script Processing on Devices Running Junos OS Evolved

Messaging
TIP: You can compare syslog messages in a Junos OS release to a Junos OS Evolved release using the System Log Explorer.  

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.

Displaying System Log Files

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 [edit system syslog host ip-address] hierarchy, you only need to configure the management-instance statement to use the mgmt_junos routing instance. You do not need to configure the mgmt_junos routing instance at the [edit system syslog host ip-address routing-instance] hierarchy.

Configure the mgmt_junos routing instance at the [edit system syslog host ip-address routing-instance] hierarchy if you want to send syslog messages to a remote host that is identified by its IP address at the [edit system syslog host ip-address] hierarchy.

routing-instance

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

Routing Policy and Firewall Filters

When you issue the show firewall filter ? command, the names of the firewall filters are listed. The names of the Flowspec filters are not listed. To see the names of the configured Flowspec filters, use the show firewall application routing command.

When you issue the show firewall filter ? command, you see not only the names of the firewall filters listed but also the names of the configured Flowspec filters. The Flowspec filters show up inside underscores.

show firewall

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.

Stateless Firewall Filter Overview

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 set firewall family inet6 filter filter-name term term-name from packet-length packet-length correctly, you need to specify the packet-length parameter without the IPv6 header size included.

When you use an IPv6 filter with packet length matching, the match length parameter includes the IPv6 header size.

Parameterized Filter Match Conditions for IPv6 Traffic

In Junos OS Evolved Release 22.1R1, the backoff-threshold, backoff-factor, maximum-time, minimum-time, and tries-before-disconnect options are not supported at [edit system login retry-options] hierarchy.

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.

retry-options

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 request system snapshot command takes a snapshot of the files currently used to run the device and copies all of these files onto an alternate solid-state drive. The snapshot includes the complete contents of the /soft, /config, and /root directories, copies of user data, and content from the /var directory (except the /var/core, /var/external, /var/log, and /var/tmp directories).

The request system snapshot command takes a snapshot of the contents of the root (/) and /config file systems.

request system snapshot (Junos OS Evolved)

Software Installation and Upgrade Overview (Junos OS Evolved)

The request system storage cleanup command does not remove Junos OS Evolved images from the device after Release 20.1R1. It removes all core files, log files from /var/log/, and all /var/log/* files. To remove old images from the device, use the request system software delete command.

The request system storage cleanup command removes all Junos OS images from the device, including old images and the currently installed image, as well as core files from /var/crash, log files from /var/log/, and certain other files from /var/tmp.

request system storage cleanup (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:

  • /var/log/dhcp_logfile

  • /var/log/event-script.log

  • /var/log/image_load_log

  • /var/log/messages

  • /var/log/op-script.log

  • /var/log/script_output

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
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 show trace application application-name node node-name command to read and decode trace messages stored in the trace files. You can modify trace options for specific applications at the [edit system trace application] hierarchy level. However, a few applications still use the traceoptions statement.

Configure traceoptions to enable trace logging for a specific process or protocol.

trace

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 show system core-dumps shows all cores generated.

For Junos OS, core files are stored in /var/crash or /var/tmp.

show system core dumps (Junos OS Evolved)

User Interface

Junos OS Evolved does not support the virtual-memory-mapping option.

The virtual-memory-mapping option of the configuration-database command defines parameters for using virtual memory mapping for the configuration database on a per-process basis.

configuration-database

The show system reboot command has options to Execute this command or Pipe through a command.

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.

show system reboot

In Junos OS Evolved, enabling the command set system switchover-on-routing-crash causes a routing engine mastership switchover to occur only on rpd crashes and any uncontrolled rpd exits from outside the CLI app (like kill -9 rpi_pid from the Linux shell). Commands like restart routing within the CLI app do NOT trigger a switchover.

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.

switchover-on-routing-crash

In Junos OS Evolved, when set system processes routing failover other-routing-engine is configured, repeating commands like restart routing and restart routing immediatelywithin the CLI app will not cause a routing engine mastership switchover when entered more than 4 times in 30 seconds. However, repeated uncontrolled exits (more than 3 times in 5 minutes) from outside the CLI app (like rpd crash -9 and rpd kill -15) from the Linux shell will cause rpd to fail and trigger a switchover. If this happens, you must restart the app via the command line interface.

Junos OS triggers a switchover when edit system processes routing failover other-routing-engine is configured and certain commands such as restart routingand restart routing immediately are used many times in short succession.

failover (System Process)

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).

Recovering Root Password

The show system firmware command displays information based on the accessibility of the device, not the FRU state. The firmware information is cached so, even if the FRU is in a fault condition, the status from the show system firmware command appears as OK. The fault is visible with the commands show chassis alarms, show chassis fpc, and so on.

When the FRU is offline, the cached firmware information of the FRU is not available to view.

show system firmware

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.

Table 2: New CLI Statements and Commands (Junos OS Evolved)

Statement or Command

Description

Link

New Statements

[edit system extensions extension-service application file filename interpreter (bash | python | python3)]

You can use the configuration statement interpreter to specify that a device running Junos OS Evolved run a daemonized on-device JET application using Bash, Python, or Python 3.

file

[edit services monitoring twamp]

You can configure the TWAMP monitoring service on devices running Junos OS Evolved by using the hierarchy level [edit services monitoring twamp] . This service sends out probes to measure network performance. The support for this service is limited to the following:

  • IPv4 traffic only for control sessions and test sessions

  • Control session status and statistics

  • Test session operational management status and history

  • Test session probe generation and reception, as well as reflection

  • Timestamps set by the Routing Engine or the Packet Forwarding Engine

  • Error reporting through system log messages only

  • Unauthenticated mode only

Understanding Two-Way Active Measurement Protocol on Routers and twamp

[edit security host-vpn]

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 connections, ike-log, and ike-secrets statements at the [edit security host-vpn] hierarchy level to configure IKE and IPsec values.

Overview of IPsec and host-vpn

[edit security host-vpn connections]

You can configure the additional algorithms aes256-sha384-modp3072 and  aes256-gcm128-modp3072 at each of the following hierarchy levels:

  • [edit security host-vpn connections parent-connection-name ike-proposal]

  • [edit security host-vpn connections parent-connection-name children child-connection-name esp-proposal]

connections (Host VPN) and children

[edit security host-vpn connections children child-name]

Statements at this hierarchy level include local-traffic-selector, and remote-traffic-selector.

children

[edit security host-vpn connections dpd-delay]

Statement to support dead peer detection. The dead peer detection delay sends keepalives to find out if a peer has gone dead.

connections (Host VPN)

[edit security host-vpn remote]

Configure identity details for authenticating the remote device during IKE negotiations.

remote (Host VPN)

[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.

auto-sw-sync

[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.

configuration-database

[edit system trace application]

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 clear trace and show trace commands listed in the New Commands section of this table.

trace

New Commands

clear node reboot

Remove all pending node halt, reboot, and power-off requests.

clear security host-vpn security-associations

Clear host IPsec security association information. See also [edit security host-vpn] in the New Statements section of this table.

clear security host-vpn security-associations

clear services monitoring twamp server control-connection

Clear connections established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients.

clear services monitoring twamp server control-connection

clear trace

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 [edit system trace application] in the New Statements section of this table.

clear trace

request node (halt | offline | online | power-off/on | reboot) node-name

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)

request node power-on (Junos OS Evolved)

request node reboot (re0 | re1) (Junos OS Evolved)

request services monitoring twamp client

Start or stop a Two-Way Active Measurement Protocol (TWAMP) session.

request services monitoring twamp client

request system application restart

Stop and then start (restart) a specific process (for example, cmdd) on the node you specify.

request system application (Junos OS Evolved)

request system debug-info

Collect debug information from Junos OS Evolved, such as logs. The logs are stored in the /var/tmp/debug_collector_timestamp directory. Use the node option to collect information from a specific node.

request system debug-info

request system software sync (all-versions | current | rollback)

Synchronize software and configurations from the primary Routing Engine to the other nodes and reboot the other nodes.

request system software sync

request system software validate restart

The command performs a dry run of the request system software add restart command and displays the ISSU impact of the new restart option. See request system software add (Junos OS Evolved) for more on the restart option.

request system software validate (Junos OS Evolved)

restart app-name

The following message is logged when you use the restart command:

App restarting <app name>. Related apps that may be impacted - <related-app name>.

restart (Junos OS Evolved)

show chassis routing-engine hard-disk-test

Display the health of the hard disk with the hard-disk-test option. Use disk /dev/disk-name status argument to display the status of a particular disk.

show chassis routing-engine

show node reboot

Display any pending halt, reboot, or power-off requests on a node.

show node statistics

Display the network statistics of a node.

 

show security host-vpn security-associations

Display host IPsec security association information for a specific security association or for all connections. See also [edit security host-vpn] in the New Statements section of this table.

show security host-vpn security-associations

show security host-vpn version

Display the version of IPsec being used in the system.

show security host-vpn version

show services monitoring rpm history-results

Display the results stored for the specified real-time performance monitoring (RPM) probes.

show services monitoring rpm history-results

show services monitoring rpm probe-results

Display the results of the most recent real-time performance monitoring (RPM) probes.

show services monitoring rpm probe-results

show services monitoring twamp client history-results

Display standard information about the results of the last 50 probes for a Two-Way Active Measurement Protocol (TWAMP) control connection.

show services monitoring twamp client history-results

show services monitoring twamp client probe-results

Display the results of the most recent Two-Way Active Measurement Protocol (TWAMP) probes.

show services monitoring twamp client probe-results

show services monitoring twamp client control-info

Display information about the control connections established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients.

show services monitoring twamp client control-info

show services monitoring twamp client test-info

Display information about the test sessions established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients.

show services monitoring twamp client test-info

show services monitoring twamp server control-info

Display information about the control connections established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients for managed servers.

show services monitoring twamp server control-info

show services monitoring twamp server test-info

Display information about the test sessions established between the Two-Way Active Measurement Protocol (TWAMP) server and control clients.

show services monitoring twamp server test-info

show system applications (app app-name | brief | detail | node node-name)

Display information about active applications on the system.

show system applications (Junos OS Evolved)

show system errors

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.

show system errors

show system errors history

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 errors history

show system nodes

View a list of all nodes in the system.

show system nodes (Junos OS Evolved)

show system software add-restart

Display all console messages from the last in-service software upgrade (ISSU).

show system software add-restart (Junos OS Evolved)

show system software list

Display the installed versions on all nodes in the system.

show system software list

show system statistics backup

Displays system statistics options for the backup Routing Engine. The options provided are the same as the options for show system statistics.

show system statistics

show system statistics jtd

Displays system jtd statistics.

show system statistics

show system ztp

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.

show system ztp

show trace

Junos OS Evolved uses a new tracing infrastructure. This command shows the trace data from all nodes that are collected on the Routing Engine.

show trace

show forwarding-options enhanced-hash-key

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.

show forwarding-options enhanced-hash-key

show vlans

Junos OS Evolved replaces the show bridge command with the show vlans command. This command displays detailed information on the VLAN configurations present on the Routing Engine and includes the following options:

  • brief: Display brief output.

  • detail: Display detailed output.

  • extensive: Display extensive output.

  • instance: Display information for a specified instance.

  • interface: Name of interface for which to display table.

  • logical-system: Name of logical system, or 'all'.

  • operational: Show operational bridging instance.

show vlans

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.

Note:

For the CLI commands that produce changed output, see Table 4.

Table 3: Modified CLI Statements and Commands (Junos OS Evolved)

Statement or Command

Change in Junos OS Evolved

Link

Modified Statements

[edit chassis error minor action]

The offline and disable-pfe actions are not available for errors with minor severity.

error

[edit firewall family family-name filter filter-name]

Egress filters do not support gre-key matches.

promote gre-key

[edit firewall family ethernet-switching filter filter-name term term-name from ip-version ipv4 tcp-flags ack]

The tcp-flags match conditions have been moved into the ip-version ipv4 hierarchy along with other TCP-IP commands. You will need to replace from tcp-flags-ack with from ip-version ipv4 tcp-flags ack when configuring the filter.

Firewall Filter Match Conditions for IPv4 Traffic

ip-version

[edit interfaces interface-name ether-options]

The following options are added to the ether-options statement:

  • fec

  • loopback-remote

ether-options

[edit system login password]

The hash algorithm that authenticates the password is limited to the following format options: (sha256 | sha512).

password

Modified Commands

clear ipv6 neighbors

In Junos OS Evolved, issuing the clear ipv6 neighbors command clears the cache for IPv6 neighbors that are in a reachable state.

clear ipv6 neighbors

monitor traffic interface The write-file option for the monitor traffic interfacecommand 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

ping

The following options of the ping command are deprecated:

  • detail

  • logical-system

  • loose-source

  • mac-address

  • strict

  • strict-source

  • vpls

ping

request chassis routing-engine master switch

The default wait time on the PTX10008 between Routing Engine switchovers when using the request chassis routing-engine master switch command has increased from 120 seconds to 360 seconds.

request chassis routing-engine master

request system software add

The following options of the request system software add command are deprecated:

  • best-effort-load

  • both-routing-engines

  • chassis

  • device-alias

  • delay-restart

  • force-host

  • lcc

  • member

  • no-copy

  • on-primary

  • (re0 | re1)

  • re-choice

  • satellite

  • scc

  • set

  • sfc

  • upgrade-group

  • unlink

  • validate

  • validate_choice

  • validate-on-host

  • validate-on-routing-engine

request system software add (Junos OS Evolved)

request system software delete

The following options of the request system software delete command are deprecated:

  • chassis

  • lcc

  • member

  • re-choice

  • scc

  • sfc

  • upgrade-group

  • unlink

  • validate

  • validate_choice

  • validate-on-host

  • validate-on-routing-engine

request system software delete (Junos OS Evolved)

request system software rollback

The following options are added to the request system software rollback command:

  • (no-validate | validate)

  • with-old-snapshot-config

The following options are deprecated from the request system software rollback command:

  • device-alias

  • satellite

  • satellite-arg

  • upgrade-group

request system software rollback

request system software validate

The following options of the request system software validate command are deprecated:

  • chassis

  • lcc

  • member

  • package-options

  • scc

  • sfc

request system software validate (Junos OS Evolved)

request system storage cleanup

Use the new option force-deep to clean up all user-generated files.

The user is prompted to check the list of files to be deleted by using the dry-run option.

The following options are deprecated:

  • re0

  • re1

  • routing-engine

request system storage cleanup (Junos OS Evolved)

request security pki ca-certificate ca-profile-group load

The default option is not supported on PTX10003-80C, PTX10003-160C, and PTX10008 routers.

request security pki ca-certificate ca-profile-group load

set forwarding options enhanced-hash-key

The vxlan configuration options are not supported.

show forwarding-options enhanced-hash-key

show agent sensors

This command displays output on each Routing Engine, instead of just the primary Routing Engine.

show agent sensors

show chassis fabric summary

More detailed information is provided. The following fields are introduced:

  • Link Error
  • Link TF
  • Reachability Errors (Local/Remote)
  • Uptime

show chassis fabric summary

show firewall

The application lsp option allows you to specify the display of implicit policers that are published by rpd.

show firewall

show host

The routing-instance mgmt_junos option is introduced.

show host

show system

The nodes and node-attributes options are introduced.

show system nodes (Junos OS Evolved)

show system connections

The following options of the show system connections command are deprecated: extensive and show-routing-instance.

The node option is introduced.

show system connections

show system core-dumps

The node option is introduced. The core dump files generated on the nodes are stored in the /var/core/ directory.

show system core-dumps

show chassis errors

The error-id option is moved to the show system errors tree.

show system errors active

show chassis routing-engine errors

The output for this command is moved to show system errors.

show system errors active

show system memory

The node option is introduced.

show system memory

show system processes

The following options of the show system processes command are deprecated:

  • esc-node

  • health

  • resource-limits

show system processes

show system storage

The node option is introduced.

The invoke-on option is removed.

show system storage

show system virtual-memory

The node option is introduced.

show system virtual-memory

show version

The node option is introduced.

show version

telnet

The following options of the telnet command are deprecated:

  • bypass-routing

  • interface

  • logical-system

  • no-resolve

  • source

telnet

traceroute

The following options of the traceroute command are deprecated:

  • logical-system

  • monitor

  • next-hop

  • port

  • propogate-ttl

traceroute

Changed CLI Command Output (Junos OS Evolved)

For changes in output for Junos OS Evolved, see Table 4.

Table 4: Changed Command Output (Junos OS Evolved)

Command

Description of Change in Output

Link

clear interfaces statistics

Clears not only LACP statistics but also the counters displayed in the show lacp statistics interfaces command.

clear interfaces statistics

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

ping

When pinging a nonresponsive route, the display output of the ping command does not print the number of packets sent or received or the packet loss.

ping

ping hostname rapid

When you use the ping hostname rapid command in Junos OS Evolved, you will see an indicator .. for missing replies only. No indicator !! for received replies is displayed.

ping

request system snapshot

Output displays the names of the directory and the individual files being copied instead of only the directory names.

request system snapshot (Junos OS Evolved)

request system software add

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.

request system software add (Junos OS Evolved)

request system software delete

Output displays the version instead of the package.

request system software delete (Junos OS Evolved)

request system software rollback

Output displays the version instead of the package.

request system software rollback (Junos OS Evolved)

The show chassis environment cb command does not show the Bus and FPGA revision information. Use the show system firmware command in order to view the FPGA revision or version information for the CB.

Use the show chassis environment cb command to display environmental information about the Control Boards (CBs).

show chassis environment cb

show chassis environment fpc

Displays different output.

show chassis environment fpc

show interfaces aenumber extensive

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 show interfaces aenumber extensive command output.

show interfaces (Aggregated Ethernet)

show interfaces

Configuration of IPv6 over the re0:mgmt-* interfaces is supported.

show interfaces

show interfaces detail

Output displays the Last Flapped field with the value Never after a Routing Engine reboot. The Last Flapped field provides details of the date, time, and how long ago the interface went up. The value Never signifies that the interface never flapped.

show interfaces detail

show interfaces extensive

Output does not display the Packet Forwarding Engine configuration and CoS default bandwidth allocation information.

show interfaces

show interfaces interface-name statistics

Junos OS Evolved does not display statistics for an interface if it is a child of an aggregated ethernet (AE) interface.

show interfaces statistics

show interfaces interface-name ifl-class

Junos OS Evolved does not display statistics for an interface if it is a child of an aggregated ethernet (AE) interface.

show interfaces statistics

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

show multicast route extensive

Output displays the Sensor ID field that corresponds to a multicast route.

show multicast route

show multicast usage

Output displays the Sensor ID field that corresponds to a multicast route.

show multicast usage

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

show snmp mib get

Output for a Routing Engine displays the Routing Engine slot number, not the Routing Engine number.

show snmp mib

show snmp mib walk

The show snmp mib walk jnxFilledDescr output only shows the fan tray number. This output does not show the number of fan slots present in each tray.

show snmp mib

show system errors fru detail

Output displays status of FRUs including CB, chassis, fans, FPC, FPM, PDU, PICS, PSM, RE, and SIB, not just FPC.

show system errors fru

show system memory

Output displays the information per node, and the System memory usage distribution displays only the total, active, inactive, and free memory.

show system memory

show system snapshot

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.

show system snapshot (Junos OS Evolved)

show system statistics arp

After running ping on an unreachable host, output shows that counts for ARP requests received and for datagrams for an address not on the interface are incremented.

show system statistics arp

show system statistics tcp

Output for the show system statistics tcp command is trimmed to show only fields supported in Junos OS Evolved.

show system statistics tcp

show system uptime

In certain releases, the output displays only the System booted and System-wide users information and does not display information on current time, system booted, protocols started, or last configured parameters. The show system uptime node command shows the other information.

show system uptime

show task replication

Output displays the same state whether the command is run from the primary or the backup Routing Engine.

show task replication

show version

Output of the show version command is changed to clearly show which Junos architecture is running on the device.

Output of the show version node all command is revised to explicitly identify the Routing Engine in both the XML and CLI output.

show version (Junos OS Evolved)

traceroute

Output of the traceroute command displays MPLS data parsed in the same way as the Linux traceroute command: L=label, E=exp_use, S=stack_bottom, and T=TTL.

traceroute

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.

Table 5: Removed CLI Statements and Commands (Junos OS Evolved)

Statement or Command

Description

Removed Statements

gigether-options

The gigether-options statement at the [edit interfaces interface-name] hierarchy no longer appears because it is not needed. To configure link aggregation groups (LAG), use the set interfaces interface-nameether-options command instead.

edit system services extension-service notification

Junos OS Evolved does not support the notification service for JET applications.

traceoptions

Junos OS Evolved removes or does not support the traceoptions option at many hierarchy levels because trace messages are logged, viewed, and configured per application. However, routing protocols (the [edit protocols] hierarchy level) and a few other applications still use traceoptions.

Removed Commands

request chassis beacon service-node

This command is removed from Junos OS Evolved.

request system core-dump

This command is removed from Junos OS Evolved.

request system recover

This command is removed from Junos OS Evolved.

request system scripts (delete | rollback)

AI-Scripts and Service Now are not supported on Junos OS Evolved.

request system software abort

This command is removed because the request system software add command has a built-in feature not to start an upgrade if a reboot is pending after an upgrade or rollback.

request system software (add | delete) set

Junos OS Evolved bundles all packages into one single ISO file, so the set option serves no purpose in the request system software add and request system software delete commands.

request system software in-service-upgrade

Use the request system software add restart command for ISSU. The request system software add command has a built-in feature not to start upgrade if a reboot is pending after an upgrade or rollback.

request system software set

To set the current system to an installed software version, use the request system software rollback reboot command.

request system storage user-disk

There are no satellite packages in Junos OS Evolved.

show bridge

The command show bridge is replaced by the command show vlan in Junos OS Evolved.

show chassis fabric unreachability

See the show system errors command for similar functionality.

show chassis memory-usage-chassisd

The functionality for this command and all options under this command are moved to show system memory.

show chassis network-services

This command is not supported.

show chassis routing-engine errors

This command has been replaced by show system errors in Junos OS Evolved.

show class-of-service forwarding-table

The removed options include classifier, classifier mapping, drop-profile, policer, rewrite-rule, rewrite-rule mapping, scheduler-map, and shaper.

show database-replication

This command is not supported.

show firewall family inet filter filter-name term term-name then traffic-class-count

The traffic-class-count option is not supported under the firewall hierarchy in Junos OS Evolved.

show interfaces mac-database

This command is not supported.

show interfaces mc-ae

This command has been replaced with show multi-chassis mc-lag.

show system buffers

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.

show system software detail

Use show system software list to display a list of the software versions installed on all nodes. For more details about the software, use show version detail.

show system switchover

This command is not supported.

show system uptime invoke-on

This command is removed from Junos OS Evolved.

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)

request system storage cleanup (Junos OS Evolved)

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>

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)

show system processes (Junos OS Evolved)

show system processes wide (Junos OS)

show system processes wide (Junos OS Evolved)