Comments
-
The CPU and Memory details that are stored at a host level per VM are stored historically somewhere in the DB because you can look at them historically in Orion though I couldn't tell you where because I haven't bothered to try and find it. When DRS moves nodes around I would guess that it moves where it's stored because…
-
All of my "data centers" are unmanaged in the DB. Did you create a separate user in VC for NPM? If so, when you assigned the rights for that user did you propagate the user permissions to all of the child objects? When you go to the permissions tab for the DataCenter in VC you should see the user in the permissions tab as…
-
Thanks for the reply. The data that I could use is not stored historically (Details found in VIM_VirtualMachineNodes). The DRS issue shouldn't be a problem as we are polling everything via Virtual Center. The problem is that in larger environments where you are doing IaaS you don't always have the option to manage all of…
-
The best way is to build a LAN 2 LAN VPN tunnel and monitor all of the devices by their actual IP addresses. If you dont have the ability to do that then you would need to do a distributed NPM install (where you have an NPM server at that location). HTH
-
What attributes are you using to define the alert? Also do you have all of the VM's managed in NPM as well as the ESX host?
-
I have opened up a support case on this and the response is basically this: "This is by design. To monitor the CPU Load and Memory of the actual Virtual Machine, you will need to enable SNMP on the Virtual Machine and monitor the device in Orion. If you select the Node it should ask if you would like to monitor the Virtual…
