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

General Routing

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

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

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

  • SMAC accounting mismatch (PTX10002-36QDD, and PTX10008) — Source MAC (SMAC) accounting over accounts the byte counter by including the L2 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.]

Junos XML API and Scripting

  • Refreshing scripts from an HTTPS server requires a certificate (ACX Series and 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.]