vmware esxi mibs文件

Document: SNMP Agent Notifications for ESX and vCenter up to vSphere 6.5 Security: none Author: mrm@vmware.com <Michael R. MacFaden> Date: : Wed Oct 5 10:38:57 PDT 2016 Version: 1.12 Source: http://communities.vmware.com/community/developer/forums/managementapi Introduction: Notifications on ESXi, NSX and VCSA are composed from IETF standard and VMWARE enterprise MIB module documents. ESXi may also generate 3rd party notifications from any vib/CIM providers installed. They may generate OEM events using their enterprise oids. All VMware MIB modules are compatible back to ESX 2.0, always load the latest set to manage all vesions of ESXi and ESX Classic. The VMWARE-OBSOLETE-MIB contains any obsolete objects and would be loaded when running older versions of software. See the VMWARE-*-AGENTCAP-MIB for which releases of code provide what versions of MIB modules. Here is a summary of the MIB modules that define notifications which are sent on the wire as either SNMPv1 Trap Protocol data units (PDUs) or SNMPv3 Trap PDU for VCSA and ESXi, NSX only supports V2c traps in its first release. See their VMWARE-NSX-AGENTCAP-MIB for details. Example output is also provided. Configuring notifications: William Lam wrote up how to configure trap/inform here for ESXi. http://blogs.vmware.com/vsphere/2012/11/configuring-snmp-v1v2cv3-using-esxcli-5-1.html Documentation for VCSA SNMP agent: VCSA https://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.vcsa.doc/GUID-3695CE84-C6DF-497E-BA4E-2B341CC366C5.html Documentation, 5.1, 5.5, 6.0 for CLI http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.monitoring.doc%2FGUID-346CDDC6-8928-466F-A356-C8DAA6112439.html Configuring NSX: https://www.vmware.com/support/pubs/nsx_pubs.html Current VMware KB Aricles on SNMP: * Downloading MIB modules http://kb.vmware.com/kb/1013445 * Listing of all OIDs by type, mib module and name: http://kb.vmware.com/kb/2054359 * Debugging notification (trap/inform) reception http://kb.vmware.com/kb/2035445 * Configuring SNMPv3 inform remotre users in ESXi SNMP agent: http://kb.vmware.com/kb/2033377 * Reverse Poll Feature aka SNMP Trap is repeated every 5 minutes http://ikb.vmware.com/kb/2020271 * Timeouts and SNMP https://ikb.vmware.com/kb/2100602 * Timeouts in ESXi snmp in storage apis: https://ikb.vmware.com/kb/2105674 * Understanding Layer 2 networking as reported by ESXi SNMP http://kb.vmware.com/kb/2118059 * Monitoring VCSA using SNMP (2145018) http://kb.vmware.com/kb/2145018 VMworld 2016 information: http://blogs.vmware.com/vsphere/2016/08/vmworld-2016-vcenter-server-sessions.html Session Title: Understand the role SNMP agents play in a VSPHERE Stack http://vmware.mediasite.com/mediasite/Play/4eab4abb038344f98c2c1e6ef8b7e2fa1d?catalog=dbf1ec28-2557-4dd3-a381-e5fe4ceabc40 Since ESXi 5.x, snmp agent should now be configured with 'esxcli system snmp' instead of vicfg-snmp script. the vicfg-snmp script is found on VCSA appliance in the bash shell and snmp.set command in the appliancesh shell. vicfg-snmp will continue to work. The vicfg-snmp uses VIM API objects will only ever support SNMPv1. The command line flags have been preserved from the RCLI to esxcli this allows for easy substitution of 'vicfg-snmp' to 'esxcli system snmp' for example: esxcli system snmp --hwsrc sensor esxcli system snmp --no traps <oid[,oid]> # see list of oids in Appendix A below esxcli system snmp set -t 192.0.2.1/mytesttrapcom --enable 1 # turn on snmp agent and sent traps to one destination. # SNMPv3 support for informs has been available since ESX 5.1, with no security (noAuthNoPriv) # is equivalent to SNMPv1 # To define a user and inform target for that user esxcli system snmp set -u john_doe/-/-/none -i 192.0.2.1@1162/john_doe/none/inform Configuring notifications with RCLI command (ESX 3.x to ESX 5.0): First one provides a backward compatibility switch for VMWARE-ENV-MIB for ESX releases prior to 5.0 use the cmd: vicfg-snmp --hwsrc sensors # switch to pre-ESXi 5.0 notifcation format Second, one can now filter out/stop sending notifications. Just provide the oid in the form enterprise.0.trapid vicfg-snmp --notraps 1.3.6.1.4.1.6876.1.0.302,1.3.6.1.4.1.6876.1.0.303 ESXi NOTIFICATIONS: SNMPv2-MIB (http://www.ietf.org/rfc/rfc3418.txt) coldStart -- sent when ESX reboots warmStart -- sent when vmware-hostd process restarts IF-MIB (http://www.ietf.org/rfc/rfc2863.txt) linkDown -- Physical interface changed to down state linkUp -- Physical interface changed to down state When one receives these notifications, they will contain the ifIndex which when used to poll the ifTable shall see the following managed objects change state: ifLastChange, ifSpeed, ifOperStatus change state) VMWARE-VMINFO-MIB vmPoweredOn TRAP-TYPE VARIABLES { vmID, vmConfigFile, vmDisplayName } DESCRIPTION "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 vmPoweredOff TRAP-TYPE VARIABLES { vmID, vmConfigFile, vmDisplayName } DESCRIPTION "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." ::= 2 vmHBLost TRAP-TYPE VARIABLES { vmID, vmConfigFile, vmDisplayName } DESCRIPTION "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." ::= 3 vmHBDetected TRAP-TYPE VARIABLES { vmID, vmConfigFile, vmDisplayName } DESCRIPTION "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." ::= 4 vmSuspended TRAP-TYPE VARIABLES { vmID, vmConfigFile, vmDisplayName } DESCRIPTION "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." ::= 5 VMWARE-CIMOM-MIB The sfcbd agent in ESXi starting in ESX 5.0 will send a heartbeat once every 5 minutes. This duration can be changed or disabled within sfcbd or filtered at the snmp agent (see Appendix A) vmwCimOmHeartbeat TRAP-TYPE VARIABLES { vmwEnvIndicationTime } DESCRIPTION "This notification, if the agent is so configured, will be sent on a periodic basis to indicate cimom indication delivery is functioning." ::= { vmwCimOmNotifications 401 } Update the sfcbc configuration etc/sfcb/sfcb.cfg" and add the key "heartbeatInterval" to the number of seconds it should be sent. VMWARE-ENV-MIB Starting with ESXi 5.0, VMware enterprise hardware related notifcations are reported in the specific identifier field of SNMPv1 trap PDU as follow: VMWARE-ENV-MIB vmwEnvHardwareEvent notification 1.3.6.1.4.1.6876.0.301 VMWARE-ENV-MIB vmwESXEnvHa