mirror/librenms-librenms
1
0
Fork 0
mirror of https://github.com/librenms/librenms.git synced 2024-10-07 16:52:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updating the mibs file from vmware (#8388)

Browse Source 
The files where retrieved from the vmware provided mibs at
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013445
This commit is contained in:
mikeSimonson
2018-03-21 00:31:14 +01:00
committed by Neil Lathwood
parent 26bcf89b76
commit 607a7f801d
21 changed files with 10231 additions and 889 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
mibs/vmware/VMWARE-AGENTCAP-MIB.mib → mibs/vmware/VMWARE-AGENTCAP-MIB
View File

1
mibs/vmware/VMWARE-CIMOM-MIB
View File

@@ -78,4 +78,3 @@ vmwCimOmNotificationGroup NOTIFICATION-GROUP
END

428
mibs/vmware/VMWARE-ENV-MIB.mib → mibs/vmware/VMWARE-ENV-MIB
View File

@@ -1,5 +1,5 @@
-- **********************************************************
-- Copyright 2008-2010 VMware, Inc. All rights reserved.
-- Copyright 2008-2017 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-ENV-MIB DEFINITIONS ::= BEGIN
@@ -21,7 +21,7 @@ IMPORTS
FROM VMWARE-TC-MIB;
vmwEnvironmentalMIB MODULE-IDENTITY
LAST-UPDATED "201005120000Z"
LAST-UPDATED "201705300000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
@@ -29,10 +29,20 @@ IMPORTS
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://communities.vmware.com/community/developer/forums/managementapi
Web: http://kb.vmware.com/kb/1013445
"
DESCRIPTION
"This MIB module identifies hardware components of a machine as provided by IPMI."
"This MIB module identifies hardware components of a machine as provided by IPMI.
The descriptions in this document will be marked with [1] to refer the IPMI specification here:
https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev1-1.pdf
which provides a definition for IPMI System Event Log (SEL).
"
REVISION "201705300000Z"
DESCRIPTION
"This revision deprecates the previous CIM based implementation. The vmwEnvTable now maps
directly to an IPMI System Event Log allowing for simpler identification and management.
vmwEnvSource.0 will now report ipmi(4) on agents implementing this mib module version."
REVISION "201005120000Z"
DESCRIPTION
@@ -63,36 +73,45 @@ vmwEnvNumber OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of number of conceptual rows in vmwEnvTable"
DESCRIPTION
"Count of number of conceptual rows in vmwEnvTable."
::= { vmwEnv 1 }
vmwEnvLastChange OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"The value of sysUptime when a conceptual row was added
or deleted from this table"
or deleted from this table."
::= { vmwEnv 2 }
vmwSELCapacity OBJECT-TYPE
SYNTAX Integer32 (0..100)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The amount of free space left in the IPMI SEL for new entries."
::= { vmwEnv 30 }
vmwEnvTable OBJECT-TYPE
SYNTAX SEQUENCE OF VmwEnvEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is populated from monitoring subsystems such as IPMI
DESCRIPTION
"This table is populated from monitoring IPMI BMC device.
One conceptual row is maintained for each reporting component.
Conceptual rows are not persistent across device resets"
This table may be cleared by operational request to BMC and
normally is configured to stop adding new entries when full."
::= { vmwEnv 3 }
vmwEnvEntry OBJECT-TYPE
SYNTAX VmwEnvEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
DESCRIPTION
"One entry for each physical component reporting its
status to ESX Operating System"
status to ESX Operating System."
INDEX { vmwEnvIndex }
::= { vmwEnvTable 1 }
@@ -101,22 +120,27 @@ VmwEnvEntry ::= SEQUENCE {
vmwSubsystemType VmwSubsystemTypes,
vmwHardwareStatus VmwSubsystemStatus,
vmwEventDescription DisplayString,
vmwEnvHardwareTime TimeTicks
vmwEnvHardwareTime DateAndTime,
vmwEnvHrDeviceIndex Integer32,
vmwEnvSelSensorNumber Integer32
}
vmwEnvIndex OBJECT-TYPE
SYNTAX Integer32 (1..1000)
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique identifier that does not persist across management restarts"
DESCRIPTION
"This is the identifier as reported by the vendor hardware's BMC
as per Table 32 section 32.1 SEL Event Records [1].
On ESXi: the command: localcli hardware ipmi sel list
can provide the listing of IPMI SEL entries as well."
::= { vmwEnvEntry 1 }
vmwSubsystemType OBJECT-TYPE
SYNTAX VmwSubsystemTypes
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Hardware component reporting environmental state"
::= { vmwEnvEntry 2 }
@@ -124,7 +148,7 @@ vmwHardwareStatus OBJECT-TYPE
SYNTAX VmwSubsystemStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Last reported state of this component"
::= { vmwEnvEntry 3 }
@@ -132,55 +156,154 @@ vmwEventDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Human readable description of this event"
::= { vmwEnvEntry 4 }
vmwEnvHardwareTime OBJECT-TYPE
SYNTAX TimeTicks
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Value of sysUptime when vmwHardwareStatus was obtained"
DESCRIPTION
"Timestamp as reported from BMC for the SEL entry.
See CLI: 'localcli hardware ipmi sel list' for same report.
Note that BMC maintains it own clock and may not be the same
as the time ESX itself reports. On ESX: the CLI command:
localcli hardware ipmi sel get
reports the BMC clock."
::= { vmwEnvEntry 5 }
vmwEnvHardwareEvent NOTIFICATION-TYPE
OBJECTS { vmwSubsystemType, vmwHardwareStatus,
vmwEventDescription, vmwEnvHardwareTime }
STATUS deprecated
DESCRIPTION
"This notification, if the agent is so configured, may be sent when the
system has detected a material change in physical condition of the
hardware"
::= { vmwNotifications 301 }
vmwESXEnvHardwareEvent NOTIFICATION-TYPE
OBJECTS { vmwSubsystemType, vmwHardwareStatus,
vmwEventDescription, vmwEnvHardwareTime }
STATUS deprecated
DESCRIPTION
"ESX Specific version of this notification,
if the agent is so configured, may be sent when
the ESX Operating System has detected a material change in
physical condition of the hardware"
::= { vmwESXNotifications 301 }
-- SNMP notifications based on indications reported by ESX CIM subsystem
vmwEnvSource OBJECT-TYPE
SYNTAX INTEGER {unknown(1), sensors(2), indications(3) }
vmwEnvHrDeviceIndex OBJECT-TYPE
SYNTAX Integer32 (0|1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The source being used to obtain hardware state."
DESCRIPTION
"The Index into hrDeviceTable for the hardware related to this event.
Report 0 if this entry does not have a related entry in hrDeviceTable."
::= { vmwEnvEntry 6 }
vmwEnvSelSensorNumber OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is the BMC reported Sensor Number byte 12 from SEL Event record
as per Table 32 section 32.1 SEL Event Records [1].
IPMI Sensors are reported in hrDeviceTable and vmwEnvTable provides
the mapping to the specific entry there. Also from CLI on ESX the command:
localcli hardware ipmi sdr list
can provide the listing of IPMI Sensors that has entered this SEL record.
"
::= { vmwEnvEntry 7 }
vmwEnvSource OBJECT-TYPE
SYNTAX INTEGER {unknown(1), sensors(2), indications(3), ipmi(4) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies which source being used to obtain hardware state. Sensors were
from host agent process, indications were from CIMOM/cim provider, and ipmi is
when snmpd reads SEL directly from IPMI to obtain hardware events "
::= { vmwEnv 100 }
vmwEnvIPMI OBJECT IDENTIFIER
::= { vmwProductSpecific 25 }
-- IPMI Based Notifications
vmwEnvIpmiSelFull NOTIFICATION-TYPE
OBJECTS { vmwSELCapacity }
STATUS current
DESCRIPTION
"An IPMI System Event Log has fixed amount of entries (65535). This event is sent once when
the managed object vmwSELCapacity reaches 100% capacity at which point new entries
to the SEL will be dropped if overflow is not enabled (default) on most hardware systems.
This event will rearm any time vmwSELCapacity.0 drops below 80%."
REFERENCE "[1] section 31 System Event Log (SEL) Commands"
::= { vmwESXNotifications 390}
vmwEnvIpmiSelMemoryRaised NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A memory related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state asserted.
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] section 32 byte 11"
::= { vmwESXNotifications 400 }
vmwEnvIpmiSelMemoryCleared NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A memory related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state deasserted
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] section 32 byte 11"
::= { vmwESXNotifications 401 }
vmwEnvIpmiSelPowerSupplyRaised NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A power supply related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state asserted.
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] section 32 byte 11"
::= { vmwESXNotifications 410 }
vmwEnvIpmiSelPowerSupplyCleared NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A power supply related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state deasserted
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] section 32 byte 11"
::= { vmwESXNotifications 411 }
vmwEnvIpmiSelFanRaised NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A fan related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state asserted.
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] section 32 byte 11"
::= { vmwESXNotifications 420 }
vmwEnvIpmiSelFanCleared NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A fan related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state deasserted
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] am/.../ipmi-second-gen-interface-spec-v2-rev1-1.pdf section 32 byte 11"
::= { vmwESXNotifications 421 }
vmwEnvIpmiSelCpuRaised NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A CPU related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state asserted.
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] section 32 byte 13"
::= { vmwESXNotifications 430 }
vmwEnvIpmiSelCpuCleared NOTIFICATION-TYPE
OBJECTS { vmwEnvSelSensorNumber, vmwEnvHardwareTime, vmwEventDescription }
STATUS current
DESCRIPTION
"A CPU related IPMI SDR has updated IPMI SEL with record id of vmwEnvIndex with state deasserted
The vmwEnvTable will have an entry at vmwEnvIndex with additional details"
REFERENCE "[1] section 32 byte 13"
::= { vmwESXNotifications 431 }
-- CIM Indication to SNMP notification conversion
vmwEnvInIndications OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of HTTP POST msgs containing CIM Indications in XML as received by agent."
::= { vmwEnv 101 }
@@ -188,7 +311,7 @@ vmwEnvLastIn OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"sysUptime when agent last received an indication."
::= { vmwEnv 102 }
@@ -196,7 +319,7 @@ vmwEnvOutNotifications OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of notifications (traps|informs) sent that originated as CIM indication."
::= { vmwEnv 103 }
@@ -204,7 +327,7 @@ vmwEnvInErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM Indications that agent did not complete receipt of."
::= { vmwEnv 104 }
@@ -212,7 +335,7 @@ vmwEnvIndOidErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM Indications having a MappingString qualifier for which the value was not a valid oid."
::= { vmwEnv 105 }
@@ -220,7 +343,7 @@ vmwEnvCvtValueErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM Indication properties having a MappingString qualifier
for which the cim value for the given cim type could not be converted."
::= { vmwEnv 106 }
@@ -229,7 +352,7 @@ vmwEnvCvtSyntaxErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM Indication properties having a MappingString qualifier
for which the cim type could not be converted to smi syntax."
::= { vmwEnv 107 }
@@ -238,7 +361,7 @@ vmwEnvCvtOidErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM Indication properties having a MappingString qualifier
for which the the oid was not valid."
::= { vmwEnv 108 }
@@ -247,7 +370,7 @@ vmwEnvGetClassErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM GetClass operations over a given cim indication class and namespace
could not be completed (timeout) or returned error."
::= { vmwEnv 109 }
@@ -256,7 +379,7 @@ vmwEnvPropertySkips OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM indications having properties which do not have MappingString qualifier
in the class definition and were not converted, sent along with the notification."
::= { vmwEnv 110 }
@@ -265,21 +388,46 @@ vmwEnvIndicationSkips OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
DESCRIPTION
"Number of CIM indications recieved for which GetClass reported no MappingStrings qualifier
and were not converted to a notification."
::= { vmwEnv 111 }
--- CIM Backed events ----
vmwEnvHardwareEvent NOTIFICATION-TYPE
OBJECTS { vmwSubsystemType, vmwHardwareStatus,
vmwEventDescription, vmwEnvHardwareTime }
STATUS deprecated
DESCRIPTION
"This notification, if the agent is so configured, may be sent when the
system has detected a material change in physical condition of the
hardware"
::= { vmwNotifications 301 }
vmwESXEnvHardwareEvent NOTIFICATION-TYPE
OBJECTS { vmwSubsystemType, vmwHardwareStatus,
vmwEventDescription, vmwEnvHardwareTime }
STATUS deprecated
DESCRIPTION
"ESX Specific version of this notification,
if the agent is so configured, may be sent when
the ESX Operating System has detected a material change in
physical condition of the hardware"
::= { vmwESXNotifications 301 }
vmwEnvCIM OBJECT IDENTIFIER
::= { vmwProductSpecific 30 }
vmwEnvDescription OBJECT-TYPE
SYNTAX VmwLongSnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"A short description of the Indication."
"A short description of the Indication."
REFERENCE
"http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property Description"
::= { vmwEnvCIM 1 }
@@ -287,12 +435,12 @@ vmwEnvDescription OBJECT-TYPE
vmwEnvEventTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"The time and date the underlying event was first
detected. May be set to the time the SNMP agent recieved the notification
"The time and date the underlying event was first
detected. May be set to the time the SNMP agent recieved the notification
if in the incoming CIM indication the value is
NULL due to the creating entity not being capable of providing
NULL due to the creating entity not being capable of providing
this information. This value is based on the notion of
local date and time of the Managed System Element
generating the Indication."
@@ -303,7 +451,7 @@ vmwEnvEventTime OBJECT-TYPE
vmwEnvIndicationTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"The time and date of creation of the underlying Indication received by the snmp agent. The
property may be set to the time SNMP agent received the notification if the entity creating the
@@ -317,9 +465,9 @@ vmwEnvIndicationTime OBJECT-TYPE
vmwEnvPerceivedSeverity OBJECT-TYPE
SYNTAX VmwCIMSeverity
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"An enumerated value that describes the severity of the
"An enumerated value that describes the severity of the
Alert Indication from the notifier's point of view."
REFERENCE
"http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property PerceivedSeverity"
@@ -328,7 +476,7 @@ vmwEnvPerceivedSeverity OBJECT-TYPE
vmwEnvAlertType OBJECT-TYPE
SYNTAX VmwCIMAlertTypes
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"Primary classification of the Indication."
REFERENCE
@@ -338,9 +486,9 @@ vmwEnvAlertType OBJECT-TYPE
vmwEnvSysCreationClassName OBJECT-TYPE
SYNTAX VmwCimName
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"The scoping System's CreationClassName for the Provider
"The scoping System's CreationClassName for the Provider
generating this Indication."
REFERENCE
"http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property SystemCreationClassName"
@@ -349,11 +497,11 @@ vmwEnvSysCreationClassName OBJECT-TYPE
vmwEnvAlertingElement OBJECT-TYPE
SYNTAX VmwCimName
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"The identifying information of the entity (ie, the
instance) for which this notification is generated. The
property contains the CIM path of an CIM object instance,
property contains the CIM path of an CIM object instance,
encoded as a string parameter - if the instance is modeled in the CIM
Schema. If not a CIM instance, the property contains
some identifying string that names the entity for which
@@ -366,7 +514,7 @@ vmwEnvAlertingElement OBJECT-TYPE
vmwEnvAlertingFormat OBJECT-TYPE
SYNTAX VmwCIMAlertFormat
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"The format of the AlertingManagedElement property is
interpretable based upon the value of this property."
@@ -377,7 +525,7 @@ vmwEnvAlertingFormat OBJECT-TYPE
vmwEnvSystemName OBJECT-TYPE
SYNTAX VmwCimName
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"The scoping System's Name for the Provider generating this message."
REFERENCE
@@ -387,7 +535,7 @@ vmwEnvSystemName OBJECT-TYPE
vmwEnvProviderName OBJECT-TYPE
SYNTAX VmwCimName
MAX-ACCESS accessible-for-notify
STATUS current
STATUS deprecated
DESCRIPTION
"The name of the CIM provider, a software module loaded into the CIM subsystem, generating this message."
REFERENCE
@@ -399,8 +547,8 @@ vmwESXEnvHardwareAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A hardware alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 302 }
@@ -409,8 +557,8 @@ vmwESXEnvBatteryAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A battery alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 303 }
@@ -419,8 +567,8 @@ vmwESXEnvChassisAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A chassis alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 304 }
@@ -430,8 +578,8 @@ vmwESXEnvThermalAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A cooling/thermal alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 305 }
@@ -440,8 +588,8 @@ vmwESXEnvDiskAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A disk drive alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 306 }
@@ -450,8 +598,8 @@ vmwESXEnvPowerAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A power suppply alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 307 }
@@ -460,8 +608,8 @@ vmwESXEnvProcessorAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A IPMI processor alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 308 }
@@ -470,8 +618,8 @@ vmwESXEnvMemoryAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"A IPMI memory alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 309 }
@@ -481,8 +629,8 @@ vmwESXEnvBIOSAlert NOTIFICATION-TYPE
OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity,
vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat,
vmwEnvSystemName, vmwEnvProviderName }
STATUS current
DESCRIPTION
STATUS deprecated
DESCRIPTION
"BIOS System Event Log alert as received from the Common Infrastructure Management (CIM) subsystem on this system."
REFERENCE "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof"
::= { vmwESXNotifications 310 }
@@ -496,10 +644,23 @@ vmwEnvMIBGroups OBJECT IDENTIFIER ::= { vmwEnvironmentalMIBConformance 2 }
-- compliance statements
vmwEnvMIBBasicCompliance3 MODULE-COMPLIANCE
vmwEnvMIBBasicCompliance4 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement the
"The compliance statement for entities which implement the
VMWARE-ENV-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwEnvCIMToSNMP, vmwEnvironmentGroup2,
vmwESXEnvNotificationGroup3}
GROUP vmwESXEnvNotificationGroup3
DESCRIPTION
"This group is mandatory for ESX based systems agents."
::= { vmwEnvironmentMIBCompliances 5 }
vmwEnvMIBBasicCompliance3 MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement for entities which implement the
VMWARE-ENV-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwEnvAlertGroup, vmwESXEnvNotificationGroup2 }
@@ -511,7 +672,7 @@ DESCRIPTION
vmwEnvMIBBasicCompliance2 MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for entities which implement the
"The compliance statement for entities which implement the
VMWARE-ENV-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwEnvironmentGroup }
@@ -529,13 +690,33 @@ DESCRIPTION
vmwEnvMIBBasicCompliance MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement for entities which implement the
"The compliance statement for entities which implement the
VMWARE-ENV-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwEnvironmentGroup, vmwEnvNotificationGroup }
::= { vmwEnvironmentMIBCompliances 2 }
vmwEnvCIMToSNMP OBJECT-GROUP
OBJECTS {
vmwEnvSource,
vmwEnvInIndications,
vmwEnvLastIn,
vmwEnvOutNotifications,
vmwEnvInErrs,
vmwEnvIndOidErrs,
vmwEnvCvtValueErrs,
vmwEnvCvtSyntaxErrs,
vmwEnvCvtOidErrs,
vmwEnvGetClassErrs,
vmwEnvPropertySkips,
vmwEnvIndicationSkips
}
STATUS current
DESCRIPTION
"Only needed if protocol conversion between CIM-XML and SNMP is supported."
::= { vmwEnvMIBGroups 20 }
vmwEnvAlertGroup OBJECT-GROUP
OBJECTS {
vmwEnvSource,
@@ -560,14 +741,14 @@ vmwEnvAlertGroup OBJECT-GROUP
vmwEnvAlertingFormat,
vmwEnvSystemName,
vmwEnvProviderName
}
STATUS current
}
STATUS obsolete
DESCRIPTION
"These objects provide physical hardware environmental details as reported by CIM subsystem."
::= { vmwEnvMIBGroups 5 }
vmwEnvironmentGroup OBJECT-GROUP
OBJECTS {
OBJECTS {
vmwEnvNumber,
vmwEnvLastChange,
vmwSubsystemType,
@@ -610,11 +791,44 @@ vmwESXEnvNotificationGroup2 NOTIFICATION-GROUP
vmwESXEnvMemoryAlert,
vmwESXEnvBIOSAlert
}
STATUS current
STATUS deprecated
DESCRIPTION
"ESX System specific notifications about physical subsystems."
::= { vmwEnvMIBGroups 4 }
vmwESXEnvNotificationGroup3 NOTIFICATION-GROUP
NOTIFICATIONS {
vmwEnvIpmiSelFull,
vmwEnvIpmiSelMemoryRaised,
vmwEnvIpmiSelMemoryCleared,
vmwEnvIpmiSelPowerSupplyRaised,
vmwEnvIpmiSelPowerSupplyCleared,
vmwEnvIpmiSelFanRaised,
vmwEnvIpmiSelFanCleared,
vmwEnvIpmiSelCpuRaised,
vmwEnvIpmiSelCpuCleared
}
STATUS current
DESCRIPTION
"IPMI System EventLog specific notifications about physical subsystems."
::= { vmwEnvMIBGroups 10 }
vmwEnvironmentGroup2 OBJECT-GROUP
OBJECTS {
vmwEnvNumber,
vmwEnvLastChange,
vmwSELCapacity,
vmwSubsystemType,
vmwHardwareStatus,
vmwEventDescription,
vmwEnvHardwareTime,
vmwEnvHrDeviceIndex,
vmwEnvSelSensorNumber
}
STATUS current
DESCRIPTION
"These objects provide physical hardware IPMI System Event Log details."
::= { vmwEnvMIBGroups 6 }
END -- end of module VMWARE-ENV-MIB.

1054
mibs/vmware/VMWARE-ESX-AGENTCAP-MIB.mib → mibs/vmware/VMWARE-ESX-AGENTCAP-MIB
View File

File diff suppressed because it is too large Load Diff

80
mibs/vmware/VMWARE-HEARTBEAT-MIB Normal file
View File

@@ -0,0 +1,80 @@
-- **********************************************************
-- Copyright 2016 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-HEARTBEAT-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF
sysUpTime
FROM SNMPv2-MIB
vmwProductSpecific
FROM VMWARE-ROOT-MIB;
vmwHBMIB MODULE-IDENTITY
LAST-UPDATED "201602100000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://communities.vmware.com/community/developer/forums/managementapi
"
DESCRIPTION
"This MIB module provides a reverse poll for systems that do not yet support polling.
See http://kb.vmware.com/kb/2020271 for details on reverse polling in VMware SNMP agents."
REVISION "201602100000Z"
DESCRIPTION
"First version."
::= { vmwHb 66 }
vmwHb OBJECT IDENTIFIER
::= { vmwProductSpecific 190 }
vmwHbNotifications OBJECT IDENTIFIER
::= {vmwHb 0 }
vmwHbHeartbeat NOTIFICATION-TYPE
OBJECTS { sysUpTime }
STATUS current
DESCRIPTION
"This notification, if the agent is so configured, will be sent
on a periodic basis to indicate cimom indication delivery is functioning."
::= { vmwHbNotifications 401 }
-- conformance information
vmwHbMIBConformance
OBJECT IDENTIFIER ::= { vmwHb 2 }
vmwHbMIBCompliances
OBJECT IDENTIFIER ::= { vmwHbMIBConformance 1 }
vmwHbMIBGroups OBJECT IDENTIFIER ::= { vmwHbMIBConformance 2 }
-- compliance statements
vmwHbMIBBasicCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement the
VMWARE-HEARTBEAT-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwHbNotificationGroup }
GROUP vmwHbNotificationGroup
DESCRIPTION
"This group is mandatory for systems without polling enabled."
::= { vmwHbMIBCompliances 4 }
vmwHbNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
vmwHbHeartbeat
}
STATUS current
DESCRIPTION
"Notifications related to snmp agent reverse poll feature."
::= { vmwHbMIBGroups 2 }
END

