Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Open Issues

Learn about open issues in this release for the PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • On the PTX Platform with FPC-PTX-P1-A or FPC2-PTX-P1A, you might encounter a single event upset (SEU) event that might cause a linked-list corruption of the TQCHIP. PR1254415

  • On routers and switches running Junos OS, with Link Aggregation Control Protocol (LACP) enabled, deactivating a remote Aggregate Ethernet (AE) member link makes the local member link move to LACP detached state and cause traffic drops on that member link. The same scenario applied when a new member link is added where the other end of that link is not yet configured with LACP. PR1423707

  • In Link aggregation groups (LAGs) Enhanced link aggregation group (a.k.a. Aggregated Ethernet child NH reduction/AE Simple/LAG Enhanced) scenario, if FPC hosting single child member Aggregate Ethernet (AE) bundle is rebooted, the aggregate next-hops on such AE bundles might be discarding traffic, as the IFL reroute tables might get stuck in the down state, the packets drop might be seen on all other FPCs that the ingress traffic towards such AE bundles and the AE interfaces might not be used. PR1551736

  • On PTX platforms, when Inline Jflow is configured and high sampling rate (more than 4000 per second) is set, high CPU utilization might be observed and this might result in relevant impacts on traffic analysis and billing.PR1569229

  • Copying files to /tmp/ causes a huge JTASK_SCHED_SLIP. Copy files to /var/tmp/ instead. PR1571214

  • Tunnel statistics displays incorrect values because it was not supposed that tunnel interfaces would cache flow. PR1627713

  • When sending BGP Labeled Unicast (BGP-LU) traffic or Layer 3 VPN traffic over IPIP tunnels, if the remote end device is a purely IP device that does not understand labels, the labeled unicast or Layer 3 VPN label cannot go on top. PR1631671

  • V6 default route will not get added after successful dhcpv6 client binding on PTX1000 router during ZTP. PR1649576

  • ZTP: DHCPACK not received at ztp-server after zeroize of the device (client).PR1658287

  • On PTX platforms, packets drop is seen because of increment in PCS and framing errors on some of the 100GE ports on PIC or its peer devices after firmware migration.PR1669267

  • When an FPC (Flexible PIC Concentrator) on PTX5000 platforms is shut down by issuing a request command (request chassis offline slot <slot-number>) or by FPC power off configuration (set chassis fpc x power off), it gets stuck in the Announce Offline state since the associated timer (fru_graceful_offline_timer) doesn't increment and expire as it is supposed to.PR1683562

Interfaces and Chassis

  • On Junos PTX platforms, there might be a traffic silently droppped which happens because of next-hop installation failure for multicast RSVP(Resource Reservation Protocol) P2MP(Point to Multipoint) traffic. This issue might only be encountered in a scaled RSVP P2MP environment after a network event which might cause reconvergence.PR1653920

Routing Protocols

  • Any platforms with Micro BFD configured on member links of the LAG/AE interface, BFD Session state in Routing Engine remains as UP always even though PEER device has ceased.PR1675921