Resolved Issues in 18.4R3
This section lists the issues fixed in this release.
On VMX instances deployed in subscriber scenario, RIOT core might be observed on VMX instances. The respective FPC might reboot after generating RIOT core. All the traffic or service related to that FPC are impacted. PR1393660
On vMX instances, the CPU utilization might be around 100% for a process or backup Routing Engine might crash in some specific conditions. PR1437762
On VMX instances, because the host CPU core 0 is not dedicated for virtual instances, it might be used by the other applications. However, VMX's vCPU resource allocation starts from core 0. When the usage of core 0 is high, the VMX instance might get less resource, which might lead to packet drop. PR1449289
On VMX platform running in SR-IOV (single-root I/O virtualization) mode with the vlan-offload option enabled, the input-vlan-map option might not work correctly. PR1460544