77
mibs/vmware/VMWARE-NSX-MANAGER-AGENTCAP-MIB Normal file
View File

@@ -0,0 +1,77 @@
-- **********************************************************
-- Copyright 2016-2017 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-NSX-MANAGER-AGENTCAP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI
vmwareAgentCapabilities
FROM VMWARE-ROOT-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF;
vmwNSXAgentCapabilityMIB MODULE-IDENTITY
LAST-UPDATED "201610240001Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://kb.vmware.com/kb/1013445
"
DESCRIPTION
"This module defines agent capabilities for deployed VMware NSX Manager agents by release."
REVISION "201610240001Z"
DESCRIPTION
"Capabilities for NSX Manager 6.3.x releases."
REVISION "201610240000Z"
DESCRIPTION
"Update release version for 2016x to was 6.2.x from 6.5."
REVISION "201606020000Z"
DESCRIPTION
"Capabilities for NSX Manager releases."
::= { vmwareAgentCapabilities 25 }
vmwNSXMCapability OBJECT IDENTIFIER ::= { vmwNSXAgentCapabilityMIB 1 }
vmwNSXManager2017-630 AGENT-CAPABILITIES
PRODUCT-RELEASE
"6.3.0"
STATUS current
DESCRIPTION
"Release 6.3.0 for VMware NSX Manager supporting only SNMPv2c trap PDUs.
It describes all the notifications sent from the NSX Manager appliance.
WARNING: This mib module will not be backward compatible with next version.
"
REFERENCE
"http://www.vmware.com/products"
SUPPORTS VMWARE-NSX-MANAGER-MIB
INCLUDES {
vmwNsxManagerNotificationGroup1,
vmwNsxManagerNotificationGroup2
}
::= { vmwNSXMCapability 6 }
vmwNSXManager2016x AGENT-CAPABILITIES
PRODUCT-RELEASE
"6.2.x"
STATUS current
DESCRIPTION
"Release 6.2.x for VMware NSX Manager supporting only SNMPv2c trap PDUs.
It describes all the notifications sent from the NSX Manager appliance.
"
REFERENCE
"http://www.vmware.com/products"
-- REVISION 201606020000Z First Version.
SUPPORTS VMWARE-NSX-MANAGER-MIB
INCLUDES {
vmwNsxManagerNotificationGroup1
}
::= { vmwNSXMCapability 5 }
END

