Upgraded to 9.5 from 9.1, and as with the last upgrade the "Virtual Machine Details" does not populate, nor does this category appear in the selected Node Details page, even though it is listed as a resource. Could somebody steer me to a solution?
Can you provide some more info as to what you are seeing or not seeing?
I will will use your NPM DEMO "labvm.aus.lab" as a comparison, since this is what ours looked like before updating to NPM 9.5.
http://oriondemo.solarwinds.com/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:433
When I select lebvm.aus.lab demo from the "home" page I am taken to ESX server details. At the bottom I see various metrics about the guests running on that ESX. Prior to our upgrade we had the same graphs for each VMWare guest at the bottom and top of the page, now nothing. Some DO show the expected Virtual Machine information, while others do not? Operator error?
Hmm that is odd, mine work on 9.5 here. Did you change anything recently on your ESX boxes? Are they running 3.5? If nothing has changed, might be best to open a support ticket as they should still work
The only thing that changed was that I upgraded to the newest version. This happend the last time we upgraded as well. I will call support tomorrow. Thanks for the responses.
From Dev:Memory usage from guest is the value reported to us from the ESX server. Of the RAM on the ESX server, how much RAM is actually being used by the VM from the ESX server’s perspective.Under disk volume, the "physical memory" is a value acquired from the Windows server itself. The Windows server “doesn’t know” that it is a VM. The ESX server lets it behave like a normal server. According to the Windows server it is using that much of its physical memory, as you show in the other screenshots. It has only 63 MB of available RAM. That value is not calculated, but is a value returned from an SNMP query to the Windows server itself.The memory utilization from the Windows server gives the memory utilization from the Windows server perspective – what the Windows server believes it is using of physical memory. High memory utilization here means that the Windows machine believes it is using a lot of its memory. Due to the complex nature of the ESX server, it is able to give RAM to a machine that doesn’t actually reside in the actual RAM of the physical machine. Thus, the value of the ESX server is that you can have more virtual RAM than actual physical RAM. The value from the ESX server is important as a whole. The ESX server reports all the RAM utilizations from all the VMs and should be monitored independently of the independent machines. Both values are important and should be monitored as such. When the Windows Server believes it is using a lot of RAM, then you will have performance issues. If all the VMs on your ESX server are using a lot of RAM, your ESX server and possibly the VMs on the ESX server might have performance issues. Monitor them both. Here is a useful link to understand how this technology works on the ESX server: vmetc.com/.../
