What's Changed
Learn about what changed in this release for vMX.
Junos XML API and Scripting
-
The
xmlns:junosattribute includes the complete software version string (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—Thexmlns:junosnamespace string in XML RPC replies includes the complete software version release number, which is identical to the version emitted by theshow versioncommand. In earlier releases, thexmlns:junosstring includes only partial software version information.
Network Management and Monitoring
-
Changes to the
show system yang package(get-system-yang-packagesRPC) XML output (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—Theshow system yang packagecommand and<get-system-yang-packages>RPC include the following changes to the XML output:-
The root element is
yang-package-informationinstead ofyang-pkgs-info. -
A
yang-packageelement encloses each set of package files. -
The
yang-pkg-idtag 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-compliantstatement 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.