5143
mibs/vmware/VMWARE-NSX-MANAGER-MIB Normal file
View File

File diff suppressed because it is too large Load Diff

1
mibs/vmware/VMWARE-OBSOLETE-MIB.mib → mibs/vmware/VMWARE-OBSOLETE-MIB
View File

@@ -576,4 +576,3 @@ vmwOldVCNotificationGroup NOTIFICATION-GROUP
::= { vmwObsMIBGroups 3 }
END

36
mibs/vmware/VMWARE-PRODUCTS-MIB.mib → mibs/vmware/VMWARE-PRODUCTS-MIB
View File

@@ -1,5 +1,5 @@
-- **********************************************************
-- Copyright 2007-2015 VMware, Inc. All rights reserved.
-- Copyright 2007-2017 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-PRODUCTS-MIB DEFINITIONS ::= BEGIN
@@ -11,7 +11,7 @@ IMPORTS
FROM VMWARE-ROOT-MIB;
vmwProducts MODULE-IDENTITY
LAST-UPDATED "201409190000Z"
LAST-UPDATED "201710130000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
@@ -19,13 +19,22 @@ vmwProducts MODULE-IDENTITY
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://communities.vmware.com/community/developer/forums/managementapi
Web: http://kb.vmware.com/kb/1013445
"
DESCRIPTION
"This MIB module provides the OID identifiers
which are returned from SNMPv2-MIB sysObjectId for
which are returned from SNMPv2-MIB sysObjectId for
agents in specific VMware products.
"
REVISION "201710130000Z"
DESCRIPTION
"Changed vmwNSXManagerAppliance, vmwNSXManagerAppliance, and vmwNSXControllerAppliance oid."
REVISION "201705170000Z"
DESCRIPTION
"Add vmwHCX appliance sysObjectIds."
REVISION "201507170000Z"
DESCRIPTION
"Add vmwNSX"
REVISION "201409190000Z"
DESCRIPTION
"Add vSphere appliance sysObjectIds."
@@ -64,8 +73,25 @@ vmwInfrastructureAppliance OBJECT IDENTIFIER
vmwManagementAppliance OBJECT IDENTIFIER
::= { vmwProductSpecific 9 }
vmwNSX OBJECT IDENTIFIER
::= { vmwProductSpecific 10 }
vmwNSXEdgeAppliance OBJECT IDENTIFIER
::= { vmwProductSpecific 130 }
vmwNSXManagerAppliance OBJECT IDENTIFIER
::= { vmwProductSpecific 131 }
vmwNSXControllerAppliance OBJECT IDENTIFIER
::= { vmwProductSpecific 132 }
vmwHCXManager OBJECT IDENTIFIER
::= { vmwProductSpecific 230 }
vmwHCXGateway OBJECT IDENTIFIER
::= { vmwProductSpecific 31 }
oidESX OBJECT IDENTIFIER
::= { vmwOID 1 }
END -- end of module VMWARE-PRODUCTS-MIB.

