Open Issues

On all the platforms with BGP SR-TE (Spring-TE), in segment routing topology the transit v4 traffic might have missing labels and might get dropped in first hop, when ingress is forwarding traffic. It might miss out all the labels except the last hop in the v4 traffic forwarded by NH interface. PR1505592

VSTP vport scale crosses 3500 leading to VSTP convergence issues due to BPDU drops in packetio of the Packet Forwarding Engine. This issue can be solved by adding DDOS configuration to support the increased scale. PR1509685

BGP-SRTE binding-sid with more than one label stack needs enhancement for PTX10003-80C PTX10003-160C. For PTX Series does not support more than 1 chain-composite-next-hop, it can configure this CLI configuration statement to disable chain-composite-next-hop as a workaround. With this configuration statement configured, all labels are pushed from egress.

PR1512213

The SR-TE label with BSID traffic gets dropped in PTX10003. Please use the following configuration statement as a workaround:

PR1529933

GRES is not supported when FPCs are restarted. PR1539685

Issue the CLI command show system fabric app-status to see list of fabric applications that are running in the system and fetch the application status using the right application name. PR1540706

On PTX10008 with inherit VRRP configuration some of the sessions might take longer time to converge. And during this period we see traffic loss for those sessions. So if system has inherit sessions configured then it is recommended to reduce the inherit advertisement interval timer to 6 seconds to avoid traffic loss. Default value of the inherit time is 120 seconds. PR1571339

For input subscription paths containing a ":" character, the extension header in case of GNMI and certain fields for the show network-agent statistics CLI has incorrect values. PR1581659

sflow ingress sampling does not work for user IPv6 traffic with aggregated Ethernet ECMP case at last hop router with UHP LSP. PR1582960

IPv6 based PKID enrollment operations are not supported over revenue ports on Junos OS Evolved platform.PR1584378

Used-power and allocated-power leaves for telemetry under /components path are currently shown as "0" for all FRUs. PR1587184

On all Junos OS Evolved platforms configured with PIM (Protocol Independent Multicast) and MoFRR (Multicast-only Fast Reroute), a brief multicast traffic drop might be observed towards the downstream receiver after performing Routing Engine switchover or restart of rpd with GRES (Graceful Routing Engine Switchover) and warm-standby enabled.PR1593810

Explicit fault trigger while Packet Forwarding Engine is in transition is not supported. Once Packet Forwarding Engine is in FAULT, Packet Forwarding Engine restart does not recover the Packet Forwarding Engine. PR1596476

The [Error]Jexpr: cannot find ifToken for counterType:12 has no impact on the operation of the system and can be safely ignored. Nothing needs to be done if this error is seen. PR1597355

With QFX5220-32CD interconnected to PTX10008 chassis line card, intermittently issue is seen where 100G SR4 optics link does not come up or flaps, and continuously increasing FEC errors are seen on the PTX Series end. PR1597528

Major host 13 Ethernet interface link down false alarm is seen after Routing Engine 1 replacement manually. PR1597763

When all Packet Forwarding Engines go offline and are brought online with multicast route being active during this cycle, multicast traffic is permanently lost due to the absence of mcast route. PR1598894

Due to issue in AGEOUT notification for inline sessions, sessions remain up till peer sends BFD down packet or BFD client brings it down. PR1599257

Do not restart fabric hub and fabric spoke applications during the FPC offline or online event. Wait for the FPC to be in stable state, before restarting the application. PR1600094

On PTX10008 routers, the set chassis redundancy routing-engine 1 master command does not change the default Routing Engine election priority. PR1601430

In PTX10008, at times, MVRP enabled trunk ports can go into blocked or designated state if the peer connected to the interface has no VLANs configured in its trunk port. PR1601915

If multiple Packet Forwarding Engines are brought online rapidly using the request chassis fpc x pfe-instance y online | restart, it might cause evo-aftmand to terminate and the FPC to reboot. PR1602035

On PTX10003, IRB ping fails post powering off and on underlying Packet Forwarding Engines for Aggregate Ethernet child member. PR1602181

Powering off Packet Forwarding Engines gives error messages Jexpr: deleteFdbEntry: Null. This happens when any of FPC has all the Packet Forwarding Engines go offline but the FPC is online and there are some routes deleted from the control plane. It does not affect any functionality. PR1602670

Slow counters (off-chip) used for ingress nexthops might not work. PR1603518

Due to the product limitation of the PTX10008 and PTX10001-36MR having to communicate between COSIM and CDA running in different VMs, periodic counter reads induce the large delays in a scale configuration. This scale scenario needs to be executed on a hardware setup. PR1603975

When using a source IP address as the management address of the box to ping a network address on a peer, the response for the ICMP ping from the peer, can end up on the management interface of the box, which is dropped by the Linux kernel as the RPF check is set to strict by default on the Linux kernel used on Junos OS Evolved. The Linux kernel expects the path to the peer to be on the WAN side and so drops the packet when it is received on the management interface from the peer when the RPF check for the management interface is set to strict. PR1498255

The alarm Host 0 Active Disk Usage Exceeded might be generated due to large files which were already marked as deleted. PR1601251

The show platform object-info anomalies summary CLI command may time out after the system is up for some time. This does not affect normal operation of the system but this debug command will not work.

Should the marvd daemon restart for any reason, the device becomes unreachable because of PCI uncorrectable non-fatal AER errors getting generated on marvd restart and system goes for reboot without any core. This is a rare event that occurs if there marvd crashes. PR1600870

This scenario happens when we enable IS-IS authentication key-chain having multiple keys between routers. The IS-IS adjacency is up because both the routers have the same key active. When we manually change the system time in such a way that routers have different keys active in the key chain, the IS-IS adjacency should go down. However, that is not happening. PR1572441

If an inet filter is configured with or without family statement then changing its configuration to without or with family statement might cause the filter process (firewalld) to restart unexpectedly. PR1556426

Post request system zeroize operation, sshd service is not enabled by default due to race condition on PTX10008. Hence it is recommended to enable edit system services ssh as part of the first commit on the device so that user 'ssh' credentials are created properly on the device and there is no need for password to log in to the backup Routing Engine. PR1594258