Dear Mike and all,
Thank you for your description on several metrics I asked. The followings
are the correspondence table of metrics you had sent us to the current
definition of VM-MIB. The metrics that are not contained in VM-MIB is
marked with "*". However, some of them cannot be obtained at
hypervisors without any support of a special tool such as VMware tools
because they are managed by a guest OS. These objects are marked
with "#".
Virtual Machine General Metrics
MachineName name of VM
==> vmName
MachineServer ESX server that hosts this VM
==> vmHvSoftware etc.
MachinePowerStatus power status of the VM
==> vmAdminState, vmOperState
MachineUpTime number of seconds since last boot
==> vmUpTime (But I think we need to clarify that this is uptime
since last boot, but not last migration)
*MachineLastUpdate number of heartbeats received from the VM
==> Need vmware tools? Hypervisors can know whether a CPU is to
scheduled to a guest without heartbeat.
MachineGuestOS fullname of the guest OS
==> vmOSType
*MachineGuestIpAddr IP address of the guest
==> Need vmware tools? ==> ENTITY-MIB?
MachineCPUNum Number of vCPUs in SYSTEM
==> The number of physical CPUs: HOST-RESOURCES-MIB at hypervisor
The number of virtual CPUs: Count entries in vmCpuTable
*MachineResourcePool The Resource Pool this VM is a part of
==> What is resource pool? an ID of hypervisor cluster?
*MachineLastVMotionTime Shows the last time a VM was vmotion
==> discussion-general-1: Do we need to have this? e.g.,
vmLastMigration
*MachineHAEligible Is this Virtual machine protected using Vmware HA
==> discussion-general-2: I don't think it's to be added to
VM-MIB.
*MachineCreatedBy Who Created this Virtual Machine
==> discussion-general-3: This is needed (as SnmpAdminString)? Or
not needed?
*MachineCreatedDateTime When was this Virtual Machine Created
==> discussion-general-4: Whether we add this or not
Virtual Machine Memory
====> In this set of metrics, I may misunderstand the difference between
host, guest, and VM
MemoryTotalSize memory size of the VM in MB
==> vmCurMem? What's the difference from MemoryGuestUsage?
MemoryMaxAlloc amount of memory in MB that the VM can receive
==> vmMaxMem
MemoryMinAlloc amount of memory in MB guaranteed to the MB
==> vmMinMem
*?MemoryHostUsage consumed host memory in MB
==> What's this?
MemoryGuestUsage active guest memory in MB
==> vmCurMem? What's the difference from MemoryTotalSize?
*MemoryHostUtil host memory used as a percentage of the total VM
memory
==> This can be calculated from vmCurMem and hrMemorySize of
HOST-RESOURCES-MIB
*MemoryGuestUtil guest memory used as a percentage of the total VM
memory
==> This an be calculated from vmCurMem and hrMemorySize of
HOST-RESOURCES-MIB?
*#?MemorySwapToFile amount of memory being swapped in KB
==> discussion-men-1: Hypervisor cannot know the swap size on
the guest OS without a special tool, i.e., this metrics is to be obtained from
the agent on guest OSes. So does VMM-MIB need not to have this?
If this means the memory managed by a hypervisor is
swapped to the hypervisor's storage, we need another discussion.
Virtual Machine Processor
*ProcessorIdleTime CPU time spend in wait state (milliseconds)
==> discussion-cpu-1: (wait state?) Related to Jon's proposal
#ProcessorUserTime CPU time spent on user processes (milliseconds)
#ProcessorSysTime CPU time spent on system processes (milliseconds)
==> vmCpuTime (user&sys are combined, because hypervisors do
not distinguish these on a guest OS.)
*ProcessorWaitTime CPU time spent in ready state (milliseconds)
==> discussion-cpu-1: (ready state?) Related to Jon's proposal
*ProcessorUtilization user time as a percentage of total CPU time
==> (calculated from vmCpuTime)
*Processor%Ready ready time as a percentage of total cpu time
==> (calculated from ProcessorWaitTime if newly defined)
Virtual Machine Disk
DiskDescription disk label
==> vmStorageResourceID?
DiskType type of disk (hard disk, floppy, etc)
==> vmStorageMediaType (but floopy is not defined),
vmStorageMediaTypeString
DiskAccess read/write
==> vmStorageAccess
DiskCapacity capacity of the virtual disk
==> vmStorageDefinedSize, vmStorageAllocatedSize
*DiskRemovable true/false
==> discussion-storage-1: whether we need this or not
Virtual Machine Partitions
*#PartitionLabel disk path (c:\, /boot, etc)
*#PartitionCapacity capacity of the disk in bytes
*#PartitionUsedSpace capacity minus freespace
*#PartitionUtilization used as a percentage of capacity
==> (should be HOST-RESOURCES-MIB on guest OS?)
Virtual Machine Network
Description Network device description
==> ifDescr or ifName from vmNetworIfIndex
PhysAddress physical MAC address
==> vmNetworkPhysAddress
Read Count number of packets read
==> ifOutUcastPkts (ifInUcastPkts?) from vmNetworIfIndex
Write Count number of packets written
==> ifInUcastPkts (ifOutUcastPkts?) from vmNetworkIfIndex
Read Rate number of bytes read
==> ifOutOctets (ifInOctets?) from vmNetworIfIndex
Write Rate number of bytes written
==> ifInOctets (ifOutOctets?) from vmNetworIfIndex
Virtual Machine Processes
*#PID Process ID
*#ProcessName ProcessName
*#ProcessParam ProcessParameters
*#ProcessCPUUsage ProcessCPUUsage
*#ProcessMemoryUsed ProcessMemoryUsage
==> (should be HOST-RESOURCES-MIB on guest OS?)
Thank you,
Hirochika
--
Hirochika Asai <[email protected]>, The University of Tokyo
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
