Resolved Issues in 19.1R2
This section lists the issues fixed in this release.
On VMX in subscriber scenario, RIOT core files might be observed on the VMX instance. The respective FPC might reboot after generating the RIOT core file. All the traffic or service through that FPC are impacted. PR1409527
On vMX on vmware (ESXI) instances, continuous disk error logs requesting for switchover due to disk failure on ada1 are seen on vCP console, even when there was no disk failure. PR1424771
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 in subscriber scenario with two loopback devices, traffic loss might be observed if rebooting the FPC when SI (inline service interface) or LT (logical tunnel) interface is used with scheduling. Note that the loopback devices are created on the VMX instance using the command set chassis fpc 0 loopback-device-count id PR1456268.