1
mibs/vmware/VMWARE-RESOURCES-MIB.mib → mibs/vmware/VMWARE-RESOURCES-MIB
View File

@@ -267,4 +267,3 @@ vmwResourceGroup OBJECT-GROUP
END

37
mibs/vmware/VMWARE-ROOT-MIB.mib → mibs/vmware/VMWARE-ROOT-MIB
View File

@@ -1,5 +1,5 @@
-- **********************************************************
-- Copyright 2007-2010 VMware, Inc. All rights reserved.
-- Copyright 2007-2016 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-ROOT-MIB DEFINITIONS ::= BEGIN
@@ -9,7 +9,7 @@ IMPORTS
FROM SNMPv2-SMI;
vmware MODULE-IDENTITY
LAST-UPDATED "201004020000Z"
LAST-UPDATED "201611030000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
@@ -24,6 +24,13 @@ vmware MODULE-IDENTITY
This module defines the VMware SNMP MIB root
and its primary subtrees.
"
REVISION "201611030000Z"
DESCRIPTION
"Arc vmwNetworkInsight defined."
REVISION "201601022000Z"
DESCRIPTION
"Arc vmwNsxManager defined."
REVISION "201004020000Z"
DESCRIPTION
@@ -88,6 +95,20 @@ DESCRIPTION
notifications from Site Recovery Manager and can not be polled."
::= { vmware 51 }
vmwVCHA OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Managed objects defined under this node are only visible in
notifications from VMware Virtual Center High Availability and can not be polled."
::= { vmware 53 }
vmwVmon OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Managed objects defined under this node are for VMware Service Lifecycle
Manager."
::= { vmware 55 }
vmwOID OBJECT-IDENTITY
STATUS deprecated
DESCRIPTION
@@ -100,6 +121,18 @@ DESCRIPTION
"All agent capabilities defnitions occur under this."
::= { vmware 70 }
vmwNsxManager OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Objects used by VMware NSX Manager and related components."
::= { vmware 90 }
vmwNetworkInsight OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Objects used by VMware vRealize Network Insight and related components."
::= { vmware 100 }
vmwExperimental OBJECT-IDENTITY
STATUS current
DESCRIPTION

1
mibs/vmware/VMWARE-SRM-EVENT-MIB.mib → mibs/vmware/VMWARE-SRM-EVENT-MIB
View File

@@ -297,4 +297,3 @@ vmwSRMNotificationGroup NOTIFICATION-GROUP
::= { vmwSRMMIBGroups 2 }
END

0
mibs/vmware/VMWARE-SYSTEM-MIB.mib → mibs/vmware/VMWARE-SYSTEM-MIB
View File

8
mibs/vmware/VMWARE-TC-MIB.mib → mibs/vmware/VMWARE-TC-MIB
View File

@@ -178,5 +178,11 @@ VmwLongSnmpAdminString ::= TEXTUAL-CONVENTION
SYNTAX OCTET STRING
END
VmwUnixAbsFilePath ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1024a"
STATUS current
DESCRIPTION "Represents the absolute path of a file on Unix system."
SYNTAX OCTET STRING (SIZE (0..1024))
END

483
mibs/vmware/VMWARE-VA-AGENTCAP-MIB
View File

