- Cover Page
- Key Features in Junos OS Release 22.4
- 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
- Class of Service
- EVPN
- Flow-based and Packet-based Processing
- High Availability
- Interfaces
- Junos Telemetry Interface
- Layer 2 VPN
- Licensing
- MPLS
- Network Address Translation (NAT)
- Network Management and Monitoring
- OpenConfig
- Precision Time Protocol (PTP)
- Routing Protocols
- Services Applications
- Software Installation and Upgrade
- Source Packet Routing in Networking (SPRING) or Segment Routing
- 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.
EVPN
Flow-label configuration status for EVPN ELAN services. The output for the
show evpn instance extensive
command now displays the flow-label and flow-label-static operational status for a device and not for the routing instances. A device withflow-label
enabled supports flow-aware transport (FAT) flow labels and advertises its support to its neighbors. A device withflow-label-static
enabled supports FAT flow labels but does not advertise its capabilities.
Network Management and Monitoring
Junos YANG modules for RPCs include the
junos:command
extension statement (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The Junos YANG modules that define RPCs for operational mode commands include thejunos:command
extension statement in schemas emitted with extensions. The statement defines the CLI command for the corresponding RPC. The Juniperyang
GitHub repository stores the RPC schemas with extensions in therpc-with-extensions
directory for the given release and device family. Additionally, when you configure theemit-extensions
statement at the[edit system services netconf yang-modules]
hierarchy level and generate the YANG schemas on the local device, the YANG modules for RPCs include thejunos:command
extension statement.
User Interface and Configuration
Changes to the JSON encoding of configuration data for YANG leaf nodes of type identityref (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—If a YANG leaf node is type identityref, Junos devices emit the namespace-qualified form of the identity in the JSON encoding of that node. In addition, Junos devices accept both the simple (no namespace) and the namespace-qualified form of an identity in JSON configuration data. In earlier releases, Junos devices only emit and accept the simple form of an identity. Emitting and accepting the namespace-qualified identity ensures that the device can properly resolve the value in the event that the YANG data model defines an identity and a leaf node containing the identifyref value in different modules.
The
file copy
command supports only text-formatted output in the CLI (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—Thefile copy
command does not emit output when the operation is successful and supports only text-formatted output when an error occurs. Thefile copy
command does not support using the| display xml
filter or the| display json
filter to display command output in XML or JSON format in any release. We've removed these options from the CLI.