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.

EVPN

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

General Routing

  • Hidden disable-fpc CLI statement (QFX5000 Series Switches)—We've hidden the disable-fpc CLI statement at the following hierarchy levels:

    • edit system ddos-protection global

    • set system ddos-protection protocols protocol-group aggregate

  • Earlier to this release, when you configure the disable-fpc CLI statement, the device generated DCPFE core when the device processes a large volume of data as it restricts the DDOS protection of the CPU.

    [See disable-fpc (DDoS).]

  • Enhanced telemetry aggregation logic alignment with SNMP counter calculations (QFX-Series)—The Junos OS telemetry is updated to include missing internal counters used in SNMP (e.g., bucket drop, idiscards, il3_incomplete, etc.). The change to the OpenConfig sensors ensures parity across both monitoring mechanisms.

    [See YANG Data Model Explorer.]

  • High-power optics support with CLI configuration option (QFX5240 and QFX5241)—You can enable high-power optics across all ports by configuring the high-power-mode option for each port. This feature supports up to 32 high-power modules, allowing you to benefit from enhanced connection capabilities. Ensure you configure the necessary settings to initialize and utilize high-power optics effectively, optimizing your network's performance.

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