How Junos OS Evolved Differs from Junos OS

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.

Junos OS Evolved does not support the following options at the [edit system login retry-options] hierarchy level:

• backoff-threshold

• backoff-factor

• maximum-time

• minimum-time

• tries-before-disconnect

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.

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.

In Junos OS Evolved, when you configure a parent interface for Aggregated Ethernet with the [set interfaces interface-name ether-options 802.3ad ae-name] statement, any secondary (child) interface configurations made from the [edit interfaces interface-name] hierarchy will not take effect until the interface has been committed to the named Aggregated Ethernet (ae) interface. This applies to both ether-options and gigether-options.

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.

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.

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.

In Junos OS Evolved, the output for show system switchover displays entries for Object database and Applications' ready state. Junos OS Evolved uses an application-based architecture.

Junos OS output for show system switchover displays an entry for

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

You must set up the password-less login between two devices to use the jcs:open extension 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.

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

If you execute the sysctl() extension function in a script and request an invalid sysctl variable name, Junos OS Evolved generates a sysctl error: No such file or directory error.

If you execute the sysctl() extension function in a script and request an invalid sysctl variable name, Junos OS does not generate any error.

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.

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 alternate-format statement at the [edit system syslog] hierarchy level to attach the node name to the process name instead of the hostname. This alternate format allows monitoring systems to identify the hostname correctly.

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

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

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.

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

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.

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 software and configuration and saves it to the /packages/sets directory.

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.

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

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.

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.

In Junos OS Evolved, hostnames cannot be configured with an underscore as part of the hostname.

You can configure the hostname at the [edit system] hierarchy level.

In Junos OS, hostnames can be configured with any combination of alphabetic characters, numbers, dashes, and underscores. Special Characters cannot be used.

You can configure the hostname at the [edit system] hierarchy level.

In Junos OS Evolved, the request system reboot command reboots the entire system (all nodes) at once.

