What’s Changed
Learn about what changed in this release for vMX.
General Routing
-
Verified the qualification of
ordered-by-user
in the hierarchies (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—The requested hierarchies are reviewed and checked to confirm if they qualify for theordered-by-user
list type. If they do not, theflag autosort
is included in the DDL definition for the list, making itordered-by-system
. The hierarchies are now indexed. The benefits from this arrangement are we get accurate data modeling and optimized configuration load in the user interface infrastructure. -
In the past inet6flow.0 was not allowed to be a primary rib in a rib-group. Starting with Release 22.3 this is now allowed.
Junos XML API and Scripting
-
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.
Network Management and Monitoring
-
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.