What's Changed
Learn about what changed in this release for ACX Series routers.
EVPN
-
New enhancement "udp source port" introduced in Junos OS Release 22.4R1 for overlay ping and traceroute-- In Junos OS releases prior to 22.4R1, you could not configure the udp source port in a ping overlay or traceroute overlay operation. You may now configure this value in an EVPN-VXLAN environment using
hash
. The configuration optionhash
will override any other hash-* options that may be used to determine the source port value.
Infrastructure
-
Label-switched interface (LSI) delay during reboot (ACX Series)—Rebooting ACX Series routers running Junos OS Evolved with a class-of-service routing-instance configuration might encounter errors due to a delay with the label-switched interface (LSI). LSI state information has been added to the output of the
show route instance
command to assist in the analysis of such errors.[See show route instance..]
General Routing
-
Label-switched interface (LSI) delay during reboot (ACX Series)—Rebooting ACX Series routers running Junos OS Evolved with a class-of-service routing-instance configuration might encounter errors due to a delay with the label-switched interface (LSI). LSI state information has been added to the output of the <cli>show route instance</cli> command to assist in the analysis of such errors.
[See show route instance. ]
-
When subscribing to the resource path /junos/system/linecard/environment, the prefix for the streamed path at the collector side was displaying as /junos/linecard/environment. This issue is resolved in Junos OS 23.1R1 and Junos OS Evolved 23.1R1 and the subscription path and the streamed path match to display /junos/system/linecard/ environment.
-
XML tag in the
get-system-yang-packages
RPC reply changed (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—Theget-system-yang-packages
RPC reply replaces thexmlproxy-yang-modules
tag with theproxy-xml-yang-modules
tag in the XML output. -
Before this change the output of a
show task replication logical-system all | display xml validate
command reported an error. After the change the output is correctly formatted with a "logical-system" root tag and no validation error occurs. -
The Ethernet link fault management process (lfmd) runs only when the link-fault-management protocol is configured.
-
The connectivity fault management process (cfmd) runs only when the ethernet connectivity-fault-management protocol is configured.
-
Label for the hours unit of time displayed in output—When there are zero minutes in the output for the
show system uptime
command, the label for the hours unit of time is displayed.[See show system uptime.]
-
The active-user-count is defined as a numeric integer value in ODL request output] -- The output for the get-system-uptime-information ODL request contains information for the active-user-count. The active-user-count is now defined as a numeric integer value and avoids an invalid value type error.
[See show system uptime.]
-
Data diagnostic sampling interval (ACX7100-32C and ACX7100-48L)-Data diagnostic sampling is essential for performance monitoring and should occur every 1 second. However, on the ACX7100-32C and ACX7100-48L platforms, the sampling interval is 4 seconds instead of 1 second.
Junos XML API and Scripting
-
The
xmlns:junos
attribute includes the complete software version string (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—Thexmlns:junos
namespace string in XML RPC replies includes the complete software version release number, which is identical to the version emitted by theshow version
command. In earlier releases, thexmlns:junos
string includes only partial software version information.
MPLS
-
Change in display of affinity constraints to hexadecimal values (MX10004, ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10004, PTX10008, and PTX10016)-Starting in Junos OS release 22.4R1 and Junos Evolved Release 22.4R1, in the output of the
show ted spring-te-policy extensive
operational command, the affinity constraints will be displayed in hexadecimal format instead of decimal.
Network Management and Monitoring
-
Changes to the
show system yang package
(get-system-yang-packages
RPC) XML output (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—Theshow system yang package
command and<get-system-yang-packages>
RPC include the following changes to the XML output:-
The root element is
yang-package-information
instead ofyang-pkgs-info
. -
A
yang-package
element encloses each set of package files. -
The
yang-pkg-id
tag is renamed topackage-id
. -
If the package does not contain translation scripts, the Translation Script(s) (
trans-scripts
) value isnone
.
-
-
NETCONF server's
<rpc-error>
response changed when<load-configuration>
usesoperation="delete"
to delete a nonexistent configuration object (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—In an earlier release, we changed the NETCONF server's<rpc-error>
response for when an<edit-config>
or<load-configuration>
operation usesoperation="delete"
to delete a configuration element that is absent in the target configuration. We've reverted the changes to the<load-configuration>
response. -
Changes to the RPC response for
<validate>
operations in RFC-compliant NETCONF sessions (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—When you configure therfc-compliant
statement at the[edit system services netconf]
hierarchy level, the NETCONF server emits only an<ok/>
or<rpc-error>
element in response to<validate>
operations. In earlier releases, the RPC reply also includes the<commit-results>
element. -
operator
login class is restricted from viewing NETCONF trace files that areno-world-readable
(ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)--When you configure NETCONF tracing options at the[edit system services netconf traceoptions]
hierarchy level and you restrict file access to the file owner by setting or omitting theno-world-readable
statement (the default), users assigned to theoperator
login class do not have permissions to view the trace file. -
Support for the
junos:cli-feature
YANG extension (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—Thecli-feature
YANG extension identifies certain CLI properties associated with some command options and configuration statements. The Junos YANG modules that define the configuration or RPCs include thecli-feature
extension statement, where appropriate, in schemas emitted with extensions. This extension is beneficial when a client consumes YANG data models, but for certain workflows, the client needs to generate CLI-based tools.
Platform and Infrastructure
-
The
ping host | display xml validate
command validates XML without error (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, and vMX)-- In Junos OS and Junos OS Evolved releases prior to 22.4R2, theping host | display xml validate
command results in CRITICAL ERROR: Root tag name mismatch. Expected 'ping-results', got 'run-command'. The command now validates the XML successfully without error.[See ping.]
-
Prior to this change the output of the
show isis statistics interface <interface_name> | display xml
command used the XML tag "interface-name", which generated an error. With the change the XML output uses the tag "isis-interface-name". -
In Junos OS Evolved platforms,
show route snooping
andshow route forwarding-table
does not show /56 routes in the VPLS address family table.
Software Installation and Upgrade
-
New options for the
request system snapshot
command (ACX Series, EX Series, MX Series, QFX Series, and SRX Series)—Therequest system snapshot
command includes new options for non-recovery snapshots. You can include thename
option to specify a user-defined name for the snapshot, and you can include theconfiguration
orno-configuration
option to include or exclude configuration files in the snapshot. By default, the snapshot saves the configuration files, which include the contents of the /config and /var directories and certain SSH files.[See request system snapshot (Junos OS with Upgraded FreeBSD).]
User Interface and Configuration
-
The
xmlns:junos
attribute includes the complete software version string (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX and vSRX)--Thexmlns:junos
namespace string in XML RPC replies includes the complete software version release number, which is identical to the version emitted by theshow version
command. In earlier releases, thexmlns:junos
string includes only partial software version information.