VMWARE-VC-EVENT-MIB

        This MIB module identifies vCenter Trap notifications (traps or inform).
    
Source file
VMWARE-VC-EVENT-MIB
Last revised
Identity
vmwVCMIB
Base OID
1.3.6.1.4.1.6876.4.3.1
Imported Objects
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
VMWARE-PRODUCTS-MIB vmwVC
VMWARE-TC-MIB VmwLongSnmpAdminString
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-VC-EVENT-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-VC-EVENT-MIB::vmwVCMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'VMWARE-VC-EVENT-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'VMWARE-VC-EVENT-MIB::vmwVCMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (13)
.1.3.6.1.4.1.6876.4.3.0
.1.3.6.1.4.1.6876.4.3.1
.1.3.6.1.4.1.6876.4.3.1.2
.1.3.6.1.4.1.6876.4.3.1.2.1
.1.3.6.1.4.1.6876.4.3.1.2.2
vmwVpxdTrapType obsolete
.1.3.6.1.4.1.6876.4.3.301
vmwVpxdHostName obsolete
.1.3.6.1.4.1.6876.4.3.302
vmwVpxdVMName obsolete
.1.3.6.1.4.1.6876.4.3.303
.1.3.6.1.4.1.6876.4.3.304
.1.3.6.1.4.1.6876.4.3.305
.1.3.6.1.4.1.6876.4.3.306
.1.3.6.1.4.1.6876.4.3.307
Enumeration
.1.3.6.1.4.1.6876.4.3.308
Dependencies (7) 5 direct · 2 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. SNMP-FRAMEWORK-MIBrfc
  5. VMWARE-ROOT-MIBvmware
  6. VMWARE-PRODUCTS-MIBvmware
  7. VMWARE-TC-MIBvmware
  8. VMWARE-VC-EVENT-MIBvmwareselected
Conformance Groups (4)
These objects provide alarm notification details.
.1.3.6.1.4.1.6876.4.3.1.2.2.1
Group of objects describing notifications (traps).
.1.3.6.1.4.1.6876.4.3.1.2.2.2
These objects provide alarm notification details.
.1.3.6.1.4.1.6876.4.3.1.2.2.3
Group of objects describing notifications (traps).
.1.3.6.1.4.1.6876.4.3.1.2.2.4
Compliance Statements (2)

OID .1.3.6.1.4.1.6876.4.3.1.2.1.2
The compliance statement for entities which implement VMWARE-VC-EVENT-MIB.
Required groups

OID .1.3.6.1.4.1.6876.4.3.1.2.1.3
The compliance statement for entities which implement VMWARE-VC-EVENT-MIB.
Required groups
Notifications / Traps (3)
NameOIDDescription
vpxdAlarm obsolete
.1.3.6.1.4.1.6876.4.3.0.201
This notification is sent on entity alarm state change, by the vCenter Server SNMP agent.
This information is also available through the vSphere client, through the Alarms screen,
or through the Managed Object Browser(MOB) interface for alarms at
https://<vCenter Server machine address>/mob/?moid=AlarmManager.
Listing individual objects of a specific type or ID can be done through the PropertyCollector SDK API.
See http://www.vmware.com/support/developer/vc-sdk/visdk2xpubs/ReferenceGuide/vmodl.query.PropertyCollector.html
for details.
.1.3.6.1.4.1.6876.4.3.0.202
This notification is sent on starting or restarting vCenter Server,
on requesting a test notification explicitly, and can also be
configured to be sent periodically at a specified time interval via
vCenter Server configuration by the vCenter Server SNMP agent.
.1.3.6.1.4.1.6876.4.3.0.203
This notification is sent on entity alarm state change, by the vCenter Server SNMP agent.
This information is also available through the vSphere client, through the Alarms screen,
or through the Managed Object Browser(MOB) interface for alarms at
https://<vCenter Server machine address>/mob/?moid=AlarmManager.
Listing individual objects of a specific type or ID can be done through the PropertyCollector SDK API.
See http://www.vmware.com/support/developer/vc-sdk/visdk2xpubs/ReferenceGuide/vmodl.query.PropertyCollector.html
for details.