Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Known Issues

 

Known Issues in 19.1R3

This section lists the known issues in the release 19.1R3.

  • On vMX, unable to see generated cores in the show system coredumps output, when you use a host name that includes a period (.). PR1474118.

  • On vMX, the virtio throughput remains same for multi-queue and single-queue deployments.PR1389338.

  • On vMX-based platforms, when you run the clear pim join instance instance-name all command, it might result in stopping of riot process on the system. PR1409527

Known Issues in 19.1R2

This section lists the known issues in the release 19.1R2.

  • 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

Known Issues in 19.1R1S2

This section lists the known issues in the release 19.1R1S2.

  • On vMX instances, IPv6 is using different unicast MAC address when you configure VRRPv3 for IPv6. PR1449014

Known Issues in 19.1R1

This section lists the known issues in the release 19.1R1.

  • On vMX-based platforms including MX150, when you run the clear pim join instance instance-name all command, it might result in stopping of riot process on the system. PR1409527.