@@ -1,5 +1,5 @@
-- **********************************************************
-- Copyright 2008-2015 VMware, Inc. All rights reserved.
-- Copyright 2008-2017 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-VA-AGENTCAP-MIB DEFINITIONS ::= BEGIN
@@ -12,7 +12,7 @@ IMPORTS
AGENT-CAPABILITIES
FROM SNMPv2-CONF;
vmwVAAgentCapabilityMIB MODULE-IDENTITY
LAST-UPDATED "201501120000Z"
LAST-UPDATED "201710130000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
@@ -23,16 +23,487 @@ vmwVAAgentCapabilityMIB MODULE-IDENTITY
Web: http://communities.vmware.com/community/developer/forums/managementapi
"
DESCRIPTION
"This module defines agent capabilities for deployed VMware Virtual Appliance agents by release."
"This module defines agent capabilities for deployed VMware Virtual Appliance agents
by release."
REVISION "201710130000Z"
DESCRIPTION
"Capabilities for VMware VSphere (Release 6.7) ESXi 2017 added."
REVISION "201604220000Z"
DESCRIPTION
"Agent updates for 6.5 Release."
REVISION "201501120000Z"
DESCRIPTION
"Capabilities for VMware Virutal Appliance."
"Capabilities for VMware Virtual Appliance, 6.0 release."
::= { vmwareAgentCapabilities 5 }
vmwVACapability OBJECT IDENTIFIER ::= { vmwVAAgentCapabilityMIB 1 }
--
-- 2017 Release and follow up patch releases
--
vmwVCSA2017x AGENT-CAPABILITIES
PRODUCT-RELEASE
"6.7.x"
STATUS current
DESCRIPTION
"Release 6.7 for VMware Virtual Appliance (VCSA) supporting SNMPv1, SNMPv2c, and SNMPv3.
Changes for this release were primarily bug fixing related.
"
REFERENCE
"http://www.vmware.com/products"
-- RFC 3418
SUPPORTS SNMPv2-MIB
INCLUDES {
snmpGroup,
systemGroup,
snmpCommunityGroup,
snmpBasicNotificationsGroup,
snmpWarmStartNotificationGroup
-- groups not supported; snmpSetGroup, snmpNotificationGroup
}
VARIATION snmpSetSerialNo
ACCESS not-implemented
DESCRIPTION "Agent provides read-only view of system information."
VARIATION snmpTrapOID
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpTrapEnterprise
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpEnableAuthenTraps
SYNTAX INTEGER { disabled(2) }
ACCESS read-only
DESCRIPTION "Agent does not support authentication traps. Poll snmpInBadCommunityNames for same info."
-- which implies:
-- VARIATION authenticationFailure
-- ACCESS not-implemented
-- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled."
-- ********************* ************ ************ *************** ***
-- RFC 2863
SUPPORTS IF-MIB
INCLUDES {
ifGeneralInformationGroup,
linkUpDownNotificationsGroup
}
VARIATION ifAdminStatus
ACCESS read-only
DESCRIPTION "Agent provides read-only view of administrative state for each physical interface."
VARIATION ifLinkUpDownTrapEnable
ACCESS read-only
DESCRIPTION "Agent provides read-only view of system information."
VARIATION ifAlias
ACCESS read-only
DESCRIPTION "ifIndexes may only change across reboot."
VARIATION ifInUnknownProtos
ACCESS not-implemented
DESCRIPTION "This counter always returns 0."
-- ifRcvAddressGroup is interface/media specific
VARIATION ifRcvAddressStatus
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
VARIATION ifRcvAddressType
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
-- ********************* ************ ************ *************** ***
-- RFC 4293
SUPPORTS IP-MIB
INCLUDES {
ipSystemStatsGroup,
ipAddressGroup,
ipNetToPhysicalGroup,
ipDefaultRouterGroup,
icmpStatsGroup,
ipSystemStatsHCOctetGroup,
ipSystemStatsHCPacketGroup,
ipv4GeneralGroup,
ipv4IfGroup,
ipv4SystemStatsGroup,
ipv4SystemStatsHCPacketGroup,
ipv6GeneralGroup2,
ipv6IfGroup,
ipAddressPrefixGroup,
ipv6RouterAdvertGroup,
ipLastChangeGroup
}
-- VARIATION ipv6ScopeGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- RFC 4292
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS IP-FORWARD-MIB
INCLUDES {
inetForwardCidrRouteGroup
}
-- RFC 4113
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS UDP-MIB
-- The next two 32 bit counters will be fixed per bug report PR 890894
-- VARIATION udpInDatagrams
-- ACCESS not-implemented, use udpHCInDatagrams
-- VARIATION udpOutDatagrams
-- ACCESS not-implemented, use udpHCOutDatagrams
INCLUDES {
udpBaseGroup,
udpEndpointGroup
}
-- RFC 4022
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS TCP-MIB
INCLUDES {
tcpBaseGroup,
tcpConnectionGroup,
tcpListenerGroup
}
-- RFC 2790
-- NOTE: For storage larger than Integer32 (Terabyte) this agent will report INT_MAX
SUPPORTS HOST-RESOURCES-MIB
INCLUDES {
hrSystemGroup,
hrStorageGroup,
hrDeviceGroup,
hrSWRunGroup,
hrSWRunPerfGroup,
hrSWInstalledGroup -- updates once an hour
}
VARIATION hrSystemNumUsers
ACCESS read-only
DESCRIPTION "Value reports number of active appliace shell sessions"
VARIATION hrSystemDate
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadDevice
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadParameters
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrStorageSize
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSWRunStatus
ACCESS read-only
DESCRIPTION "agent provides read only access"
-- hrDeviceStatus reports unknown for: cpu, nic either running/unknown.
-- disk reports running, warning, down, unknown
-- device error counters do not account for all failure cases
VARIATION hrSWOSIndex
ACCESS not-implemented
DESCRIPTION "No operatingSystem entry exists in hrSWRunGroup hrSWRunTable"
VARIATION hrFSLastFullBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrFSLastPartialBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterStatus
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterDetectedErrorState
ACCESS not-implemented
DESCRIPTION "is not implemented"
-- ********************* ************ ************ *************** ***
-- RFC 4133
SUPPORTS ENTITY-MIB
INCLUDES {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup
}
-- VARIATION entityNotificationsGroup
-- ACCESS not-implemented
-- VARIATION entityMappingGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201008020000Z
SUPPORTS VMWARE-SYSTEM-MIB
INCLUDES {
vmwSystemGroup
}
-- VARIATION vmwProdUpdate
-- ACCESS not-implemented
-- VARIATION vmwProdPatch
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201602030000Z
SUPPORTS VMWARE-VCHA-MIB
INCLUDES {
vmwVchaNotificationInfoGroup,
vmwVchaNotificationGroup
}
::= { vmwVACapability 7 }
--
-- 2016 Release and follow up patch releases
--
vmwVCSA2016x AGENT-CAPABILITIES
PRODUCT-RELEASE
"6.5.x"
STATUS current
DESCRIPTION
"Release 6.5 for VMware Virtual Appliance supporting SNMPv1, SNMPv2c, and SNMPv3.
Adds VMWARE-VCHA-MIB module support.
This agent supports read-only protocol operations, shares same configuration file as VMware ESXi agent.
This implies that configuring the SNMPv3 Agent can not be done via SET operations or use SET PDU to
discover engine id. Hence IETF standard SNMPv3 agent configuration mibs are not provided.
The SNMPv3 protocol is fully supported once configured via the CLI command interface, run
appliancesh shell using the 'snmp' command set. Lastly this SNMP agent provides one read-only view of
the entire system to which all SNMPv3 users configured are assigned.
"
REFERENCE
"http://www.vmware.com/products"
-- RFC 3418
SUPPORTS SNMPv2-MIB
INCLUDES {
snmpGroup,
systemGroup,
snmpCommunityGroup,
snmpBasicNotificationsGroup,
snmpWarmStartNotificationGroup
-- groups not supported; snmpSetGroup, snmpNotificationGroup
}
VARIATION snmpSetSerialNo
ACCESS not-implemented
DESCRIPTION "Agent provides read-only view of system information."
VARIATION snmpTrapOID
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpTrapEnterprise
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpEnableAuthenTraps
SYNTAX INTEGER { disabled(2) }
ACCESS read-only
DESCRIPTION "Agent does not support authentication traps. Poll snmpInBadCommunityNames for same info."
-- which implies:
-- VARIATION authenticationFailure
-- ACCESS not-implemented
-- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled."
-- ********************* ************ ************ *************** ***
-- RFC 2863
SUPPORTS IF-MIB
INCLUDES {
ifGeneralInformationGroup,
linkUpDownNotificationsGroup
}
VARIATION ifAdminStatus
ACCESS read-only
DESCRIPTION "Agent provides read-only view of administrative state for each physical interface."
VARIATION ifLinkUpDownTrapEnable
ACCESS read-only
DESCRIPTION "Agent provides read-only view of system information."
VARIATION ifAlias
ACCESS read-only
DESCRIPTION "ifIndexes may only change across reboot."
VARIATION ifInUnknownProtos
ACCESS not-implemented
DESCRIPTION "This counter always returns 0."
-- ifRcvAddressGroup is interface/media specific
VARIATION ifRcvAddressStatus
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
VARIATION ifRcvAddressType
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
-- ********************* ************ ************ *************** ***
-- RFC 4293
SUPPORTS IP-MIB
INCLUDES {
ipSystemStatsGroup,
ipAddressGroup,
ipNetToPhysicalGroup,
ipDefaultRouterGroup,
icmpStatsGroup,
ipSystemStatsHCOctetGroup,
ipSystemStatsHCPacketGroup,
ipv4GeneralGroup,
ipv4IfGroup,
ipv4SystemStatsGroup,
ipv4SystemStatsHCPacketGroup,
ipv6GeneralGroup2,
ipv6IfGroup,
ipAddressPrefixGroup,
ipv6RouterAdvertGroup,
ipLastChangeGroup
}
-- VARIATION ipv6ScopeGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- RFC 4292
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS IP-FORWARD-MIB
INCLUDES {
inetForwardCidrRouteGroup
}
-- RFC 4113
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS UDP-MIB
-- The next two 32 bit counters will be fixed per bug report PR 890894
-- VARIATION udpInDatagrams
-- ACCESS not-implemented, use udpHCInDatagrams
-- VARIATION udpOutDatagrams
-- ACCESS not-implemented, use udpHCOutDatagrams
INCLUDES {
udpBaseGroup,
udpEndpointGroup
}
-- RFC 4022
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS TCP-MIB
INCLUDES {
tcpBaseGroup,
tcpConnectionGroup,
tcpListenerGroup
}
-- RFC 2790
-- NOTE: For storage larger than Integer32 (Terabyte) this agent will report INT_MAX
SUPPORTS HOST-RESOURCES-MIB
INCLUDES {
hrSystemGroup,
hrStorageGroup,
hrDeviceGroup,
hrSWRunGroup,
hrSWRunPerfGroup,
hrSWInstalledGroup -- updates once an hour
}
VARIATION hrSystemNumUsers
ACCESS read-only
DESCRIPTION "Value reports number of active appliace shell sessions"
VARIATION hrSystemDate
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadDevice
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadParameters
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrStorageSize
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSWRunStatus
ACCESS read-only
DESCRIPTION "agent provides read only access"
-- hrDeviceStatus reports unknown for: cpu, nic either running/unknown.
-- disk reports running, warning, down, unknown
-- device error counters do not account for all failure cases
VARIATION hrSWOSIndex
ACCESS not-implemented
DESCRIPTION "No operatingSystem entry exists in hrSWRunGroup hrSWRunTable"
VARIATION hrFSLastFullBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrFSLastPartialBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterStatus
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterDetectedErrorState
ACCESS not-implemented
DESCRIPTION "is not implemented"
-- ********************* ************ ************ *************** ***
-- RFC 4133
SUPPORTS ENTITY-MIB
INCLUDES {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup
}
-- VARIATION entityNotificationsGroup
-- ACCESS not-implemented
-- VARIATION entityMappingGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201008020000Z
SUPPORTS VMWARE-SYSTEM-MIB
INCLUDES {
vmwSystemGroup
}
-- VARIATION vmwProdUpdate
-- ACCESS not-implemented
-- VARIATION vmwProdPatch
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201602030000Z
SUPPORTS VMWARE-VCHA-MIB
INCLUDES {
vmwVchaNotificationInfoGroup,
vmwVchaNotificationGroup
}
::= { vmwVACapability 6 }
--
-- 2015 Release and follow up patch releases
--
@@ -48,7 +519,7 @@ vmwVA2015x AGENT-CAPABILITIES
This implies that configuring the SNMPv3 Agent can not be done via SET operations or use SET PDU to
discover engine id. Hence IETF standard SNMPv3 agent configuration mibs are not provided.
The SNMPv3 protocol is fully supported once configured via the CLI command interface, run
applianceh shell using the 'snmp' command set. Lastly this SNMP agent provides one read-only view of
appliancesh shell using the 'snmp' command set. Lastly this SNMP agent provides one read-only view of
the entire system to which all SNMPv3 users configured are assigned.
This initial release does not have: UDP-MIB, TCP-MIB modules.
@@ -242,6 +713,6 @@ vmwVA2015x AGENT-CAPABILITIES
::= { vmwVACapability 5 }
END

