Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 15.1F6 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 FPC3, IPv4 and IPv6 port mirroring is not supported on the egress interface. PR1081329
  • 100G mode for 96x10G/24x40G PIC is not supported. PR1129888
  • On PTX3000 routers using FPC3-SFF-PTX-U1 FPC, removing the master Control Board from the chassis ungracefully can result in packet loss. To avoid packet loss, use the request chassis Routing Eengine master switch command to change the master Routing Engine and Control Board to be the backup before removal. PR1137194
  • Traffic may drop during Routing Engine switchover. PR1164107
  • For PTX5000 platforms with Broadway-based FPCs, BFD V6 sessions with aggressive timers or when CPU load is high on the Routing Engine might flap, eg., during GRES or if less than 10 milisecond timer has been configured. This is applicable only for IPV6 BFD sessions on PTX Series platforms for Broadway-based FPCs. PR1165719

Integrated Photonic Line Card and Expansion Module

  • The show chassis fpc command does not properly display the temperature of the IPLC expansion module. PR1183222
  • The show chassis environment command does not display the temperature for the IPLC expansion module. PR118232
  • Trap notifications for TCA alerts are not always sent properly on the IPLC module. PR1185291


  • This is a rare scenario, where LSP's bw is modified to maximum possible value of the link bw in one commit, upon commit some of the LSPs will be delayed to signal to the new bandwidth. For example, while the static bw of LSPs is modified by apply-group, let's say 500 LSPs each has 1m reservation is modified by apply-group configuration to 2m where total link bw is 1g. In this case some of the LSPs will be delayed to signal because of non-availability of bw. These LSPs will be signaled when they have sufficient bw to signal. This will only delay the process, and does not fail them to resignal with new bw. PR1125323

Routing Protocols

  • BFD sessions (both PPMAN and TOE based sessions) using firewall daemon (dfwd) for steering Rx packets to Anchor Packet Forwarding Engine with NSR configured may flap post switchover. This is restricted to PTX Series platforms with FPC 3 equipped. The issue is seen only with BFD over AE and multi-hop BFD sessions. PR1112218
  • When we have two paths for the same route, the route gets pointed to Unilist NH, which in turn gets pointed to two separate Unicast NHs. The route is determined by OSPF and we have BFD enabled on one of the paths which runs through an l2circuit path. When the link on the l2circuit gets cut, the link flap is informed by BFD as well as through OSPF LSAs. Ideally the BFD should inform the link down event before the OSPF LSA. But at the current situation, the OSPF LSAs update the current event a second before BFD. Due to this reason, we do get the route to be pointing to a new UNILIST NH with the weights swapped. But the Unicast NH for which the L3 link is down, gets added to the Unilist NH, the BFD assumes the link to be up, and hence updates the weights inappropriately and hence we do see traffic loss. Once the BFD link down event is processed at the OSPF protocol level, now the route points to only Unicast NH and we do see traffic flowing through the currently active link. The traffic outage would be hardly for less than a second during FRR. Also, this can be avoided if the BFD keepalive intervals are maintained around 50 ms with multiplier of 3 as opposed to 100 ms with a multiplier of 3. PR1119253
  • On dual-Routing Engine platforms, in scaling scenario (e.g., there are 6 million routes on "old" master Routing Engine), if graceful Routing Engine switchover (GRES) or graceful restart (GR) is not enabled, the routing protocol process (rpd) may crash on the "old" master Routing Engine after performing Routing Engine switchover. As a workaround, if possible, rebooting the "old" master Routing Engine (new backup Routing Engine) after switchover could avoid the issue. PR1128023

Related Documentation

Modified: 2017-03-22