Open Issues

New alarm is reported for 3 consecutive failures on a particular fan tray (this can be power or fan-fails). PR1500920

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

FPC core files get stuck in /var/lib/ftp/in/. Sometimes when the core files from multiple FPCs are generated, core files from one FPC might get left behind in /var/lib/ftp/in and are not processed by core-mgr. If the show system core-dumps shows some older core files in /var/lib/ftp/in/fpc-hostname and core files newer than those appear in /var/core/node-name, it indicates this issue was hit. PR1522404

In Junos OS Evolved 20.3, fabsopke-fchip core file can be seen if fabsopke-fchip restart and sib offline happens one after the other with in the same minute. Any previous alarm does not get cleared. PR1525577

If a filter that has more than 8000 IPv6 prefix match statements is modified, it could lead to unexpected behavior. This is because a filter with more than 8000 IPv6 prefix matches occupies more than 50% of filter memory space available in the ASIC. When an active filter's configuration is updated, the software tries to program a new filter before deleting the old filter. In this particular case because the filter under question requires more than 50% of system's total filter memory, the new filter can not be programmed without deleting the old filter. Software does not handle this situation gracefully currently and this could lead to unexpected behavior. The workaround is to unbind the filter from all interfaces it is applied on, make the necessary updates to the filter configuration and then apply the filter back to the interface(s). PR1530597

The interrupt dp_xx_viqm_intr_req_enq_err might surface up intermittently in the logs, but it can be safely ignored as it surfaces up mostly for a number of scenarios which would not have any service impact. Because of the design of the underlying silicon this interrupt cannot be completely avoided which would have absolutely no service impact in almost all scenarios unless joined by a few other severe interrupts. PR1553943

Junos OS Evolved based PTX Series platforms sees incomplete objects anomalies with scale beyond 16,000 logical interfaces in the system. PR1573994

With Junos OS Evolved on PTX10001-36MR or PTX100008 platforms, when the scheduler configuration is not applied to all 8 egress queues of an interface and one or more egress queues have buffer size remainder configuration, the distribution of buffer to egress queues with buffer size remainder is not distributed correctly, which might lead to unexpected tail drops. PR1575798

On Junos OS Evolved platforms, CB <slot> becomes Fault Standby after issuingrequest node power-off re slot on master re slot. The correct CB state is offline. This applies to PTX10004. PTX10008, and PTX10016 slots. PR1581476

On all PTX Series platforms running Junos OS Evolved, addition or deletion of the filter configuration in loopback interface might result in error messages with some packet drop for short duration, which might be self-recovered. PR1589296

VM core file is observed only once and that too after performing NSR switchover for 42 times. PR1590372

Transient traffic drop is seen during MBB of RSVP LSP without optimize-adaptive-teardown delay 60 configuration statement. PR1590656

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

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

PTX10008 : PDT: On loading different configurations, we see the following in the backup Routing Engine: RPD_KRT_KERNEL_BAD_ROUTE: krt unsolic client.128.0.0.5+62000: lost ifl 0 for route. PR1612487

After system reboot or power cycle, a few fabric links showing init CRCs is expected with Gen3/Gen5 fabric connectors. They do not indicate any issue as long as the CRC count is not incrementing with time. A higher corrected Tmax value after system reboot is not an indication of bad link. However, if you see links in FAULT or links showing incrementing CRCs after system reboot, the recommendation is to try graceful OIR for the affected FPC. PR1613214

With Gen3 fabric connectors, it is possible that a few fabric links come up in FAULT or show incrementing CRCs. Normally, this type of issue starts happening after a FPC/SIB reset event. And it might continue even after the FPC goes offline or online or system reboot. Please try gracefully resetting the affected FPC to recover from the issue. PR1613559

The errors are displayed with following next-hop hieINH->COMPNH->UCAST->AE_IFL. During aggregated Ethernet logical interface flaps control detects and initiates MBB. It is possible that Packet Forwarding Engine can see an compNH->ucast with aggregated Ethernet logical interface down resulting into these error messages, howevera this is only transient. There is no functionality impact due to these error messages. PR1617388

Traffic loss observed on BGP-LU paths after restoring primary paths in setup with IGP/LDP RLFA enabled. PR1619229

