Resolved Issues
This section lists the issues fixed in this release.
On vMX, you might not unable to view the generated cores using the show system coredumps command output, when you use a host with a host name that includes a period (.). PR1474118
On vMX instance, after every commit, the following error message is displayed in the log.
content_copy zoom_out_mapchassisd[7836]: %DAEMON-3-CHASSISD_IOCTL_FAILURE: acb_get_fpga_rev: unable to get FPGA revision for Control Board (Inappropriate ioctl for device)
On MX150 and vMX platform, the input errors might be displayed as zero when you use the show interfaces extensive output when there are CRC/Align errors present on the interface. PR1485706
The core.vmxt.mpc0 is seen at 5 0x096327d5 in l2alm_sync_entry_in_pfes (context=0xd92e7b28, sync_info=0xd92e7a78) at ../../../../../src/pfe/common/applications/l2alm/l2alm_common_hw_api.c:1727. PR1430440
On MX150 and vMX platform, VXLAN (Virtual Extensible LANs) packet may be discarded because flow caching does not support VXLAN when flow caching enabled. PR1466470
On MX150 platform running as virtual Broadband Network Gateway (vBNG) or vMX running in pay-as-you-go (payg) service mode, if you upgrade to Junos OS release 19.2R1 and above, all the subscriber services might be unavailable due to license failure. PR1467368