1
mibs/vmware/VMWARE-VC-EVENT-MIB.mib → mibs/vmware/VMWARE-VC-EVENT-MIB
View File

@@ -249,4 +249,3 @@ vmwVCAlarmNotificationGroup NOTIFICATION-GROUP
::= { vmwVCMIBGroups 4 }
END -- end of VMWARE-VC-EVENT-MIB.

589
mibs/vmware/VMWARE-VCHA-MIB Normal file
View File

@@ -0,0 +1,589 @@
-- **********************************************************
-- Copyright 2015-2016 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-VCHA-MIB DEFINITIONS::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InetAddress, InetAddressType
FROM INET-ADDRESS-MIB
vmwVCHA
FROM VMWARE-ROOT-MIB
TEXTUAL-CONVENTION, TruthValue
FROM SNMPv2-TC;
vmwVchaMIB MODULE-IDENTITY
LAST-UPDATED "201607190000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://communities.vmware.com/community/developer/forums/managementapi
"
DESCRIPTION
"This MIB module describes the vCenter High Availability Service (VCHA).
A VCHA cluster consists of three VMs identified by a single instance UUID.
One is the Active vCenter VM that serves client requests. Second is the
Passive VM that is identical to the Active vCenter VM in terms of database
and filesystem state. Passive VM constantly receives updates from Active
VM and takes over the role of Active vCenter VM in the event of a
failover. Third is the Witness VM that acts as a quorum VM in a VCHA
cluster. The sole purpose of Witness VM is to avoid classic split-brain
problem in a VCHA cluster.
client
+
|
|
+----------------v---+ +--------------------+
| Public IP | |
| | | |
| Active vCenter | | Passive vCenter |
| | | |
+---Private-IP+------+ +------+Private-IP---+
^ <--------------------------> ^
| DB & File replication |
+ +
+ +
+ +
+------> <----------+
+----Private-IP----+
| |
| Witness vCenter |
| (Quorum) |
| |
+------------------+
All events will not be repeated for the duration of a given state entered.
It is highly recommended that the administrator links the SNMP trap receiver
to both public network and vCenter HA cluster network, so that the
monitoring system is able to get notified as long as one of the
networks is up.
"
REVISION "201607190000Z"
DESCRIPTION
"Removed vmwVchaFileReplicationEventQueueOverflowed and cleaned up a few
descriptions. Fixed vCenter HA related terminologies and typos."
REVISION "201604060000Z"
DESCRIPTION
"Aggregate vmwVchaFileWatchFailed, vmwVchaFileReplicationFailed and
vmwVchaFileResyncSucceeded into vmwVchaFileReplicationStateChanged
notification. Add three more notification for failover failure cases.
Combine syncPeerStarted and syncPeerCompleted into a single state: sync."
REVISION "201602030000Z"
DESCRIPTION
"Add two more notifications vmwVchaFailoverSucceeded and
vmwVchaContinueAsActive to indicate whether a failover succeeds. Also add
one more parameter to vmwVchaNodeJoined and vmwVchaNodeLeft to distinguish
between the role of sender node and target node."
REVISION "201601270000Z"
DESCRIPTION
"Change the terminology from DB replication mode to DB replication state
and add one more state to it. Also use past tense for all notification
names."
REVISION "201601150000Z"
DESCRIPTION
"Add two more notifications vmwVchaClusterStateChange and
vmwVchaFileReplicationEventQueueOverflowed."
REVISION "201601040000Z"
DESCRIPTION
"This is the first version of this MIB module."
::= { vmwVCHA 1 }
vmwVCHANotifications OBJECT IDENTIFIER ::= { vmwVCHA 0 }
-- Definition of roles for VCHA, see RFC 4133 entLogicalType
vmwVchaActive OBJECT IDENTIFIER ::= { vmwVCHA 250 }
vmwVchaPassive OBJECT IDENTIFIER ::= { vmwVCHA 255 }
vmwVchaWitness OBJECT IDENTIFIER ::= { vmwVCHA 260 }
-- **********************************************************
-- Enumerations for notification parameters
-- **********************************************************
VmwVchaNodeRoleType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent the role each node in the cluster is running as.
active (1) Active vCenter serves client requests.
passive (2) Passive node is identical to the Active node in
terms of database and filesystem state. Passive
node constantly receives updates from the Active
node and takes over the role of Active node in the
event of a failover.
witness (3) Witness node acts as a quorum node in a vCenter HA
cluster. Sole purpose of Witness VM is to avoid
the classic split-brain problem in a VCHA cluster.
unknown (4) Node without any role assigned."
SYNTAX INTEGER { active(1), passive(2), witness(3), unknown(4) }
VmwVchaClusterModeType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent VCHA cluster modes: enabled, disabled or maintenance:
enabled (1) State replication between Active and Passive nodes
is enabled and automatic failover happens if the
Active node fails while the VCHA cluster is healthy.
disabled (2) All three nodes are part of VCHA cluster but the
state replication and automatic failover are
disabled.
maintenance (3) All three nodes are part of VCHA cluster but
automatic failover is disabled while state
replication continues. The Active node continues to
serve client requests even if Passive and Witness
nodes are lost."
SYNTAX INTEGER { enabled(1), disabled(2), maintenance(3) }
VmwVchaClusterStateType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent the health state of the vCenter HA cluster.
healthy (1) All three nodes in a VCHA cluster are healthy and
connected. State replication between the Active and
Passive nodes is working and both nodes are in-sync.
degraded (2) A VCHA cluster is said to be in degraded state when
it has lost one of the three nodes. Node loss can
be due to various reasons and as a result, the lost
node is not visible to other two nodes. If the
Active node is lost, the Passive node will take the
role of the Active node. If the Passive or Witness
node is lost, the Active node will continue to serve
requests. A VCHA cluster can also be in degraded
state if state replication fails between the Active
and Passive nodes.
isolated (3) All three nodes are isolated from each other. If
this happens when VCHA cluster is in enabled mode,
the Active node stops serving client requests. If
nodes are isolated in a disabled VCHA cluster mode,
the Active node continues to serve client requests."
SYNTAX INTEGER { healthy(1), degraded(2), isolated(3) }
VmwVchaDbReplicationStateType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent DB replication states: sync, async or no replication.
noReplication (1) There is no DB replication between the Active
and Passive nodes. This could happen when
vPostgres is not running on the Passive node.
sync (3) In sync state, the Passive vCenter keeps the
up-to-date state with the Active vCenter.
async (4) Async state replication makes the state of
Passive node fall behind the Active vCenter.
This causes a data loss when an automatic
failover happens."
SYNTAX INTEGER { noReplication(1), sync(3), async(4) }
VmwVchaFileReplicationProviderType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent the file replication providers.
serviceConfig (1) This provider maintains the replication of
service configuration files, which are small in
size.
serviceState (2) This provider maintains the replication of
service state files, which are large in size."
SYNTAX INTEGER { serviceConfig(1), serviceState(2) }
-- **********************************************************
-- Notifications by an agent that implements this MIB module
-- **********************************************************
vmwVchaNodeJoined NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressType,
vmwVchaPrivateAddressAddr,
vmwVchaTargetNodeRole
}
STATUS current
DESCRIPTION
"This informative notification is sent from the Active node when it
notices a peer node rejoin the cluster. It is sent only once."
::= { vmwVCHANotifications 100 }
vmwVchaNodeLeft NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressType,
vmwVchaPrivateAddressAddr,
vmwVchaTargetNodeRole
}
STATUS current
DESCRIPTION
"This warning notification is sent from the Active node when it notices
a peer node has left the cluster. This is sent only once. Operator
should check the liveness and connectivity of the departed node and try
to bring it back by either rebooting the appliance or resolving the
network problem."
::= { vmwVCHANotifications 105 }
vmwVchaNodeIsolated NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressType,
vmwVchaPrivateAddressAddr,
vmwVchaTargetNodeRole
}
STATUS current
DESCRIPTION
"This warning notification is sent when a node is network isolated from
the cluster. This notification can only be sent from the isolated node,
not by other nodes in the cluster. After being isolated, the node will
reboot itself trigging coldStart notification. In case of Active node
failure, the cluster will trigger a reelection and every slave node will
be declared as isolated temporarily before the cluster re-election
completes."
::= { vmwVCHANotifications 110 }
vmwVchaClusterStateChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaClusterState
}
STATUS current
DESCRIPTION
"This notification is sent only once from the Active node when vCenter
HA cluster state changes to either healthy, degraded or isolated. Please
see VmwVchaClusterStateType for detailed description of each state. And
administrator should receive another notification describing the state
change of cluster subsystem (cluster membership, DB replication or file
replication) which is trigger of cluster state change."
::= { vmwVCHANotifications 130 }
vmwVchaClusterModeChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaClusterMode
}
STATUS current
DESCRIPTION
"This notification is sent only once from the Active node when vCenter
HA cluster mode changes to either enabled, maintenance or disabled."
::= { vmwVCHANotifications 150 }
vmwVchaPublicIpUp NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPublicAddressType,
vmwVchaPublicAddressAddr
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the public IP
address is brought up on the Active node. At this time, the Active node
is reachable from the client and will be able to serve client requests
when services are up and running."
::= { vmwVCHANotifications 205 }
vmwVchaPublicIpDown NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPublicAddressType,
vmwVchaPublicAddressAddr
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the public
network interface is brought down on the Active node. This can happen
when InitiateFailover is invoked on the Active node or vcha process
gracefully shuts down resulting in a reboot of the appliance (triggered
by network isolation). During this time, clients cannot connect to
vCenter Server and users will experience downtime until the public
network interface is brought up. In either case, users should not
expect more than five minutes of downtime. If VCHA cluster is still not
connectable, the operator should verify the reachability of each node
through the cluster network."
::= { vmwVCHANotifications 206 }
vmwVchaFailoverTriggered NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaIsPlannedFailover
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when a failover is
triggered from the Active node to Passive node. Passive node should
take over the Active role if the cluster is in healthy state."
::= { vmwVCHANotifications 210 }
vmwVchaFailoverSucceeded NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the Passive node
takes over the Active role and brings up the public network interface."
::= { vmwVCHANotifications 220 }
vmwVchaFailoverFailedDisabledMode NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This warning notification is sent only once when the Active node fails
to initiate a failover because the cluster is in disabled mode."
::= { vmwVCHANotifications 225 }
vmwVchaFailoverFailedNodeLost NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This warning notification is sent only once when the Active node fails
to initiate a failover because the cluster does not have all three
nodes connected."
::= { vmwVCHANotifications 226 }
vmwVchaFailoverFailedPassiveNotReady NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This warning notification is sent only once when the Active node fails
to initiate a failover because vPostgres service on the Passive node is
not ready to take over."
::= { vmwVCHANotifications 227 }
vmwVchaContinueAsActive NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the last Active
node continue as the Active node to servce client's request. This can
happen in many scenarios:
1. After triggering a planned failover, DB or file replicator failed to
flush data to the Passive node and failover didn't proceed because of
data loss.
2. After triggering a planned or forced failover, Passive node failed to
pick up the Active role for reasons like: auto failover cannot happen in
maintenance mode or cluster is in disabled mode."
::= { vmwVCHANotifications 230 }
vmwVchaDbReplicationStateChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaDbReplicationState
}
STATUS current
DESCRIPTION
"This informative notification is sent only once from the Active node
when database replication state changes to sync, async or no
replication. Database replication is not healthy when it is in async or
no replication state. Reasons include large network delays or vPostgres
service becoming unresponsive on the Passive node."
::= { vmwVCHANotifications 300 }
vmwVchaFileReplicationStateChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaFileReplicationProvider,
vmwVchaIsFileProviderInSync
}
STATUS current
DESCRIPTION
"This informative notification is sent only once from the Active node
when file replication state changes to in-sync or out-of-sync. File
replication state is out-of-sync when VCHA fails to set a watch on a
file at the Active node or fails to replicate a file from the Active
node to Passive. Administrators should check the corresponding KB
article for recovery action."
::= { vmwVCHANotifications 350 }
-- **********************************************************
-- Notification variables
-- **********************************************************
vmwVchaInstanceUuid OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"A string that uniquely identify the vCenter HA cluster. This is the same
as instance UUID of the active vCenter Server."
::= { vmwVCHA 5 }
vmwVchaPrivateAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The type of cluster network interface: ipv4 or ipv6."
::= { vmwVCHA 11 }
vmwVchaPublicAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The type of public network interface: ipv4 or ipv6."
::= { vmwVCHA 12 }
vmwVchaPrivateAddressAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This is the IP address of each node in cluster network that is used to
communicate with other nodes in the cluster and transfer data between
the Active node and the Passive node."
::= { vmwVCHA 15 }
vmwVchaPublicAddressAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The IP address of a node in public network that serves client's request."
::= { vmwVCHA 16 }
vmwVchaTargetNodeRole OBJECT-TYPE
SYNTAX VmwVchaNodeRoleType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the role of node being affected by the given event. See MIB
module general description for detailed expalanation for each role."
::= { vmwVCHA 20 }
vmwVchaClusterState OBJECT-TYPE
SYNTAX VmwVchaClusterStateType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"vCenter HA cluster states: healthy, degraded or isolated."
::= { vmwVCHA 25 }
vmwVchaClusterMode OBJECT-TYPE
SYNTAX VmwVchaClusterModeType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"vCenter HA cluster modes: enabled, maintenance or disabled."
::= { vmwVCHA 30 }
vmwVchaIsPlannedFailover OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"For planned failover, the Active node flushes all the state to the Passive
node, waits for the flush to complete before causing a failover.
After the failover, the Passive node starts without any data loss.
For unplanned failover, the failover is initiated immediately and may
result in data loss."
::= { vmwVCHA 40 }
vmwVchaDbReplicationState OBJECT-TYPE
SYNTAX VmwVchaDbReplicationStateType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Database replication states: sync, async or no replication."
::= { vmwVCHA 50 }
vmwVchaIsFileProviderInSync OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This variable represents the file replication provider state. When it is
false, the service configuration and state files are out of sync between
the Passive and Active nodes. This could result from file replication
failures."
::= { vmwVCHA 55 }
vmwVchaFileReplicationProvider OBJECT-TYPE
SYNTAX VmwVchaFileReplicationProviderType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"File replication providers: service-config or service-state."
::= { vmwVCHA 60 }
-- conformance information
vmwVchaMIBConformance OBJECT IDENTIFIER ::= { vmwVchaMIB 2 }
vmwVchaMIBCompliances OBJECT IDENTIFIER ::= { vmwVchaMIBConformance 1 }
vmwVchaMIBGroups OBJECT IDENTIFIER ::= { vmwVchaMIBConformance 2 }
vmwVchaMIBBasicComplianceRev2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement VMWARE-VCHA-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwVchaNotificationInfoGroup, vmwVchaNotificationGroup }
::= { vmwVchaMIBCompliances 3 }
vmwVchaNotificationInfoGroup OBJECT-GROUP
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressAddr,
vmwVchaPrivateAddressType,
vmwVchaPublicAddressAddr,
vmwVchaPublicAddressType,
vmwVchaTargetNodeRole,
vmwVchaClusterState,
vmwVchaClusterMode,
vmwVchaIsPlannedFailover,
vmwVchaDbReplicationState,
vmwVchaIsFileProviderInSync,
vmwVchaFileReplicationProvider
}
STATUS current
DESCRIPTION
"These objects provide notification details."
::= { vmwVchaMIBGroups 1 }
vmwVchaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
vmwVchaNodeJoined,
vmwVchaNodeLeft,
vmwVchaNodeIsolated,
vmwVchaClusterStateChanged,
vmwVchaClusterModeChanged,
vmwVchaPublicIpUp,
vmwVchaPublicIpDown,
vmwVchaFailoverTriggered,
vmwVchaFailoverSucceeded,
vmwVchaFailoverFailedDisabledMode,
vmwVchaFailoverFailedNodeLost,
vmwVchaFailoverFailedPassiveNotReady,
vmwVchaContinueAsActive,
vmwVchaDbReplicationStateChanged,
vmwVchaFileReplicationStateChanged
}
STATUS current
DESCRIPTION
"Group of objects describing notifications (traps)."
::= { vmwVchaMIBGroups 2 }
END -- end of VMWARE-VCHA-MIB.