On scaling system, load override and commit of baseline cfg causes the rpd to spin high on CPU. As the GRPC configuration is removed as well, sensors needs to be uninstalled. However, the rpd does not respond to these telemetry sensors uninstallation requests. So sensors uninstallation fails. Later when GRPC is enabled back on the box and same sensor profile ( cfg .json file used with jtimon) is requested from the collector, rpd sends packets with higher sequence numbers (Because sensor was not removed from rpd earlier) and this is considered as drops by collectors which rely on sequence-numbers. PR1621347

PTX10008 routing subsystem does not run with warm-standby option enabled. After configuring the warm-standby option, please wait for 3 minutes before performing a Routing Engine switchover. PR1623601

In a working and non-working logs, l2d index is different for vrrp group number 187. This is the same group for which packet gets dropped out of 400 groups, other groups work as expected. So there is some fix between working and NKWR related to l2dId which has exposed VRRP issue. Both VRRP MAC and interface MAC gets stored in SLU my_mac_hash table. For finding hash index for vrrp mac we use l2dId, protocol type and vrrp group number as a key. In a non-working scenario there is a collision between interface mac and vrrp mac on same hash index. Ideally hash movement should happen to address collision, however somehow it is not properly done. PR1633986

MTS-MCAST: [PTX10003] Auto RP base verification fails with multiple RPs with same group range.PR1634982

Due to DDoS protection on bandwidth and burst size limit, copying of files to the RCB over WAN ports is slow. This is observed across all platforms running Junos OS Evolved platforms. If there is a need to speed it up, please increase the DDoS's bandwidth. For details, please refer to the following workaround field. PR1636194

The system ID that is exported must be different for UDP and GRPC/GNMI. In the case of UDP, the system name must be appended with the local IP address. PR1640442

Protocol-specific rewrite rules are not yet supported in Junos OS Evolved products. PR1632134

Rebooting the PTX10003 during a broadcast storm on the management port might cause a fault on the PTX10003. PR1423216

Local switching traffic sequence number are not reset. PR1560111

Junos OS Evolved has the latest gRPC stub functions. gRPC beta stub functions are not supported for on-device scripts. In Junos OS Evolved, there are two different gRPC Python files for each JAPI file. The names of the files are *pb2_grpc.py and *pb2.py. The stub creation functions are present in *pb2_grpc.py. PR1580789

If request system zeroize does not trigger zero-touch provisioning, please re-initiate the ZTP as a workaround. PR1529246

MLDP transit statistics reset after Routing Engine switchover. PR1596395

On PTX series platforms, when express segments are configured with SR-TE (Segment Routing Traffic Engineering) underlay path, the rpd might crash when express segments are deleted or re-advertised. PR1613372

After the fix, programmed filter terms in the hardware is in sorted order based upon terms sequence-id. Please also note that show | display translation-scripts translated-config CLI still displays the filter terms per OC configuration, however hardware programming of filter terms is in sorted order of sequence-id. PR1621620

On Junos OS Evolved Release 20.4R3 platforms, the unsupported configuration of BGP flow spec interface-group exclude might lead to some errors and Packet Forwarding Engine corruption which does not permit filter bind. PR1639391

The default remnant hold time is 300seconds which is not sufficient for this scale (1.7M fib routes, 37K LSPs, jflow enabled). We need to increase this hold time to 600 seconds to avoid any protocol flap during RPD crash or restart set routing-options forwarding-table remnant-holdtime 600.PR1593445

Services resolving over BGP-LUoLDP and BGP-LUoLDP transit stitching that involves 2 labels must enable set routing-options forwarding-table chained-composite-next-hop ingress ldp configuration statement. PR1638259

File delete with regex might fail. However, it works if you use the filename without regex. PR1624562

Configd might not clean up shared pointers in DDS as seen in the output of show platform object-info anomalies app configd. There is no functional impact of these anomalies and these can be cleared by restarting configd from CLI using the command restart configd .PR1641960

If after any configuration commit an anomaly is seen for configd in the output of show platform object-info anomalies app configd, it means that the application configd has not released the shared pointer after deleting the published object. This has no functional impact and the anomaly can be cleared by restarting app configd using the command show platform object-info anomalies app configd .PR1643192

Improper XML might be displayed when there is a protocol violation. Tag ddos-protocol-group might be skipped from the display due to which the command's output is not rendered properly. The command show ddos-protection protocols violations | display xml provides enough information to figure out which protocol is being violated. PR1647046