What's Changed
Learn about what changed in this release for EX Series switches.
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.
Forwarding and Sampling
-
Support added for interface-group match condition for MPLS firewall filter family.
General Routing
-
Non-revertive switchover for sender based MoFRR—In earlier Junos OS 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, that is, 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
protocols mvpn hot-root-standby min-rate.[See min-rate.]
-
For MPC5E line card with flexible-queuing-mode enabled, queue resources are shared between scheduler block 0 and 1. Resource monitor CLI output displays an equal distribution of the total available and used queues between scheduler blocks. This correctly represents the queue availability to the Routing Engine.
[See show system resource-monitor and show system resource-monitor ifd-cos-queue-mapping fpc.]
-
New CLIs introduced to collect Layer 2 bridging and Layer 2 protocols for smart debugging. PR1803119
-
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.
-
Enhancement to fix output with Junos PyEz for duplicate keys in PKI (MX Series, SRX Series, EX Series)—In earlier releases, though the CLI output displayed all the duplicate keys for the corresponding hash algorithms in PKI using
show security pki local-certificate detail | display jsoncommand, for the same requested data, Junos PyEz displayed the last key only. Starting this release, the CLI output and the PyEz displays all the duplicate keys with the enhanced tags. -
Field name update in the CLI output--The
show system licensecommand output field name changed frominvalidtolicense not installed.PR1812126 -
Feature name updates in CLI output—Starting in this release, the
show system licensecommand output displays the feature name.PR1815591 -
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.
-
Support added for interface-group match condition for MPLS firewall filter family.
-
Option
allow-transientsis set by default for the EZ-LAG commit script—The EZ-LAG feature simplifies setting up EVPN multihoming configurations using a set of configuration statements and a commit script. The commit script applies transient configuration changes, which requires theallow-transientssystem commit scripts option to be set. Now the default system configuration sets theallow-transientsoption at the EZ-LAG commit script file level, removing the need to set this option manually. In earlier releases where this option isn?t set by default, you must still configure the option explicitly either globally or only for the EZ-LAG commit script. -
SSH key options for user account credentials—You can configure key-options key-options option at the set system login user user authentication [ssh-rsa|ssh-ecdsa|ssh-ed25519] ssh key hierarchy level.
-
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 thesecondary-independent-resolutionoption.PR1827906 -
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.
-
Option
allow-transientsis set by default for the EZ-LAG commit script—The EZ-LAG feature simplifies setting up EVPN multihoming configurations using a set of configuration statements and a commit script. The commit script applies transient configuration changes, which requires theallow-transientssystem commit scripts option to be set. Now the default system configuration sets theallow-transientsoption at the EZ-LAG commit script file level, removing the need to set this option manually. In earlier releases where this option isn?t set by default, you must still configure the option explicitly either globally or only for the EZ-LAG commit script. -
Deprecation of jnxLEDTable—The jnxLEDTable table is no longer supported.PR1848057
-
A new counter "Sessions hit due to high rate" is added to
show services service-sets screen-session-limit-counterscommand for all subscriber traffic. This counter tracks the sessions that come up on the screen irrespective of the "alarm-without-drop" configuration. When "alarm-without-drop" option is disabled, all the counters display updated statistics. When "alarm-without-drop" is enabled, then, the screen-drop counters onshow services service-sets statistic screen-dropcommand do not increase. The "sessions hit due to high rate" value is displayed.[See alarm-without-drop (IDS Screen Next Gen Services), show services service-sets statistic screen-drops (Next Gen Services), and show services service-sets statistic screen-session-limit-counters (Next Gen Services).]PR1849594
-
Changes to request system recover command syntax (EX Series)—Options (all-members | local | member member-id) have been added to the request system recover command to specify the members for which the system needs to recover data.
-
Support for 4x10G uplink module—You can use the 4x10G uplink module to support both 10G and 1G transceivers and interfaces. The device automatically detects the presence of a 10G or 1G transceiver and creates a physical interface of the corresponding speed.
Junos XML API and Scripting
-
Commit script input to identify software upgrades during boot time (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—The
junos-contextnode-set includes thesw-upgrade-in-progresstag. Commit scripts can test thesw-upgrade-in-progresstag value to determine if the commit is taking place during boot time and a software upgrade is in progress. The tag value isyesif the commit takes place during the first reboot after a software upgrade, software downgrade, or rollback. The tag value isnoif the device is booting normally.[See Global Parameters and Variables in Junos OS Automation Scripts.]
Platform and Infrastructure
-
Unsupported Interface-Group Matching for Bridge and VPLS Families (MX and EX92xx)—The interface-group match conditions for bridge and VPLS families are currently not supported, and counters do not increment for the related input and output filters. You must avoid configuring the interface-group match configurations for these families and adapt alternative monitoring and filtering methods.PR1817756
Routing Protocols
-
iBGP RR Update for Link Bandwidth Aggregation—In iBGP Route Reflector (RR) deployments, aggregation policies may advertise BGP Link Bandwidth (LBW) values that differ from the arithmetic sum of LBWs that multiple Provider Edges (PEs) provide. The update clarifies and enforces correct LBW calculation on RRs because the RRs recompute bandwidth locally instead of summing it cumulatively. Users might observe changes in the LBW values that RRs advertise, which can influence traffic-engineering behavior.PR1806864
-
Update to IGMP snooping membership command options—The
instanceoption is now visible when issuing theshow igmp snooping membership ?command. Earlier, theinstanceoption was available but not visible when?was issued to view all possible completions for theshow igmp snooping membershipcommand. -
IS-IS minimum SPF holdown time—We have reduced the minimum value for configuring holddown times in the IS-IS Shortest Path First (SPF) algorithm. You can now set the holddown time to a minimum of 1 second (1000 milliseconds).
-
Support for RFC 8950 compliant next hop encoding (Junos OS and Junos OS Evolved)—Enables advertising IPv4 and VPN IPv4 NLRI with IPv6 next hops over IPv6 BGP sessions. This capability aligns with extended next-hop encoding standards and improves interoperability across multi-vendor environments. The configuration is now visible and fully user configurable, ensuring standards-based behavior for IPv4 NLRI over IPv6 next hops.
-
Display Issue in IS-IS Protocol (Junos OS and Junos OS Evolved)—A display issue has been identified in the IS-IS protocol where the ISO address is not picked up properly, and the system identifier (system ID) does not show the correct value when loopback interfaces per routing instance are configured. This issue affects all platforms supporting the IS-IS protocol. You notice that the system ID value in the
show isis overviewcommand output reflects the system ID of the primary instance's loopback interface for all routing instances, rather than the locally configured ISO addresses for each routing instance. Despite this display inaccuracy, the actual system IDs utilized by the IS-IS protocol remain correct and can be verified through theshow isis hostnamecommand or by inspecting IS-IS packets.[See Configuring an ISO System Identifier for the Router.]PR1816371
-
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.logor for all vlans with the configuration statementedit 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 theshow isis database extensivecommand. 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 routeorshow isis route flex-algorithm-id (id)command with the destination prefix, all the route types for that destination prefix are displayed.PR1828221 -
MLD snooping proxy and l2-querier source-address (ACX7024, ACX7100-32C, EX4400-24MP, PTX10001-36MR, QFX5120-32C, and QFX5130-32CD)—The
source-addressconfigured forproxyandl2-querierunder 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.]
-
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
-
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 routeandshow route table bgp.rtarget.0 protocol rtargetoutputs, 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
traceoptionsoption is supported under the[edit routing-instance protocols igmp-snooping vlan]and[edit routing-instance protocols mld-snooping vlan]hierarchy.traceoptionscan be enabled for both specific and all vlans.[See vlan (IGMP Snooping) and vlan (MLD Snooping).]PR1845242
-
BGP Task Progress Monitoring—The
show task jobs extensivecommand now displays progress for BGP-specific jobs including BGP init policy walk, BGP group join, BGP Peer Reconfig, New policy flash update, and BGP RIB reconfig. This provides network administrators with detailed visibility into BGP task completion status, improving operational transparency and diagnostics.PR1857368
User Interface and Configuration
-
Compact format deprecated for JSON-formatted state data (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—We've removed the
compactoption at the[edit system export-format state-data json]hierarchy level because Junos devices no longer support emitting JSON-formatted state data in compact format. -
Changes to the
show system informationandshow versioncommand output (ACX Series, EX Series, MX Series, QFX Series, SRX Series, and vSRX)—Theshow system informationcommand output lists theHostnamefield first instead of last. Theshow versioncommand output includes theFamilyfield. TheFamilyfield identifies the device family under which the device is categorized, for example,junos,junos-es,junos-ex, orjunos-qfx.[See show system information and show version.]
-
Detection of legacy PD (PoE)—The detection of legacy PD (powered device) is disabled by default in EX4400-24MP, EX4400-48MP, EX4400-48MXP, EX4400-48XP, EX4400-24P, and EX4400-48P models. To enable a legacy PD in a port for these models, see Enabling Legacy Powered Device.
-
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 informationcommand is designed to generate system information for troubleshooting and debugging purposes. Users with the specific access privilegesmaintenance,view, andview-configurationcan execute request support information command.PR1835092