Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

What's Changed

Learn about what changed in this release for MX Series routers.

General Routing

  • A new counter "Sessions hit due to high rate" is added to show services service-sets screen-session-limit-counters command 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 on show services service-sets statistic screen-drop command do not increase. As a result, the "sessions hit due to high rate" value is displayed.

    [See https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/alarm-without-drop-edit-services-screen-ids-options-usf.html, https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/command/show-services-service-sets-statistic-screen-drop.html, and https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/command/show-services-service-sets-statistic-screen-session-limit-counters.html.]PR1849594

  • When you run the request vmhost zeroize command to zeroize a single Routing Engine on a dual Routing Engine device, the CLI incorrectly displays a message indicating that it will zeroize both Routing Engines.

  • G.8275.1 profile configuration with PTP, SyncE, and hybrid mode (Junos)— On all Junos platforms, when configuring the G.8275.1 profile, it is mandatory to configure Precision Time Protocol (PTP), Synchronous Ethernet (SyncE), and hybrid mode. Earlier, the system would not raise a commit error even if the required hybrid and SyncE configurations were missing while configuring G.8275.1 profile. However, going forward you will not be able to configure the G.8275.1 profile without configuring PTP, SyncE and hybrid mode to be compliant with the ITU-T standards.

    [See G.8275.1 Telecom Profile].

  • You can monitor chassis temperature on MX Series devices at Flexible PIC Concentrator (FPC) level as well using the show chassis alarms command, which displays a minor, major or critical alarm, "Temperature Warm" when the FPC exceeds the configured warm threshold temperature. PR1877621

  • On the MPC7E-10G line card, when you configure the 10-Gigabit Ethernet ports to operate as 1-Gigabit Ethernet ports, use the speed statement at both the [edit interfaces interface-name gigether-options] and [edit interfaces interface-name] hierarchy levels.PR1879198

  • log-tag functionality—The log-tag functionality is introduced in set services service-setPR1885614

  • Default route installation for non-default routing instances with iked process (MX480 and MX960)—You can install default route when the st0 interface is in a non-default routing instance. This enhancement supports migration from MS-MPC to SPC3 as MX-SPC3 injects these routes through auto route insertion (ARI) for traffic selector routes. The configuration facilitates route installation in specified routing instances.

    [See Traffic Selectors in Route-Based VPNs.]

  • New option for debug collector data storage path—We've included the option outdir to specify an output directory for storing debug collector data in a customised path. This allows you to organise and access diagnostic information more efficiently, adapting storage to your specific requirements.

    [See request system debug-info.]

Subscriber Access Management

  • You can configure VLAN termination cause codes to specify RADIUS attribute values for different termination scenarios on JUNOS MX platforms supporting the Layer-2 Bitstream Access (L2BSA) feature. You can diagnose and manage network issues effectively by understanding the specific reasons for VLAN termination. Ensure that the correct termination cause codes are sent by validating configuration and testing scenarios to correctly interpret network events. When a subscriber logs out, the system occasionally sends an incorrect termination cause value to RADIUS. The subscriber VLAN "Account-Terminate-Cause" in "Acct-Stop" message for different L2BSA subscriber logout error scenarios is modified to display correct reasons for termination.

    [See VLAN Termination Causes and Code Values and show network-access aaa terminate-code.

User Interface and Configuration

  • Changes to the show system storage command output (ACX Series, EX Series, MX Series, PTX Series, QFX Series, and SRX Series)—We've updated the show system storage command output to include only true (physical) storage and exclude any host/hypervisor level storage. In earlier releases, the output also includes a container/jail storage, which does not have a separate storage of its own.

    [See show system storage.]

  • Stale ui-state.db data in persistent NETCONF sessions post-mgd restart—Existing NETCONF sessions might fetch stale data from ui-state.db after mgd -N restart. New sessions correctly map the refreshed database. Scripts must establish new sessions post-restart to access updated values. Functional configuration remains unaffected. Script failures monitoring "local-host" NETCONF sessions-Scripts might fail when including "local-host" NETCONF sessions in monitoring operations. Internal sessions are now excluded from tracking. Scripts must filter out "local-host" sessions. No impact to internal application functionality.