Any ideas what that means?
This is a VM so there's no physical disk error.
VMs are on same machine, in it's own port group.
Is the Hyperviser used is ESXi ? Also can you share the comple log messages noticed.. are this messages seen on console?
What is the vMX version you are using?
Yep. ESXi on 19.1
How do I get the log file? asusming on the vfp?
You can share the screenshot of the error message... Are this errors noticed on vCP or vFP ?
What is the ESXi Version used?
we have the same behaviour.
vMX-Versions with this behaviour: 19.1r1.6, 18.4r1.8, 18.4r1-s2.4ESX-version: 6.5
We can see this error only on the vcp-vm, vfp is working normal.
vcp is freshly deployed, without any config-change.
This is know issue on 18.4,19.1 releases on vMX . We have a fix applied to latest release under this branch, Fix will be avilabe in 18.4.R2 & 19.1R2.
when will this version be released?
Does the error has any implications on a production system?
18.4R2 is expected by mid of June'19..
19.1R2 is expected by mid of October'19.
There should not be any impact on the box.
I had the same issue. Thank you - 18.4R2.7 booted for me.
© 1999 - 2019 Juniper Networks, Inc.
All rights reserved