VMWARE-VMINFO-MIB

Monitored by Observium
        This MIB module provides for monitoring of inventory and state via polling
and notifications of state changes for virtual machines residing on
this host system.  This MIB module also provides a mapping beween SMI
managed objects defined here and their corresponding VMware Virtual
Infrastructure Management (VIM) API properties.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Discovery
Explore Observium network monitoring
Source file
VMWARE-VMINFO-MIB
Last revised
Identity
vmwVmInfoMIB
Base OID
1.3.6.1.4.1.6876.2.10
Imported Objects
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DisplayString PhysAddress
VMWARE-ENV-MIB vmwESXNotifications
VMWARE-ROOT-MIB vmwTraps vmwVirtMachines
VMWARE-TC-MIB VmwConnectedState
Net-SNMP examples using the vmware MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'VMWARE-VMINFO-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-VMINFO-MIB::vmwVmInfoMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'VMWARE-VMINFO-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'VMWARE-VMINFO-MIB::vmwVmInfoMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (50)
7 directly used by Observium
vmwVmTable OBS ✓
.1.3.6.1.4.1.6876.2.1
.1.3.6.1.4.1.6876.2.1.1
Integer32
.1.3.6.1.4.1.6876.2.1.1.1
vmwVmUUID OBS ✓
OctetString
.1.3.6.1.4.1.6876.2.1.1.10
.1.3.6.1.4.1.6876.2.1.1.2
.1.3.6.1.4.1.6876.2.1.1.3
vmwVmGuestOS OBS ✓
.1.3.6.1.4.1.6876.2.1.1.4
vmwVmMemSize OBS ✓
.1.3.6.1.4.1.6876.2.1.1.5
vmwVmState OBS ✓
.1.3.6.1.4.1.6876.2.1.1.6
vmwVmVMID obsolete
.1.3.6.1.4.1.6876.2.1.1.7
.1.3.6.1.4.1.6876.2.1.1.8
vmwVmCpus OBS ✓
.1.3.6.1.4.1.6876.2.1.1.9
.1.3.6.1.4.1.6876.2.10
.1.3.6.1.4.1.6876.2.10.2
.1.3.6.1.4.1.6876.2.10.2.1
.1.3.6.1.4.1.6876.2.10.2.2
.1.3.6.1.4.1.6876.2.2
.1.3.6.1.4.1.6876.2.2.1
Integer32
.1.3.6.1.4.1.6876.2.2.1.1
Integer32
.1.3.6.1.4.1.6876.2.2.1.2
.1.3.6.1.4.1.6876.2.2.1.3
.1.3.6.1.4.1.6876.2.2.1.4
.1.3.6.1.4.1.6876.2.3
.1.3.6.1.4.1.6876.2.3.1
Integer32
.1.3.6.1.4.1.6876.2.3.1.1
Integer32
.1.3.6.1.4.1.6876.2.3.1.2
.1.3.6.1.4.1.6876.2.3.1.3
.1.3.6.1.4.1.6876.2.4
.1.3.6.1.4.1.6876.2.4.1
Integer32
.1.3.6.1.4.1.6876.2.4.1.1
Integer32
.1.3.6.1.4.1.6876.2.4.1.2
.1.3.6.1.4.1.6876.2.4.1.3
.1.3.6.1.4.1.6876.2.4.1.4
vmwVmNetConnType obsolete
.1.3.6.1.4.1.6876.2.4.1.5
.1.3.6.1.4.1.6876.2.4.1.6
.1.3.6.1.4.1.6876.2.4.1.7
.1.3.6.1.4.1.6876.2.5
.1.3.6.1.4.1.6876.2.5.1
Integer32
.1.3.6.1.4.1.6876.2.5.1.1
Integer32
.1.3.6.1.4.1.6876.2.5.1.2
.1.3.6.1.4.1.6876.2.5.1.3
.1.3.6.1.4.1.6876.2.5.1.4
.1.3.6.1.4.1.6876.2.6
.1.3.6.1.4.1.6876.2.6.1
Integer32
.1.3.6.1.4.1.6876.2.6.1.1
Integer32
.1.3.6.1.4.1.6876.2.6.1.2
.1.3.6.1.4.1.6876.2.6.1.3
.1.3.6.1.4.1.6876.2.6.1.4
.1.3.6.1.4.1.6876.50.101
.1.3.6.1.4.1.6876.50.102
Dependencies (7) 6 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-CONFrfc
  3. SNMPv2-TCrfc
  4. VMWARE-ROOT-MIBvmware
  5. VMWARE-PRODUCTS-MIBvmware
  6. VMWARE-TC-MIBvmware
  7. VMWARE-ENV-MIBvmware
  8. VMWARE-VMINFO-MIBvmwareselected
Conformance Groups (3)
Compliance Statements (1)

OID .1.3.6.1.4.1.6876.2.10.2.1.2
The compliance statement for entities which implement the
VMWARE-RESOURCE-MIB.
Required groups
Notifications / Traps (5)
NameOIDDescription
.1.3.6.1.4.1.6876.4.1.0.1
This trap is sent when a virtual machine is powered on from a suspended
or a powered off state. The origin of this event can be several:
for instance may be operator initiated, existing vmx process reconnects to control subsystem.
NOTE: vms powered up due to VMotion are not reported. Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status.
.1.3.6.1.4.1.6876.4.1.0.2
This trap is sent when a virtual machine is powered off. The origin of this event can be several:
for instance may be operator initiated, vmx process terminating abnormally. NOTE: vms powered down due
to VMotion are not reported. Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status.
.1.3.6.1.4.1.6876.4.1.0.3
This trap is sent when a virtual machine detects a loss in guest heartbeat. The Guest heartbeat
is only sent if VMware Tools are installed in the Guest OS. Control process will send this event whenever it
determines the number of guest heartbeats for a given period of time have not been received.
Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status.
.1.3.6.1.4.1.6876.4.1.0.4
This trap is sent when a virtual machine detects or regains the required number of guest heartbeats
for a given period of time. This is only sent if VMware tools are installed in the Guest OS.
Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status.
.1.3.6.1.4.1.6876.4.1.0.5
This trap is sent when a virtual machine is suspended. The origin of this event may be several: operator
initiated, by software api clients, and by other means.
Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status.