Esxi 6 update 2 no stats reported under monitoring

digital_janitor

Intel NUC NUC6i3SYH, using vlans and TL-SG108E as the switch on esxi 6 update 2 shows no stats for anything under monitoring. Everything reports 0. Using vxnet3 nics. I have installed esxi 5.5 update 3 on the same hardware and everything works. I confirmed this behavior on both 2.3.2 and 2.2 pfsense.

It's pretty apparent it's an esxi 6 u3 problem to me, but would welcome suggestions.

Thanks!

johnpoz

What shows 0 under monitoring exactly?

Like your traffic - see attached. And what specific build are you running? You say update 2, then you say update 3.. Update 3 is not even out?

So current build is 4192238, and was release 2016-08-04, update 2 which was released on 2016-03-15 is build 3620759 What specific build are you running??

As you can see I am running current build - and I am seeing traffic and everything else in monitoring..

traffic.jpg_thumb

esxibuild.jpg_thumb

digital_janitor

Sorry for the confusion and thank you for the response. I was using both 5.5 u3 and 6.0 u2 so simply swapped those.

I am using build 3620759.

I have attached an image that shows where it was working previously on my old esx server, and now after migrating the vm to a different machine on 6.0u2 it wasn't working.

However, it started working several hours later. Which is baffling.

I am wondering if there is something with openvmtools or something.

Basically it shows 0 for everything for hours, cpu, memory, latency, packets. And then suddenly started reporting.

1.jpg_thumb

digital_janitor

Seems to happen on reboot of the vm as well.

I attached a screen shot, I am guessing some hours from now it will magically start reporting again.

The VM is connected to a portgroup 4095(all) The portgroup is set to promiscuous mode. The pfsense vm does the tagging for 3 vlans 10,20,30. 2 WANs, 1 LAN. All cpu cores exposed, 2GB ram, 8GB of ssd disk.

Untitled3.jpg_thumb

johnpoz

Your actually quite behind for build numbers, the current build is 4510822, which is 3 newer than what your running.

I have been running pfsense on esxi for many years and have never seen such an issue. But then again your issue has ZERO to do be it the pfsense was virtual or on hardware.

You should create your thread in different area, maybe the general area.. What your seeing has zero to do with system being vm or not.