To reboot a specific node, use the request node reboot command.

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.

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.

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.

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

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

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.

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 (like kill -9 rpi_pid from the Linux shell). Commands like restart routing within the CLI do NOT trigger a switchover.

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 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 (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 using the command line interface.

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

[edit chassis fabric event reachability-fault degraded error-threshold percentage]

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

[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 and IPv6 traffic (including link-local addresses) 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 and SNMP traps only

• Unauthenticated mode only

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

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

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

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

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

[edit security host-vpn remote]

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

Increase the memory space available for the 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.

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 services monitoring twamp server control-connection

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

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.

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

request services monitoring twamp client

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

request system application restart

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

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 software sync (all-versions | current | rollback)

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.

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

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

Display the version of IPsec being used in the system.

show services monitoring rpm history-results

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

show services monitoring rpm probe-results

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

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 probe-results

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

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 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 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 test-info

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

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

Display information about active applications on the system.

show system errors

Display information about faults in the system.

show system errors history

Display information about faults in the system that have been cleared.

View a list of all nodes in the system.

show system software add-restart

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

show system software list

Display the installed versions on all nodes in the system.

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 jtd

Displays system jtd 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 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 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.

[edit chassis error minor action]

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

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

[set forwarding options enhanced-hash-key]

The vxlan configuration options are not supported.

[edit instance-type mac-vrf protocols evpn]

In Junos OS Evolved, instance-type mac-vrf protocols evpn is configured instead of instance-type evpn as in Junos OS.

[edit instance-type virtual-switch protocols vpls]

In Junos OS Evolved, instance-type virtual-switch protocols vpls is configured instead of instance-type vpls as in Junos OS.

[edit interfaces interface-name ether-options]

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

• fec

• loopback-remote

[edit interfaces aggregated-interface-name aggregated-ether-options lacp]

The following options for this command are not supported:

• accept-data

• link-protection

• no-peer-loopback-validation

[edit services monitoring twamp client control-connection test-session offload-type]

In Junos OS Evolved, the option inline-timestamping is configured instead of the hardware-timestamping option as in Junos OS.

In Junos OS Evolved, the following options are not supported:

• gre-path-mtu-discovery

• icmpv4-rate-limit

• icmpv6-rate-limit

• ipip-path-mtu-discovery

• ipv6-path-mtu-discovery-timeout

• no-gre-path-mtu-discovery

• no-ipip-path-mtu-discovery

• no-ipv6-path-mtu-discovery

• no-ipv6-reject-zero-hop-limit

• no-source-quench

• no-tcp-reset

• no-tcp-rfc1323

• no-tcp-rfc1323-paws

• source-port

• source-quench

• tcp-drop-synfin-set

host other-routing-engine

In Junos OS Evolved, the host other-routing-engine statement is not available.

Junos OS Evolved does not support the following options:

• fast-synchronize

• peers

• peer-synchronize

• commit-synchronize-server

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.

ping

Junos OS Evolved does not support the following ping command options:

• detail

• logical-system

• loose-source

• mac-address

• strict

• strict-source

• vpls

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 system software add

The following request system software add command options are not applicable in Junos OS Evolved:

• 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-on-host

• validate-on-routing-engine

request system software delete

The following request system software delete command options are not applicable in Junos OS Evolved:

• chassis

• lcc

• member

• re-choice

• scc

• sfc

• upgrade-group

• unlink

• validate

• validate-on-host

• validate-on-routing-engine

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 not applicable in Junos OS Evolved:

• device-alias

• satellite

• satellite-arg

• upgrade-group

request system software validate

The following request system software validate command options are not applicable in Junos OS Evolved:

• chassis

• lcc

• member

• package-options

• scc

• sfc

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 not applicable in Junos OS Evolved:

• re0

• re1

• routing-engine

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

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

request system zeroize

The local option is removed. The command will reboot all Routing Engines on the local chassis when you issue the command.

show agent sensors

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

show chassis fabric summary

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

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

show firewall

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

show host

The routing-instance mgmt_junos option is introduced.

show system

The nodes and node-attributes options are introduced.

show system connections

The node option is introduced.

Junos OS Evolved does not support the following show system connections command options:.

• extensive

• show-routing-instance

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

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

show chassis routing-engine errors

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

show system memory

The node option is introduced.

show system processes

The following show system processes command options are not applicable in Junos OS Evolved:

• health

• resource-limits

show system storage

The node option is introduced.

The invoke-on option is removed.

show system virtual-memory

The node option is introduced.

show version

The node option is introduced.

Junos OS Evolved does not support the following ssh command options:

• interface

telnet

Junos OS Evolved does not support the following telnet command options:

• bypass-routing

• interface

• logical-system

• no-resolve

• source

traceroute

Junos OS Evolved does not support the following traceroute command options:

• interface

• logical-system

• next-hop

• port

• propagate-ttl

clear interfaces statistics

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

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.

request system snapshot

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

request system software add

request system software delete

Output displays the version instead of the package.

request system software rollback

Output displays the version instead of the package.

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 fpc

Displays different output.

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

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

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 extensive

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

Output displays zero for all loopback interface (lo0) statistics.

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 interface-name ifl-class

show multicast route extensive

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

show multicast usage

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

show snmp mib get

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

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

Output displays the information per node, and the System memory usage distribution displays only the total, active, inactive, and free 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 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 tcp

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

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 task replication

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

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.

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.

[edit forwarding-options analyzer]

[edit forwarding-options enhanced-hash-key ecmp-dlb ether-type]

[edit forwarding-options enhanced-hash-key lag-dlb ether-type]

[edit system services extension-service notification]

[set chassis fabric degraded action-on-non-blackhole-degradation percentage]

[set chassis fabric degraded action-on-per-plane-fpc-degradation percentage]

gigether-options

request chassis beacon service-node

request system core-dump

request system recover

request system scripts (delete | rollback)

request system software abort

request system software (add | delete) set

request system software in-service-upgrade

request system software set

request system storage user-disk

show bridge

show chassis fabric unreachability

show chassis memory-usage-chassisd

show chassis network-services

show chassis routing-engine errors

show class-of-service forwarding-table

show database-replication

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

show interfaces mac-database

show interfaces mc-ae

show system buffers

show system software detail

show system uptime invoke-on

traceoptions