What's Changed

Pseudowire status display update in show evpn vpws-instance output—For EVPN-VPWS pseudowire interfaces configured with protocols ccc, the pseudowire field in the show evpn vpws-instance command output now displays the correct corresponding pseudowire status value "Not Present" when the local logical interface for the pseudowire connection is not present. Previously, this field still displayed the value "CCC-Up" even when the Status output field showed the local interface was not present.

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. 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)

SFP Optics LOS alarms (MX Series)—SFP Optics don't support Tx laser disabled alarm, Tx loss of signal functionality alarm, and Rx loss of signal alarm as diagnostics output.

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.

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

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.

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.]

Run CSDS CLI commands as root user (MX240, MX304, MX480, MX960, MX10004, and MX10008)—Run CSDS CLI operations as the root user to ensure successful execution of maintenance commands for key exchange, authentication, and JDM interactions. Run the following commands as root user: request csds jdm add csds-instance-id csds-instance-id image vsrx-image-with-path, request csds authenticate-host csds-instance-id csds-instance-id, request csds delete-vsrx csds-instance-id csds-instance-id, request csds extract-vsrx-keys csds-instance-id csds-instance-id, request csds jdm add csds-instance-id csds-instance-id image vsrx-image-with-path, and request csds sync-controller other-controller-ip other-controller-ip. If a non-root user runs these commands, you'll see the following warning message - warning: Must be logged in as root to execute command.

[See request csds add-vsrx, request csds authenticate-host, request csds delete-vsrx, request csds jdm, request csds extract-vsrx-keys, andrequest csds sync-controller.]

New file path for customer binding information—The Dynamic Host Configuration Protocol (DHCP) local server or relay agent now stores customer binding information to a file in /var/db. Previously, the file was stored in /var/preserve, which was not secured. To restore the customer binding information after an upgrade or reboot, choose one of the following approaches: -Before upgrading, copy the file from /var/preserve to /var/db. -After upgrading, copy the file from /var/preserve to /var/db and run the request dhcp restore-persistent-clients from-file command.

[See Configuring DHCP Local Server to Preserve Subscriber Binding Information.]PR1934180

Deprecation of shell option—The shell option no longer requires a separate configuration and is now the default behavior. Deprecating the shell option enhances efficiency and simplifies management tasks.PR1892385

Supports static route configurations with /32 host addresses—Static Route Configuration with /32 host addresses allows configuring static routes using an interface as the next-hop, even if the interface has a /32 netmask. This change is significant for network administrators managing static routes in environments where interfaces are often assigned /32 addresses. Routes configured in this manner will now commit successfully, removing previous limitations. Example for CLI commands of static routes that uses an interface addresses as next-hop: set routing-options static route 45.63.100.176/32 next-hop et-0/0/32.0 and set interfaces et-0/0/32 unit 0 family inet address 169.254.255.32/32. PR1929438