- Introduction
- Cover Page
- play_arrow Junos OS Release Notes for ACX Series
- play_arrow Junos OS Release Notes for cPCE
- 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
- Hardware
- Authentication and Access Control
- Chassis
- Class of Service
- Dynamic Host Configuration Protocol
- EVPN
- Forwarding Options
- High Availability
- Interfaces
- Juniper Extension Toolkit (JET)
- Junos OS API and Scripting
- Junos Telemetry Interface
- MPLS
- Network Management and Monitoring
- Precision Time Protocol (PTP)
- Public Key Infrastructure (PKI)
- Routing Policy and Firewall Filters
- Routing Protocols
- Securing GTP and SCTP Traffic
- Serviceability
- Services Applications
- Source Packet Routing in Networking (SPRING) or Segment Routing
- Software Installation and Upgrade
- Subscriber Management and Services
- 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 What's New
- Hardware
- Application Identification (AppID)
- Chassis
- Flow-Based and Packet-Based Processing
- High Availability
- Interfaces
- Juniper Advanced Threat Prevention Cloud (ATP Cloud)
- Juniper Extension Toolkit (JET)
- J-Web
- Network Management and Monitoring
- Public Key Infrastructure (PKI)
- Serviceability
- Software Installation and Upgrade
- VPNs
- Additional Features
- What's Changed
- Known Limitations
- Open Issues
- Resolved Issues
- Migration, Upgrade, and Downgrade Instructions
- Documentation Updates
- 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 QFX Series Switches.
For all QFX5110 models, the standard name of the image has been changed from “5e” to “5x.” As follows:
Old format: jinstall-host-qfx-5e-
New format: jinstall-host-qfx-5x-
The new format is in effect starting with Junos OS 24.2R1 and will be used for all subsequent mainline Junos OS releases. No maintenance or service releases for release trains prior to 24.2 will implement the change.
EVPN
OISM SBD bit in EVPN Type 3 route multicast flags extended community—In EVPN Type 3 Inclusive Multicast Ethernet Tag (IMET) route advertisements for interfaces associated with the supplemental bridge domain (SBD) in an EVPN optimized intersubnet multicast (OISM) network, we now set the SBD bit in the multicast flags extended community. We set this bit for interoperability with other vendors, and to comply with the IETF draft standard for OISM, draft-ietf-bess-evpn-irb-mcast .
[See the description of the
show route table bgp.evpn.0 extensive
command in CLI Commands to Verify the OISM configuration.]New commit check for MAC-VRF routing instances with the encapsulate-inner-vlan statement configured— We introduced a new commit check that prevents you from configuring an IRB interface and the
encapsulate-inner-vlan
statement together in a MAC-VRF routing instance. Please correct or remove these configurations prior to upgrading to 23.2R2 or newer to avoid a configuration validation failure during the upgrade.[See encapsulate-inner-vlan.]
Default behavior changes and new options for the easy EVPN LAG configuration (EZ-LAG) feature—The easy EVPN LAG configuration feature now uses some new default or derived values, as follows:
Peer PE device
peer-id
value can only be 1 or 2.You are required to configure the loopback subnet addresses for each peer PE device using the new
loopback peer1-subnet
andloopback peer2-subnet
options at the [edit services evpn device-attribute
] hierarchy level. The commit script uses these values for each peer PE device's loopback subnet instead of deriving those values on each PE device. These replace theloopback-subnet
option at the [edit services evpn device-attribute
] hierarchy level, which has been deprecated.If you configure the
no-policy-and-routing-options-config
option, you must configure a policy statement calledEXPORT-LO0
that the default underlay configuration requires, or configure the newno-underlay-config
option and include your own underlay configuration.The commit script generates "notice" messages instead of "error" messages for configuration errors so you can better handle [
edit services evpn
] configuration issues.The commit script includes the element names you configure (such as IRB instance names and server names) in description statements in the generated configuration.
This feature also now includes a few new options so you have more flexibility to customize the generated configuration:
no-underlay-config
at the [edit services evpn
] hierarchy level—To provide your own underlay peering configuration.mtu overlay-mtu
andmtu underlay-mtu
options at the [edit services evpn global-parameters
] hierarchy level—To change the default assigned MTU size for underlay or overlay packets.
General Routing
Starting in Junos OS Release 24.2R1, when you run the
run show lldp local-information interface <interface-name> | display xml
command, the output is displayed under the lldp-local-info root tag and in the lldp-local-interface-info container tag. When you run therun show lldp local-information interface | display xml
command, the lldp-tlv-filter and lldp-tlv-select information are displayed under the lldp-local-interface-info container tag in the output.Non-revertive switchover for sender based MoFRR— In earlier Junos releases, source-based MoFRR ensured that the traffic reverted to the primary path from the backup path, when the primary path or session was restored. This reversion could result in traffic loss. Starting in Junos OS 22.4R3-S1, source-based MoFRR will not revert to the primary path, i.e. traffic will continue to flow through the backup path as long as the traffic flow rate on the backup path does not go below the configured threshold set under the
protocols mvpn hot-root-standby min-rate
command.Show active forwarding session for sender based MoFRR
— Theshow multicast route extensive
command will show the active forwarding session in the case of source-based MoFRR. The field Session Status: Up & Forwarding will indicate that the particular session is currently forwarding traffic.
Infrastructure
Option to disable path MTU discovery—Path MTU discovery is enabled by default. To disable it for IPv4 traffic, you can configure the
no-path-mtu-discovery
statement at the [edit system internet-options
] hierarchy level. To reenable it, use thepath-mtu-discovery
statement.[See Path MTU Discovery.]
Routing Protocols
Optimized mesh group routes (QFX5110, QFX5120, QFX5130, QFX5700 and ACX Series)—The
show route snooping
command for inet.1/inet6.1 table andshow route snooping table inet.1/inet6.1
will display only CE mesh group routes for platforms that support EVPN-MPLS or EVPN-VxLAN multicast. In earlier releases, other mesh groups like the VE mesh group were also displayed.
VPNs
Increase in revert-delay timer range— The
revert-delay
timer range is increased to 600 seconds from 20 seconds.[See min-rate.]