1430
mibs/vmware/VMWARE-VCOPS-EVENT-MIB
View File

File diff suppressed because it is too large Load Diff

1
mibs/vmware/VMWARE-VMINFO-MIB.mib → mibs/vmware/VMWARE-VMINFO-MIB
View File

@@ -702,4 +702,3 @@ vmwVmObsoleteGroup OBJECT-GROUP
END -- end of module VMWARE-VMINFO-MIB.

132
mibs/vmware/VMWARE-VRNI-AGENTCAP-MIB Normal file
View File

@@ -0,0 +1,132 @@
-- **********************************************************
-- Copyright 2016-2017 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-VRNI-AGENTCAP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI
vmwareAgentCapabilities
FROM VMWARE-ROOT-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF;
vmwVRNIAgentCapabilityMIB MODULE-IDENTITY
LAST-UPDATED "201710130000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://kb.vmware.com/kb/1013445
"
DESCRIPTION
"This module defines agent capabilities for deployed VRNI agents by release."
REVISION "201710130000Z"
DESCRIPTION
"Change vmwVRNIAgentCapabilityMIB root oid to fix duplicate oid."
REVISION "201709050000Z"
DESCRIPTION
"Notifications send by VRNI as updated in 3.5 release"
REVISION "201706010000Z"
DESCRIPTION
"Notifications send by VRNI as updated in 3.4 release"
REVISION "201703020000Z"
DESCRIPTION
"Notifications send by VRNI as updated in 3.3 release"
REVISION "201611220001Z"
DESCRIPTION
"Describe SNMP agent capabilities for each VRNI appliance release."
::= { vmwareAgentCapabilities 125 }
vmwVRNICapability OBJECT IDENTIFIER ::= { vmwVRNIAgentCapabilityMIB 10 }
vmwVRNIAgent2016v350 AGENT-CAPABILITIES
PRODUCT-RELEASE
"3.5.0"
STATUS current
DESCRIPTION
"Release 3.5.0 for VMware VRNI supporting only SNMPv2c trap PDUs.
It describes all the notifications sent from the VRNI appliance."
REFERENCE
"http://www.vmware.com/products"
-- REVISION 201709050000Z Fourth Version
SUPPORTS VMWARE-VRNI-MIB
INCLUDES {
vmwNetworkInsightNotificationGroup1,
vmwNetworkInsightNotificationGroup2,
vmwNetworkInsightNotificationGroup3,
vmwNetworkInsightNotificationGroup4,
vmwNetworkInsightNotificationInfoGroup2
}
::= { vmwVRNICapability 9 }
vmwVRNIAgent2017v340 AGENT-CAPABILITIES
PRODUCT-RELEASE
"3.4.0"
STATUS current
DESCRIPTION
"Release 3.4.0 for VMware VRNI supporting only SNMPv2c trap PDUs.
It describes all the notifications sent from the VRNI appliance.
This mib module is backward compatible with next version."
REFERENCE
"http://www.vmware.com/products"
-- REVISION 201706010000Z Third Version
SUPPORTS VMWARE-VRNI-MIB
INCLUDES {
vmwNetworkInsightNotificationGroup1,
vmwNetworkInsightNotificationGroup2,
vmwNetworkInsightNotificationGroup3,
vmwNetworkInsightNotificationInfoGroup2
}
::= { vmwVRNICapability 8 }
vmwVRNIAgent2017v330 AGENT-CAPABILITIES
PRODUCT-RELEASE
"3.3.0"
STATUS current
DESCRIPTION
"Release 3.3.0 for VMware VRNI supporting only SNMPv2c trap PDUs.
It describes all the notifications sent from the VRNI appliance.
This mib module is backward compatible with next version. It
extends 3.2 release events by appending eventName managed object
to each notification's variable binding and adding a new set of
notifications."
REFERENCE
"http://www.vmware.com/products"
-- REVISION 201702200000Z Second Version.
SUPPORTS VMWARE-VRNI-MIB
INCLUDES {
vmwNetworkInsightNotificationGroup1,
vmwNetworkInsightNotificationGroup2,
vmwNetworkInsightNotificationInfoGroup2
}
::= { vmwVRNICapability 7 }
vmwVRNIAgent2016v320 AGENT-CAPABILITIES
PRODUCT-RELEASE
"3.2.0"
STATUS current
DESCRIPTION
"Release 3.2.0 for VMware VRNI supporting only SNMPv2c trap PDUs.
It describes all the notifications sent from the VRNI appliance.
WARNING: This mib module will not be backward compatible with next version.
"
REFERENCE
"http://www.vmware.com/products"
-- REVISION 201610260000Z First Version.
SUPPORTS VMWARE-VRNI-MIB
INCLUDES {
vmwNetworkInsightMIBGroups
}
::= { vmwVRNICapability 6 }
END

1617
mibs/vmware/VMWARE-VRNI-MIB Normal file
View File

File diff suppressed because it is too large Load Diff