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 PTX Series routers.

General Routing

  • Support added for source and destination port optimization for port ranges for ipv6 input firewall filters.

  • Deprecation of jnxLEDTable—The jnxLEDTable table is no longer supported.

  • Control Board offline delay for system stability (PTX10008)—After initiating a node halt, you must wait 1 minute before doing Control Board (CB) offline. Attempting to offline the CB within this period will result in an error message. This delay helps maintain the stability and proper functioning of the system.

    [See request chassis cb.]

  • Log file location during system downgrade (PTX10002-36QDD) — When performing a system downgrade, if the downgrade fails, the validation failure log message now points to the log file location at /var/log/validation_config.log.

  • The show subscribers extensive client-type dhcp | display xml validate command has now been updated to display correct output instead of Duplicate data element error.

  • Starting in Junos OS Evolved Release 24.4R2, you can set the set protocols ptp delay-comp interface ifd-name transmit tx-comp-in-nsec receive rx-comp-in-nsec command to compensate for external latencies for a given physical interface (IFD) on PTX10008 routers. You can use it to compensate for transceiver latencies, which are significantly higher in PAM4 optics, and other delays such as optics latency and cable asymmetry. The range of latency that can be compensated is from -1000ns to +1000ns. See "ptp", ?delay-comp?, and "Precision Time Protocol Delay Compensation"

  • Change in CLI output (PTX Series)—The CLI output for show system license bandwidth, show system license bandwidth fpc, and show system license fpc commands is updated.

    [See Monitor Junos Licenses.]

  • Deprecated license trace (Junos OS Evolved)—We've deprecated the CLI option show system license liblicense-trace.

  • SMAC accounting mismatch (PTX10002-36QDD, and PTX10008) — Source MAC (SMAC) accounting over accounts the byte counter by including the Layer 2 overhead in an IP packet. Both ingress and egress accounting for a SMAC learnt on any interface is affected. The packet accounting and the number of SMAC addresses learnt is correct.

    [See MAC address accounting for L3 interfaces and aggregated Ethernet interfaces.]

Class of Service (CoS)

  • In Junos OS Evolved, do not associate a default forwarding class name with a different queue number. Use a custom forwarding class name instead. Defining customer forwarding classes with factory default forwarding class names causes errors.

EVPN

  • Easy EVPN LAG (EZ-LAG) feature lightweight loop detection configuration change—We have updated the configuration generated by the easy EZ-LAG feature?s commit script to use logical interface names for the lightweight leaf to server loop detection feature. The EZ-LAG commit script previously generated the loop detection configuration with physical interface names, but the loop detection feature works only for logical interfaces. The lightweight loop detection configuration uses the loop-detect statement at the edit protocols hierarchy level.

    [See Easy EVPN LAG (EZ-LAG) Configuration.]

Interfaces and Chassis

  • Vlan Tagging 1. For PTX EVO platforms, if you have configured an Interface Device (IFD) with the family ethernet switching vlan members configuration, you cannot use both VLAN tagging and flexible VLAN tagging CLI commands on the IFD at the same time. This configuration is not supported, and a warning is issued if you try to commit this configuration. 2. For EVO platforms, if you have configured any Logical Interface (IFL) on an Interface Device (IFD) with the family ethernet-switching configuration, you cannot configure any other families on a different IFL unless you configure the IFD with the flexible-ethernet-services encapsulation type. This configuration is not supported, and a warning is issued if you try to commit this configuration.

Junos XML API and Scripting

  • Refreshing scripts from an HTTPS server requires a certificate (ACX Series, PTX Series, and QFX Series)—When you refresh a local commit, event, op, SNMP, or Juniper Extension Toolkit (JET) script from an HTTPS server, you must specify the certificate (Root CA or self-signed) that the device uses to validate the server's certificate, thus ensuring that the server is authentic. In earlier releases, when you refresh scripts from an HTTPS server, the device does not perform certificate validation. Before you refresh a script using the set refresh or set refresh-from configuration mode command, first configure the cert-file statement under the hierarchy level where you configure the script. The certificate must be in Privacy-Enhanced Mail (PEM) format.

    [See cert-file.]

Routing Protocols

  • Extension of traceoptions support for VLANs in IGMP/MLD snooping— The traceoptions option is supported under the edit routing-instance protocols igmp-snooping vlan and edit routing-instance protocols mld-snooping vlan hierarchy. traceoptions can be enabled for both specific and all VLANs.

    [See vlan (IGMP Snooping) .]

User Interface and Configuration

  • Access privileges for request support information command (PTX Series Firewalls)— The request support information command is designed to generate system information for troubleshooting and debugging purposes. Users with the specific access privileges maintenance, view, and view-configuration can execute request support information command.

  • Changes to the show system storage command output (ACX Series, PTX Series, and QFX 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.]

  • Option to view combined disk space usage statistics for all configuration databases (ACX Series, PTX Series, and QFX Series)—The show system configuration database usage command provides the merge option. When you include the merge option, the command output displays combined disk space usage statistics for all configuration databases, including the static configuration database and all ephemeral configuration database instances.

    [See show system configuration database usage.]