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.

[See show evpn vpws-instance.]PR1918931

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

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

Correct auto-negotiation status display for 1G full-duplex links (EX2300-48MP, EX3400-48T, EX4100-48MP, EX4100-48P, and EX4400-48P)—You should be aware that when operating at a speed of 1G with full-duplex mode and no auto-negotiation, the system internally advertises auto-negotiation capabilities despite displaying incorrect status as "disabled" and "No-auto-negotiation" in interface commands. You need to remove the 1G option for copper ports while configuring speed to avoid this discrepancy.

Support added for new payload match conditions (EX4100, EX4400, EX5200, and QFX5120)—Support added for payload-source-ipv4-address, payload-destination-ipv4-address, payload-source-ipv6-address, payload-destination-ipv6-address, payload-source-mac-address, and payload-destination-mac-address match conditions for IPv4 and IPv6 traffic which can be applied on the ingress port only.

[See Firewall Filter Match Conditions for IPv4 Traffic.]PR1914083

Enhanced loop detection for Layer 2 networks (EX4650, QFX5120-32C, QFX5120-48T, QFX5120-48Y, and QFX5120-48YM) —We've added support for monitoring all VLANs on a logical interface. You can set vlan-id all option under the [edit vlans vlan-name] hierarchy. With this change, the devices can detect network loops across multiple VLANs and interfaces, improving network stability and performance.

[See Enable Lightweight PE-CE Loop Detect on a Logical Interface and loop-detect.]PR1924351

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/32PR1929438