Open Issues

On a Junos OS Evolved system, with EVPN VXLAN enabled, if there is a default route in primary instance pointing to management interface, it could result in anomalies in Junos OS Evolved database. PR1622035

In Junos OS Evolved 21.1R1, BFD is not supported for ACX7100. The error message Invalid RPC request key: 0x000a0000 is seen when BFD is configured and the respective BFD session comes up. PR1552436

ACX7100-32C : Interface : 400G DAC link does not come up between ACX7100-32C and ACX7100-48L. PR1560431

In some corner cases traffic is not scheduled equally between strict priority queues. This can happen in the following scenario: Priority queue configured and is completely utilizing the bandwidth and remaining queues are starved and traffic completely drops on those queues. In this state if we configure a second strict high priority queue, traffic is not scheduled equally between strict priority queues. This is hardware specific issue, Q2C specific. PR1577035

A restart of DHCP takes more time because of internal issues with the SIGTERM event. PR1610229

After picd or rpdagent app restart multpile object-info anomalies for evo-pfemand, following types of anomalies are seen Type : net::juniper::rtnh::Route Type : net::juniper::rtnh::NHOpaqueTlv Type : net::juniper::rtnh::Nexthop Type : net::juniper::rtnh::Unilist Type : net::juniper::rtnh::BfdSessionId. PR1628843

In a working and non-working logs, l2d index is different for VRRP group number 187. This is the same group for which packet is getting dropped out of 400 groups, other groups are working as expected. So there is some fix which went 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 have happened to address collision but somehow it is not properly done. Going further we need to debug why hash movement is not happening and fix that code area. This code is very sensitive and requires a lot of testing before doing any changes. So we should commit it in DCB first before committing to any other release. PR1633986

File delete with regular expressions might fail. It works if you use filename without regular expressions. PR1624562