Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

What's Changed

Learn about what changed in this release for QFX Series Switches.

Note:

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

  • EVPN system log messages for CCC interface up and down events—Devices will now log EVPN and EVPN-VPWS interface up and down event messages for interfaces configured with circuit cross-connect (CCC) encapsulation types. You can look for error messages with message types EVPN_INTF_CCC_DOWN and EVPN_INTF_CCC_UP in the device system log file (/var/log/syslog). PR1822918

General Routing

  • Change to the commit process—In prior Junos OS and Junos OS Evolved releases, if you use the commit prepare command and modify the configuration before activating the configuration using the commit activate command, the prepared commit cache becomes invalid due to the interim configuration change. As a result, you cannot perform a regular commit operation using the commit command. The CLI shows an error message: 'error: Commit activation is pending, either activate or clear commit prepare'. If you now try running the commit activate command, the CLI shows an error message: 'error: Prepared commit cache invalid, failed to activate'. You then must clear the prepared configuration using the clear system commit prepared command before performing a regular commit operation. From this Junos and Junos OS Evolved release, when you modify a device configuration after 'commit prepare' and then issue a 'commit', the OS detects that the prepared cache is invalid and automatically clears the prepared cache before proceeding with regular 'commit' operation. PR1806197

    [See id-commit-preparation-and-activation-overview, commit prepare, and commit activate.]

  • In a firewall filter configured with a port-mirror-instance or port-mirror action, if l2-mirror action is also configured, then port-mirroring instance family should be any. In the absence of the l2-mirror action, port-mirroring instance family should be the firewall filter family.PR1818423

  • Support added for interface-group match condition for MPLS firewall filter family. PR1818968

  • BGP FlowSpec with secondary-independent-resolution—The secondary-independent-resolution option is available only for the default instance for inet and inet6 families. We do not support configuring BGP FlowSpec in a VRF along with the secondary-independent-resolution option.PR1827906

  • Deprecation of jnxLEDTable—The jnxLEDTable table is no longer supported. PR1848057

Routing Protocols

  • MLD snooping proxy and l2-querier source-address (ACX7024, ACX7100-32C, EX4400-24MP, PTX10001-36MR, QFX5120-32C, and QFX5130-32CD)— The source-address configured for proxy and l2-querier under the mld-snooping hierarchy should be an IPv6 link-local address in the range of fe80::/64. The CLI help text has been updated to "Source IPv6 link local address to use for proxy/L2 querier". In earlier releases, the CLI help text read, "Source IP address to use for proxy/L2 querier."

    [See source-address.]

  • Update to IGMP snooping membership command options—The instance option is now visible when issuing the show igmp snooping membership ? command. Earlier, the instance option was available but not visible when ? was issued to view all possible completions for the show igmp snooping membership command.

    [See show igmp snooping membership.]PR1810650

  • Configure IGMP snooping traceoptions (ACX Series, EX Series, QFX Series, and SRX Series)—Global traceoptions for IGMP snooping are disabled. Enable IGMP snooping traceoptions either for a specific vlan by configuring edit protocols igmp-snooping vlan v100 traceoptions file igmp_snooping.log or for all vlans with the configuration statement edit protocols igmp-snooping vlan all traceoptions file igmp_snooping_all_vlans.log.

    [See Configuration of IGMP snooping traceoptions on L2NG platforms.]PR1820227

  • Display Alignment Update for show isis database extensive—We have improved the display alignment in the output of the show isis database extensive command. Application-specific text is now presented after legacy information and without misalignment in traffic engineering metrics when the L-Flag is set, enhancing data readability and usability. PR1822385

  • IS-IS Routing Table Display Change—When you filter routes using the show isis route or show isis route flex-algorithm-id <id> command with the destination prefix, all the route types for that destination prefix are displayed.

  • Upgrade limit-bandwidth from 32-bit to 64-bit for Extended Bandwidth Support (All platforms)—The limit-bandwidth action in routing policy statements currently supports a maximum value of 4.2 G because it uses a 32-bit field. Update the implementation with a 64-bit (uint64) field to allow higher bandwidth advertisements.PR1829950

  • SNMP Trap Behavior Honors Logical-System Hierarchy (All Platforms)—The snmp-options backward-traps-only-from-established configuration now correctly applies when set under a logical system. In earlier releases, the setting needed a commit full or a corresponding global configuration to take effect. Logical-system-specific values are activated with a standard commit and don't depend on global scope.PR1837269

  • RTC Route Display Fixed (Junos OS and Junos OS Evolved)—The latest update corrects the display issue for RTC routes associated with transport targets in BGP show command output. Earlier versions failed to format (pretty-print) those routes correctly in the show route and show route table bgp.rtarget.0 protocol rtarget outputs, leading to readability problems. This enhancement now presents RTC routes in a clear format, making routing table inspections and troubleshooting more efficient.PR1839269

  • Extension of traceoptions support for VLANs in IGMP/MLD snooping—The traceoptions option is supported under the [edit routing-instance protocols igmp-snooping vlan] and [edit routing-instance protocols mld-snooping vlan] hierarchy. traceoptions can be enabled for both specific and all vlans.

    [See vlan (IGMP Snooping) and vlan (MLD Snooping).]PR1845242

  • Modification of SRTE Advertisement Policy Name Display—BGP will now not generate and not display the Advertised Policy Name field for BGP-SRTE routes in show command output when the "Name TLV" is not received in the tunnel encapsulation attribute with the BGP-SRTE NLRI. The field will only be displayed when the Name TLV is received. This update eliminates ambiguity by ensuring multiple NLRIs do not display the same policy name, providing clearer and more accurate route information in command outputs.PR1853958

User Interface and Configuration

  • Changes to the show system information and show version command output (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—The show system information command output lists the Hostname field first instead of last. The show version command output includes the Family field. The Family field identifies the device family under which the device is categorized, for example, junos, junos-es, junos-ex, or junos-qfx.

    [See show system information and show version.]

  • Access privileges for request support information command (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series Firewalls, and vSRX Virtual Firewall)—The request support information command is designed to generate system information for troubleshooting and debugging purposes. Users with the specific access privileges maintenance, view, and view-configuration can execute request support information command. PR1835092