- Key Features in Junos OS Release 22.2
- play_arrow Junos OS Release Notes for ACX Series
- play_arrow Junos OS Release Notes for cRPD
- play_arrow Junos OS Release Notes for cSRX
- play_arrow Junos OS Release Notes for EX Series
- play_arrow Junos OS Release Notes for JRR Series
- play_arrow Junos OS Release Notes for MX Series
- play_arrow What's New
- play_arrow What's New in 22.2R1-S2
- play_arrow What's New in 22.2R1
- EVPN
- High Availability
- Interfaces
- IP Tunneling
- Junos Telemetry Interface
- Licensing
- MACsec
- MPLS
- Platform and Infrastructure
- Precision Time Protocol (PTP)
- Routing Policy and Firewall Filters
- Routing Protocols
- Routing Policy and Firewall Filters
- Source Packet Routing in Networking (SPRING) or Segment Routing
- Software Installation and Upgrade
- Subscriber Management and Services
- VPNs
- Additional Features
- What’s Changed
- Known Limitations
- Open Issues
- Resolved Issues
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for NFX Series
- play_arrow Junos OS Release Notes for PTX Series
- play_arrow Junos OS Release Notes for QFX Series
- play_arrow Junos OS Release Notes for SRX Series
- play_arrow Junos OS Release Notes for vRR
- play_arrow Junos OS Release Notes for vSRX
- Licensing
- Finding More Information
- Requesting Technical Support
- Revision History
What’s Changed
Learn about what changed in this release for vMX.
Authentication and Access Control
SHA-1 password format deprecated (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX and vSRX)—We've removed the
sha1
option at the[edit system login password format]
hierarchy level because SHA-1 is no longer supported for plain-text password encryption.
General Routing
The
<request-system-zeroize/>
RPC response indicates when the device successfully initiates the requested operation (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When the<request-system-zeroize/>
RPC successfully initiates the zeroize operation, the device emits the<system-zeroize-status>zeroizing re0</system-zeroize-status>
response tag to indicate that the process has started. If the device fails to initiate the zeroize operation, the device does not emit the<system-zeroize-status>
response tag.Instance type change is not permitted from default to L3VRF in open configuration (ACX Series, EX Series, MX Series, QFX Series, SRX Series, vMX, and vSRX)—DEFAULT_INSTANCE is the primary instance that runs when there is no specific instance type configured in the route
set routing-options
. Any instance you explicitly configure is translated intoset routing-instance r1 routing-options
. The issue appears in translation, when you change instance type DEFAULT_INSTANCE (any instance to DEFAULT_INSTANCE) to L3VRF or L3VRF to DEFAULT_INSTANCE. As a result, such changes are not permitted. Additionally, DEFAULT_INSTANCE can only be named DEFAULT, and DEFAULT is reserved for DEFAULT_INSTANCE, therefore allowing no such changes.
Network Management and Monitoring
DES deprecation for SNMPv3—The Data Encryption Standard (DES) privacy protocol for SNMPv3 is deprecated due to weak security and vulnerability to cryptographic attacks. For enhanced security, configure the triple Data Encryption Standard (3DES) or the Advanced Encryption Standard (CFB128-AES-128 Privacy Protocol) as the encryption algorithm for SNMPv3 users.
[See privacy-3des and privacy-aes128.]
Changes when deactivating or deleting instances of the ephemeral configuration database (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The following changes apply when you deactivate or delete ephemeral database instances in the static configuration database:
When you deactivate the entire
[edit system configuration-database ephemeral]
hierarchy level, the device deletes the files and corresponding configuration data for all user-defined ephemeral instances. In earlier releases, the files and configuration data are preserved; however, the configuration data is not merged with the static configuration database.When you delete an ephemeral instance in the static configuration database, the instance's configuration files are also deleted. In earlier releases, the configuration files are preserved.
You can delete the files and corresponding configuration data for the default ephemeral database instance by configuring the
delete-ephemeral-default
statement in conjunction with theignore-ephemeral-default
statement at the[edit system configuration-database ephemeral
hierarchy level.[See Enable and Configure Instances of the Ephemeral Configuration Database.]
Changes to the NETCONF
<edit-config>
RPC response (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When the<edit-config>
operation returns an error, the NETCONF server does not emit a<load-error-count>
element in the RPC response. In earlier releases, the<edit-config>
RPC response includes the<load-error-count>
element when the operation fails.
User Interface and Configuration
Load JSON configuration data with unordered list entries (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The Junos schema requires that list keys precede any other siblings within a list entry and appear in the order specified by the schema. Junos devices provide two options to load JSON configuration data that contains unordered list entries:
Use the
request system convert-json-configuration
operational mode command to produce JSON configuration data with ordered list entries before loading the data on the device.Configure the
reorder-list-keys
statement at the[edit system configuration input format json]
hierarchy level. After you configure the statement, you can load JSON configuration data with unordered list entries, and the device reorders the list keys as required by the Junos schema during the load operation.When you configure the
reorder-list-keys
statement, the load operation can take significantly longer to parse the configuration, depending on the size of the configuration and number of lists. Therefore, for large configurations or configurations with many lists, we recommend using therequest system convert-json-configuration
command instead of thereorder-list-keys
statement.Junos XML protocol Perl modules deprecated (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—We no longer provide the Junos XML protocol Perl client for download. To use Perl to manage Junos devices, use the NETCONF Perl library instead.
[See Understanding the NETCONF Perl Client and Sample Scripts..]