What's Changed
Learn about what changed in this release for the PTX Series.
EVPN
-
Specify the UDP source port in a ping overlay or traceroute overlay operation—In Junos OS releases prior to 22.4R1, you could not configure the udp source port in a ping overlay or traceroute overlay operation. You may now configure this value in an EVPN-VXLAN environment using
hash. The configuration optionhashwill override any other hash-* options that may be used to determine the source port value.
General Routing
Single source of data for operational state sensor leaves (PTX10008)—You can use the suppress-interface-leaf CLI statement to suppress telemetry streaming of the following sensors from the packet forwarding engine (PFE):
This might be required for collectors that require a single source of data for each sensor./interfaces/interface/state/high-speed /interfaces/interface/state/oper-status
[See suppress-interface-leaf.]
-
Two new alarms are added and can be seen with MPC11E when 400G-ZR optics are used. High Power Optics Too Warm: warning of the increase in chassis ambient temperature with no functional action taken on the optics Temperature too high for optics power on: New inserted optics when the chassis ambient temperature is elevated beyond the threshold will not be powered on and would need to be reinserted when the ambient temperature is within the acceptable rangePR1719569
-
The packet rate and byte rate fields for LSP sensors on AFT (with the legacy path) have been renamed as jnx-packet-rate and jnx-byte-rate and is in parity with the UKERN behavior. Previously, these rate fields were named as packetRate and byteRate.PR1725641
-
In older Junos Releases, Data Definition Language (DDL) lists were ordered by the sequence in which the user configured the list items, for example a series of static routes. With this change, the list order is determined by the system with items displayed in numerical sequence rather than by the order in which the items were configured. There is no functional impact to this change.PR1738014
-
Changes to XML output for MACsec operational commands—We have changed the XML output for the following MACsec operational commands (and the corresponding RPCs) so that they emit valid XML.
show security mka sessions brief ?A new "session-common" element encloses each set of information for each session.show security mka sessions detail ?A new "session-live" element encloses the state of the interface.show security mka sessions summary ?A new "mka-session-terse" tag encloses the set of tags for each session.show security macsec connections ?A new "macsec-interface-common-information" element encloses the set of tags for each connection.show security mka statistics ?A new "mka-interface-statistics" element encloses each interface's protocol statistics.[See show security mka sessions, show security macsec connections, and show security mka statistics.]PR1744564
-
Write cache disabled alarms no longer raised—The "Disk 2 Write Cache disabled" alarms were reported in the chassis alarms due to a missing SSD model in Junos OS supported device table. The support is now added, and alarms are no longer reported. PR1956899
Interfaces and Chassis
-
Starting in Junos OS release 23.2R1 and Junos OS Evolved release 23.2R1-EVO, the output of show chassis power command displays the state of the power supply in PTX10003 and QFX10003 platforms.
[See show chassis power.]
-
When all the members of the AE have the same speed (x) and no mixed speed configured. If you change the speed value of any member of the AE to a value other than x, the commit succeeded in earlier releases. From this release, the commit fails. When there are et interfaces with different speeds and you want them to be part of an AE interface. If you change the speed of all the members of the interfaces to be the same speed (x), configure the AE interface, and commit, the commit failed in earlier releases. From this release, such commits succeed.
Junos XML API and Scripting
-
Ability to commit
extension-service fileconfiguration when application file is unavailable—When you set theoptionaloption at the[edit system extension extension-service application file file-name]hierarchy level, the operating system can commit the configuration even if the file is not available at the /var/db/scripts/jet file path.[See file (JET).]PR1712065
-
Ability to restart restart daemonized applications—Use the
request extension-service restart-daemonize-app application-namecommand to restart a daemonized application running on a Junos device. Restarting the application can assist you with debugging and troubleshooting.[See request extension-service restart-daemonize-app.]PR1725063
Network Management and Monitoring
-
Changes to the NETCONF server's
<rpc-error>element when theoperation="delete"operation deletes a nonexistent configuration object (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX )—We've changed the<rpc-error>response that the NETCONF server returns when the<edit-config>operation usesoperation="delete"to delete a configuration element that is absent in the target configuration. The error severity is error instead of warning, and the<rpc-error>element includes the<error-tag>data-missing</error-tag>and<error-type>application</error-type>elements. -
Changes to the RPC response for
<validate>operations in RFC-compliant NETCONF sessions (ACX Series, EX Series, MX Series, PTX 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.
Platform and Infrastructure
-
The
ping host | display xmlcommand produces CLI output without errors (ACX Series, PTX Series, and QFX Series) — In Junos OS release 22.4R2, theping host | display xmlcommand now produces CLI output formatted in XML.[See ping.]
-
Earlier, shaping of Layer 2 pseudowires did not work on logical tunnel interfaces. This has been fixed for all platforms except QX chip-based MICs and MPCs.PR1751798
Routing Protocols
-
TI-LFA and Legacy LFA Configuration Commit Validation Update (Junos OS and Junos OS Evolved)—You can now enable TI-LFA and legacy FRR (node-link-protection) in separate OSPF instances. The system generates a commit error only if you enable both TI-LFA and legacy FRR under the same OSPF instance. In that case, the commit fails and triggers the following message: "error: commit failed: (statements constraint check failed)".
[See Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS and OSPF.]PR1718886
-
BGP Multipath route calculation—When configuring multipath in the routing-instance, BGP routes that are inactive due to cluster-list length are also considered as eligible for multipath calculations. This enhances route selection by including more potential paths in your multipath configuration.
-
Correction in
show bgp neighborOutput (Junos OS and Junos OS Evolved)—We corrected a typo in theshow bgp neighborcommand output whereconfigruedwas displayed instead ofconfigured. We've also added the existing optionAcceptedPrefixLimitto the output so it displays when configured. This improvement ensures accurate display of the configuration settings and provides additional information for monitoring and managing BGP neighbor configurations.[See show bgp neighbor.]PR1740982
-
BGP Neighbor Telemetry Statistics (Junos OS and Junos OS Evolved)—BGP neighbor statistics reported through telemetry are now always aggregated, regardless of whether
rib-shardingis enabled. Previously, when sharding was active, statistics were streamed per shard. With the current behavior, sensors are installed appropriately, and statistics are aggregated in the main thread before being streamed. The controllers and collectors now receive a single, unified view of BGP neighbor statistics.PR1765189
User Interface and Configuration
-
Port Mirroring Configuration Update—Interface ranges are no longer supported as part of configuration groups for creating analysers. If you attempt to use an interface-range in a config group, you will encounter an error indicating an invalid interface type. Additionally, interface ranges or interface lists cannot be configured under this setting. This change ensures precise and error-free configuration by requiring the specification of individual interfaces rather than ranges, thus improving the accuracy and reliability of port mirroring setups.PR1728883
-
Viewing files with the
file compare filescommand requires users to havemaintenancepermission—Thefile compare filescommand in Junos OS and Junos OS Evolved requires a user to have a login class withmaintenancepermission.
VPNs
-
Enhancement to MVPN Sender Site Configuration—MVPN (Multicast Virtual Private Network) sender sites configured with an IR (Ingress Replication) tunnel send Type 1 routes with label 0. This means that remote PEs do not add the Type 1 route as a leaf of the tunnel but will still add the sender site PE as MVPN neighbor. This ensures that traffic from the sender site PE is not dropped by the remote PEs due to unknown MVPN neighbor. But since the sender site PE sends the label as 0, remote PEs will not add the sender site PE as a leaf and traffic from the remote PE will not be replicated to this PE ensuring sender site functionality.PR1711769