do i understand it right that VMware MIB fixes are due in the next NPM service pack? that is, where i can see LUN volumes, disk info, .etc?
These are not "fixes". Monitoring LUNs, etc. would constitute a feature because we've never provided that functionality. Expanding the vmware features is something we're considering.
thanks. the LUNs work great with the Windows OS and Orion - but it is a big issue with VMware across the board.
i'm struggling trying to make use of UnDP to work with VMware drives - Orion does not see native drives in VMware - is this correct or am i missing something?
on another issue:
how about the CPU issue with VMware 3.0.x - this is really beating me up with reports to management. is there a fix for that coming soon? thanks again...
I would also love to see some additional monitoring for ESX disk I/O. All of our ESX storage is SAN based, so monitoring I/O for HBAs is becoming critical for us.
I'd also be happy if there were some UnDPs for drive space utilization on our vmfs volumes.
I would like to have the same functionality on the VMware ESX details for the disk table as we get now for the CPU, Memory, and Network. The OID's are easy enough to pull, but it is the assoication with a particular VM and transforming the data from the counter that it is into a useful "gauge" that would be much appreciated.
$oids = array(
"hbaname" => ".126.96.36.199.4.1.68188.8.131.52.2",
"numreads" => ".184.108.40.206.4.1.68220.127.116.11.5",
"kbread" => ".18.104.22.168.4.1.6822.214.171.124.6",
"vmid" => ".126.96.36.199.4.1.68188.8.131.52.7",
"displayname" => ".184.108.40.206.4.1.68220.127.116.11.2",
"hbavmid" => ".18.104.22.168.4.1.6822.214.171.124.3",
"index" => ".126.96.36.199.4.1.68188.8.131.52.1",
"numwrites" => ".184.108.40.206.4.1.68220.127.116.11.7",
"kbwritten" => ".18.104.22.168.4.1.6822.214.171.124.8"
If we knew where to write the custom SQL we could do it ourselves. We are just learning all this stuff ourselves.