diff options
| author | David Leutgeb <david.leutgeb@mannundmouse.com> | 2023-12-05 12:25:34 +0100 |
|---|---|---|
| committer | David Leutgeb <david.leutgeb@mannundmouse.com> | 2023-12-05 12:25:34 +0100 |
| commit | 98a672123c7872f6b9b75a9a2b6bb3aea504de6a (patch) | |
| tree | 9b13bd7f563c3198047bd359195327cf28b3caf0 /MIBS/vmware | |
| download | mibs-main.tar.gz mibs-main.zip | |
Diffstat (limited to 'MIBS/vmware')
31 files changed, 40544 insertions, 0 deletions
diff --git a/MIBS/vmware/VELOCLOUD-EDGE-MIB b/MIBS/vmware/VELOCLOUD-EDGE-MIB new file mode 100644 index 0000000..b5924e1 --- /dev/null +++ b/MIBS/vmware/VELOCLOUD-EDGE-MIB @@ -0,0 +1,1073 @@ +------------------------------------ +-- VeloCloud Edge MIB Definitions -- +------------------------------------ + +VELOCLOUD-EDGE-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, + OBJECT-TYPE, + Integer32, + TimeTicks, + Counter64 + FROM SNMPv2-SMI + + OBJECT-GROUP, + MODULE-COMPLIANCE + FROM SNMPv2-CONF + + TruthValue, + DisplayString, + TEXTUAL-CONVENTION, + PhysAddress + FROM SNMPv2-TC + + InetAddress, + InetAddressType + FROM INET-ADDRESS-MIB + + InterfaceIndex + FROM IF-MIB + + UUID + FROM UUID-TC-MIB + + modules + FROM VELOCLOUD-MIB +; + +edge MODULE-IDENTITY + LAST-UPDATED "201908020000Z" + ORGANIZATION "VMware Corporation" + CONTACT-INFO "postal: VMware Corporation + World Headquarters + 3401 Hillview Avenue + Palo Alto, CA 94304 + USA + + email: contact@velocloud.com + web: www.velocloud.com" + DESCRIPTION "VeloCloud Edge MIB Definitions" + + REVISION "201908020000Z" + DESCRIPTION "Update definition of VeloCloud Edge MIB Objects" + + REVISION "201701180000Z" + DESCRIPTION "Implementation of VeloCloud Edge Module MIB Objects" + + REVISION "201701130000Z" + DESCRIPTION "Inital definition of VeloCloud MIB Objects" +::= { modules 1 } + + +VceHaAdminStateType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION "VeloCloud specified enumeration type ha adminstration state." + SYNTAX INTEGER { + none(1), + theVelocloudActiveStandbyPair(2), + theVeloCloudCluster(3), + nonVeloCloudVrrpPair(4), + unknown(5) + } + +VceHaPeerStateType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION "VeloCloud specified enumeration type for ha peer state." + SYNTAX INTEGER { + initializing(1), + active(2), + standby(3), + unknown(4) + } + +VceLinkStateType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION "VeloCloud specified enumeration type for link state." + SYNTAX INTEGER { + initial(1), + dead(2), + unusable(3), + quiet(4), + standby(5), + unstable(6), + stable(7), + unknown(8) + } + +VcePathStateType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION "VeloCloud specified enumeration type for path state." + SYNTAX INTEGER { + initial(1), + dead(2), + unusable(3), + quiet(4), + unstable(5), + bwUnmeasurable(6), + waitingForLinkbw(7), + measuringTxBw(8), + measuringRxBw(9), + stable(10), + active(11), + upHsby(12), + idleHsby(13), + backup(14), + unknown(15) + } + +VcePathTunlModeType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION "VeloCloud specified enumeration type for path tunnel mode." + SYNTAX INTEGER { + default(1), + trusted(2), + untrustedTransport(3), + untrustedTunnel(4), + unknown(5) + } + +VceArpStateType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION "VeloCloud specified enumeration type for arp state." + SYNTAX INTEGER { + reachable(1), + stale(2), + invalid(5), + unknown(6), + incomplete(7) + } + + +-------------------------------- +-- .edge(1) Top Level -- +-- -- +-- Contains OIDs: -- +-- .vceCompliance(1) -- +-- .vceEdgeObject(2) -- +-------------------------------- +vceCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION "Compliance statement for all VeloCloud edge(vce) objects." + MODULE + MANDATORY-GROUPS { + vceHaGroup, + vceHealthGroup, + vceLinkGroup, + vcePathGroup, + vceArpGroup + } +::= { edge 1 } + +vceEdgeObject OBJECT IDENTIFIER ::= { edge 2 } + + +-------------------------------- +-- .vceEdgeObject(2) -- +-- -- +-- Contains OIDs: -- +-- .vceHA(1) -- +-- .vceHealth(2) -- +-- .vceLink(3) -- +-- .vcePath(4) -- +-- .vceARP(5) -- +-------------------------------- +vceHA OBJECT IDENTIFIER ::= { vceEdgeObject 1 } +vceHealth OBJECT IDENTIFIER ::= { vceEdgeObject 2 } +vceLink OBJECT IDENTIFIER ::= { vceEdgeObject 3 } +vcePath OBJECT IDENTIFIER ::= { vceEdgeObject 4 } +vceARP OBJECT IDENTIFIER ::= { vceEdgeObject 5 } + + +-------------------------------- +-- .vceDevice(1) -- +-- -- +-- Contains OIDs: -- +-- .deviceGroup(1) -- +-- .vceDeviceObject(2) -- +-------------------------------- +vceHaGroup OBJECT-GROUP + OBJECTS { + vceHaAdminState, + vceHaPeerState, + vceHaActiveWanItfNum, + vceHaActiveLanItfNum, + vceHaStanbyWanItfNum, + vceHaStanbyLanItfNum + } + STATUS current + DESCRIPTION "Conformance group for vceHaGroup objects." +::= { vceHA 1 } +vceHAObject OBJECT IDENTIFIER ::= { vceHA 2 } + + +---------------------------------- +-- .vceHAObject(2) -- +-- -- +-- Contains OIDs: -- +-- .vcehaState(1) -- +-- .vcehaActiveWanItfNum(2)-- +-- .vcehaActiveLanItfNum(3)-- +-- .vcehaStanbyWanItfNum(4) -- +-- .vcehaStanbyWLanItfNum(5) -- +---------------------------------- +vceHaAdminState OBJECT-TYPE + SYNTAX VceHaAdminStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The state of HA administration." +::= { vceHAObject 1 } + +vceHaPeerState OBJECT-TYPE + SYNTAX VceHaPeerStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The state of HA peer." +::= { vceHAObject 2 } + +vceHaActiveWanItfNum OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of WAN interface on this active edge." +::= { vceHAObject 3 } + +vceHaActiveLanItfNum OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of LAN interface on this active edge." +::= { vceHAObject 4 } + +vceHaStanbyWanItfNum OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of WAN interface on stanby peer." +::= { vceHAObject 5 } + +vceHaStanbyLanItfNum OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of LAN interface on stanby peer." +::= { vceHAObject 6 } + + +-------------------------------- +-- .vceHealth(2) -- +-- -- +-- Contains OIDs: -- +-- .vceHealthGroup(1) -- +-- .vceHealthObject(2) -- +-------------------------------- +vceHealthGroup OBJECT-GROUP + OBJECTS { + vceCpuUtilPct5min, + vceCpuUtilPct30sec, + vceMemUsedPct + } + STATUS current + DESCRIPTION "Conformance group for vceHealthGroup objects." +::= { vceHealth 1 } +vceHealthObject OBJECT IDENTIFIER ::= { vceHealth 2 } + + +-------------------------------- +-- .vceHealtObject(2) -- +-- -- +-- Contains OIDs: -- +-- .vceCpuUtilPct5min(1) -- +-- .vceCpuUtilPct30sec(2)-- +-- .vceMemUsedPct(3) -- +-------------------------------- +vceCpuUtilPct5min OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The average CPU utilization percentage of the VeloCloud Edge in 5 minutes." +::= { vceHealthObject 1 } + +vceCpuUtilPct30sec OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The average CPU utilization percentage of the VeloCloud Edge in 30 seconds." +::= { vceHealthObject 2 } + +vceMemUsedPct OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total used memory percentage of the VeloCloud Edge." +::= { vceHealthObject 3 } + + +-------------------------------- +-- .vceLink(4) -- +-------------------------------- +vceLinkGroup OBJECT-GROUP + OBJECTS { + vceLinkNum, + vceLinkName, + vceLinkTxP1Pkt, + vceLinkRxP1Pkt, + vceLinkTxP1Bytes, + vceLinkRxP1Bytes, + vceLinkTxP2Pkt, + vceLinkRxP2Pkt, + vceLinkTxP2Bytes, + vceLinkRxP2Bytes, + vceLinkTxP3Pkt, + vceLinkRxP3Pkt, + vceLinkTxP3Bytes, + vceLinkRxP3Bytes, + vceLinkTxCtlPkt, + vceLinkRxCtlPkt, + vceLinkTxCtlBytes, + vceLinkRxCtlBytes, + vceLinkTxJitter, + vceLinkRxJitter, + vceLinkTxLatency, + vceLinkRxLatency, + vceLinkTxLostPkt, + vceLinkRxLostPkt, + vceLinkVpnState, + vceLinkPublicIpType, + vceLinkPublicIp, + vceLinkLocalIpType, + vceLinkLocalIp, + vceLinkVlanId, + vceLinkMtu, + vceLinkItf, + vceLinkState, + vceLinkVeloSvcReachable, + vceLinkTotTxPkts, + vceLinkTotRxPkts, + vceLinkTotTxbytes, + vceLinkTotRxBytes, + vceLinkIf, + vceLinkNextHopType, + vceLinkNextHop + } + STATUS current + DESCRIPTION "Conformance group for vceLinkGroup objects." +::= { vceLink 1 } +vceLinkObject OBJECT IDENTIFIER ::= { vceLink 2 } + +vceLinkNum OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of links presented on the VeloCloud Edge." +::= { vceLinkObject 1 } + +vceLinkTable OBJECT-TYPE + SYNTAX SEQUENCE OF VceLinkEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "A list of link entries. The number of entries + is given by the value of vceLinkNum." +::= { vceLinkObject 2 } + +vceLinkEntry OBJECT-TYPE + SYNTAX VceLinkEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "An entry containing additional management information + applicable to a particular link" + INDEX { vceLinkIntId } +::= { vceLinkTable 1 } + +VceLinkEntry ::= + SEQUENCE { + vceLinkIntId UUID, + vceLinkName DisplayString, + vceLinkTxP1Pkt Counter64, + vceLinkRxP1Pkt Counter64, + vceLinkTxP1Bytes Counter64, + vceLinkRxP1Bytes Counter64, + vceLinkTxP2Pkt Counter64, + vceLinkRxP2Pkt Counter64, + vceLinkTxP2Bytes Counter64, + vceLinkRxP2Bytes Counter64, + vceLinkTxP3Pkt Counter64, + vceLinkRxP3Pkt Counter64, + vceLinkTxP3Bytes Counter64, + vceLinkRxP3Bytes Counter64, + vceLinkTxCtlPkt Counter64, + vceLinkRxCtlPkt Counter64, + vceLinkTxCtlBytes Counter64, + vceLinkRxCtlBytes Counter64, + vceLinkTxJitter Counter64, + vceLinkRxJitter Counter64, + vceLinkTxLatency Counter64, + vceLinkRxLatency Counter64, + vceLinkTxLostPkt Counter64, + vceLinkRxLostPkt Counter64, + vceLinkVpnState VceLinkStateType, + vceLinkPublicIpType InetAddressType, + vceLinkPublicIp InetAddress, + vceLinkLocalIpType InetAddressType, + vceLinkLocalIp InetAddress, + vceLinkVlanId Integer32, + vceLinkMtu Integer32, + vceLinkItf DisplayString, + vceLinkState VceLinkStateType, + vceLinkVeloSvcReachable TruthValue, + vceLinkTotTxPkts Counter64, + vceLinkTotRxPkts Counter64, + vceLinkTotTxbytes Counter64, + vceLinkTotRxBytes Counter64, + vceLinkIf InterfaceIndex, + vceLinkNextHopType InetAddressType, + vceLinkNextHop InetAddress + } + +-------------------------------- +-- .linkEntry -- +-- -- +-- Contains OIDs: -- +-- .vceLinkIntId(2) -- +-- .vceLinkName(3) -- +-- ... -- +-- ... -- +-- ... -- +-- .vceLinkNextHop(42) -- +-------------------------------- +vceLinkIntId OBJECT-TYPE + SYNTAX UUID + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "A unique value, greater than zero, for each link." +::= { vceLinkEntry 2 } + +vceLinkName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The textual name configured for the link." +::= { vceLinkEntry 3 } + +vceLinkTxP1Pkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets transmitted through P1 link." +::= { vceLinkEntry 4 } + +vceLinkRxP1Pkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets received through P1 link." +::= { vceLinkEntry 5 } + +vceLinkTxP1Bytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total Bytes transmitted through P1 link." +::= { vceLinkEntry 6 } + +vceLinkRxP1Bytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total Bytes received through P1 link." +::= { vceLinkEntry 7 } + +vceLinkTxP2Pkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets transmitted through P2 link." +::= { vceLinkEntry 8 } + +vceLinkRxP2Pkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets received through P2 link." +::= { vceLinkEntry 9 } + +vceLinkTxP2Bytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total Bytes transmitted through P2 link." +::= { vceLinkEntry 10 } + +vceLinkRxP2Bytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total Bytes received through P2 link." +::= { vceLinkEntry 11 } + +vceLinkTxP3Pkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets transmitted through P3 link." +::= { vceLinkEntry 12 } + +vceLinkRxP3Pkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets received through P3 link." +::= { vceLinkEntry 13 } + +vceLinkTxP3Bytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total Bytes transmitted through P3 link." +::= { vceLinkEntry 14 } + +vceLinkRxP3Bytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total Bytes received through P3 link." +::= { vceLinkEntry 15 } + +vceLinkTxCtlPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total control packets transmitted." +::= { vceLinkEntry 16 } + +vceLinkRxCtlPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total control packets received." +::= { vceLinkEntry 17 } + +vceLinkTxCtlBytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total control bytes transmitted." +::= { vceLinkEntry 18 } + +vceLinkRxCtlBytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total control bytes received." +::= { vceLinkEntry 19 } + +vceLinkTxJitter OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total outbound jitter." +::= { vceLinkEntry 20 } + +vceLinkRxJitter OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total inbound jitter." +::= { vceLinkEntry 21 } + +vceLinkTxLatency OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total outbound latency." +::= { vceLinkEntry 22 } + +vceLinkRxLatency OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total inbound latency." +::= { vceLinkEntry 23 } + +vceLinkTxLostPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total outbound loss packets." +::= { vceLinkEntry 24 } + +vceLinkRxLostPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total inbound loss packets." +::= { vceLinkEntry 25 } + +vceLinkVpnState OBJECT-TYPE + SYNTAX VceLinkStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "State of VPN connection." +::= { vceLinkEntry 26 } + +vceLinkPublicIpType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Type of public IP address of the link." +::= { vceLinkEntry 27 } + +vceLinkPublicIp OBJECT-TYPE + SYNTAX InetAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Public IP address of the link." +::= { vceLinkEntry 28 } + +vceLinkLocalIpType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Type of local IP address assigned." +::= { vceLinkEntry 29 } + + +vceLinkLocalIp OBJECT-TYPE + SYNTAX InetAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Local IP address assigned." +::= { vceLinkEntry 30 } + +vceLinkVlanId OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "VLAN ID assigned." +::= { vceLinkEntry 31 } + +vceLinkMtu OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "MTU set for the link." +::= { vceLinkEntry 32 } + +vceLinkItf OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Interface logic name of the link." +::= { vceLinkEntry 33 } + +vceLinkState OBJECT-TYPE + SYNTAX VceLinkStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "State of the Link." +::= { vceLinkEntry 34 } + +vceLinkVeloSvcReachable OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Reachability of the service state." +::= { vceLinkEntry 35 } + +vceLinkTotTxPkts OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets transmitted." +::= { vceLinkEntry 36 } + +vceLinkTotRxPkts OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total packets received." +::= { vceLinkEntry 37 } + +vceLinkTotTxbytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total bytes transmitted." +::= { vceLinkEntry 38 } + +vceLinkTotRxBytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total bytes received." +::= { vceLinkEntry 39 } + +vceLinkIf OBJECT-TYPE + SYNTAX InterfaceIndex + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Interface Index of the vceLink bounded interface." +::= { vceLinkEntry 40 } + +vceLinkNextHopType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Type of the link Next Hop IP address." +::= { vceLinkEntry 41 } + +vceLinkNextHop OBJECT-TYPE + SYNTAX InetAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The link Next Hop IP address." +::= { vceLinkEntry 42 } + + +-------------------------------- +-- .vcePath(5) -- +-------------------------------- +vcePathGroup OBJECT-GROUP + OBJECTS { + vcePathNum, + vcePathIpType, + vcePathIp, + vcePathPeerName, + vcePathState, + vcePathUpTime, + vcePathRxState, + vcePathTxState, + vcePathTunlMode, + vcePathTxAveLatency, + vcePathRxAveLatency, + vcePathRxBytes, + vcePathTxBytes, + vcePathRxLostPkt, + vcePathTxLostPkt, + vcePathRxPkt, + vcePathTxPkt, + vcePathRxJitter, + vcePathTxJitter + } + STATUS current + DESCRIPTION "Conformance group for vcePathGroup objects." +::= { vcePath 1 } +vcePathObject OBJECT IDENTIFIER ::= { vcePath 2 } + +vcePathNum OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of path presented on the VeloCloud Edge." +::= { vcePathObject 1 } + +vcePathTable OBJECT-TYPE + SYNTAX SEQUENCE OF VcePathEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "A list of path entries. The number of entries + is given by the value of vcePathNum." +::= { vcePathObject 2 } + +vcePathEntry OBJECT-TYPE + SYNTAX VcePathEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "An entry containing additional management information + applicable to a particular path" + INDEX { vcePathIfIntId, vcePathGwAddrType, vcePathGwAddr } +::= { vcePathTable 1 } + +VcePathEntry ::= + SEQUENCE { + vcePathIfIntId UUID, + vcePathIpType InetAddressType, + vcePathIp InetAddress, + vcePathGwAddrType InetAddressType, + vcePathGwAddr InetAddress, + vcePathPeerName DisplayString, + vcePathState VcePathStateType, + vcePathUpTime TimeTicks, + vcePathRxState VcePathStateType, + vcePathTxState VcePathStateType, + vcePathTunlMode VcePathTunlModeType, + vcePathTxAveLatency Integer32, + vcePathRxAveLatency Integer32, + vcePathRxBytes Counter64, + vcePathTxBytes Counter64, + vcePathRxLostPkt Counter64, + vcePathTxLostPkt Counter64, + vcePathRxPkt Counter64, + vcePathTxPkt Counter64, + vcePathRxJitter Counter64, + vcePathTxJitter Counter64 + } + +-------------------------------- +-- .pathEntry -- +-- -- +-- Contains OIDs: -- +-- .vcePathIfIntId(1) -- +-- ... -- +-- ... -- +-- ... -- +-- .vcePathTxJitter(22) -- +-------------------------------- +vcePathIfIntId OBJECT-TYPE + SYNTAX UUID + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "A unique value, greater than zero, representing the internal id of the + link used by the path." +::= { vcePathEntry 1 } + +vcePathIpType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Type of the path IP address." +::= { vcePathEntry 2 } + +vcePathIp OBJECT-TYPE + SYNTAX InetAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The IP address of the path." +::= { vcePathEntry 3 } + +vcePathGwAddrType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "Type of path gateway IP address." +::= { vcePathEntry 4 } + +vcePathGwAddr OBJECT-TYPE + SYNTAX InetAddress + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "The path gateway IP address." +::= { vcePathEntry 5 } + +vcePathPeerName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The textual name configured for the path." +::= { vcePathEntry 6 } + +vcePathState OBJECT-TYPE + SYNTAX VcePathStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The current state of the path." +::= { vcePathEntry 7 } + +vcePathUpTime OBJECT-TYPE + SYNTAX TimeTicks + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total uptime of the path in miliseconds." +::= { vcePathEntry 8 } + +vcePathRxState OBJECT-TYPE + SYNTAX VcePathStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The receive state of the path." +::= { vcePathEntry 10 } + +vcePathTxState OBJECT-TYPE + SYNTAX VcePathStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The transmit state of the path." +::= { vcePathEntry 11 } + +vcePathTunlMode OBJECT-TYPE + SYNTAX VcePathTunlModeType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The mode type of the path tunnel." +::= { vcePathEntry 12 } + +vcePathTxAveLatency OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The average inbound latency measured on the path." +::= { vcePathEntry 13 } + +vcePathRxAveLatency OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The average inbound latency measured on the path." +::= { vcePathEntry 14 } + +vcePathRxBytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of received bytes." +::= { vcePathEntry 15 } + +vcePathTxBytes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of transmitted bytes." +::= { vcePathEntry 16 } + +vcePathRxLostPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The Total number of lost inbound packets." +::= { vcePathEntry 17 } + +vcePathTxLostPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of lost outbound packets." +::= { vcePathEntry 18 } + +vcePathRxPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total number of received packets." +::= { vcePathEntry 19 } + +vcePathTxPkt OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total number of transmitted packets." +::= { vcePathEntry 20 } + +vcePathRxJitter OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total inbound jitter." +::= { vcePathEntry 21 } + +vcePathTxJitter OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "Total outbound jitter." +::= { vcePathEntry 22 } + + +-------------------------------- +-- .vceARP(6) -- +-------------------------------- +vceArpGroup OBJECT-GROUP + OBJECTS { + vceArpNum, + vceArpMac, + vceArpStag, + vceArpCtag, + vceArpState + } + STATUS current + DESCRIPTION "Conformance group for vceArpGroup objects." +::= { vceARP 1 } +vceArpObject OBJECT IDENTIFIER ::= { vceARP 2 } + +vceArpNum OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The total number of arp entries presented on the VeloCloud Edge." +::= { vceArpObject 1 } + +vceArpTable OBJECT-TYPE + SYNTAX SEQUENCE OF VceArpEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "A list of arp entries. The number of entries + is given by the value of vceArpNum." +::= { vceArpObject 2 } + +vceArpEntry OBJECT-TYPE + SYNTAX VceArpEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "An entry containing additional management information + applicable to a particular arp entry" + INDEX { vceArpItf, vceArpIpAddrType, vceArpIpAddr } +::= { vceArpTable 1 } + +VceArpEntry ::= + SEQUENCE { + vceArpItf InterfaceIndex, + vceArpIpAddrType InetAddressType, + vceArpIpAddr InetAddress, + vceArpMac PhysAddress, + vceArpStag Integer32, + vceArpCtag Integer32, + vceArpState VceArpStateType + } + +-------------------------------- +-- .arpEntry -- +-- -- +-- Contains OIDs: -- +-- .vcerpItf(1) -- +-- ... -- +-- .vceArpState(7) -- +-------------------------------- +vceArpItf OBJECT-TYPE + SYNTAX InterfaceIndex + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "A unique value, greater than zero, for the interface used by the arp entry." +::= { vceArpEntry 1 } + +vceArpIpAddrType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "The type of arp IP address." +::= { vceArpEntry 2 } + +vceArpIpAddr OBJECT-TYPE + SYNTAX InetAddress + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION "The Ip address of the arp entry" +::= { vceArpEntry 3 } + +vceArpMac OBJECT-TYPE + SYNTAX PhysAddress (SIZE(0..65535)) + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The MAC address of the arp entry" +::= { vceArpEntry 4 } + +vceArpStag OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "S-tag value" +::= { vceArpEntry 5 } + +vceArpCtag OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "C-tag value" +::= { vceArpEntry 6 } + +vceArpState OBJECT-TYPE + SYNTAX VceArpStateType + MAX-ACCESS read-only + STATUS current + DESCRIPTION "The State of arp entry" +::= { vceArpEntry 7 } + +END
\ No newline at end of file diff --git a/MIBS/vmware/VELOCLOUD-MIB b/MIBS/vmware/VELOCLOUD-MIB new file mode 100644 index 0000000..5928b32 --- /dev/null +++ b/MIBS/vmware/VELOCLOUD-MIB @@ -0,0 +1,42 @@ +------------------------------- +-- VeloCloud MIB Definitions -- +-- -- +-- Contains: -- +-- .velocloud(45346) -- +-- .orchestrator(1) -- +-- .edge(2) -- +-- .gateway(3) -- +------------------------------- + +VELOCLOUD-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, enterprises FROM SNMPv2-SMI +; + +velocloud MODULE-IDENTITY + LAST-UPDATED "201908020000Z" + ORGANIZATION "VMware Corporation" + CONTACT-INFO "postal: VMware Corporation + World Headquarters + 3401 Hillview Avenue + Palo Alto, CA 943043 + USA + + web: www.velocloud.com + email: contact@velocloud.com" + DESCRIPTION "Top-level infrastructure of the VeloCloud enterprise MIB tree" + + REVISION "201908020000Z" + DESCRIPTION "Implementation of VeloCloud Edge MIB Objects" + + REVISION "201701180000Z" + DESCRIPTION "Implementation of VCO MIB Objects" + + REVISION "201701130000Z" + DESCRIPTION "Inital definition of VeloCloud MIB Objects" +::= { enterprises 45346 } + +modules OBJECT IDENTIFIER ::= { velocloud 1 } + +END
\ No newline at end of file diff --git a/MIBS/vmware/VMWARE-AGENTCAP-MIB b/MIBS/vmware/VMWARE-AGENTCAP-MIB new file mode 100644 index 0000000..5f1b257 --- /dev/null +++ b/MIBS/vmware/VMWARE-AGENTCAP-MIB @@ -0,0 +1,548 @@ +-- ********************************************************** +-- Copyright 2008 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-AGENTCAP-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + vmwareAgentCapabilities + FROM VMWARE-ROOT-MIB + AGENT-CAPABILITIES + FROM SNMPv2-CONF; +vmwAgentCapabilityMIB MODULE-IDENTITY + LAST-UPDATED "200810270000Z" + 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 module defines agent capabilities for VMware agents." + REVISION "200810270000Z" + DESCRIPTION + "Capabilities for VMware ESX 4.0 added." + ::= { vmwareAgentCapabilities 1 } + +vmwEsxCapability OBJECT IDENTIFIER ::= { vmwAgentCapabilityMIB 1 } + + +vmwESX41x AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.1.x" + STATUS current + DESCRIPTION + "Release 4.1.x for VMware ESX" + 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above implies this: + -- 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 interface. + ESX virtual layer 2 switches may support changing administrative state + of physical network interfaces (nics)." + + 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." + + -- ********************* ************ ************ *************** *** + + -- REVISION 200712270000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 200810230000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 200712270000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvNotificationGroup + } + + ::= { vmwEsxCapability 2 } + + +vmwESX40x AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.0.x" + STATUS current + DESCRIPTION + "Release 4.0.x for VMware ESX" + 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above implies this: + -- 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 + SYNTAX INTEGER { up(1) } + ACCESS read-only + DESCRIPTION "Agent provides read-only view of system information and + does not support changing operational state." + + VARIATION ifLinkUpDownTrapEnable + ACCESS read-only + DESCRIPTION "Agent provides read-only view of system information." + + -- ifXTable not implemented + VARIATION ifTableLastChange + ACCESS not-implemented + DESCRIPTION "post RFC 1213 managed objects not implemented." + + VARIATION ifConnectorPresent + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + VARIATION ifHighSpeed + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + VARIATION ifName + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + VARIATION ifAlias + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + -- ifFixedLengthGroup + VARIATION ifAlias + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifHCFixedLengthGroup + VARIATION ifHCInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifPacketGroup + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifMtu + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifPromiscuousMode + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + + -- ifHCPacketGroup + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifMtu + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifPromiscuousMode + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifVHCPacketGroup + VARIATION ifHCInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifMtu + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifPromiscuousMode + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifCounterDiscontinuityGroup + VARIATION ifCounterDiscontinuityTime + ACCESS not-implemented + DESCRIPTION "Required if Performance counters are implemented." + + -- 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." + + + -- ********************* ************ ************ *************** *** + + -- REVISION 200712270000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 200810230000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 200712270000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvNotificationGroup + } + + ::= { vmwEsxCapability 1 } + +END + diff --git a/MIBS/vmware/VMWARE-CIMOM-MIB b/MIBS/vmware/VMWARE-CIMOM-MIB new file mode 100644 index 0000000..0e7aad1 --- /dev/null +++ b/MIBS/vmware/VMWARE-CIMOM-MIB @@ -0,0 +1,80 @@ +-- ********************************************************** +-- Copyright 2010 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-CIMOM-MIB DEFINITIONS ::= BEGIN + + IMPORTS + MODULE-IDENTITY, NOTIFICATION-TYPE + FROM SNMPv2-SMI + MODULE-COMPLIANCE, NOTIFICATION-GROUP + FROM SNMPv2-CONF + vmwEnvIndicationTime + FROM VMWARE-ENV-MIB + vmwProductSpecific + FROM VMWARE-ROOT-MIB; + + vmwCIMOMMIB MODULE-IDENTITY + LAST-UPDATED "201008200000Z" + 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 instrumentation of a CIM Object Manager." +REVISION "201008200000Z" +DESCRIPTION + "Information on a CIM object manager subsystem." +::= { vmwCimOm 10 } + +vmwCimOm OBJECT IDENTIFIER + ::= { vmwProductSpecific 90 } + +vmwCimOmNotifications OBJECT IDENTIFIER + ::= {vmwCimOm 0 } + +vmwCimOmHeartbeat NOTIFICATION-TYPE + OBJECTS { vmwEnvIndicationTime } + 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." + ::= { vmwCimOmNotifications 401 } + +-- conformance information +vmwCimOmMIBConformance +OBJECT IDENTIFIER ::= { vmwCimOm 2 } +vmwCimOmMIBCompliances +OBJECT IDENTIFIER ::= { vmwCimOmMIBConformance 1 } +vmwCimOmMIBGroups OBJECT IDENTIFIER ::= { vmwCimOmMIBConformance 2 } + +-- compliance statements + +vmwCimOmMIBBasicCompliance MODULE-COMPLIANCE +STATUS current +DESCRIPTION + "The compliance statement for entities which implement the + VMWARE-CIMOM-MIB." +MODULE -- this module +MANDATORY-GROUPS { vmwCimOmNotificationGroup } +GROUP vmwCimOmNotificationGroup +DESCRIPTION + "This group is mandatory for systems with CIM object manager." +::= { vmwCimOmMIBCompliances 4 } + +vmwCimOmNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwCimOmHeartbeat + } + STATUS current + DESCRIPTION + "Notifications related to CIM Object Manager subsystem." + ::= { vmwCimOmMIBGroups 2 } + + +END diff --git a/MIBS/vmware/VMWARE-ENV-MIB b/MIBS/vmware/VMWARE-ENV-MIB new file mode 100644 index 0000000..a063822 --- /dev/null +++ b/MIBS/vmware/VMWARE-ENV-MIB @@ -0,0 +1,836 @@ +-- ********************************************************** +-- Copyright 2008-2017 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-ENV-MIB DEFINITIONS ::= BEGIN + +IMPORTS + Counter32, Integer32, NOTIFICATION-TYPE, OBJECT-TYPE, TimeTicks, + MODULE-IDENTITY, OBJECT-IDENTITY + FROM SNMPv2-SMI + DisplayString, DateAndTime + FROM SNMPv2-TC + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + vmwProductSpecific, vmwNotifications + FROM VMWARE-ROOT-MIB + vmwESX + FROM VMWARE-PRODUCTS-MIB + VmwLongSnmpAdminString, VmwCIMSeverity, VmwSubsystemStatus, VmwSubsystemTypes, + VmwCIMAlertTypes, VmwCIMAlertFormat, VmwCimName + FROM VMWARE-TC-MIB; + + vmwEnvironmentalMIB MODULE-IDENTITY + LAST-UPDATED "201706050000Z" + 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 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 "201706050000Z" +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. + The first implementation of vmwEnvTable adds vmwEnvHrDeviceIndex and + changes vmwEnvHardwareTime syntax from TimeTicks to DateAndTime" + +REVISION "201005120000Z" +DESCRIPTION + "This revision adds support for CIM OMC_IpmiAlertIndication as the source of events + instead of only IPMI sensors thus more areas of hardware can be reported on. + This required a new notification set to be defined replacing previous + notifications." + +REVISION "200810300000Z" +DESCRIPTION + "Introduce vmwESXNotification to match ESX 3.5 agent." + +REVISION "200712270000Z" +DESCRIPTION + "This is the first revision of this MIB module." +::= { vmwEnv 10 } + +vmwEnv OBJECT IDENTIFIER + ::= { vmwProductSpecific 20 } + +vmwESXNotifications OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Parent of all ESX specific notifications (traps, informs)." + ::= { vmwESX 0 } + +vmwEnvNumber OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Count of number of conceptual rows in vmwEnvTable." + ::= { vmwEnv 1 } + +vmwEnvLastChange OBJECT-TYPE + SYNTAX TimeTicks + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The value of sysUptime when a conceptual row was added + 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 IPMI BMC device. + One conceptual row is maintained for each reporting component. + 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 + "One entry for each physical component reporting its + status to ESX Operating System." + INDEX { vmwEnvIndex } + ::= { vmwEnvTable 1 } + +VmwEnvEntry ::= SEQUENCE { + vmwEnvIndex Integer32, + vmwSubsystemType VmwSubsystemTypes, + vmwHardwareStatus VmwSubsystemStatus, + vmwEventDescription DisplayString, + vmwEnvHardwareTime DateAndTime, + vmwEnvHrDeviceIndex Integer32, + vmwEnvSelSensorNumber Integer32 +} + +vmwEnvIndex OBJECT-TYPE + SYNTAX Integer32 (1..65535) + MAX-ACCESS not-accessible + STATUS current + 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 + "Hardware component reporting environmental state" + ::= { vmwEnvEntry 2 } + +vmwHardwareStatus OBJECT-TYPE + SYNTAX VmwSubsystemStatus + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Last reported state of this component" + ::= { vmwEnvEntry 3 } + +vmwEventDescription OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Human readable description of this event" + ::= { vmwEnvEntry 4 } + +vmwEnvHardwareTime OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS read-only + STATUS current + 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 } + +vmwEnvHrDeviceIndex OBJECT-TYPE + SYNTAX Integer32 (0|1..2147483647) + MAX-ACCESS read-only + STATUS current + 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 + "Number of HTTP POST msgs containing CIM Indications in XML as received by agent." + ::= { vmwEnv 101 } + +vmwEnvLastIn OBJECT-TYPE + SYNTAX TimeTicks + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "sysUptime when agent last received an indication." + ::= { vmwEnv 102 } + +vmwEnvOutNotifications OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of notifications (traps|informs) sent that originated as CIM indication." + ::= { vmwEnv 103 } + +vmwEnvInErrs OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of CIM Indications that agent did not complete receipt of." + ::= { vmwEnv 104 } + +vmwEnvIndOidErrs OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of CIM Indications having a MappingString qualifier for which the value was not a valid oid." + ::= { vmwEnv 105 } + +vmwEnvCvtValueErrs OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + 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 } + +vmwEnvCvtSyntaxErrs OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of CIM Indication properties having a MappingString qualifier + for which the cim type could not be converted to smi syntax." + ::= { vmwEnv 107 } + +vmwEnvCvtOidErrs OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of CIM Indication properties having a MappingString qualifier + for which the the oid was not valid." + ::= { vmwEnv 108 } + +vmwEnvGetClassErrs OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of CIM GetClass operations over a given cim indication class and namespace + could not be completed (timeout) or returned error." + ::= { vmwEnv 109 } + +vmwEnvPropertySkips OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + 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 } + +vmwEnvIndicationSkips OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + 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 deprecated + DESCRIPTION + "A short description of the Indication." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property Description" + ::= { vmwEnvCIM 1 } + +vmwEnvEventTime OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS accessible-for-notify + 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 + if in the incoming CIM indication the value is + 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." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property EventTime" + ::= { vmwEnvCIM 2 } + +vmwEnvIndicationTime OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS accessible-for-notify + 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 + Indication is not capable of determining this + information and delivers a null IndicationTime property. Note that IndicationTime may be the same + for two Indications that are generated in rapid succession." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property IndicationTime" + ::= { vmwEnvCIM 3 } + +vmwEnvPerceivedSeverity OBJECT-TYPE + SYNTAX VmwCIMSeverity + MAX-ACCESS accessible-for-notify + STATUS deprecated + DESCRIPTION + "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" + ::= { vmwEnvCIM 4 } + +vmwEnvAlertType OBJECT-TYPE + SYNTAX VmwCIMAlertTypes + MAX-ACCESS accessible-for-notify + STATUS deprecated + DESCRIPTION + "Primary classification of the Indication." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property AlertType" + ::= { vmwEnvCIM 5 } + +vmwEnvSysCreationClassName OBJECT-TYPE + SYNTAX VmwCimName + MAX-ACCESS accessible-for-notify + STATUS deprecated + DESCRIPTION + "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" + ::= { vmwEnvCIM 6 } + +vmwEnvAlertingElement OBJECT-TYPE + SYNTAX VmwCimName + MAX-ACCESS accessible-for-notify + 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, + 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 + the Alert is generated. The path or identifying string + is formatted per the AlertingElementFormat property." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property AlertingManagedElement" + ::= { vmwEnvCIM 7 } + +vmwEnvAlertingFormat OBJECT-TYPE + SYNTAX VmwCIMAlertFormat + MAX-ACCESS accessible-for-notify + STATUS deprecated + DESCRIPTION + "The format of the AlertingManagedElement property is + interpretable based upon the value of this property." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property AlertingElementFormat" + ::= { vmwEnvCIM 8 } + +vmwEnvSystemName OBJECT-TYPE + SYNTAX VmwCimName + MAX-ACCESS accessible-for-notify + STATUS deprecated + DESCRIPTION + "The scoping System's Name for the Provider generating this message." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property SystemName" + ::= { vmwEnvCIM 9 } + +vmwEnvProviderName OBJECT-TYPE + SYNTAX VmwCimName + MAX-ACCESS accessible-for-notify + STATUS deprecated + DESCRIPTION + "The name of the CIM provider, a software module loaded into the CIM subsystem, generating this message." + REFERENCE + "http://www.dmtf.org/standards/cim/cim_schema_v2240 : file CIM_AlertIndication.mof : property ProviderName" + ::= { vmwEnvCIM 10 } + + +vmwESXEnvHardwareAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + +vmwESXEnvBatteryAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + +vmwESXEnvChassisAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + + +vmwESXEnvThermalAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + +vmwESXEnvDiskAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + +vmwESXEnvPowerAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + +vmwESXEnvProcessorAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + +vmwESXEnvMemoryAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + + +vmwESXEnvBIOSAlert NOTIFICATION-TYPE + OBJECTS {vmwEnvDescription, vmwEnvEventTime, vmwEnvIndicationTime, vmwEnvPerceivedSeverity, + vmwEnvAlertType, vmwEnvSysCreationClassName, vmwEnvAlertingElement, vmwEnvAlertingFormat, + vmwEnvSystemName, vmwEnvProviderName } + 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 } + +-- conformance information +vmwEnvironmentalMIBConformance +OBJECT IDENTIFIER ::= { vmwEnvironmentalMIB 2 } +vmwEnvironmentMIBCompliances +OBJECT IDENTIFIER ::= { vmwEnvironmentalMIBConformance 1 } +vmwEnvMIBGroups OBJECT IDENTIFIER ::= { vmwEnvironmentalMIBConformance 2 } + +-- compliance statements + +vmwEnvMIBBasicCompliance4 MODULE-COMPLIANCE +STATUS current +DESCRIPTION + "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 } +GROUP vmwESXEnvNotificationGroup2 +DESCRIPTION + "This group is mandatory for ESX based systems agents." +::= { vmwEnvironmentMIBCompliances 4 } + +vmwEnvMIBBasicCompliance2 MODULE-COMPLIANCE +STATUS deprecated +DESCRIPTION + "The compliance statement for entities which implement the + VMWARE-ENV-MIB." +MODULE -- this module +MANDATORY-GROUPS { vmwEnvironmentGroup } + + +GROUP vmwESXEnvNotificationGroup +DESCRIPTION + "This group is mandatory for ESX based systems agents." + +GROUP vmwEnvNotificationGroup +DESCRIPTION + "This group is mandatory for vmware based systems agents." +::= { vmwEnvironmentMIBCompliances 3 } + +vmwEnvMIBBasicCompliance MODULE-COMPLIANCE +STATUS obsolete +DESCRIPTION + "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, + vmwEnvInIndications, + vmwEnvLastIn, + vmwEnvOutNotifications, + vmwEnvInErrs, + vmwEnvIndOidErrs, + vmwEnvCvtValueErrs, + vmwEnvCvtSyntaxErrs, + vmwEnvCvtOidErrs, + vmwEnvGetClassErrs, + vmwEnvPropertySkips, + vmwEnvIndicationSkips, + vmwEnvDescription, + vmwEnvEventTime, + vmwEnvIndicationTime, + vmwEnvPerceivedSeverity, + vmwEnvAlertType, + vmwEnvSysCreationClassName, + vmwEnvAlertingElement, + vmwEnvAlertingFormat, + vmwEnvSystemName, + vmwEnvProviderName + } + STATUS obsolete + DESCRIPTION + "These objects provide physical hardware environmental details as reported by CIM subsystem." + ::= { vmwEnvMIBGroups 5 } + +vmwEnvironmentGroup OBJECT-GROUP + OBJECTS { + vmwEnvNumber, + vmwEnvLastChange, + vmwSubsystemType, + vmwHardwareStatus, + vmwEventDescription, + vmwEnvHardwareTime + } + STATUS deprecated + DESCRIPTION + "These objects provide physical hardware environmental details." + ::= { vmwEnvMIBGroups 1 } + +vmwEnvNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwEnvHardwareEvent + } + STATUS deprecated + DESCRIPTION + "Notifications related to physical subsystems." + ::= { vmwEnvMIBGroups 2 } + +vmwESXEnvNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwESXEnvHardwareEvent + } + STATUS deprecated + DESCRIPTION + "ESX System specific notifications about physical subsystems." + ::= { vmwEnvMIBGroups 3 } + +vmwESXEnvNotificationGroup2 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwESXEnvHardwareAlert, + vmwESXEnvBatteryAlert, + vmwESXEnvChassisAlert, + vmwESXEnvThermalAlert, + vmwESXEnvDiskAlert, + vmwESXEnvPowerAlert, + vmwESXEnvProcessorAlert, + vmwESXEnvMemoryAlert, + vmwESXEnvBIOSAlert + } + 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. diff --git a/MIBS/vmware/VMWARE-ESX-AGENTCAP-MIB b/MIBS/vmware/VMWARE-ESX-AGENTCAP-MIB new file mode 100644 index 0000000..7341ef1 --- /dev/null +++ b/MIBS/vmware/VMWARE-ESX-AGENTCAP-MIB @@ -0,0 +1,3029 @@ +-- ********************************************************** +-- Copyright 2008-2022 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-ESX-AGENTCAP-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + vmwareAgentCapabilities + FROM VMWARE-ROOT-MIB + AGENT-CAPABILITIES + FROM SNMPv2-CONF; +vmwAgentCapabilityMIB MODULE-IDENTITY + LAST-UPDATED "202209150000Z" + 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: Downloading MIB modules http://kb.vmware.com/kb/1013445 + OID list http://kb.vmware.com/kb/2054359 + " + DESCRIPTION + "This module defines agent capabilities for deployed VMware ESX agents by release." + + REVISION "202209150000Z" + DESCRIPTION + "Capabilities for VMware VSphere (Release 8.0) ESXi 2022 added." + + REVISION "202003270000Z" + DESCRIPTION + "Capabilities for VMware VSphere (Release 7.0) ESXi 2020 added." + REVISION "201710130000Z" + DESCRIPTION + "Capabilities for VMware VSphere (Release 6.7) ESXi 2017 added." + REVISION "201604220000Z" + DESCRIPTION + "Capabilities for VMware VSphere ESXi 2016 added." + REVISION "201501120000Z" + DESCRIPTION + "Renamed mib module to reflect this contains only the VMware ESX agent." + + REVISION "201408020000Z" + DESCRIPTION + "Capabilities for VMware VSphere ESXi 2015 added." + + REVISION "201210030000Z" + DESCRIPTION + "Capabilities for VMware ESX 5.5 agent added." + + REVISION "201207130000Z" + DESCRIPTION + "Capabilities for VMware ESX 5.1 agent added." + + REVISION "201010180000Z" + DESCRIPTION + "Capabilities for VMware ESX 5.0 added." + REVISION "200810270000Z" + DESCRIPTION + "Capabilities for VMware ESX 4.0 added." + ::= { vmwareAgentCapabilities 1 } + +vmwEsxCapability OBJECT IDENTIFIER ::= { vmwAgentCapabilityMIB 1 } + + +-- +-- ESXi 8.0 and follow up patch releases +-- + +vmwESX80x AGENT-CAPABILITIES + PRODUCT-RELEASE + "8.0.x" + STATUS current + DESCRIPTION + "Release 8.0 for VMware ESXi supports SNMPv1, SNMPv2c, and SNMPv3. + Changes in 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above clause implies this: + -- VARIATION authenticationFailure + -- ACCESS not-implemented + -- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled." + + -- ********************* ************ ************ *************** *** + -- RFC 3412 + SUPPORTS SNMP-MPD-MIB + INCLUDES { + snmpMPDGroup + } + + -- ********************* ************ ************ *************** *** + -- 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. + ESX virtual switches support changing administrative state + of physical network interfaces (nics) up or down. For example the command: + esxcli network nic [up|down] -n vmnic0 + Virtual vmware interfaces (ifType 238) also support changing administratie state: + network ip interface set --enabled [yes|no] -i vmk0 + " + + 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 SNMPv2/3 Contexts for multiple instances + 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, + udpHCGroup + } + + -- ********************* ************ ************ *************** *** + -- RFC 4022 + -- supports SNMPv2/3 Contexts for multiple instances + SUPPORTS TCP-MIB + INCLUDES { + tcpBaseGroup, + tcpConnectionGroup, + tcpListenerGroup + } + + -- RFC 2790 + -- NOTE: For storage luns larger than Integer32 (Terabyte) this agent will report INT_MAX + -- Enable Largestorage: true CLI: esxcli system snmp set largestorage + SUPPORTS HOST-RESOURCES-MIB + INCLUDES { + hrSystemGroup, + hrStorageGroup, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active ESX Shell sessions" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + 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. pnic 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 200810150000Z + SUPPORTS IEEE8021-BRIDGE-MIB + INCLUDES { + ieee8021BridgeBaseBridgeGroup, + ieee8021BridgeBasePortGroup, + ieee8021BridgeTpPortGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200810150000Z + -- virtual switch uplinks (physical ports) do perform do mac learning and will + -- not report in FDB/forwarding tables + SUPPORTS IEEE8021-Q-BRIDGE-MIB + INCLUDES { + ieee8021QBridgeBaseGroup, + ieee8021QBridgeVlanGroup, + ieee8021QBridgeVlanStaticGroup, + ieee8021QBridgePortGroup2, + ieee8021QBridgeFdbUnicastGroup, + ieee8021QBridgeFdbMulticastGroup, + ieee8021QBridgeFdbStaticGroup, + ieee8021QBridgeVlanStatisticsGroup + } + -- VARATION ieee8021QBridgeVlanCurrentUntaggedPorts + -- Reports count of 0 if only untagged vlan access (vid 0) is defined + + -- ********************* ************ ************ *************** *** + -- REVISION 200706200000Z + -- VDS link aggregations are not reported this release, issue PR 859941 + -- only VSS, traditional vswitch, nic teams are reported entries + SUPPORTS IEEE8023-LAG-MIB + INCLUDES { + dot3adAggGroup, + dot3adAggPortGroup, + dot3adTablesLastChangedGroup, + dot3adAggPortListGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200906080000Z + SUPPORTS LLDP-V2-MIB + INCLUDES { + lldpV2ConfigGroup, + lldpV2ConfigTxGroup, + lldpV2StatsTxGroup, + lldpV2LocSysGroup, + lldpV2ConfigRxGroup, + lldpV2StatsRxGroup, + lldpV2RemSysGroup, + lldpV2NotificationsGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201706050000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvCIMToSNMP, + vmwEnvironmentGroup2, + vmwESXEnvNotificationGroup3 + } + + -- REVISION 201008200000Z + SUPPORTS VMWARE-CIMOM-MIB + INCLUDES { + vmwCimOmNotificationGroup + } + + ::= { vmwEsxCapability 18 } + + +-- +-- ESXi 7.0 and follow up patch releases +-- + +vmwESX70x AGENT-CAPABILITIES + PRODUCT-RELEASE + "7.0.x" + STATUS current + DESCRIPTION + "Release 7.0 for VMware ESXi supports SNMPv1, SNMPv2c, and SNMPv3. + Changes in 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above clause implies this: + -- VARIATION authenticationFailure + -- ACCESS not-implemented + -- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled." + + -- ********************* ************ ************ *************** *** + -- RFC 3412 + SUPPORTS SNMP-MPD-MIB + INCLUDES { + snmpMPDGroup + } + + -- ********************* ************ ************ *************** *** + -- 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. + ESX virtual switches support changing administrative state + of physical network interfaces (nics) up or down. For example the command: + esxcli network nic [up|down] -n vmnic0 + Virtual vmware interfaces (ifType 238) also support changing administratie state: + network ip interface set --enabled [yes|no] -i vmk0 + " + + 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 SNMPv2/3 Contexts for multiple instances + 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, + udpHCGroup + } + + -- ********************* ************ ************ *************** *** + -- RFC 4022 + -- supports SNMPv2/3 Contexts for multiple instances + SUPPORTS TCP-MIB + INCLUDES { + tcpBaseGroup, + tcpConnectionGroup, + tcpListenerGroup + } + + -- RFC 2790 + -- NOTE: For storage luns larger than Integer32 (Terabyte) this agent will report INT_MAX + -- Enable Largestorage: true CLI: esxcli system snmp set largestorage + SUPPORTS HOST-RESOURCES-MIB + INCLUDES { + hrSystemGroup, + hrStorageGroup, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active ESX Shell sessions" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + 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. pnic 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 200810150000Z + SUPPORTS IEEE8021-BRIDGE-MIB + INCLUDES { + ieee8021BridgeBaseBridgeGroup, + ieee8021BridgeBasePortGroup, + ieee8021BridgeTpPortGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200810150000Z + -- virtual switch uplinks (physical ports) do perform do mac learning and will + -- not report in FDB/forwarding tables + SUPPORTS IEEE8021-Q-BRIDGE-MIB + INCLUDES { + ieee8021QBridgeBaseGroup, + ieee8021QBridgeVlanGroup, + ieee8021QBridgeVlanStaticGroup, + ieee8021QBridgePortGroup2, + ieee8021QBridgeFdbUnicastGroup, + ieee8021QBridgeFdbMulticastGroup, + ieee8021QBridgeFdbStaticGroup, + ieee8021QBridgeVlanStatisticsGroup + } + -- VARATION ieee8021QBridgeVlanCurrentUntaggedPorts + -- Reports count of 0 if only untagged vlan access (vid 0) is defined + + -- ********************* ************ ************ *************** *** + -- REVISION 200706200000Z + -- VDS link aggregations are not reported this release, issue PR 859941 + -- only VSS, traditional vswitch, nic teams are reported entries + SUPPORTS IEEE8023-LAG-MIB + INCLUDES { + dot3adAggGroup, + dot3adAggPortGroup, + dot3adTablesLastChangedGroup, + dot3adAggPortListGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200906080000Z + SUPPORTS LLDP-V2-MIB + INCLUDES { + lldpV2ConfigGroup, + lldpV2ConfigTxGroup, + lldpV2StatsTxGroup, + lldpV2LocSysGroup, + lldpV2ConfigRxGroup, + lldpV2StatsRxGroup, + lldpV2RemSysGroup, + lldpV2NotificationsGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201706050000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvCIMToSNMP, + vmwEnvironmentGroup2, + vmwESXEnvNotificationGroup3 + } + + -- REVISION 201008200000Z + SUPPORTS VMWARE-CIMOM-MIB + INCLUDES { + vmwCimOmNotificationGroup + } + + ::= { vmwEsxCapability 17 } + + +-- +-- ESXi 6.7 and follow up patch releases +-- + +vmwESX67x AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.7.x" + STATUS current + DESCRIPTION + "Release 6.7 for VMware ESXi supports SNMPv1, SNMPv2c, and SNMPv3. + VMWARE-ENV-MIB was fully implmented, now possible to poll BMC (IPMI) System Event Log. + New notifications were created for specific SDR sensors and agent will now notify + when IPMI SEL becomes full/capacity. + Other 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above clause implies this: + -- VARIATION authenticationFailure + -- ACCESS not-implemented + -- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled." + + -- ********************* ************ ************ *************** *** + -- RFC 3412 + SUPPORTS SNMP-MPD-MIB + INCLUDES { + snmpMPDGroup + } + + -- ********************* ************ ************ *************** *** + -- 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. + ESX virtual switches support changing administrative state + of physical network interfaces (nics) up or down. For example the command: + esxcli network nic [up|down] -n vmnic0 + Virtual vmware interfaces (ifType 238) also support changing administratie state: + network ip interface set --enabled [yes|no] -i vmk0 + " + + 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 SNMPv2/3 Contexts for multiple instances + 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, + udpHCGroup + } + + -- ********************* ************ ************ *************** *** + -- 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, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active ESX Shell sessions" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + 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. pnic 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 200810150000Z + SUPPORTS IEEE8021-BRIDGE-MIB + INCLUDES { + ieee8021BridgeBaseBridgeGroup, + ieee8021BridgeBasePortGroup, + ieee8021BridgeTpPortGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200810150000Z + -- virtual switch uplinks (physical ports) do perform do mac learning and will + -- not report in FDB/forwarding tables + SUPPORTS IEEE8021-Q-BRIDGE-MIB + INCLUDES { + ieee8021QBridgeBaseGroup, + ieee8021QBridgeVlanGroup, + ieee8021QBridgeVlanStaticGroup, + ieee8021QBridgePortGroup2, + ieee8021QBridgeFdbUnicastGroup, + ieee8021QBridgeFdbMulticastGroup, + ieee8021QBridgeFdbStaticGroup, + ieee8021QBridgeVlanStatisticsGroup + } + -- VARATION ieee8021QBridgeVlanCurrentUntaggedPorts + -- Reports count of 0 if only untagged vlan access (vid 0) is defined + + -- ********************* ************ ************ *************** *** + -- REVISION 200706200000Z + -- VDS link aggregations are not reported this release, issue PR 859941 + -- only VSS, traditional vswitch, nic teams are reported entries + SUPPORTS IEEE8023-LAG-MIB + INCLUDES { + dot3adAggGroup, + dot3adAggPortGroup, + dot3adTablesLastChangedGroup, + dot3adAggPortListGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200906080000Z + SUPPORTS LLDP-V2-MIB + INCLUDES { + lldpV2ConfigGroup, + lldpV2ConfigTxGroup, + lldpV2StatsTxGroup, + lldpV2LocSysGroup, + lldpV2ConfigRxGroup, + lldpV2StatsRxGroup, + lldpV2RemSysGroup, + lldpV2NotificationsGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201706050000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvCIMToSNMP, + vmwEnvironmentGroup2, + vmwESXEnvNotificationGroup3 + } + + -- REVISION 201008200000Z + SUPPORTS VMWARE-CIMOM-MIB + INCLUDES { + vmwCimOmNotificationGroup + } + + ::= { vmwEsxCapability 16 } + +-- +-- ESX 6.5 and follow up patch releases +-- + +vmwESX65x AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.5.x" + STATUS current + DESCRIPTION + "Release 6.5 for VMware ESXi supports SNMPv1, SNMPv2c, and SNMPv3 with a stand-alone snmpd process. + NSX VDS now supported by BRIDGE MIB modules. + No vDR instrumentation is yet available. + Agent can now handle slow responses from SAN Storage when reporting LUN storage, see + https://kb.vmware.com/kb/2135500 + This agent supports read-only protocol operations. This implies that configuring the SNMPv3 Agent + can not be done via SET operations. Hence IETF standard SNMPv3 agent configuration mibs are not provided. + The SNMPv3 protocol is fully supported once configured via the CLI command interface (esxcli system snmp) + command set or vCenter Server host profiles. 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above clause implies this: + -- VARIATION authenticationFailure + -- ACCESS not-implemented + -- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled." + + -- ********************* ************ ************ *************** *** + -- RFC 3412 + SUPPORTS SNMP-MPD-MIB + INCLUDES { + snmpMPDGroup + } + + -- ********************* ************ ************ *************** *** + -- 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. + ESX virtual switches support changing administrative state + of physical network interfaces (nics) up or down. For example the command: + esxcli network nic [up|down] -n vmnic0 + Virtual vmware interfaces (ifType 238) also support changing administratie state: + network ip interface set --enabled [yes|no] -i vmk0 + " + + 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 SNMPv2/3 Contexts for multiple instances + 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, + udpHCGroup + } + + -- ********************* ************ ************ *************** *** + -- 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, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active ESX Shell sessions" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + 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. pnic 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 200810150000Z + SUPPORTS IEEE8021-BRIDGE-MIB + INCLUDES { + ieee8021BridgeBaseBridgeGroup, + ieee8021BridgeBasePortGroup, + ieee8021BridgeTpPortGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200810150000Z + -- virtual switch uplinks (physical ports) do perform do mac learning and will + -- not report in FDB/forwarding tables + SUPPORTS IEEE8021-Q-BRIDGE-MIB + INCLUDES { + ieee8021QBridgeBaseGroup, + ieee8021QBridgeVlanGroup, + ieee8021QBridgeVlanStaticGroup, + ieee8021QBridgePortGroup2, + ieee8021QBridgeFdbUnicastGroup, + ieee8021QBridgeFdbMulticastGroup, + ieee8021QBridgeFdbStaticGroup, + ieee8021QBridgeVlanStatisticsGroup + } + -- VARATION ieee8021QBridgeVlanCurrentUntaggedPorts + -- Reports count of 0 if only untagged vlan access (vid 0) is defined + + -- ********************* ************ ************ *************** *** + -- REVISION 200706200000Z + -- VDS link aggregations are not reported this release, issue PR 859941 + -- only VSS, traditional vswitch, nic teams are reported entries + SUPPORTS IEEE8023-LAG-MIB + INCLUDES { + dot3adAggGroup, + dot3adAggPortGroup, + dot3adTablesLastChangedGroup, + dot3adAggPortListGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200906080000Z + SUPPORTS LLDP-V2-MIB + INCLUDES { + lldpV2ConfigGroup, + lldpV2ConfigTxGroup, + lldpV2StatsTxGroup, + lldpV2LocSysGroup, + lldpV2ConfigRxGroup, + lldpV2StatsRxGroup, + lldpV2RemSysGroup, + lldpV2NotificationsGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201005120000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvAlertGroup, + vmwESXEnvNotificationGroup2 + } + + -- REVISION 201008200000Z + SUPPORTS VMWARE-CIMOM-MIB + INCLUDES { + vmwCimOmNotificationGroup + } + + ::= { vmwEsxCapability 15 } + +-- +-- ESX 6.0 and follow up patch releases +-- + +vmwESX60x AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.0.x" + STATUS current + DESCRIPTION + "Release 6.0 for VMware ESXi supports SNMPv1, SNMPv2c, and SNMPv3 with a stand-alone snmpd process. + + Only Minor changes and bug fixes in this release of the SNMP Agent. + + No vDR instrumentation is yet available. + + This agent supports read-only protocol operations. This implies that configuring the SNMPv3 Agent + can not be done via SET operations. Hence IETF standard SNMPv3 agent configuration mibs are not provided. + The SNMPv3 protocol is fully supported once configured via the CLI command interface (esxcli system snmp) + command set or vCenter Server host profiles. 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above clause implies this: + -- VARIATION authenticationFailure + -- ACCESS not-implemented + -- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled." + + -- ********************* ************ ************ *************** *** + -- RFC 3412 + SUPPORTS SNMP-MPD-MIB + INCLUDES { + snmpMPDGroup + } + + -- ********************* ************ ************ *************** *** + -- 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. + ESX virtual switches support changing administrative state + of physical network interfaces (nics) up or down. For example the command: + esxcli network nic [up|down] -n vmnic0 + Virtual vmware interfaces (ifType 238) also support changing administratie state: + network ip interface set --enabled [yes|no] -i vmk0 + " + + 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 SNMPv2/3 Contexts for multiple instances + 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, + udpHCGroup + } + + -- ********************* ************ ************ *************** *** + -- 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, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active ESX Shell sessions" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + 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. pnic 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 200810150000Z + SUPPORTS IEEE8021-BRIDGE-MIB + INCLUDES { + ieee8021BridgeBaseBridgeGroup, + ieee8021BridgeBasePortGroup, + ieee8021BridgeTpPortGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200810150000Z + -- virtual switch uplinks (physical ports) do perform do mac learning and will + -- not report in FDB/forwarding tables + SUPPORTS IEEE8021-Q-BRIDGE-MIB + INCLUDES { + ieee8021QBridgeBaseGroup, + ieee8021QBridgeVlanGroup, + ieee8021QBridgeVlanStaticGroup, + ieee8021QBridgePortGroup2, + ieee8021QBridgeFdbUnicastGroup, + ieee8021QBridgeFdbMulticastGroup, + ieee8021QBridgeFdbStaticGroup, + ieee8021QBridgeVlanStatisticsGroup + } + -- VARATION ieee8021QBridgeVlanCurrentUntaggedPorts + -- Reports count of 0 if only untagged vlan access (vid 0) is defined + + -- ********************* ************ ************ *************** *** + -- REVISION 200706200000Z + -- VDS link aggregations are not reported this release, issue PR 859941 + -- only VSS, traditional vswitch, nic teams are reported entries + SUPPORTS IEEE8023-LAG-MIB + INCLUDES { + dot3adAggGroup, + dot3adAggPortGroup, + dot3adTablesLastChangedGroup, + dot3adAggPortListGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200906080000Z + SUPPORTS LLDP-V2-MIB + INCLUDES { + lldpV2ConfigGroup, + lldpV2ConfigTxGroup, + lldpV2StatsTxGroup, + lldpV2LocSysGroup, + lldpV2ConfigRxGroup, + lldpV2StatsRxGroup, + lldpV2RemSysGroup, + lldpV2NotificationsGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201005120000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvAlertGroup, + vmwESXEnvNotificationGroup2 + } + + -- REVISION 201008200000Z + SUPPORTS VMWARE-CIMOM-MIB + INCLUDES { + vmwCimOmNotificationGroup + } + + ::= { vmwEsxCapability 10 } + +-- +-- ESX 5.5 and follow up patch releases +-- + +vmwESX55 AGENT-CAPABILITIES + PRODUCT-RELEASE + "5.5.x" + STATUS current + DESCRIPTION + "Release 5.5 for VMware ESXi supports SNMPv1, SNMPv2c, and SNMPv3 with a stand-alone snmpd process. + + This release features support for monitoring multiple IP Stacks. The standard IP-MIB, UDP-MIB, and TCP-MIB + may be used with a context set to the IP Stack Name as found in ENTITY-MIB entLogicalTable + or via command: esxcli network ip netstack list + An example using net-snmp's snmpwalk command:: snmpwalk -v2c -n defaultTcpipStack ip + + No vDR instrumentation is yet available. + + This agent supports read-only protocol operations. This implies that configuring the SNMPv3 Agent + can not be done via SET operations. Hence IETF standard SNMPv3 agent configuration mibs are not provided. + The SNMPv3 protocol is fully supported once configured via the CLI command interface (esxcli system snmp) + command set or vCenter Server host profiles. 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above clause implies this: + -- VARIATION authenticationFailure + -- ACCESS not-implemented + -- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled." + + -- ********************* ************ ************ *************** *** + -- RFC 3412 + SUPPORTS SNMP-MPD-MIB + INCLUDES { + snmpMPDGroup + } + + -- ********************* ************ ************ *************** *** + -- 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. + ESX virtual switches support changing administrative state + of physical network interfaces (nics) up or down. For example the command: + esxcli network nic [up|down] -n vmnic0 + Virtual vmware interfaces (ifType 238) also support changing administratie state: + network ip interface set --enabled [yes|no] -i vmk0 + " + + 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 SNMPv2/3 Contexts for multiple instances + 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, + udpHCGroup + } + + -- ********************* ************ ************ *************** *** + -- 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, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active ESX Shell sessions" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + 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. pnic 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 200810150000Z + SUPPORTS IEEE8021-BRIDGE-MIB + INCLUDES { + ieee8021BridgeBaseBridgeGroup, + ieee8021BridgeBasePortGroup, + ieee8021BridgeTpPortGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200810150000Z + -- virtual switch uplinks (physical ports) do perform do mac learning and will + -- not report in FDB/forwarding tables + SUPPORTS IEEE8021-Q-BRIDGE-MIB + INCLUDES { + ieee8021QBridgeBaseGroup, + ieee8021QBridgeVlanGroup, + ieee8021QBridgeVlanStaticGroup, + ieee8021QBridgePortGroup2, + ieee8021QBridgeFdbUnicastGroup, + ieee8021QBridgeFdbMulticastGroup, + ieee8021QBridgeFdbStaticGroup, + ieee8021QBridgeVlanStatisticsGroup + } + -- VARATION ieee8021QBridgeVlanCurrentUntaggedPorts + -- Reports count of 0 if only untagged vlan access (vid 0) is defined + + -- ********************* ************ ************ *************** *** + -- REVISION 200706200000Z + -- VDS link aggregations are not reported this release, issue PR 859941 + -- only VSS, traditional vswitch, nic teams are reported entries + SUPPORTS IEEE8023-LAG-MIB + INCLUDES { + dot3adAggGroup, + dot3adAggPortGroup, + dot3adTablesLastChangedGroup, + dot3adAggPortListGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200906080000Z + SUPPORTS LLDP-V2-MIB + INCLUDES { + lldpV2ConfigGroup, + lldpV2ConfigTxGroup, + lldpV2StatsTxGroup, + lldpV2LocSysGroup, + lldpV2ConfigRxGroup, + lldpV2StatsRxGroup, + lldpV2RemSysGroup, + lldpV2NotificationsGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201005120000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvAlertGroup, + vmwESXEnvNotificationGroup2 + } + + -- REVISION 201008200000Z + SUPPORTS VMWARE-CIMOM-MIB + INCLUDES { + vmwCimOmNotificationGroup + } + + ::= { vmwEsxCapability 5 } + +-- +-- ESX 5.1 and follow up patch releases +-- + +vmwESX51x AGENT-CAPABILITIES + PRODUCT-RELEASE + "5.1.x" + STATUS current + DESCRIPTION + "Release 5.1.x for VMware ESXi supports SNMPv1, SNMPv2c, and SNMPv3 with a stand-alone snmpd process. + This agent supports read-only protocol operations. This implies that configuring the SNMPv3 Agent + can not be done via SET operations. Hence IETF standard SNMPv3 agent configuration mibs are not provided. + SNMPv3 protocol is fully supported once configured via the CLI command interface (esxcli system snmp) + command set or host profiles. 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above clause implies this: + -- 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. + ESX virtual switches support changing administrative state + of physical network interfaces (nics) up or down. For example the command: + esxcli network nic [up|down] -n vmnic0 + Virtual vmware interfaces (ifType 238) also support changing administratie state: + network ip interface set --enabled [yes|no] -i vmk0 + " + + 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 IP-FORWARD-MIB + INCLUDES { + inetForwardCidrRouteGroup + } + + -- ********************* ************ ************ *************** *** + -- RFC 4113 + 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, + udpHCGroup + } + + -- ********************* ************ ************ *************** *** + -- RFC 4022 + 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, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active ESX Shell sessions" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + 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. pnic 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 200810150000Z + SUPPORTS IEEE8021-BRIDGE-MIB + INCLUDES { + ieee8021BridgeBaseBridgeGroup, + ieee8021BridgeBasePortGroup, + ieee8021BridgeTpPortGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200810150000Z + -- virtual switch uplinks (physical ports) do perform do mac learning and will + -- not report in FDB/forwarding tables + SUPPORTS IEEE8021-Q-BRIDGE-MIB + INCLUDES { + ieee8021QBridgeBaseGroup, + ieee8021QBridgeVlanGroup, + ieee8021QBridgeVlanStaticGroup, + ieee8021QBridgePortGroup2, + ieee8021QBridgeFdbUnicastGroup, + ieee8021QBridgeFdbMulticastGroup, + ieee8021QBridgeFdbStaticGroup, + ieee8021QBridgeVlanStatisticsGroup + } + -- VARATION ieee8021QBridgeVlanCurrentUntaggedPorts + -- Reports count of 0 if only untagged vlan access (vid 0) is defined + + -- ********************* ************ ************ *************** *** + -- REVISION 200706200000Z + -- VDS link aggregations are not reported this release, issue PR 859941 + -- only VSS, traditional vswitch, nic teams are reported entries + SUPPORTS IEEE8023-LAG-MIB + INCLUDES { + dot3adAggGroup, + dot3adAggPortGroup, + dot3adTablesLastChangedGroup, + dot3adAggPortListGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 200906080000Z + SUPPORTS LLDP-V2-MIB + INCLUDES { + lldpV2ConfigGroup, + lldpV2ConfigTxGroup, + lldpV2StatsTxGroup, + lldpV2LocSysGroup, + lldpV2ConfigRxGroup, + lldpV2StatsRxGroup, + lldpV2RemSysGroup, + lldpV2NotificationsGroup + } + + -- ********************* ************ ************ *************** *** + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201005120000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvAlertGroup, + vmwESXEnvNotificationGroup2 + } + + -- REVISION 201008200000Z + SUPPORTS VMWARE-CIMOM-MIB + INCLUDES { + vmwCimOmNotificationGroup + } + + ::= { vmwEsxCapability 4 } + + +vmwESX50x AGENT-CAPABILITIES + PRODUCT-RELEASE + "5.0.x" + STATUS current + DESCRIPTION + "Release 5.0.x for VMware ESXi. The SNMPv1/v2c agent is a subsystem in the hostd process" + 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above implies this: + -- 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. + Note: ESX virtual switches now may support changing administrative state + of physical network interfaces (nics) up or down." + + 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 2790 + SUPPORTS HOST-RESOURCES-MIB + INCLUDES { + hrSystemGroup, + hrStorageGroup, -- visorfs "ramdisks" are not reported + hrDeviceGroup, + hrSWRunGroup, + hrSWRunPerfGroup, + hrSWInstalledGroup -- updates once an hour + } + + VARIATION hrSystemNumUsers + ACCESS read-only + DESCRIPTION "Value reports number of active login sessions in host agent (hostd)" + + VARIATION hrSWRunName + ACCESS read-only + DESCRIPTION "Value does not match hrSWInstalledName" + + VARIATION hrDeviceErrors + ACCESS not-implemented + DESCRIPTION "ESXi pcpu, network interface cards, do not provide error stats" + + -- hrDeviceStatus reports unknown for: cpu. pnic 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" + + 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" + + -- ********************* ************ ************ *************** *** + + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 201006220000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 201005120000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvNotificationGroup + } + + ::= { vmwEsxCapability 3 } + + +-- +-- +-- + +vmwESX41x AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.1.x" + STATUS current + DESCRIPTION + "Release 4.1.x for VMware ESX, the SNMP agent is now a subsystem in the hostd process on ESXi." + 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above implies this: + -- 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 interface. + ESX virtual layer 2 switches may support changing administrative state + of physical network interfaces (nics)." + + 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." + + -- ********************* ************ ************ *************** *** + + -- REVISION 200712270000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 200810230000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 200712270000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvNotificationGroup + } + + ::= { vmwEsxCapability 2 } + +-- +-- +-- + +vmwESX40x AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.0.x" + STATUS current + DESCRIPTION + "Release 4.0.x for VMware ESX. The SNMP agent is now part of the hostd process" + 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 allow authentication traps. Poll snmpInBadCommunityNames for same info." + -- the above implies this: + -- 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 + SYNTAX INTEGER { up(1) } + ACCESS read-only + DESCRIPTION "Agent provides read-only view of system information and + does not support changing operational state." + + VARIATION ifLinkUpDownTrapEnable + ACCESS read-only + DESCRIPTION "Agent provides read-only view of system information." + + -- ifXTable not implemented + VARIATION ifTableLastChange + ACCESS not-implemented + DESCRIPTION "post RFC 1213 managed objects not implemented." + + VARIATION ifConnectorPresent + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + VARIATION ifHighSpeed + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + VARIATION ifName + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + VARIATION ifAlias + ACCESS not-implemented + DESCRIPTION "ifXTable not implemented." + + -- ifFixedLengthGroup + VARIATION ifAlias + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifHCFixedLengthGroup + VARIATION ifHCInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifPacketGroup + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifMtu + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifPromiscuousMode + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + + -- ifHCPacketGroup + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifMtu + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifPromiscuousMode + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifVHCPacketGroup + VARIATION ifHCInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifHCOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutOctets + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUnknownProtos + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutErrors + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifMtu + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifInDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutUcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutMulticastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutBroadcastPkts + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifOutDiscards + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + VARIATION ifPromiscuousMode + ACCESS not-implemented + DESCRIPTION "Performance counters not implemented." + + -- ifCounterDiscontinuityGroup + VARIATION ifCounterDiscontinuityTime + ACCESS not-implemented + DESCRIPTION "Required if Performance counters are implemented." + + -- 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." + + + -- ********************* ************ ************ *************** *** + + -- REVISION 200712270000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- REVISION 200810150000Z + SUPPORTS VMWARE-RESOURCES-MIB + INCLUDES { + vmwResourceGroup + } + -- REVISION 200810230000Z + SUPPORTS VMWARE-VMINFO-MIB + INCLUDES { + vmwVmInfoGroup, + vmwVmInfoNotificationGroup + } + -- VARIATION vmwVmNetConnType + -- DESCRIPTION "This object was valid for ESX 2.5 systems only. Only value returned was 'monitor_dev'" + -- STATUS deprecated + + -- REVISION 200712270000Z + SUPPORTS VMWARE-ENV-MIB + INCLUDES { + vmwEnvNotificationGroup + } + + ::= { vmwEsxCapability 1 } + +END + diff --git a/MIBS/vmware/VMWARE-HEARTBEAT-MIB b/MIBS/vmware/VMWARE-HEARTBEAT-MIB new file mode 100644 index 0000000..be35dac --- /dev/null +++ b/MIBS/vmware/VMWARE-HEARTBEAT-MIB @@ -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 + diff --git a/MIBS/vmware/VMWARE-HZECC-AGENTCAP-MIB b/MIBS/vmware/VMWARE-HZECC-AGENTCAP-MIB new file mode 100644 index 0000000..6961eae --- /dev/null +++ b/MIBS/vmware/VMWARE-HZECC-AGENTCAP-MIB @@ -0,0 +1,57 @@ +-- ********************************************************** +-- Copyright 2021 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-HZECC-AGENTCAP-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + vmwareAgentCapabilities + FROM VMWARE-ROOT-MIB + AGENT-CAPABILITIES + FROM SNMPv2-CONF; + +vmwHzeccAgentCapabilityMIB MODULE-IDENTITY + LAST-UPDATED "202105170000Z" + 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 + Horizon Cloud Connector (Hze CC) agents by release. + Releases of Horizon Cloud Connector (Hze CC) + prior to 2.0 are not supported." + + REVISION "202105170000Z" + DESCRIPTION + "Notifications sent by Hze CC as updated in 2.0 release" + ::= { vmwareAgentCapabilities 140 } + +vmwHzeccCapability OBJECT IDENTIFIER ::= { vmwHzeccAgentCapabilityMIB 1 } + +vmwHZECCAgent2021v200 AGENT-CAPABILITIES + PRODUCT-RELEASE + "2.0.0" + STATUS current + DESCRIPTION + "Release 2.1.0.0 for VMware Horizon Cloud Connector supporting + only SNMPv3 trap PDUs. It describes all the notifications + sent from the Hzee CC appliance. + " + REFERENCE + "http://www.vmware.com/products" + -- REVISION 202105170000Z First Version. + SUPPORTS VMWARE-HZECC-EVENT-MIB + INCLUDES { + vmwHzeccNotificationGroup + } + ::= { vmwHzeccCapability 4 } + +END diff --git a/MIBS/vmware/VMWARE-HZECC-EVENT-MIB b/MIBS/vmware/VMWARE-HZECC-EVENT-MIB new file mode 100644 index 0000000..1b58749 --- /dev/null +++ b/MIBS/vmware/VMWARE-HZECC-EVENT-MIB @@ -0,0 +1,227 @@ +-- ********************************************************** +-- Copyright 2021 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-HZECC-EVENT-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + TEXTUAL-CONVENTION + FROM SNMPv2-TC + SnmpAdminString + FROM SNMP-FRAMEWORK-MIB + vmwHzecc + FROM VMWARE-ROOT-MIB; + + vmwHzeccMIB MODULE-IDENTITY + LAST-UPDATED "202105170000Z" + 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: https://kb.vmware.com/s/article/1013445 + " + DESCRIPTION + "This MIB file contains the definition of the SNMP + interface of VMware Horizon Cloud Connector. + + Horizon Cloud Connector is an important product which + enables subscription license for Horizon on-prem VDI & APPs: + https://www.vmware.com/in/products/horizon.html + https://www.vmware.com/in/products/horizon-cloud-virtual-desktops.html + + For more information about Horizon Cloud Connector (Hze CC), please see + the latest documentation of Horizon Cloud Connector: + https://docs.vmware.com/en/VMware-Horizon-Cloud-Service + " + + REVISION "202105170000Z" + DESCRIPTION + "Initial revision" + + ::= { vmwHzecc 1 } + +vmwHzeccNotifications OBJECT IDENTIFIER ::= { vmwHzecc 0 } +vmwHzeccLifecycleEvents OBJECT IDENTIFIER ::= { vmwHzecc 4 } +vmwHzeccSubscriptionLicenseEvents OBJECT IDENTIFIER ::= { vmwHzecc 5 } + +VmwHzeccLifecycleEventType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "The lifecycle event type. + This trap is sent when a life cycle event occurs. + Except the failure events all other events are informational only + The value of the same is defined with codes. + + paired - 1 - Indicates that Cloud Connector is being configured + or reconfigured by an admin by providing Horizon enterprise pod details. + This is an information only event. + For more information refer - + https://docs.vmware.com/en/VMware-Horizon-Cloud-Service/services/hzncloudmsazure.getstarted15/GUID-CFC5C50E-FBA2-4F9B-89EB-56A090D4C158.html + ---------------------------------------------------------------- + unplug - 2 - Indicates that an admin is deleting + the Cloud Connector pod and related configuration. This is an + information only event. + ---------------------------------------------------------------- + Upgrade Events - Cloud Connector Upgrade is based on Blue Green approach. + Blue appliance is the existing appliance. + Green appliance is the target upgraded version appliance + https://docs.vmware.com/en/VMware-Horizon-Cloud-Service/services/hzncloudmsazure.admin15/GUID-D3F6C0CB-5740-4CA4-9C20-D780F415E900.html + ---------------------------------------------------------------- + bluepreupgrade - 10 - Indicates that upgrade + is about to start. This indicates an admin is initiating + manual or scheduled upgrade of cloud connector appliance. + This is an information only event. + ---------------------------------------------------------------- + bluepostupgradesuccess - 20 - Indicates that upgrade + has successfully completed. This is an information only event. + ---------------------------------------------------------------- + bluepostupgradefailure - 21 - Indicates that upgrade + has failed. Upgrade can be restarted back. An Admin who + initiates upgrade would need to restart the upgrade. + This is an information only event. + ---------------------------------------------------------------- + greenpostupgradesuccess - 30 - Indicates that upgrade + has successfully completed. This is an information only event. + ---------------------------------------------------------------- + greenpostupgradefailure - 31 - Indicates that upgrade + has failed during configuration migration step. + Upgrade can be restarted back by an Admin. + This is an information only event. + ---------------------------------------------------------------- + " + SYNTAX INTEGER { + paired(1), + unplug(2), + bluepreupgrade(10), + bluepostupgradesuccess(20), + bluepostupgradefailure(21), + greenpostupgradesuccess(30), + greenpostupgradefailure(31) + } + +-- +-- Object Types +-- + +vmwHzeccLCEventName OBJECT-TYPE + SYNTAX VmwHzeccLifecycleEventType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The life cycle event generated." + ::= { vmwHzeccLifecycleEvents 1 } + + +vmwHzeccSubscriptionLicenseFailStatus OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Subscription license sync status. + This trap is sent when a subscription license sync fails. + Subscription license is synced at minimum every 24 hours + from Horizon Cloud Control Plane to Horizon on-prem. + + This trap indicates that the license sync failed due to the + mentioned error code. If you received this event for + more than one day in a row, please navigate to + Horizon Admin Console and check for connectivity. + You can then refer the KB http://kb.vmware.com/s/article/79509 + for more information on error codes. + + Possible values - LicenseFailed_400, LicenseFailed_401. + The number part is the API response code from horizon enterprise. + + In case issue doesn't resolve after following troubleshooting + steps mentioned in KB article, please reach to VMware support. + " + ::= { vmwHzeccSubscriptionLicenseEvents 1 } + +-- +-- Notifications Objects +-- + +vmwHzeccLifecycleEventTrap NOTIFICATION-TYPE + OBJECTS { + vmwHzeccLCEventName + } + STATUS current + DESCRIPTION + "This trap is sent when a life cycle event occurs. + This is an informational event only. There is no action to take upon receipt. + Frequency: + This event is sent once when (some part of your system) receives a configuration update. + The value of the same is defined with codes. + " + ::= { vmwHzeccNotifications 1 } + +vmwHzeccSubscriptionLicenseEventTrap NOTIFICATION-TYPE + OBJECTS { + vmwHzeccSubscriptionLicenseFailStatus + } + STATUS current + DESCRIPTION + "This trap is sent when a subscription license sync fails. + Subscription license is synced at every 24 hours + from Horizon Cloud Control Plane to Horizon on-prem. + + This trap indicates that the license sync failed due to the + mentioned error code. If you received this event for + more than one day in a row, please navigate to + Horizon Admin Console and check for connectivity. + You can then refer the KB http://kb.vmware.com/s/article/79509 + for more information on error codes. + + Frequency: This event is sent when the license sync fails. + After that once every 24 hrs until the issue is resolved + + Possible values - LicenseFailed_400, LicenseFailed_401, LicenseFailed_500 etc. + The number part is the API response code from horizon enterprise. + + In case issue doesn't resolve after following troubleshooting + steps mentioned in KB article, please reach to VMware support. + " + ::= { vmwHzeccNotifications 2 } + +-- conformance information + +vmwHzeccMIBConformance OBJECT IDENTIFIER ::= { vmwHzeccMIB 1 } +vmwHzeccMIBCompliances OBJECT IDENTIFIER ::= { vmwHzeccMIBConformance 1 } +vmwHzeccMIBGroups OBJECT IDENTIFIER ::= { vmwHzeccMIBConformance 2 } + +vmwHzeccMIBBasicCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement VMWARE-HZECC-EVENT-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwHzeccNotificationGroup, vmwHzeccObjectGroup } + ::= { vmwHzeccMIBCompliances 1 } + +vmwHzeccObjectGroup OBJECT-GROUP + OBJECTS { + vmwHzeccLCEventName, + vmwHzeccSubscriptionLicenseFailStatus + } + STATUS current + DESCRIPTION + "These objects provide notification details." + ::= { vmwHzeccMIBGroups 1 } + +vmwHzeccNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwHzeccLifecycleEventTrap, + vmwHzeccSubscriptionLicenseEventTrap + } + STATUS current + DESCRIPTION + "Group of objects describing notifications." + ::= { vmwHzeccMIBGroups 2 } + +END diff --git a/MIBS/vmware/VMWARE-NSX-AGENTCAP-MIB b/MIBS/vmware/VMWARE-NSX-AGENTCAP-MIB new file mode 100644 index 0000000..6cf1f93 --- /dev/null +++ b/MIBS/vmware/VMWARE-NSX-AGENTCAP-MIB @@ -0,0 +1,780 @@ +-- ********************************************************** +-- Copyright 2020-2022 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-NSX-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 "202202140000Z" + 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 agents by release." + REVISION "202201240000Z" + DESCRIPTION + "NSX-T Data Center 3.2.0 release. Supports both notifications and polling over v1/v2c/v3" + REVISION "202108060000Z" + DESCRIPTION + "NSX-T Data Center 3.1.3 release. Supports both notifications and polling over v1/v2c/v3" + REVISION "202104220000Z" + DESCRIPTION + "NSX-T Data Center 3.1.2 release. Supports both notifications and polling over v1/v2c/v3" + REVISION "202103250000Z" + DESCRIPTION + "NSX-T Data Center 3.0.3 release. Supports both notifications and polling over v1/v2c/v3" + REVISION "202010300000Z" + DESCRIPTION + "NSX-T Data Center 3.1.x releases. Supports both notifications and polling over v1/v2c/v3" + REVISION "202009220000Z" + DESCRIPTION + "NSX-T Data Center 3.0.2 release. Supports both notifications and polling over v1/v2c/v3" + REVISION "202003270000Z" + DESCRIPTION + "NSX-T Data Center 3.0.0 and 3.0.1 releases. Supports both notifications and polling over v1/v2c/v3" + ::= { vmwareAgentCapabilities 26 } + +vmwNSXCapability OBJECT IDENTIFIER ::= { vmwNSXAgentCapabilityMIB 1 } + +-- +-- Applies to NSX-T Data Center 3.0 Release and follow up patch releases +-- + +vmwNSXManagerDC30 AGENT-CAPABILITIES + PRODUCT-RELEASE + "VMware NSX-T Data Center 3.0" + STATUS current + DESCRIPTION + "Release 3.0 VMware NSX-T Data Center 3.0. + Notifications may be v1, v2c, or v3 noAuthNoPriv to authPriv securityLevel with SHA1/AES128" + REFERENCE "http://www.vmware.com/products" + + -- NSX Specific Notifications + SUPPORTS VMWARE-NSX-MIB + INCLUDES { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup6, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup6 + } + + -- RFC 3418 sysObjectId in VMWARE-PRODUCTS-MIB node: vmwNSX + 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" + + VARIATION hrSWInstalledTable + ACCESS not-implemented + DESCRIPTION "is not implemented" + + -- ********************* ************ ************ *************** *** + -- RFC 4133 + -- SMBIOS data provided in entPhysicalTable + SUPPORTS ENTITY-MIB + INCLUDES { + entityPhysicalGroup, + entityPhysical2Group, + entityPhysical3Group, + entityGeneralGroup + } + -- VARIATION entityNotificationsGroup + -- ACCESS not-implemented + -- VARIATION entityMappingGroup + -- ACCESS not-implemented + + -- ********************* ************ ************ *************** *** + -- Enterprise MIB module to provide standardized product version information. + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- VARIATION vmwProdUpdate + -- ACCESS not-implemented + -- VARIATION vmwProdPatch + -- ACCESS not-implemented + + ::= { vmwNSXCapability 11 } + +-- +-- Applies to NSX-T Data Center 3.1 Release and follow up patch releases +-- + +vmwNSXManagerDC30 AGENT-CAPABILITIES + PRODUCT-RELEASE + "VMware NSX-T Data Center 3.1" + STATUS current + DESCRIPTION + "Release 3.1 VMware NSX-T Data Center 3.1. + Notifications may be v1, v2c, or v3 noAuthNoPriv to authPriv securityLevel with SHA1/AES128" + REFERENCE "http://www.vmware.com/products" + + -- NSX Specific Notifications + SUPPORTS VMWARE-NSX-MIB + INCLUDES { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationInfoGroup6, + vmwNsxTDataCenterNotificationInfoGroup7, + vmwNsxTDataCenterNotificationInfoGroup8, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4, + vmwNsxTDataCenterNotificationGroup5, + vmwNsxTDataCenterNotificationGroup6, + vmwNsxTDataCenterNotificationGroup7, + vmwNsxTDataCenterNotificationGroup8 + } + + -- RFC 3418 sysObjectId in VMWARE-PRODUCTS-MIB node: vmwNSX + 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" + + VARIATION hrSWInstalledTable + ACCESS not-implemented + DESCRIPTION "is not implemented" + + -- ********************* ************ ************ *************** *** + -- RFC 4133 + -- SMBIOS data provided in entPhysicalTable + SUPPORTS ENTITY-MIB + INCLUDES { + entityPhysicalGroup, + entityPhysical2Group, + entityPhysical3Group, + entityGeneralGroup + } + -- VARIATION entityNotificationsGroup + -- ACCESS not-implemented + -- VARIATION entityMappingGroup + -- ACCESS not-implemented + + -- ********************* ************ ************ *************** *** + -- Enterprise MIB module to provide standardized product version information. + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- VARIATION vmwProdUpdate + -- ACCESS not-implemented + -- VARIATION vmwProdPatch + -- ACCESS not-implemented + + ::= { vmwNSXCapability 13 } + +-- +-- Applies to NSX-T Data Center 3.2 Release and follow up patch releases +-- + +vmwNSXManagerDC30 AGENT-CAPABILITIES + PRODUCT-RELEASE + "VMware NSX-T Data Center 3.2" + STATUS current + DESCRIPTION + "Release 3.2 VMware NSX-T Data Center 3.2. + Notifications may be v1, v2c, or v3 noAuthNoPriv to authPriv securityLevel with SHA1/AES128" + REFERENCE "http://www.vmware.com/products" + + -- NSX Specific Notifications + SUPPORTS VMWARE-NSX-MIB + INCLUDES { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationInfoGroup6, + vmwNsxTDataCenterNotificationInfoGroup7, + vmwNsxTDataCenterNotificationInfoGroup8, + vmwNsxTDataCenterNotificationInfoGroup9, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4, + vmwNsxTDataCenterNotificationGroup5, + vmwNsxTDataCenterNotificationGroup6, + vmwNsxTDataCenterNotificationGroup7, + vmwNsxTDataCenterNotificationGroup8, + vmwNsxTDataCenterNotificationGroup9 + } + + -- RFC 3418 sysObjectId in VMWARE-PRODUCTS-MIB node: vmwNSX + 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" + + VARIATION hrSWInstalledTable + ACCESS not-implemented + DESCRIPTION "is not implemented" + + -- ********************* ************ ************ *************** *** + -- RFC 4133 + -- SMBIOS data provided in entPhysicalTable + SUPPORTS ENTITY-MIB + INCLUDES { + entityPhysicalGroup, + entityPhysical2Group, + entityPhysical3Group, + entityGeneralGroup + } + -- VARIATION entityNotificationsGroup + -- ACCESS not-implemented + -- VARIATION entityMappingGroup + -- ACCESS not-implemented + + -- ********************* ************ ************ *************** *** + -- Enterprise MIB module to provide standardized product version information. + -- REVISION 201008020000Z + SUPPORTS VMWARE-SYSTEM-MIB + INCLUDES { + vmwSystemGroup + } + -- VARIATION vmwProdUpdate + -- ACCESS not-implemented + -- VARIATION vmwProdPatch + -- ACCESS not-implemented + + ::= { vmwNSXCapability 15 } + +END diff --git a/MIBS/vmware/VMWARE-NSX-MANAGER-AGENTCAP-MIB b/MIBS/vmware/VMWARE-NSX-MANAGER-AGENTCAP-MIB new file mode 100644 index 0000000..db81756 --- /dev/null +++ b/MIBS/vmware/VMWARE-NSX-MANAGER-AGENTCAP-MIB @@ -0,0 +1,263 @@ +-- ********************************************************** +-- Copyright 2016-2020 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 "202006030000Z" + 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 "202006030000Z" + DESCRIPTION + "Capabilities for NSX Manager 6.4.x releases." + 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 } + +vmwNSXManager2020x647 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.4.7" + STATUS current + DESCRIPTION + "Release 6.4.7 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, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7, + vmwNsxManagerNotificationGroup8, + vmwNsxManagerNotificationGroup9, + vmwNsxManagerNotificationGroup10 + } + ::= { vmwNSXMCapability 14 } + +vmwNSXManager2019x646 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.4.6" + STATUS current + DESCRIPTION + "Release 6.4.6 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, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7, + vmwNsxManagerNotificationGroup8, + vmwNsxManagerNotificationGroup9 + } + ::= { vmwNSXMCapability 13 } + +vmwNSXManager2019x645 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.4.5" + STATUS current + DESCRIPTION + "Release 6.4.5 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, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7, + vmwNsxManagerNotificationGroup8 + } + ::= { vmwNSXMCapability 12 } + +vmwNSXManager2018x642 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.4.2" + STATUS current + DESCRIPTION + "Release 6.4.2 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, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7 + } + ::= { vmwNSXMCapability 11 } + +vmwNSXManager2018x637 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.3.7" + STATUS current + DESCRIPTION + "Release 6.3.7 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, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup4, + vmwNsxManagerNotificationGroup6 + } + ::= { vmwNSXMCapability 10 } + +-- +-- Applies to 2018 Release and follow up patch releases +-- + +vmwNSXManager2018x641 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.4.1" + STATUS current + DESCRIPTION + "Release 6.4.1 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, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5 + } + ::= { vmwNSXMCapability 9 } + +-- +-- Applies to 2018 Release and follow up patch releases +-- + +vmwNSXManager2018x636 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.3.6" + STATUS current + DESCRIPTION + "Release 6.3.6 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, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup4 + } + ::= { vmwNSXMCapability 8 } + +-- +-- Applies to 2017 Release and follow up patch releases +-- + +vmwNSXManager2017x640 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.4.0" + STATUS current + DESCRIPTION + "Release 6.4.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, + vmwNsxManagerNotificationGroup3 + } + ::= { vmwNSXMCapability 7 } + + +vmwNSXManager2017x630 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 + diff --git a/MIBS/vmware/VMWARE-NSX-MANAGER-MIB b/MIBS/vmware/VMWARE-NSX-MANAGER-MIB new file mode 100644 index 0000000..b58685e --- /dev/null +++ b/MIBS/vmware/VMWARE-NSX-MANAGER-MIB @@ -0,0 +1,7099 @@ +-- ********************************************************** +-- Copyright 2016-2020 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-NSX-MANAGER-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32 + FROM SNMPv2-SMI + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + TEXTUAL-CONVENTION, DateAndTime + FROM SNMPv2-TC + UUID + FROM UUID-TC-MIB + vmwNsxManager + FROM VMWARE-ROOT-MIB; + + vmwNsxManagerMIB MODULE-IDENTITY + LAST-UPDATED "202006030001Z" + 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 MIB file contains the information that the receiving party needs + in order to interpret SNMP traps sent by NSX Manager. + + VMware NSX for vSphere is a key product in the SDDC architecture. With + NSX, virtualization delivers for networking what it has already delivered + for compute and storage. In much the same way that server virtualization + programmatically creates, snapshots, deletes and restores software-based + virtual machines (VMs), NSX network virtualization programmatically + creates, snapshots, deletes, and restores software-based virtual + networks. The result is a completely transformative approach to + networking that not only enables data center managers to achieve orders + of magnitude better agility and economics, but also allows for a vastly + simplified operational model for the underlying physical network. With + the ability to be deployed on any IP network, including both existing + traditional networking models and next-generation fabric architectures + from any vendor, NSX is a completely non-disruptive solution. In fact, + with NSX, the physical network infrastructure you already have is all you + need to deploy a software-defined data center. + + The NSX Manager provides the graphical user interface (GUI) and the REST + APIs for creating, configuring, and monitoring NSX components, such as + controllers, logical switches, and edge services gateways. The NSX + Manager provides an aggregated system view and is the centralized network + management component of NSX. NSX Manager is installed as a virtual + appliance on any ESX host in your vCenter environment. + + Support requests can be filed with VMware using KB article: + http://kb.vmware.com/kb/2006985 + + To reach NSX Manager Service Composer UI, login to + vSphere UI(https://<vsphere-ip>)->Networking & Security->Service + Composer" + REVISION "202006030001Z" + DESCRIPTION + "Addition of traps for releases 6.4.7" + REVISION "201907090001Z" + DESCRIPTION + "Addition of traps for releases 6.4.6" + REVISION "201902120001Z" + DESCRIPTION + "Addition of traps for releases 6.4.5" + REVISION "201805310001Z" + DESCRIPTION + "Addition of traps for releases 6.4.2" + REVISION "201804250001Z" + DESCRIPTION + "Addition of traps for releases 6.3.7" + REVISION "201803080000Z" + DESCRIPTION + "Addition of traps for releases 6.3.6 and 6.4.1." + REVISION "201712080000Z" + DESCRIPTION + "Addition of one new trap for capacity dashbard events." + REVISION "201711220000Z" + DESCRIPTION + "Addition of one new varbinds : vmwNsxMVxlanHostEvents. + Represents the security events received from host to NSX Manager." + REVISION "201711010000Z" + DESCRIPTION + "See VMWARE-NSX-MANAGER-AGENTCAP-MIB.mib for Versions of NSX manager which support this MIB version. + This file describes all the notifications sent from the NSX Manager appliance. Includes + Addition of three new varbinds: vmwNsxMEventSourceID, vmwNsxMEventSourceType and + vmwNsxMEventSourceIP + to vmwNsxMMessagingConfigFailed, vmwNsxMMessagingConfigFailed, vmwNsxMMessagingReconfigFailed, + vmwNsxMMessagingConfigFailedNotifSkip, vmwNsxMMessagingInfraUp, vmwNsxMMessagingInfraDown, + vmwNsxMMessagingDisabled, vmwNsxMVxlanControllerDisconnected, vmwNsxMVxlanControllerConnected, + vmwNsxMVxlanControllerVmPoweredOn. + Represents the Controller VM connected or disconnected, and Controller + VM Powered On respectively. + WARNING: This mib module will not be backward compatible with next version." + + REVISION "201707050000Z" + DESCRIPTION + "Addition of two new varbinds : vmwNsxMVxlanPortgroupDeleted, vmwNsxMVxlanVDSandPgMismatch. + Represents the Vxlan Port Group Deleted and DVS, Vxlan PG Mismatch respectively." + REVISION "201707030000Z" + DESCRIPTION + "Addition of traps for capacity dashboard events." + REVISION "201706010000Z" + DESCRIPTION + "Addition of three new varbinds : vmwNsxMEventSourceID, vmwNsxMEventSourceType and vmwNsxMEventSourceIP. + Represents the event source's ID, Type and IP address respectively." + REVISION "201704270000Z" + DESCRIPTION + "This is the 6.3.0 version of the NSX Manager MIB. + It describes all the notifications sent from the NSX Manager appliance. + Added new traps to indicate Application Rule Manager related events + See https://pubs.vmware.com/NSX-62/index.jsp?topic=%2Fcom.vmware.nsx.admin.doc%2FGUID-8BC71FF1-9A94-4CBD-BA95-551B0B2266FA.html" + REVISION "201606020000Z" + DESCRIPTION + "Release 6.2.3 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." + + ::= { vmwNsxManager 1 } + +-- +-- Data type definitions +-- +VmwNsxManagerTypeSeverity ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Severity enumeration definition of NSX Manager events" + SYNTAX INTEGER { informational(1), low(2), medium(3), major(4), + critical(5), high(6) } + +VmwNsxManagerSourceID ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The event sources' IDs for the NSX Manager system event. This data type can be used to + specify multiple event source IDs seperated by a semicolon. In NSX Manager, we can have + multiple event sources and hence multiple event source IDs." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxManagerSourceType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The event sources' types for the NSX Manager system event. This data type can be used to + specify multiple event source types seperated by a semicolon. In NSX Manager, we can have + multiple event sources and hence multiple event source types." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxManagerSourceIPAddress ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The IP address(es) of the source(s) of the NSX Manager event. This data type can be used to + specify multiple IP addresses seperated by a semicolon. Using InetAddress and InetAddressType + from INET-ADDRESS-MIB would have been relevant in case there was a single event source. + In NSX Manager, we can have multiple event sources and hence multiple IP addresses." + SYNTAX OCTET STRING (SIZE (0..256)) + +-- +-- Top-level MIB groups +-- + +-- Group 1: Generic data sent in All Alerts + +vmwNsxMAlertData OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This members of this group are the OIDs for VarBinds + that contain data for ALL Alerts." + ::= { vmwNsxManagerMIB 1 } + +-- Group 2: Alerts sent as notifications + +vmwNsxMNotification OBJECT-IDENTITY + STATUS current + DESCRIPTION + "All notifications for NSX Manager use this oid prefix." + ::= { vmwNsxManagerMIB 2 } + +vmwNsxMEventCode OBJECT-TYPE + SYNTAX Integer32 (1..2147483647) + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The event code of the alert that was generated. To fetch a list of all the + events with their code, severity and description please invoke the + nsx-manager url https://<nsx-manager-host>/api/2.0/systemevent/eventcode . + The event code specifically identifies each individual event type. This + event code is uniquely assigned only once to a particular event type." + ::= { vmwNsxMAlertData 1 } + +vmwNsxMEventTimestamp OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The timestamp when the event was raised in the NSX Manager." + ::= { vmwNsxMAlertData 2 } + +vmwNsxMEventMessage OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This object provides a human readable description of the event or group + of events" + ::= { vmwNsxMAlertData 3 } + +vmwNsxMEventSeverity OBJECT-TYPE + SYNTAX VmwNsxManagerTypeSeverity + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The severity for the event that was generated. The severity is + pre-defined and can only be changed from the NSX Manager section + of vsphere web client if the administrator so wishes." + ::= { vmwNsxMAlertData 4 } + +vmwNsxMEventComponent OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The NSX manager component where this event was generated." + ::= { vmwNsxMAlertData 5 } + +vmwNsxMUuid OBJECT-TYPE + SYNTAX UUID + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The NSX manager UUID where this event was generated." + ::= { vmwNsxMAlertData 6 } + +vmwNsxMCount OBJECT-TYPE + SYNTAX Integer32 (1..2147483647) + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The count of the number of events for a particular group raised in the + last 5 minute interval." + ::= { vmwNsxMAlertData 7 } + +vmwNsxMEventSourceID OBJECT-TYPE + SYNTAX VmwNsxManagerSourceID + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The object ID(s) of the source(s) of the event." + ::= { vmwNsxMAlertData 8 } + +vmwNsxMEventSourceType OBJECT-TYPE + SYNTAX VmwNsxManagerSourceType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The object type(s) of the source(s) of the event." + ::= { vmwNsxMAlertData 9 } + +vmwNsxMEventSourceIP OBJECT-TYPE + SYNTAX VmwNsxManagerSourceIPAddress + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The IP address(es) of the source(s) of the event." + ::= { vmwNsxMAlertData 10 } + +-- +-- Groups related traps +-- + +vmwNsxMBranch OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Branch segregated out for various groups and other future requirements." + ::= { vmwNsxMNotification 0 } + +vmwNsxMGroupsBranch OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Grouped Notifications will have this OID prefix." + ::= { vmwNsxMBranch 1 } + +vmwNsxMGroupsPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Prefix added to place zero in penultimate sub-identifier of group oids." + ::= { vmwNsxMGroupsBranch 0 } + +vmwNsxMConfigGroup NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventTimestamp, + vmwNsxMCount, + vmwNsxMEventMessage, + vmwNsxMUuid + } + STATUS current + DESCRIPTION + "Configuration notifications that are grouped will have this OID prefix." + ::= { vmwNsxMGroupsPrefix 1 } + +-- +-- Snmp related traps +-- + +vmwNsxMSnmp OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Snmp related will have this OID prefix." + ::= { vmwNsxMNotification 1 } + +vmwNsxMSnmpPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Snmp module." + ::= { vmwNsxMSnmp 0 } + +vmwNsxMSnmpDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "This notification is sent when the sending out of Snmp traps is disabled. + This would most likely be the last Snmp trap the snmp manager receives. + You may some times not receive it in case of high volume of traps. In those + cases you can rely on the heartbeat traps not being sent out. + Action required: None. If the sending of Snmp traps is enabled a warmStart + trap is received. + Frequency of traps: Once, whenever the sending snmp traps is disabled." + ::= { vmwNsxMSnmpPrefix 1 } + +vmwNsxMSnmpManagerConfigUpdated NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "This notification is sent when the snmp manager configuration has been + updated. The event message will carry the semicolon separated new snmp + managers' details. + Action required: None + Frequency of traps: Once, whenever the Snmp manager configuration is updated." + ::= { vmwNsxMSnmpPrefix 2 } + +-- +-- Security related traps +-- + +vmwNsxMSecurity OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are security related will have this OID prefix." + ::= { vmwNsxMNotification 2 } + +vmwNsxMSecurityPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for security module." + ::= { vmwNsxMSecurity 0 } + +vmwNsxMIpAddedBlackList NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever user authentication fails for number of times that + user is blacklisted and further login attempts are disabled for that user + from given IP address for some time. + Action required: None + Frequency of traps: Whenever user authentication fails consecutively within + some time." + ::= { vmwNsxMSecurityPrefix 1 } + +vmwNsxMIpRemovedBlackList NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "After user is blacklisted, after blacklist duration expires, + user is removed from blacklist. + Action required: None + Frequency of traps: Whenever blacklist duration expires for any user." + ::= { vmwNsxMSecurityPrefix 2 } + +vmwNsxMSsoConfigFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever configuration of lookup service / SSO fails due to + various reasons like invalid credentials, invalid configuration, time sync + problem etc. + Action required: Check the event message and reconfigure lookup service + with correct details. + Frequency of traps: Once per failed configuration of lookup service." + ::= { vmwNsxMSecurityPrefix 3 } + +vmwNsxMSsoUnconfigured NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever user unconfigures lookup service. + Action required: None + Frequency of traps: Once per unconfiguration event of lookup service." + ::= { vmwNsxMSecurityPrefix 4 } + +vmwNsxMUserRoleAssigned NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "When role is assigned on NSX manager for vCenter user. + Action required: None + Frequency of traps: Once for each user who is assigned role." + ::= { vmwNsxMSecurityPrefix 5 } + +vmwNsxMUserRoleUnassigned NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "When role is unassigned on NSX manager for vCenter user. + Action: None + Frequency of traps: Once for each user where role is removed." + ::= { vmwNsxMSecurityPrefix 6 } + +vmwNsxMGroupRoleAssigned NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "When role is assigned on NSX manager for vCenter group. + Action required: None + Frequency of traps: Once for each group who is assigned role." + ::= { vmwNsxMSecurityPrefix 7 } + +vmwNsxMGroupRoleUnassigned NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "When role is unassigned on NSX manager for vCenter group. + Action required: None + Frequency of traps: Once for each group where role is removed." + ::= { vmwNsxMSecurityPrefix 8 } + +vmwNsxMVcLoginFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever Connection with vCenter starts failing due to + invalid credentials. + Action required: Reconfigure NSX Manager vCenter configuration with + correct credentials." + ::= { vmwNsxMSecurityPrefix 9 } + +vmwNsxMVcDisconnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever there is disconnectivity for default VCenter + Connection maintained by NSX. + Action required: Administrator needs to check the connectivity with vCenter + for network problems or any other reasons." + ::= { vmwNsxMSecurityPrefix 10 } + +vmwNsxMLostVcConnectivity NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever there is disconnectivity for default VCenter + Connection maintained by NSX. + Action required: Administrator needs to check the connectivity with + vCenter for network problems or any other reasons." + ::= { vmwNsxMSecurityPrefix 11 } + +vmwNsxMSsoDisconnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever there is disconnection with SSO lookup service. + Action required: Please check the configuration for possible disconnection + reasons like Invalid Credentials, Time sync issues, Network connectivity + problems etc. Navigate to Appliance management Web UI in browser + (https://<nsx-manager-host>/) traverse to Manage vCenter Registration tab + and verify the configuration for SSO Lookupservice. + Frequency of traps: Once per disconnect event, default frequency to check + SSO connection state is 1 hour." + ::= { vmwNsxMSecurityPrefix 12 } + +vmwNsxMSsoTimeout NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "When we try to configure VC on a system where SSO is already configured, + we fetch the token to login to the VC using SSO. If it times out during + that, this trap is raised. + Action required: Try reconnecting to the SSO server and if the service remains + unresponsive, try restarting the NSX management service from the NSX appliance + management UI. Contact the SSO administrator if the issue persists. + Frequency of traps: Whenever we try to configure VC on a system where + SSO is already configured." + ::= { vmwNsxMSecurityPrefix 13 } + +-- +-- Distributed Firewall related traps +-- + +vmwNsxMFirewall OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are firewall related will have this OID prefix." + ::= { vmwNsxMNotification 3 } + +vmwNsxMFirewallPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for firewall module." + ::= { vmwNsxMFirewall 0 } + +vmwNsxMFltrCnfgUpdateFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager failed to enforce DFW. VMs on this host may not be protected by the DFW. Contextual data provided with this event may indicate the cause of this failure. +This could happen if the VIB version mismatches on the NSX Manager and ESX host. This may happen during an upgrade. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 1 } + +vmwNsxMFltrCnfgNotAppliedToVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager failed to enforce DFW configuration on a vnic. This particular VM may not be protected by the DFW. Contextual data provided with this event may indicate the cause of this failure.This could happen if the VIB version mismatches on the NSX Manager and ESX host. This may happen during an upgrade. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 2 } + +vmwNsxMFltrCnfgAppliedToVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Successfully updated filter config. + Action required: None" + ::= { vmwNsxMFirewallPrefix 3 } + +vmwNsxMFltrCreatedForVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Filter created. DFW is enforced in the datapath for the + vnic. + Action required: None" + ::= { vmwNsxMFirewallPrefix 4 } + +vmwNsxMFltrDeletedForVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Filter deleted. DFW is removed from the vnic. + Action required: None" + ::= { vmwNsxMFirewallPrefix 5 } + +vmwNsxMFirewallConfigUpdateFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Firewall rule Configuration between the NSX Manager and the host is not in sync. Contextual data provided with this event may indicate the cause of this failure. Verify that the host in question was properly prepared by NSX Manager. Collect error logs (vsfwd.log) when the host received firewall config. Force sync firewall config using ForceSync API/UI. See kb.vmware.com/kb/2125437 . + +If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 6 } + +vmwNsxMFirewallRuleFailedVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to apply Distributed Firewall configuration. +Contextual data provided with this event may indicate the cause of this failure. +Collect error logs (vmkernel.log) when the firewall configuration was applied to the vnic. vsip kernel heaps may not have enough free memory. Check VSFWD logs . See kb.vmware.com/kb/2125437. + +If the issue persists, please collect the ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 7 } + +vmwNsxMFirewallRuleAppliedVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Applied firewall config. Key value will have context info + like generation number and also other debugging info. + Action required: None" + ::= { vmwNsxMFirewallPrefix 8 } + +vmwNsxMCntnrCnfgUpdateFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed receive, parse or update the container configuration. Contextual data provided with this event may indicate the cause of this failure. +Collect error logs (vmkernel.log) when firewall configuration was applied to the vnic. Verify that vsip kernel heaps have enough free memory. Check VSFWD logs. See kb.vmware.com/kb/2125437 . +If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 9 } + +vmwNsxMFlowMissed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Flow missed. +Contextual data provided with this event may indicate the cause of this failure. +Collect error logs (vmkernel.log) when firewall configuration was applied to the vnic. Verify that vsip kernel heaps have enough free memory and vsfwd memory consumption is within resource limits. Check VSFWD logs. See kb.vmware.com/kb/2125437. +If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 10 } + +vmwNsxMSpoofGuardCnfgUpdateFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to receive, parse or Update the spoofguard configuration. +Contextual data provided with this event may indicate the cause of this failure. +Verify that the host in question was properly prepared by NSX Manager. +Collect error logs (vmkernel.log) when the spoofguard configuration was applied to the host. For Sync the firewall configuration . See kb.vmware.com/kb/2125437." + ::= { vmwNsxMFirewallPrefix 11 } + +vmwNsxMSpoofGuardFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to apply spoofguard to the vnic. +Contextual data provided with this event may indicate the cause of this failure. +Verify that vsip kernel heaps have enough free memory. +Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 12 } + +vmwNsxMSpoofGuardApplied NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Enabled spoofguard for vnic. + Action required: None" + ::= { vmwNsxMFirewallPrefix 13 } + +vmwNsxMSpoofGuardDisableFail NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to disable spoofguard on the vnic. +Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 14 } + +vmwNsxMSpoofGuardDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Disabled spoofguard for vnic. + Action required: None" + ::= { vmwNsxMFirewallPrefix 15 } + +vmwNsxMLegacyAppServiceDeletionFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when legacy application service VM + deletion failed." + ::= { vmwNsxMFirewallPrefix 16 } + +vmwNsxMFirewallCpuThresholdCrossed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd CPU usage threshold was exceeded. +Reduce the amount of traffic of VMs on the host in question." + ::= { vmwNsxMFirewallPrefix 17 } + +vmwNsxMFirewallMemThresholdCrossed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd heap memory threshold exceeded for the specified heap. +Reduce the number of of VMs on the host in question, reduce the number of rules or containers in firewall config. Use appliedTo feature to limit the number of rules for the current cluster." + ::= { vmwNsxMFirewallPrefix 18 } + +vmwNsxMConnPerSecThrshldCrossed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd Connectons Per Second (CPS) threshold exceeded for the specified vnic. +Reduce the amount of new connections of VMs on the host in question." + ::= { vmwNsxMFirewallPrefix 19 } + +vmwNsxMFirewallCnfgUpdateTimedOut NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager waits for 2 minutes after publishing the Firewall configuration to each host in the cluster. If a host takes more than 2 minutes to process the data, it times out. +Please check the Host in question. See if VSFWD is functioning or not. Also use CLI commands to verify if the rule realization is working properly or not. See kb.vmware.com/kb/2125437. +Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 20 } + +vmwNsxMSpoofGuardCnfgUpdateTmOut NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager waits for 2 minutes after publishing the Spoofguard configuration to each host in the cluster. If a host takes more than 2 minutes to process the data, it times out. +Please check the Host in question. See if VSFWD is functioning or not. Also use CLI commands to verify if the rule realization is working properly or not. See kb.vmware.com/kb/2125437. +Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 21 } + +vmwNsxMFirewallPublishFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Firewall Configuration Publishing has failed for a given cluster/host. +Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 22 } + +vmwNsxMCntnrUpdatePublishFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Publishing of container (IP/MAC/vNIC) update pdate failed for a given host/cluster object. +Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 23 } + +vmwNsxMSpoofGuardUpdatePublishFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The publishing of the spoofguard updates on this host has failed. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 24 } + +vmwNsxMExcludeListPublishFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The publishing of the exclude list or updates to the exclude list on this host has failed. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 25 } + +vmwNsxMFirewallCnfgUpdateOnDltCntnr NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Deletion of the object referenced in firewall rules. + Action required: Go to the NSX manager DFW UI. All the invalid reference + are marked invalid on the UI as well. Please remove the orphaned referenced + and update the firewall rules." + ::= { vmwNsxMFirewallPrefix 26 } + +vmwNsxMHostSyncFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Host-level force synchronization has failed. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 27 } + +vmwNsxMHostSynced NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Force Sync operation for host succeeded. + Action required: None" + ::= { vmwNsxMFirewallPrefix 28 } + +vmwNsxMFirewallInstalled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The Distributed Firewall was successfully Installed on the host." + ::= { vmwNsxMFirewallPrefix 29 } + +vmwNsxMFirewallInstallFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The Distributed Firewall Installation has failed. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 30 } + +vmwNsxMFirewallClusterInstalled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The Distributed Firewall has been installed at the request of a user." + ::= { vmwNsxMFirewallPrefix 31 } + +vmwNsxMFirewallClusterUninstalled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The Distributed Firewall has been uninstalled at the request of a user." + ::= { vmwNsxMFirewallPrefix 32 } + +vmwNsxMFirewallClusterDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The Distributed Firewall has been disabeld on the cluster at the request of a user." + ::= { vmwNsxMFirewallPrefix 33 } + +vmwNsxMFirewallForceSyncClusterFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Force Sync operation for the cluster has failed. +Use CLI commands to look at the logs and verify if any error messages appeared during the operation. See kb.vmware.com/kb/2125437. +Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and +http://kb.vmware.com/kb/1010705" + ::= { vmwNsxMFirewallPrefix 34 } + +vmwNsxMFirewallForceSyncClusterSuccess NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Force Sync operation for cluster succeeded. + Action required: None" + ::= { vmwNsxMFirewallPrefix 35 } + +vmwNsxMFirewallVsfwdProcessStarted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd process started on host. + Action required: None" + ::= { vmwNsxMFirewallPrefix 36 } + +vmwNsxMFirewallRulesetApplyAllFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failure to apply all the rule section configuration. Contextual data provided with this event may indicate the cause of this failure. + Collect error logs (vmkernel.log) when firewall configuration was applied to the vnic. Verify that vsip kernel heaps have enough free memory. Check VSFWD logs. See kb.vmware.com/kb/2125437 . + If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 37 } + +vmwNsxMFirewallRulesetAppliedAll NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Successfully applied all rule section config. + Action required: None." + ::= { vmwNsxMFirewallPrefix 38 } + +vmwNsxMCntnrCnfgApplyFailedToVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failure to apply the container configuration. Contextual data provided with this event may indicate the cause of this failure. + Collect error logs (vmkernel.log) when firewall configuration was applied to the vnic. Verify that vsip kernel heaps have enough free memory. Check VSFWD logs. See kb.vmware.com/kb/2125437 . + If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 39 } + +vmwNsxMCntnrCnfgApplyAllFailedToVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failure to apply all container configuration. Contextual data provided with this event may indicate the cause of this failure. + Collect error logs (vmkernel.log) when firewall configuration was applied to the vnic. Verify that vsip kernel heaps have enough free memory. Check VSFWD logs. See kb.vmware.com/kb/2125437 . + If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 40 } + +vmwNsxMCntnrCnfgAppliedAllToVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Successfully applied all container config to all vnics. + Action required: None." + ::= { vmwNsxMFirewallPrefix 41 } + +vmwNsxMSpoofGuardApplyAllFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to apply all spoofguard to the vnics. + Contextual data provided with this event may indicate the cause of this failure. + Verify that vsip kernel heaps have enough free memory. + Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and + http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 42 } + +vmwNsxMSpoofGuardAppliedAll NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Applied all spoofguard for vnics. + Action required: None." + ::= { vmwNsxMFirewallPrefix 43 } + +vmwNsxMFirewallTimeoutUpdateFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Firewall session timer timeout configuration parse/update failed. Timeout values are unchanged. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vsfwd.log) when the host received firewall config. Force sync firewall config using ForceSync API/UI. See kb.vmware.com/kb/2125437 . + If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 44 } + +vmwNsxMFirewallTimeoutApplyFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Firewall session timer timeout configuration apply failed. Certain timeout values are unchanged. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vsfwd.log) when the host received firewall config. Force sync firewall config using ForceSync API/UI. See kb.vmware.com/kb/2125437 . + If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 45 } + +vmwNsxMFirewallTimeoutApplied NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Applied session timeout values for a vnic. + Action required: None." + ::= { vmwNsxMFirewallPrefix 46 } + +vmwNsxMFirewallTimeoutApplyAllFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to apply all firewall session timer timeout configuration. Some timeout values are unchanged. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vsfwd.log) when the host received firewall config. Force sync firewall config using ForceSync API/UI. See kb.vmware.com/kb/2125437 . + If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 47 } + +vmwNsxMFirewallTimeoutAppliedAll NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Applied session timeout values for all vnics. + Action required: None." + ::= { vmwNsxMFirewallPrefix 48 } + +vmwNsxMCntnrCnfgAppliedToVnic NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Successfully applied container config to all vnics. + Action required: None." + ::= { vmwNsxMFirewallPrefix 49 } + +vmwNsxMFirewallMaxConcurrentConnectionsThresholdCrossed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd maximum concurrent connections threshold was exceeded for the specified vnic. + Reduce the amount of traffic on the vnic in question." + ::= { vmwNsxMFirewallPrefix 50 } + +vmwNsxMFirewallProcessMemoryThresholdCrossed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd memory utilization threshold was exceeded for the specified process. + Reduce the number of rules or containers in firewall config. If persists, there may be memory leaks in the process so restarting it may be necessary." + ::= { vmwNsxMFirewallPrefix 51 } + +vmwNsxMFirewallCpuThresholdCrossCleared NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd CPU usage is back to below threshold level. + Action required: None." + ::= { vmwNsxMFirewallPrefix 52 } + +vmwNsxMFirewallMemThresholdCrossCleared NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd heap memory usage is back to below threshold level for the specified heap. + Action required: None." + ::= { vmwNsxMFirewallPrefix 53 } + +vmwNsxMConnPerSecThrshldCrossCleared NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd Connectons Per Second (CPS) is back to below threshold level for the specified vnic. + Action required: None." + ::= { vmwNsxMFirewallPrefix 54 } + +vmwNsxMFirewallMaxConcurrentConnectionsThresholdCrossCleared NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd maximum concurrent connections is back to below threshold level for the specified vnic. + Action required: None." + ::= { vmwNsxMFirewallPrefix 55 } + +vmwNsxMFirewallProcessMemoryThresholdCrossCleared NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "vsfwd memory utilization is back to below threshold level for the specified process. + Action required: None." + ::= { vmwNsxMFirewallPrefix 56 } + +vmwNsxMFirewallThresholdConfigApplied NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Successfully applied all threshold config. + Action required: None." + ::= { vmwNsxMFirewallPrefix 57 } + +vmwNsxMFirewallThresholdConfigApplyFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Firewall threshold configuration apply failed. Certain threshold values are unchanged. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vsfwd.log) when the host received firewall config. Force sync firewall config using ForceSync API/UI. See kb.vmware.com/kb/2125437 . + If the issue persists, please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.com/kb/2074678 and http://kb.vmware.com/kb/653." + ::= { vmwNsxMFirewallPrefix 58 } + +vmwNsxMUnsupportedIPsetConfigured NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Whenever an IP address 0.0.0.0 or 0.0.0.0/32 is configured as IPSet. + KB article: https://ikb.vmware.com/kb/53157 + Action: Information-only event. No action required. Workaround to this issue documented in KB article." + ::= { vmwNsxMFirewallPrefix 59 } + +-- +-- Edge related traps +-- + +vmwNsxMEdge OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are edge related will have this OID prefix." + ::= { vmwNsxMNotification 4 } + +vmwNsxMEdgePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for edge module." + ::= { vmwNsxMEdge 0 } + +vmwNsxMEdgeNoVmServing NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "None of the Edge VMs found in serving state. There is a + possibility of network disruption. + Action required: System auto recovers from this state today. Event should + be followed by traps with event code 30202 or 30203" + ::= { vmwNsxMEdgePrefix 1 } + +vmwNsxMEdgeGatewayCreated NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Edge Gateway created. + Action required: None" + ::= { vmwNsxMEdgePrefix 2 } + +vmwNsxMEdgeVmBadState NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Edge VM in bad state. Needs a force sync. + Action required: System auto triggres force sync but if problem is + sustained then manual force sync should be triggered. For ESG force + sync is disruptive and will reboot edge VMs." + ::= { vmwNsxMEdgePrefix 3 } + +vmwNsxMEdgeVmCommFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Failed to communicate with the Edge VM. + Action required: Need investigation depending upon comunication channel. + Log needs to be checked for VIX error code for futher action." + ::= { vmwNsxMEdgePrefix 4 } + +vmwNsxMEdgeVmCnfgChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when NSX Edge VM configuration is + changed. + Action required: None" + ::= { vmwNsxMEdgePrefix 5 } + +vmwNsxMEdgeGatewayDeleted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge Gateway is deleted. + Action required: None" + ::= { vmwNsxMEdgePrefix 6 } + +vmwNsxMEdgeGatewayReDeployed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge Gateway is redeployed. + Action required: None" + ::= { vmwNsxMEdgePrefix 7 } + +vmwNsxMEdgeVmPowerOff NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when NSX Edge VM is powered off. + Action required: None" + ::= { vmwNsxMEdgePrefix 8 } + +vmwNsxMEdgeApplianceSizeChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge appliance size has + changed. + Action required: None" + ::= { vmwNsxMEdgePrefix 9 } + +vmwNsxMEdgeUpgrade51x NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge Gateway is upgraded + to 5.1.x. + Action required: None" + ::= { vmwNsxMEdgePrefix 10 } + +vmwNsxMEdgeLicenseChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge licensing changed on + vCenter Server. + Action required: None" + ::= { vmwNsxMEdgePrefix 11 } + +vmwNsxMEdgeApplianceMoved NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge appliance is moved in the vCenter + inventory." + ::= { vmwNsxMEdgePrefix 12 } + +vmwNsxMEdgeApplianceNotFound NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge appliance not found in + the vCenter inventory. + Action required: If VM is accidentally deleted, redeploy edge." + ::= { vmwNsxMEdgePrefix 13 } + +vmwNsxMEdgeVMHealthCheckMiss NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM is not responding to + health check. + Action required: Communicaiton issues between manager and edge. Log + analysis required to root cause issue." + ::= { vmwNsxMEdgePrefix 14 } + +vmwNsxMEdgeHealthCheckMiss NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when none of the Edge VMs are found + in serving state. There is a possibility of network disruption. + Action required: Commnunicaiton issues between manager and edge. Log + analysis required to root cause issue." + ::= { vmwNsxMEdgePrefix 15 } + +vmwNsxMEdgeCommAgentNotConnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge Communication Agent is not + connected to vCenter Server. + Action required: Check VSM and VC connectivity. Try registering VSM to VC" + ::= { vmwNsxMEdgePrefix 16 } + +vmwNsxMApplianceWithDifferentId NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM is discovered with + a different vmId. + Action required: None" + ::= { vmwNsxMEdgePrefix 17 } + +vmwNsxMFirewallRuleModified NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge firewall rule is modified. + Action required: Revisit firewall rule and perform required updates" + ::= { vmwNsxMEdgePrefix 18 } + +vmwNsxMEdgeAntiAffinityRuleViolated NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when powering on NSX Edge appliance + violates a virtual machine anti-affinity rule. + Action required: Anti affinity rules removed from cluster. Both HA VM may + run on same host. Go to VC and please revisit anti affinity rules + on Cluster" + ::= { vmwNsxMEdgePrefix 19} + +vmwNsxMEdgeHaEnabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when NSX Edge HighAvailability is + enabled. + Action required: None" + ::= { vmwNsxMEdgePrefix 20 } + +vmwNsxMEdgeHaDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when NSX Edge HighAvailability + is disabled. + Action required: None" + ::= { vmwNsxMEdgePrefix 21 } + +vmwNsxMEdgeGatewayRecovered NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when NSX Edge Gateway has recovered + and now responding to health check. + Action required: None" + ::= { vmwNsxMEdgePrefix 22 } + +vmwNsxMEdgeVmRecovered NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when NSX Edge VM has recovered + and now responding to health check. + Actione required: None" + ::= { vmwNsxMEdgePrefix 23 } + +vmwNsxMEdgeGatewayUpgraded NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge Gateway is upgraded. + Action required: None" + ::= { vmwNsxMEdgePrefix 24 } + +vmwNsxMEdgeVmHlthChkDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM health check is + disabled on consecutive critical vix errors. Please redeploy or force + sync vm to resume health check. + Action required: This points to environmental issues that lead to + repeated failure over vix. Log analysis needs to be done to identify + root cause. Post resoving issues force sync edge vm to resume health + check. Force sync and redeploy are disruptive operation." + ::= { vmwNsxMEdgePrefix 25 } + +vmwNsxMEdgePrePublishFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Pre Publish has failed on Edge + VM. + Action required: Firewall rules might be out of sync. System auto recovers + but if problem persists then trigger force sync." + ::= { vmwNsxMEdgePrefix 26 } + +vmwNsxMEdgeForcedSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM was force synced. + Action required: None" + ::= { vmwNsxMEdgePrefix 27 } + +vmwNsxMEdgeVmBooted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM was booted. + Action required: None" + ::= { vmwNsxMEdgePrefix 28 } + +vmwNsxMEdgeVmInBadState NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM is in Bad State. Needs + a force sync. + Action required: Force sync required." + ::= { vmwNsxMEdgePrefix 29 } + +vmwNsxMEdgeVmCpuUsageIncreased NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM CPU usage has + increased. + Action required: Spikes are normal but collect tech support logs for + further analysis if high CPU sustained for longer duration." + ::= { vmwNsxMEdgePrefix 30 } + +vmwNsxMEdgeVmMemUsageIncreased NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM Memory usage has + increased. + Action required: System recovers but collect tech support logs for further + analysis." + ::= { vmwNsxMEdgePrefix 31 } + +vmwNsxMEdgeVmProcessFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM process monitor detects + a process failure. + Action required: System recovers but collect tech support logs for further + analysis." + ::= { vmwNsxMEdgePrefix 32 } + +vmwNsxMEdgeVmSysTimeBad NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM system time is bad. + Action required: System recovers. Check NTP setting on hosts." + ::= { vmwNsxMEdgePrefix 33 } + +vmwNsxMEdgeVmSysTimeSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM system time sync up happens. + Action required: None" + ::= { vmwNsxMEdgePrefix 34 } + +vmwNsxMEdgeAesniCryptoEngineUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when AESNI crypto engine is up. + Action required: None" + ::= { vmwNsxMEdgePrefix 35 } + +vmwNsxMEdgeAesniCryptoEngineDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when AESNI crypto engine is down. + Action required: None" + ::= { vmwNsxMEdgePrefix 36 } + +vmwNsxMEdgeVmOom NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge VM is out of memory. The + Edge is rebooting in 3 seconds. + Action required: Collect tech support for further analysis." + ::= { vmwNsxMEdgePrefix 37 } + +vmwNsxMEdgeFileSysRo NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge file system is read only. + Action required: Check datastore issues, once resolved force sync is + required." + ::= { vmwNsxMEdgePrefix 38 } + +vmwNsxMEdgeHaCommDisconnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge HighAvailability + communication channel is disconnected from peer node. + Action required: User will need to check network infrastructure + (virtual and physical) to look for any failures, specially on + the interfaces and the path configured for HA." + ::= { vmwNsxMEdgePrefix 39 } + +vmwNsxMEdgeHaSwitchOverSelf NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when High Availability is disabled for NSX Edge. + The primary NSX Edge VM has its state transitioned from ACTIVE to SELF. + High Availability (HA) ensures that NSX Edge services are always available, + by deploying an additional Edge VM for failover. The primary NSX Edge VM is + the ACTIVE node and the secondary VM is the STANDBY node. Whenever the + ACTIVE VM is unreachable on account of VM powered off or network + connectivity issues, the STANDBY VM takes over the ACTIVE vm's role. + In the event NSX Edge High Availability is disabled, the STANDBY VM is + deleted and the ACTIVE VM continues to function with its ACTIVE state + transitioned to SELF. + Action required: None" + ::= { vmwNsxMEdgePrefix 40 } + +vmwNsxMEdgeHaSwitchOverActive NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when High Availability switch over has happened + for NSX Edge. The secondary NSX Edge VM has its state transitioned from + STANDBY to ACTIVE. High Availability (HA) ensures that NSX Edge services + are always available, by deploying an additional Edge VM for failover. + The primary NSX Edge VM is the ACTIVE node and the secondary VM is the + STANDBY node. Whenever the ACTIVE VM is unreachable on account of VM + powered off or network connectivity issues, the STANDBY VM takes over the + ACTIVE vm's role. + Action required: None" + ::= { vmwNsxMEdgePrefix 41 } + +vmwNsxMEdgeHaSwitchOverStandby NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when High Availability switch over has happened + for NSX Edge. The primary NSX Edge VM has its state transitioned from + ACTIVE to STANDBY. High Availability (HA) ensures that NSX Edge services + are always available, by deploying an additional Edge VM for failover. + The primary NSX Edge VM is the ACTIVE node and the secondary VM is the + STANDBY node. Whenever the ACTIVE VM is unreachable on account of VM + powered off or network connectivity issues, the STANDBY VM takes over the + ACTIVE vm's role. When connectivity is re-established between the NSX Edge + VM's, one of the VM's state is transitioned from ACTIVE to STANDBY. + Action required: None" + ::= { vmwNsxMEdgePrefix 42 } + +vmwNsxMEdgeMonitorProcessFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge process monitor detected + a process failure. + Action required: Collect tech support logs for further analysis." + ::= { vmwNsxMEdgePrefix 43 } + +vmwNsxMLbVirtualServerPoolUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when LoadBalancer virtualServer/pool + is up. + Action required: None" + ::= { vmwNsxMEdgePrefix 44 } + +vmwNsxMLbVirtualServerPoolDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when LoadBalancer virtualServer/pool + is down." + ::= { vmwNsxMEdgePrefix 45 } + +vmwNsxMLbVirtualServerPoolWrong NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when LoadBalancer virtualServer/pool state is + wrong." + ::= { vmwNsxMEdgePrefix 46 } + +vmwNsxMLbPoolWarning NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when LoadBalancer pool changed to a warning + state." + ::= { vmwNsxMEdgePrefix 47 } + +vmwNsxMIpsecChannelUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when IPsec Channel is up. + Action required: None" + ::= { vmwNsxMEdgePrefix 48 } + +vmwNsxMIpsecChannelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when IPsec Channel is down. + Action required: Collect tech support logs for further analysis." + ::= { vmwNsxMEdgePrefix 49 } + +vmwNsxMIpsecTunnelUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when IPsec Tunnel is up. + Action required: None" + ::= { vmwNsxMEdgePrefix 50 } + +vmwNsxMIpsecTunnelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when IPsec Tunnel is down. + Action required: Collect tech support logs for further analysis." + ::= { vmwNsxMEdgePrefix 51 } + +vmwNsxMIpsecChannelUnknown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when IPsec Channel status is + unknown. + Action required: Collect tech support logs for further analysis." + ::= { vmwNsxMEdgePrefix 52 } + +vmwNsxMIpsecTunnelUnknown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when IPsec Tunnel status is unknown. + Action required: Collect tech support logs for further analysis." + ::= { vmwNsxMEdgePrefix 53 } + +vmwNsxMGlobalLbMemberUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Global Loadbalancer member + status is up. + Action required: None" + ::= { vmwNsxMEdgePrefix 54 } + +vmwNsxMGlobalLbMemberWarning NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Global Loadbalancer member + status is warning." + ::= { vmwNsxMEdgePrefix 55 } + +vmwNsxMGlobalLbMemberDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Global Loadbalancer member + status is down." + ::= { vmwNsxMEdgePrefix 56 } + +vmwNsxMGlobalLbMemberUnknown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Global Loadbalancer member + status is unknown." + ::= { vmwNsxMEdgePrefix 57 } + +vmwNsxMGlobalLbPeerUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Global Loadbalancer peer status + is up. + Action required: None" + ::= { vmwNsxMEdgePrefix 58 } + +vmwNsxMGlobalLbPeerDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Global Loadbalancer peer status + is down." + ::= { vmwNsxMEdgePrefix 59 } + +vmwNsxMDhcpServiceDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when DHCP Relay Service is + disabled." + ::= { vmwNsxMEdgePrefix 60 } + +vmwNsxMEdgeResourceReservationFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Insufficient CPU and/or Memory Resources available on Host or Resource + Pool, during resource reservation at the time of NSX Edge deployment. + Resources are explicitly reserved to ensure sufficient resources are + available for NSX Edge to service High Availability. User can view the + available resources vs reserved resources by navigating to the page + Home > Hosts and Clusters > [Cluster-name] > Monitor > Resource Reservation. + Action required: After checking available resources, re-specify the + resources as part of appliance configuration so that resource reservation + succeeds." + ::= { vmwNsxMEdgePrefix 61 } + +vmwNsxMEdgeSplitBrainDetected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Split Brain detected for NSX Edge with HighAvailability. + NSX Edge VM's configured for High Availability are unable to + determine if the other VM is alive due to network failure. In + such scenario, both the VM's think the other is not alive and + take on the ACTIVE state. This may cause network disruption. + Action required: User will need to check network infrastructure + (virtual and physical) to look for any failures, specially on + the interfaces and the path configured for HA." + ::= { vmwNsxMEdgePrefix 62 } + +vmwNsxMEdgeSplitBrainRecovered NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Resolved Split Brain for NSX Edge with HighAvailability. + The network path used by the NSX Edge VM's High Availability has been + re-established. NSX Edge VM's are able to communicate with each other, + and one of the VM has taken the STANDBY role, resolving the ACTIVE-ACTIVE + split brain scenario. + Action required: None" + ::= { vmwNsxMEdgePrefix 63 } + +vmwNsxMEdgeSplitBrainRecoveryAttempt NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Attempted Split Brain resolution for NSX Edge. + Split Brain recovery is being attempted on NSX Edge by NSX Manager. + Action required: None" + ::= { vmwNsxMEdgePrefix 64 } + +vmwNsxMEdgeResourceReservationSuccess NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "User specified or system managed CPU and/or Memory Resource reservation for + Edge VM is successful on Cluster or Resource + Pool, during deployment/redeployment of NSX Edge or Edge VM appliance + configuration. + Resources are explicitly reserved to ensure sufficient resources are + available for NSX Edge to service High Availability. User can view the + available resources vs reserved resources by navigating to the page + Home > Hosts and Clusters > [Cluster-name] > Monitor > Resource Reservation. + Action required: None" + ::= { vmwNsxMEdgePrefix 65 } + +vmwNsxMEdgeSddcChannelUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "VMCI communication channel to vmcd is up on specified NSX Edge. + Action required: None + Frequency: Once when the VMCI communication channel come up. + URL: Nil" + ::= { vmwNsxMEdgePrefix 66 } + +vmwNsxMEdgeSddcChannelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "VMCI communication channel to vmcd is down on specified NSX Edge. + Action required: Check status of vmcd daemon process. + Go to the ESX host and check vmcd status /etc/init.d/vmcd status + If not running, start vmcd /etc/init.d/vmcd start. + Frequency: Once when the VMCI communication channel goes down. + URL: Nil" + ::= { vmwNsxMEdgePrefix 67 } + + +vmwNsxMEdgeDuplicateIpDetected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "The NSX Edge IP has been assigned to another device on the network. MAC address of the conflicting device is provided. + Action required: Change the IP address of the other device on network. + Frequency: Once when the Edge detects the duplication of its IP by another macAddress in the same network. + URL: Nil" + ::= { vmwNsxMEdgePrefix 68 } + + +vmwNsxMEdgeDuplicateIpResolved NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "NSX Edge Duplicate IP address issue is resolved. + Action required: None + Frequency: Once when the Edge detects the duplication is resolved + URL: Nil" + ::= { vmwNsxMEdgePrefix 69 } + +vmwNsxMEdgeBgpNeighborUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when BGP neighbor is up. + BGP neighbor IP address in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: None" + ::= { vmwNsxMEdgePrefix 70 } + +vmwNsxMEdgeBgpNeighborDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when BGP neighbor is down. Once per neighbor. + BGP neighbor IP address in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: None" + ::= { vmwNsxMEdgePrefix 71 } + +vmwNsxMEdgeBgpNeighborASMismatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when there is a mismatch in AS number configured. Raised repeatedly when BGP neighbor is getting established. + BGP neighbor IP address in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: Correct the configured AS number" + ::= { vmwNsxMEdgePrefix 72 } + +vmwNsxMEdgeOSPFNeighborUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when OSPF neighbor is up. + OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: None" + ::= { vmwNsxMEdgePrefix 73 } + +vmwNsxMEdgeOSPFNeighborDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when OSPF neighbor is down. + OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: None" + ::= { vmwNsxMEdgePrefix 74 } + +vmwNsxMEdgeOSPFNeighborMTUMismatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when there is a MTU mismatch in neighbor ship request. + OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: Correct the MTU configured." + ::= { vmwNsxMEdgePrefix 75 } + +vmwNsxMEdgeOSPFNeighborAreaIdMisMatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when there is a areaId mismatch in neighbor ship request. + OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: Correct the areaId configured." + ::= { vmwNsxMEdgePrefix 76 } + +vmwNsxMEdgeOSPFNeighborHelloTimerMisMatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when there is hello timer mismatch in neighbor ship request. + OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: Correct the hello timer configured." + ::= { vmwNsxMEdgePrefix 77 } + +vmwNsxMEdgeOSPFNeighborDeadTimerMisMatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when there is dead timer mismatch in neighbor ship request. + OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. + Action required: Correct the dead timer configured." + ::= { vmwNsxMEdgePrefix 78 } + +vmwNsxMEdgeL2vpnTunnelUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when the l2vpn tunnel is up. + Action required: None" + ::= { vmwNsxMEdgePrefix 79 } + +vmwNsxMEdgeL2vpnTunnelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when the l2vpn tunnel is down. + We can debug why the l2vpn tunnel is down using the following cli commands, + show service l2vpn, + show configuration l2vpn, + show service l2vpn bridge + Action required: None." + ::= { vmwNsxMEdgePrefix 80 } + +vmwNsxMEdgeHAForceStandbyRemoved NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "A notification generated when forced standby for edge + enforced by NSX Manager gets removed. + Action required: None." + ::= { vmwNsxMEdgePrefix 81 } + +vmwNsxMEdgeHAForceStandbyRemovalFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when the force standby removal for edge failed. + Action required: None." + ::= { vmwNsxMEdgePrefix 82 } + + +vmwNsxMEdgeVmBADStateRecovered NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when edge VM is recovered from bad state. + Action required: None." + ::= { vmwNsxMEdgePrefix 83 } + +vmwNsxMEdgeVmBADStateAutoHealRecoveryDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "Raised when VM can not be recovered from bad state after system specified retry of auto recovery ForceSync operation. + Action required: Trigger force sync to recover edge VM from bad state. To trigger force sync from UI see + (https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.2/com.vmware.nsx.admin.doc/GUID-21FF2937-4CDF-491C-933E-8F44E21ED55E.html) + or call the API (POST https://<nsx-manager-host>/api/4.0/edges/<edge-id>?action=forcesync)" + ::= { vmwNsxMEdgePrefix 84 } + +vmwNsxMEdgeHaInUseVnicChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + + "A notification generated when internally allocated vnic + for HA internal communication is changed because vnic configurations + have changed. + Action required: None." + ::= { vmwNsxMEdgePrefix 85 } + +vmwNsxMEdgeHaCommConnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "A notification generated when Edge HighAvailability + communication channel is established with peer node. + Action required: None." + ::= { vmwNsxMEdgePrefix 86 } + +vmwNsxMEdgeVmRenameFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when Edge VM rename operation failed. + Given Edge name has invalid characters or exceeds + maximum number of characters permitted. There is + no functionality effect on the Edge. User may + choose a shorter name and rename the Edge. + Action required: None." + ::= { vmwNsxMEdgePrefix 87 } + +vmwNsxMEdgeBgpNeighborshipError NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when something goes wrong in neighborship establishment. + Error message will have error code and sub error code. BGP neighbor IP + address in the eventSourceId tells us for which neighbor this event is + getting raised. + vmwNsxMEventMessage for example will contain following details: + (Error when establishing BGP neighborship with neighbor 10.20.30.40 + having AS number 1201 with error code 6, error sub code 5.) + Action required: The error code given in message are standard error codes. + Act accordingly as per the error codes." + ::= { vmwNsxMEdgePrefix 88 } + +vmwNsxMEdgeVmBadStateNotRecovered NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when failed to recover NSX Edge VM from Bad State after force sync. + Action required: None." + ::= { vmwNsxMEdgePrefix 89 } + +vmwNsxMEdgeVmDcnOutOfSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when GroupingObject sync is timed out on NSX Edge VM. + Action required: None." + ::= { vmwNsxMEdgePrefix 90 } + +vmwNsxMEdgeConsumedResourcesMissingInInventory NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when missing or deleted resources from inventory are found used + in NSX Edges. + Action required: Please reconfigure these NSX Edges to use existing + resources. Refer to NSX Manager logs for the complete list of missing + resources." + ::= { vmwNsxMEdgePrefix 91 } + + +vmwNsxMEdgeIpsecDeprecatedComplianceSuiteInUse NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when a deprecated compliance suite is used in an IPSec site in + NSX Edges. + Action required: Please reconfigure IPSec site to use supported + compliance suite." + ::= { vmwNsxMEdgePrefix 92 } + +vmwNsxMEdgeConnectedToMultipleTZHavingSameClusters NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when a NSX Distributed Logical Router is connected to multiple + transport zones having same clusters. + Action required: None." + ::= { vmwNsxMEdgePrefix 93 } + +vmwNsxMEdgeConnectedToMultipleTZHavingDifferentClusters NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Raised when a NSX Distributed Logical Router is connected to multiple + transport zones having different clusters. This may cause network + disruption on clusters which are not common to all transport zones. + Action required: Please fix the configuration by either reconfiguring + transport zones to have same clusters or by connecting NSX Distributed + Logical Router to a single transport zone." + ::= { vmwNsxMEdgePrefix 94 } + +-- +-- Endpoint related traps +-- + +vmwNsxMEndpoint OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Endpoint related will have this OID prefix." + ::= { vmwNsxMNotification 5 } + +vmwNsxMEndpointPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Endpoint module." + ::= { vmwNsxMEndpoint 0 } + +vmwNsxMEndpointThinAgentEnabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when Thin agent is enabled." + ::= { vmwNsxMEndpointPrefix 1 } + +vmwNsxMGuestIntrspctnEnabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when Guest Introspection solution + is enabled." + ::= { vmwNsxMEndpointPrefix 2 } + +vmwNsxMGuestIntrspctnIncompatibleEsx NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when Guest Introspection solution + was contacted by an incompatible version of the ESX module." + ::= { vmwNsxMEndpointPrefix 3 } + +vmwNsxMGuestIntrspctnEsxConnFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when connection between the ESX + module and the Guest Introspection solution failed." + ::= { vmwNsxMEndpointPrefix 4 } + +vmwNsxMGuestIntrspctnStatusRcvFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when failed to receive status + from Guest Introspection solution." + ::= { vmwNsxMEndpointPrefix 5 } + +vmwNsxMEsxModuleEnabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when ESX module is enabled." + ::= { vmwNsxMEndpointPrefix 6 } + +vmwNsxMEsxModuleUninstalled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when ESX module is uninstalled." + ::= { vmwNsxMEndpointPrefix 7 } + +vmwNsxMGuestIntrspctnHstMxMssngRep NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when Guest Introspection host MUX + is missing report." + ::= { vmwNsxMEndpointPrefix 8 } + +vmwNsxMEndpointUndefined NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when Endpoint is undefined." + ::= { vmwNsxMEndpointPrefix 9 } + +-- +-- Eam related traps +-- + +vmwNsxMEam OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Eam related will have this OID prefix." + ::= { vmwNsxMNotification 6 } + +vmwNsxMEamPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Eam module." + ::= { vmwNsxMEam 0 } + +vmwNsxMEamGenericAlarm NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "EAM reports problems to NSX during vib/service VM + install/upgrade as these traps. + Action required: Use resolve API to resolve the Alarm. + Frequency of traps: N times per cluster per user action, where N is number + of hosts in a cluster." + ::= { vmwNsxMEamPrefix 1 } + +-- +-- Fabric related traps +-- + +vmwNsxMFabric OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Fabric related will have this OID prefix." + ::= { vmwNsxMNotification 7 } + +vmwNsxMFabricPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Fabric module." + ::= { vmwNsxMFabric 0 } + +vmwNsxMFabricDplymntStatusChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The status of a service on a cluster has changed. It can + change to RED(Failure), GREEN(Success), YELLOW(in-progress). + Action required: RED state would be accompanied with an + EAM Alarm/Event/Trap, that indicates root cause. Use resolver API to fix + it. + Frequency of traps: Once per state change. State could change 2-3 times + per user operation [Deploy/Undeploy/Update]" + ::= { vmwNsxMFabricPrefix 1 } + +vmwNsxMFabricDplymntUnitCreated NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager has created the required objects for deploying + a service on a cluster. This would be followed by deployment of the + service on all hosts in the cluster. + Action required: None + Frequency: Once per cluster" + ::= { vmwNsxMFabricPrefix 2 } + +vmwNsxMFabricDplymntUnitUpdated NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager has made changes in the objects required for + deploying a service on a cluster. This would be followed by updation of + the service on all hosts in the cluster. + Action required: None + Frequency of traps: Once per cluster per user operation [Update]" + ::= { vmwNsxMFabricPrefix 3 } + +vmwNsxMFabricDplymntUnitDestroyed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A service has been removed from all hosts in a cluster. NSX + Manager has deleted the objects for the service on the cluster. + Action required: None + Frequency of traps: Once per cluster" + ::= { vmwNsxMFabricPrefix 4 } + +vmwNsxMDataStoreNotCnfgrdOnHost NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Datastore could not be configured on host, probably its + not connected. + Action required: Ensure that datastore is connected to the host. Use + resolve API to resolve the Alarm. Service will be deployed. + Frequency of traps: Once per cluster per user operation [Deploy]." + ::= { vmwNsxMFabricPrefix 5 } + +vmwNsxMFabricDplymntInstallationFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Installation of service failed, please check if ovf/vib urls + are accessible, in correct format and all the properties in ovf environment + have been configured in service attributes. Please check logs for details. + Action required: Ensure that ovf/vib urls accessible from VC and are in + correct format. Use resolve API to resolve the Alarm. Service will + be deployed. + Frequency of traps: Once per cluster per user operation [Deploy]." + ::= { vmwNsxMFabricPrefix 6 } + +vmwNsxMFabricAgentCreated NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The service has been successfully installed on a host. + Action required: None + Frequency of traps: N times per cluster, where N is number of hosts in a + cluster." + ::= { vmwNsxMFabricPrefix 7 } + +vmwNsxMFabricAgentDestroyed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The service has been successfully removed from a host. + Action required: None + Frequency of traps: N times per cluster, where N is number of hosts in + a cluster." + ::= { vmwNsxMFabricPrefix 8 } + +vmwNsxMFabricSrvceNeedsRedplymnt NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service will need to be redeployed as the location of the + OVF / VIB bundles to be deployed has changed. + Action required: Use resolve API to resolve the Alarm. Service will be + redeployed. + Frequency of traps: N times per NSX Manager IP change, where N is number + of cluster and service combinations deployed." + ::= { vmwNsxMFabricPrefix 9 } + +vmwNsxMUpgradeOfDplymntFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Upgrade of deployment unit failed, please check if ovf/vib + urls are accessible, in correct format and all the properties in ovf + environment have been configured in service attributes. Please check + logs for details. + Action required: Ensure that ovf/vib urls accessible from VC and are in + correct format. Use resolve API to resolve the Alarm. Service will be + redeployed. + Frequency of traps: Once per cluster per user operation [Upgrade]" + ::= { vmwNsxMFabricPrefix 10 } + +vmwNsxMFabricDependenciesNotInstalled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The service being installed is dependent on another service + that has not yet been installed. + Action required: Deploy the required service on the cluster. + Frequency of traps: Once per cluster per user operation [Deploy]" + ::= { vmwNsxMFabricPrefix 11 } + +vmwNsxMFabricErrorNotifSecBfrUpgrade NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Error while notifying security solution before upgrade. The + solution may not be reachable/responding. + Action required: Ensure that solution urls are accessible from NSX. Use + resolve API to resolve the Alarm. Service will be redeployed. + Frequency of traps: Once per cluster per user operation [Upgrade]" + ::= { vmwNsxMFabricPrefix 12 } + +vmwNsxMFabricErrCallbackNtRcvdUpgrade NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Did not receive callback from security solution for upgrade + notification even after timeout. + Action required: Ensure that solution urls are accessible from NSX, and + NSX is reachable from the solution. Use resolve API to resolve the Alarm. + Service will be redeployed. + Frequency : Once per cluster per user operation [Upgrade]" + ::= { vmwNsxMFabricPrefix 13 } + +vmwNsxMFabricErrCallbackNtRcvdUninstall NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Uninstallation of service failed. + Action required: Ensure that solution urls are accessible from NSX, and + NSX is reachable from the solution. Use resolve API to resolve the Alarm. + Service will be removed. + Frequency of traps: Once per cluster per user operation [Uninstall]" + ::= { vmwNsxMFabricPrefix 14 } + +vmwNsxMFabricUninstallServiceFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Error while notifying security solution before uninstall. + Resolve to notify once again, or delete to uninstall without notification. + Action required: Ensure that solution urls are accessible from NSX, and + NSX is reachable from the solution. Use resolve API to resolve the Alarm. + Service will be removed. + Frequency of traps: Once per cluster per user operation [Uninstall]" + ::= { vmwNsxMFabricPrefix 15 } + +vmwNsxMFabricErrorNotifSecBfrUninstall NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Error while notifying security solution before uninstall. + Resolve to notify once again, or delete to uninstall without notification. + Action required: Ensure that solution urls are accessible from NSX, and + NSX is reachable from the solution. Use resolve API to resolve the Alarm. + Service will be removed. + Frequency of traps: Once per cluster per user operation [Uninstall]" + ::= { vmwNsxMFabricPrefix 16 } + +vmwNsxMFabricServerRebootUninstall NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Server rebooted while security solution notification for + uninstall was going on. + Action required: Ensure that solution urls are accessible from NSX. + Use resolve API to resolve the Alarm. Service will be uninstalled. + Frequency of traps: Once per cluster per user operation [Uninstall]" + ::= { vmwNsxMFabricPrefix 17 } + +vmwNsxMFabricServerRebootUpgrade NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Server rebooted while security solution notification for + upgrade was going on. + Action required: Ensure that solution urls are accessible from NSX. + Use resolve API to resolve the Alarm. Service will be redeployed. + Frequency of traps: Once per cluster per user operation [Upgrade]" + ::= { vmwNsxMFabricPrefix 18 } + +vmwNsxMFabricConnEamFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager relies on the ESX Agent Manager service in VC for + deploying/monitoring NSX vibs on ESX. The connection to this EAM service + has gone down. This could be due to EAM service or VC restart/stop or an + issue in the EAM service. + Action required: In the NSX UI, traverse to Manage, then NSX Management + Service. Verify that the status of VC connection on this page is Green. + Use the VC IP to verify that EAM is UP by visiting https://<vc ip>/eam/mob. + Frequency of traps: Once per switch from success to failed EAM connection" + ::= { vmwNsxMFabricPrefix 19 } + +vmwNsxMFabricConnEamRestored NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager relies on the EAM service in VC for + deploying/monitoring NSX vibs on ESX. The connection of NSX to this EAM + service was re-established successfully. + Action required: None + Frequency of traps: Once per switch from failed to success EAM connection" + ::= { vmwNsxMFabricPrefix 20 } + +vmwNsxMFabricPreUninstallCleanUpFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Pre Uninstall cleanup failed. + Action required: Use resolve API to resolve the Alarm. Service will be removed. + Frequency of traps: Once per cluster per user operation [Uninstall]" + ::= { vmwNsxMFabricPrefix 21 } + +vmwNsxMFabricBackingEamNotFound NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The backing EAM agency for this deployment could not be found. + It is possible that the VC services may still be initializing. Please try + to resolve the alarm to check existence of the agency. In case you have + deleted the agency manually, please delete the deployment entry from NSX. + Action required: Use resolve API to check existence of the agency, if + backing agency exists in EAM, else delete the deployment entry from NSX. + Frequency of traps: Once per cluster." + ::= { vmwNsxMFabricPrefix 22 } + +vmwNsxMFabricVibManualInstallationRequired NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "This trap is generated when an attempt is made to upgrade or uninstall + NSX vibs on stateless host using EAM. All stateless host should be + prepared using the auto deploy feature (Refer : https://kb.vmware.com/s/article/2005131). + Fix configuration using auto deploy feature and use the resolve API to resolve the alarm. + Action required: Use the resolve API to resolve the alarm. + Frequency of traps: Once per host." + ::= { vmwNsxMFabricPrefix 23 } + +vmwNsxMFabricUninstallDeploymentUnit NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Deployment unit fabric state is UNINSTALLED and health Status is SUCCEEDED. Resolve this alarm to complete uninstallation. + Frequency of traps: Once per cluster." + ::= { vmwNsxMFabricPrefix 24 } + +-- +-- DeploymentPlugin related traps +-- + +vmwNsxMDepPlugin OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are DeploymentPlugin related will have this OID + prefix." + ::= { vmwNsxMNotification 8 } + +vmwNsxMDepPluginPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for DeploymentPlugin module." + ::= { vmwNsxMDepPlugin 0 } + +vmwNsxMDepPluginIpPoolExhausted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "When deploying Guest Introspection or other VM based service + with static IP, NSX Manager needs to have a IP pool, for IP assignment to + the VM. This pool has been exhausted, and new service VMs cannot be + provisioned. + Action required: Traverse to the Networking & Security page on VMWare + vSphere Web Client, then go to Installation, followed by Service + Deployments. Note the IP pool name for the failed service. Now + traverse to NSX Managers, then go to Manage tab, followed by Grouping + Objects sub-tab. Click on IP Pools, and add more Ips to the static IP + pool. Use resolve API to resolve the Alarm. Service will be deployed. + Frequency of traps: N times per cluster, where N is number of hosts in + the cluster." + ::= { vmwNsxMDepPluginPrefix 1 } + +vmwNsxMDepPluginGenericAlarm NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Deployment plugin generic alarm. + Action required: Use resolve API to resolve the Alarm. Service will be + deployed. + Frequency of traps: N times per cluster, where N is number of hosts in + the cluster." + ::= { vmwNsxMDepPluginPrefix 2 } + +vmwNsxMDepPluginGenericException NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Deployment plugin generic exception alarm. + Action required: Use resolve API to resolve the Alarm. Service will be + deployed. + Frequency of traps: N times per cluster, where N is number of hosts in + the cluster." + ::= { vmwNsxMDepPluginPrefix 3 } + +vmwNsxMDepPluginVmReboot NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "VM needs to be rebooted for some changes to be + made/take effect. + Action required: Use resolve API to resolve the Alarm. + Frequency of traps: N times per cluster, where N is number of hosts in + the cluster." + ::= { vmwNsxMDepPluginPrefix 4 } + +-- +-- Messaging related traps +-- + +vmwNsxMMessaging OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Messaging related will have this OID prefix." + ::= { vmwNsxMNotification 9 } + +vmwNsxMMessagingPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Messaging module." + ::= { vmwNsxMMessaging 0 } + +vmwNsxMMessagingConfigFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when host messaging configuration + failed." + ::= { vmwNsxMMessagingPrefix 1 } + +vmwNsxMMessagingReconfigFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when host messaging connection + reconfiguration failed." + ::= { vmwNsxMMessagingPrefix 2 } + +vmwNsxMMessagingConfigFailedNotifSkip NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when host messaging configuration + failed and notifications were skipped." + ::= { vmwNsxMMessagingPrefix 3 } + +vmwNsxMMessagingInfraUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Manager runs a heartbeat with all hosts it manages. Missing + heartbeat responses from a host indicate a communication issue between + manager and the host. Such instances are indicated by event code 391002. + When the communication is restored after such an instance, it is indicated + by this event/trap. + Action required: Refer to KB article http://kb.vmware.com/kb/2133897 + Frequency of traps: Will be seen within 3 minutes of communication being + restored between manager and a host. + URL: http://kb.vmware.com/kb/2133897" + ::= { vmwNsxMMessagingPrefix 4 } + +vmwNsxMMessagingInfraDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Manager runs a heartbeat with all hosts it manages. Missing + heartbeat responses from a host indicate a communication issue between + manager and the host. In the case of such a communication issue, this trap + will be sent. + Action required: Refer to KB article http://kb.vmware.com/kb/2133897 + Frequency of traps: Will be seen within 6 minutes of a communication + failure between manager and a host. + URL: http://kb.vmware.com/kb/2133897" + ::= { vmwNsxMMessagingPrefix 5 } + +vmwNsxMMessagingDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A messaging client such as a Host, an Edge appliance or + a USVM appliance is expected to change its password within 2 hours of + being prepped or deployed. If the password isn't changed in this + duration, the messaging account for the client is disabled. + Action required: This event will indicate communication issue between + the manager and the client. Verify if the client is running. + If running, in case of a Host, re-sync messaging. In case of an Edge or + a USVM, redeploy. + Frequency of traps: Will be seen 2 hours after prep, host re-sync + or deployment of appliance. + URL: http://kb.vmware.com/kb/2133897" + ::= { vmwNsxMMessagingPrefix 6 } + +-- +-- ServiceComposer related traps +-- + +vmwNsxMServiceComposer OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are ServiceComposer related will have this OID prefix." + ::= { vmwNsxMNotification 10 } + +vmwNsxMServiceComposerPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for ServiceComposer module." + ::= { vmwNsxMServiceComposer 0 } + +vmwNsxMServiceComposerPolicyOutOfSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error while attempting to + enforce rules on this Policy. + Action required: Administrator needs to check the rules on the given Policy + for any errors, as reported in the message. After fixing the rules in the + Policy, user would need to resolve the alarm to bring this Policy back in + sync. Policy's alarm can either be resolved from NSX Manager Service Composer + UI or by using alarms API. + Frequency of traps: This trap is generated only once, if an error is + encountered while enforcing the Policy." + ::= { vmwNsxMServiceComposerPrefix 1 } + +vmwNsxMServiceComposerPolicyDeleted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A Policy got deleted as a result of the internal + SecurityGroup, over which the Policy was created, got deleted. + Frequency of traps: This event is generated once every time + any internal SecurityGroup, that is being consumed by a policy, + gets deleted." + ::= { vmwNsxMServiceComposerPrefix 2 } + +vmwNsxMServiceComposerFirewallPolicyOutOfSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error while attempting to + enforce Firewall rules on this Policy. Firewall related changes on this + Policy will not take effect, until this alarm is resolved. + Action required: Administrator needs to check the rules on the given Policy + for any errors, as reported in the message. After fixing the rules in the + Policy, user would need to resolve the alarm to bring this Policy back in + sync. Policy's alarm can either be resolved from NSX Manager Service Composer + UI or by using alarms API. + Frequency of traps: This trap is generated only once, if an error is + encountered while enforcing the Policy." + ::= { vmwNsxMServiceComposerPrefix 3 } + +vmwNsxMServiceComposerNetworkPolicyOutOfSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error while attempting to + enforce Network Introspection rules on this Policy. Network Introspection + related changes on this Policy will not take effect, until this alarm is + resolved. + Action required: Administrator needs to check the rules on the given Policy + for any errors, as reported in the message. After fixing the rules in the + Policy, user would need to resolve the alarm to bring this Policy back in + sync. Policy's alarm can either be resolved from NSX Manager Service Composer + UI or by using alarms API. + Frequency of traps: This trap is generated only once, if an error is + encountered while enforcing the Policy." + ::= { vmwNsxMServiceComposerPrefix 4 } + +vmwNsxMServiceComposerGuestPolicyOutOfSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error while attempting to + enforce Guest Introspection rules on this Policy. Guest Introspection + related changes on this Policy will not take effect, until this alarm + is resolved. + Action required: Administrator needs to check the rules on the given Policy + for any errors, as reported in the message. After fixing the rules in the + Policy, user would need to resolve the alarm to bring this Policy back in + sync. Policy's alarm can either be resolved from NSX Manager Service Composer + UI or by using alarms API. + Frequency of traps: This trap is generated only once, if an error is + encountered while enforcing the Policy." + ::= { vmwNsxMServiceComposerPrefix 5 } + +vmwNsxMServiceComposerOutOfSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error synchronizing Policies. Any changes on + Service Composer will not be pushed to Firewall/Network Introspection + Services, until this alarm is resolved. + Action required: Administrator needs to check Policies and/or Firewall + sections for any errors, as reported in the message. After fixing the errors, + user would need to resolve the alarm to bring Service Composer back in sync. + Alarm can either be resolved from NSX Manager Service Composer UI or by using + alarms API. + Frequency of traps: This trap is generated only once, whenever an error is + encountered." + ::= { vmwNsxMServiceComposerPrefix 6 } + + vmwNsxMServiceComposerOutOfSyncRebootFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error while synchronizing Policies on + reboot. + Action required: Administrator needs to check Policies and/or Firewall config + for any errors, as reported in the message. After fixing the errors, user + would need to resolve the alarm to bring Service Composer back in sync. Alarm + can either be resolved from NSX Manager Service Composer UI or by using + alarms API. + Frequency of traps: This trap is generated only once on NSX Manager reboot, + if an error is encountered." + ::= { vmwNsxMServiceComposerPrefix 7 } + +vmwNsxMServiceComposerOutOfSyncDraftRollback NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer went out of sync due to rollback of drafts from Firewall. + Any changes on Service Composer will not be pushed to Firewall/Network + Introspection Services, until this alarm is resolved. + Action required: Administrator needs to resolve the alarm to bring Service + Composer back in sync. Alarm can either be resolved from NSX Manager Service + Composer UI or by using alarms API. + Frequency of traps: This trap is generated only once, whenever Firewall + config is reverted to an older version of drafts." + ::= { vmwNsxMServiceComposerPrefix 8 } + +vmwNsxMServiceComposerOutOfSyncSectionDeletionFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error while deleting the section + corresponding to the Policy. This generally happens if third party(NetX) + service's Manager is not reachable. + Action required: Administrator needs to check connectivity with third + party(NetX) service's Manager. Once the connectivity is restored, user would + need to resolve the alarm. Alarm can either be resolved from Service Composer + UI or by using alarms API. + Frequency of traps: This trap is generated only once if a failure is + encountered while deleting a Policy's section on Policy deletion." + ::= { vmwNsxMServiceComposerPrefix 9 } + +vmwNsxMServiceComposerOutOfSyncPrecedenceChangeFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error reordering sections to reflect + Policy's precedence change. This generally happens if there are Alarms on any + other Policy. + Action required: Administrator needs to check Policies and/or Firewall + sections for any errors, as reported in the message. After fixing the errors, + user would need to resolve the alarm. Alarm can either be resolved from + NSX Manager Service Composer UI or by using alarms API. + Frequency of traps: This trap is generated only once if a failure is + encountered while reordering section to reflect precedence change." + ::= { vmwNsxMServiceComposerPrefix 10 } + +vmwNsxMServiceComposerOutOfSyncDraftSettingFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Composer encountered an error while initializing auto save drafts + setting. + Action required: Administrator needs to check Policies and/or Firewall + sections for any errors, as reported in the message. After fixing the errors, + user would need to resolve the alarm. Alarm can either be resolved from + NSX Manager Service Composer UI or by using alarms API. + Frequency of traps: This trap is generated only once if a failure is + encountered while initializing auto save drafts setting." + ::= { vmwNsxMServiceComposerPrefix 11 } + +-- +-- SvmOperations related traps +-- + +vmwNsxMSvmOperations OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are SvmOperations related will have this OID prefix." + ::= { vmwNsxMNotification 11 } + +vmwNsxMSvmOperationsPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for SvmOperations module." + ::= { vmwNsxMSvmOperations 0 } + +vmwNsxMInconsistentSvmAlarm NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service VMs are deployed per ESX host, to provide functionality like + guest introspection and McAfee/Trend virus checking in VMs on the host. + An issue is detected with the state of the deployed Service VM. Follow + instructions in http://kb.vmware.com/kb/2125482 to analyze the logs + further. Warning: Resolving this alarm will delete the VM. After + deletion you will see a different alarm saying VM is deleted. If you + resolve same, it will reinstall the VM. If redeployment of the VM does + not fix the original issue, the original alarm will be added back + immediately. + Action required: Use resolve API to resolve the Alarm. + Frequency of traps: Once per host." + ::= { vmwNsxMSvmOperationsPrefix 1 } + +vmwNsxMSvmRestartAlarm NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service VMs are deployed per ESX host, to provide functionality like + guest introspection and McAfee/Trend virus checking in VMs on the host. + An issue is detected with the state of the deployed Service VM. Follow + instructions in http://kb.vmware.com/kb/2125482 to analyze the logs + further. Warning: Resolving this alarm will restart the VM. If the + root cause here is not solved, the same alarm will be added back + immediately. + Action required: Use resolve API to resolve the Alarm. + Frequency of traps: Once per host." + ::= { vmwNsxMSvmOperationsPrefix 2 } + +vmwNsxMSvmAgentUnavailable NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "An issue is detected while marking agent as available. Kindly + check the logs. Resolving this alarm will attempt to mark the agent as + available. + Action required: Use resolve API to resolve the Alarm. + Frequency of traps: Once per host." + ::= { vmwNsxMSvmOperationsPrefix 3 } + +-- +-- Translation related traps +-- + +vmwNsxMTranslation OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Translation related will have this OID prefix." + ::= { vmwNsxMNotification 12 } + +vmwNsxMTranslationPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Translation module." + ::= { vmwNsxMTranslation 0 } + +vmwNsxMVmAddedToSg NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A VM has got added to the SecurityGroup. + Frequency of traps: Once for every VM getting added to any SecurityGroup." + ::= { vmwNsxMTranslationPrefix 1 } + +vmwNsxMVmRemovedFromSg NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A VM has got removed from the SecurityGroup. + Frequency of traps: Once for every VM getting removed from any + SecurityGroup." + ::= { vmwNsxMTranslationPrefix 2 } + +-- +-- UniversalSync related traps +-- + +vmwNsxMUniversalSync OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are UniversalSync related will have this OID prefix." + ::= { vmwNsxMNotification 13 } + +vmwNsxMUniversalSyncPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for UniversalSync module." + ::= { vmwNsxMUniversalSync 0 } + +vmwNsxMFullUniversalSyncFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A failure is encountered when doing full sync of universal + objects on a secondary NSX manager. IP address of the secondary NSX + manager is present in event's message variable. + Action required: Kindly check NSX manager logs on the secondary NSX + manager on which the full sync has failed. + Frequency of traps: This trap is generated once per NSX manager on which + full sync failure is seen." + ::= { vmwNsxMUniversalSyncPrefix 1 } + +vmwNsxMSecondaryDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Secondary NSX manager is unreachable. + Action required: Kindly check if NSX manager is running and is reachable + from primary NSX manager. IP address of the secondary NSX + manager is present in event's message variable. + Frequency of traps: This trap is generated once per NSX manager for which + connection issue is seen." + ::= { vmwNsxMUniversalSyncPrefix 2 } + +vmwNsxMUniversalSyncFailedForEntity NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A failure is encountered when doing sync of universal object + on a secondary NSX manager. IP address of the secondary NSX + manager is present in event's message variable. + Action required: Kindly check NSX manager logs on the secondary NSX manager + on which the sync has failed. + Frequency of traps: This trap is generated once per universal object on + a NSX manager on which sync failure is seen." + ::= { vmwNsxMUniversalSyncPrefix 3 } + +vmwNsxMUniversalSyncStoppedOnSecondary NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Secondary NSX manager is no longer receiving periodic universal sync updates. + IP address of the NSX manager is present in event's message variable. + Action required: Kindly check NSX manager logs and universal configuration on + the primary NSX manager to check if the secondary NSX manager has got removed. + Frequency of traps: This trap is generated one every 4 hours if secondary NSX + manager has not received universal sync updates for more than 4 hours." + ::= { vmwNsxMUniversalSyncPrefix 4 } + +vmwNsxMUniversalSyncResumedOnSecondary NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Secondary NSX manager has resumed receiving periodic universal sync updates. + Frequency of traps: This trap is generated whenever communication between + primary and secondary managers resumes." + ::= { vmwNsxMUniversalSyncPrefix 5 } +-- +-- AsyncRest related traps +-- + +vmwNsxMAsyncRest OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are AsyncRest related will have this OID prefix." + ::= { vmwNsxMNotification 14 } + +vmwNsxMAsyncRestPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for AsyncRest module." + ::= { vmwNsxMAsyncRest 0 } + +vmwNsxMServerUp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Denotes that NSX manager server is up and in running state, + Informs clients of NSX Manager of the current state. + Action required: None + Frequency of traps: Once for every query" + ::= { vmwNsxMAsyncRestPrefix 1 } + +-- +-- ExtensionRegistration related traps +-- + +vmwNsxMExtensionRegistration OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are ExtensionRegistration related will have this + OID prefix." + ::= { vmwNsxMNotification 15 } + +vmwNsxMExtensionRegistrationPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for ExtensionRegistration module." + ::= { vmwNsxMExtensionRegistration 0 } + +vmwNsxMExtensionRegistered NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Registers NSX manager as a vCenter extenstion. This is + applicable when no other NSX Manager is registered with vCenter and the + current NSX manager is the one registering with vCenter. + Action required: None + Frequency of traps: Only once when the extension is registered for the + very first time." + ::= { vmwNsxMExtensionRegistrationPrefix 1 } + +vmwNsxMExtensionUpdated NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Updates the vCenter extension registration with the new NSX + Manager. This is applicable when there already exists another NSX manager + that is registered as a vCenter extension and the current one overwrites + it. + Action required: None + Frequency of traps: Every time a NSX Manager registers as a vCenter + extension when there already exists another NSX manager registered with + vCenter" + ::= { vmwNsxMExtensionRegistrationPrefix 2 } + +-- +-- Dlp related traps +-- + +vmwNsxMDlp OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Dlp related will have this OID prefix." + ::= { vmwNsxMNotification 16 } + +vmwNsxMDlpPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Dlp module." + ::= { vmwNsxMDlp 0 } + +vmwNsxMDataSecScanStarted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid + } + STATUS current + DESCRIPTION + "A notification generated when NSX Data Security scan started + on VirtualMachine." + ::= { vmwNsxMDlpPrefix 1 } + +vmwNsxMDataSecScanEnded NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid + } + STATUS current + DESCRIPTION + "A notification generated when NSX Data Security scan ended + on VirtualMachine." + ::= { vmwNsxMDlpPrefix 2 } + +-- +-- SamSystem related traps +-- + +vmwNsxMSamSystem OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are SamSystem related will have this OID prefix." + ::= { vmwNsxMNotification 17 } + +vmwNsxMSamSystemPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for SamSystem module." + ::= { vmwNsxMSamSystem 0 } + +vmwNsxMSamDataCollectionEnabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Activity Monitoring will start collecting data. + Action required: None + Frequency of traps: Event is triggered when SAM data collection state is + toggled." + ::= { vmwNsxMSamSystemPrefix 1 } + +vmwNsxMSamDataCollectionDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Activity Monitoring will stop collecting data. + Action required: SAM data collection can be enabled to start collectiing + data. + Frequency of traps: Event is triggered when SAM data collection state is + toggled" + ::= { vmwNsxMSamSystemPrefix 2 } + +vmwNsxMSamDataStoppedFlowing NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Activity Monitoring data stopped flowing from USVM + Action required: Check the following + - USVM log to see if heartbeats are recieved and sent + - is the USVM running + - is the Mux - USVM connection healthy + - is the USVM - RMQ connection healthy + - does the VM have endpoint driver installed + Frequency of traps: Event is triggered when NSX Manager does not receives + SAM data from USVM" + ::= { vmwNsxMSamSystemPrefix 3 } + +vmwNsxMSamDataResumedFlowing NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Service Activity Monitoring data resumes flowing from USVM + Action required: None + Frequency of traps: Event is triggered when SAM data is received from USVM." + ::= { vmwNsxMSamSystemPrefix 4 } + +-- +-- Usvm related traps +-- + +vmwNsxMUsvm OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Usvm related will have this OID prefix." + ::= { vmwNsxMNotification 18 } + +vmwNsxMUsvmPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Usvm module." + ::= { vmwNsxMUsvm 0 } + +vmwNsxMUsvmHeartbeatStopped NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "USVM stopped sending heartbeats to management plane. + Action required: Connection to NSX Manager was lost. Check why the + Manager didn't send a heartbeat. + Frequency of traps: Event is triggered when NSX Manager does not receives + heartbeats from USVM" + ::= { vmwNsxMUsvmPrefix 1 } + +vmwNsxMUsvmHeartbeatResumed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "USVM will start sending heartbeats to management plane. + Action required: None + Frequency of traps: Event is triggered when NSX Manager receives + heartbeats from USVM" + ::= { vmwNsxMUsvmPrefix 2 } + +vmwNsxMUsvmReceivedHello NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "USVM sent a HELLO message to Mux + Action: None + Frequency of traps: Event is triggered when Epsec Mux receives HELLO + message from USVM during initial connection establishement." + ::= { vmwNsxMUsvmPrefix 3 } + +-- +-- VsmCore related traps +-- + +vmwNsxMVsmCore OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are VsmCore related will have this OID prefix." + ::= { vmwNsxMNotification 19 } + +vmwNsxMVsmCorePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for VsmCore module." + ::= { vmwNsxMVsmCore 0 } + +vmwNsxMUpgradeSuccess NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when NSX Manager upgraded + successfully." + ::= { vmwNsxMVsmCorePrefix 1 } + +vmwNsxMRestoreSuccess NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when NSX Manager restored + successfully." + ::= { vmwNsxMVsmCorePrefix 2 } + +vmwNsxMDuplicateIp NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The NSX Manager IP has been assigned to another machine + Action: None + Frequency: This is triggered whenever NSX Manager detects that its IP + address is being used by another machine in the same network" + ::= { vmwNsxMVsmCorePrefix 3 } + +vmwNsxMCPUHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager CPU usage is currently high.CPU usage is based on load across all cores. + Action: If NSX Manager is facing performance issue, please collect the technical + support logs for NSX Manager and the host, and contact VMware technical support. + Frequency: This is triggered whenever NSX Manager CPU is above high threshold for consecutive 5 intervals. + Default value of high threshold and interval are 80% and 1 minute respectively." + ::= { vmwNsxMVsmCorePrefix 12 } + +vmwNsxMCPUNormal NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager CPU usage is back to normal.CPU usage is based on load across all cores. + Action: None + Frequency: This is triggered whenever NSX Manager CPU is below high threshold after 1 interval from CPU being above high threshold. + Default value of high threshold and interval are 80% and 1 minute respectively." + ::= { vmwNsxMVsmCorePrefix 13 } + +vmwNsxMVirtualMachineMarkedAsSystemResource NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Virtual machine is marked as system resource + Action: None + Frequency: This is triggered whenever any virtual machine is marked as system + resource" + ::= { vmwNsxMVsmCorePrefix 4 } + +vmwNsxMScaleAboveSupportedLimits NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The scale value(s) of the mentioned parameter(s) has crossed the supported scale limits + Action: Reduce the scale of the parameter(s) mentioned + Frequency: This is triggered every hour if any new parameters cross the supported scale limits" + ::= { vmwNsxMVsmCorePrefix 5 } + +vmwNsxMScaleAboveThreshold NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The scale value(s) of the mentioned parameter(s) has crossed set threshold scale value + Action: Reduce the scale of the parameter(s) mentioned + Frequency: This is triggered every hour if any new parameters cross the set threshold value" + ::= { vmwNsxMVsmCorePrefix 6 } + + +vmwNsxMScaleNormalized NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The scale value(s) of the mentioned parameter(s) is back to normal after being above the set threshold or the supported value + Action: No action required. + Frequency: This is triggered every hour if any new parameters return to normal after being above the set threshold or the supported value" + ::= { vmwNsxMVsmCorePrefix 7 } + +vmwNsxMScaleNotEqualToRecommendedValue NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The scale value(s) of the mentioned parameter(s) is not matching the recommended value + Action: Increase/Decrease number of objects for the parameter(s) mentioned, to match with recommended value. Please refer NSX Administration guide. + Frequency: This is triggered every hour if any new parameters does not match the recommended value" + ::= { vmwNsxMVsmCorePrefix 8 } + +vmwNsxMCertificateExpired NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Certificate with mentioned id has expired. + Action: Replace expired certificate. Please refer to NSX Administration and API guide for details on certificate related operations. + Frequency: This is triggered every day until expired certificate is replaced." + ::= { vmwNsxMVsmCorePrefix 10 } + +vmwNsxMCertificateAboutToExpire NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType + } + STATUS current + DESCRIPTION + "Certificate with mentioned id will expire on mentioned date. + Action: Replace expiring certificate. Please refer to NSX Administration and API guide for details on certificate related operations. + Frequency: This is triggered every day until expiring certificate is replaced." + ::= { vmwNsxMVsmCorePrefix 11 } + +-- +-- Vxlan related traps +-- + +vmwNsxMVxlan OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Vxlan related will have this OID prefix." + ::= { vmwNsxMNotification 20 } + +vmwNsxMVxlanPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + vmware NSX manager specific trap OID's for Vxlan module." + ::= { vmwNsxMVxlan 0 } + +vmwNsxMVxlanLogicalSwitchImproperlyCnfg NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "This event is triggered if one or more distributed virtual + port groups backing a certain Logical Switch were modified and/or removed. + Or if migration of Control plane mode for a Logical Switch/Transport + Zone failed. + Action required: (1) If the event was triggered due to + deletion/modification of backing distributed virtual port groups, then the + error will be visible on Logical Switch UI page. Resolve from there will + try and create missing distributed virtual port groups for the Logical + Switch. (2) If event was triggered due to failure of Control plan mode + migration, redo the migration for that Logical Switch or Transport Zone. + Frequency of traps: Event is triggered due to user actions as explained + in description. + Affects: Logical Switch network traffic." + ::= { vmwNsxMVxlanPrefix 1 } + +vmwNsxMVxlanLogicalSwitchProperlyCnfg NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Logical Switch status has been marked good, most probably as + result of resolving any errors on it. + Action required: None + Frequency of traps: Event is triggered when user resolves the Logical + Switch error and as a result missing backing distributed virtual port + groups are recreated." + ::= { vmwNsxMVxlanPrefix 2 } + +vmwNsxMVxlanInitFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to configure vmknic as a VTEP, VXLAN traffic through + this interface will be dropped until this is resolved. + Action required: Check the host's vmkernel.log for more details. + Frequency of traps: Every time a VTEP vmknic tries to connect to it's + Distributed Virtual Port. + Affects: VXLAN traffic on the affected Host." + ::= { vmwNsxMVxlanPrefix 3 } + +vmwNsxMVxlanPortInitFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Failed to configure VXLAN on the Distributed Virtual Port, + the port will be disconnected. + Action required: Check the host's vmkernel.log for more details. + Frequency of traps: Every time a VXLAN vNic tries to connect to it's + Distributed Virtual Port on the host. + Affects: VXLAN traffic on the affected Host." + ::= { vmwNsxMVxlanPrefix 4 } + +vmwNsxMVxlanInstanceDoesNotExist NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "VXLAN configuration was received for a Distributed Virtual + Port, but the host has not yet enabled VXLAN on the vSphere Distributed + Switch. VXLAN ports on affected Host will fail to connect until resolved. + Action required: See KB 2107951 (https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2107951&sliceId=1&docTypeID=DT_KB_1_1&dialogID=40732862&stateId=0%200%2040754197) + Frequency of traps: Every time any VXLAN related port (vNic or vmknic) + tries to connect to it's Distributed Virtual Port on the host. + Affects: VXLAN Traffic on that Host." + ::= { vmwNsxMVxlanPrefix 5 } + +vmwNsxMVxlanLogicalSwitchWrkngImproperly NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "VTEP interface was unable to join the specified multicast + address, the VTEP will be unable to receive some traffic from other hosts + until this is resolved. The host will periodically retry joining the group + until it is successful. + Action required: Check the host's vmkernel.log for more details. + Frequency of traps: NSX retries joining failed mcast groups every + 5 seconds. + Affects: Logical Switch associated with problem VTEP interface won't work + properly." + ::= { vmwNsxMVxlanPrefix 6 } + +vmwNsxMVxlanTransportZoneIncorrectlyWrkng NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "The IP address of a VTEP vmknic has changed. + Action required: None. + Frequency of traps: Every time a VTEP IP changes" + ::= { vmwNsxMVxlanPrefix 7 } + +vmwNsxMVxlanTransportZoneNotUsed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "VTEP vmknic does not have a valid IP address assigned, all + VXLAN traffic through this vmknic will be dropped. + Action required: Verify the IP configuration for the interface, and the + DHCP server if DHCP is used. + Frequency of traps: Once per VTEP loosing it's IP address." + ::= { vmwNsxMVxlanPrefix 8 } + +vmwNsxMVxlanOverlayClassMissingOnDvs NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX packages where not installed prior to DVS configuration + for VXLAN. All VXLAN ports will fail to connect until resolved. + Action required: See KB 2107951 https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2107951&sliceId=1&docTypeID=DT_KB_1_1&dialogID=40732862&stateId=0%200%2040754197 + Frequency of traps: Once per setting of the com.vmware.netoverlay.layer0=vxlan + opaque property or whenver the host is configured for vxlan or Host + reconnects to VCEnter and host has some problem. + Affects: VXLAN Traffic for that Host will be affected." + ::= { vmwNsxMVxlanPrefix 9 } + +vmwNsxMVxlanControllerRemoved NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when VXLAN Controller has been removed due to + the connection cant be built, please check controller IP configuration + and deploy again." + ::= { vmwNsxMVxlanPrefix 10 } + +vmwNsxMVxlanControllerConnProblem NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected the connection between two controller + nodes is broken. + Action required: It is a warning event, users need to check the controller + cluster for the further steps. Check following KB 2127655 https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2127655&sliceId=1&docTypeID=DT_KB_1_1&dialogID=40732913&stateId=0%200%2040754965 to see if issue matches. + Frequency of traps: Whenever the controller reports the issue. + Affects: Networking might get affected." + ::= { vmwNsxMVxlanPrefix 11 } + +vmwNsxMVxlanControllerInactive NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "Host Certification information couldn't be sent to NSX + Controllers. + Action required: Ensure that NSX Controller cluster is in healthy state + before preparing a new Host. Invoke Controller Sync API to try and rectify + this error. + Frequency of traps: When a new host is prepared for NSX networking. + Affects: Newly prepared Host. Communication channel between Host and NSX + Controllers might have issues." + ::= { vmwNsxMVxlanPrefix 12 } + +vmwNsxMVxlanControllerActive NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "A notification generated when Controller cluster state is + now active. Controller Synchronization job is in progress. + Frequency of traps: Controller cluster becomes active again from a + previous inactive state. + Action required: User doesnt have to take any corrective action. + NSX will auto-sync the controllers." + ::= { vmwNsxMVxlanPrefix 13 } + +vmwNsxMVxlanVmknicMissingOrDeleted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "VXLAN vmknic is missing or deleted from host. + Action required: Issue can be resolved from Logical Network + Preparation - VXLAN Transport UI section. Clicking on resolve will try to + rectify the issue. + Frequency of traps: First time NSX Manager finds that VXLAN vmknic is + missing or deleted from Host. + Affects: VXLAN Traffic to/from the mentioned Host will be affected." + ::= { vmwNsxMVxlanPrefix 14 } + +vmwNsxMVxlanInfo NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager will raise this event when connection between + either of the following component is established/re-established + (i) connection between NSX Manager and Host Firewall agent. + (ii) connection between NSX Manager and Control Plane Agent. + (iii) connection between Control Plane Agent to Controllers. + Action required: None + Frequency of traps: NSX Manager will raise this event when connection + between either of the following component is established/re-established + (i) connection between NSX Manager and Host Firewall agent. + (ii) connection between NSX Manager and Control Plane Agent + (iii) connection between Control Plane Agent to Controllers." + ::= { vmwNsxMVxlanPrefix 15 } + +vmwNsxMVxlanVmknicPortGrpMissing NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected one vxlan vmknic is missing on VC. + Action required: Check the host, if that vmknic is deleted, click on the + resolve button on UI, or call the remediate API (POST /api/2.0/vdn/config/host/{hostId}/vxlan/vteps?action=remediate) + to recreate the vxlan vmknic. + Frequency of traps: First time when vxlan vmknic is detected missing + (manually deleted by user or inventory report the incorrect information) + Affects: The VXLAN traffic on that host may be interrupted." + ::= { vmwNsxMVxlanPrefix 16 } + +vmwNsxMVxlanVmknicPortGrpAppears NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected one vxlan vmknic that was marked as + missing has now reappeared on VC. + Action required: None + Frequency of traps: When that missing vmknic re-appears again. + Affects: The VXLAN traffic on that host may be resumed." + ::= { vmwNsxMVxlanPrefix 17 } + +vmwNsxMVxlanConnDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "This event is triggered when either of the following + connections are detected down by NSX Manager: + (i) connection between NSX Manager and Host Firewall agent. + (ii) connection between NSX Manager and Control Plane Agent. + (iii) connection between Control Plane Agent to Controllers. + Action required: + (i) If NSX Manager to Host Firewall Agent connection is + down, check NSX Manager and Firewall Agent logs to get error details. You + can try Fabric Synchronize API to try and retificy this issue. + (ii) If NSX Manager to Control Plane Agent connection is down, please + check NSX Manager and Control Plane Agent logs to get the error detail, + check whether the Control Plane Agent process is down. + (iii) If Control Plane Agent to Controllers connection is down, please go + to UI Installation page to check the connection status for crossponding + Host. + Frequency of traps: When + (i) NSX Manager looses connection with Firewall agent on host or + (ii) NSX Manager losses connection with Control plane agent on host or + (iii) Control plane agent on Host looses connection with NSX Controllers. + Affects: VMs on that Host might get affected." + ::= { vmwNsxMVxlanPrefix 18 } + +vmwNsxMBackingPortgroupMissing NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected one backing portgroup of a logical + switch is missing on VCenter. + Action required: Click on the resolve button on UI or call the API + (POST https://<nsx-manager-host>/api/2.0/vdn/virtualwires/<virtualwireId>/backing?action=remediate) + to recreate that backing portgroup. + Frequency of traps: Whenever logical switch backing portgroup is missing + on VC. + Affects: VMs cannot be connected to this Logical Switch." + ::= { vmwNsxMVxlanPrefix 19 } + +vmwNsxMBackingPortgroupReappears NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected one backing portgroup of a logical + switch that was missing reappears on VC. + Action required: None + Frequency of traps: Whenever user triggered remediate API on Logical + Switch which has missing backing portgroup." + ::= { vmwNsxMVxlanPrefix 20 } + +vmwNsxMManagedObjectIdChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected the Managed Objectid of one backing + portgroup of a logical switch changed. + Action required: None + Frequnecy of traps: This typically happens when user restores a backup + of Logical Switch backing portgroup." + ::= { vmwNsxMVxlanPrefix 21 } + +vmwNsxMHighLatencyOnDisk NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected some disk on a NSX Controller has high + latency. + Action required: Rectify the issue on specified device and controller. + Frequency of traps: First time NSX detected this issue as reported by + Controller. When this issue gets resolved another Informational event will + be raised by NSX Manager indicating the same. + Affects: NSX Controller." + ::= { vmwNsxMVxlanPrefix 22 } + +vmwNsxMHighLatencyOnDiskResolved NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected the disk high latency alert on a some + disk on a NSX Controller has been resolved. + Frequency of traps: First time NSX detected, previously raised disk + latency issue has been resolved." + ::= { vmwNsxMVxlanPrefix 23 } + +vmwNsxMControllerVmPoweredOff NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected a Controller Virtual Machine is powered + off from vCenter. + Action required: Click on the 'Resolve' button on Controller page on UI or + call the API (POST https://<nsx-manager-host>/api/2.0/vdn/controller/{controllerId}?action=remediate) + to power on the Controller Virtual Machine. + Frequency of traps: This event wil be raised when controller Virtual + Machine is powered off from vCenter. + Affects: Controller cluster status might go to disconnected if a controller + Virtual Machine is powered off. Any operation that requires an active + Controller Cluster may be affected." + ::= { vmwNsxMVxlanPrefix 24 } + +vmwNsxMControllerVmDeleted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected a Controller Virtual Machine is deleted + from vCenter. + Action required: Click on the Resolve button on Controller page on UI or + call the API (POST https://<nsx-manager-host>/api/2.0/vdn/controller/{controllerId}?action=remediate) + to clean up NSX manager's database state. + Frequency of traps: This event will be raised when Controller Virtual + Machine is deleted from vCenter. + Affects: Controller cluster status might go to disconnected if a controller + Virtual Machine is powered off. Any operation that requires an active + Controller Cluster may be affected." + ::= { vmwNsxMVxlanPrefix 25 } + +vmwNsxMVxlanConfigNotSet NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX manager detected the VXLAN configuration is not set on + the host (would-block issue). And this event indicates NSX Manager tried + to rectify this issue by resending the VXLAN configuration on Host. + Action required: See KB 2107951 https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2107951&sliceId=1&docTypeID=DT_KB_1_1&dialogID=40732862&stateId=0%200%2040754197 + for more information. + Frequency of traps: This event will generate when host preparation task is + triggered for a host and Host encounters would-block issue. + Affects: It is a notification, no specific guide for the next step." + ::= { vmwNsxMVxlanPrefix 26 } + +vmwNsxMVxlanPortgroupDeleted NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "NSX Manager will raise this event when a VXLAN portgroup is deleted from + a switch. + ACTION: User does not have to take any action. This is just a notification + for the user. + FREQUENCY: This event is generated a single time when the VXLAN portgroup + is deleted from the switch. + AFFECTS: The VXLAN traffic on the switch is interrupted." + ::= { vmwNsxMVxlanPrefix 27 } + +vmwNsxMVxlanVDSandPgMismatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "DESCRIPTION: NSX Manager will raise this event when the teaming policies of + a VDS and it's associated VXLAN portgroup are not the same. + ACTION: Set the VXLAN portgroup teaming policy back to the original value. + Below is the workaround to correctly update the teaming policy in a deployed + cluster: The supported method to correct teaming policy inconsistencies is + to create and prepare a new NSX cluster with the required teaming policy, + and to migrate ESXi hosts to that cluster. Changing the teaming policy in + the manager DB by some other means only applies to newly created virtual + wires after the DB change is made. + FREQUENCY: This event will generate whenever the VXLAN portgroup teaming + policy is changed to something different than the VDS teaming policy. + AFFECTS: The VXLAN traffic on the switch may be interrupted." + ::= { vmwNsxMVxlanPrefix 28 } + +vmwNsxMVxlanControllerDisconnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "DESCRIPTION: NSX Manager raises this event when the Controller VM is + Disconnected ie the controller can not reached from the NSX Manager. + ACTION: Make sure the IP is assigned to the controller VM and it is + reachable form the NSX Manager. + FREQUENCY: The event occurs when the Controller VM is powered off or not responding. + Minimum 40 secs between two disconnecet events. + AFFECTS: Controller cluster status might go to disconnected if a controller + Virtual Machine is disconnected. Any operation that requires an active + Controller Cluster may be affected." + ::= { vmwNsxMVxlanPrefix 29 } + +vmwNsxMVxlanControllerConnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "DESCRIPTION: NSX Manager will raise this informational event when the + controller VM is connected to controller cluster. + ACTION: No action to be taken. + FREQUENCY: Event occurs as controller is connected to controller-cluster. + Minimum 40 secs between two connecet events. + AFFECTS: None." + ::= { vmwNsxMVxlanPrefix 30 } + +vmwNsxMVxlanControllerVmPoweredOn NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "DESCRIPTION: NSX manager detected a Controller Virtual Machine is powered on from vCenter. + ACTION: None. + FREQUENCY: This event occurs when Controller Virtual Machine is powered On. + AFFECTS: Controller cluster status might go to disconnected if a controller Virtual Machine + is powered off. Any operation that requires an active Controller Cluster may be affected." + ::= { vmwNsxMVxlanPrefix 31 } + +vmwNsxMVxlanHostEvents NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "DESCRIPTION: NSX manager receives a notification from the host informing MAC mismatch occurred. + ACTION: Contact the administrator to take following action: + (1) Look for VMs that caused this issue at hosts. + (2) If VMs are rouge, shut dowm these VMs. + FREQUENCY: Event is triggerred as MAC mismatch occurs at switchport on the hosts. + AFFECTS: Identify the VMs causing this issue." + ::= { vmwNsxMVxlanPrefix 32 } + +-- +-- Domain Controller Event Log server related trap +-- +vmwNsxMLogserver OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Domain Controller Event Log server related will have this OID prefix." + ::= { vmwNsxMNotification 21 } + +vmwNsxMLogserverPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is the prefix one uses when creating + vmware NSX manager specific trap OID's for VsmCore module." + ::= { vmwNsxMLogserver 0 } + +vmwNsxMLogserverEventGenStopped NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid + } + STATUS current + DESCRIPTION + "DESCRIPTION: This event is triggered if the security log on domain controller event log server is full. + ACTION: See article regarding the issue : https://support.microsoft.com/en-us/kb/867860 + Contact Domain Administrator to take one of the following actions: + (1). Inclease the size of security log. + (2). Clear the security log. + (3). Archive the security log. + FREQUENCY: Event is triggered due to event log size reaches its limit. + AFFECTS: Identity firewall stops functioning." + ::= { vmwNsxMLogserverPrefix 1 } + +-- +-- Application Rule Manager Event Log related trap +-- +vmwNsxMApplicationRuleManager OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications that are Application Rule Manager related will have this OID prefix." + ::= { vmwNsxMNotification 22 } + +vmwNsxMApplicationRuleManagerPrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is the prefix one uses when creating + vmware NSX manager specific trap OID's for Application Rule Manager module." + ::= { vmwNsxMApplicationRuleManager 0 } + +vmwNsxMApplicationRuleManagerFlowAnalysisStart NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid + } + STATUS current + DESCRIPTION + "Started flow analysis on Application Rule Manager session. + Action required: None + Frequency of traps:This trap is sent once for each session on which analysis has started" + ::= { vmwNsxMApplicationRuleManagerPrefix 1 } + +vmwNsxMApplicationRuleManagerFlowAnalysisFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid + } + STATUS current + DESCRIPTION + "Flow analysis failed on Application Rule Manager session. + Contextual data provided with this event may indicate the cause of this failure. + Action required: Start a new monitoring session for the applcation and try analyzing flows again. + On repeated failure, collect ESX & NSX Manager tech support bundle and open SR with Vmware tech support. + Frequency of traps:This trap is sent once for each session on which analysis has failed" + ::= { vmwNsxMApplicationRuleManagerPrefix 2 } + +vmwNsxMApplicationRuleManagerFlowAnalysisComplete NOTIFICATION-TYPE + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid + } + STATUS current + DESCRIPTION + "Completed flow analysis on Application Rule Manager session. + Action required: None + Frequency of traps:This trap is sent once for each session on which analysis has completed" + ::= { vmwNsxMApplicationRuleManagerPrefix 3 } + +-- conformance information +vmwNsxManagerMIBConformance OBJECT IDENTIFIER ::= { vmwNsxManagerMIB 99 } +vmwNsxManagerMIBCompliances OBJECT IDENTIFIER ::= + { vmwNsxManagerMIBConformance 1 } +vmwNsxManagerMIBGroups OBJECT IDENTIFIER ::= { vmwNsxManagerMIBConformance 2 } + +-- compliance statements +vmwNsxManagerMIBBasicCompliance MODULE-COMPLIANCE + STATUS obsolete + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1 } + ::= { vmwNsxManagerMIBCompliances 3 } + +vmwNsxManagerNotificationInfoGroup1 OBJECT-GROUP + OBJECTS { + vmwNsxMEventCode, + vmwNsxMEventTimestamp, + vmwNsxMEventMessage, + vmwNsxMEventSeverity, + vmwNsxMEventComponent, + vmwNsxMUuid, + vmwNsxMCount, + vmwNsxMEventSourceID, + vmwNsxMEventSourceType, + vmwNsxMEventSourceIP + } + STATUS current + DESCRIPTION + "These objects provide details in NSX Manager notifications." + ::= { vmwNsxManagerMIBGroups 2 } + +vmwNsxManagerNotificationGroup1 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMConfigGroup, + vmwNsxMIpAddedBlackList, + vmwNsxMIpRemovedBlackList, + vmwNsxMSsoConfigFailure, + vmwNsxMSsoUnconfigured, + vmwNsxMUserRoleAssigned, + vmwNsxMUserRoleUnassigned, + vmwNsxMGroupRoleAssigned, + vmwNsxMGroupRoleUnassigned, + vmwNsxMVcLoginFailed, + vmwNsxMVcDisconnected, + vmwNsxMLostVcConnectivity, + vmwNsxMFltrCnfgUpdateFailed, + vmwNsxMFltrCnfgNotAppliedToVnic, + vmwNsxMFltrCnfgAppliedToVnic, + vmwNsxMFltrCreatedForVnic, + vmwNsxMFltrDeletedForVnic, + vmwNsxMFirewallConfigUpdateFailed, + vmwNsxMFirewallRuleFailedVnic, + vmwNsxMFirewallRuleAppliedVnic, + vmwNsxMCntnrCnfgUpdateFailed, + vmwNsxMFlowMissed, + vmwNsxMSpoofGuardCnfgUpdateFailed, + vmwNsxMSpoofGuardFailed, + vmwNsxMSpoofGuardApplied, + vmwNsxMSpoofGuardDisableFail, + vmwNsxMSpoofGuardDisabled, + vmwNsxMLegacyAppServiceDeletionFailed, + vmwNsxMFirewallCpuThresholdCrossed, + vmwNsxMFirewallMemThresholdCrossed, + vmwNsxMConnPerSecThrshldCrossed, + vmwNsxMFirewallCnfgUpdateTimedOut, + vmwNsxMSpoofGuardCnfgUpdateTmOut, + vmwNsxMFirewallPublishFailed, + vmwNsxMCntnrUpdatePublishFailed, + vmwNsxMSpoofGuardUpdatePublishFailed, + vmwNsxMExcludeListPublishFailed, + vmwNsxMFirewallCnfgUpdateOnDltCntnr, + vmwNsxMHostSyncFailed, + vmwNsxMHostSynced, + vmwNsxMFirewallInstalled, + vmwNsxMFirewallClusterInstalled, + vmwNsxMFirewallClusterUninstalled, + vmwNsxMFirewallClusterDisabled, + vmwNsxMEdgeNoVmServing, + vmwNsxMEdgeGatewayCreated, + vmwNsxMEdgeVmBadState, + vmwNsxMEdgeVmCommFailed, + vmwNsxMEdgeVmCnfgChanged, + vmwNsxMEdgeGatewayDeleted, + vmwNsxMEdgeGatewayReDeployed, + vmwNsxMEdgeVmPowerOff, + vmwNsxMEdgeApplianceSizeChanged, + vmwNsxMEdgeUpgrade51x, + vmwNsxMEdgeLicenseChanged, + vmwNsxMEdgeApplianceMoved, + vmwNsxMEdgeApplianceNotFound, + vmwNsxMEdgeVMHealthCheckMiss, + vmwNsxMEdgeHealthCheckMiss, + vmwNsxMEdgeCommAgentNotConnected, + vmwNsxMApplianceWithDifferentId, + vmwNsxMFirewallRuleModified, + vmwNsxMEdgeAntiAffinityRuleViolated, + vmwNsxMEdgeHaEnabled, + vmwNsxMEdgeHaDisabled, + vmwNsxMEdgeHaInUseVnicChanged, + vmwNsxMEdgeGatewayRecovered, + vmwNsxMEdgeVmRecovered, + vmwNsxMEdgeGatewayUpgraded, + vmwNsxMEdgeVmHlthChkDisabled, + vmwNsxMEdgePrePublishFailed, + vmwNsxMEdgeForcedSync, + vmwNsxMEdgeVmBooted, + vmwNsxMEdgeVmInBadState, + vmwNsxMEdgeVmCpuUsageIncreased, + vmwNsxMEdgeVmMemUsageIncreased, + vmwNsxMEdgeVmProcessFailure, + vmwNsxMEdgeVmSysTimeBad, + vmwNsxMEdgeVmSysTimeSync, + vmwNsxMEdgeAesniCryptoEngineUp, + vmwNsxMEdgeAesniCryptoEngineDown, + vmwNsxMEdgeVmOom, + vmwNsxMEdgeFileSysRo, + vmwNsxMEdgeHaCommDisconnected, + vmwNsxMEdgeHaSwitchOverSelf, + vmwNsxMEdgeHaSwitchOverActive, + vmwNsxMEdgeHaSwitchOverStandby, + vmwNsxMEdgeMonitorProcessFailure, + vmwNsxMLbVirtualServerPoolUp, + vmwNsxMLbVirtualServerPoolDown, + vmwNsxMLbVirtualServerPoolWrong, + vmwNsxMLbPoolWarning, + vmwNsxMIpsecChannelUp, + vmwNsxMIpsecChannelDown, + vmwNsxMIpsecTunnelUp, + vmwNsxMIpsecTunnelDown, + vmwNsxMIpsecChannelUnknown, + vmwNsxMIpsecTunnelUnknown, + vmwNsxMGlobalLbMemberUp, + vmwNsxMGlobalLbMemberWarning, + vmwNsxMGlobalLbMemberDown, + vmwNsxMGlobalLbMemberUnknown, + vmwNsxMGlobalLbPeerUp, + vmwNsxMGlobalLbPeerDown, + vmwNsxMDhcpServiceDisabled, + vmwNsxMEndpointThinAgentEnabled, + vmwNsxMGuestIntrspctnEnabled, + vmwNsxMGuestIntrspctnIncompatibleEsx, + vmwNsxMGuestIntrspctnEsxConnFailed, + vmwNsxMGuestIntrspctnStatusRcvFailed, + vmwNsxMEsxModuleEnabled, + vmwNsxMEsxModuleUninstalled, + vmwNsxMGuestIntrspctnHstMxMssngRep, + vmwNsxMEndpointUndefined, + vmwNsxMEamGenericAlarm, + vmwNsxMFabricDplymntStatusChanged, + vmwNsxMFabricDplymntUnitCreated, + vmwNsxMFabricDplymntUnitUpdated, + vmwNsxMFabricDplymntUnitDestroyed, + vmwNsxMDataStoreNotCnfgrdOnHost, + vmwNsxMFabricDplymntInstallationFailed, + vmwNsxMFabricAgentCreated, + vmwNsxMFabricAgentDestroyed, + vmwNsxMFabricSrvceNeedsRedplymnt, + vmwNsxMUpgradeOfDplymntFailed, + vmwNsxMFabricDependenciesNotInstalled, + vmwNsxMFabricErrorNotifSecBfrUpgrade, + vmwNsxMFabricErrCallbackNtRcvdUpgrade, + vmwNsxMFabricErrCallbackNtRcvdUninstall, + vmwNsxMFabricUninstallServiceFailed, + vmwNsxMFabricErrorNotifSecBfrUninstall, + vmwNsxMFabricServerRebootUninstall, + vmwNsxMFabricServerRebootUpgrade, + vmwNsxMFabricConnEamFailed, + vmwNsxMFabricConnEamRestored, + vmwNsxMFabricPreUninstallCleanUpFailed, + vmwNsxMFabricBackingEamNotFound, + vmwNsxMFabricUninstallDeploymentUnit, + vmwNsxMDepPluginIpPoolExhausted, + vmwNsxMDepPluginGenericAlarm, + vmwNsxMDepPluginGenericException, + vmwNsxMDepPluginVmReboot, + vmwNsxMMessagingConfigFailed, + vmwNsxMMessagingReconfigFailed, + vmwNsxMMessagingConfigFailedNotifSkip, + vmwNsxMMessagingInfraUp, + vmwNsxMMessagingInfraDown, + vmwNsxMMessagingDisabled, + vmwNsxMServiceComposerPolicyOutOfSync, + vmwNsxMServiceComposerPolicyDeleted, + vmwNsxMInconsistentSvmAlarm, + vmwNsxMSvmRestartAlarm, + vmwNsxMSvmAgentUnavailable, + vmwNsxMVmAddedToSg, + vmwNsxMVmRemovedFromSg, + vmwNsxMFullUniversalSyncFailed, + vmwNsxMSecondaryDown, + vmwNsxMUniversalSyncFailedForEntity, + vmwNsxMServerUp, + vmwNsxMExtensionRegistered, + vmwNsxMExtensionUpdated, + vmwNsxMDataSecScanStarted, + vmwNsxMDataSecScanEnded, + vmwNsxMSamDataCollectionEnabled, + vmwNsxMSamDataCollectionDisabled, + vmwNsxMSamDataStoppedFlowing, + vmwNsxMSamDataResumedFlowing, + vmwNsxMUsvmHeartbeatStopped, + vmwNsxMUsvmHeartbeatResumed, + vmwNsxMUsvmReceivedHello, + vmwNsxMUpgradeSuccess, + vmwNsxMRestoreSuccess, + vmwNsxMVxlanLogicalSwitchImproperlyCnfg, + vmwNsxMVxlanLogicalSwitchProperlyCnfg, + vmwNsxMVxlanInitFailed, + vmwNsxMVxlanPortInitFailed, + vmwNsxMVxlanInstanceDoesNotExist, + vmwNsxMVxlanLogicalSwitchWrkngImproperly, + vmwNsxMVxlanTransportZoneIncorrectlyWrkng, + vmwNsxMVxlanTransportZoneNotUsed, + vmwNsxMVxlanOverlayClassMissingOnDvs, + vmwNsxMVxlanControllerRemoved, + vmwNsxMVxlanControllerConnProblem, + vmwNsxMVxlanControllerInactive, + vmwNsxMVxlanControllerActive, + vmwNsxMVxlanVmknicMissingOrDeleted, + vmwNsxMVxlanInfo, + vmwNsxMVxlanVmknicPortGrpMissing, + vmwNsxMVxlanVmknicPortGrpAppears, + vmwNsxMVxlanConnDown, + vmwNsxMSamDataCollectionDisabled, + vmwNsxMSamDataStoppedFlowing, + vmwNsxMSamDataResumedFlowing, + vmwNsxMVxlanOverlayClassMissingOnDvs, + vmwNsxMVxlanControllerRemoved, + vmwNsxMVxlanControllerConnProblem, + vmwNsxMVxlanControllerInactive, + vmwNsxMSsoDisconnected, + vmwNsxMFirewallInstallFailed, + vmwNsxMFirewallForceSyncClusterFailed, + vmwNsxMFirewallForceSyncClusterSuccess, + vmwNsxMFirewallVsfwdProcessStarted, + vmwNsxMEdgeResourceReservationFailure, + vmwNsxMEdgeSplitBrainDetected, + vmwNsxMEdgeSplitBrainRecovered, + vmwNsxMEdgeSplitBrainRecoveryAttempt, + vmwNsxMServiceComposerFirewallPolicyOutOfSync, + vmwNsxMServiceComposerNetworkPolicyOutOfSync, + vmwNsxMServiceComposerGuestPolicyOutOfSync, + vmwNsxMServiceComposerOutOfSync, + vmwNsxMServiceComposerOutOfSyncRebootFailure, + vmwNsxMServiceComposerOutOfSyncDraftRollback, + vmwNsxMServiceComposerOutOfSyncSectionDeletionFailure, + vmwNsxMServiceComposerOutOfSyncPrecedenceChangeFailure, + vmwNsxMServiceComposerOutOfSyncDraftSettingFailure, + vmwNsxMBackingPortgroupMissing, + vmwNsxMBackingPortgroupReappears, + vmwNsxMManagedObjectIdChanged, + vmwNsxMHighLatencyOnDisk, + vmwNsxMHighLatencyOnDiskResolved, + vmwNsxMControllerVmPoweredOff, + vmwNsxMControllerVmDeleted, + vmwNsxMVxlanConfigNotSet, + vmwNsxMSnmpDisabled, + vmwNsxMSnmpManagerConfigUpdated, + vmwNsxMDuplicateIp + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 3 } + + +vmwNsxManagerMIB630Compliance MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB" + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2 } + ::= { vmwNsxManagerMIBCompliances 4 } + +vmwNsxManagerNotificationGroup2 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMFirewallRulesetApplyAllFailed, + vmwNsxMFirewallRulesetAppliedAll, + vmwNsxMCntnrCnfgApplyFailedToVnic, + vmwNsxMCntnrCnfgApplyAllFailedToVnic, + vmwNsxMCntnrCnfgAppliedAllToVnic, + vmwNsxMSpoofGuardApplyAllFailed, + vmwNsxMSpoofGuardAppliedAll, + vmwNsxMFirewallTimeoutUpdateFailed, + vmwNsxMFirewallTimeoutApplyFailed, + vmwNsxMFirewallTimeoutApplied, + vmwNsxMFirewallTimeoutApplyAllFailed, + vmwNsxMFirewallTimeoutAppliedAll, + vmwNsxMCntnrCnfgAppliedToVnic, + vmwNsxMLogserverEventGenStopped, + vmwNsxMApplicationRuleManagerFlowAnalysisStart, + vmwNsxMApplicationRuleManagerFlowAnalysisFailed, + vmwNsxMApplicationRuleManagerFlowAnalysisComplete, + vmwNsxMEdgeResourceReservationSuccess, + vmwNsxMVirtualMachineMarkedAsSystemResource, + vmwNsxMEdgeSddcChannelUp, + vmwNsxMEdgeSddcChannelDown, + vmwNsxMScaleAboveSupportedLimits, + vmwNsxMScaleAboveThreshold, + vmwNsxMScaleNormalized, + vmwNsxMVxlanPortgroupDeleted, + vmwNsxMVxlanVDSandPgMismatch + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 4 } + + + +vmwNsxManagerMIB64Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB" + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3 } + ::= { vmwNsxManagerMIBCompliances 5 } + + +vmwNsxManagerNotificationGroup3 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMEdgeDuplicateIpDetected, + vmwNsxMEdgeDuplicateIpResolved, + vmwNsxMEdgeBgpNeighborUp, + vmwNsxMEdgeBgpNeighborDown, + vmwNsxMEdgeBgpNeighborASMismatch, + vmwNsxMEdgeOSPFNeighborUp, + vmwNsxMEdgeOSPFNeighborDown, + vmwNsxMEdgeOSPFNeighborMTUMismatch, + vmwNsxMEdgeOSPFNeighborAreaIdMisMatch, + vmwNsxMEdgeOSPFNeighborHelloTimerMisMatch, + vmwNsxMEdgeOSPFNeighborDeadTimerMisMatch, + vmwNsxMEdgeL2vpnTunnelUp, + vmwNsxMEdgeL2vpnTunnelDown, + vmwNsxMEdgeHAForceStandbyRemoved, + vmwNsxMEdgeHAForceStandbyRemovalFailed, + vmwNsxMEdgeVmBADStateRecovered, + vmwNsxMEdgeVmBADStateAutoHealRecoveryDisabled, + vmwNsxMFirewallMaxConcurrentConnectionsThresholdCrossed, + vmwNsxMFirewallProcessMemoryThresholdCrossed, + vmwNsxMFirewallCpuThresholdCrossCleared, + vmwNsxMFirewallMemThresholdCrossCleared, + vmwNsxMConnPerSecThrshldCrossCleared, + vmwNsxMFirewallMaxConcurrentConnectionsThresholdCrossCleared, + vmwNsxMFirewallProcessMemoryThresholdCrossCleared, + vmwNsxMFirewallThresholdConfigApplied, + vmwNsxMFirewallThresholdConfigApplyFailed, + vmwNsxMEdgeHaCommConnected, + vmwNsxMVxlanControllerDisconnected, + vmwNsxMVxlanControllerConnected, + vmwNsxMVxlanControllerVmPoweredOn, + vmwNsxMVxlanHostEvents, + vmwNsxMScaleNotEqualToRecommendedValue + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 5 } + +vmwNsxManagerMIB636Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB" + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup4 } + ::= { vmwNsxManagerMIBCompliances 6 } + + +vmwNsxManagerNotificationGroup4 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMUniversalSyncStoppedOnSecondary, + vmwNsxMUniversalSyncResumedOnSecondary + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 6 } + +vmwNsxManagerMIB641Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB" + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5 } + ::= { vmwNsxManagerMIBCompliances 7 } + + +vmwNsxManagerNotificationGroup5 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMUniversalSyncStoppedOnSecondary, + vmwNsxMUniversalSyncResumedOnSecondary, + vmwNsxMCertificateExpired, + vmwNsxMCertificateAboutToExpire, + vmwNsxMCPUHigh, + vmwNsxMCPUNormal, + vmwNsxMUnsupportedIPsetConfigured + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 7 } + +vmwNsxManagerMIB637Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup4, + vmwNsxManagerNotificationGroup6} + ::= { vmwNsxManagerMIBCompliances 8 } + + +vmwNsxManagerNotificationGroup6 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMUnsupportedIPsetConfigured + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 8 } + +vmwNsxManagerMIB642Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7} + ::= { vmwNsxManagerMIBCompliances 9 } + +vmwNsxManagerNotificationGroup7 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMSsoTimeout, + vmwNsxMFabricVibManualInstallationRequired + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 9 } + +vmwNsxManagerMIB645Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7, + vmwNsxManagerNotificationGroup8} + ::= { vmwNsxManagerMIBCompliances 10 } + +vmwNsxManagerNotificationGroup8 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMEdgeVmRenameFailed, + vmwNsxMEdgeBgpNeighborshipError + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 10 } + +vmwNsxManagerMIB646Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7, + vmwNsxManagerNotificationGroup8, + vmwNsxManagerNotificationGroup9} + ::= { vmwNsxManagerMIBCompliances 11 } + +vmwNsxManagerNotificationGroup9 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMEdgeVmBadStateNotRecovered, + vmwNsxMEdgeVmDcnOutOfSync, + vmwNsxMEdgeConsumedResourcesMissingInInventory + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 11 } + +vmwNsxManagerMIB647Compliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwNsxManagerNotificationInfoGroup1, + vmwNsxManagerNotificationGroup1, + vmwNsxManagerNotificationGroup2, + vmwNsxManagerNotificationGroup3, + vmwNsxManagerNotificationGroup5, + vmwNsxManagerNotificationGroup7, + vmwNsxManagerNotificationGroup8, + vmwNsxManagerNotificationGroup9, + vmwNsxManagerNotificationGroup10} + ::= { vmwNsxManagerMIBCompliances 12 } + +vmwNsxManagerNotificationGroup10 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxMEdgeIpsecDeprecatedComplianceSuiteInUse, + vmwNsxMEdgeConnectedToMultipleTZHavingSameClusters, + vmwNsxMEdgeConnectedToMultipleTZHavingDifferentClusters + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwNsxManagerMIBGroups 12 } + +END diff --git a/MIBS/vmware/VMWARE-NSX-MIB b/MIBS/vmware/VMWARE-NSX-MIB new file mode 100644 index 0000000..a6e3af2 --- /dev/null +++ b/MIBS/vmware/VMWARE-NSX-MIB @@ -0,0 +1,13579 @@ +-- ********************************************************** +-- Copyright 2019-2022 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-NSX-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + TEXTUAL-CONVENTION, DateAndTime + FROM SNMPv2-TC + vmwNSXsys + FROM VMWARE-ROOT-MIB; + + vmwNSXsysMIB MODULE-IDENTITY + LAST-UPDATED "202202140000Z" + 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 + "In much the same way that server virtualization programmatically + creates, snapshots, deletes, and restores software-based virtual + machines (VMs), NSX-T Data Center network virtualization + programmatically creates, deletes, and restores software-based + virtual networks. + + With network virtualization, the functional equivalent of a network + hypervisor reproduces the complete set of Layer 2 through Layer 7 + networking services (for example, switching, routing, access control, + firewalling, QoS) in software. As a result, these services can be + programmatically assembled in any arbitrary combination, to produce + unique, isolated virtual networks in a matter of seconds. + + For more information about NSX-T Data Center, please visit: + https://docs.vmware.com/en/VMware-NSX-T-Data-Center/ + " + + REVISION "202202140000Z" + DESCRIPTION + "This revision adds 174 new notifications for NSX-T Data Center 3.2.0" + + REVISION "202108060000Z" + DESCRIPTION + "This revision adds 18 new notifications for NSX-T Data Center 3.1.3" + + REVISION "202104220000Z" + DESCRIPTION + "This revision adds 12 new notifications for NSX-T Data Center 3.1.2" + + REVISION "202103250000Z" + DESCRIPTION + "This revision adds 2 new notifications for NSX-T Data Center 3.0.3" + + REVISION "202101300000Z" + DESCRIPTION + "This revision adds 2 new notifications for NSX-T Data Center 3.1.1" + + REVISION "202010300000Z" + DESCRIPTION + "This revision adds 56 new notifications for NSX-T Data Center 3.1.0" + + REVISION "202009220000Z" + DESCRIPTION + "This revision adds 10 new notifications for NSX-T Data Center 3.0.2" + + REVISION "202006290000Z" + DESCRIPTION + "This revision adds 12 new notifications for NSX-T Data Center 3.0.1" + + REVISION "202003240000Z" + DESCRIPTION + "Initial revision of NSX-T Data Center SNMP event notifications." + + ::= { vmwNSXsys 1 } + +-- ********************************************************** +-- Top-level MIB groups +-- ********************************************************** + +vmwNsxTDataCenterNotifications OBJECT-IDENTITY + STATUS current + DESCRIPTION + "All event notifications from NSX-T Data Center fall under this oid." + ::= { vmwNSXsysMIB 0 } + +vmwNsxTDataCenterData OBJECT-IDENTITY + STATUS current + DESCRIPTION + "All variables that are sent in NSX-T Data Center event notifications + fall under this oid." + ::= { vmwNSXsysMIB 1 } + +-- ********************************************************** +-- Type definitions +-- ********************************************************** + +VmwNsxTDataCenterFeatureIdType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "The NSX-T Data Center feature ID associated with the event. + For example, this value identifies the feature is managerHealth, + edgeHealth, loadBalancer, etc." + SYNTAX INTEGER { + managerHealth(1), + edgeHealth(2), + certificates(3), + passwordManagement(4), + licenses(5), + intelligenceHealth(6), + infrastructureCommunication(7), + intelligenceCommunication(9), + cniHealth(10), + ncpHealth(11), + nodeAgentsHealth(12), + endpointProtection(13), + vpn(15), + alarmManagement(16), + loadBalancer(17), + transportNodeHealth(18), + infrastructureService(19), + dhcp(20), + highAvailability(21), + capacity(22), + auditLogHealth(24), + routing(28), + dns(30), + distributedFirewall(31), + federation(32), + distributedIdsIps(33), + communication(35), + identityFirewall(36), + ipam(38), + gatewayFirewall(39), + clustering(40), + nsxApplicationPlatformCommunication(41), + mtuCheck(42), + nsxApplicationPlatformHealth(43), + edge(45), + nat(46) + } + +VmwNsxTDataCenterEventTypeType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of the NSX-T Data Center event. The complete set of events + are reported by the NSX API GET /api/v1/events." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSeverityType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "The severity of the NSX-T Data Center event. Currently only the + critical(2), error(3), warning(4) and informational(6) levels + are used, but the other levels may be used in future releases." + SYNTAX INTEGER { + emergency(0), + alert(1), + critical(2), + error(3), + warning(4), + notice(5), + informational(6), + debug(7) + } + +VmwNsxTDataCenterNodeIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The node ID from where a NSX-T Data Center event was emitted. A + node ID can be for a cluster node as reported by the NSX API + GET /api/v1/cluster. Or a node ID can be for a transport node + as reported by the NSX API GET /api/v1/transport-nodes." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNodeTypeType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "The type of node from where a NSX-T Data Center event was emitted." + SYNTAX INTEGER { + manager(0), + edge(1), + esx(2), + kvm(3), + publiccloudgateway(4), + intelligence(5), + autonomousedge(6), + globalmanager(7) + } + +VmwNsxTDataCenterEntityIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The ID of a NSX-T Data Center entity an event pertains to. The event + description field provides additional details of the entity. For + example the ID can be for a specific Load Balancer rule as reported by + the NSX API GET /api/v1/loadbalancer/rules or a specific certificate + as reported by the NSX API GET /api/v1/trust-management/certificates." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSystemResourceUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The CPU, memory, or disk usage percentage of an NSX-T appliance. The + value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDiskPartitionNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of a disk partition in an NSX-T appliance. For example, the + name for the /tmp partition is '/tmp'." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterLicenseEditionTypeType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The edition type of an NSX-T license. For example, the type for an NSX-T + evaluation license is 'NSX Data Center Evaluation'." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterApplianceAddressType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The NSX appliance's IP address. The value is an IPv4 address." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterCurrentGatewayStateType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The current gateway state. The value could be active/standby/admin down." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterCurrentServiceStateType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The current service state. The value could be start/stop/restart/crashed." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDatapathResourceUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The CPU, memory, or disk usage percentage of the datapath on a NSX-T appliance. + The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDHCPPoolUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The usage of a DHCP pool. The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgeServiceNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of the service running on the Edge node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFailureReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The detailed reason of any module failure like BGP down, IKE down, etc." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterPreviousGatewayStateType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The previous gateway state. The value could be active/standby/admin down." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterPreviousServiceStateType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The previous service state. The value could be start/stop/restart/crashed." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSystemUsageThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The configured threshold value for the CPU, memory, or disk usage + percentage of an NSX-T appliance. The value is an integer between 0 and + 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterUsernameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of a user in an NSX-T appliance." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDHCPServerIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The UUID of a DHCP server." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterServiceNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of the service running in an NSX-T appliance." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterIntelligenceNodeIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The node ID of an NSX-T Intelligence node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterHostnameOrIPAddressWithPortType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Hostname or ip address with port of logging server." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEventIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The event identifier." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterActiveGlobalManagerType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The identifier for the active Global Manager node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterActiveGlobalManagersType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "A comma delimited list of identifiers for the active Global Manager nodes." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSessionDownReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Down reason of the IPsec VPN session." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterManagerNodeNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The display name of a NSX-T Manager node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTransportNodeAddressType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The IP address of a NSX-T Transport node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTransportNodeNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The display name of a NSX-T Transport node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterCentralControlPlaneIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The UUID of a NSX centrol control plane." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTunnelDownReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Down reason of the IPsec VPN tunnel." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterHeapTypeType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Heap type information for DFW memory usage like vsip-attr, vsip-flow, vsip-fqdni, etc." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterMempoolNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Name of a memory pool." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterPasswordExpirationDaysType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The number of days left before expiration of the password of an NSX-T + appliance user. The value is an integer greater than 0." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterBGPNeighborIPType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "IP address of BGP Neighbor. This could be either IPv4 or IPv6 address." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterLDAPServerType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name or IP address of a LDAP server." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterPeerAddressType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "IP address of BFD peer." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterMaxIDSEventsAllowedType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The maximum number of IDS events that are allowed in the system, anything beyond this + would be purged at regular intervals." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterStaticAddressType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "A Static IP address." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDuplicateIPAddressType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Duplicate IP address." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterCapacityDisplayNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Display name of type on capacity dashboard." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterCapacityUsageCountType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Current usage count of capacity usage type." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgeNICNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of the NIC whose link is down or which faced tx/rx ring buffer overflow." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterRxRingBufferOverflowPercentageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The NIC's receive descriptor ring buffer on a NSX-T Edge or Gateway node has no space left + to accomodate new incoming packets and there is a significant drop due to it. + The value is a float between 0 to 100 describing the overflow percentage due to the packet drops." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTxRingBufferOverflowPercentageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The NIC's transmit descriptor ring buffer on a NSX-T Edge or Gateway node has no space left + to accomodate new outgoing packets and there is a significant drop due to it. + The value is a float between 0 to 100 describing the overflow percentage due to the packet drops." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSrIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Service Router UUID." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterIDSEventsCountType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Count of the IDS events in the system currently." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterRemoteSiteNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Name of a remote site in federation. For more information on remote + sites and an overview of the federation feature, please refer to: + https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-D5B6DC79-6733-44A7-8072-50221CF2122A.html" + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterBGPSourceIPType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Source IP address of BGP session. This could be either an IPv4 address + in dotted-decimal format or an IPv6 address in IPv6 address format." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterRemoteSiteIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The identifier for a remote site." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSiteIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The identifier for a local site." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSiteNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Name of a local site in federation. For more information on local + sites and an overview of the federation feature, please refer to: + https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-D5B6DC79-6733-44A7-8072-50221CF2122A.html" + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterLrIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Logical Router UUID." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterRxMissesType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The number of packets missed while receiving due to rx ring buffer being full." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterRxProcessedType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The number of successful incoming packets while polling for rx buffer full event." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTxMissesType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The number of packets missed while transmitting due to tx ring buffer being full." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTxProcessedType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The number of successful outgoing packets while polling for tx buffer full event." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterLrportIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Logical Router Port UUID." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterServiceIPType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The IP configured for the service running in an NSX-T appliance in dotted-decimal format." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterRemoteManagerNodeIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The remote Manager node UUID." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDirectoryDomainType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of a directory domain." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTimeoutInMinutesType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Timeout value in minutes." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterMaxCapacityThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Maximum threshold defined for capacity usage type." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterMinCapacityThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Minimum threshold defined for capacity usage type." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterMaxSupportedCapacityCountType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Maximum supported count for capacity usage type." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterLatencySourceType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The source of reported latency." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterLatencyThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Threshold value of reported IO latency." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterLatencyValueType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Value of reported IO latency." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterApplianceFQDNType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The NSX appliance's fully qualified domain name." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterRemoteApplianceAddressType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The remote NSX appliance's IP address. The value is an IPv4 address." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterManagerNodeIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The Manager node UUID." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDisplayedLicenseKeyType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The last 5 characters of the license key of an NSX-T license." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgeThreadNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of the Edge node thread." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterIntentPathType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The policy intent path." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFirewallHalfopenFlowUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Current firewall TCP half-open connection usage percentage of max supported value. + The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFirewallICMPFlowUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Current firewall ICMP connection usage percentage of max supported value. + The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterServiceDownReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Reason service is down." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFirewallUDPFlowUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Current firewall UDP connection usage percentage of max supported value. + The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFirewallIPFlowUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Current firewall IP connection usage percentage of max supported value. + The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDNSIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The DNS forwarder identifier." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterDNSUpstreamIPType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "IP address of one DNS forwarder upstream server." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterCABundleAgeThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The age threshold in days for the CA bundle." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterAPICollectionPathType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The API path of the collection containing entity_id." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgeNodeSettingMismatchReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "String containing Policy/MP intent of Edge transport node settings + that differs from corresponding Edge transport node settings on Edge NSX CLI." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "String containing Policy/MP intent of Edge transport node vSphere + deployment configuration that differs from corresponding Edge transport node + configuration on vSphere." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFirewallSNATPortsUsageType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Current firewall SNAT ports usage percentage of max supported value. + The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgevSphereLocationMismatchReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "String containing Policy/MP intent of vSphere deployment configuration that differs + from corresponding Edge transport node configuration on vSphere when vMotion happens + for Edge node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "String containing Policy/MP intent of Edge transport node settings and vSphere + deployment configuration that differs from corresponding Edge transport node + settings on Edge NSX CLI and Edge transport node configuration on vSphere." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSNATIPAddressType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The SNAT IP address which ran out of port threshold." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNappClusterIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The cluster ID of the NSX Application Platform cluster." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNappMessagingLAGThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The configured threshold value for the number of pending messages + in an NSX Application Platform messaging topic." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNappNodeIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The node ID of an NSX Application Platform node." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNappServiceNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The service name of an NSX Application Platform service." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFlowIdentifierType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "A flow identifier indicating the direction of flow of data which is one of following. + - GM_2_LM + - LM_2_GM_NOTIFICATION + - LM_2_GM_ONBOARD_CONFIG" + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterSyncIssueReasonType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "A reason for data synchronization issue." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterQueueNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The name of the queue used to synchronize data between two sites." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterQueueSizeType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The occupancy size of queue used to synchronize data between two sites." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterQueueSizeThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Maximum threshold value of reported queue size." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterGroupTypeType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The group type of a GMLE cluster." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterManagerNodeIDSType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "A comma delimited list of identifiers for the Manager nodes." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterServiceRouterIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The ID of a service-router that is part of a tier0 or tier1 gateway + spanning one or more edges" + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterTransportNodeIdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The Transport node UUID." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterFromGMPathType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Policy path of the Global Manager." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterToGMPathType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Policy path of the Global Manager." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNICThroughputType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The NIC throughput, as a percentage. The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNICThroughputThresholdType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The NIC throughput threshold, as a percentage. The value is an integer between 0 and 100." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterEdgeCryptoDrvNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Name of the edge crypto driver." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwNsxTDataCenterNappNodeNameType ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "The node name of an NSX Application Platform node." + SYNTAX OCTET STRING (SIZE (0..256)) + +vmwNsxTDataCenterTimestamp OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The timestamp when the NSX-T Data Center event occurred." + ::= { vmwNsxTDataCenterData 1 } + +vmwNsxTDataCenterFeatureName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFeatureIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The NSX-T Data Center feature ID associated with the event." + ::= { vmwNsxTDataCenterData 2 } + +vmwNsxTDataCenterEventType OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEventTypeType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The name of the NSX-T Data Center event." + ::= { vmwNsxTDataCenterData 3 } + +vmwNsxTDataCenterEventSeverity OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSeverityType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The severity of the NSX-T Data Center event." + ::= { vmwNsxTDataCenterData 4 } + +vmwNsxTDataCenterNodeId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNodeIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The node ID from where a NSX-T Data Center event was emitted." + ::= { vmwNsxTDataCenterData 5 } + +vmwNsxTDataCenterNodeType OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNodeTypeType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The type of node from where a NSX-T Data Center event was emitted." + ::= { vmwNsxTDataCenterData 6 } + +vmwNsxTDataCenterEntityId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEntityIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The ID of a NSX-T Data Center entity an event pertains to. The event + description field provides additional details of the entity. For + example the ID can be for a specific Load Balancer rule as reported by + the NSX API GET /api/v1/loadbalancer/rules or a specific certificate + as reported by the NSX API GET /api/v1/trust-management/certificates." + ::= { vmwNsxTDataCenterData 21 } + +vmwNsxTDataCenterSystemResourceUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSystemResourceUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The CPU, memory, or disk usage percentage of an NSX-T appliance. The + value is an integer between 0 and 100." + ::= { vmwNsxTDataCenterData 22 } + +vmwNsxTDataCenterDiskPartitionName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDiskPartitionNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The name of a disk partition in an NSX-T appliance. For example, the + name for the /tmp partition is '/tmp'." + ::= { vmwNsxTDataCenterData 23 } + +vmwNsxTDataCenterLicenseEditionType OBJECT-TYPE + SYNTAX VmwNsxTDataCenterLicenseEditionTypeType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The edition type of an NSX-T license. For example, the type for an NSX-T + evaluation license is 'NSX Data Center Evaluation'." + ::= { vmwNsxTDataCenterData 24 } + +vmwNsxTDataCenterApplianceAddress OBJECT-TYPE + SYNTAX VmwNsxTDataCenterApplianceAddressType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The NSX appliance's IP address. The value is an IPv4 address." + ::= { vmwNsxTDataCenterData 25 } + +vmwNsxTDataCenterCurrentGatewayState OBJECT-TYPE + SYNTAX VmwNsxTDataCenterCurrentGatewayStateType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The current gateway state. The value could be active/standby/admin down." + ::= { vmwNsxTDataCenterData 26 } + +vmwNsxTDataCenterCurrentServiceState OBJECT-TYPE + SYNTAX VmwNsxTDataCenterCurrentServiceStateType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The current service state. The value could be start/stop/restart/crashed." + ::= { vmwNsxTDataCenterData 27 } + +vmwNsxTDataCenterDatapathResourceUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDatapathResourceUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The CPU, memory, or disk usage percentage of the datapath on a NSX-T appliance. + The value is an integer between 0 and 100." + ::= { vmwNsxTDataCenterData 28 } + +vmwNsxTDataCenterDHCPPoolUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDHCPPoolUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The usage of a DHCP pool. The value is an integer between 0 and 100." + ::= { vmwNsxTDataCenterData 29 } + +vmwNsxTDataCenterEdgeServiceName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgeServiceNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The name of the service running on the Edge node." + ::= { vmwNsxTDataCenterData 30 } + +vmwNsxTDataCenterFailureReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFailureReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The detailed reason of any module failure like BGP down, IKE down, etc." + ::= { vmwNsxTDataCenterData 31 } + +vmwNsxTDataCenterPreviousGatewayState OBJECT-TYPE + SYNTAX VmwNsxTDataCenterPreviousGatewayStateType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The previous gateway state. The value could be active/standby/admin down." + ::= { vmwNsxTDataCenterData 32 } + +vmwNsxTDataCenterPreviousServiceState OBJECT-TYPE + SYNTAX VmwNsxTDataCenterPreviousServiceStateType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The previous service state. The value could be start/stop/restart/crashed." + ::= { vmwNsxTDataCenterData 33 } + +vmwNsxTDataCenterSystemUsageThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSystemUsageThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The configured threshold value for the CPU, memory, or disk usage + percentage of an NSX-T appliance. The value is an integer between 0 and + 100." + ::= { vmwNsxTDataCenterData 34 } + +vmwNsxTDataCenterUsername OBJECT-TYPE + SYNTAX VmwNsxTDataCenterUsernameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The name of a user in an NSX-T appliance." + ::= { vmwNsxTDataCenterData 35 } + +vmwNsxTDataCenterDHCPServerId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDHCPServerIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The UUID of a DHCP server." + ::= { vmwNsxTDataCenterData 36 } + +vmwNsxTDataCenterServiceName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterServiceNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The name of the service running in an NSX-T appliance." + ::= { vmwNsxTDataCenterData 37 } + +vmwNsxTDataCenterIntelligenceNodeId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterIntelligenceNodeIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The node ID of an NSX-T Intelligence node." + ::= { vmwNsxTDataCenterData 38 } + +vmwNsxTDataCenterHostnameOrIPAddressWithPort OBJECT-TYPE + SYNTAX VmwNsxTDataCenterHostnameOrIPAddressWithPortType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 39 } + +vmwNsxTDataCenterEventId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEventIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The event identifier." + ::= { vmwNsxTDataCenterData 40 } + +vmwNsxTDataCenterActiveGlobalManager OBJECT-TYPE + SYNTAX VmwNsxTDataCenterActiveGlobalManagerType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 41 } + +vmwNsxTDataCenterActiveGlobalManagers OBJECT-TYPE + SYNTAX VmwNsxTDataCenterActiveGlobalManagersType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 42 } + +vmwNsxTDataCenterSessionDownReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSessionDownReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Down reason of the IPsec VPN session." + ::= { vmwNsxTDataCenterData 43 } + +vmwNsxTDataCenterManagerNodeName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterManagerNodeNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 44 } + +vmwNsxTDataCenterTransportNodeAddress OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTransportNodeAddressType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 45 } + +vmwNsxTDataCenterTransportNodeName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTransportNodeNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 46 } + +vmwNsxTDataCenterCentralControlPlaneId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterCentralControlPlaneIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 47 } + +vmwNsxTDataCenterTunnelDownReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTunnelDownReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Down reason of the IPsec VPN tunnel." + ::= { vmwNsxTDataCenterData 48 } + +vmwNsxTDataCenterHeapType OBJECT-TYPE + SYNTAX VmwNsxTDataCenterHeapTypeType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Heap type information for DFW memory usage like vsip-attr, vsip-flow, vsip-fqdni, etc." + ::= { vmwNsxTDataCenterData 49 } + +vmwNsxTDataCenterMempoolName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterMempoolNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Name of a memory pool." + ::= { vmwNsxTDataCenterData 50 } + +vmwNsxTDataCenterPasswordExpirationDays OBJECT-TYPE + SYNTAX VmwNsxTDataCenterPasswordExpirationDaysType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The number of days left before expiration of the password of an NSX-T + appliance user. The value is an integer greater than 0." + ::= { vmwNsxTDataCenterData 51 } + +vmwNsxTDataCenterBGPNeighborIP OBJECT-TYPE + SYNTAX VmwNsxTDataCenterBGPNeighborIPType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "IP address of BGP Neighbor. This could be either IPv4 or IPv6 address." + ::= { vmwNsxTDataCenterData 52 } + +vmwNsxTDataCenterLDAPServer OBJECT-TYPE + SYNTAX VmwNsxTDataCenterLDAPServerType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 53 } + +vmwNsxTDataCenterPeerAddress OBJECT-TYPE + SYNTAX VmwNsxTDataCenterPeerAddressType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "IP address of BFD peer." + ::= { vmwNsxTDataCenterData 54 } + +vmwNsxTDataCenterMaxIDSEventsAllowed OBJECT-TYPE + SYNTAX VmwNsxTDataCenterMaxIDSEventsAllowedType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 55 } + +vmwNsxTDataCenterStaticAddress OBJECT-TYPE + SYNTAX VmwNsxTDataCenterStaticAddressType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "A Static IP address." + ::= { vmwNsxTDataCenterData 56 } + +vmwNsxTDataCenterDuplicateIPAddress OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDuplicateIPAddressType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Duplicate IP address." + ::= { vmwNsxTDataCenterData 57 } + +vmwNsxTDataCenterCapacityDisplayName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterCapacityDisplayNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 58 } + +vmwNsxTDataCenterCapacityUsageCount OBJECT-TYPE + SYNTAX VmwNsxTDataCenterCapacityUsageCountType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 59 } + +vmwNsxTDataCenterEdgeNICName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgeNICNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The name of the NIC whose link is down or which faced tx/rx ring buffer overflow." + ::= { vmwNsxTDataCenterData 60 } + +vmwNsxTDataCenterRxRingBufferOverflowPercentage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterRxRingBufferOverflowPercentageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The NIC's receive descriptor ring buffer on a NSX-T Edge or Gateway node has no space left + to accomodate new incoming packets and there is a significant drop due to it. + The value is a float between 0 to 100 describing the overflow percentage due to the packet drops." + ::= { vmwNsxTDataCenterData 61 } + +vmwNsxTDataCenterTxRingBufferOverflowPercentage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTxRingBufferOverflowPercentageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The NIC's transmit descriptor ring buffer on a NSX-T Edge or Gateway node has no space left + to accomodate new outgoing packets and there is a significant drop due to it. + The value is a float between 0 to 100 describing the overflow percentage due to the packet drops." + ::= { vmwNsxTDataCenterData 62 } + +vmwNsxTDataCenterSrId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSrIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Service Router UUID." + ::= { vmwNsxTDataCenterData 63 } + +vmwNsxTDataCenterIDSEventsCount OBJECT-TYPE + SYNTAX VmwNsxTDataCenterIDSEventsCountType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 64 } + +vmwNsxTDataCenterRemoteSiteName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterRemoteSiteNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 65 } + +vmwNsxTDataCenterBGPSourceIP OBJECT-TYPE + SYNTAX VmwNsxTDataCenterBGPSourceIPType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 66 } + +vmwNsxTDataCenterRemoteSiteId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterRemoteSiteIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 67 } + +vmwNsxTDataCenterSiteId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSiteIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 68 } + +vmwNsxTDataCenterSiteName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSiteNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 69 } + +vmwNsxTDataCenterLrId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterLrIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 70 } + +vmwNsxTDataCenterRxMisses OBJECT-TYPE + SYNTAX VmwNsxTDataCenterRxMissesType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 71 } + +vmwNsxTDataCenterRxProcessed OBJECT-TYPE + SYNTAX VmwNsxTDataCenterRxProcessedType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 72 } + +vmwNsxTDataCenterTxMisses OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTxMissesType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 73 } + +vmwNsxTDataCenterTxProcessed OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTxProcessedType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 74 } + +vmwNsxTDataCenterLrportId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterLrportIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Logical Router Port UUID." + ::= { vmwNsxTDataCenterData 75 } + +vmwNsxTDataCenterServiceIP OBJECT-TYPE + SYNTAX VmwNsxTDataCenterServiceIPType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The Ip configured for the service running in an NSX-T appliance." + ::= { vmwNsxTDataCenterData 77 } + +vmwNsxTDataCenterRemoteManagerNodeId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterRemoteManagerNodeIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 80 } + +vmwNsxTDataCenterDirectoryDomain OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDirectoryDomainType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 81 } + +vmwNsxTDataCenterTimeoutInMinutes OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTimeoutInMinutesType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 82 } + +vmwNsxTDataCenterMaxCapacityThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterMaxCapacityThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 83 } + +vmwNsxTDataCenterMinCapacityThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterMinCapacityThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 84 } + +vmwNsxTDataCenterMaxSupportedCapacityCount OBJECT-TYPE + SYNTAX VmwNsxTDataCenterMaxSupportedCapacityCountType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 85 } + +vmwNsxTDataCenterLatencySource OBJECT-TYPE + SYNTAX VmwNsxTDataCenterLatencySourceType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 86 } + +vmwNsxTDataCenterLatencyThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterLatencyThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 87 } + +vmwNsxTDataCenterLatencyValue OBJECT-TYPE + SYNTAX VmwNsxTDataCenterLatencyValueType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 88 } + +vmwNsxTDataCenterApplianceFQDN OBJECT-TYPE + SYNTAX VmwNsxTDataCenterApplianceFQDNType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 89 } + +vmwNsxTDataCenterRemoteApplianceAddress OBJECT-TYPE + SYNTAX VmwNsxTDataCenterRemoteApplianceAddressType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 90 } + +vmwNsxTDataCenterManagerNodeId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterManagerNodeIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 91 } + +vmwNsxTDataCenterDisplayedLicenseKey OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDisplayedLicenseKeyType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 92 } + +vmwNsxTDataCenterEdgeThreadName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgeThreadNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 93 } + +vmwNsxTDataCenterIntentPath OBJECT-TYPE + SYNTAX VmwNsxTDataCenterIntentPathType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 94 } + +vmwNsxTDataCenterFirewallHalfopenFlowUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFirewallHalfopenFlowUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Firewall TCP half-open connection usage." + ::= { vmwNsxTDataCenterData 95 } + +vmwNsxTDataCenterFirewallICMPFlowUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFirewallICMPFlowUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Firewall ICMP connection usage." + ::= { vmwNsxTDataCenterData 96 } + +vmwNsxTDataCenterServiceDownReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterServiceDownReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 97 } + +vmwNsxTDataCenterFirewallUDPFlowUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFirewallUDPFlowUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Firewall UDP connection usage." + ::= { vmwNsxTDataCenterData 98 } + +vmwNsxTDataCenterFirewallIPFlowUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFirewallIPFlowUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Firewall IP connection usage." + ::= { vmwNsxTDataCenterData 99 } + +vmwNsxTDataCenterDNSId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDNSIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "DNS forwarder identifier." + ::= { vmwNsxTDataCenterData 100 } + +vmwNsxTDataCenterDNSUpstreamIP OBJECT-TYPE + SYNTAX VmwNsxTDataCenterDNSUpstreamIPType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "DNS forwarder upstream server IP address." + ::= { vmwNsxTDataCenterData 101 } + +vmwNsxTDataCenterCABundleAgeThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterCABundleAgeThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 121 } + +vmwNsxTDataCenterAPICollectionPath OBJECT-TYPE + SYNTAX VmwNsxTDataCenterAPICollectionPathType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 122 } + +vmwNsxTDataCenterEdgeNodeSettingMismatchReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgeNodeSettingMismatchReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 123 } + +vmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 124 } + +vmwNsxTDataCenterFirewallSNATPortsUsage OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFirewallSNATPortsUsageType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 125 } + +vmwNsxTDataCenterEdgevSphereLocationMismatchReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgevSphereLocationMismatchReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 126 } + +vmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 127 } + +vmwNsxTDataCenterSNATIPAddress OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSNATIPAddressType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 128 } + +vmwNsxTDataCenterNappClusterId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNappClusterIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 129 } + +vmwNsxTDataCenterNappMessagingLAGThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNappMessagingLAGThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 130 } + +vmwNsxTDataCenterNappNodeId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNappNodeIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 131 } + +vmwNsxTDataCenterNappServiceName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNappServiceNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 132 } + +vmwNsxTDataCenterFlowIdentifier OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFlowIdentifierType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 133 } + +vmwNsxTDataCenterSyncIssueReason OBJECT-TYPE + SYNTAX VmwNsxTDataCenterSyncIssueReasonType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 134 } + +vmwNsxTDataCenterQueueName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterQueueNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 135 } + +vmwNsxTDataCenterQueueSize OBJECT-TYPE + SYNTAX VmwNsxTDataCenterQueueSizeType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 136 } + +vmwNsxTDataCenterQueueSizeThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterQueueSizeThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 137 } + +vmwNsxTDataCenterGroupType OBJECT-TYPE + SYNTAX VmwNsxTDataCenterGroupTypeType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 138 } + +vmwNsxTDataCenterManagerNodeIDS OBJECT-TYPE + SYNTAX VmwNsxTDataCenterManagerNodeIDSType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 139 } + +vmwNsxTDataCenterServiceRouterId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterServiceRouterIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 140 } + +vmwNsxTDataCenterTransportNodeId OBJECT-TYPE + SYNTAX VmwNsxTDataCenterTransportNodeIdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 141 } + +vmwNsxTDataCenterFromGMPath OBJECT-TYPE + SYNTAX VmwNsxTDataCenterFromGMPathType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 142 } + +vmwNsxTDataCenterToGMPath OBJECT-TYPE + SYNTAX VmwNsxTDataCenterToGMPathType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 143 } + +vmwNsxTDataCenterNICThroughput OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNICThroughputType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 144 } + +vmwNsxTDataCenterNICThroughputThreshold OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNICThroughputThresholdType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 145 } + +vmwNsxTDataCenterEdgeCryptoDrvName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterEdgeCryptoDrvNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 146 } + +vmwNsxTDataCenterNappNodeName OBJECT-TYPE + SYNTAX VmwNsxTDataCenterNappNodeNameType + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This value is not expected to be empty." + ::= { vmwNsxTDataCenterData 147 } + +-- ********************************************************** +-- AlarmManagement feature event notifications +-- ********************************************************** + +vmwNsxTAlarmManagementFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the AlarmManagement feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 16 } + +vmwNsxTAlarmManagementFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for AlarmManagement feature notifications. + " + ::= { vmwNsxTAlarmManagementFeaturePrefix 0 } + +vmwNsxTAlarmManagementAlarmServiceOverloaded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Due to heavy volume of alarms reported, the alarm service is temporarily + overloaded. The NSX UI and GET /api/v1/alarms NSX API have stopped + reporting new alarms; however, syslog entries and SNMP traps (if enabled) + are still being emitted reporting the underlying event details. When the + underlying issues causing the heavy volume of alarms are addressed, the + alarm service will start reporting new alarms again. + + Action required: + Review all active alarms using the Alarms page in the NSX UI or using the + GET /api/v1/alarms?status=OPEN,ACKNOWLEDGED,SUPPRESSED NSX API. For each + active alarm investigate the root cause by following the recommended action + for the alarm. When sufficient alarms are resolved, the alarm service will + start reporting new alarms again. + " + ::= { vmwNsxTAlarmManagementFeature 1 } + +vmwNsxTAlarmManagementAlarmServiceOverloadedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The heavy volume of alarms has subsided and new alarms are being reported + again. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTAlarmManagementFeature 2 } + +vmwNsxTAlarmManagementHeavyVolumeOfAlarms NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEventId + } + STATUS current + DESCRIPTION + "Due to heavy volume of vmwNsxTDataCenterEventId alarms, the alarm service has + temporarily stopped reporting alarms of this type. The NSX UI and + GET /api/v1/alarms NSX API are not reporting new instances of these + alarms; however, syslog entries and SNMP traps (if enabled) are + still being emitted reporting the underlying event details. When the + underlying issues causing the heavy volume of vmwNsxTDataCenterEventId alarms are + addressed, the alarm service will start reporting new vmwNsxTDataCenterEventId + alarms when new issues are detected again. + + Action required: + Review all active alarms of type vmwNsxTDataCenterEventId using the + Alarms page in the NSX UI or using the NSX API GET + /api/v1/alarms?status=OPEN,ACKNOWLEDGED,SUPPRESSED. For each active + alarm investigate the root cause by following the recommended action + for the alarm. When sufficient alarms are resolved, the alarm service + will start reporting new vmwNsxTDataCenterEventId alarms again. + " + ::= { vmwNsxTAlarmManagementFeature 3 } + +vmwNsxTAlarmManagementHeavyVolumeOfAlarmsClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEventId + } + STATUS current + DESCRIPTION + "The heavy volume of vmwNsxTDataCenterEventId alarms has subsided and new alarms of + this type are being reported again. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTAlarmManagementFeature 4 } + +-- ********************************************************** +-- AuditLogHealth feature event notifications +-- ********************************************************** + +vmwNsxTAuditLogHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the AuditLogHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 24 } + +vmwNsxTAuditLogHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for AuditLogHealth feature notifications. + " + ::= { vmwNsxTAuditLogHealthFeaturePrefix 0 } + +vmwNsxTAuditLogHealthAuditLogFileUpdateError NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "At least one of the monitored log files has read-only permissions or has + incorrect user/group ownership or rsyslog.log is missing on Manager, + Global Manager, Edge or Public Cloud Gateway nodes. + + Action required: + 1. On all NSX appliances, for example Manager nodes, Edge nodes, etc., + ensure the permissions for the /var/log directory is 775 and the ownership + is root:syslog. + 2. On Manager and Global Manager nodes, ensure the file permissions + for auth.log, nsx-audit.log, nsx-audit-write.log, rsyslog.log and syslog + under /var/log is 640 and ownership is syslog:admin. + 3. On Edge and Public Cloud Gateway nodes, ensure the file permissions + for rsyslog.log and syslog under /var/log is 640 and ownership is syslog:admin. + 4. On ESXi host nodes, ensure the file permissions of auth.log, nsx-syslog.log + and syslog.log under /var/log is 755 and ownership is root:root. + 5. On KVM host nodes, ensure the file permissions of auth.log and syslog + under /var/log is 775 and ownership is root:syslog. + 6. If any of these files have incorrect permissions or ownership, invoke the + commands `chmod <mode> <path>` and `chown <user>:<group> <path>`. + 7. If rsyslog.log is missing on Manager, Global Manager, Edge or Public + Cloud Gateway nodes, invoke the NSX CLI command `restart service syslog` + which restarts the logging service and regenerates /var/log/rsyslog.log. + " + ::= { vmwNsxTAuditLogHealthFeature 1 } + +vmwNsxTAuditLogHealthAuditLogFileUpdateErrorClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "All monitored log files have the correct file permissions and ownership + and rsyslog.log exists on Manager, Global Manager, Edge or Public + Cloud Gateway nodes. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTAuditLogHealthFeature 2 } + +vmwNsxTAuditLogHealthRemoteLoggingServerError NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterHostnameOrIPAddressWithPort + } + STATUS current + DESCRIPTION + "Log messages to logging server vmwNsxTDataCenterHostnameOrIPAddressWithPort (vmwNsxTDataCenterEntityId) + cannot be delivered possibly due to an unresolvable FQDN, an invalid TLS + certificate or missing NSX appliance iptables rule. + + Action required: + 1. Ensure that vmwNsxTDataCenterHostnameOrIPAddressWithPort is the correct hostname or + IP address and port. + 2. If the logging server is specified using a FQDN, ensure the FQDN is resolvable + from the NSX appliance using the NSX CLI command `nslookup <fqdn>`. If not + resolvable, verify the correct FQDN is specified and the network DNS server has + the required entry for the FQDN. + 3. If the logging server is configured to use TLS, verify the specified certificate + is valid. For example, ensure the logging server is actually using the certificate + or verify the certificate has not expired using the openssl command + `openssl x509 -in <cert-file-path> -noout -dates`. + 4. NSX appliances use iptables rules to explicitly allow outgoing traffic. Verify + the iptables rule for the logging server is configured properly by invoking the + NSX CLI command `verify logging-servers` which re-configures logging server + iptables rules as needed. + 5. If for any reason the logging server is misconfigured, it should be deleted + using the NSX CLI `del logging-server <hostname-or-ip-address[:port]> + proto <proto> level <level>` command and re-added with the correct configuration. + " + ::= { vmwNsxTAuditLogHealthFeature 3 } + +vmwNsxTAuditLogHealthRemoteLoggingServerErrorClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterHostnameOrIPAddressWithPort + } + STATUS current + DESCRIPTION + "Configuration for logging server vmwNsxTDataCenterHostnameOrIPAddressWithPort (vmwNsxTDataCenterEntityId) + appear correct. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTAuditLogHealthFeature 4 } + +-- ********************************************************** +-- Capacity feature event notifications +-- ********************************************************** + +vmwNsxTCapacityFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Capacity feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 22 } + +vmwNsxTCapacityFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Capacity feature notifications. + " + ::= { vmwNsxTCapacityFeaturePrefix 0 } + +vmwNsxTCapacityMaximumCapacity NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCapacityDisplayName, + vmwNsxTDataCenterCapacityUsageCount, + vmwNsxTDataCenterMaxSupportedCapacityCount + } + STATUS current + DESCRIPTION + "The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has + reached vmwNsxTDataCenterCapacityUsageCount which is above the maximum supported + count of vmwNsxTDataCenterMaxSupportedCapacityCount. + + Action required: + Ensure that the number of NSX objects created is within the limits + supported by NSX. If there are any unused objects, delete them using the + respective NSX UI or API from the system. + Consider increasing the form factor of all Manager nodes and/or Edge + nodes. Note that the form factor of each node type should be the + same. If not the same, the capacity limits for the lowest form factor + deployed are used. + " + ::= { vmwNsxTCapacityFeature 1 } + +vmwNsxTCapacityMaximumCapacityClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCapacityDisplayName, + vmwNsxTDataCenterCapacityUsageCount, + vmwNsxTDataCenterMaxSupportedCapacityCount + } + STATUS current + DESCRIPTION + "The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has + reached vmwNsxTDataCenterCapacityUsageCount and is at or below the maximum supported count of + vmwNsxTDataCenterMaxSupportedCapacityCount. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCapacityFeature 2 } + +vmwNsxTCapacityMaximumCapacityThreshold NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCapacityDisplayName, + vmwNsxTDataCenterCapacityUsageCount, + vmwNsxTDataCenterMaxCapacityThreshold + } + STATUS current + DESCRIPTION + "The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has + reached vmwNsxTDataCenterCapacityUsageCount which is above the maximum capacity + threshold of vmwNsxTDataCenterMaxCapacityThreshold%. + + Action required: + Navigate to the capacity page in the NSX UI and review current usage versus + threshold limits. If the current usage is expected, consider increasing the + maximum threshold values. If the current usage is unexpected, review the + network policies configured to decrease usage at or below the maximum threshold. + " + ::= { vmwNsxTCapacityFeature 3 } + +vmwNsxTCapacityMaximumCapacityThresholdClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCapacityDisplayName, + vmwNsxTDataCenterCapacityUsageCount, + vmwNsxTDataCenterMaxCapacityThreshold + } + STATUS current + DESCRIPTION + "The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has + reached vmwNsxTDataCenterCapacityUsageCount and is at or below the maximum capacity threshold + of vmwNsxTDataCenterMaxCapacityThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCapacityFeature 4 } + +vmwNsxTCapacityMinimumCapacityThreshold NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCapacityDisplayName, + vmwNsxTDataCenterCapacityUsageCount, + vmwNsxTDataCenterMinCapacityThreshold + } + STATUS current + DESCRIPTION + "The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has + reached vmwNsxTDataCenterCapacityUsageCount which is above the minimum capacity + threshold of vmwNsxTDataCenterMinCapacityThreshold%. + + Action required: + Navigate to the capacity page in the NSX UI and review current usage versus + threshold limits. If the current usage is expected, consider increasing the + minimum threshold values. If the current usage is unexpected, review the + network policies configured to decrease usage at or below the minimum threshold. + " + ::= { vmwNsxTCapacityFeature 5 } + +vmwNsxTCapacityMinimumCapacityThresholdClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCapacityDisplayName, + vmwNsxTDataCenterCapacityUsageCount, + vmwNsxTDataCenterMinCapacityThreshold + } + STATUS current + DESCRIPTION + "The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has + reached vmwNsxTDataCenterCapacityUsageCount and is at or below the minimum capacity threshold + of vmwNsxTDataCenterMinCapacityThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCapacityFeature 6 } + +-- ********************************************************** +-- Certificates feature event notifications +-- ********************************************************** + +vmwNsxTCertificatesFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Certificates feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 3 } + +vmwNsxTCertificatesFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Certificates feature notifications. + " + ::= { vmwNsxTCertificatesFeaturePrefix 0 } + +vmwNsxTCertificatesCABundleUpdateRecommended NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCABundleAgeThreshold + } + STATUS current + DESCRIPTION + "The trusted CA bundle vmwNsxTDataCenterEntityId was updated more than + vmwNsxTDataCenterCABundleAgeThreshold days ago. + Update for the trusted CA bundle is recommended. + + Action required: + Ensure services that are currently using the trusted CA bundle are updated + to use a recently-updated trusted CA bundle. Unless it is system-provided + bundle, the bundle can be updated using the + PUT /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. + Once the expired bundle is no longer in use, it should be deleted (if not + system-provided) by invoking the + DELETE /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. + " + ::= { vmwNsxTCertificatesFeature 7 } + +vmwNsxTCertificatesCABundleUpdateRecommendedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The trusted CA bundle vmwNsxTDataCenterEntityId has been removed, updated, or is no longer + in use. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCertificatesFeature 8 } + +vmwNsxTCertificatesCABundleUpdateSuggested NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCABundleAgeThreshold + } + STATUS current + DESCRIPTION + "The trusted CA bundle vmwNsxTDataCenterEntityId was updated more than + vmwNsxTDataCenterCABundleAgeThreshold days ago. + Update for the trusted CA bundle is suggested. + + Action required: + Ensure services that are currently using the trusted CA bundle are updated + to use a recently-updated trusted CA bundle. Unless it is system-provided + bundle, the bundle can be updated using the + PUT /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. + Once the expired bundle is no longer in use, it should be deleted (if not + system-provided) by invoking the + DELETE /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. + " + ::= { vmwNsxTCertificatesFeature 9 } + +vmwNsxTCertificatesCABundleUpdateSuggestedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The trusted CA bundle vmwNsxTDataCenterEntityId has been removed, updated, or is no longer + in use. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCertificatesFeature 10 } + +vmwNsxTCertificatesCertificateExpirationApproaching NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterAPICollectionPath + } + STATUS current + DESCRIPTION + "Certificate vmwNsxTDataCenterEntityId is approaching expiration. + + Action required: + Ensure services that are currently using the certificate are updated + to use a new, non-expiring certificate. Once the expiring + certificate is no longer in use, it should be deleted by invoking the + DELETE vmwNsxTDataCenterAPICollectionPathvmwNsxTDataCenterEntityId NSX API. + " + ::= { vmwNsxTCertificatesFeature 1 } + +vmwNsxTCertificatesCertificateExpirationApproachingClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The expiring certificate vmwNsxTDataCenterEntityId has been removed or is no longer + approaching expiration. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCertificatesFeature 2 } + +vmwNsxTCertificatesCertificateExpired NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterAPICollectionPath + } + STATUS current + DESCRIPTION + "Certificate vmwNsxTDataCenterEntityId has expired. + + Action required: + Ensure services that are currently using the certificate are updated + to use a new, non-expired certificate. Once the expired + certificate is no longer in use, it should be deleted by invoking the + DELETE vmwNsxTDataCenterAPICollectionPathvmwNsxTDataCenterEntityId NSX API. + If the expired certificate is used by NAPP Platform, + the connection is broken between NSX and NAPP Platform. + Please check the NAPP Platform troubleshooting document + to use a self-signed NAPP CA certificate for recovering the connection. + " + ::= { vmwNsxTCertificatesFeature 3 } + +vmwNsxTCertificatesCertificateExpiredClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The expired certificate vmwNsxTDataCenterEntityId has been removed or is no longer + expired. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCertificatesFeature 4 } + +vmwNsxTCertificatesCertificateIsAboutToExpire NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterAPICollectionPath + } + STATUS current + DESCRIPTION + "Certificate vmwNsxTDataCenterEntityId is about to expire. + + Action required: + Ensure services that are currently using the certificate are updated + to use a new, non-expiring certificate. Once the expiring + certificate is no longer in use, it should be deleted by invoking the + DELETE vmwNsxTDataCenterAPICollectionPathvmwNsxTDataCenterEntityId NSX API. + " + ::= { vmwNsxTCertificatesFeature 5 } + +vmwNsxTCertificatesCertificateIsAboutToExpireClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The expiring certificate vmwNsxTDataCenterEntityId has been removed or is no longer + about to expire. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCertificatesFeature 6 } + +-- ********************************************************** +-- Clustering feature event notifications +-- ********************************************************** + +vmwNsxTClusteringFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Clustering feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 40 } + +vmwNsxTClusteringFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Clustering feature notifications. + " + ::= { vmwNsxTClusteringFeaturePrefix 0 } + +vmwNsxTClusteringClusterDegraded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterGroupType + } + STATUS current + DESCRIPTION + "Group member vmwNsxTDataCenterManagerNodeId of service vmwNsxTDataCenterGroupType is down. + + Action required: + 1. Invoke the NSX CLI command 'get cluster status' to view the status + of group members of the cluster. + 2. Ensure the service for vmwNsxTDataCenterGroupType is running on node. Invoke the GET + /api/v1/node/services/<service_name>/status NSX API or the + `get service <service_name>` NSX CLI command to determine if the service is running. + If not running, invoke the POST /api/v1/node/services/<service_name>?action=restart NSX API or + the `restart service <service_name>` NSX CLI to restart the service. + 3. Check /var/log/ of service vmwNsxTDataCenterGroupType to see if there are errors reported. + " + ::= { vmwNsxTClusteringFeature 1 } + +vmwNsxTClusteringClusterDegradedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterGroupType + } + STATUS current + DESCRIPTION + "Group member vmwNsxTDataCenterManagerNodeId of vmwNsxTDataCenterGroupType is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTClusteringFeature 2 } + +vmwNsxTClusteringClusterUnavailable NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeIDS, + vmwNsxTDataCenterGroupType + } + STATUS current + DESCRIPTION + "All group members vmwNsxTDataCenterManagerNodeIDS of service vmwNsxTDataCenterGroupType are down. + + Action required: + 1. Ensure the service for vmwNsxTDataCenterGroupType is running on node. Invoke the GET + /api/v1/node/services/<service_name>/status NSX API or the + `get service <service_name>` NSX CLI command to determine if the service is running. + If not running, invoke the POST /api/v1/node/services/<service_name>?action=restart NSX API or + the `restart service <service_name>` NSX CLI to restart the service. + 2. Check /var/log/ of service vmwNsxTDataCenterGroupType to see if there are errors reported. + " + ::= { vmwNsxTClusteringFeature 3 } + +vmwNsxTClusteringClusterUnavailableClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeIDS, + vmwNsxTDataCenterGroupType + } + STATUS current + DESCRIPTION + "All group members vmwNsxTDataCenterManagerNodeIDS of service vmwNsxTDataCenterGroupType are up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTClusteringFeature 4 } + +-- ********************************************************** +-- CniHealth feature event notifications +-- ********************************************************** + +vmwNsxTCniHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the CniHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 10 } + +vmwNsxTCniHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for CniHealth feature notifications. + " + ::= { vmwNsxTCniHealthFeaturePrefix 0 } + +vmwNsxTCniHealthHyperbusManagerConnectionDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Hyperbus cannot communicate with the Manager node. + + Action required: + The hyperbus vmkernel interface (vmk50) may be missing. Please refer to + Knowledge Base article https://kb.vmware.com/s/article/67432. + " + ::= { vmwNsxTCniHealthFeature 3 } + +vmwNsxTCniHealthHyperbusManagerConnectionDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Hyperbus can communicate with the Manager node. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCniHealthFeature 4 } + +-- ********************************************************** +-- Communication feature event notifications +-- ********************************************************** + +vmwNsxTCommunicationFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Communication feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 35 } + +vmwNsxTCommunicationFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Communication feature notifications. + " + ::= { vmwNsxTCommunicationFeaturePrefix 0 } + +vmwNsxTCommunicationControlChannelToManagerNodeDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceAddress, + vmwNsxTDataCenterTimeoutInMinutes + } + STATUS current + DESCRIPTION + "The Transport node vmwNsxTDataCenterEntityId control plane connection to Manager node vmwNsxTDataCenterApplianceAddress is + down for at least vmwNsxTDataCenterTimeoutInMinutes minutes from the Transport node's point of view. + + Action required: + 1. Check the connectivity from Transport node vmwNsxTDataCenterEntityId to Manager node vmwNsxTDataCenterApplianceAddress + interface via ping. If they are not pingable, check for flakiness in network connectivity. + 2. Check to see if the TCP connections are established using the netstat output to see if the + Controller service on the Manager node vmwNsxTDataCenterApplianceAddress is listening for connections on port + 1235. If not, check firewall (or) iptables rules to see if port 1235 is blocking Transport node + vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in + the underlay are blocking the required IP ports between Manager nodes and Transport nodes. + This is documented in our ports and protocols tool which is here: https://ports.vmware.com/. + 3. It is possible that the Transport node vmwNsxTDataCenterEntityId may still be in maintenance mode. + You can check whether the Transport node is in maintenance mode via the following API: + GET https://<nsx-mgr>/api/v1/transport-nodes/<tn-uuid> + When maintenance mode is set, the Transport node will not be connected to the Controller + service. This is usually the case when host upgrade is in progress. Wait for a few minutes and + check connectivity again. + Note: Please note that this alarm is not critical and should be resolved. GSS need not be + contacted for the notification of this alarm unless the alarm remains unresolved over an + extended period of time. + " + ::= { vmwNsxTCommunicationFeature 7 } + +vmwNsxTCommunicationControlChannelToManagerNodeDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "The Transport node vmwNsxTDataCenterEntityId restores the control plane connection to Manager node + vmwNsxTDataCenterApplianceAddress. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 8 } + +vmwNsxTCommunicationControlChannelToManagerNodeDownTooLong NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceAddress, + vmwNsxTDataCenterTimeoutInMinutes + } + STATUS current + DESCRIPTION + "The Transport node vmwNsxTDataCenterEntityId control plane connection to Manager node vmwNsxTDataCenterApplianceAddress is + down for at least vmwNsxTDataCenterTimeoutInMinutes minutes from the Transport node's point of view. + + Action required: + 1. Check the connectivity from Transport node vmwNsxTDataCenterEntityId to Manager node vmwNsxTDataCenterApplianceAddress + interface via ping. If they are not pingable, check for flakiness in network connectivity. + 2. Check to see if the TCP connections are established using the netstat output to see if the + Controller service on the Manager node vmwNsxTDataCenterApplianceAddress is listening for connections on port + 1235. If not, check firewall (or) iptables rules to see if port 1235 is blocking Transport node + vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in + the underlay are blocking the required IP ports between Manager nodes and Transport nodes. + This is documented in our ports and protocols tool which is here: https://ports.vmware.com/. + 3. It is possible that the Transport node vmwNsxTDataCenterEntityId may still be in maintenance mode. + You can check whether the Transport node is in maintenance mode via the following API: + GET https://<nsx-mgr>/api/v1/transport-nodes/<tn-uuid>. + When maintenance mode is set, the Transport node will not be connected to the Controller + service. This is usually the case when host upgrade is in progress. Wait for a few minutes and + check connectivity again. + " + ::= { vmwNsxTCommunicationFeature 9 } + +vmwNsxTCommunicationControlChannelToManagerNodeDownTooLongClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "The Transport node vmwNsxTDataCenterEntityId restores the control plane connection to Manager node + vmwNsxTDataCenterApplianceAddress. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 10 } + +vmwNsxTCommunicationControlChannelToTransportNodeDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCentralControlPlaneId + } + STATUS current + DESCRIPTION + "Controller service vmwNsxTDataCenterCentralControlPlaneId to Transport node vmwNsxTDataCenterEntityId down for at + least three minutes from Controller service's point of view. + + Action required: + 1. Check the connectivity from the Controller service vmwNsxTDataCenterCentralControlPlaneId and + Transport node vmwNsxTDataCenterEntityId. interface via ping. If they are not pingable, check for flakiness in + network connectivity. + 2. Check to see if the TCP connections are established using the netstat output to see if the + Controller service vmwNsxTDataCenterCentralControlPlaneId is listening for connections on port + 1235. If not, check firewall (or) iptables rules to see if port 1235 is blocking Transport node + vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in + the underlay are blocking the required IP ports between Manager nodes and Transport nodes. + This is documented in our ports and protocols tool which is here: https://ports.vmware.com/. + 3. It is possible that the Transport node vmwNsxTDataCenterEntityId may still be in maintenance mode. + You can check whether the Transport node is in maintenance mode via the following API: + GET https://<nsx-mgr>/api/v1/transport-nodes/<tn-uuid> + When maintenance mode is set, the Transport node will not be connected to the Controller + service. This is usually the case when host upgrade is in progress. Wait for a few minutes and + check connectivity again. + Note: Please note that this alarm is not critical and should be resolved. GSS need not be + contacted for the notification of this alarm unless the alarm remains unresolved over an + extended period of time. + " + ::= { vmwNsxTCommunicationFeature 11 } + +vmwNsxTCommunicationControlChannelToTransportNodeDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCentralControlPlaneId + } + STATUS current + DESCRIPTION + "Controller service vmwNsxTDataCenterCentralControlPlaneId restores connection to Transport node vmwNsxTDataCenterEntityId. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 12 } + +vmwNsxTCommunicationControlChannelToTransportNodeDownLong NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCentralControlPlaneId + } + STATUS current + DESCRIPTION + "Controller service vmwNsxTDataCenterCentralControlPlaneId to Transport node vmwNsxTDataCenterEntityId down for at + least 15 minutes from Controller service's point of view. + + Action required: + 1. Check the connectivity from the Controller service vmwNsxTDataCenterCentralControlPlaneId and + Transport node vmwNsxTDataCenterEntityId. interface via ping. If they are not pingable, check for flakiness in + network connectivity. + 2. Check to see if the TCP connections are established using the netstat output to see if the + Controller service vmwNsxTDataCenterCentralControlPlaneId is listening for connections on port + 1235. If not, check firewall (or) iptables rules to see if port 1235 is blocking Transport node + vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in + the underlay are blocking the required IP ports between Manager nodes and Transport nodes. + This is documented in our ports and protocols tool which is here: https://ports.vmware.com/. + 3. It is possible that the Transport node vmwNsxTDataCenterEntityId may still be in maintenance mode. + You can check whether the Transport node is in maintenance mode via the following API: + GET https://<nsx-mgr>/api/v1/transport-nodes/<tn-uuid> + When maintenance mode is set, the Transport node will not be connected to the Controller + service. This is usually the case when host upgrade is in progress. Wait for a few minutes and + check connectivity again. + " + ::= { vmwNsxTCommunicationFeature 19 } + +vmwNsxTCommunicationControlChannelToTransportNodeDownLongClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterCentralControlPlaneId + } + STATUS current + DESCRIPTION + "Controller service vmwNsxTDataCenterCentralControlPlaneId restores connection to Transport node vmwNsxTDataCenterEntityId. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 20 } + +vmwNsxTCommunicationManagementChannelToManagerNodeDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterApplianceAddress, + vmwNsxTDataCenterTransportNodeId + } + STATUS current + DESCRIPTION + "Management channel to Manager Node vmwNsxTDataCenterManagerNodeId + (vmwNsxTDataCenterApplianceAddress) is down for 5 minutes. + + Action required: + Ensure there is network connectivity between the + Transport node vmwNsxTDataCenterTransportNodeId + and master Manager node. Also ensure no firewalls are blocking traffic + between the nodes. Ensure the messaging manager service is running on + Manager nodes by invoking the command `/etc/init.d/messaging-manager status`. + If the messaging manager is not running, restart it by + invoking the command `/etc/init.d/messaging-manager restart`. + " + ::= { vmwNsxTCommunicationFeature 13 } + +vmwNsxTCommunicationManagementChannelToManagerNodeDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "Management channel to Manager Node vmwNsxTDataCenterManagerNodeId + (vmwNsxTDataCenterApplianceAddress) is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 14 } + +vmwNsxTCommunicationManagementChannelToManagerNodeDownLong NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterApplianceAddress, + vmwNsxTDataCenterTransportNodeId + } + STATUS current + DESCRIPTION + "Management channel to Manager Node vmwNsxTDataCenterManagerNodeId + (vmwNsxTDataCenterApplianceAddress) is down for 15 minutes. + + Action required: + Ensure there is network connectivity between the + Transport node vmwNsxTDataCenterTransportNodeId + and master Manager nodes. Also ensure no firewalls are blocking traffic + between the nodes. Ensure the messaging manager service is running on + Manager nodes by invoking the command `/etc/init.d/messaging-manager status`. + If the messaging manager is not running, restart it by + invoking the command `/etc/init.d/messaging-manager restart`. + " + ::= { vmwNsxTCommunicationFeature 25 } + +vmwNsxTCommunicationManagementChannelToManagerNodeDownLongClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "Management channel to Manager Node vmwNsxTDataCenterManagerNodeId + (vmwNsxTDataCenterApplianceAddress) is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 26 } + +vmwNsxTCommunicationManagementChannelToTransportNodeDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName, + vmwNsxTDataCenterTransportNodeAddress + } + STATUS current + DESCRIPTION + "Management channel to Transport Node vmwNsxTDataCenterTransportNodeName + (vmwNsxTDataCenterTransportNodeAddress) is down for 5 minutes. + + Action required: + Ensure there is network connectivity between the Manager nodes + and Transport node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) + and no firewalls are blocking traffic between the nodes. + On Windows Transport nodes, ensure the nsx-proxy service is running on the + Transport node by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 status` + in the Windows PowerShell. If it is not running, restart it by + invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 restart`. + On all other Transport nodes, ensure the nsx-proxy service is running on the + Transport node by invoking the command `/etc/init.d/nsx-proxy status`. + If it is not running, restart it by invoking the command + `/etc/init.d/nsx-proxy restart`. + " + ::= { vmwNsxTCommunicationFeature 1 } + +vmwNsxTCommunicationManagementChannelToTransportNodeDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName, + vmwNsxTDataCenterTransportNodeAddress + } + STATUS current + DESCRIPTION + "Management channel to Transport Node vmwNsxTDataCenterTransportNodeName + (vmwNsxTDataCenterTransportNodeAddress) is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 2 } + +vmwNsxTCommunicationManagementChannelToTransportNodeDownLg NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName, + vmwNsxTDataCenterTransportNodeAddress + } + STATUS current + DESCRIPTION + "Management channel to Transport Node vmwNsxTDataCenterTransportNodeName + (vmwNsxTDataCenterTransportNodeAddress) is down for 15 minutes. + + Action required: + Ensure there is network connectivity between the Manager nodes + and Transport node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) + and no firewalls are blocking traffic between the nodes. + On Windows Transport nodes, ensure the nsx-proxy service is running on the + Transport node by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 status` + in the Windows PowerShell. If it is not running, restart it by + invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 restart`. + On all other Transport nodes, ensure the nsx-proxy service is running on the + Transport node by invoking the command `/etc/init.d/nsx-proxy status`. + If it is not running, restart it by invoking the command + `/etc/init.d/nsx-proxy restart`. + " + ::= { vmwNsxTCommunicationFeature 5 } + +vmwNsxTCommunicationManagementChannelToTransportNodeDownLgClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName, + vmwNsxTDataCenterTransportNodeAddress + } + STATUS current + DESCRIPTION + "Management channel to Transport Node vmwNsxTDataCenterTransportNodeName + (vmwNsxTDataCenterTransportNodeAddress) is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 6 } + +vmwNsxTCommunicationManagerClusterLatencyHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterApplianceAddress, + vmwNsxTDataCenterRemoteManagerNodeId, + vmwNsxTDataCenterRemoteApplianceAddress + } + STATUS current + DESCRIPTION + "The average network latency between Manager nodes vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) + and vmwNsxTDataCenterRemoteManagerNodeId (vmwNsxTDataCenterRemoteApplianceAddress) is more than 10ms for the last 5 minutes. + + Action required: + Ensure there are no firewall rules blocking ping traffic between the Manager nodes. + If there are other high bandwidth servers and applications sharing the local network, + consider moving these to a different network. + " + ::= { vmwNsxTCommunicationFeature 17 } + +vmwNsxTCommunicationManagerClusterLatencyHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterApplianceAddress, + vmwNsxTDataCenterRemoteManagerNodeId, + vmwNsxTDataCenterRemoteApplianceAddress + } + STATUS current + DESCRIPTION + "The average network latency between Manager nodes vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) + and vmwNsxTDataCenterRemoteManagerNodeId (vmwNsxTDataCenterRemoteApplianceAddress) is within 10ms. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 18 } + +vmwNsxTCommunicationManagerControlChannelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeName, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "The communication between the management function and the control + function has failed on Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterApplianceAddress). + + Action required: + 1. On Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterApplianceAddress), please invoke the + following NSX CLI command: `get service applianceproxy` to check the status + of the service periodically for 60 minutes. + + 2. If the service is not running for more than 60 minutes, invoke + the following NSX CLI command: `restart service applianceproxy` and recheck the + status. If the service is still down, please contact VMware support. + " + ::= { vmwNsxTCommunicationFeature 3 } + +vmwNsxTCommunicationManagerControlChannelDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterManagerNodeName, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "The communication between the management function and the control function + has been restored on Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterApplianceAddress). + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 4 } + +vmwNsxTCommunicationManagerFQDNLookupFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceFQDN + } + STATUS current + DESCRIPTION + "DNS lookup failed for Manager node vmwNsxTDataCenterEntityId with FQDN + vmwNsxTDataCenterApplianceFQDN and the publish_fqdns flag was set. + + Action required: + 1. Assign correct FQDNs to all Manager nodes and verify the DNS + configuration is correct for successful lookup of all Manager + nodes' FQDNs. + 2. Alternatively, disable the use of FQDNs by invoking the NSX API + PUT /api/v1/configs/management with publish_fqdns set to false in the + request body. After that calls from Transport nodes and from Federation + to Manager nodes in this cluster will use only IP addresses. + " + ::= { vmwNsxTCommunicationFeature 21 } + +vmwNsxTCommunicationManagerFQDNLookupFailureClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceFQDN + } + STATUS current + DESCRIPTION + "FQDN lookup succeeded for Manager node vmwNsxTDataCenterEntityId with FQDN + vmwNsxTDataCenterApplianceFQDN or the publish_fqdns flag was cleared. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 22 } + +vmwNsxTCommunicationManagerFQDNReverseLookupFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "Reverse DNS lookup failed for Manager node vmwNsxTDataCenterEntityId with IP address + vmwNsxTDataCenterApplianceAddress and the publish_fqdns flag was set. + + Action required: + 1. Assign correct FQDNs to all Manager nodes and verify the DNS + configuration is correct for successful reverse lookup of the Manager + node's IP address. + 2. Alternatively, disable the use of FQDNs by invoking the NSX API + PUT /api/v1/configs/management with publish_fqdns set to false in the + request body. After that calls from Transport nodes and from Federation + to Manager nodes in this cluster will use only IP addresses. + " + ::= { vmwNsxTCommunicationFeature 23 } + +vmwNsxTCommunicationManagerFQDNReverseLookupFailureClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterApplianceAddress + } + STATUS current + DESCRIPTION + "Reverse DNS lookup succeeded for Manager node vmwNsxTDataCenterEntityId with IP address + vmwNsxTDataCenterApplianceAddress or the publish_fqdns flag was cleared. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTCommunicationFeature 24 } + +-- ********************************************************** +-- DHCP feature event notifications +-- ********************************************************** + +vmwNsxTDHCPFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the DHCP feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 20 } + +vmwNsxTDHCPFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for DHCP feature notifications. + " + ::= { vmwNsxTDHCPFeaturePrefix 0 } + +vmwNsxTDHCPPoolLeaseAllocationFailed NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDHCPServerId + } + STATUS current + DESCRIPTION + "The addresses in IP Pool vmwNsxTDataCenterEntityId of DHCP Server vmwNsxTDataCenterDHCPServerId have + been exhausted. The last DHCP request has failed and future requests will + fail. + + Action required: + Review the DHCP pool configuration in the NSX UI or on the Edge node where + the DHCP server is running by invoking the NSX CLI command `get dhcp ip-pool`. + Also review the current active leases on the Edge node by invoking the NSX + CLI command `get dhcp lease`. Compare the leases to the number of active + VMs. Consider reducing the lease time on the DHCP server configuration if + the number of VMs are low compared to the number of active leases. Also + consider expanding the pool range for the DHCP server by visiting the + Networking | Segments | Segment page in the NSX UI. + " + ::= { vmwNsxTDHCPFeature 1 } + +vmwNsxTDHCPPoolLeaseAllocationFailedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDHCPServerId + } + STATUS current + DESCRIPTION + "IP Pool vmwNsxTDataCenterEntityId of DHCP Server vmwNsxTDataCenterDHCPServerId is no longer exhausted. + A lease is successfully allocated to the last DHCP request. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDHCPFeature 2 } + +vmwNsxTDHCPPoolOverloaded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDHCPServerId, + vmwNsxTDataCenterDHCPPoolUsage + } + STATUS current + DESCRIPTION + "The DHCP Server vmwNsxTDataCenterDHCPServerId IP Pool vmwNsxTDataCenterEntityId usage is approaching + exhaustion with vmwNsxTDataCenterDHCPPoolUsage% IPs allocated. + + Action required: + Review the DHCP pool configuration in the NSX UI or on the Edge node where + the DHCP server is running by invoking the NSX CLI command `get dhcp ip-pool`. + Also review the current active leases on the Edge node by invoking the NSX + CLI command `get dhcp lease`. Compare the leases to the number of active + VMs. Consider reducing the lease time on the DHCP server configuration if + the number of VMs are low compared to the number of active leases. Also + consider expanding the pool range for the DHCP server by visiting the + Networking | Segments | Segment page in the NSX UI. + " + ::= { vmwNsxTDHCPFeature 3 } + +vmwNsxTDHCPPoolOverloadedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDHCPServerId + } + STATUS current + DESCRIPTION + "The DHCP Server vmwNsxTDataCenterDHCPServerId IP Pool vmwNsxTDataCenterEntityId has fallen below the + high usage threshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDHCPFeature 4 } + +-- ********************************************************** +-- DistributedFirewall feature event notifications +-- ********************************************************** + +vmwNsxTDistributedFirewallFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the DistributedFirewall feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 31 } + +vmwNsxTDistributedFirewallFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for DistributedFirewall feature notifications. + " + ::= { vmwNsxTDistributedFirewallFeaturePrefix 0 } + +vmwNsxTDistributedFirewallDFWCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The DFW CPU usage on Transport node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Consider re-balancing the VM workloads on this host to other hosts. Please + review the security design for optimization. For example, use the apply-to + configuration if the rules are not applicable to the entire datacenter. + " + ::= { vmwNsxTDistributedFirewallFeature 1 } + +vmwNsxTDistributedFirewallDFWCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The DFW CPU usage on Transport node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedFirewallFeature 2 } + +vmwNsxTDistributedFirewallDFWMemoryUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterHeapType, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The DFW Memory usage vmwNsxTDataCenterHeapType on Transport node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which + is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + View the current DFW memory usage by invoking the NSX CLI command + `get firewall thresholds` on the host. Consider re-balancing the + workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedFirewallFeature 3 } + +vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterHeapType, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The DFW Memory usage vmwNsxTDataCenterHeapType on Transport node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which + is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedFirewallFeature 4 } + +vmwNsxTDistributedFirewallDFWSessionCountHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The DFW session count is high on Transport node vmwNsxTDataCenterEntityId, it has + reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Review the network traffic load level of the workloads on the host. + Consider re-balancing the workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedFirewallFeature 5 } + +vmwNsxTDistributedFirewallDFWSessionCountHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The DFW session count on Transport node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the the threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedFirewallFeature 6 } + +vmwNsxTDistributedFirewallDFWVmotionFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName + } + STATUS current + DESCRIPTION + "The DFW vMotion for DFW filter vmwNsxTDataCenterEntityId on destination host + vmwNsxTDataCenterTransportNodeName has failed and the port for the entity has been + disconnected. + + Action required: + Check VMs on the host in NSX Manager, manually repush the DFW configuration + through NSX Manager UI. The DFW policy to be repushed can be traced by the + DFW filter vmwNsxTDataCenterEntityId. Also consider finding the VM to which the DFW filter + is attached and restart it. + " + ::= { vmwNsxTDistributedFirewallFeature 7 } + +vmwNsxTDistributedFirewallDFWVmotionFailureClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName + } + STATUS current + DESCRIPTION + "The DFW configuration for DFW filter vmwNsxTDataCenterEntityId on the destination host + vmwNsxTDataCenterTransportNodeName has succeeded and error caused by DFW vMotion failure + cleared. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedFirewallFeature 8 } + +-- ********************************************************** +-- DistributedIDSIPS feature event notifications +-- ********************************************************** + +vmwNsxTDistributedIDSIPSFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the DistributedIDSIPS feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 33 } + +vmwNsxTDistributedIDSIPSFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for DistributedIDSIPS feature notifications. + " + ::= { vmwNsxTDistributedIDSIPSFeaturePrefix 0 } + +vmwNsxTDistributedIDSIPSMaxEventsReached NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIDSEventsCount, + vmwNsxTDataCenterMaxIDSEventsAllowed + } + STATUS current + DESCRIPTION + "The number of intrusion events in the system is vmwNsxTDataCenterIDSEventsCount + which is higher than the maximum allowed value vmwNsxTDataCenterMaxIDSEventsAllowed. + + Action required: + There is no manual intervention required. A purge job will kick in automatically + every 3 minutes and delete 10% of the older records to bring the total intrusion events + count in the system to below the threshold value of 1.5 million events. + " + ::= { vmwNsxTDistributedIDSIPSFeature 3 } + +vmwNsxTDistributedIDSIPSMaxEventsReachedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIDSEventsCount, + vmwNsxTDataCenterMaxIDSEventsAllowed + } + STATUS current + DESCRIPTION + "The number of intrusion events in the system is vmwNsxTDataCenterIDSEventsCount + which is below the maximum allowed value vmwNsxTDataCenterMaxIDSEventsAllowed. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 4 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine CPU usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is at or above the high + threshold value of 75%. + + Action required: + Consider re-balancing the VM workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedIDSIPSFeature 7 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine CPU usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is below the high + threshold value of 75%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 8 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine CPU usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is at or above the medium + high threshold value of 85%. + + Action required: + Consider re-balancing the VM workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedIDSIPSFeature 21 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine CPU usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is below the medium high + threshold value of 85%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 22 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine CPU usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is at or above the very + high threshold value of 95%. + + Action required: + Consider re-balancing the VM workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedIDSIPSFeature 9 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine CPU usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is below the very + high threshold value of 95%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 10 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "NSX IDPS is enabled via NSX policy and IDPS rules are configured, but + NSX-IDPS engine is down. + + Action required: + 1. Check /var/log/nsx-syslog.log to see if there are errors reported. + 2. Invoke the NSX CLI command `get ids engine status` to check + if NSX Distributed IDPS is in disabled state. If so, + invoke `/etc/init.d/nsx-idps start` to start the service. + 3. Invoke `/etc/init.d/nsx-vdpi status` to check if nsx-vdpi is running. + If not, invoke `/etc/init.d/nsx-vdpi start` to start the service. + " + ::= { vmwNsxTDistributedIDSIPSFeature 13 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "NSX IDPS is in one of the cases below. + 1. NSX IDPS is disabled via NSX policy. + 2. NSX IDPS engine is enabled, NSX-IDPS engine and vdpi are up, and + NSX IDPS has been enabled and IDPS rules are configured + via NSX Policy. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 14 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine memory usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is at or above the high + threshold value of 75%. + + Action required: + Consider re-balancing the VM workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedIDSIPSFeature 15 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine memory usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is below the high threshold + value of 75%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 16 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine memory usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is at or above the medium + high threshold value of 85%. + + Action required: + Consider re-balancing the VM workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedIDSIPSFeature 17 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine memory usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is below the medium + high threshold value of 85%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 18 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine memory usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is at or above the + very high threshold value of 95%. + + Action required: + Consider re-balancing the VM workloads on this host to other hosts. + " + ::= { vmwNsxTDistributedIDSIPSFeature 19 } + +vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage + } + STATUS current + DESCRIPTION + "NSX-IDPS engine memory usage has reached + vmwNsxTDataCenterSystemResourceUsage%, which is below the very high + threshold value of 95%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDistributedIDSIPSFeature 20 } + +-- ********************************************************** +-- DNS feature event notifications +-- ********************************************************** + +vmwNsxTDNSFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the DNS feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 30 } + +vmwNsxTDNSFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for DNS feature notifications. + " + ::= { vmwNsxTDNSFeaturePrefix 0 } + +vmwNsxTDNSForwarderDisabled NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "DNS forwarder vmwNsxTDataCenterEntityId is disabled. + + Action required: + 1. Invoke the NSX CLI command `get dns-forwarders status` to verify + if the DNS forwarder is in the disabled state. + 2. Use NSX Policy API or Manager API to enable the DNS forwarder it + should not be in the disabled state. + " + ::= { vmwNsxTDNSFeature 1 } + +vmwNsxTDNSForwarderDisabledClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "DNS forwarder vmwNsxTDataCenterEntityId is enabled. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDNSFeature 2 } + +vmwNsxTDNSForwarderDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "DNS forwarder vmwNsxTDataCenterEntityId is not running. This is impacting the + identified DNS Forwarder that is currently enabled. + + Action required: + 1. Invoke the NSX CLI command `get dns-forwarders status` to verify + if the DNS forwarder is in down state. + 2. Check /var/log/syslog to see if there are errors reported. + 3. Collect a support bundle and contact the NSX support team. + " + ::= { vmwNsxTDNSFeature 3 } + +vmwNsxTDNSForwarderDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "DNS forwarder vmwNsxTDataCenterEntityId is running again. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDNSFeature 4 } + +vmwNsxTDNSForwarderUpstreamServerTimeout NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntentPath, + vmwNsxTDataCenterDNSId, + vmwNsxTDataCenterDNSUpstreamIP + } + STATUS current + DESCRIPTION + "DNS forwarder vmwNsxTDataCenterIntentPath(vmwNsxTDataCenterDNSId) did not receive a timely response + from upstream server vmwNsxTDataCenterDNSUpstreamIP. Compute instance connectivity to + timed out FQDNs may be impacted. + + Action required: + 1. Invoke the NSX API GET /api/v1/dns/forwarders/vmwNsxTDataCenterDNSId/nslookup? + address=<address>&server_ip=vmwNsxTDataCenterDNSUpstreamIP&source_ip=<source_ip>. + This API request triggers a DNS lookup to the upstream server in the + DNS forwarder's network namespace. <address> is the IP address or FQDN + in the same domain as the upstream server. <source_ip> is an IP address + in the upstream server's zone. + If the API returns a connection timed out response, there is likely a + network error or upstream server problem. Please check why DSN lookups + are not reaching the upstream server or why the upstream server is not + returning a response. If the API response indicates the upstream server + is answering, proceed to step 2. + 2. Invoke the NSX API GET /api/v1/dns/forwarders/vmwNsxTDataCenterDNSId/nslookup? + address=<address>. + This API request triggers a DNS lookup to the DNS forwarder. If the API + returns a valid response, the upstream server may have recovered and this + alarm should get resolved within a few minutes. If the API returns a + connection timed out response, proceed to step 3. + 3. Invoke the NSX CLI command `get dns-forwarder vmwNsxTDataCenterDNSId live-debug + server-ip vmwNsxTDataCenterDNSUpstreamIP`. + This command triggers live debugging on the upstream server and logs + details and statistics showing why the DNS forwarder is not getting a + response. + " + ::= { vmwNsxTDNSFeature 5 } + +vmwNsxTDNSForwarderUpstreamServerTimeoutClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntentPath, + vmwNsxTDataCenterDNSId, + vmwNsxTDataCenterDNSUpstreamIP + } + STATUS current + DESCRIPTION + "DNS forwarder vmwNsxTDataCenterIntentPath(vmwNsxTDataCenterDNSId) upstream server vmwNsxTDataCenterDNSUpstreamIP + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTDNSFeature 6 } + +-- ********************************************************** +-- Edge feature event notifications +-- ********************************************************** + +vmwNsxTEdgeFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Edge feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 45 } + +vmwNsxTEdgeFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Edge feature notifications. + " + ::= { vmwNsxTEdgeFeaturePrefix 0 } + +vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReason + } + STATUS current + DESCRIPTION + "The Edge node vmwNsxTDataCenterEntityId settings and vSphere configuration are changed and does not + match the policy intent configuration. The Edge node configuration visible to user + on UI or API is not same as what is realized. The realized Edge node changes made by + user outside of NSX Manager are shown in the details of this alarm and any edits in + UI or API will overwrite the realized configuration. Fields that differ for Edge node + settings and vSphere configuration are listed in runtime data vmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReason + + Action required: + Please review the node settings and vSphere configuration of this Edge Transport Node vmwNsxTDataCenterEntityId. + Please follow one of following actions to resolve alarm - + 1. Manually update Edge Transport Node setting Policy intent using + API : PUT https://<manager-ip>/api/v1/transport-nodes/<tn-id>. + 2. Accept intent or vSphere realized Edge node configuration or realized + Edge node settings for this Edge Transport Node through Edge Transport Node + resolver to resolve this alarm. + 3. Resolve alarm by accepting the Edge node settings and vSphere realized configuration + using refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. + " + ::= { vmwNsxTEdgeFeature 1 } + +vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChangedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Edge node vmwNsxTDataCenterEntityId node settings and vSphere settings are consistent with policy intent now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeFeature 2 } + +vmwNsxTEdgeEdgeNodeSettingsMismatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNodeSettingMismatchReason + } + STATUS current + DESCRIPTION + "The Edge node vmwNsxTDataCenterEntityId settings configuration does not match the policy + intent configuration. The Edge node configuration visible to user on + UI or API is not same as what is realized. The realized Edge node changes + made by user outside of NSX Manager are shown in the details of this alarm + and any edits in UI or API will overwrite the realized configuration. + Fields that differ for the Edge node are listed in runtime data + vmwNsxTDataCenterEdgeNodeSettingMismatchReason + + Action required: + Please review the node settings of this Edge transport node vmwNsxTDataCenterEntityId. + Please follow one of following actions to resolve alarm - + 1. Manually update Edge transport node setting Policy intent + using API - PUT https://<manager-ip>/api/v1/transport-nodes/<tn-id>. + 2. Accept intent or realized Edge node settings for this Edge transport node + through Edge transport node resolver to resolve this alarm. + 3. Resolve alarm by accepting the Edge node settings configuration using + refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. + " + ::= { vmwNsxTEdgeFeature 3 } + +vmwNsxTEdgeEdgeNodeSettingsMismatchClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Edge node vmwNsxTDataCenterEntityId node settings are consistent with policy intent now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeFeature 4 } + +vmwNsxTEdgeEdgeVmvSphereSettingsMismatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReason + } + STATUS current + DESCRIPTION + "The Edge node vmwNsxTDataCenterEntityId configuration on vSphere does not match the policy + intent configuration. The Edge node configuration visible to user on UI or API + is not same as what is realized. The realized Edge node changes made by user + outside of NSX Manager are shown in the details of this alarm and any edits + in UI or API will overwrite the realized configuration. Fields that differ for + the Edge node are listed in runtime data vmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReason + + Action required: + Please review the vSphere configuration of this Edge Transport Node vmwNsxTDataCenterEntityId. + Please follow one of following actions to resolve alarm - + 1. Accept intent or vSphere realized Edge node configuration for this Edge Transport Node + through Edge Transport Node resolver to resolve this alarm. + 2. Resolve alarm by accepting the Edge node vSphere realized configuration using + refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. + " + ::= { vmwNsxTEdgeFeature 5 } + +vmwNsxTEdgeEdgeVmvSphereSettingsMismatchClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Edge node vmwNsxTDataCenterEntityId VM vSphere settings are consistent with policy intent now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeFeature 6 } + +vmwNsxTEdgeEdgevSphereLocationMismatch NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgevSphereLocationMismatchReason + } + STATUS current + DESCRIPTION + "The Edge node vmwNsxTDataCenterEntityId has been moved using vMotion. The Edge node vmwNsxTDataCenterEntityId, the configuration + on vSphere does not match the policy intent configuration. The Edge node configuration visible to + user on UI or API is not same as what is realized. The realized Edge node changes made by user outside + of NSX Manager are shown in the details of this alarm. Fields that differ for the Edge node are listed + in runtime data vmwNsxTDataCenterEdgevSphereLocationMismatchReason + + Action required: + Please review the vSphere configuration of this Edge Transport Node vmwNsxTDataCenterEntityId. + Please follow one of following actions to resolve alarm - + 1. Resolve alarm by accepting the Edge node vSphere realized config using + refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. + 2. If you want to return to the previous location please use + NSX Redeploy API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=redeploy. + vMotion back to the original host is not supported. + " + ::= { vmwNsxTEdgeFeature 7 } + +vmwNsxTEdgeEdgevSphereLocationMismatchClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Edge node vmwNsxTDataCenterEntityId node vSphere settings are consistent with policy intent now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeFeature 8 } + +-- ********************************************************** +-- EdgeHealth feature event notifications +-- ********************************************************** + +vmwNsxTEdgeHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the EdgeHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 2 } + +vmwNsxTEdgeHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for EdgeHealth feature notifications. + " + ::= { vmwNsxTEdgeHealthFeaturePrefix 0 } + +vmwNsxTEdgeHealthDatapathThreadDeadlocked NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeThreadName + } + STATUS current + DESCRIPTION + "Edge node datapath thread vmwNsxTDataCenterEdgeThreadName is deadlocked. + + Action required: + Restart the dataplane service by invoking the NSX CLI command `restart service dataplane`. + " + ::= { vmwNsxTEdgeHealthFeature 45 } + +vmwNsxTEdgeHealthDatapathThreadDeadlockedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeThreadName + } + STATUS current + DESCRIPTION + "Edge node datapath thread vmwNsxTDataCenterEdgeThreadName is free from deadlock. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 46 } + +vmwNsxTEdgeHealthEdgeCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this Edge + node. Consider adjusting the Edge appliance form factor size or rebalancing + services to other Edge nodes for the applicable workload. + " + ::= { vmwNsxTEdgeHealthFeature 1 } + +vmwNsxTEdgeHealthEdgeCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 2 } + +vmwNsxTEdgeHealthEdgeCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this Edge + node. Consider adjusting the Edge appliance form factor size or rebalancing + services to other Edge nodes for the applicable workload. + " + ::= { vmwNsxTEdgeHealthFeature 3 } + +vmwNsxTEdgeHealthEdgeCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 4 } + +vmwNsxTEdgeHealthEdgeDatapathConfigurationFailure NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Failed to enable the datapath on the Edge node after three attempts. + + Action required: + Ensure the Edge node's connectivity to the Manager node is healthy. From + the Edge node's NSX CLI, invoke the command `get services` to check the + health of services. If the dataplane service is stopped, invoke the + command `start service dataplane` to start it. + " + ::= { vmwNsxTEdgeHealthFeature 21 } + +vmwNsxTEdgeHealthEdgeDatapathConfigurationFailureClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Datapath on the Edge node has been successfully enabled. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 22 } + +vmwNsxTEdgeHealthEdgeDatapathCPUHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDatapathResourceUsage + } + STATUS current + DESCRIPTION + "The datapath CPU usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterDatapathResourceUsage% which is at or above the high + threshold for at least two minutes. + + Action required: + Review the CPU statistics on the Edge node by invoking the NSX CLI command + `get dataplane cpu stats` to show packet rates per CPU core. Higher CPU + usage is expected with higher packet rates. Consider increasing the Edge + appliance form factor size and rebalancing services on this Edge node to + other Edge nodes in the same cluster or other Edge clusters. + " + ::= { vmwNsxTEdgeHealthFeature 17 } + +vmwNsxTEdgeHealthEdgeDatapathCPUHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached below the + high threshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 18 } + +vmwNsxTEdgeHealthEdgeDatapathCPUVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDatapathResourceUsage + } + STATUS current + DESCRIPTION + "The datapath CPU usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterDatapathResourceUsage% which is at or above the very high + threshold for at least two minutes. + + Action required: + Review the CPU statistics on the Edge node by invoking the NSX CLI command + `get dataplane cpu stats` to show packet rates per CPU core. Higher CPU + usage is expected with higher packet rates. Consider increasing the Edge + appliance form factor size and rebalancing services on this Edge node to + other Edge nodes in the same cluster or other Edge clusters. + " + ::= { vmwNsxTEdgeHealthFeature 19 } + +vmwNsxTEdgeHealthEdgeDatapathCPUVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached below the + very high threshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 20 } + +vmwNsxTEdgeHealthEdgeDatapathCryptodrvDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeCryptoDrvName + } + STATUS current + DESCRIPTION + "Edge node crypto driver vmwNsxTDataCenterEdgeCryptoDrvName is down. + + Action required: + Upgrade the Edge node as needed. + " + ::= { vmwNsxTEdgeHealthFeature 23 } + +vmwNsxTEdgeHealthEdgeDatapathCryptodrvDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeCryptoDrvName + } + STATUS current + DESCRIPTION + "Edge node crypto driver vmwNsxTDataCenterEdgeCryptoDrvName is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 24 } + +vmwNsxTEdgeHealthEdgeDatapathMempoolHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterMempoolName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The datapath mempool usage for vmwNsxTDataCenterMempoolName on Edge node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which + is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Log in as the root user and invoke the command + `edge-appctl -t /var/run/vmware/edge/dpd.ctl mempool/show` and + `edge-appctl -t /var/run/vmware/edge/dpd.ctl memory/show malloc_heap` to + check DPDK memory usage. + " + ::= { vmwNsxTEdgeHealthFeature 25 } + +vmwNsxTEdgeHealthEdgeDatapathMempoolHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterMempoolName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The datapath mempool usage for vmwNsxTDataCenterMempoolName on Edge node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which + is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 26 } + +vmwNsxTEdgeHealthEdgeDatapathNICThroughputHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName, + vmwNsxTDataCenterNICThroughput, + vmwNsxTDataCenterNICThroughputThreshold + } + STATUS current + DESCRIPTION + "The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which is at or above + the high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. + + Action required: + Examine the traffic thoughput levels on the NIC and determine whether + configuration changes are needed. The 'get dataplane thoughput <seconds>' + command can be used to monitor throughput. + " + ::= { vmwNsxTEdgeHealthFeature 49 } + +vmwNsxTEdgeHealthEdgeDatapathNICThroughputHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName, + vmwNsxTDataCenterNICThroughput, + vmwNsxTDataCenterNICThroughputThreshold + } + STATUS current + DESCRIPTION + "The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which + is below the high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 50 } + +vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName, + vmwNsxTDataCenterNICThroughput, + vmwNsxTDataCenterNICThroughputThreshold + } + STATUS current + DESCRIPTION + "The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which is at or above + the very high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. + + Action required: + Examine the traffic thoughput levels on the NIC and determine whether + configuration changes are needed. The 'get dataplane thoughput <seconds>' + command can be used to monitor throughput. + " + ::= { vmwNsxTEdgeHealthFeature 51 } + +vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName, + vmwNsxTDataCenterNICThroughput, + vmwNsxTDataCenterNICThroughputThreshold + } + STATUS current + DESCRIPTION + "The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node + vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which + is below the very high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 52 } + +vmwNsxTEdgeHealthEdgeDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Examine the partition with high usage and see if there are any + unexpected large files that can be removed. + " + ::= { vmwNsxTEdgeHealthFeature 9 } + +vmwNsxTEdgeHealthEdgeDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 10 } + +vmwNsxTEdgeHealthEdgeDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above + the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Examine the partition with high usage and see if there are any + unexpected large files that can be removed. + " + ::= { vmwNsxTEdgeHealthFeature 11 } + +vmwNsxTEdgeHealthEdgeDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is below the + very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 12 } + +vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDatapathResourceUsage + } + STATUS current + DESCRIPTION + "Global ARP table usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterDatapathResourceUsage% which is above the high threshold + for over two minutes. + + Action required: + Log in as the root user and invoke the command + `edge-appctl -t /var/run/vmware/edge/dpd.ctl neigh/show` and check + if neigh cache usage is normal. If it is normal, invoke the command + `edge-appctl -t /var/run/vmware/edge/dpd.ctl neigh/set_param max_entries` + to increase the ARP table size. + " + ::= { vmwNsxTEdgeHealthFeature 27 } + +vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Global arp table usage on Edge node vmwNsxTDataCenterEntityId has reached + below the high threshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 28 } + +vmwNsxTEdgeHealthEdgeMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this Edge + node. Consider adjusting the Edge appliance form factor size or rebalancing + services to other Edge nodes for the applicable workload. + " + ::= { vmwNsxTEdgeHealthFeature 5 } + +vmwNsxTEdgeHealthEdgeMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 6 } + +vmwNsxTEdgeHealthEdgeMemoryUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the very + high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this Edge + node. Consider adjusting the Edge appliance form factor size or rebalancing + services to other Edge nodes for the applicable workload. + " + ::= { vmwNsxTEdgeHealthFeature 7 } + +vmwNsxTEdgeHealthEdgeMemoryUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Edge node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 8 } + +vmwNsxTEdgeHealthEdgeNICLinkStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName + } + STATUS current + DESCRIPTION + "Edge node NIC vmwNsxTDataCenterEdgeNICName link is down. + + Action required: + On the Edge node confirm if the NIC link is physically down by invoking + the NSX CLI command `get interfaces`. If it is down, verify the cable + connection. + " + ::= { vmwNsxTEdgeHealthFeature 29 } + +vmwNsxTEdgeHealthEdgeNICLinkStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName + } + STATUS current + DESCRIPTION + "Edge node NIC vmwNsxTDataCenterEdgeNICName link is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 30 } + +vmwNsxTEdgeHealthEdgeNICOutOfReceiveBuffer NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName, + vmwNsxTDataCenterRxRingBufferOverflowPercentage, + vmwNsxTDataCenterRxMisses, + vmwNsxTDataCenterRxProcessed + } + STATUS current + DESCRIPTION + "Edge NIC vmwNsxTDataCenterEdgeNICName receive ring buffer has overflowed by + vmwNsxTDataCenterRxRingBufferOverflowPercentage% on Edge node vmwNsxTDataCenterEntityId. + The missed packet count is vmwNsxTDataCenterRxMisses and processed packet count + is vmwNsxTDataCenterRxProcessed. + + Action required: + Invoke the NSX CLI command `get dataplane cpu stats`, and check + 1. If cpu usage is high, i.e., > 90%, then take a packet capture on + the interface using the command `start capture interface + <interface-name> direction input` or `start capture interface + <interface-name> direction input core <core-id>` (to capture + packets ingressing on specific core whose usage is high). + Then analyze the capture to see if there are majority of + fragmented packets or ipsec packets. If yes, then it is expected + behavior. If not probably datapath is stuck processing other bookkeeping + operations and if alarm lasts or more than 2-3 min, contact VMware Support. + 2. If cpu usage is not high, i.e., < 90%, then check if rx pps is high + using the command `get dataplane cpu stats` (just to make sure the + traffic rate is increasing). Then increase the ring size by 1024 + using the command `set dataplane ring-size rx <ring-size>`. + NOTE - The continuous increase of ring size by 1024 factor can lead + to some performance issue due to cache line thrashing internally. + If even after increasing the ring size, the issue persists then + it is an indication that edge needs a larger form factor deployment + to accommodate the traffic. + 3. If the alarm keeps on flapping i.e., triggers and resolves very soon, + then it is due to bursty traffic. In this case check if rx pps as + described above, if it is not high during the alarm active period + then contact VMware Support. If pps is high it confirms bursty traffic. + Consider suppressing the alarm. + NOTE - There is no specific benchmark to decide what is regarded as a + high pps value. It depends on infrastructure and type of traffic. + The comparison can be made by noting down when alarm is inactive and + when it is active. + " + ::= { vmwNsxTEdgeHealthFeature 31 } + +vmwNsxTEdgeHealthEdgeNICOutOfReceiveBufferClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName + } + STATUS current + DESCRIPTION + "Edge NIC vmwNsxTDataCenterEdgeNICName receive ring buffer usage on Edge node + vmwNsxTDataCenterEntityId is no longer overflowing. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 32 } + +vmwNsxTEdgeHealthEdgeNICOutOfTransmitBuffer NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName, + vmwNsxTDataCenterTxRingBufferOverflowPercentage, + vmwNsxTDataCenterTxMisses, + vmwNsxTDataCenterTxProcessed + } + STATUS current + DESCRIPTION + "Edge NIC vmwNsxTDataCenterEdgeNICName transmit ring buffer has overflowed by + vmwNsxTDataCenterTxRingBufferOverflowPercentage% on Edge node vmwNsxTDataCenterEntityId. + The missed packet count is vmwNsxTDataCenterTxMisses and processed packet count + is vmwNsxTDataCenterTxProcessed. + + Action required: + 1. If a lot of VMs are accommodated along with edge by the hypervisor + then edge VM might not get time to run, hence the packets might + not be retrieved by hypervisor. Then probably migrating the edge VM + to a host with fewer VMs. + 2. Increase the ring size by 1024 using the command `set dataplane + ring-size tx <ring-size>`. If even after increasing the ring size, + the issue persists then contact VMware Support as the ESX side + transmit ring buffer might be of lower value. If there is no + issue on ESX side, it indicates the edge needs to be scaled to + a larger form factor deployment to accommodate the traffic. + 3. If the alarm keeps on flapping, i.e., triggers and resolves very soon, + then it is due to bursty traffic. In this case check if tx pps using + the command `get dataplane cpu stats`. If it is not high during the + alarm active period then contact VMware Support. + If pps is high it confirms bursty traffic. Consider suppressing the + alarm. + NOTE - There is no specific benchmark to decide what is regarded as a + high pps value. It depends on infrastructure and type of traffic. + The comparison can be made by noting down when alarm is inactive and + when it is active. + " + ::= { vmwNsxTEdgeHealthFeature 33 } + +vmwNsxTEdgeHealthEdgeNICOutOfTransmitBufferClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeNICName + } + STATUS current + DESCRIPTION + "Edge NIC vmwNsxTDataCenterEdgeNICName transmit ring buffer usage on Edge node + vmwNsxTDataCenterEntityId is no longer overflowing. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 34 } + +vmwNsxTEdgeHealthFailureDomainDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeId + } + STATUS current + DESCRIPTION + "All members of failure domain vmwNsxTDataCenterTransportNodeId are down. + + Action required: + 1. On the Edge node identified by vmwNsxTDataCenterTransportNodeId, check the connectivity + to the management and control planes by invoking the NSX CLI command + `get managers` and `get controllers`. + 2. Invoke the NSX CLI command `get interface eth0` to check the management + interface status. + 3. Invoke the CLI `get services` to check the core services status like + dataplane/local-controller/nestdb/router, etc. + 4. Inspect the /var/log/syslog to find the suspecting error. + 5. Reboot the Edge node. + " + ::= { vmwNsxTEdgeHealthFeature 53 } + +vmwNsxTEdgeHealthFailureDomainDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeId + } + STATUS current + DESCRIPTION + "All members of failure domain vmwNsxTDataCenterTransportNodeId are reachable. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 54 } + +vmwNsxTEdgeHealthStorageError NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName + } + STATUS current + DESCRIPTION + "The following disk partitions on the Edge node are in + read-only mode: vmwNsxTDataCenterDiskPartitionName + + Action required: + Examine the read-only partition to see if reboot resolves the issue + or the disk needs to be replaced. Contact GSS for more information. + " + ::= { vmwNsxTEdgeHealthFeature 37 } + +vmwNsxTEdgeHealthStorageErrorClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName + } + STATUS current + DESCRIPTION + "The following disk partitions on the Edge node have recovered from + read-only mode: vmwNsxTDataCenterDiskPartitionName + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEdgeHealthFeature 38 } + +-- ********************************************************** +-- EndpointProtection feature event notifications +-- ********************************************************** + +vmwNsxTEndpointProtectionFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the EndpointProtection feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 13 } + +vmwNsxTEndpointProtectionFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for EndpointProtection feature notifications. + " + ::= { vmwNsxTEndpointProtectionFeaturePrefix 0 } + +vmwNsxTEndpointProtectionEAMStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "ESX Agent Manager (EAM) service on compute manager vmwNsxTDataCenterEntityId is down. + + Action required: + Start the ESX Agent Manager (EAM) service. SSH into vCenter and invoke + the command `service vmware-eam start`. + " + ::= { vmwNsxTEndpointProtectionFeature 1 } + +vmwNsxTEndpointProtectionEAMStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "ESX Agent Manager (EAM) service on compute manager vmwNsxTDataCenterEntityId is either up + or compute manager vmwNsxTDataCenterEntityId has been removed. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEndpointProtectionFeature 2 } + +vmwNsxTEndpointProtectionPartnerChannelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The connection between host module and Partner SVM vmwNsxTDataCenterEntityId + is down. + + Action required: + Refer to https://kb.vmware.com/s/article/85844 and make sure + that Partner SVM vmwNsxTDataCenterEntityId is re-connected to the host module. + " + ::= { vmwNsxTEndpointProtectionFeature 3 } + +vmwNsxTEndpointProtectionPartnerChannelDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The connection between host module and Partner SVM vmwNsxTDataCenterEntityId + is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTEndpointProtectionFeature 4 } + +-- ********************************************************** +-- Federation feature event notifications +-- ********************************************************** + +vmwNsxTFederationFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Federation feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 32 } + +vmwNsxTFederationFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Federation feature notifications. + " + ::= { vmwNsxTFederationFeaturePrefix 0 } + +vmwNsxTFederationGMToGMLatencyWarning NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFromGMPath, + vmwNsxTDataCenterToGMPath, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteId + } + STATUS current + DESCRIPTION + "Latency is higher than expected between Global Managers vmwNsxTDataCenterFromGMPath and vmwNsxTDataCenterToGMPath. + + Action required: + Check the connectivity from Global Manager vmwNsxTDataCenterFromGMPath(vmwNsxTDataCenterSiteId) to the Global Manager + vmwNsxTDataCenterToGMPath(vmwNsxTDataCenterRemoteSiteId) via ping. If they are not pingable, check for flakiness in WAN connectivity. + " + ::= { vmwNsxTFederationFeature 17 } + +vmwNsxTFederationGMToGMLatencyWarningClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFromGMPath, + vmwNsxTDataCenterToGMPath + } + STATUS current + DESCRIPTION + "Latency is below expected levels between Global Managers vmwNsxTDataCenterFromGMPath and vmwNsxTDataCenterToGMPath. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 18 } + +vmwNsxTFederationGMToGMSplitBrain NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterActiveGlobalManagers + } + STATUS current + DESCRIPTION + "Multiple Global Manager nodes are active: vmwNsxTDataCenterActiveGlobalManagers. Only one Global Manager node must be active + at any time. + + Action required: + Configure only one Global Manager node as active and all other Global Manager nodes as standby. + " + ::= { vmwNsxTFederationFeature 9 } + +vmwNsxTFederationGMToGMSplitBrainClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterActiveGlobalManager + } + STATUS current + DESCRIPTION + "Global Manager node vmwNsxTDataCenterActiveGlobalManager is the only active Global Manager node now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 10 } + +vmwNsxTFederationGMToGMSynchronizationError NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFromGMPath, + vmwNsxTDataCenterToGMPath, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteId + } + STATUS current + DESCRIPTION + "Active Global Manager vmwNsxTDataCenterFromGMPath to Standby Global Manager vmwNsxTDataCenterToGMPath cannot + synchronize for more than 5 minutes. + + Action required: + Check the connectivity from Global Manager vmwNsxTDataCenterFromGMPath(vmwNsxTDataCenterSiteId) to the Global Manager + vmwNsxTDataCenterToGMPath(vmwNsxTDataCenterRemoteSiteId) via ping. + " + ::= { vmwNsxTFederationFeature 19 } + +vmwNsxTFederationGMToGMSynchronizationErrorClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFromGMPath, + vmwNsxTDataCenterToGMPath + } + STATUS current + DESCRIPTION + "Synchronization from active Global Manager vmwNsxTDataCenterFromGMPath to standby vmwNsxTDataCenterToGMPath is healthy. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 20 } + +vmwNsxTFederationGMToGMSynchronizationWarning NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFromGMPath, + vmwNsxTDataCenterToGMPath, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteId + } + STATUS current + DESCRIPTION + "Active Global Manager vmwNsxTDataCenterFromGMPath to Standby Global Manager vmwNsxTDataCenterToGMPath can not synchronize. + + Action required: + Check the connectivity from Global Manager vmwNsxTDataCenterFromGMPath(vmwNsxTDataCenterSiteId) to the Global Manager + vmwNsxTDataCenterToGMPath(vmwNsxTDataCenterRemoteSiteId) via ping. + " + ::= { vmwNsxTFederationFeature 21 } + +vmwNsxTFederationGMToGMSynchronizationWarningClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFromGMPath, + vmwNsxTDataCenterToGMPath + } + STATUS current + DESCRIPTION + "Synchronization from active Global Manager vmwNsxTDataCenterFromGMPath to standby vmwNsxTDataCenterToGMPath is healthy. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 22 } + +vmwNsxTFederationGMToLMLatencyWarning NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterLatencyValue, + vmwNsxTDataCenterLatencyThreshold + } + STATUS current + DESCRIPTION + "Latency between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) has reached + vmwNsxTDataCenterLatencyValue which is above the threshold value of vmwNsxTDataCenterLatencyThreshold. + + Action required: + 1. Check the network connectivity between remote site and local site via ping. + 2. Ensure port TCP/1236 traffic is allowed between the local and remote sites. + 3. Check /var/log/async-replicator/ar.log to see if there are errors reported. + " + ::= { vmwNsxTFederationFeature 27 } + +vmwNsxTFederationGMToLMLatencyWarningClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterLatencyValue, + vmwNsxTDataCenterLatencyThreshold + } + STATUS current + DESCRIPTION + "Latency between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) has reached + vmwNsxTDataCenterLatencyValue which below the threshold value of vmwNsxTDataCenterLatencyThreshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 28 } + +vmwNsxTFederationGMToLMSynchronizationError NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterFlowIdentifier, + vmwNsxTDataCenterSyncIssueReason + } + STATUS current + DESCRIPTION + "Data synchronization between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) + failed for the vmwNsxTDataCenterFlowIdentifier for an extended period. Reason: vmwNsxTDataCenterSyncIssueReason. + + Action required: + 1. Check the network connectivity between remote site and local site via ping. 2. Ensure port TCP/1236 traffic is allowed between the local and remote sites. 3. Ensure the async-replicator service is running on both local and remote sites. Invoke the GET /api/v1/node/services/async_replicator/status NSX API or the `get service async_replicator` NSX CLI command to determine if the service is running. If not running, invoke the POST /api/v1/node/services/async_replicator?action=restart NSX API or the `restart service async_replicator` NSX CLI to restart the service. 4. Check /var/log/async-replicator/ar.log to see if there are errors reported. 5. Collect a support bundle and contact the NSX support team. + " + ::= { vmwNsxTFederationFeature 23 } + +vmwNsxTFederationGMToLMSynchronizationErrorClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterFlowIdentifier + } + STATUS current + DESCRIPTION + "Sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized for vmwNsxTDataCenterFlowIdentifier. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 24 } + +vmwNsxTFederationGMToLMSynchronizationWarning NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterFlowIdentifier, + vmwNsxTDataCenterSyncIssueReason + } + STATUS current + DESCRIPTION + "Data synchronization between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) failed for the + vmwNsxTDataCenterFlowIdentifier. Reason: vmwNsxTDataCenterSyncIssueReason + + Action required: + 1. Check the network connectivity between remote site and local site via ping. 2. Ensure port TCP/1236 traffic is allowed between the local and remote sites. 3. Ensure the async-replicator service is running on both local and remote sites. Invoke the GET /api/v1/node/services/async_replicator/status NSX API or the `get service async_replicator` NSX CLI command to determine if the service is running. If not running, invoke the POST /api/v1/node/services/async_replicator?action=restart NSX API or the `restart service async_replicator` NSX CLI to restart the service. 4. Check /var/log/async-replicator/ar.log to see if there are errors reported. + " + ::= { vmwNsxTFederationFeature 25 } + +vmwNsxTFederationGMToLMSynchronizationWarningClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterFlowIdentifier + } + STATUS current + DESCRIPTION + "Sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized for vmwNsxTDataCenterFlowIdentifier. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 26 } + +vmwNsxTFederationLMRestoreWhileConfigImportInProgress NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId + } + STATUS current + DESCRIPTION + "Config import from site vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) is in progress. However site vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) is restored + from backup by the administrator leaving it in an inconsistent state. + + Action required: + 1. Log in to NSX Global Manager appliance CLI. + 2. Switch to root. + 3. Invoke the NSX API DELETE http://localhost:64440/gm/api/v1/infra/sites/<site-name>/onboarding/status in local mode, + this will delete site on-boarding status for Global Manager. + 4. Re-initiate config on-boarding again. + " + ::= { vmwNsxTFederationFeature 31 } + +vmwNsxTFederationLMRestoreWhileConfigImportInProgressClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId + } + STATUS current + DESCRIPTION + "Config inconsistency at site vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) is resolved. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 32 } + +vmwNsxTFederationLmToLmSynchronizationError NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId + } + STATUS current + DESCRIPTION + "The synchronization between vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) + failed for more than 5 minutes. + + Action required: + 1. Invoke the NSX CLI command `get site-replicator remote-sites` to get connection + state between the remote locations. If a remote location is connected but not synchronized, + it is possible that the location is still in the process of master resolution. In + this case, wait for around 10 seconds and try invoking the CLI again to + check for the state of the remote location. If a location is disconnected, try the next + step. + 2. Check the connectivity from Local Manager (LM) in location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) to the LMs + in location vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) via ping. If they are not pingable, + check for flakiness in WAN connectivity. If there are no physical network + connectivity issues, try the next step. + 3. Check the /var/log/cloudnet/nsx-ccp.log file on the Manager nodes in the local cluster in + location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) that triggered the alarm to see if there are any cross-site + communication errors. In addition, also look for errors being logged by the + nsx-appl-proxy subcomponent within /var/log/syslog. + " + ::= { vmwNsxTFederationFeature 3 } + +vmwNsxTFederationLmToLmSynchronizationErrorClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId + } + STATUS current + DESCRIPTION + "Remote sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 4 } + +vmwNsxTFederationLmToLmSynchronizationWarning NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId + } + STATUS current + DESCRIPTION + "The synchronization between vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) failed. + + Action required: + 1. Invoke the NSX CLI command `get site-replicator remote-sites` to get connection + state between the remote locations. If a remote location is connected but not synchronized, + it is possible that the location is still in the process of master resolution. In + this case, wait for around 10 seconds and try invoking the CLI again to + check for the state of the remote location. If a location is disconnected, try the next + step. + 2. Check the connectivity from Local Manager (LM) in location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) to the LMs + in location vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) via ping. If they are not pingable, + check for flakiness in WAN connectivity. If there are no physical network + connectivity issues, try the next step. + 3. Check the /var/log/cloudnet/nsx-ccp.log file on the Manager nodes in the local cluster in + location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) that triggered the alarm to see if there are any cross-site + communication errors. In addition, also look for errors being logged by the + nsx-appl-proxy subcomponent within /var/log/syslog. + " + ::= { vmwNsxTFederationFeature 5 } + +vmwNsxTFederationLmToLmSynchronizationWarningClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId + } + STATUS current + DESCRIPTION + "Remote locations vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 6 } + +vmwNsxTFederationQueueOccupancyThresholdExceeded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterQueueName, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterQueueSize, + vmwNsxTDataCenterQueueSizeThreshold + } + STATUS current + DESCRIPTION + "Queue (vmwNsxTDataCenterQueueName) used for syncing data between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) + has reached size vmwNsxTDataCenterQueueSize which is at or above the maximum threshold of vmwNsxTDataCenterQueueSizeThreshold%. + + Action required: + Queue size can exceed threshold due to communication issue with remote site or an overloaded system. + Please check system performance and /var/log/async-replicator/ar.log to see if there are any errors reported. + " + ::= { vmwNsxTFederationFeature 29 } + +vmwNsxTFederationQueueOccupancyThresholdExceededClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterQueueName, + vmwNsxTDataCenterSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterQueueSize, + vmwNsxTDataCenterQueueSizeThreshold + } + STATUS current + DESCRIPTION + "Queue (vmwNsxTDataCenterQueueName) used for syncing data between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) + has reached size vmwNsxTDataCenterQueueSize which is below the maximum threshold of vmwNsxTDataCenterQueueSizeThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 30 } + +vmwNsxTFederationRtepBGPDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterBGPSourceIP, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterBGPNeighborIP, + vmwNsxTDataCenterFailureReason + } + STATUS current + DESCRIPTION + "RTEP (Remote Tunnel Endpoint) BGP session from source IP vmwNsxTDataCenterBGPSourceIP + to remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP is down. + Reason: vmwNsxTDataCenterFailureReason. + + Action required: + 1. Invoke the NSX CLI command `get logical-routers` on the affected edge node. + 2. Switch to REMOTE_TUNNEL_VRF context. + 3. Invoke the NSX CLI command `get bgp neighbor summary` to check the BGP neighbor status. + 4. Alternatively, invoke the NSX API GET /api/v1/transport-nodes/<transport-node-id>/inter-site/bgp/summary + to get the BGP neighbor status. + 5. Invoke the NSX CLI command `get interfaces` and check if the correct RTEP IP address is assigned + to the interface with name remote-tunnel-endpoint. + 6. Check if the ping is working successfully between assigned RTEP IP address (vmwNsxTDataCenterBGPSourceIP) and the + remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP. + 7. Check /var/log/syslog for any errors related to BGP. + 8. Invoke the NSX API GET or PUT /api/v1/transport-nodes/<transport-node-id> to get/update remote_tunnel_endpoint + configuration on the edge node. + This will update the RTEP IP assigned to the affected edge node. + + If the reason indicates `Edge is not ready`, check why edge is not in good state. + 1. Invoke the NSX CLI command `get edge-cluster status` to check reason why edge might be down. + 2. Invoke the NSX CLI commands `get bfd-config` and `get bfd-sessions` to check if BFD is running well. + 3. Check any edge health related alarms to get more information. + " + ::= { vmwNsxTFederationFeature 1 } + +vmwNsxTFederationRtepBGPDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterBGPSourceIP, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterBGPNeighborIP + } + STATUS current + DESCRIPTION + "RTEP (Remote Tunnel Endpoint) BGP session from source IP vmwNsxTDataCenterBGPSourceIP + to remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP is established. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 2 } + +vmwNsxTFederationRtepConnectivityLost NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName, + vmwNsxTDataCenterRemoteSiteName + } + STATUS current + DESCRIPTION + "Edge node vmwNsxTDataCenterTransportNodeName lost RTEP (Remote Tunnel Endpoint) connectivity + with remote location vmwNsxTDataCenterRemoteSiteName. + + Action required: + 1. Invoke the NSX CLI command `get logical-routers` on the affected edge node vmwNsxTDataCenterTransportNodeName. + 2. Switch to REMOTE_TUNNEL_VRF context. + 3. Invoke the NSX CLI command `get bgp neighbor summary` to check the BGP neighbor status. + 4. Alternatively, invoke the NSX API GET /api/v1/transport-nodes/<transport-node-id>/inter-site/bgp/summary + to get the BGP neighbor status. + 5. Invoke the NSX CLI command `get interfaces` and check if the correct RTEP IP address is assigned + to the interface with name remote-tunnel-endpoint. + 6. Check if the ping is working successfully between assigned RTEP IP address and the RTEP IP addresses + on the remote location vmwNsxTDataCenterRemoteSiteName. + 7. Check /var/log/syslog for any errors related to BGP. + 8. Invoke the NSX API GET or PUT /api/v1/transport-nodes/<transport-node-id> to get/update remote_tunnel_endpoint + configuration on the edge node. + This will update the RTEP IP assigned to the affected edge node vmwNsxTDataCenterTransportNodeName. + " + ::= { vmwNsxTFederationFeature 7 } + +vmwNsxTFederationRtepConnectivityLostClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeName, + vmwNsxTDataCenterRemoteSiteName + } + STATUS current + DESCRIPTION + "Edge node vmwNsxTDataCenterTransportNodeName has restored RTEP (Remote Tunnel Endpoint) connectivity + with remote location vmwNsxTDataCenterRemoteSiteName. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTFederationFeature 8 } + +-- ********************************************************** +-- GatewayFirewall feature event notifications +-- ********************************************************** + +vmwNsxTGatewayFirewallFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the GatewayFirewall feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 39 } + +vmwNsxTGatewayFirewallFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for GatewayFirewall feature notifications. + " + ::= { vmwNsxTGatewayFirewallFeaturePrefix 0 } + +vmwNsxTGatewayFirewallICMPFlowCountExceeded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallICMPFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for ICMP traffic on logical + router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallICMPFlowUsage% which is at or above the + high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usage for ICMP flows. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 21 } + +vmwNsxTGatewayFirewallICMPFlowCountExceededClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached + below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 22 } + +vmwNsxTGatewayFirewallICMPFlowCountHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallICMPFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for ICMP on logical router vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterFirewallICMPFlowUsage% which is at or above the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usege for ICMP flows. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 23 } + +vmwNsxTGatewayFirewallICMPFlowCountHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for ICMP on logical router + vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 24 } + +vmwNsxTGatewayFirewallIPFlowCountExceeded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallIPFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for IP traffic on logical router vmwNsxTDataCenterEntityId has + reached vmwNsxTDataCenterFirewallIPFlowUsage% which is at or above the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usage for IP flows. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 25 } + +vmwNsxTGatewayFirewallIPFlowCountExceededClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached + below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 26 } + +vmwNsxTGatewayFirewallIPFlowCountHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallIPFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for IP on logical router vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterFirewallIPFlowUsage% which is at or above the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usege for IP flows. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 27 } + +vmwNsxTGatewayFirewallIPFlowCountHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for non IP flows on logical router + vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 28 } + +vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceeded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallHalfopenFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for TCP half-open traffic on logical + router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallHalfopenFlowUsage% which is at or above the + high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usage for TCP half-open flows. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 29 } + +vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceededClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached + below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 30 } + +vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallHalfopenFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for TCP on logical router vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterFirewallHalfopenFlowUsage% which is at or above the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usege for TCP half-open flow. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 31 } + +vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for TCP half-open on logical router + vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 32 } + +vmwNsxTGatewayFirewallUDPFlowCountExceeded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallUDPFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for UDP traffic on logical + router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallUDPFlowUsage% which is at or above the + high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usage for UDP flows. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 33 } + +vmwNsxTGatewayFirewallUDPFlowCountExceededClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached + below the high threshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 34 } + +vmwNsxTGatewayFirewallUDPFlowCountHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterFirewallUDPFlowUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for UDP on logical router vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterFirewallUDPFlowUsage% which is at or above the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + New flows will be dropped by Gateway firewall when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> interface stats | json` by using + right interface uuid and check flow table usege for UDP flows. + Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. + " + ::= { vmwNsxTGatewayFirewallFeature 35 } + +vmwNsxTGatewayFirewallUDPFlowCountHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Gateway firewall flow table usage for UDP on logical router + vmwNsxTDataCenterEntityId has reached below the high threshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTGatewayFirewallFeature 36 } + +-- ********************************************************** +-- HighAvailability feature event notifications +-- ********************************************************** + +vmwNsxTHighAvailabilityFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the HighAvailability feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 21 } + +vmwNsxTHighAvailabilityFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for HighAvailability feature notifications. + " + ::= { vmwNsxTHighAvailabilityFeaturePrefix 0 } + +vmwNsxTHighAvailabilityTier0GatewayFailover NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterPreviousGatewayState, + vmwNsxTDataCenterCurrentGatewayState, + vmwNsxTDataCenterServiceRouterId + } + STATUS current + DESCRIPTION + "The tier0 gateway vmwNsxTDataCenterEntityId failover from vmwNsxTDataCenterPreviousGatewayState + to vmwNsxTDataCenterCurrentGatewayState, service-router vmwNsxTDataCenterServiceRouterId. + + Action required: + Invoke the NSX CLI command `get logical-router <service_router_id>` to + identify the tier0 service-router vrf ID. Switch to the vrf context by + invoking `vrf <vrf-id>` then invoke `get high-availability status` + to determine the service that is down. + " + ::= { vmwNsxTHighAvailabilityFeature 9 } + +vmwNsxTHighAvailabilityTier0GatewayFailoverClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The tier0 gateway vmwNsxTDataCenterEntityId is now up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTHighAvailabilityFeature 10 } + +vmwNsxTHighAvailabilityTier1GatewayFailover NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterPreviousGatewayState, + vmwNsxTDataCenterCurrentGatewayState, + vmwNsxTDataCenterServiceRouterId + } + STATUS current + DESCRIPTION + "The tier1 gateway vmwNsxTDataCenterEntityId failover from vmwNsxTDataCenterPreviousGatewayState + to vmwNsxTDataCenterCurrentGatewayState, service-router vmwNsxTDataCenterServiceRouterId. + + Action required: + Invoke the NSX CLI command `get logical-router <service_router_id>` to + identify the tier1 service-router vrf ID. Switch to the vrf context by + invoking `vrf <vrf-id>` then invoke `get high-availability status` + to determine the service that is down. + " + ::= { vmwNsxTHighAvailabilityFeature 11 } + +vmwNsxTHighAvailabilityTier1GatewayFailoverClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The tier1 gateway vmwNsxTDataCenterEntityId is now up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTHighAvailabilityFeature 12 } + +-- ********************************************************** +-- IdentityFirewall feature event notifications +-- ********************************************************** + +vmwNsxTIdentityFirewallFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the IdentityFirewall feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 36 } + +vmwNsxTIdentityFirewallFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for IdentityFirewall feature notifications. + " + ::= { vmwNsxTIdentityFirewallFeaturePrefix 0 } + +vmwNsxTIdentityFirewallConnectivityToLDAPServerLost NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLDAPServer + } + STATUS current + DESCRIPTION + "The connectivity to LDAP server vmwNsxTDataCenterLDAPServer is lost. + + Action required: + Please check + 1. The LDAP server is reachable from NSX nodes. + 2. The LDAP server details are configured correctly in NSX. + 3. The LDAP server is running correctly. + 4. There are no firewalls blocking access between the LDAP server + and NSX nodes. + Afer the issue is fixed, use TEST CONNECTION in NSX UI under + Identity Firewall AD to test the connection. + " + ::= { vmwNsxTIdentityFirewallFeature 1 } + +vmwNsxTIdentityFirewallConnectivityToLDAPServerLostClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLDAPServer + } + STATUS current + DESCRIPTION + "The connectivity to LDAP server vmwNsxTDataCenterLDAPServer is restored. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIdentityFirewallFeature 2 } + +vmwNsxTIdentityFirewallErrorInDeltaSync NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDirectoryDomain + } + STATUS current + DESCRIPTION + "Errors occurred while performing delta sync with vmwNsxTDataCenterDirectoryDomain. + + Action required: + 1. Check if there are any connectivity to LDAP server lost alarms. + 2. Find the error details in /var/log/syslog. Around the alarm trigger + time, search for text: Error happened when synchronize LDAP objects. + 3. Check with AD administrator if there are any recent AD changes which + may cause the errors. + 4. If the errors persist, collect the technical support bundle and + contact VMware technical support. + " + ::= { vmwNsxTIdentityFirewallFeature 3 } + +vmwNsxTIdentityFirewallErrorInDeltaSyncClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDirectoryDomain + } + STATUS current + DESCRIPTION + "No errors occurred while performing delta sync with vmwNsxTDataCenterDirectoryDomain. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIdentityFirewallFeature 4 } + +-- ********************************************************** +-- InfrastructureCommunication feature event notifications +-- ********************************************************** + +vmwNsxTInfrastructureCommunicationFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the InfrastructureCommunication feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 7 } + +vmwNsxTInfrastructureCommunicationFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for InfrastructureCommunication feature notifications. + " + ::= { vmwNsxTInfrastructureCommunicationFeaturePrefix 0 } + +vmwNsxTInfrastructureCommunicationEdgeTunnelsDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The overall tunnel status of Edge node vmwNsxTDataCenterEntityId is down. + + Action required: + Invoke the NSX CLI command `get tunnel-ports` to get all tunnel ports, + then check each tunnel's stats by invoking NSX CLI command + `get tunnel-port <UUID> stats` to check if there are any drops. Also + check /var/log/syslog if there are tunnel related errors. + " + ::= { vmwNsxTInfrastructureCommunicationFeature 17 } + +vmwNsxTInfrastructureCommunicationEdgeTunnelsDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The tunnels of Edge node vmwNsxTDataCenterEntityId have been restored. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTInfrastructureCommunicationFeature 18 } + +-- ********************************************************** +-- InfrastructureService feature event notifications +-- ********************************************************** + +vmwNsxTInfrastructureServiceFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the InfrastructureService feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 19 } + +vmwNsxTInfrastructureServiceFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for InfrastructureService feature notifications. + " + ::= { vmwNsxTInfrastructureServiceFeaturePrefix 0 } + +vmwNsxTInfrastructureServiceEdgeServiceStatusChanged NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeServiceName, + vmwNsxTDataCenterPreviousServiceState, + vmwNsxTDataCenterCurrentServiceState, + vmwNsxTDataCenterServiceDownReason + } + STATUS current + DESCRIPTION + "The service vmwNsxTDataCenterEdgeServiceName changed from vmwNsxTDataCenterPreviousServiceState + to vmwNsxTDataCenterCurrentServiceState. + vmwNsxTDataCenterServiceDownReason + + Action required: + On the Edge node, verify the service hasn't exited due to an error by + looking for core files in the /var/log/core directory. In addition, + invoke the NSX CLI command `get services` to confirm whether the service + is stopped. If so, invoke `start service <service-name>` to restart the + service. + " + ::= { vmwNsxTInfrastructureServiceFeature 1 } + +vmwNsxTInfrastructureServiceEdgeServiceStatusChangedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeServiceName, + vmwNsxTDataCenterPreviousServiceState, + vmwNsxTDataCenterCurrentServiceState + } + STATUS current + DESCRIPTION + "The service vmwNsxTDataCenterEdgeServiceName changed from vmwNsxTDataCenterPreviousServiceState + to vmwNsxTDataCenterCurrentServiceState. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTInfrastructureServiceFeature 2 } + +vmwNsxTInfrastructureServiceEdgeServiceStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeServiceName, + vmwNsxTDataCenterServiceDownReason + } + STATUS current + DESCRIPTION + "The service vmwNsxTDataCenterEdgeServiceName is down for at least one minute. + vmwNsxTDataCenterServiceDownReason + + Action required: + On the Edge node, verify the service hasn't exited due to an error by + looking for core files in the /var/log/core directory. In addition, + invoke the NSX CLI command `get services` to confirm whether the service + is stopped. If so, invoke `start service <service-name>` to restart the + service. + " + ::= { vmwNsxTInfrastructureServiceFeature 3 } + +vmwNsxTInfrastructureServiceEdgeServiceStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEdgeServiceName + } + STATUS current + DESCRIPTION + "The service vmwNsxTDataCenterEdgeServiceName is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTInfrastructureServiceFeature 4 } + +vmwNsxTInfrastructureServiceServiceStatusUnknown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterServiceName + } + STATUS current + DESCRIPTION + "The service vmwNsxTDataCenterServiceName has been unresponsive for 10 seconds. + + Action required: + Verify vmwNsxTDataCenterServiceName service is still running by invoking `/etc/init.d/vmwNsxTDataCenterServiceName status`. + If the service is reported as running, it may need to get restarted which can be done by + `/etc/init.d/vmwNsxTDataCenterServiceName restart`. Rerun the status command to verify the service is now + running. If the script `/etc/init.d/vmwNsxTDataCenterServiceName` is unavailable, please try invoking + `systemctl vmwNsxTDataCenterServiceName status` and restart by `systemctl vmwNsxTDataCenterServiceName restart` with root + priviledges. If restarting the service does not resolve the issue or if the issue reoccurs after + a successful restart, please contact VMware Support. + " + ::= { vmwNsxTInfrastructureServiceFeature 7 } + +vmwNsxTInfrastructureServiceServiceStatusUnknownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterServiceName + } + STATUS current + DESCRIPTION + "The service vmwNsxTDataCenterServiceName is responsive again. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTInfrastructureServiceFeature 8 } + +-- ********************************************************** +-- IntelligenceCommunication feature event notifications +-- ********************************************************** + +vmwNsxTIntelligenceCommunicationFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the IntelligenceCommunication feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 9 } + +vmwNsxTIntelligenceCommunicationFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for IntelligenceCommunication feature notifications. + " + ::= { vmwNsxTIntelligenceCommunicationFeaturePrefix 0 } + +vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The flow exporter on Transport node vmwNsxTDataCenterEntityId is disconnected from + the Intelligence node's messaging broker. Data collection is affected. + + Action required: + Restart the messaging service if it is not running in the Intelligence + node. Resolve the network connection failure between the Transport node + flow exporter and the Intelligence node. + " + ::= { vmwNsxTIntelligenceCommunicationFeature 7 } + +vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnectedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The flow exporter on Transport node vmwNsxTDataCenterEntityId has reconnected to + the Intelligence node's messaging broker. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceCommunicationFeature 8 } + +-- ********************************************************** +-- IntelligenceHealth feature event notifications +-- ********************************************************** + +vmwNsxTIntelligenceHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the IntelligenceHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 6 } + +vmwNsxTIntelligenceHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for IntelligenceHealth feature notifications. + " + ::= { vmwNsxTIntelligenceHealthFeaturePrefix 0 } + +vmwNsxTIntelligenceHealthCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Use the top command to check which processes have the most CPU usages, and + then check /var/log/syslog and these processes' local logs to see if there + are any outstanding errors to be resolved. + " + ::= { vmwNsxTIntelligenceHealthFeature 41 } + +vmwNsxTIntelligenceHealthCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 42 } + +vmwNsxTIntelligenceHealthCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Use the top command to check which processes have the most CPU usages, and + then check /var/log/syslog and these processes' local logs to see if there + are any outstanding errors to be resolved. + " + ::= { vmwNsxTIntelligenceHealthFeature 43 } + +vmwNsxTIntelligenceHealthCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 44 } + +vmwNsxTIntelligenceHealthDataDiskPartitionUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition /data on Intelligence node + vmwNsxTDataCenterIntelligenceNodeId is above the high threshold value + of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Stop NSX intelligence data collection until the disk usage is below + the threshold. Examine disk partition /data and see if there are any + unexpected large files that can be removed. + " + ::= { vmwNsxTIntelligenceHealthFeature 45 } + +vmwNsxTIntelligenceHealthDataDiskPartitionUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition /data on Intelligence node + vmwNsxTDataCenterIntelligenceNodeId is below the high threshold value + of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 46 } + +vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition /data on Intelligence node + vmwNsxTDataCenterIntelligenceNodeId is above the very high threshold value + of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Stop NSX intelligence data collection until the disk usage is below + the threshold. In the NSX UI, navigate to System | Appliances | NSX + Intelligence Appliance. Then click ACTONS, Stop Collecting Data. + " + ::= { vmwNsxTIntelligenceHealthFeature 47 } + +vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition /data on Intelligence node + vmwNsxTDataCenterIntelligenceNodeId is below the very high threshold value + of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 48 } + +vmwNsxTIntelligenceHealthDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on + Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Examine disk partition vmwNsxTDataCenterDiskPartitionName and see if there are any + unexpected large files that can be removed. + " + ::= { vmwNsxTIntelligenceHealthFeature 49 } + +vmwNsxTIntelligenceHealthDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on + Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 50 } + +vmwNsxTIntelligenceHealthDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on + Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above + the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Examine disk partition vmwNsxTDataCenterDiskPartitionName and see if there are any + unexpected large files that can be removed. + " + ::= { vmwNsxTIntelligenceHealthFeature 51 } + +vmwNsxTIntelligenceHealthDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on + Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below + the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 52 } + +vmwNsxTIntelligenceHealthMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Use the top command to check which processes have the most memory usages, + and then check /var/log/syslog and these processes' local logs to see if + there are any outstanding errors to be resolved. + " + ::= { vmwNsxTIntelligenceHealthFeature 53 } + +vmwNsxTIntelligenceHealthMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 54 } + +vmwNsxTIntelligenceHealthMemoryUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Use the top command to check which processes have the most memory usages, + and then check /var/log/syslog and these processes' local logs to see if + there are any outstanding errors to be resolved. + " + ::= { vmwNsxTIntelligenceHealthFeature 55 } + +vmwNsxTIntelligenceHealthMemoryUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId + is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 56 } + +vmwNsxTIntelligenceHealthNodeStatusDegraded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterServiceName, + vmwNsxTDataCenterIntelligenceNodeId + } + STATUS current + DESCRIPTION + "Intelligence node vmwNsxTDataCenterIntelligenceNodeId is degraded. + + Action required: + Invoke the NSX API GET /napp/api/v1/platform/monitor/category/health to + check which specific pod is down and the reason behind it. Invoke the following + CLI command to restart the degraded service: + `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` + " + ::= { vmwNsxTIntelligenceHealthFeature 57 } + +vmwNsxTIntelligenceHealthNodeStatusDegradedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterServiceName, + vmwNsxTDataCenterIntelligenceNodeId + } + STATUS current + DESCRIPTION + "Intelligence node vmwNsxTDataCenterIntelligenceNodeId is running properly. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 58 } + +vmwNsxTIntelligenceHealthStorageLatencyHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The storage latency of disk partition vmwNsxTDataCenterDiskPartitionName on + Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold milliseconds. + + Action required: + Transient high storage latency may happen due to spike of I/O requests. + If storage latency remains high for more than 30 minutes, + consider deploying NSX Intelligence appliance in a low latency disk, + or not sharing the same storage device with other VMs. + " + ::= { vmwNsxTIntelligenceHealthFeature 63 } + +vmwNsxTIntelligenceHealthStorageLatencyHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The storage latency of disk partition vmwNsxTDataCenterDiskPartitionName on + Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold milliseconds. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIntelligenceHealthFeature 64 } + +-- ********************************************************** +-- IPAM feature event notifications +-- ********************************************************** + +vmwNsxTIPAMFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the IPAM feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 38 } + +vmwNsxTIPAMFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for IPAM feature notifications. + " + ::= { vmwNsxTIPAMFeaturePrefix 0 } + +vmwNsxTIPAMIPBlockUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntentPath + } + STATUS current + DESCRIPTION + "IP block usage of vmwNsxTDataCenterIntentPath is very high. + IP block nearing its total capacity, creation of subnet using IP block might fail. + + Action required: + Please review IP block usage. Use new IP block for resource creation or delete unused IP subnet from the IP block. + To check subnet being used for IP Block. From NSX UI, navigate to Networking | IP Address pools | IP Address pools tab. + Select IP pools where IP block being used, check Subnets and Allocated IPs column on UI. If no allocation has been used for the IP pool and it is not going to be used in future then delete subnet or IP pool. + Use following API to check if IP block being used by IP pool and also check if any IP allocation done: + To get configured subnets of an IP pool, invoke the NSX API + GET /policy/api/v1/infra/ip-pools/<ip-pool>/ip-subnets + To get IP allocations, invoke the NSX API + GET /policy/api/v1/infra/ip-pools/<ip-pool>/ip-allocations + Please note: Deletion of IP pool/subnet should only be done if it does not have any allocated IPs and it is not going to be used in future. + " + ::= { vmwNsxTIPAMFeature 1 } + +vmwNsxTIPAMIPBlockUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntentPath + } + STATUS current + DESCRIPTION + "IP block usage of vmwNsxTDataCenterIntentPath is below threshold level. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIPAMFeature 2 } + +vmwNsxTIPAMIPPoolUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntentPath + } + STATUS current + DESCRIPTION + "IP pool usage of vmwNsxTDataCenterIntentPath is very high. + IP pool nearing its total capacity. Creation of entity/service depends on IP being allocated from IP pool might fail. + + Action required: + Please review IP pool usage. + Release unused ip allocations from IP pool or create new IP pool and use it. + From NSX UI navigate to Networking | IP Address pools | IP Address pools tab. + Select IP pools and check Allocated IPs column, this will show IPs allocated from the IP pool. + If user see any IPs are not being used then those IPs can be released. + To release unused IP allocations, invoke the NSX API + DELETE /policy/api/v1/infra/ip-pools/<ip-pool>/ip-allocations/<ip-allocation> + " + ::= { vmwNsxTIPAMFeature 3 } + +vmwNsxTIPAMIPPoolUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterIntentPath + } + STATUS current + DESCRIPTION + "IP pool usage of vmwNsxTDataCenterIntentPath is normal now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTIPAMFeature 4 } + +-- ********************************************************** +-- Licenses feature event notifications +-- ********************************************************** + +vmwNsxTLicensesFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Licenses feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 5 } + +vmwNsxTLicensesFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Licenses feature notifications. + " + ::= { vmwNsxTLicensesFeaturePrefix 0 } + +vmwNsxTLicensesLicenseExpired NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLicenseEditionType, + vmwNsxTDataCenterDisplayedLicenseKey + } + STATUS current + DESCRIPTION + "The vmwNsxTDataCenterLicenseEditionType license key ending with + vmwNsxTDataCenterDisplayedLicenseKey, has expired. + + Action required: + Add a new, non-expired license using the NSX UI by navigating to + System | Licenses then click ADD and specify the key of the new + license. The expired license should be deleted by checking the + checkbox of the license, then click DELETE. + " + ::= { vmwNsxTLicensesFeature 1 } + +vmwNsxTLicensesLicenseExpiredClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLicenseEditionType, + vmwNsxTDataCenterDisplayedLicenseKey + } + STATUS current + DESCRIPTION + "The expired vmwNsxTDataCenterLicenseEditionType license key ending with + vmwNsxTDataCenterDisplayedLicenseKey, has been removed, updated or is no + longer about to expire. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLicensesFeature 2 } + +vmwNsxTLicensesLicenseIsAboutToExpire NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLicenseEditionType, + vmwNsxTDataCenterDisplayedLicenseKey + } + STATUS current + DESCRIPTION + "The vmwNsxTDataCenterLicenseEditionType license key ending with + vmwNsxTDataCenterDisplayedLicenseKey, is about to expire. + + Action required: + The license is about to expire in several days. Please plan to add a + new, non-expiring license using the NSX UI by navigating to System | + Licenses then click ADD and specify the key of the new license. The + expired license should be deleted by checking the checkbox of the + license, then click DELETE. + " + ::= { vmwNsxTLicensesFeature 3 } + +vmwNsxTLicensesLicenseIsAboutToExpireClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLicenseEditionType, + vmwNsxTDataCenterDisplayedLicenseKey + } + STATUS current + DESCRIPTION + "The expiring vmwNsxTDataCenterLicenseEditionType license key ending with + vmwNsxTDataCenterDisplayedLicenseKey, has been removed, updated or is no + longer about to expire. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLicensesFeature 4 } + +-- ********************************************************** +-- LoadBalancer feature event notifications +-- ********************************************************** + +vmwNsxTLoadBalancerFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the LoadBalancer feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 17 } + +vmwNsxTLoadBalancerFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for LoadBalancer feature notifications. + " + ::= { vmwNsxTLoadBalancerFeaturePrefix 0 } + +vmwNsxTLoadBalancerDLBStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The distributed load balancer service vmwNsxTDataCenterEntityId is down. + + This notification is sent once when the down state is first detected. + + Action required: + On ESXi host node, invoke the NSX CLI command `get load-balancer + <lb-uuid> status`. + If 'Conflict LSP' is reported, please check whether this LSP is attached + to other load balancer service. Please check whether this conflict is + acceptable. + If 'Not Ready LSP' is reported, please check the status of this LSP by + invoking NSX CLI command `get logical-switch-port status`. + " + ::= { vmwNsxTLoadBalancerFeature 17 } + +vmwNsxTLoadBalancerDLBStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The distributed load balancer service vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 18 } + +vmwNsxTLoadBalancerLBCPUVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of load balancer vmwNsxTDataCenterEntityId is vmwNsxTDataCenterSystemResourceUsage% + which is higher than the very high threshold of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + If the load balancer CPU utilization is higher than vmwNsxTDataCenterSystemUsageThreshold%, + the workload is too high for this load balancer. Rescale the load balancer + service by changing the load balancer size from small to medium or from + medium to large. If the CPU utilization of this load balancer is still high, + consider adjusting the Edge appliance form factor size or moving load + balancer services to other Edge nodes for the applicable workload. + " + ::= { vmwNsxTLoadBalancerFeature 1 } + +vmwNsxTLoadBalancerLBCPUVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU utilization of load balancer vmwNsxTDataCenterEntityId is vmwNsxTDataCenterSystemResourceUsage% + which is lower than the very high threshold of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 2 } + +vmwNsxTLoadBalancerLBEdgeCapacityInUseHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The usage of load balancer service in Edge node vmwNsxTDataCenterEntityId is high. + The threshold is vmwNsxTDataCenterSystemUsageThreshold%. + + This notification is sent once when the high usage state is first detected. + + Action required: + If multiple LB instances have been configurerd in this Edge node, deploy a + new Edge node and move some LB instances to that new Edge node. If only a + single LB instance (small/medium/etc) has been configured in an Edge node of + same size (small/medium/etc), deploy a new Edge of bigger size and move the + LB instance to that new Edge node. + " + ::= { vmwNsxTLoadBalancerFeature 3 } + +vmwNsxTLoadBalancerLBEdgeCapacityInUseHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The usage of load balancer service in Edge node vmwNsxTDataCenterEntityId is below + the threshold of vmwNsxTDataCenterSystemUsageThreshold% for a sufficient number + of samples over 2 minutes. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 4 } + +vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The usage of pool members in Edge node vmwNsxTDataCenterEntityId is very high. + The threshold is vmwNsxTDataCenterSystemUsageThreshold%. + + This notification is sent once when the high usage state is first detected. + + Action required: + Deploy a new Edge node and move the load balancer service from existing Edge + nodes to the newly deployed Edge node. + " + ::= { vmwNsxTLoadBalancerFeature 5 } + +vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The usage of pool members in Edge node vmwNsxTDataCenterEntityId is below + the threshold of vmwNsxTDataCenterSystemUsageThreshold% for a sufficient number + of samples over 2 minutes. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 6 } + +vmwNsxTLoadBalancerLBStatusDegraded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The load balancer service vmwNsxTDataCenterEntityId is degraded. + + This notification is sent once when the degraded state is first detected. + + Action required: + For centralized load balancer: + On standby Edge node, check load balancer status by invoking the NSX CLI + command `get load-balancer <lb-uuid> status`. If the LB-State of load + balancer service is not_ready or there is no output, make the Edge node + enter maintenance mode, then exit maintenance mode. + For distributed load balancer: + 1. Get detailed status by invoking NSX-T API GET + /policy/api/v1/infra/lb-services/<LBService>/detailed-status?source=realtime + 2. From API output, find ESXi host reporting a non-zero instance_number + with status NOT_READY or CONFLICT. + 3. On ESXi host node, invoke the NSX CLI command `get load-balancer + <lb-uuid> status`. + If 'Conflict LSP'is reported, please check whether this LSP is attached + to other load balancer service. Please check whether this conflict is + acceptable. + If 'Not Ready LSP' is reported, please check the status of this LSP by + invoking NSX CLI command `get logical-switch-port status`. + " + ::= { vmwNsxTLoadBalancerFeature 15 } + +vmwNsxTLoadBalancerLBStatusDegradedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The load balancer service vmwNsxTDataCenterEntityId is not degraded. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 16 } + +vmwNsxTLoadBalancerLBStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The load balancer service vmwNsxTDataCenterEntityId is down. + + Action required: + Verify whether the load balancer service in the Edge node is running. + If the status of load balancer service is not ready, make the Edge + node enter maintenance mode, then exit maintenance mode. If the status + of load balancer is still not recovered, please check whether there + are any error log in /var/log/syslog. + " + ::= { vmwNsxTLoadBalancerFeature 7 } + +vmwNsxTLoadBalancerLBStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The noad balancer service vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 8 } + +vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemory NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeId + } + STATUS current + DESCRIPTION + "The load balancer configuration vmwNsxTDataCenterEntityId is not realized, + due to high memory usage on Edge node vmwNsxTDataCenterTransportNodeId. + + Action required: + Prefer defining small and medium sized load balancers over large sized load balancers. + Spread out load balancer services among the available Edge nodes. + Reduce number of Virtual Servers defined. + " + ::= { vmwNsxTLoadBalancerFeature 19 } + +vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemoryClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTransportNodeId + } + STATUS current + DESCRIPTION + "The load balancer configuration vmwNsxTDataCenterEntityId is realized on vmwNsxTDataCenterTransportNodeId. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 20 } + +vmwNsxTLoadBalancerPoolStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The load balancer pool vmwNsxTDataCenterEntityId status is down. + + Action required: + Consult the load balancer pool to determine which members are down by + invoking the NSX CLI command + `get load-balancer <lb-uuid> pool <pool-uuid> status` + or NSX API GET + /policy/api/v1/infra/lb-services/<lb-service-id>/lb-pools/<lb-pool-id>/detailed-status + If DOWN or UNKNOWN is reported, please verify the pool member. + Check network connectivity from the load balancer to the impacted pool members. + Validate application health of each pool member. Also validate the health + of each pool member using the configured monitor. When the health of the + member is established, the pool member status is updated to healthy based + on the 'Rise Count' configuration in the monitor. + Remediate the issue by rebooting the pool member or make the Edge node + enter maintenance mode, then exit maintenance mode. + " + ::= { vmwNsxTLoadBalancerFeature 9 } + +vmwNsxTLoadBalancerPoolStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The load balancer pool vmwNsxTDataCenterEntityId status is up + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 10 } + +vmwNsxTLoadBalancerVirtualServerStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The load balancer virtual server vmwNsxTDataCenterEntityId is down. + + Action required: + Consult the load balancer pool to determine its status and verify its + configuration. If incorrectly configured, reconfigure it and remove the + load balancer pool from the virtual server then re-add it to the + virtual server again. + " + ::= { vmwNsxTLoadBalancerFeature 11 } + +vmwNsxTLoadBalancerVirtualServerStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The load balancer virtual server vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTLoadBalancerFeature 12 } + +-- ********************************************************** +-- ManagerHealth feature event notifications +-- ********************************************************** + +vmwNsxTManagerHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the ManagerHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 1 } + +vmwNsxTManagerHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for ManagerHealth feature notifications. + " + ::= { vmwNsxTManagerHealthFeaturePrefix 0 } + +vmwNsxTManagerHealthDuplicateIPAddress NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDuplicateIPAddress + } + STATUS current + DESCRIPTION + "Manager node vmwNsxTDataCenterEntityId IP address vmwNsxTDataCenterDuplicateIPAddress is + currently being used by another device in the network. + + Action required: + 1. Determine which device is using the Manager's IP address + and assign the device a new IP address. Note, reconfiguring + the Manager to use a new IP address is not supported. + 2. Ensure the static IP address pool/DHCP server is configured correctly. + 3. Correct the IP address of the device if it is manually assigned. + " + ::= { vmwNsxTManagerHealthFeature 17 } + +vmwNsxTManagerHealthDuplicateIPAddressClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDuplicateIPAddress + } + STATUS current + DESCRIPTION + "The device using the IP address assigned to Manager node + vmwNsxTDataCenterEntityId appears to no longer be using vmwNsxTDataCenterDuplicateIPAddress. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 18 } + +vmwNsxTManagerHealthManagerConfigDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /config has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of rising disk + usage by the NSX Datastore service under the /config/corfu directory. + + Action required: + Please run the following tool and contact GSS if any issues are reported + /opt/vmware/tools/support/inspect_checkpoint_issues.py + " + ::= { vmwNsxTManagerHealthFeature 13 } + +vmwNsxTManagerHealthManagerConfigDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /config has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 14 } + +vmwNsxTManagerHealthManagerConfigDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /config has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value + of vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of high disk usage + by the NSX Datastore service under the /config/corfu directory. + + Action required: + Please run the following tool and contact GSS if any issues are reported + /opt/vmware/tools/support/inspect_checkpoint_issues.py + " + ::= { vmwNsxTManagerHealthFeature 15 } + +vmwNsxTManagerHealthManagerConfigDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /config has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 16 } + +vmwNsxTManagerHealthManagerCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this + Manager node. Consider adjusting the Manager appliance form factor size. + " + ::= { vmwNsxTManagerHealthFeature 1 } + +vmwNsxTManagerHealthManagerCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 2 } + +vmwNsxTManagerHealthManagerCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this + Manager node. Consider adjusting the Manager appliance form factor size. + " + ::= { vmwNsxTManagerHealthFeature 3 } + +vmwNsxTManagerHealthManagerCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 4 } + +vmwNsxTManagerHealthManagerDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Examine the partition with high usage and see if there are any + unexpected large files that can be removed. + " + ::= { vmwNsxTManagerHealthFeature 9 } + +vmwNsxTManagerHealthManagerDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 10 } + +vmwNsxTManagerHealthManagerDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Examine the partition with high usage and see if there are any + unexpected large files that can be removed. + " + ::= { vmwNsxTManagerHealthFeature 11 } + +vmwNsxTManagerHealthManagerDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName + has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 12 } + +vmwNsxTManagerHealthManagerMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this + Manager node. Consider adjusting the Manager appliance form factor size. + " + ::= { vmwNsxTManagerHealthFeature 5 } + +vmwNsxTManagerHealthManagerMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 6 } + +vmwNsxTManagerHealthManagerMemoryUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the very + high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Please review the configuration, running services and sizing of this + Manager node. Consider adjusting the Manager appliance form factor size. + " + ::= { vmwNsxTManagerHealthFeature 7 } + +vmwNsxTManagerHealthManagerMemoryUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage on Manager node vmwNsxTDataCenterEntityId has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 8 } + +vmwNsxTManagerHealthOperationsDbDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /nonconfig has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of rising disk + usage by the NSX Datastore service under the /nonconfig/corfu directory. + + Action required: + Please run the following tool and contact GSS if any issues are reported + /opt/vmware/tools/support/inspect_checkpoint_issues.py --nonconfig + " + ::= { vmwNsxTManagerHealthFeature 19 } + +vmwNsxTManagerHealthOperationsDbDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /nonconfig has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 20 } + +vmwNsxTManagerHealthOperationsDbDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /nonconfig has reached + vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value + of vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of high disk usage + by the NSX Datastore service under the /nonconfig/corfu directory. + + Action required: + Please run the following tool and contact GSS if any issues are reported + /opt/vmware/tools/support/inspect_checkpoint_issues.py --nonconfig + " + ::= { vmwNsxTManagerHealthFeature 21 } + +vmwNsxTManagerHealthOperationsDbDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage for the Manager node disk partition /nonconfig has reached + vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of + vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 22 } + +vmwNsxTManagerHealthStorageError NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName + } + STATUS current + DESCRIPTION + "The following disk partition on the Manager node vmwNsxTDataCenterEntityId is in + read-only mode: vmwNsxTDataCenterDiskPartitionName + + Action required: + Examine the read-only partition to see if reboot resolves the issue + or the disk needs to be replaced. Contact GSS for more information. + " + ::= { vmwNsxTManagerHealthFeature 23 } + +vmwNsxTManagerHealthStorageErrorClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterDiskPartitionName + } + STATUS current + DESCRIPTION + "The following disk partition on the Manager node vmwNsxTDataCenterEntityId + has recovered from read-only mode: vmwNsxTDataCenterDiskPartitionName + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTManagerHealthFeature 24 } + +-- ********************************************************** +-- MTUCheck feature event notifications +-- ********************************************************** + +vmwNsxTMTUCheckFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the MTUCheck feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 42 } + +vmwNsxTMTUCheckFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for MTUCheck feature notifications. + " + ::= { vmwNsxTMTUCheckFeaturePrefix 0 } + +vmwNsxTMTUCheckGlobalRouterMTUTooBig NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The global router MTU configuration is bigger than MTU of switches in overlay Transport Zone which connects + to Tier0 or Tier1. Global router MTU value should be less than all switches MTU value by at least + a 100 as we require 100 quota for Geneve encapsulation. + + Action required: + 1. Navigate to System | Fabric | Settings | MTU Configuration Check | Inconsistent on the NSX UI to check + more mismatch details. + 2. Set the bigger MTU value on switches by invoking the NSX API + PUT /api/v1/host-switch-profiles/<host-switch-profile-id> with mtu in the + request body, or API PUT /api/v1/global-configs/SwitchingGlobalConfig + with physical_uplink_mtu in request body. + 3. Or set the smaller MTU value of global router configuration by invoking the NSX API PUT + /api/v1/global-configs/RoutingGlobalConfig with logical_uplink_mtu in the request body. + " + ::= { vmwNsxTMTUCheckFeature 3 } + +vmwNsxTMTUCheckGlobalRouterMTUTooBigClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The global router MTU is less than the MTU of overlay Transport Zone now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTMTUCheckFeature 4 } + +vmwNsxTMTUCheckMTUMismatchWithinTransportZone NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "MTU configuration mismatch between Transport Nodes (ESXi, KVM and Edge) attached to the same Transport Zone. + MTU values on all switches attached to the same Transport Zone not being consistent will cause + connectivity issues. + + Action required: + 1. Navigate to System | Fabric | Settings | MTU Configuration Check | Inconsistent on the NSX UI to check + more mismatch details. + 2. Set the same MTU value on all switches attached to the same Transport Zone + by invoking the NSX API PUT /api/v1/host-switch-profiles/<host-switch-profile-id> + with mtu in the request body, or API PUT /api/v1/global-configs/SwitchingGlobalConfig + with physical_uplink_mtu in request body. + " + ::= { vmwNsxTMTUCheckFeature 1 } + +vmwNsxTMTUCheckMTUMismatchWithinTransportZoneClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "All MTU values between Transport Nodes attached to the same Transport Zone are consistent now. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTMTUCheckFeature 2 } + +-- ********************************************************** +-- NAT feature event notifications +-- ********************************************************** + +vmwNsxTNATFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the NAT feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 46 } + +vmwNsxTNATFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for NAT feature notifications. + " + ::= { vmwNsxTNATFeaturePrefix 0 } + +vmwNsxTNATSNATPortUsageOnGatewayIsHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSNATIPAddress, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "SNAT ports usage on logical router vmwNsxTDataCenterEntityId for + SNAT IP vmwNsxTDataCenterSNATIPAddress has reached + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will + not be SNATed when usage reaches the maximum limit. + + Action required: + Log in as the admin user on Edge node and invoke the NSX CLI command + `get firewall <LR_INT_UUID> connection state` by using the right interface + uuid and check various SNAT mappings for the SNAT IP vmwNsxTDataCenterSNATIPAddress. + Check traffic flows going through the gateway is not a denial-of-service + attack or anomalous burst. If the traffic appears to be within + the normal load but the alarm threshold is hit, consider adding more + SNAT IP addresses to distribute the load or + route new traffic to another Edge node. + " + ::= { vmwNsxTNATFeature 1 } + +vmwNsxTNATSNATPortUsageOnGatewayIsHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSNATIPAddress, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "SNAT ports usage on logical router vmwNsxTDataCenterEntityId for SNAT IP vmwNsxTDataCenterSNATIPAddress + has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNATFeature 2 } + +-- ********************************************************** +-- NCPHealth feature event notifications +-- ********************************************************** + +vmwNsxTNCPHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the NCPHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 11 } + +vmwNsxTNCPHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for NCPHealth feature notifications. + " + ::= { vmwNsxTNCPHealthFeaturePrefix 0 } + +vmwNsxTNCPHealthNCPPluginDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Manager Node has detected the NCP is down or unhealthy. + + Action required: + To find the clusters which are having issues, please use the + NSX UI and navigate to the Alarms page. The Entity name value for + this alarm instance identifies the cluster name. Or invoke the + NSX API GET /api/v1/systemhealth/container-cluster/ncp/status + to fetch all cluster statuses and determine the name of any clusters + that report DOWN or UNKNOWN. Then on the NSX UI + Inventory | Container | Clusters page find the cluster by name and + click the Nodes tab which lists all Kubernetes and PAS cluster members. + For Kubernetes cluster: + 1. Check NCP Pod liveness by finding the K8s master node from all the + cluster members and log onto the master node. Then invoke the kubectl + command `kubectl get pods --all-namespaces`. If there is an issue with + the NCP Pod, please use kubectl logs command to check the issue and fix + the error. + 2. Check the connection between NCP and Kubernetes API server. The + NSX CLI can be used inside the NCP Pod to check this connection status + by invoking the following commands from the master VM. + `kubectl exec -it <NCP-Pod-Name> -n nsx-system bash` + `nsxcli` + `get ncp-k8s-api-server status` + If there is an issue with the connection, please check both the network + and NCP configurations. + 3. Check the connection between NCP and NSX Manager. The NSX CLI can be + used inside the NCP Pod to check this connection status by invoking the + following command from the master VM. + `kubectl exec -it <NCP-Pod-Name> -n nsx-system bash` + `nsxcli` + `get ncp-nsx status` + If there is an issue with the connection, please check both the network + and NCP configurations. + For PAS cluster: + 1. Check the network connections between virtual machines and fix any + network issues. + 2. Check the status of both nodes and services and fix crashed nodes + or services. Invoke the command `bosh vms` and `bosh instances -p` to + check the status of nodes and services. + " + ::= { vmwNsxTNCPHealthFeature 3 } + +vmwNsxTNCPHealthNCPPluginDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Manager Node has detected the NCP is up or healthy again. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNCPHealthFeature 4 } + +-- ********************************************************** +-- NodeAgentsHealth feature event notifications +-- ********************************************************** + +vmwNsxTNodeAgentsHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the NodeAgentsHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 12 } + +vmwNsxTNodeAgentsHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for NodeAgentsHealth feature notifications. + " + ::= { vmwNsxTNodeAgentsHealthFeaturePrefix 0 } + +vmwNsxTNodeAgentsHealthNodeAgentsDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The agents running inside the Node VM appear to be down. + + Action required: + For ESX: + 1. If Vmk50 is missing, refer to this Knowledge Base article + https://kb.vmware.com/s/article/67432. + 2. If Hyperbus 4094 is missing, restarting nsx-cfgagent or restarting the + container host VM may help. + 3. If container host VIF is blocked, check the connection to the Controller + to make sure all configurations are sent down. + 4. If nsx-cfg-agent has stopped, restart nsx-cfgagent. + For KVM: + 1. If Hyperbus namespace is missing, restarting the nsx-opsagent may help + recreate the namespace. + 2. If Hyperbus interface is missing inside the hyperbus namespace, + restarting the nsx-opsagent may help. + 3. If nsx-agent has stopped, restart nsx-agent. + For Both ESX and KVM: + 1. If the node-agent package is missing, check whether node-agent package + has been successfully installed in the container host vm. + 2. If the interface for node-agent in container host vm is down, check the + eth1 interface status inside the container host vm. + " + ::= { vmwNsxTNodeAgentsHealthFeature 3 } + +vmwNsxTNodeAgentsHealthNodeAgentsDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The agents inside the Node VM are running. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNodeAgentsHealthFeature 4 } + +-- ********************************************************** +-- NSXApplicationPlatformCommunication feature event notifications +-- ********************************************************** + +vmwNsxTNSXApplicationPlatformCommunicationFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the NSXApplicationPlatformCommunication feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 41 } + +vmwNsxTNSXApplicationPlatformCommunicationFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for NSXApplicationPlatformCommunication feature notifications. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeaturePrefix 0 } + +vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflow NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappMessagingLAGThreshold + } + STATUS current + DESCRIPTION + "The number of pending messages in the messaging topic Over Flow is above the + pending message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. + + Action required: + Add nodes and then scale up the NSX Application Platform cluster. If bottleneck can be attributed to a specific service, + for example, the analytics service, then scale up the specific service when the new nodes are added. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 7 } + +vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflowClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappMessagingLAGThreshold + } + STATUS current + DESCRIPTION + "The number of pending messages in the messaging topic Over Flow is below the pending + message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 8 } + +vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflow NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappMessagingLAGThreshold + } + STATUS current + DESCRIPTION + "The number of pending messages in the messaging topic Raw Flow is above the + pending message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. + + Action required: + Add nodes and then scale up the NSX Application Platform cluster. If the bottleneck can be attributed to a specific service, + for example, the analytics service, then scale up the specific service when the new nodes are added. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 11 } + +vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflowClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappMessagingLAGThreshold + } + STATUS current + DESCRIPTION + "The number of pending messages in the messaging topic Raw Flow is below the pending + message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 12 } + +vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId + } + STATUS current + DESCRIPTION + "The NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is disconnected + from the NSX management cluster. + + Action required: + Check whether the manager cluster certificate, manager node certificates, + kafka certificate and ingress certificate match on both NSX Manager and the + NSX Application Platform cluster. Check expiration dates of the above mentioned + certificates to make sure they are valid. Check the network connection between + NSX Manager and NSX Application Platform cluster and resolve any network connection failures. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 1 } + +vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnectedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId + } + STATUS current + DESCRIPTION + "The NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is reconnected + to the NSX management cluster. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 2 } + +vmwNsxTNSXApplicationPlatformCommunicationExpDisconnected NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The flow exporter on Transport node vmwNsxTDataCenterEntityId is disconnected from + the NSX Application Platform cluster's messaging broker. Data collection is affected. + + Action required: + Restart the messaging service if it is not running in the NSX Application + Platform cluster. Resolve the network connection failure between the Transport node + flow exporter and the NSX Application Platform cluster. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 13 } + +vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The flow exporter on Transport node vmwNsxTDataCenterEntityId has reconnected to + the NSX Application Platform cluster's messaging broker. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformCommunicationFeature 14 } + +-- ********************************************************** +-- NSXApplicationPlatformHealth feature event notifications +-- ********************************************************** + +vmwNsxTNSXApplicationPlatformHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the NSXApplicationPlatformHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 43 } + +vmwNsxTNSXApplicationPlatformHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for NSXApplicationPlatformHealth feature notifications. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeaturePrefix 0 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Analytics service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Analytics service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 1 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Analytics service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 2 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Analytics service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Analytics service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 3 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Analytics service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 4 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Analytics service is above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services or the Analytics service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 5 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Analytics service is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 6 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Analytics service is above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services or the Analytics service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 7 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Analytics service is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 8 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Analytics service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Analytics service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 9 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Analytics service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 10 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Analytics service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Analytics service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 11 } + +vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Analytics service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 12 } + +vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the System Load field of individual services to see + which service is under pressure. See if the load can be reduced. If more + computing power is required, click on the Scale Out button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 13 } + +vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 14 } + +vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the System Load field of individual services to see + which service is under pressure. See if the load can be reduced. If more + computing power is required, click on the Scale Out button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 15 } + +vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 16 } + +vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Storage field of individual services to see + which service is under pressure. See if the load can be reduced. If more + disk storage is required, click on the Scale Out button to request more resources. + If data storage service is under strain, another way is to click on the Scale Up button + to increase disk size. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 17 } + +vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 18 } + +vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Storage field of individual services to see + which service is under pressure. See if the load can be reduced. If more + disk storage is required, click on the Scale Out button to request more resources. + If data storage service is under strain, another way is to click on the Scale Up button + to increase disk size. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 19 } + +vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 20 } + +vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Memory field of individual services to see + which service is under pressure. See if the load can be reduced. If more + memory is required, click on the Scale Out button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 21 } + +vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 22 } + +vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Memory field of individual services to see + which service is under pressure. See if the load can be reduced. If more + memory is required, click on the Scale Out button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 23 } + +vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is + below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 24 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Configuration Database service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 31 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Configuration Database service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 32 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Configuration Database service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 33 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Configuration Database service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 34 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Configuration Database service is above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 35 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Configuration Database service is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 36 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Configuration Database service is above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 37 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Configuration Database service is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 38 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Configuration Database service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 109 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Configuration Database service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 110 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Configuration Database service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 39 } + +vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Configuration Database service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 40 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Data Storage service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Data Storage service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 41 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Data Storage service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 42 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Data Storage service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Data Storage service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 43 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Data Storage service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 44 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Data Storage service is above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out or scale up the data storage service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 45 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Data Storage service is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 46 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Data Storage service is above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out or scale up the data storage service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 47 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Data Storage service is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 48 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Data Storage service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Data Storage service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 49 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Data Storage service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 50 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Data Storage service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Data Storage service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 51 } + +vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Data Storage service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 52 } + +vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Messaging service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Messaging service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 53 } + +vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Messaging service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 54 } + +vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Messaging service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Messaging service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 55 } + +vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Messaging service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 56 } + +vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Messaging service is above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services or the Messaging service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 57 } + +vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Messaging service is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 58 } + +vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Messaging service is above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services or the Messaging service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 59 } + +vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Messaging service is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 60 } + +vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Messaging service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Messaging service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 61 } + +vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Messaging service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 62 } + +vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Messaging service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services or the Messaging service. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 63 } + +vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Messaging service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 64 } + +vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Metrics service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 97 } + +vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Metrics service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 98 } + +vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Metrics service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 99 } + +vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Metrics service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 100 } + +vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Metrics service is above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 101 } + +vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Metrics service is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 102 } + +vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Metrics service is above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 103 } + +vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Metrics service is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 104 } + +vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Metrics service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 105 } + +vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Metrics service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 106 } + +vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Metrics service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 107 } + +vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Metrics service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 108 } + +vmwNsxTNSXApplicationPlatformHealthNappStatusDegraded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId + } + STATUS current + DESCRIPTION + "NSX Application Platform cluster vmwNsxTDataCenterNappClusterId overall status is degraded. + + Action required: + Get more information from alarms of nodes and services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 117 } + +vmwNsxTNSXApplicationPlatformHealthNappStatusDegradedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId + } + STATUS current + DESCRIPTION + "NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is running properly. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 118 } + +vmwNsxTNSXApplicationPlatformHealthNappStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId + } + STATUS current + DESCRIPTION + "NSX Application Platform cluster vmwNsxTDataCenterNappClusterId overall status is down. + + Action required: + Get more information from alarms of nodes and services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 119 } + +vmwNsxTNSXApplicationPlatformHealthNappStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappClusterId + } + STATUS current + DESCRIPTION + "NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is running properly. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 120 } + +vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the System Load field of individual services to see + which service is under pressure. See if load can be reduced. If only a small minority + of the nodes have high CPU usage, by default, Kubernetes will reschedule services automatically. + If most nodes have high CPU usage and load cannot be reduced, click on the Scale Out + button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 65 } + +vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 66 } + +vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the System Load field of individual services to see + which service is under pressure. See if load can be reduced. If only a small minority + of the nodes have high CPU usage, by default, Kubernetes will reschedule services automatically. + If most nodes have high CPU usage and load cannot be reduced, click on the Scale Out + button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 67 } + +vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 68 } + +vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Storage field of individual services to see which service is + under pressure. Clean up unused data or log to free up disk resources + and see if the load can be reduced. If more disk storage is required, Scale Out the + service under pressure. If data storage service is under strain, another way is to + click on the Scale Up button to increase disk size. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 69 } + +vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below + the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 70 } + +vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above + the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Storage field of individual services to see + which service is under pressure. Clean up unused data or log to free up disk resources + and see if the load can be reduced. If more disk storage is required, Scale Out the + service under pressure. If data storage service is under strain, another way is to + click on the Scale Up button to increase disk size. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 71 } + +vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below + the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 72 } + +vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Memory field of individual services to see + which service is under pressure. See if load can be reduced. If only a small minority + of the nodes have high Memory usage, by default, Kubernetes will reschedule services automatically. + If most nodes have high Memory usage and load cannot be reduced, click on the Scale Out + button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 73 } + +vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 74 } + +vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services + and check the Memory field of individual services to see + which service is under pressure. See if load can be reduced. If only a small minority + of the nodes have high Memory usage, by default, Kubernetes will reschedule services automatically. + If most nodes have high Memory usage and load cannot be reduced, click on the Scale Out + button to request more resources. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 75 } + +vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName + is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 76 } + +vmwNsxTNSXApplicationPlatformHealthNodeStatusDegraded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName + } + STATUS current + DESCRIPTION + "NSX Application Platform node vmwNsxTDataCenterNappNodeName is degraded. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Resources to + check which node is degraded. Check network, memory and CPU usage of the node. + Reboot the node if it is a worker node. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 77 } + +vmwNsxTNSXApplicationPlatformHealthNodeStatusDegradedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName + } + STATUS current + DESCRIPTION + "NSX Application Platform node vmwNsxTDataCenterNappNodeName is running properly. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 78 } + +vmwNsxTNSXApplicationPlatformHealthNodeStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName + } + STATUS current + DESCRIPTION + "NSX Application Platform node vmwNsxTDataCenterNappNodeName is not running. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Resources to + check which node is down. Check network, memory and CPU usage of the node. + Reboot the node if it is a worker node. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 79 } + +vmwNsxTNSXApplicationPlatformHealthNodeStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappNodeName + } + STATUS current + DESCRIPTION + "NSX Application Platform node vmwNsxTDataCenterNappNodeName is running properly. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 80 } + +vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Platform Services service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 81 } + +vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Platform Services service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 82 } + +vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Platform Services service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 83 } + +vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The CPU usage of Platform Services service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 84 } + +vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Platform Services service is above the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 85 } + +vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Platform Services service is below the high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 86 } + +vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Platform Services service is above the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Clean up files not needed. + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 87 } + +vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The disk usage of Platform Services service is below the very high + threshold value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 88 } + +vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHigh NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Platform Services service is above the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 89 } + +vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHighClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Platform Services service is below the high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 90 } + +vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHi NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Platform Services service is above the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + Scale out all services. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 91 } + +vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHiClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSystemUsageThreshold + } + STATUS current + DESCRIPTION + "The memory usage of Platform Services service is below the very high threshold + value of vmwNsxTDataCenterSystemUsageThreshold%. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 92 } + +vmwNsxTNSXApplicationPlatformHealthServiceStatusDegraded NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappServiceName + } + STATUS current + DESCRIPTION + "Service vmwNsxTDataCenterNappServiceName is degraded. The service may still be able to reach a quorum while + pods associated with vmwNsxTDataCenterNappServiceName are not all stable. Resources consumed by these + unstable pods may be released. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service + is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which + specific service is degraded and the reason behind it. Invoke the following CLI command to restart + the degraded service if necessary: + `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` + Degraded services can function correctly but performance is sub-optimal. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 93 } + +vmwNsxTNSXApplicationPlatformHealthServiceStatusDegradedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappServiceName + } + STATUS current + DESCRIPTION + "Service vmwNsxTDataCenterNappServiceName is running properly. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 94 } + +vmwNsxTNSXApplicationPlatformHealthServiceStatusDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappServiceName + } + STATUS current + DESCRIPTION + "Service vmwNsxTDataCenterNappServiceName is not running. + + Action required: + In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service + is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which + specific service is down and the reason behind it. Invoke the following CLI command to restart + the degraded service: + `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 95 } + +vmwNsxTNSXApplicationPlatformHealthServiceStatusDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterNappServiceName + } + STATUS current + DESCRIPTION + "Service vmwNsxTDataCenterNappServiceName is running properly. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTNSXApplicationPlatformHealthFeature 96 } + +-- ********************************************************** +-- PasswordManagement feature event notifications +-- ********************************************************** + +vmwNsxTPasswordManagementFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the PasswordManagement feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 4 } + +vmwNsxTPasswordManagementFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for PasswordManagement feature notifications. + " + ::= { vmwNsxTPasswordManagementFeaturePrefix 0 } + +vmwNsxTPasswordManagementPasswordExpirationApproaching NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterUsername, + vmwNsxTDataCenterPasswordExpirationDays + } + STATUS current + DESCRIPTION + "The password for user vmwNsxTDataCenterUsername is approaching expiration in + vmwNsxTDataCenterPasswordExpirationDays days. + + Action required: + The password for the user vmwNsxTDataCenterUsername needs to be changed soon. For example, + to apply a new password to a user, invoke the following NSX API with a valid + password in the request body: PUT /api/v1/node/users/<userid> where <userid> + is the ID of the user. + " + ::= { vmwNsxTPasswordManagementFeature 1 } + +vmwNsxTPasswordManagementPasswordExpirationApproachingClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterUsername + } + STATUS current + DESCRIPTION + "The password for the user vmwNsxTDataCenterUsername has been changed successfully or + is no longer expired. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTPasswordManagementFeature 2 } + +vmwNsxTPasswordManagementPasswordExpired NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterUsername + } + STATUS current + DESCRIPTION + "The password for user vmwNsxTDataCenterUsername has expired. + + Action required: + The password for user vmwNsxTDataCenterUsername must be changed now to access the + system. For example, to apply a new password to a user, invoke the + following NSX API with a valid password in the request body: PUT + /api/v1/node/users/<userid> where <userid> is the ID of the user. If the + admin user (with <userid> 10000) password has expired, admin must login to + the system via SSH (if enabled) or console in order to change the password. + Upon entering the current expired password, admin will be prompted to enter + a new password. + " + ::= { vmwNsxTPasswordManagementFeature 3 } + +vmwNsxTPasswordManagementPasswordExpiredClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterUsername + } + STATUS current + DESCRIPTION + "The password for user vmwNsxTDataCenterUsername has been changed successfully or + is no longer expired. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTPasswordManagementFeature 4 } + +vmwNsxTPasswordManagementPasswordIsAboutToExpire NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterUsername, + vmwNsxTDataCenterPasswordExpirationDays + } + STATUS current + DESCRIPTION + "The password for user vmwNsxTDataCenterUsername is about to expire in + vmwNsxTDataCenterPasswordExpirationDays days. + + Action required: + Ensure the password for the user vmwNsxTDataCenterUsername is changed immediately. For + example, to apply a new password to a user, invoke the following NSX API + with a valid password in the request body: PUT /api/v1/node/users/<userid> + where <userid> is the ID of the user. + " + ::= { vmwNsxTPasswordManagementFeature 5 } + +vmwNsxTPasswordManagementPasswordIsAboutToExpireClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterUsername + } + STATUS current + DESCRIPTION + "The password for the user vmwNsxTDataCenterUsername has been changed successfully or + is no longer expired. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTPasswordManagementFeature 6 } + +-- ********************************************************** +-- Routing feature event notifications +-- ********************************************************** + +vmwNsxTRoutingFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the Routing feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 28 } + +vmwNsxTRoutingFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for Routing feature notifications. + " + ::= { vmwNsxTRoutingFeaturePrefix 0 } + +vmwNsxTRoutingBFDDownOnExternalInterface NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLrId, + vmwNsxTDataCenterPeerAddress, + vmwNsxTDataCenterSrId + } + STATUS current + DESCRIPTION + "In router vmwNsxTDataCenterLrId, BFD session for peer vmwNsxTDataCenterPeerAddress is down. + + Action required: + 1. Invoke the NSX CLI command `get logical-routers`. + 2. Switch to the service router vmwNsxTDataCenterSrId + 3. Invoke the NSX CLI command `ping vmwNsxTDataCenterPeerAddress` to verify the + connectivity. + " + ::= { vmwNsxTRoutingFeature 7 } + +vmwNsxTRoutingBFDDownOnExternalInterfaceClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLrId, + vmwNsxTDataCenterPeerAddress + } + STATUS current + DESCRIPTION + "In router vmwNsxTDataCenterLrId, BFD session for peer vmwNsxTDataCenterPeerAddress is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTRoutingFeature 8 } + +vmwNsxTRoutingBGPDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLrId, + vmwNsxTDataCenterBGPNeighborIP, + vmwNsxTDataCenterFailureReason, + vmwNsxTDataCenterSrId + } + STATUS current + DESCRIPTION + "In Router vmwNsxTDataCenterLrId, BGP neighbor vmwNsxTDataCenterEntityId (vmwNsxTDataCenterBGPNeighborIP) is down. + Reason: vmwNsxTDataCenterFailureReason. + + Action required: + 1. Invoke the NSX CLI command `get logical-routers`. + 2. Switch to service-router vmwNsxTDataCenterSrId. + If the reason indicates Network or config error - + 3. Invoke the NSX CLI command `get bgp neighbor summary` to check the + BGP neighbor status. + If the reason indicates `Edge is not ready`, check why edge is not in good state. + 4. Invoke the NSX CLI command `get edge-cluster status` to check reason why edge might be down. + 5. Invoke the NSX CLI commands `get bfd-config` and `get bfd-sessions` to check if BFD is running well. + 6. Check any edge health related alarms to get more information. + Check /var/log/syslog to see if there are any errors related to BGP + connectivity. + " + ::= { vmwNsxTRoutingFeature 1 } + +vmwNsxTRoutingBGPDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLrId, + vmwNsxTDataCenterBGPNeighborIP + } + STATUS current + DESCRIPTION + "In Router vmwNsxTDataCenterLrId, BGP neighbor vmwNsxTDataCenterEntityId (vmwNsxTDataCenterBGPNeighborIP) is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTRoutingFeature 2 } + +vmwNsxTRoutingOSPFNeighborWentDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterPeerAddress + } + STATUS current + DESCRIPTION + "OSPF neighbor vmwNsxTDataCenterPeerAddress moved from full to another state. + + Action required: + 1. Invoke the NSX CLI command `get logical-routers` to get the vrf id and + switch to TIER0 service router. + 2. Run `get ospf neighbor` to check the current state of this neighbor. If the + neighbor is not listed in the output, the neighbor has gone down or out of + the network. + 3. Invoke the NSX CLI command `ping <OSPF neighbor IP address>` to verify the + connectivity. + 4. Also, verify the configuration for both NSX and peer router to ensure that + timers and area-id match. + 5. Check /var/log/syslog to see if there are any errors related to connectivity. + " + ::= { vmwNsxTRoutingFeature 11 } + +vmwNsxTRoutingOSPFNeighborWentDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterPeerAddress + } + STATUS current + DESCRIPTION + "OSPF neighbor vmwNsxTDataCenterPeerAddress moved to full state. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTRoutingFeature 12 } + +vmwNsxTRoutingProxyARPNotConfiguredForServiceIP NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterServiceIP, + vmwNsxTDataCenterLrportId, + vmwNsxTDataCenterLrId + } + STATUS current + DESCRIPTION + "Proxy arp for Service IP vmwNsxTDataCenterServiceIP and Service entity vmwNsxTDataCenterEntityId + is not configured as the number of arp proxy entries generated due to overlap of + the Service IP with subnet of lrport vmwNsxTDataCenterLrportId on Router vmwNsxTDataCenterLrId has exceeded + the allowed threshold limit of 16384. + + This notification is sent once when the threshold limit is exceeded. + + Action required: + Reconfigure the Service IP vmwNsxTDataCenterServiceIP for the Service entity vmwNsxTDataCenterEntityId + or change the subnet of the lrport vmwNsxTDataCenterLrportId on Router vmwNsxTDataCenterLrId so that the proxy arp entries + generated due to the overlap between the Service IP and the subnet of lrport is less than + the allowed threshold limit of 16384. + " + ::= { vmwNsxTRoutingFeature 13 } + +vmwNsxTRoutingProxyARPNotConfiguredForServiceIPClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLrportId, + vmwNsxTDataCenterLrId + } + STATUS current + DESCRIPTION + "Proxy arp for Service entity vmwNsxTDataCenterEntityId is generated successfully as the + overlap of service Ip with subnet of lrport vmwNsxTDataCenterLrportId on Router vmwNsxTDataCenterLrId is + within the allowed limit of 16384 entries. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTRoutingFeature 14 } + +vmwNsxTRoutingRoutingDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "All BGP/BFD sessions are down. + + Action required: + Invoke the NSX CLI command `get logical-routers` to get the tier0 service router + and switch to this vrf, then invoke the following NSX CLI commands. + 1. `ping <BFD peer IP address>` to verify connectivity. + 2. `get bfd-config` and `get bfd-sessions` to check if BFD is running well. + 3. `get bgp neighbor summary` to check if BGP is running well. + Also check /var/log/syslog to see if there are any errors related to BGP + connectivity. + " + ::= { vmwNsxTRoutingFeature 9 } + +vmwNsxTRoutingRoutingDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "At least one BGP/BFD session up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTRoutingFeature 10 } + +vmwNsxTRoutingStaticRoutingRemoved NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLrId, + vmwNsxTDataCenterStaticAddress, + vmwNsxTDataCenterSrId + } + STATUS current + DESCRIPTION + "In router vmwNsxTDataCenterLrId, static route vmwNsxTDataCenterEntityId (vmwNsxTDataCenterStaticAddress) was removed because + BFD was down. + + Action required: + The static routing entry was removed because the BFD session was down. + 1. Invoke the NSX CLI command `get logical-routers`. + 2. Switch to the service-router vmwNsxTDataCenterSrId. + 3. Invoke the NSX CLI command `ping <BFD peer IP address>` to verify the + connectivity. + Also, verify the configuration in both NSX and the BFD peer to ensure that + timers have not been changed. + " + ::= { vmwNsxTRoutingFeature 5 } + +vmwNsxTRoutingStaticRoutingRemovedClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterLrId, + vmwNsxTDataCenterStaticAddress + } + STATUS current + DESCRIPTION + "In router vmwNsxTDataCenterLrId, static route vmwNsxTDataCenterEntityId (vmwNsxTDataCenterStaticAddress) was re-added as BFD + recovered. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTRoutingFeature 6 } + +-- ********************************************************** +-- TransportNodeHealth feature event notifications +-- ********************************************************** + +vmwNsxTTransportNodeHealthFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the TransportNodeHealth feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 18 } + +vmwNsxTTransportNodeHealthFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for TransportNodeHealth feature notifications. + " + ::= { vmwNsxTTransportNodeHealthFeaturePrefix 0 } + +vmwNsxTTransportNodeHealthLAGMemberDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "LACP reporting member down. + + Action required: + Check the connection status of LAG members on hosts. + 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | + Host Transport Nodes. + 2. In the Host Transport Nodes list, check the Node Status column. Find the + Transport node with the degraded or down Node Status. + 3. Select <transport node> | Monitor. Find the bond(uplink) which is + reporting degraded or down. + 4. Check the LACP member status details by logging into the failed host and + invoking `esxcli network vswitch dvs vmware lacp status get` on an ESXi + host or `ovs-appctl bond/show` and `ovs-appctl lacp/show` on a KVM host. + " + ::= { vmwNsxTTransportNodeHealthFeature 5 } + +vmwNsxTTransportNodeHealthLAGMemberDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "LACP reporting member up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTTransportNodeHealthFeature 6 } + +vmwNsxTTransportNodeHealthNVDSUplinkDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Uplink is going down. + + Action required: + Check the physical NICs' status of uplinks on hosts. + 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | + Host Transport Nodes. + 2. In the Host Transport Nodes list, check the Node Status column. Find the + Transport node with the degraded or down Node Status. + 3. Select <transport node> | Monitor. Check the status details of the + bond(uplink) which is reporting degraded or down. To avoid a degraded state, + ensure all uplink interfaces are connected and up regardless of whether they + are in use or not. + " + ::= { vmwNsxTTransportNodeHealthFeature 3 } + +vmwNsxTTransportNodeHealthNVDSUplinkDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Uplink is going up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTTransportNodeHealthFeature 4 } + +vmwNsxTTransportNodeHealthTransportNodeUplinkDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Uplink is going down. + + Action required: + Check the physical NICs' status of uplinks on hosts. + 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | + Host Transport Nodes. + 2. In the Host Transport Nodes list, check the Node Status column. Find the + Transport node with the degraded or down Node Status. + 3. Select <transport node> | Monitor. Check the status details of the + bond(uplink) which is reporting degraded or down. To avoid a degraded state, + ensure all uplink interfaces are connected and up regardless of whether they + are in use or not. + " + ::= { vmwNsxTTransportNodeHealthFeature 7 } + +vmwNsxTTransportNodeHealthTransportNodeUplinkDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "Uplink is going up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTTransportNodeHealthFeature 8 } + +-- ********************************************************** +-- VPN feature event notifications +-- ********************************************************** + +vmwNsxTVPNFeaturePrefix OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Notifications applicable to the VPN feature have this OID prefix." + ::= { vmwNsxTDataCenterNotifications 15 } + +vmwNsxTVPNFeature OBJECT-IDENTITY + STATUS current + DESCRIPTION + "Sub-identifier added to ensure the next-to-last sub-identifier is zero + for VPN feature notifications. + " + ::= { vmwNsxTVPNFeaturePrefix 0 } + +vmwNsxTVPNIPsecPolicyBasedSessionDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSessionDownReason + } + STATUS current + DESCRIPTION + "The policy based IPsec VPN session vmwNsxTDataCenterEntityId is down. + Reason: vmwNsxTDataCenterSessionDownReason. + + Action required: + Check IPsec VPN session configuration and resolve errors based on the + session down reason. + " + ::= { vmwNsxTVPNFeature 7 } + +vmwNsxTVPNIPsecPolicyBasedSessionDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The policy based IPsec VPN session vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTVPNFeature 8 } + +vmwNsxTVPNIPsecPolicyBasedTunnelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "One or more policy based IPsec VPN tunnels in session vmwNsxTDataCenterEntityId are down. + + Action required: + Check IPsec VPN session configuration and resolve errors based on the + tunnel down reason. + " + ::= { vmwNsxTVPNFeature 9 } + +vmwNsxTVPNIPsecPolicyBasedTunnelDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "All policy based IPsec VPN tunnels in session vmwNsxTDataCenterEntityId are up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTVPNFeature 10 } + +vmwNsxTVPNIPsecRouteBasedSessionDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterSessionDownReason + } + STATUS current + DESCRIPTION + "The route based IPsec VPN session vmwNsxTDataCenterEntityId is down. + Reason: vmwNsxTDataCenterSessionDownReason. + + Action required: + Check IPsec VPN session configuration and resolve errors based on the + session down reason. + " + ::= { vmwNsxTVPNFeature 11 } + +vmwNsxTVPNIPsecRouteBasedSessionDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The route based IPsec VPN session vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTVPNFeature 12 } + +vmwNsxTVPNIPsecRouteBasedTunnelDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterTunnelDownReason + } + STATUS current + DESCRIPTION + "The route based IPsec VPN tunnel in session vmwNsxTDataCenterEntityId is down. + Reason: vmwNsxTDataCenterTunnelDownReason. + + Action required: + Check IPsec VPN session configuration and resolve errors based on the + tunnel down reason. + " + ::= { vmwNsxTVPNFeature 13 } + +vmwNsxTVPNIPsecRouteBasedTunnelDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The route based IPsec VPN tunnel in session vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTVPNFeature 14 } + +vmwNsxTVPNIPsecServiceDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterServiceDownReason + } + STATUS current + DESCRIPTION + "The IPsec service vmwNsxTDataCenterEntityId is down. Reason: vmwNsxTDataCenterServiceDownReason. + + Action required: + 1. Disable and enable the IPsec service from NSX Manager UI. + 2. If the issue still persists, check syslog for error logs and contact + VMware support. + " + ::= { vmwNsxTVPNFeature 17 } + +vmwNsxTVPNIPsecServiceDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The IPsec service vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTVPNFeature 18 } + +vmwNsxTVPNL2VpnSessionDown NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The L2VPN session vmwNsxTDataCenterEntityId is down. + + Action required: + Check L2VPN session status for session down reason and resolve errors based + on the reason. + " + ::= { vmwNsxTVPNFeature 15 } + +vmwNsxTVPNL2VpnSessionDownClear NOTIFICATION-TYPE + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterEntityId + } + STATUS current + DESCRIPTION + "The L2VPN session vmwNsxTDataCenterEntityId is up. + + Action required: + None, receipt of this notification indicates event cleared. + " + ::= { vmwNsxTVPNFeature 16 } + +-- ********************************************************** +-- Conformance information +-- ********************************************************** + +vmwNsxTDataCenterConformance OBJECT IDENTIFIER ::= { vmwNSXsysMIB 2 } +vmwNsxTDataCenterCompliances OBJECT IDENTIFIER ::= { vmwNsxTDataCenterConformance 1 } +vmwNsxTDataCenterSMIBGroups OBJECT IDENTIFIER ::= { vmwNsxTDataCenterConformance 2 } + +-- ********************************************************** +-- Compliance statements +-- ********************************************************** + +vmwNsxTDataCenterBasicCompliance MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationGroup + } + ::= { vmwNsxTDataCenterCompliances 1 } + +vmwNsxTDataCenterNotificationInfoGroup OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterTimestamp, + vmwNsxTDataCenterFeatureName, + vmwNsxTDataCenterEventType, + vmwNsxTDataCenterEventSeverity, + vmwNsxTDataCenterNodeId, + vmwNsxTDataCenterNodeType, + vmwNsxTDataCenterApplianceAddress, + vmwNsxTDataCenterBGPNeighborIP, + vmwNsxTDataCenterCurrentGatewayState, + vmwNsxTDataCenterCurrentServiceState, + vmwNsxTDataCenterDHCPPoolUsage, + vmwNsxTDataCenterDHCPServerId, + vmwNsxTDataCenterDatapathResourceUsage, + vmwNsxTDataCenterDiskPartitionName, + vmwNsxTDataCenterDuplicateIPAddress, + vmwNsxTDataCenterEdgeNICName, + vmwNsxTDataCenterEdgeServiceName, + vmwNsxTDataCenterEntityId, + vmwNsxTDataCenterEventId, + vmwNsxTDataCenterFailureReason, + vmwNsxTDataCenterHeapType, + vmwNsxTDataCenterIntelligenceNodeId, + vmwNsxTDataCenterLicenseEditionType, + vmwNsxTDataCenterMempoolName, + vmwNsxTDataCenterPasswordExpirationDays, + vmwNsxTDataCenterPeerAddress, + vmwNsxTDataCenterPreviousGatewayState, + vmwNsxTDataCenterPreviousServiceState, + vmwNsxTDataCenterRxRingBufferOverflowPercentage, + vmwNsxTDataCenterServiceName, + vmwNsxTDataCenterSessionDownReason, + vmwNsxTDataCenterSrId, + vmwNsxTDataCenterStaticAddress, + vmwNsxTDataCenterSystemResourceUsage, + vmwNsxTDataCenterSystemUsageThreshold, + vmwNsxTDataCenterTunnelDownReason, + vmwNsxTDataCenterTxRingBufferOverflowPercentage, + vmwNsxTDataCenterUsername + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 1 } + +vmwNsxTDataCenterNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTAlarmManagementAlarmServiceOverloaded, + vmwNsxTAlarmManagementAlarmServiceOverloadedClear, + vmwNsxTAlarmManagementHeavyVolumeOfAlarms, + vmwNsxTAlarmManagementHeavyVolumeOfAlarmsClear, + vmwNsxTCertificatesCertificateExpirationApproaching, + vmwNsxTCertificatesCertificateExpirationApproachingClear, + vmwNsxTCertificatesCertificateExpired, + vmwNsxTCertificatesCertificateExpiredClear, + vmwNsxTCertificatesCertificateIsAboutToExpire, + vmwNsxTCertificatesCertificateIsAboutToExpireClear, + vmwNsxTCniHealthHyperbusManagerConnectionDown, + vmwNsxTCniHealthHyperbusManagerConnectionDownClear, + vmwNsxTDHCPPoolLeaseAllocationFailed, + vmwNsxTDHCPPoolLeaseAllocationFailedClear, + vmwNsxTDHCPPoolOverloaded, + vmwNsxTDHCPPoolOverloadedClear, + vmwNsxTDistributedFirewallDFWCPUUsageVeryHigh, + vmwNsxTDistributedFirewallDFWCPUUsageVeryHighClear, + vmwNsxTDistributedFirewallDFWMemoryUsageVeryHigh, + vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighClear, + vmwNsxTDNSForwarderDisabled, + vmwNsxTDNSForwarderDisabledClear, + vmwNsxTDNSForwarderDown, + vmwNsxTDNSForwarderDownClear, + vmwNsxTEdgeHealthEdgeCPUUsageHigh, + vmwNsxTEdgeHealthEdgeCPUUsageHighClear, + vmwNsxTEdgeHealthEdgeCPUUsageVeryHigh, + vmwNsxTEdgeHealthEdgeCPUUsageVeryHighClear, + vmwNsxTEdgeHealthEdgeDatapathConfigurationFailure, + vmwNsxTEdgeHealthEdgeDatapathConfigurationFailureClear, + vmwNsxTEdgeHealthEdgeDatapathCPUHigh, + vmwNsxTEdgeHealthEdgeDatapathCPUHighClear, + vmwNsxTEdgeHealthEdgeDatapathCPUVeryHigh, + vmwNsxTEdgeHealthEdgeDatapathCPUVeryHighClear, + vmwNsxTEdgeHealthEdgeDatapathCryptodrvDown, + vmwNsxTEdgeHealthEdgeDatapathCryptodrvDownClear, + vmwNsxTEdgeHealthEdgeDatapathMempoolHigh, + vmwNsxTEdgeHealthEdgeDatapathMempoolHighClear, + vmwNsxTEdgeHealthEdgeDiskUsageHigh, + vmwNsxTEdgeHealthEdgeDiskUsageHighClear, + vmwNsxTEdgeHealthEdgeDiskUsageVeryHigh, + vmwNsxTEdgeHealthEdgeDiskUsageVeryHighClear, + vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHigh, + vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHighClear, + vmwNsxTEdgeHealthEdgeMemoryUsageHigh, + vmwNsxTEdgeHealthEdgeMemoryUsageHighClear, + vmwNsxTEdgeHealthEdgeMemoryUsageVeryHigh, + vmwNsxTEdgeHealthEdgeMemoryUsageVeryHighClear, + vmwNsxTEdgeHealthEdgeNICLinkStatusDown, + vmwNsxTEdgeHealthEdgeNICLinkStatusDownClear, + vmwNsxTEdgeHealthEdgeNICOutOfReceiveBuffer, + vmwNsxTEdgeHealthEdgeNICOutOfReceiveBufferClear, + vmwNsxTEdgeHealthEdgeNICOutOfTransmitBuffer, + vmwNsxTEdgeHealthEdgeNICOutOfTransmitBufferClear, + vmwNsxTEndpointProtectionEAMStatusDown, + vmwNsxTEndpointProtectionEAMStatusDownClear, + vmwNsxTEndpointProtectionPartnerChannelDown, + vmwNsxTEndpointProtectionPartnerChannelDownClear, + vmwNsxTHighAvailabilityTier0GatewayFailover, + vmwNsxTHighAvailabilityTier0GatewayFailoverClear, + vmwNsxTHighAvailabilityTier1GatewayFailover, + vmwNsxTHighAvailabilityTier1GatewayFailoverClear, + vmwNsxTInfrastructureCommunicationEdgeTunnelsDown, + vmwNsxTInfrastructureCommunicationEdgeTunnelsDownClear, + vmwNsxTInfrastructureServiceEdgeServiceStatusChanged, + vmwNsxTInfrastructureServiceEdgeServiceStatusChangedClear, + vmwNsxTInfrastructureServiceEdgeServiceStatusDown, + vmwNsxTInfrastructureServiceEdgeServiceStatusDownClear, + vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnected, + vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnectedClear, + vmwNsxTIntelligenceHealthCPUUsageHigh, + vmwNsxTIntelligenceHealthCPUUsageHighClear, + vmwNsxTIntelligenceHealthCPUUsageVeryHigh, + vmwNsxTIntelligenceHealthCPUUsageVeryHighClear, + vmwNsxTIntelligenceHealthDataDiskPartitionUsageHigh, + vmwNsxTIntelligenceHealthDataDiskPartitionUsageHighClear, + vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHigh, + vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHighClear, + vmwNsxTIntelligenceHealthDiskUsageHigh, + vmwNsxTIntelligenceHealthDiskUsageHighClear, + vmwNsxTIntelligenceHealthDiskUsageVeryHigh, + vmwNsxTIntelligenceHealthDiskUsageVeryHighClear, + vmwNsxTIntelligenceHealthMemoryUsageHigh, + vmwNsxTIntelligenceHealthMemoryUsageHighClear, + vmwNsxTIntelligenceHealthMemoryUsageVeryHigh, + vmwNsxTIntelligenceHealthMemoryUsageVeryHighClear, + vmwNsxTIntelligenceHealthNodeStatusDegraded, + vmwNsxTIntelligenceHealthNodeStatusDegradedClear, + vmwNsxTLicensesLicenseExpired, + vmwNsxTLicensesLicenseExpiredClear, + vmwNsxTLicensesLicenseIsAboutToExpire, + vmwNsxTLicensesLicenseIsAboutToExpireClear, + vmwNsxTLoadBalancerLBCPUVeryHigh, + vmwNsxTLoadBalancerLBCPUVeryHighClear, + vmwNsxTLoadBalancerLBStatusDown, + vmwNsxTLoadBalancerLBStatusDownClear, + vmwNsxTLoadBalancerPoolStatusDown, + vmwNsxTLoadBalancerPoolStatusDownClear, + vmwNsxTLoadBalancerVirtualServerStatusDown, + vmwNsxTLoadBalancerVirtualServerStatusDownClear, + vmwNsxTManagerHealthDuplicateIPAddress, + vmwNsxTManagerHealthDuplicateIPAddressClear, + vmwNsxTManagerHealthManagerConfigDiskUsageHigh, + vmwNsxTManagerHealthManagerConfigDiskUsageHighClear, + vmwNsxTManagerHealthManagerConfigDiskUsageVeryHigh, + vmwNsxTManagerHealthManagerConfigDiskUsageVeryHighClear, + vmwNsxTManagerHealthManagerCPUUsageHigh, + vmwNsxTManagerHealthManagerCPUUsageHighClear, + vmwNsxTManagerHealthManagerCPUUsageVeryHigh, + vmwNsxTManagerHealthManagerCPUUsageVeryHighClear, + vmwNsxTManagerHealthManagerDiskUsageHigh, + vmwNsxTManagerHealthManagerDiskUsageHighClear, + vmwNsxTManagerHealthManagerDiskUsageVeryHigh, + vmwNsxTManagerHealthManagerDiskUsageVeryHighClear, + vmwNsxTManagerHealthManagerMemoryUsageHigh, + vmwNsxTManagerHealthManagerMemoryUsageHighClear, + vmwNsxTManagerHealthManagerMemoryUsageVeryHigh, + vmwNsxTManagerHealthManagerMemoryUsageVeryHighClear, + vmwNsxTNCPHealthNCPPluginDown, + vmwNsxTNCPHealthNCPPluginDownClear, + vmwNsxTNodeAgentsHealthNodeAgentsDown, + vmwNsxTNodeAgentsHealthNodeAgentsDownClear, + vmwNsxTPasswordManagementPasswordExpirationApproaching, + vmwNsxTPasswordManagementPasswordExpirationApproachingClear, + vmwNsxTPasswordManagementPasswordExpired, + vmwNsxTPasswordManagementPasswordExpiredClear, + vmwNsxTPasswordManagementPasswordIsAboutToExpire, + vmwNsxTPasswordManagementPasswordIsAboutToExpireClear, + vmwNsxTRoutingBFDDownOnExternalInterface, + vmwNsxTRoutingBFDDownOnExternalInterfaceClear, + vmwNsxTRoutingBGPDown, + vmwNsxTRoutingBGPDownClear, + vmwNsxTRoutingRoutingDown, + vmwNsxTRoutingRoutingDownClear, + vmwNsxTRoutingStaticRoutingRemoved, + vmwNsxTRoutingStaticRoutingRemovedClear, + vmwNsxTTransportNodeHealthLAGMemberDown, + vmwNsxTTransportNodeHealthLAGMemberDownClear, + vmwNsxTTransportNodeHealthNVDSUplinkDown, + vmwNsxTTransportNodeHealthNVDSUplinkDownClear, + vmwNsxTVPNIPsecPolicyBasedSessionDown, + vmwNsxTVPNIPsecPolicyBasedSessionDownClear, + vmwNsxTVPNIPsecPolicyBasedTunnelDown, + vmwNsxTVPNIPsecPolicyBasedTunnelDownClear, + vmwNsxTVPNIPsecRouteBasedSessionDown, + vmwNsxTVPNIPsecRouteBasedSessionDownClear, + vmwNsxTVPNIPsecRouteBasedTunnelDown, + vmwNsxTVPNIPsecRouteBasedTunnelDownClear, + vmwNsxTVPNL2VpnSessionDown, + vmwNsxTVPNL2VpnSessionDownClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 2 } + +vmwNsxTDataCenterBasicCompliance2 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2 + } + ::= { vmwNsxTDataCenterCompliances 2 } + +vmwNsxTDataCenterNotificationInfoGroup2 OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterBGPSourceIP, + vmwNsxTDataCenterRemoteSiteId, + vmwNsxTDataCenterRemoteSiteName, + vmwNsxTDataCenterSiteId, + vmwNsxTDataCenterSiteName + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 3 } + +vmwNsxTDataCenterNotificationGroup2 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTEdgeHealthStorageError, + vmwNsxTEdgeHealthStorageErrorClear, + vmwNsxTFederationLmToLmSynchronizationError, + vmwNsxTFederationLmToLmSynchronizationErrorClear, + vmwNsxTFederationLmToLmSynchronizationWarning, + vmwNsxTFederationLmToLmSynchronizationWarningClear, + vmwNsxTFederationRtepBGPDown, + vmwNsxTFederationRtepBGPDownClear, + vmwNsxTManagerHealthOperationsDbDiskUsageHigh, + vmwNsxTManagerHealthOperationsDbDiskUsageHighClear, + vmwNsxTManagerHealthOperationsDbDiskUsageVeryHigh, + vmwNsxTManagerHealthOperationsDbDiskUsageVeryHighClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 4 } + +vmwNsxTDataCenterBasicCompliance3 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3 + } + ::= { vmwNsxTDataCenterCompliances 3 } + +vmwNsxTDataCenterNotificationInfoGroup3 OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterLrId, + vmwNsxTDataCenterManagerNodeName, + vmwNsxTDataCenterRxMisses, + vmwNsxTDataCenterRxProcessed, + vmwNsxTDataCenterTransportNodeAddress, + vmwNsxTDataCenterTransportNodeName, + vmwNsxTDataCenterTxMisses, + vmwNsxTDataCenterTxProcessed + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 5 } + +vmwNsxTDataCenterNotificationGroup3 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTCommunicationManagementChannelToTransportNodeDown, + vmwNsxTCommunicationManagementChannelToTransportNodeDownClear, + vmwNsxTCommunicationManagementChannelToTransportNodeDownLg, + vmwNsxTCommunicationManagementChannelToTransportNodeDownLgClear, + vmwNsxTCommunicationManagerControlChannelDown, + vmwNsxTCommunicationManagerControlChannelDownClear, + vmwNsxTFederationRtepConnectivityLost, + vmwNsxTFederationRtepConnectivityLostClear, + vmwNsxTManagerHealthStorageError, + vmwNsxTManagerHealthStorageErrorClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 6 } + +vmwNsxTDataCenterBasicCompliance4 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4 + } + ::= { vmwNsxTDataCenterCompliances 4 } + +vmwNsxTDataCenterNotificationInfoGroup4 OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterActiveGlobalManager, + vmwNsxTDataCenterActiveGlobalManagers, + vmwNsxTDataCenterApplianceFQDN, + vmwNsxTDataCenterCapacityDisplayName, + vmwNsxTDataCenterCapacityUsageCount, + vmwNsxTDataCenterCentralControlPlaneId, + vmwNsxTDataCenterDirectoryDomain, + vmwNsxTDataCenterDisplayedLicenseKey, + vmwNsxTDataCenterEdgeThreadName, + vmwNsxTDataCenterHostnameOrIPAddressWithPort, + vmwNsxTDataCenterIDSEventsCount, + vmwNsxTDataCenterLDAPServer, + vmwNsxTDataCenterLatencySource, + vmwNsxTDataCenterLatencyThreshold, + vmwNsxTDataCenterLatencyValue, + vmwNsxTDataCenterManagerNodeId, + vmwNsxTDataCenterMaxCapacityThreshold, + vmwNsxTDataCenterMaxIDSEventsAllowed, + vmwNsxTDataCenterMaxSupportedCapacityCount, + vmwNsxTDataCenterMinCapacityThreshold, + vmwNsxTDataCenterRemoteApplianceAddress, + vmwNsxTDataCenterRemoteManagerNodeId, + vmwNsxTDataCenterTimeoutInMinutes + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 7 } + +vmwNsxTDataCenterNotificationGroup4 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTAuditLogHealthAuditLogFileUpdateError, + vmwNsxTAuditLogHealthAuditLogFileUpdateErrorClear, + vmwNsxTAuditLogHealthRemoteLoggingServerError, + vmwNsxTAuditLogHealthRemoteLoggingServerErrorClear, + vmwNsxTCapacityMaximumCapacity, + vmwNsxTCapacityMaximumCapacityClear, + vmwNsxTCapacityMaximumCapacityThreshold, + vmwNsxTCapacityMaximumCapacityThresholdClear, + vmwNsxTCapacityMinimumCapacityThreshold, + vmwNsxTCapacityMinimumCapacityThresholdClear, + vmwNsxTCommunicationControlChannelToManagerNodeDown, + vmwNsxTCommunicationControlChannelToManagerNodeDownClear, + vmwNsxTCommunicationControlChannelToManagerNodeDownTooLong, + vmwNsxTCommunicationControlChannelToManagerNodeDownTooLongClear, + vmwNsxTCommunicationControlChannelToTransportNodeDown, + vmwNsxTCommunicationControlChannelToTransportNodeDownClear, + vmwNsxTCommunicationControlChannelToTransportNodeDownLong, + vmwNsxTCommunicationControlChannelToTransportNodeDownLongClear, + vmwNsxTCommunicationManagerClusterLatencyHigh, + vmwNsxTCommunicationManagerClusterLatencyHighClear, + vmwNsxTCommunicationManagerFQDNLookupFailure, + vmwNsxTCommunicationManagerFQDNLookupFailureClear, + vmwNsxTCommunicationManagerFQDNReverseLookupFailure, + vmwNsxTCommunicationManagerFQDNReverseLookupFailureClear, + vmwNsxTDistributedIDSIPSMaxEventsReached, + vmwNsxTDistributedIDSIPSMaxEventsReachedClear, + vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHigh, + vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHighClear, + vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHigh, + vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHighClear, + vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHigh, + vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHighClear, + vmwNsxTDistributedIDSIPSNSXIDPSEngineDown, + vmwNsxTDistributedIDSIPSNSXIDPSEngineDownClear, + vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHigh, + vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighClear, + vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHigh, + vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHighClear, + vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHigh, + vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHighClear, + vmwNsxTEdgeHealthDatapathThreadDeadlocked, + vmwNsxTEdgeHealthDatapathThreadDeadlockedClear, + vmwNsxTFederationGMToGMSplitBrain, + vmwNsxTFederationGMToGMSplitBrainClear, + vmwNsxTIdentityFirewallConnectivityToLDAPServerLost, + vmwNsxTIdentityFirewallConnectivityToLDAPServerLostClear, + vmwNsxTIdentityFirewallErrorInDeltaSync, + vmwNsxTIdentityFirewallErrorInDeltaSyncClear, + vmwNsxTInfrastructureServiceServiceStatusUnknown, + vmwNsxTInfrastructureServiceServiceStatusUnknownClear, + vmwNsxTIntelligenceHealthStorageLatencyHigh, + vmwNsxTIntelligenceHealthStorageLatencyHighClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 8 } + +vmwNsxTDataCenterBasicCompliance5 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4, + vmwNsxTDataCenterNotificationGroup5 + } + ::= { vmwNsxTDataCenterCompliances 5 } + +vmwNsxTDataCenterNotificationGroup5 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTRoutingOSPFNeighborWentDown, + vmwNsxTRoutingOSPFNeighborWentDownClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 10 } + +vmwNsxTDataCenterBasicCompliance6 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationInfoGroup6, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4, + vmwNsxTDataCenterNotificationGroup5, + vmwNsxTDataCenterNotificationGroup6 + } + ::= { vmwNsxTDataCenterCompliances 6 } + +vmwNsxTDataCenterNotificationInfoGroup6 OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterLrportId, + vmwNsxTDataCenterServiceIP + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 11 } + +vmwNsxTDataCenterNotificationGroup6 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTRoutingProxyARPNotConfiguredForServiceIP, + vmwNsxTRoutingProxyARPNotConfiguredForServiceIPClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 12 } + +vmwNsxTDataCenterBasicCompliance7 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationInfoGroup6, + vmwNsxTDataCenterNotificationInfoGroup7, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4, + vmwNsxTDataCenterNotificationGroup5, + vmwNsxTDataCenterNotificationGroup6, + vmwNsxTDataCenterNotificationGroup7 + } + ::= { vmwNsxTDataCenterCompliances 7 } + +vmwNsxTDataCenterNotificationInfoGroup7 OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterIntentPath + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 13 } + +vmwNsxTDataCenterNotificationGroup7 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTIPAMIPBlockUsageVeryHigh, + vmwNsxTIPAMIPBlockUsageVeryHighClear, + vmwNsxTIPAMIPPoolUsageVeryHigh, + vmwNsxTIPAMIPPoolUsageVeryHighClear, + vmwNsxTLoadBalancerDLBStatusDown, + vmwNsxTLoadBalancerDLBStatusDownClear, + vmwNsxTLoadBalancerLBEdgeCapacityInUseHigh, + vmwNsxTLoadBalancerLBEdgeCapacityInUseHighClear, + vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHigh, + vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHighClear, + vmwNsxTLoadBalancerLBStatusDegraded, + vmwNsxTLoadBalancerLBStatusDegradedClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 14 } + +vmwNsxTDataCenterBasicCompliance8 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationInfoGroup7, + vmwNsxTDataCenterNotificationInfoGroup8, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4, + vmwNsxTDataCenterNotificationGroup5, + vmwNsxTDataCenterNotificationGroup6, + vmwNsxTDataCenterNotificationGroup7, + vmwNsxTDataCenterNotificationGroup8 + } + ::= { vmwNsxTDataCenterCompliances 8 } + +vmwNsxTDataCenterNotificationInfoGroup8 OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterDNSId, + vmwNsxTDataCenterDNSUpstreamIP, + vmwNsxTDataCenterFirewallHalfopenFlowUsage, + vmwNsxTDataCenterFirewallICMPFlowUsage, + vmwNsxTDataCenterFirewallIPFlowUsage, + vmwNsxTDataCenterFirewallUDPFlowUsage + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 15 } + +vmwNsxTDataCenterNotificationGroup8 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTDNSForwarderUpstreamServerTimeout, + vmwNsxTDNSForwarderUpstreamServerTimeoutClear, + vmwNsxTGatewayFirewallICMPFlowCountExceeded, + vmwNsxTGatewayFirewallICMPFlowCountExceededClear, + vmwNsxTGatewayFirewallICMPFlowCountHigh, + vmwNsxTGatewayFirewallICMPFlowCountHighClear, + vmwNsxTGatewayFirewallIPFlowCountExceeded, + vmwNsxTGatewayFirewallIPFlowCountExceededClear, + vmwNsxTGatewayFirewallIPFlowCountHigh, + vmwNsxTGatewayFirewallIPFlowCountHighClear, + vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceeded, + vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceededClear, + vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHigh, + vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHighClear, + vmwNsxTGatewayFirewallUDPFlowCountExceeded, + vmwNsxTGatewayFirewallUDPFlowCountExceededClear, + vmwNsxTGatewayFirewallUDPFlowCountHigh, + vmwNsxTGatewayFirewallUDPFlowCountHighClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 16 } + +vmwNsxTDataCenterBasicCompliance9 MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement VMWARE-NSX-MIB." + MODULE -- this module + MANDATORY-GROUPS { + vmwNsxTDataCenterNotificationInfoGroup, + vmwNsxTDataCenterNotificationInfoGroup2, + vmwNsxTDataCenterNotificationInfoGroup3, + vmwNsxTDataCenterNotificationInfoGroup4, + vmwNsxTDataCenterNotificationInfoGroup7, + vmwNsxTDataCenterNotificationInfoGroup8, + vmwNsxTDataCenterNotificationInfoGroup9, + vmwNsxTDataCenterNotificationGroup, + vmwNsxTDataCenterNotificationGroup2, + vmwNsxTDataCenterNotificationGroup3, + vmwNsxTDataCenterNotificationGroup4, + vmwNsxTDataCenterNotificationGroup5, + vmwNsxTDataCenterNotificationGroup6, + vmwNsxTDataCenterNotificationGroup7, + vmwNsxTDataCenterNotificationGroup8, + vmwNsxTDataCenterNotificationGroup9 + } + ::= { vmwNsxTDataCenterCompliances 9 } + +vmwNsxTDataCenterNotificationInfoGroup9 OBJECT-GROUP + OBJECTS { + vmwNsxTDataCenterAPICollectionPath, + vmwNsxTDataCenterCABundleAgeThreshold, + vmwNsxTDataCenterEdgeCryptoDrvName, + vmwNsxTDataCenterEdgeNodeSettingMismatchReason, + vmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReason, + vmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReason, + vmwNsxTDataCenterEdgevSphereLocationMismatchReason, + vmwNsxTDataCenterFirewallSNATPortsUsage, + vmwNsxTDataCenterFlowIdentifier, + vmwNsxTDataCenterFromGMPath, + vmwNsxTDataCenterGroupType, + vmwNsxTDataCenterManagerNodeIDS, + vmwNsxTDataCenterNICThroughput, + vmwNsxTDataCenterNICThroughputThreshold, + vmwNsxTDataCenterNappClusterId, + vmwNsxTDataCenterNappMessagingLAGThreshold, + vmwNsxTDataCenterNappNodeId, + vmwNsxTDataCenterNappNodeName, + vmwNsxTDataCenterNappServiceName, + vmwNsxTDataCenterQueueName, + vmwNsxTDataCenterQueueSize, + vmwNsxTDataCenterQueueSizeThreshold, + vmwNsxTDataCenterSNATIPAddress, + vmwNsxTDataCenterServiceDownReason, + vmwNsxTDataCenterServiceRouterId, + vmwNsxTDataCenterSyncIssueReason, + vmwNsxTDataCenterToGMPath, + vmwNsxTDataCenterTransportNodeId + } + STATUS current + DESCRIPTION + "These objects provide details in NSX-T Data Center event notifications." + ::= { vmwNsxTDataCenterSMIBGroups 17 } + +vmwNsxTDataCenterNotificationGroup9 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxTCertificatesCABundleUpdateRecommended, + vmwNsxTCertificatesCABundleUpdateRecommendedClear, + vmwNsxTCertificatesCABundleUpdateSuggested, + vmwNsxTCertificatesCABundleUpdateSuggestedClear, + vmwNsxTClusteringClusterDegraded, + vmwNsxTClusteringClusterDegradedClear, + vmwNsxTClusteringClusterUnavailable, + vmwNsxTClusteringClusterUnavailableClear, + vmwNsxTCommunicationManagementChannelToManagerNodeDown, + vmwNsxTCommunicationManagementChannelToManagerNodeDownClear, + vmwNsxTCommunicationManagementChannelToManagerNodeDownLong, + vmwNsxTCommunicationManagementChannelToManagerNodeDownLongClear, + vmwNsxTDistributedFirewallDFWSessionCountHigh, + vmwNsxTDistributedFirewallDFWSessionCountHighClear, + vmwNsxTDistributedFirewallDFWVmotionFailure, + vmwNsxTDistributedFirewallDFWVmotionFailureClear, + vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChanged, + vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChangedClear, + vmwNsxTEdgeEdgeNodeSettingsMismatch, + vmwNsxTEdgeEdgeNodeSettingsMismatchClear, + vmwNsxTEdgeEdgeVmvSphereSettingsMismatch, + vmwNsxTEdgeEdgeVmvSphereSettingsMismatchClear, + vmwNsxTEdgeEdgevSphereLocationMismatch, + vmwNsxTEdgeEdgevSphereLocationMismatchClear, + vmwNsxTEdgeHealthEdgeDatapathNICThroughputHigh, + vmwNsxTEdgeHealthEdgeDatapathNICThroughputHighClear, + vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHigh, + vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHighClear, + vmwNsxTEdgeHealthFailureDomainDown, + vmwNsxTEdgeHealthFailureDomainDownClear, + vmwNsxTFederationGMToGMLatencyWarning, + vmwNsxTFederationGMToGMLatencyWarningClear, + vmwNsxTFederationGMToGMSynchronizationError, + vmwNsxTFederationGMToGMSynchronizationErrorClear, + vmwNsxTFederationGMToGMSynchronizationWarning, + vmwNsxTFederationGMToGMSynchronizationWarningClear, + vmwNsxTFederationGMToLMLatencyWarning, + vmwNsxTFederationGMToLMLatencyWarningClear, + vmwNsxTFederationGMToLMSynchronizationError, + vmwNsxTFederationGMToLMSynchronizationErrorClear, + vmwNsxTFederationGMToLMSynchronizationWarning, + vmwNsxTFederationGMToLMSynchronizationWarningClear, + vmwNsxTFederationLMRestoreWhileConfigImportInProgress, + vmwNsxTFederationLMRestoreWhileConfigImportInProgressClear, + vmwNsxTFederationQueueOccupancyThresholdExceeded, + vmwNsxTFederationQueueOccupancyThresholdExceededClear, + vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemory, + vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemoryClear, + vmwNsxTMTUCheckGlobalRouterMTUTooBig, + vmwNsxTMTUCheckGlobalRouterMTUTooBigClear, + vmwNsxTMTUCheckMTUMismatchWithinTransportZone, + vmwNsxTMTUCheckMTUMismatchWithinTransportZoneClear, + vmwNsxTNATSNATPortUsageOnGatewayIsHigh, + vmwNsxTNATSNATPortUsageOnGatewayIsHighClear, + vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflow, + vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflowClear, + vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflow, + vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflowClear, + vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnected, + vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnectedClear, + vmwNsxTNSXApplicationPlatformCommunicationExpDisconnected, + vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectedClear, + vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHigh, + vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHigh, + vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHigh, + vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHigh, + vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHigh, + vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHigh, + vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHi, + vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHiClear, + vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHigh, + vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHigh, + vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHigh, + vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHigh, + vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHigh, + vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHigh, + vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHigh, + vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHigh, + vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHigh, + vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHi, + vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHiClear, + vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHi, + vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHiClear, + vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthNappStatusDegraded, + vmwNsxTNSXApplicationPlatformHealthNappStatusDegradedClear, + vmwNsxTNSXApplicationPlatformHealthNappStatusDown, + vmwNsxTNSXApplicationPlatformHealthNappStatusDownClear, + vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHigh, + vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHigh, + vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHigh, + vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthNodeStatusDegraded, + vmwNsxTNSXApplicationPlatformHealthNodeStatusDegradedClear, + vmwNsxTNSXApplicationPlatformHealthNodeStatusDown, + vmwNsxTNSXApplicationPlatformHealthNodeStatusDownClear, + vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHigh, + vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHigh, + vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHighClear, + vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHigh, + vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHigh, + vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHighClear, + vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHi, + vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHiClear, + vmwNsxTNSXApplicationPlatformHealthServiceStatusDegraded, + vmwNsxTNSXApplicationPlatformHealthServiceStatusDegradedClear, + vmwNsxTNSXApplicationPlatformHealthServiceStatusDown, + vmwNsxTNSXApplicationPlatformHealthServiceStatusDownClear, + vmwNsxTTransportNodeHealthTransportNodeUplinkDown, + vmwNsxTTransportNodeHealthTransportNodeUplinkDownClear, + vmwNsxTVPNIPsecServiceDown, + vmwNsxTVPNIPsecServiceDownClear + } + STATUS current + DESCRIPTION + "Group of objects describing event notifications emitted by + NSX-T Data Center. + " + ::= { vmwNsxTDataCenterSMIBGroups 18 } + +END diff --git a/MIBS/vmware/VMWARE-OBSOLETE-MIB b/MIBS/vmware/VMWARE-OBSOLETE-MIB new file mode 100644 index 0000000..ef3cc8e --- /dev/null +++ b/MIBS/vmware/VMWARE-OBSOLETE-MIB @@ -0,0 +1,578 @@ +-- ********************************************************** +-- Copyright 2008 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-OBSOLETE-MIB DEFINITIONS ::= BEGIN + + IMPORTS + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, + Counter32, Gauge32, Counter64, Integer32 + FROM SNMPv2-SMI + DisplayString + FROM SNMPv2-TC + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + vmwResources, vmwTraps, vmwObsolete, vmwNotifications + FROM VMWARE-ROOT-MIB + vmwESX + FROM VMWARE-PRODUCTS-MIB + vmwVmID, vmwVmConfigFilePath + FROM VMWARE-VMINFO-MIB + vmwMemory, vmwCPU + FROM VMWARE-RESOURCES-MIB; + + vmwObsoleteMIB MODULE-IDENTITY + LAST-UPDATED "200810151159Z" + 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 contains all previously published managed objects that have been made + obsolete. The mib preserves OID mappings such that backward compatiblity is maintained." + +REVISION "200810151159Z" +DESCRIPTION + "This is the first version of this mib module. Objects from VMWARE-RESOURCES-MIB, + VMWARE-TRAPS-MIB moved here." +::= { vmwObsolete 1 } + + +-- Originally defined in VMWARE-VMKERNEL-MIB +vmkLoaded OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Has the vmkernel been loaded? (yes/no)" + ::= { vmwESX 1 } + +-- Originally defined in VMWARE-RESOURCES-MIB +--vmwResources OBJECT IDENTIFIER ::= { vmware 3 } +--vmwCPU OBJECT IDENTIFIER ::= { vmwResources 1 } + +vmwCpuTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwCpuEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "CPU Usage table by virtual machine." + ::= { vmwCPU 2 } + +vmwCpuEntry OBJECT-TYPE + SYNTAX VmwCpuEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "A record for CPU usage by a single virtual machine." + INDEX { vmwCpuVMID } + ::= { vmwCpuTable 1 } + + VmwCpuEntry ::= SEQUENCE { + vmwCpuVMID Integer32, + vmwCpuShares Gauge32, + vmwCpuUtil Gauge32 + } + +vmwCpuVMID OBJECT-TYPE + SYNTAX Integer32 (0..1023) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "ID allocated to running vm by the vmkernel." + ::= { vmwCpuEntry 1 } + +vmwCpuShares OBJECT-TYPE + SYNTAX Gauge32 + UNITS "unknown" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Share of CPU allocated to vm by vmkernel." + ::= { vmwCpuEntry 2 } + +vmwCpuUtil OBJECT-TYPE + SYNTAX Gauge32 + UNITS "seconds" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Time the virtual machine has been running on the CPU (seconds)." + ::= { vmwCpuEntry 3 } + +vmwMemTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwMemEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "Table of memory usage by virtual machine." + ::= { vmwMemory 4 } + +vmwMemEntry OBJECT-TYPE + SYNTAX VmwMemEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "A record for memory usage by a single virtual machine." + INDEX { vmwMemVMID } + ::= { vmwMemTable 1 } + + VmwMemEntry ::= SEQUENCE { + vmwMemVMID Integer32, + vmwMemShares Gauge32, + vmwMemConfigured Gauge32, + vmwMemUtil Gauge32 + } + +vmwMemVMID OBJECT-TYPE + SYNTAX Integer32 (0..1023) + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "ID allocated to running vm by the vmkernel." + ::= { vmwMemEntry 1 } + +vmwMemShares OBJECT-TYPE + SYNTAX Gauge32 + UNITS "unknown" + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Shares of memory allocated to vm by vmkernel." + ::= { vmwMemEntry 2 } + +vmwMemConfigured OBJECT-TYPE + SYNTAX Gauge32 + UNITS "kilobytes" + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Amount of memory the vm was configured with. (KB)" + ::= { vmwMemEntry 3 } + +vmwMemUtil OBJECT-TYPE + SYNTAX Gauge32 + UNITS "kilobytes" + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Amount of memory utilized by the vm. (KB; instantaneous)" + ::= { vmwMemEntry 4 } + +vmwHBATable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwHbaEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "Disk adapter and target information table." + ::= { vmwResources 3 } + +vmwHBAEntry OBJECT-TYPE + SYNTAX VmwHbaEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "A record for a single hba on the machine." + INDEX { vmwHbaIdx } + ::= { vmwHBATable 1 } + + VmwHbaEntry ::= SEQUENCE { + vmwHbaIdx Integer32, + vmwHbaName DisplayString, + vmwHbaVMID Integer32, + vmwDiskShares Gauge32, + vmwNumReads Counter32, + vmwKbRead Counter32, + vmwNumWrites Counter32, + vmwKbWritten Counter32 + } + + +vmwHbaIdx OBJECT-TYPE + SYNTAX Integer32 (0..1023) + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "Index for HBA table @todo fix this!." + ::= { vmwHBAEntry 1 } + +vmwHbaName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "String describing the disk. Format: <devname#>:<tgt>:<lun> " + ::= { vmwHBAEntry 2 } + +vmwHbaVMID OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "ID assigned to running vm by the vmkernel." + ::= { vmwHBAEntry 3 } + +vmwDiskShares OBJECT-TYPE + SYNTAX Gauge32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Share of disk bandwidth allocated to this vm." + ::= { vmwHBAEntry 4 } + +vmwNumReads OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Number of reads to this disk since disk module was loaded." + ::= { vmwHBAEntry 5 } + +vmwKbRead OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Kilobytes read from this disk since disk module was loaded." + ::= { vmwHBAEntry 6 } + +vmwNumWrites OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Number of writes to this disk since disk module was loaded." + ::= { vmwHBAEntry 7 } + +vmwKbWritten OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Kilobytes written to this disk since disk module was loaded." + ::= { vmwHBAEntry 8 } + + +vmwNetTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwNetEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "Network adapter statistics." + ::= { vmwResources 4 } + +vmwNetEntry OBJECT-TYPE + SYNTAX VmwNetEntry + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "A record for a single nic on the machine." + INDEX { vmwNetIdx } + ::= { vmwNetTable 1 } + + VmwNetEntry ::= SEQUENCE { + vmwNetIdx Integer32, + vmwNetName DisplayString, + vmwNetVMID Integer32, + vmwNetIfAddr DisplayString, + vmwNetShares Gauge32, + vmwNetPktsTx Counter32, + vmwNetKbTx Counter32, + vmwNetPktsRx Counter32, + vmwNetKbRx Counter32, + vmwNetHCPktsTx Counter64, + vmwNetHCKbTx Counter64, + vmwNetHCPktsRx Counter64, + vmwNetHCKbRx Counter64 + } + + +vmwNetIdx OBJECT-TYPE + SYNTAX Integer32 (0..255) + MAX-ACCESS not-accessible + STATUS obsolete + DESCRIPTION + "Index for net table." + ::= { vmwNetEntry 1 } + +vmwNetName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "String describing the network adapter. Format: vmnic*" + ::= { vmwNetEntry 2 } + +vmwNetVMID OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "ID assigned to running vm by the vmkernel." + ::= { vmwNetEntry 3 } + +vmwNetIfAddr OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "MAC address of vm's virtual NIC." + ::= { vmwNetEntry 4 } + +vmwNetShares OBJECT-TYPE + SYNTAX Gauge32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Share of net bandwidth allocated to this vm." + ::= { vmwNetEntry 5 } + +vmwNetPktsTx OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Number of pkts transmitted on this NIC since network module was + loaded. Deprecated in favour of pktsHCTx." + ::= { vmwNetEntry 6 } + +vmwNetKbTx OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Kilobytes sent from this NIC since network module was loaded. + Deprecated in favour of kbHCTx." + ::= { vmwNetEntry 7 } + +vmwNetPktsRx OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Number of pkts received on this NIC since network module was loaded. + Deprecated in favour of pktsHCRx." + ::= { vmwNetEntry 8 } + +vmwNetKbRx OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Kilobytes received on this NIC since network module was loaded. + Deprecated in favour of kbHCRx." + ::= { vmwNetEntry 9 } + +-- +-- High Capacity Counter objects. These objects are all 64 bit version +-- of the above four counter objects. They have the same +-- basic semantics as their 32-bit counterparts, however, their syntax +-- has been extended to 64 bits. +-- + +vmwNetHCPktsTx OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Number of pkts transmitted on this NIC since network module was loaded." + ::= { vmwNetEntry 10 } + +vmwNetHCKbTx OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Kilobytes sent from this NIC since network module was loaded." + ::= { vmwNetEntry 11 } + +vmwNetHCPktsRx OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Number of pkts received on this NIC since network module was loaded." + ::= { vmwNetEntry 12 } + +vmwNetHCKbRx OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Kilobytes received on this NIC since network module was loaded." + ::= { vmwNetEntry 13 } + +-- VMWARE-TRAPS-MIB + +vpxdTrapType OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the trap type in the preceding traps." + ::= { vmwTraps 301 } + +vpxdHostName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the name of the host in the preceding traps." + ::= { vmwTraps 302 } + +vpxdVMName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the name of the VM in the preceding traps." + ::= { vmwTraps 303 } + +vpxdOldStatus OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the old status in the preceding traps." + ::= { vmwTraps 304 } + +vpxdNewStatus OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the new status in the preceding traps." + ::= { vmwTraps 305 } + +vpxdObjValue OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the current object value in the preceding traps." + ::= { vmwTraps 306 } + +-- obsolete notifications as originally published in VMWARE-TRAPS-MIB.mib + + +vmPoweredOn NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath } + STATUS obsolete + DESCRIPTION + "This trap is sent when a virtual machine is powered ON from a suspended + or a powered off state." + ::= { vmwNotifications 1 } + +vmPoweredOff NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath } + STATUS obsolete + DESCRIPTION + "This trap is sent when a virtual machine is powered OFF." + ::= { vmwNotifications 2 } + +vmHBLost NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath } + STATUS obsolete + DESCRIPTION + "This trap is sent when a virtual machine detects a loss in guest heartbeat." + ::= { vmwNotifications 3 } + +vmHBDetected NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath } + STATUS obsolete + DESCRIPTION + "This trap is sent when a virtual machine detects or regains the guest heartbeat." + ::= { vmwNotifications 4 } + +vmSuspended NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath } + STATUS obsolete + DESCRIPTION + "This trap is sent when a virtual machine is suspended." + ::= { vmwNotifications 5 } + +vpxdTrap NOTIFICATION-TYPE + OBJECTS { vpxdTrapType, vpxdHostName, vpxdVMName, vpxdNewStatus, + vpxdOldStatus, vpxdObjValue } + STATUS obsolete + DESCRIPTION + "This trap is sent when entity status changed." + ::= { vmwNotifications 201 } + + +-- conformance information + +vmwObsoleteMIBConformance +OBJECT IDENTIFIER ::= { vmwObsoleteMIB 2 } +vmwObsoleteMIBCompliances +OBJECT IDENTIFIER ::= { vmwObsoleteMIBConformance 1 } +vmwObsMIBGroups OBJECT IDENTIFIER ::= { vmwObsoleteMIBConformance 2 } + +vmwObsoleteObsoleteMIBCompliance MODULE-COMPLIANCE +STATUS obsolete +DESCRIPTION + "The compliance statement for entities which implement the + VMWARE-RESOURCE-MIB." +MODULE -- this module +MANDATORY-GROUPS { vmwObsoleteGroup, vmwOldVCNotificationGroup } +::= { vmwObsoleteMIBCompliances 3 } + +vmwObsoleteGroup OBJECT-GROUP + OBJECTS { + vmkLoaded, + vmwCpuShares, + vmwCpuUtil, + vmwMemShares, + vmwMemConfigured, + vmwMemUtil, + vmwHbaName, + vmwHbaVMID, + vmwDiskShares, + vmwNumReads, + vmwKbRead, + vmwNumWrites, + vmwKbWritten, + vmwNetName, + vmwNetVMID, + vmwNetIfAddr, + vmwNetShares, + vmwNetPktsTx, + vmwNetKbTx, + vmwNetPktsRx, + vmwNetKbRx, + vmwNetHCPktsTx, + vmwNetHCKbTx, + vmwNetHCPktsRx, + vmwNetHCKbRx, + vpxdTrapType, + vpxdHostName, + vpxdVMName, + vpxdOldStatus, + vpxdNewStatus, + vpxdObjValue + } + STATUS obsolete + DESCRIPTION + "These objects are no longer provided, see VMWARE-VMINFO-MIB for replacement." + ::= { vmwObsMIBGroups 2 } + +vmwOldVCNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vpxdTrap, + vmPoweredOn, + vmPoweredOff, + vmHBLost, + vmHBDetected, + vmSuspended + } + STATUS obsolete + DESCRIPTION + "Group of objects describing notifications (traps)." + ::= { vmwObsMIBGroups 3 } + +END diff --git a/MIBS/vmware/VMWARE-PRODUCTS-MIB b/MIBS/vmware/VMWARE-PRODUCTS-MIB new file mode 100644 index 0000000..53789b7 --- /dev/null +++ b/MIBS/vmware/VMWARE-PRODUCTS-MIB @@ -0,0 +1,115 @@ +-- ********************************************************** +-- Copyright 2007-2021 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-PRODUCTS-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + vmwOID, vmwProductSpecific + FROM VMWARE-ROOT-MIB; + +vmwProducts MODULE-IDENTITY + LAST-UPDATED "202104290000Z" + 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 MIB module provides the OID identifiers + which are returned from SNMPv2-MIB sysObjectId for + agents in specific VMware products. + " + REVISION "202104290000Z" + DESCRIPTION + "Add Horizon Cloud Connector sysObjectId value." + REVISION "201808300000Z" + DESCRIPTION + "Add vmwTunnelServer sysObjectId value." + REVISION "201806270000Z" + DESCRIPTION + "Add vmwVrops snmp agent's sysObjectId value." + 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." + REVISION "201109290000Z" + DESCRIPTION + "Add vmwVCOps snmp agent's sysObjectId value." + REVISION "200707300000Z" + DESCRIPTION + "The initial revision." + ::= { vmwProductSpecific 11 } + +vmwESX OBJECT IDENTIFIER + ::= { vmwProductSpecific 1 } + +vmwDVS OBJECT IDENTIFIER + ::= { vmwProductSpecific 2 } + +vmwVC OBJECT IDENTIFIER + ::= { vmwProductSpecific 3 } + +vmwServer OBJECT IDENTIFIER + ::= { vmwProductSpecific 4 } + +vmwVCOps OBJECT IDENTIFIER + ::= { vmwProductSpecific 5 } + +vmwVrops OBJECT IDENTIFIER + ::= { vmwProductSpecific 50 } + +vmwGenericAppliance OBJECT IDENTIFIER + ::= { vmwProductSpecific 6 } + +vmwEmbeddedVirtualCenterAppliance OBJECT IDENTIFIER + ::= { vmwProductSpecific 7 } + +vmwInfrastructureAppliance OBJECT IDENTIFIER + ::= { vmwProductSpecific 8 } + +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 } + +vmwTunnelServer OBJECT IDENTIFIER + ::= { vmwProductSpecific 250 } + +vmwHorizonCloudConnector OBJECT IDENTIFIER + ::= { vmwProductSpecific 350 } + +oidESX OBJECT IDENTIFIER + ::= { vmwOID 1 } + +END -- end of module VMWARE-PRODUCTS-MIB. diff --git a/MIBS/vmware/VMWARE-RESOURCES-MIB b/MIBS/vmware/VMWARE-RESOURCES-MIB new file mode 100644 index 0000000..d75e09e --- /dev/null +++ b/MIBS/vmware/VMWARE-RESOURCES-MIB @@ -0,0 +1,269 @@ +-- ********************************************************** +-- Copyright 2007-2011 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-RESOURCES-MIB DEFINITIONS ::= BEGIN + + IMPORTS + MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Gauge32, Integer32 + FROM SNMPv2-SMI + DisplayString + FROM SNMPv2-TC + MODULE-COMPLIANCE, OBJECT-GROUP + FROM SNMPv2-CONF + VmwSubsystemStatus + FROM VMWARE-TC-MIB + vmwResources + FROM VMWARE-ROOT-MIB; + + vmwResourcesMIB MODULE-IDENTITY + LAST-UPDATED "200810150000Z" + 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 instrumentation of ESX Hypervisor resources such + as cpu, memory, and disk." + +REVISION "200810150000Z" +DESCRIPTION + "All per-VM managed objects were moved to new managed objects in VMWARE-VMINFO MIB. + See VMWARE-OBSOLETE-RESOURCE-MIB for oid assignments in prior version of this mib module. + Add to comments the Managed Object Browser (MOB) URLs which provide + data this MIB module exposes." + +REVISION "200712270000Z" +DESCRIPTION + "This is the first revision in SMIv2 format. Prior version was published as SMIv1." +::= { vmwResources 10 } + +vmwCPU OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Information about physical CPU(s)" +::= { vmwResources 1 } + +vmwNumCPUs OBJECT-TYPE + SYNTAX Gauge32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of physical CPUs on the system." + ::= { vmwCPU 1 } + +-- Memory subtree + +vmwMemory OBJECT IDENTIFIER ::= { vmwResources 2 } + +vmwMemSize OBJECT-TYPE + SYNTAX Gauge32 + UNITS "kilobytes" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Amount of physical memory present on machine as provided by Hypervisor. + It is computed from the sum of vmwMemCOS plus unreserved property as + reported VIM subsystem. Unreserved is computed from hypervisor's total + number of memory pages. + + VIM Parent Container: https://esx.example.com/mob/?moid=memorySystem + VIM property: unreserved + MOB: https://esx.example.com/mob/?moid=memoryManagerSystem&doPath=consoleReservationInfo + + For reference here two other related VIM properties: + VIM property: memorySize + MOB: https://esx.example.com/mob/?moid=ha%2dhost&doPath=summary%2ehardware + + VIM property: totalMemory + MOB: https://esx.example.com/mob/?moid=ha%2dcompute%2dres&doPath=summary + " + ::= { vmwMemory 1 } + +vmwMemCOS OBJECT-TYPE + SYNTAX Gauge32 + UNITS "kilobytes" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This managed object reports memory allocated for COS, theConsole OS + (aka Service Console) which is a memory region carved out of physical + memory to boot a RedHat Linux distribution/provides device management + interface. + + Note that in the VMware ESXi product there is no COS so this will report 0. + + This managed object reports the amount of physical memory allocated to the COS. + VIM Parent Container: https://esx.example.com/mob/?moid=memorySystem + VIM property: serviceConsoleReserved + MOB: https://esx.example.com/mob/?moid=memoryManagerSystem&doPath=consoleReservationInfo + " + ::= { vmwMemory 2 } + +vmwMemAvail OBJECT-TYPE + SYNTAX Gauge32 + UNITS "kilobytes" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Amount of memory available to run Virutal Machines and to allocate for + hypervisor needs. It is computed by subtracting vmwMemCOS from + vmwMemSize. The result is the amount of memory available to VMs and to + the hypervisor. + + To get a more accurate view of memory available to VMs the following property + represents the amount of resources available for the root resource pool for running + virtual machines. + + VIM property: effectiveMemory + MOB: https://esx.example.com/mob/?moid=ha%2dcompute%2dres&doPath=summary + " + ::= { vmwMemory 3 } + + +-- Storage subtree + +vmwStorage OBJECT IDENTIFIER ::= { vmwResources 5 } +vmwHostBusAdapterNumber OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of entries in vmwHostBusAdapterTable." + ::= { vmwStorage 1 } + +vmwHostBusAdapterTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwHostBusAdapterEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Inventory of Host Bus Adatpers found in this system. + CLI: esxcfg-scsidevs -a + VIM Parent Container: https://esx.example.com/mob/?moid=storageSystem + VIM property: hostBusAdapter + MOB: https://esx.example.com/mob/?moid=storageSystem&doPath=storageDeviceInfo" + ::= { vmwStorage 2 } + +vmwHostBusAdapterEntry OBJECT-TYPE + SYNTAX VmwHostBusAdapterEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Details for this adapter." + INDEX { vmwHostBusAdapterIndex } + ::= { vmwHostBusAdapterTable 1 } + +VmwHostBusAdapterEntry ::= SEQUENCE +{ +vmwHostBusAdapterIndex Integer32, +vmwHbaDeviceName DisplayString, +vmwHbaBusNumber Integer32, +vmwHbaStatus VmwSubsystemStatus, +vmwHbaModelName DisplayString, +vmwHbaDriverName DisplayString, +vmwHbaPci DisplayString +} + +vmwHostBusAdapterIndex OBJECT-TYPE + SYNTAX Integer32 (0..1023) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "An arbitrary index assigned to this adapter." + ::= { vmwHostBusAdapterEntry 1 } + +vmwHbaDeviceName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The system device name for this host bus adapter." + ::= { vmwHostBusAdapterEntry 2 } + +vmwHbaBusNumber OBJECT-TYPE + SYNTAX Integer32 (-1|0..1023) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The host bus number. For unsuported HBA's reports -1." + ::= { vmwHostBusAdapterEntry 3 } + +vmwHbaStatus OBJECT-TYPE + SYNTAX VmwSubsystemStatus + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The operational status of the adapter." + ::= { vmwHostBusAdapterEntry 4 } + +vmwHbaModelName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The model name of the host bus adapter." + ::= { vmwHostBusAdapterEntry 5 } + +vmwHbaDriverName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The name of the driver." + ::= { vmwHostBusAdapterEntry 6 } + +vmwHbaPci OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The Peripheral Connect Interface (PCI) ID of the device." + ::= { vmwHostBusAdapterEntry 7 } + +-- Net subtree +-- See IF-MIB for details of network interfaces + + +-- conformance information +vmwResourceMIBConformance +OBJECT IDENTIFIER ::= { vmwResourcesMIB 2 } +vmwResourceMIBCompliances +OBJECT IDENTIFIER ::= { vmwResourceMIBConformance 1 } +vmwResMIBGroups OBJECT IDENTIFIER ::= { vmwResourceMIBConformance 2 } + +-- compliance statements +vmwResourceMIBCompliance MODULE-COMPLIANCE +STATUS current +DESCRIPTION + "The compliance statement for entities which implement the + VMWARE-RESOURCE-MIB." +MODULE -- this module +MANDATORY-GROUPS { vmwResourceGroup } +::= { vmwResourceMIBCompliances 2 } + +vmwResourceGroup OBJECT-GROUP + OBJECTS { + vmwNumCPUs, + vmwMemSize, + vmwMemCOS, + vmwMemAvail, + vmwHostBusAdapterNumber, + vmwHbaDeviceName, + vmwHbaBusNumber, + vmwHbaStatus, + vmwHbaModelName, + vmwHbaDriverName, + vmwHbaPci + } + STATUS current + DESCRIPTION + "These objects provide resource details." + ::= { vmwResMIBGroups 1 } + + +END diff --git a/MIBS/vmware/VMWARE-ROOT-MIB b/MIBS/vmware/VMWARE-ROOT-MIB new file mode 100644 index 0000000..344297e --- /dev/null +++ b/MIBS/vmware/VMWARE-ROOT-MIB @@ -0,0 +1,191 @@ +-- ********************************************************** +-- Copyright 2007-2017 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-ROOT-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-IDENTITY, enterprises + FROM SNMPv2-SMI; + +vmware MODULE-IDENTITY + LAST-UPDATED "202105170000Z" + 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 + "VMware managed object root assignements + This module defines the VMware SNMP MIB root + and its primary subtrees. + " + REVISION "202105170000Z" + DESCRIPTION + "Arc vmwHzecc defined." + REVISION "201808300000Z" + DESCRIPTION + "Arc vmwPerAppTunnel defined." + REVISION "201710300000Z" + DESCRIPTION + "Arc vmwNSXsys defined." + REVISION "201706070000Z" + DESCRIPTION + "Arc vmwHCX defined." + REVISION "201611030000Z" + DESCRIPTION + "Arc vmwNetworkInsight defined." + + REVISION "201601022000Z" + DESCRIPTION + "Arc vmwNsxManager defined." + + REVISION "201004020000Z" + DESCRIPTION + "Arc vmwDocumentation defined." + + REVISION "200707300000Z" + DESCRIPTION + "The initial revision. Prior version was released in + SMIv1 format as VMWARE-ROOT-MIB." + ::= { enterprises 6876 } + + +-- The parent oid of snmpv1 traps when sent in snmpv2/v3 +-- vmwNotifications OBJECT IDENTIFIER ::= { vmware 0 } +vmwNotifications OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Parent of all notifications (traps, informs)." + ::= { vmware 0 } + +vmwSystem OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Parent of all managed objects relating to system software identification." +::= { vmware 1 } + +vmwVirtMachines OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Parent of all managed objects relating to virtual machine inventory." +::= { vmware 2 } + +vmwResources OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Parent of all managed objects relating to resource utilization." +::= { vmware 3 } + +vmwProductSpecific OBJECT-IDENTITY +STATUS current +DESCRIPTION + "parent of objects specific to a given hardware/software product." +::= { vmware 4 } + +vmwLdap OBJECT-IDENTITY +STATUS current +DESCRIPTION + "VMware specific LDAP schema definitions." +::= { vmware 40 } + +vmwTraps OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Managed objects defined under this node are only visible in + notifications varbind lists and can not be polled." +::= { vmware 50 } + +vmwSRM OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Managed objects defined under this node are only visible in + 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 + "Assignments under this are no longer made." +::= { vmware 60 } + +vmwareAgentCapabilities OBJECT-IDENTITY +STATUS current +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 } + +vmwHCX OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Objects used by VMware HCX appliance and related components." +::= { vmware 110 } + +vmwNSXsys OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Objects used by VMware NSX systems and related components." +::= { vmware 120 } + +vmwPerAppTunnel OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Objects used by VMware PerApp Tunnel and related components." +::= { vmware 130 } + +vmwHzecc OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Objects used by VMware Horizon Cloud Connector and related components." +::= { vmware 140 } + +vmwExperimental OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Used for product testing and development." +::= { vmware 700 } + +vmwDocumentation OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Used in product documentation, examples." +::= { vmware 750 } + +vmwObsolete OBJECT-IDENTITY +STATUS current +DESCRIPTION + "Conformance, meta SMI oids for Obsolete smi assignements done under this arc." +::= { vmware 800 } + +END + diff --git a/MIBS/vmware/VMWARE-SRM-EVENT-MIB b/MIBS/vmware/VMWARE-SRM-EVENT-MIB new file mode 100644 index 0000000..0b47c91 --- /dev/null +++ b/MIBS/vmware/VMWARE-SRM-EVENT-MIB @@ -0,0 +1,299 @@ +-- ********************************************************** +-- Copyright 2012 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-SRM-EVENT-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + vmwSRM + FROM VMWARE-ROOT-MIB + DisplayString + FROM SNMPv2-TC; + + vmwSRMMIB MODULE-IDENTITY + LAST-UPDATED "201202070000Z" + 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 identifies Site Recovery Maager notifications (traps or inform)." + +REVISION "201202070000Z" +DESCRIPTION + "This is the first revision in SMIv2 format. Prior version was published as SMIv1. + Notifications were formerly in the VMWARE-SRM-TRAPS-1-0.MIB." +::= { vmwSRM 10 } + +vmwSrmNotification OBJECT IDENTIFIER ::= { vmwSRM 1 } + +vmwSRMevents OBJECT IDENTIFIER ::= {vmwSRM 0 } + +vmwSrmVmName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the name of the affected VM generating the trap." + ::= { vmwSrmNotification 1 } + +vmwSrmRecoveryName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the name of the Recovery Plan generating the trap." + ::= { vmwSrmNotification 2 } + +vmwSrmPromptString OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the text of the prompt generating the trap." + ::= { vmwSrmNotification 3 } + +vmwSrmRecoveryType OBJECT-TYPE + SYNTAX INTEGER { test(1), recovery(2), reprotect(3), cleanup(4) } + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the mode of execution for the the Recovery Plan." + ::= { vmwSrmNotification 4 } + +vmwSrmRecoveryState OBJECT-TYPE + SYNTAX INTEGER { uninitialized(1), running(2), paused(3), + cancelled(4), completed(5) } + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the state of execution for the the Recovery Plan." + ::= { vmwSrmNotification 5 } + +vmwSrmSiteString OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the name of the DR site that is causing the trap." + ::= { vmwSrmNotification 6 } + +vmwSrmVmUuid OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the UUID of the affected VM generating the trap." + ::= { vmwSrmNotification 7 } + +vmwSrmResult OBJECT-TYPE + SYNTAX INTEGER { success(1), failure(2), warning(3), + cancelled(4) } + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the result of running a Recovery Plan." + ::= { vmwSrmNotification 8 } + +vmwSrmCommandName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the name of a callout command executed during Recovery Plan execution." + ::= { vmwSrmNotification 9 } + +vmwareSrmRecoveryPlanExecuteTestBeginTrap NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan starts a test." + ::= { vmwSRMevents 1 } + +vmwareSrmRecoveryPlanExecuteTestEndEvent NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmResult } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan ends a test." + ::= { vmwSRMevents 2 } + +vmwareSrmRecoveryPlanExecuteBeginEvent NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan starts a recovery." + ::= { vmwSRMevents 3 } + +vmwareVmwSrmRecoveryPlanExecuteEndEvent NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmResult } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan ends a recovery." + ::= { vmwSRMevents 4 } + +vmwareVmwSrmRecoveryVmBeginEvent NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmVmName, vmwSrmVmUuid } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan starts recovering a VM." + ::= { vmwSRMevents 5 } + +vmwareSrmRecoveryVmEndEvent NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmVmName, vmwSrmVmUuid, vmwSrmResult } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan has finished recovering a VM." + ::= { vmwSRMevents 6 } + +vmwareSrmRecoveryPlanPromptDisplay NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmPromptString } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan requires user input before continuing." + ::= { vmwSRMevents 7 } + +vmwareSrmRecoveryPlanPromptResponse NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan no longer requires user input before continuing." + ::= { vmwSRMevents 8 } + +vmwareVmwSrmRecoveryPlanServerCommandBegin NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmCommandName } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan starts the execution of a command callout on SRM server's machine." + ::= { vmwSRMevents 9 } + +vmwareSrmRecoveryPlanServerCommandEnd NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmCommandName, vmwSrmResult } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan has finished the execution of a command callout on SRM server's machine." + ::= { vmwSRMevents 10 } + +vmwareSrmRecoveryPlanVmCommandBegin NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmCommandName, vmwSrmVmName, vmwSrmVmUuid } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan starts the execution of a command callout on a recovered VM." + ::= { vmwSRMevents 11 } + +vmwareSrmRecoveryPlanVmCommandEnd NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmCommandName, vmwSrmVmName, vmwSrmVmUuid, + vmwSrmResult } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan has finished the execution of a command callout on a recovered VM." + ::= { vmwSRMevents 12 } + +vmwareSrmRecoveryPlanExecuteReprotectBegin NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState } + STATUS current + DESCRIPTION + "This trap is sent when SRM starts the reprotect workflow for a Recovery Plan." + ::= { vmwSRMevents 13 } + +vmwareSrmRecoveryPlanExecuteReprotectEnd NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmResult } + STATUS current + DESCRIPTION + "This trap is sent when SRM has finished the reprotect workflow for a Recovery Plan." + ::= { vmwSRMevents 14 } + +vmwareVmwSrmRecoveryPlanExecuteCleanupBegin NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState } + STATUS current + DESCRIPTION + "This trap is sent when a Recovery Plan starts a test cleanup." + ::= { vmwSRMevents 15 } + +vmwSrmRecoveryPlanExecuteCleanupEnd NOTIFICATION-TYPE + OBJECTS { vmwSrmSiteString, vmwSrmRecoveryName, vmwSrmRecoveryType, + vmwSrmRecoveryState, vmwSrmResult } + STATUS current + DESCRIPTION + "This trap is sent a Recovery Plan ends a test cleanup." + ::= { vmwSRMevents 16 } + +-- conformance information +vmwSRMMIBConformance OBJECT IDENTIFIER ::= { vmwSRMMIB 2 } +vmwSRMMIBCompliances OBJECT IDENTIFIER ::= { vmwSRMMIBConformance 1 } +vmwSRMMIBGroups OBJECT IDENTIFIER ::= { vmwSRMMIBConformance 2 } + +-- compliance statements +vmwSRMMIBBasicCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement VMWARE-SRM-EVENT-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwSRMNotificationInfoGroup, vmwSRMNotificationGroup } + ::= { vmwSRMMIBCompliances 2 } + +vmwSRMNotificationInfoGroup OBJECT-GROUP + OBJECTS { + vmwSrmVmName, + vmwSrmRecoveryName, + vmwSrmPromptString, + vmwSrmRecoveryType, + vmwSrmRecoveryState, + vmwSrmSiteString, + vmwSrmVmUuid, + vmwSrmResult, + vmwSrmCommandName + } + STATUS current + DESCRIPTION + "These objects provide details in SRM notifications." + ::= { vmwSRMMIBGroups 1 } + +vmwSRMNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwareSrmRecoveryPlanExecuteTestBeginTrap, + vmwareSrmRecoveryPlanExecuteTestEndEvent, + vmwareSrmRecoveryPlanExecuteBeginEvent, + vmwareVmwSrmRecoveryPlanExecuteEndEvent, + vmwareVmwSrmRecoveryVmBeginEvent, + vmwareSrmRecoveryVmEndEvent, + vmwareSrmRecoveryPlanPromptDisplay, + vmwareSrmRecoveryPlanPromptResponse, + vmwareVmwSrmRecoveryPlanServerCommandBegin, + vmwareSrmRecoveryPlanServerCommandEnd, + vmwareSrmRecoveryPlanVmCommandBegin, + vmwareSrmRecoveryPlanVmCommandEnd, + vmwareSrmRecoveryPlanExecuteReprotectBegin, + vmwareSrmRecoveryPlanExecuteReprotectEnd, + vmwareVmwSrmRecoveryPlanExecuteCleanupBegin, + vmwSrmRecoveryPlanExecuteCleanupEnd + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps)." + ::= { vmwSRMMIBGroups 2 } + +END diff --git a/MIBS/vmware/VMWARE-SYSTEM-MIB b/MIBS/vmware/VMWARE-SYSTEM-MIB new file mode 100644 index 0000000..89fda6f --- /dev/null +++ b/MIBS/vmware/VMWARE-SYSTEM-MIB @@ -0,0 +1,130 @@ +-- ********************************************************** +-- Copyright 2007-2010 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-SYSTEM-MIB DEFINITIONS ::= BEGIN + + IMPORTS + MODULE-IDENTITY, OBJECT-TYPE + FROM SNMPv2-SMI + DisplayString + FROM SNMPv2-TC + MODULE-COMPLIANCE, OBJECT-GROUP + FROM SNMPv2-CONF + vmwSystem + FROM VMWARE-ROOT-MIB; + + vmwSystemMIB MODULE-IDENTITY + LAST-UPDATED "201008020000Z" + 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 for System Software identification" + +REVISION "201008020000Z" +DESCRIPTION + "Add vmwProdPatch managed object to report patch level" + +REVISION "200801120000Z" +DESCRIPTION + "Add to comments the Managed Object Browser (MOB) URLs which provide + data this MIB module exposes." + +REVISION "200712270000Z" +DESCRIPTION + "This is the first revision in SMIv2 format. One object + (vmwProdOID) has been dropped from the original SMIv1 version + as it duplicates sysObjectId from SNMPv2-MIB." + +::= { vmwSystem 10 } + +vmwProdName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This product's name. + VIM Property: AboutInfo.name + https://esx.example.com/mob/?moid=ServiceInstance&doPath=content%2eabout" + ::= { vmwSystem 1 } + +vmwProdVersion OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The product's version release identifier. Format is Major.Minor.Update + VIM Property: AboutInfo.version + https://esx.example.com/mob/?moid=ServiceInstance&doPath=content%2eabout" + ::= { vmwSystem 2 } + +-- { vmwSystem 3 } oid obsolete, do not reuse + +vmwProdBuild OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This identifier represents the most specific identifier. + VIM Property: AboutInfo.build + https://esx.example.com/mob/?moid=ServiceInstance&doPath=content%2eabout" + ::= { vmwSystem 4 } + +vmwProdUpdate OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This identifier represents the update level applied to this system. + VIM Property: Advanced Options key: Misc.HostAgentUpdateLevel + https://esx.example.com/mob/?moid=ha%2dadv%2doptions" + ::= { vmwSystem 5 } + +vmwProdPatch OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This identifier represents the patch level applied to this system. + VIM Property: None. + CLI: esxcli system version get" + ::= { vmwSystem 6 } + +-- conformance information +vmwSystemMIBConformance +OBJECT IDENTIFIER ::= { vmwSystemMIB 2 } +vmwSystemMIBCompliances +OBJECT IDENTIFIER ::= { vmwSystemMIBConformance 1 } +vmwSysMIBGroups OBJECT IDENTIFIER ::= { vmwSystemMIBConformance 2 } + +-- compliance statements +vmwSysMIBBasicCompliance MODULE-COMPLIANCE +STATUS current +DESCRIPTION + "The compliance statement for entities which implement the + VMWARE-SYSTEM-MIB." +MODULE -- this module +MANDATORY-GROUPS { vmwSystemGroup } +::= { vmwSystemMIBCompliances 2 } + +vmwSystemGroup OBJECT-GROUP + OBJECTS { + vmwProdName, + vmwProdVersion, + vmwProdBuild, + vmwProdUpdate, + vmwProdPatch + } + STATUS current + DESCRIPTION + "These objects uniquely identifies a given VMware system software image." + ::= { vmwSysMIBGroups 1 } + +END -- end of module VMWARE-SYSTEM-MIB. diff --git a/MIBS/vmware/VMWARE-TC-MIB b/MIBS/vmware/VMWARE-TC-MIB new file mode 100644 index 0000000..1a698ff --- /dev/null +++ b/MIBS/vmware/VMWARE-TC-MIB @@ -0,0 +1,188 @@ +-- ********************************************************** +-- Copyright 2007 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-TC-MIB DEFINITIONS ::= BEGIN + + IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + TEXTUAL-CONVENTION + FROM SNMPv2-TC + vmwSystem + FROM VMWARE-ROOT-MIB; + + vmwTcMIB MODULE-IDENTITY + LAST-UPDATED "200909050000Z" + 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 common datatypes for use in VMWARE + enterprise mib modules" +REVISION "200909050000Z" +DESCRIPTION + "Added VmwLongDisplayString" +REVISION "200712270000Z" +DESCRIPTION + "This is the first revision." +::= { vmwSystem 11 } + +VmwSubsystemTypes ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Define the various hardware subsystems." + SYNTAX INTEGER { unknown(1), chassis(2), powerSupply(3), fan(4), cpu(5), + memory(6), battery(7), temperatureSensor(8), + raidController(9), voltage(10) + } + +VmwCIMAlertTypes ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Primary classifications for alert messages." + SYNTAX INTEGER { other(1), communications(2), qos(3), processingError(4), + deviceAlert(5), environmentalAlert(6), modelChange(7), + securityAlert(8) + } + +VmwCIMAlertFormat ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Indication of what the Alerting Managed Element property is." + SYNTAX INTEGER { unknown(0), other(1), cimObjectPath(2) } + +VmwSubsystemStatus ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Define the state of a given subsystem if known." + SYNTAX INTEGER { unknown(1), normal(2), marginal(3), critical(4), failed(5) } + +VmwCIMSeverity ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Recommendation.ITU|X733.Perceived severity possible values." + SYNTAX INTEGER { unknown(0), other(1), information(2), warning(3), minor(4), major(5), critical(6), fatal(7) } + +VmwCimName ::= TEXTUAL-CONVENTION + DISPLAY-HINT "256a" + STATUS current + DESCRIPTION + "Contains a name of no more than 256 characters." + SYNTAX OCTET STRING (SIZE (0..256)) + +VmwConnectedState ::= TEXTUAL-CONVENTION + DISPLAY-HINT "7a" + STATUS current + DESCRIPTION + "Can hold one of the following values: 'true' or 'false' or 'unknown'." + SYNTAX OCTET STRING (SIZE (4..7)) + +VmwLongDisplayString ::= TEXTUAL-CONVENTION + DISPLAY-HINT "1a" + STATUS current + DESCRIPTION + "Represents textual information taken from the NVT ASCII + character set, as defined in pages 4, 10-11 of RFC 854. + + To summarize RFC 854, the NVT ASCII repertoire specifies: + + - the use of character codes 0-127 (decimal) + + - the graphics characters (32-126) are interpreted as + US ASCII + + - NUL, LF, CR, BEL, BS, HT, VT and FF have the special + meanings specified in RFC 854 + + - the other 25 codes have no standard interpretation + + - the sequence 'CR LF' means newline + + - the sequence 'CR NUL' means carriage-return + + - an 'LF' not preceded by a 'CR' means moving to the + same column on the next line. + + - the sequence 'CR x' for any x other than LF or NUL is + illegal. (Note that this also means that a string may + end with either 'CR LF' or 'CR NUL', but not with CR.) + + An object defined using this syntax may be of indefinite + length, as specified by the protocol, but displays may + choose to display only the first 4096 characters." + SYNTAX OCTET STRING + +VmwLongSnmpAdminString ::= TEXTUAL-CONVENTION + DISPLAY-HINT "4096t" + STATUS current + DESCRIPTION "This TC adapted from SnmpAdminString from SNMP-FRAMEWORK-MIB An + octet string containing administrative information, preferably + in human-readable form. + + To facilitate internationalization, this + information is represented using the ISO/IEC + IS 10646-1 character set, encoded as an octet + string using the UTF-8 transformation format + described in [RFC2279]. + + Since additional code points are added by + amendments to the 10646 standard from time + to time, implementations must be prepared to + encounter any code point from 0x00000000 to + 0x7fffffff. Byte sequences that do not + correspond to the valid UTF-8 encoding of a + code point or are outside this range are + prohibited. + + The use of control codes should be avoided. + + When it is necessary to represent a newline, + the control code sequence CR LF should be used. + + The use of leading or trailing white space should + be avoided. + + For code points not directly supported by user + interface hardware or software, an alternative + means of entry and display, such as hexadecimal, + may be provided. + + For information encoded in 7-bit US-ASCII, + the UTF-8 encoding is identical to the + US-ASCII encoding. + + UTF-8 may require multiple bytes to represent a + single character / code point; thus the length + of this object in octets may be different from + the number of characters encoded. Similarly, + size constraints refer to the number of encoded + octets, not the number of characters represented + by an encoding. + + Note that when this TC is used for an object that + is used or envisioned to be used as an index, then + a SIZE restriction MUST be specified so that the + number of sub-identifiers for any object instance + does not exceed the limit of 128, as defined by + [RFC3416]. + + Note that the size of an SnmpAdminString object is + measured in octets, not characters." + + SYNTAX OCTET STRING + +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 diff --git a/MIBS/vmware/VMWARE-TUNNEL-SERVER-AGENTCAP-MIB b/MIBS/vmware/VMWARE-TUNNEL-SERVER-AGENTCAP-MIB new file mode 100644 index 0000000..b5ae19c --- /dev/null +++ b/MIBS/vmware/VMWARE-TUNNEL-SERVER-AGENTCAP-MIB @@ -0,0 +1,156 @@ +-- ********************************************************** +-- Copyright 2018-2022 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMW-TUNNEL-SERVER-AGENTCAP-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + vmwareAgentCapabilities + FROM VMWARE-ROOT-MIB + AGENT-CAPABILITIES + FROM SNMPv2-CONF; + + +vmwTunnelServerAgentCapMIB MODULE-IDENTITY + LAST-UPDATED "202210280000Z" + 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: https://kb.vmware.com/s/article/1013445 + " + DESCRIPTION + "This module defines agent capabilities for deployed + VMware Workspace ONE Tunnel Server by release." + + REVISION "202210280000Z" + DESCRIPTION + "Capabilities for VMware Tunnel Server 22.12.00 release." + REVISION "202007210000Z" + DESCRIPTION + "Capabilities for VMware Tunnel Server 20.09.00 release." + REVISION "201910300000Z" + DESCRIPTION + "Capabilities for VMware Tunnel Server 4.2.0 release." + REVISION "201809040000Z" + DESCRIPTION + "Capabilities for VMware Tunnel Server 4.0.0 release." + ::= { vmwareAgentCapabilities 28 } + +vmwTunnelServerCapability OBJECT IDENTIFIER ::= + { vmwTunnelServerAgentCapMIB 1 } + + +-- +-- Applies to 22.12.00 Release +-- + + +vmwTunnelServer2022-221200 AGENT-CAPABILITIES + PRODUCT-RELEASE + "22.12.00" + STATUS current + DESCRIPTION + "Release 22.12.00 for VMware Workspace ONE Tunnel Server + supporting tunnel statistic and information queries. + " + REFERENCE + "https://www.vmware.com/products/workspace-one.html" + SUPPORTS VMWARE-TUNNEL-SERVER-MIB -- REVISION 202210280000Z + + INCLUDES { + vmwTunnelServerInfoGroup, + vmwTunnelServerInfoGroup2, + vmwTunnelServerInfoGroup3, + vmwTunnelServerStatGroup, + vmwTunnelServerStatGroup2, + vmwTunnelServerStatGroup3, + vmwTunnelServerStatGroup4 + } + ::= { vmwTunnelServerCapability 4 } + + +-- +-- Applies to 20.09.00 Release +-- + + +vmwTunnelServer2020-200900 AGENT-CAPABILITIES + PRODUCT-RELEASE + "20.09.00" + STATUS current + DESCRIPTION + "Release 20.09.00 for VMware Tunnel Server supporting tunnel + statistic and information queries. + " + REFERENCE + "https://www.vmware.com/products/workspace-one.html" + SUPPORTS VMWARE-TUNNEL-SERVER-MIB -- REVISION 202007210000Z + + INCLUDES { + vmwTunnelServerInfoGroup, + vmwTunnelServerInfoGroup2, + vmwTunnelServerStatGroup, + vmwTunnelServerStatGroup2, + vmwTunnelServerStatGroup3 + } + ::= { vmwTunnelServerCapability 3 } + + +-- +-- Applies to 4.2.0 Release +-- + + +vmwTunnelServer2019-420 AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.2.0" + STATUS current + DESCRIPTION + "Release 4.2.0 for VMware Tunnel Server supporting tunnel + statistic and information queries. + " + REFERENCE + "https://www.vmware.com/products/workspace-one.html" + SUPPORTS VMWARE-TUNNEL-SERVER-MIB -- REVISION 201910300000Z + + INCLUDES { + vmwTunnelServerStatGroup, + vmwTunnelServerInfoGroup, + vmwTunnelServerStatGroup2 + } + ::= { vmwTunnelServerCapability 2 } + + +-- +-- Applies to 4.0.0 Release +-- + + +vmwTunnelServer2018-400 AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.0.0" + STATUS current + DESCRIPTION + "Release 4.0.0 for VMware Tunnel Server supporting tunnel + statistic and information queries. + " + REFERENCE + "https://www.vmware.com/products/workspace-one.html" + SUPPORTS VMWARE-TUNNEL-SERVER-MIB -- REVISION 201808300000Z + + INCLUDES { + vmwTunnelServerStatGroup, + vmwTunnelServerInfoGroup + } + ::= { vmwTunnelServerCapability 1 } + + +END + + diff --git a/MIBS/vmware/VMWARE-TUNNEL-SERVER-MIB b/MIBS/vmware/VMWARE-TUNNEL-SERVER-MIB new file mode 100644 index 0000000..47907fd --- /dev/null +++ b/MIBS/vmware/VMWARE-TUNNEL-SERVER-MIB @@ -0,0 +1,770 @@ +-- ********************************************************** +-- Copyright 2018-2022 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-TUNNEL-SERVER-MIB DEFINITIONS ::= BEGIN + +IMPORTS + + OBJECT-TYPE, Unsigned32, Gauge32, Counter64, MODULE-IDENTITY + FROM SNMPv2-SMI + MODULE-COMPLIANCE, OBJECT-GROUP + FROM SNMPv2-CONF + TEXTUAL-CONVENTION, DateAndTime, TruthValue + FROM SNMPv2-TC + vmwPerAppTunnel + FROM VMWARE-ROOT-MIB + VmwLongDisplayString + FROM VMWARE-TC-MIB; + + +vmwTunnelServerMIB MODULE-IDENTITY + LAST-UPDATED "202210280000Z" + 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: https://kb.vmware.com/s/article/1013445 + " + DESCRIPTION + "This MIB file contains the definition of the SNMP + interface of VMware Workspace ONE Tunnel Server. + + Workspace ONE Tunnel is part of Workspace ONE by VMware: + https://www.vmware.com/products/workspace-one.html + + For more information about Workspace ONE Tunnel, please see + the latest documentation of VMware Workspace ONE UEM: + https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/ + " + + REVISION "202210280000Z" + DESCRIPTION + "Added counters vmwTunnelNumDevicesBlockedByZTNA, + vmwTunnelNumDevicesBlockedByAdm, + vmwTunnelNumConnBlockedByZTNA, vmwTunnelTLSPortSharing, + vmwTunnelZTNADTR, vmwTunnelZTNAPDTR, vmwTunnelNumZTNADTR, + vmwTunnelNumZTNAPDTR, vmwTunnelIsAppliance, + vmwTunnelIsContainer,vmwTunnelGeneveMetadata" + REVISION "202008210000Z" + DESCRIPTION + "Renamed whitelist counters to allowlist counters" + REVISION "202007210000Z" + DESCRIPTION + "Adding counters vmwTunnelLogLevel, + vmwTunnelNumDDoSRejected, + vmwTunnelNumConnSuccessful, + vmwTunnelNumConnFailed, + vmwTunnelNumBackEnds, vmwTunnelNumBackEndsDown, + vmwTunnelMemoryVirtual, vmwTunnelMemoryResident, + vmwTunnelMemoryShared, vmwTunnelProcessUpTime, + vmwTunnelServerStatus" + REVISION "201910300000Z" + DESCRIPTION + "Adding whitelist check failure counters" + REVISION "201808300000Z" + DESCRIPTION + "Initial revision" + + ::= { vmwPerAppTunnel 1 } + + +vmwTunnelServerStat OBJECT IDENTIFIER ::= { vmwTunnelServerMIB 1 } +vmwTunnelServerInfo OBJECT IDENTIFIER ::= { vmwTunnelServerMIB 2 } + + +-- +-- Textual-Conventions +-- + + +VmwTunnelUpDownState ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Can hold one of the following values: 1 = up or 2 = down." + SYNTAX INTEGER { up(1), down(2) } + +VmwTunnelCascadeModeState ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Can hold one of the following values: + 1 = off, 2 = frontend or 3 = backend." + SYNTAX INTEGER { off(1), frontend(2), backend(3) } + +VmwTunnelLogState ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Can hold one of the following values: + 0 = off, 1 = error, 2 = warning, 3 = info or 4 = debug." + SYNTAX INTEGER { off(0), error(1), warning(2), info(3), debug(4) } + + +-- +-- Statistic Objects +-- + + +vmwTunnelNumDevices OBJECT-TYPE + SYNTAX Gauge32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices currently connected." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 1 } + +vmwTunnelNumDevicesPeak OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "High watermark of number of devices connected. + The is the greatest number of devices connected + since Tunnel Server process restarted." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 2 } + +vmwTunnelNumConnections OBJECT-TYPE + SYNTAX Gauge32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of connections currently connected to hosts." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 3 } + +vmwTunnelNumConnectionsPeak OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "High watermark of number of connections to hosts. + This is the greatest number of outbound connections + to hosts since Tunnel Server process restarted." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 4 } + +vmwTunnelDownstreamBitRate OBJECT-TYPE + SYNTAX Unsigned32 + UNITS "kB/s" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Downstream bitrate of all traffic." + ::= { vmwTunnelServerStat 20 } + +vmwTunnelUpstreamBitRate OBJECT-TYPE + SYNTAX Unsigned32 + UNITS "kB/s" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Upstream bitrate of all traffic." + ::= { vmwTunnelServerStat 21 } + +vmwTunnelNumProxies OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of proxies defined in traffic rules." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 40 } + +vmwTunnelNumProxiesDown OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of proxies defined in traffic rules but + currently unreachable." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 41 } + +vmwTunnelNumTrafficRules OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of traffic rules defined." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 50 } + +vmwTunnelNumAllowListedDevices OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices in the allowlist." + DEFVAL { 0 } + ::= { vmwTunnelServerStat 60 } + +vmwTunnelNumClosedHandshakes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of TLS handshakes closed before authenticated. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 70 } + +vmwTunnelNumFailedHandshakes OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of TLS handshakes failed authentication. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 71 } + +vmwTunnelNumNotInAllowlist OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices failed to connect due to not in allowlist. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 72 } + +vmwTunnelNumNonCompliant OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices failed to connect due to non-compliant + status. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 73 } + +vmwTunnelNumNonManaged OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices failed to connect due to non-managed + status. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 74 } + +vmwTunnelNumDDoSRejected OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices rejected due to DDoS protection. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 75 } + +vmwTunnelNumDevicesBlockedByZTNA OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices rejected due to ZTNA policy. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 76 } + +vmwTunnelNumDevicesBlockedByAdm OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of devices blocked by admin in UEM Console. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 77 } + +vmwTunnelNumDevicesSinceStart OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of device connections since process restart. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 80 } + +vmwTunnelNumConnSuccessful OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of outbound connections successfully established. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 90 } + +vmwTunnelNumConnFailed OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of outbound connections failed. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 91 } + +vmwTunnelNumConnBlockedByZTNA OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of outbound connections blocked by ZTNA policy. + + Discontinuities in the value of this counter can occur at + re-initialization of the Tunnel Server process." + ::= { vmwTunnelServerStat 92 } + + +vmwTunnelNumBackEnds OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "In Cascade Mode, the number of IP addresses + resolved from back-end hostname. + + (Available on Cascade Mode front-ends only)" + DEFVAL { 0 } + ::= { vmwTunnelServerStat 100 } + +vmwTunnelNumBackEndsDown OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "In Cascade Mode, the number of back-ends that are + unresponsive to health check pinging. + + (Available on Cascade Mode front-ends only)" + DEFVAL { 0 } + ::= { vmwTunnelServerStat 101 } + +vmwTunnelMemoryVirtual OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel service virtual memory size." + + DEFVAL { 0 } + ::= { vmwTunnelServerStat 110 } + +vmwTunnelMemoryResident OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel service resident memory size." + + DEFVAL { 0 } + ::= { vmwTunnelServerStat 111 } + +vmwTunnelMemoryShared OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel service shared memory size." + + DEFVAL { 0 } + ::= { vmwTunnelServerStat 112 } + + +-- +-- Information Objects +-- + + +vmwTunnelServerVersion OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel server version." + ::= { vmwTunnelServerInfo 1 } + +vmwTunnelConsoleVersion OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Console server version." + ::= { vmwTunnelServerInfo 2 } + +vmwTunnelOperatingSystem OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel server machine operating system." + ::= { vmwTunnelServerInfo 3 } + +vmwTunnelAPIConnectivity OBJECT-TYPE + SYNTAX VmwTunnelUpDownState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel server to Console API connectivity." + ::= { vmwTunnelServerInfo 10 } + +vmwTunnelAWCMConnectivity OBJECT-TYPE + SYNTAX VmwTunnelUpDownState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel server to AWCM server connectivity." + ::= { vmwTunnelServerInfo 11 } + +vmwTunnelAPILastResponse OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Last HTTP response from Console API. + Value can be any HTTP response codes such as + '200 OK', '401 Unauthorized' etc." + ::= { vmwTunnelServerInfo 12 } + +vmwTunnelAWCMLastResponse OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Last HTTP response from AWCM server. + Value can be any HTTP response codes such as + '200 OK', '401 Unauthorized' etc." + ::= { vmwTunnelServerInfo 13 } + +vmwTunnelAPILastSyncTime OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The date and time the last Console API configuration + was downloaded." + ::= { vmwTunnelServerInfo 14 } + +vmwTunnelAWCMLastSyncTime OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The date and time the last AWCM message was received." + ::= { vmwTunnelServerInfo 15 } + +vmwTunnelProcessStartTime OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The date and time the vpnserv process restarted." + ::= { vmwTunnelServerInfo 20 } + + vmwTunnelProcessUpTime OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The number of seconds passed since the vpnserv process + restarted" + ::= { vmwTunnelServerInfo 21 } + +vmwTunnelCascadeMode OBJECT-TYPE + SYNTAX VmwTunnelCascadeModeState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server cascade mode." + ::= { vmwTunnelServerInfo 30 } + +vmwTunnelDeploymentMode OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server deployment mode." + ::= { vmwTunnelServerInfo 40 } + +vmwTunnelTrafficRulesEnabled OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server traffic rules mode." + ::= { vmwTunnelServerInfo 50 } + +vmwTunnelFIPSEnabled OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server FIPS mode." + ::= { vmwTunnelServerInfo 60 } + +vmwTunnelNSXEnabled OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server to NSX integration. + + See here for more details: + https://techzone.vmware.com/sites/default/files/ + vmware-tunnel-NSX-micro-segmentation-Integration.pdf" + ::= { vmwTunnelServerInfo 70 } + +vmwTunnelLogLevel OBJECT-TYPE + SYNTAX VmwTunnelLogState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server log level." + ::= { vmwTunnelServerInfo 80 } + + +vmwTunnelServerStatus OBJECT-TYPE + SYNTAX VmwTunnelUpDownState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server up/down status." + ::= { vmwTunnelServerInfo 90 } + +vmwTunnelTLSPortSharing OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "UAG TLS port sharing status." + ::= { vmwTunnelServerInfo 100 } + +vmwTunnelZTNADTR OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "ZTNA Device Traffic Rules validation enabled." + ::= { vmwTunnelServerInfo 110 } + +vmwTunnelZTNAPDTR OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "ZTNA Per Device Traffic Rules validation enabled." + ::= { vmwTunnelServerInfo 111 } + +vmwTunnelNumZTNADTR OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of ZTNA Device Traffic Rules in cache." + ::= { vmwTunnelServerInfo 112 } + +vmwTunnelNumZTNAPDTR OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of ZTNA Per Device Traffic Rules in cache." + ::= { vmwTunnelServerInfo 113 } + +vmwTunnelIsAppliance OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server is running in appliance mode." + ::= { vmwTunnelServerInfo 120 } + +vmwTunnelIsContainer OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Tunnel Server is running in container mode." + ::= { vmwTunnelServerInfo 130 } + +vmwTunnelGeneveMetadata OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Metadata is provided in Geneve Tunnel Options." + ::= { vmwTunnelServerInfo 140 } +-- +-- Groups +-- + + +vmwTunnelServerMIBConformance OBJECT IDENTIFIER + ::= { vmwTunnelServerMIB 3 } +vmwTunnelServerMIBCompliances OBJECT IDENTIFIER + ::= { vmwTunnelServerMIBConformance 1 } +vmwTunnelServerMIBGroups OBJECT IDENTIFIER + ::= { vmwTunnelServerMIBConformance 2 } + + +vmwTunnelServerStatGroup OBJECT-GROUP + OBJECTS { + vmwTunnelNumDevices, + vmwTunnelNumDevicesPeak, + vmwTunnelNumConnections, + vmwTunnelNumConnectionsPeak, + vmwTunnelDownstreamBitRate, + vmwTunnelUpstreamBitRate, + vmwTunnelNumProxies, + vmwTunnelNumProxiesDown, + vmwTunnelNumTrafficRules, + vmwTunnelNumAllowListedDevices, + vmwTunnelNumClosedHandshakes, + vmwTunnelNumFailedHandshakes, + vmwTunnelNumDevicesSinceStart + } + STATUS current + DESCRIPTION + "A collection of VMware Tunnel Server runtime values." + ::= { vmwTunnelServerMIBGroups 1 } + + + +vmwTunnelServerInfoGroup OBJECT-GROUP + OBJECTS { + vmwTunnelServerVersion, + vmwTunnelConsoleVersion, + vmwTunnelOperatingSystem, + vmwTunnelAPIConnectivity, + vmwTunnelAWCMConnectivity, + vmwTunnelAPILastResponse, + vmwTunnelAWCMLastResponse, + vmwTunnelAPILastSyncTime, + vmwTunnelAWCMLastSyncTime, + vmwTunnelProcessStartTime, + vmwTunnelCascadeMode, + vmwTunnelDeploymentMode, + vmwTunnelTrafficRulesEnabled, + vmwTunnelFIPSEnabled, + vmwTunnelNSXEnabled + } + STATUS current + DESCRIPTION + "A collection of VMware Tunnel Server runtime information." + ::= { vmwTunnelServerMIBGroups 2 } + + +vmwTunnelServerStatGroup2 OBJECT-GROUP + OBJECTS { + vmwTunnelNumNotInAllowlist, + vmwTunnelNumNonCompliant, + vmwTunnelNumNonManaged + } + STATUS current + DESCRIPTION + "A collection of VMware Tunnel Server runtime values." + ::= { vmwTunnelServerMIBGroups 3 } + +vmwTunnelServerInfoGroup2 OBJECT-GROUP + OBJECTS { + vmwTunnelLogLevel, + vmwTunnelProcessUpTime, + vmwTunnelServerStatus + } + STATUS current + DESCRIPTION + "A collection of VMware Tunnel Server runtime information." + ::= { vmwTunnelServerMIBGroups 4 } + + +vmwTunnelServerStatGroup3 OBJECT-GROUP + OBJECTS { + vmwTunnelNumDDoSRejected, + vmwTunnelNumConnSuccessful, + vmwTunnelNumConnFailed, + vmwTunnelNumBackEnds, + vmwTunnelNumBackEndsDown, + vmwTunnelMemoryVirtual, + vmwTunnelMemoryResident, + vmwTunnelMemoryShared + } + STATUS current + DESCRIPTION + "A collection of VMware Tunnel Server runtime values." + ::= { vmwTunnelServerMIBGroups 5 } + + +vmwTunnelServerInfoGroup3 OBJECT-GROUP + OBJECTS { + vmwTunnelTLSPortSharing, + vmwTunnelZTNADTR, + vmwTunnelZTNAPDTR, + vmwTunnelNumZTNADTR, + vmwTunnelNumZTNAPDTR, + vmwTunnelIsAppliance, + vmwTunnelIsContainer, + vmwTunnelGeneveMetadata + } + STATUS current + DESCRIPTION + "A collection of VMware Tunnel Server runtime information." + ::= { vmwTunnelServerMIBGroups 6 } + + +vmwTunnelServerStatGroup4 OBJECT-GROUP + OBJECTS { + vmwTunnelNumDevicesBlockedByZTNA, + vmwTunnelNumDevicesBlockedByAdm, + vmwTunnelNumConnBlockedByZTNA + } + STATUS current + DESCRIPTION + "A collection of VMware Tunnel Server runtime values." + ::= { vmwTunnelServerMIBGroups 7 } + + +-- +-- Compliance +-- + + +vmwTunnelServerMIBCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for VMware Tunnel Server SNMP + interface." + MODULE + MANDATORY-GROUPS { + vmwTunnelServerInfoGroup, + vmwTunnelServerInfoGroup2, + vmwTunnelServerInfoGroup3, + vmwTunnelServerStatGroup, + vmwTunnelServerStatGroup2, + vmwTunnelServerStatGroup3, + vmwTunnelServerStatGroup4 } + + ::= { vmwTunnelServerMIBCompliances 1 } + + +END diff --git a/MIBS/vmware/VMWARE-VA-AGENTCAP-MIB b/MIBS/vmware/VMWARE-VA-AGENTCAP-MIB new file mode 100644 index 0000000..97b2b83 --- /dev/null +++ b/MIBS/vmware/VMWARE-VA-AGENTCAP-MIB @@ -0,0 +1,1185 @@ +-- ********************************************************** +-- Copyright 2008-2022 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-VA-AGENTCAP-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + vmwareAgentCapabilities + FROM VMWARE-ROOT-MIB + AGENT-CAPABILITIES + FROM SNMPv2-CONF; +vmwVAAgentCapabilityMIB MODULE-IDENTITY + LAST-UPDATED "202209150000Z" + 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 module defines agent capabilities for deployed VMware Virtual Appliance agents + by release." + REVISION "202209150000Z" + DESCRIPTION + "Capabilities for VMware VSphere (Release 8.0) VCenter added." + + REVISION "202003270000Z" + DESCRIPTION + "Capabilities for VMware VSphere (Release 7.0) VCenter added." + + REVISION "201710130000Z" + DESCRIPTION + "Capabilities for VMware VSphere (Release 6.7) VCenter added." + + REVISION "201604220000Z" + DESCRIPTION + "Agent updates for 6.5 Release." + + REVISION "201501120000Z" + DESCRIPTION + "Capabilities for VMware Virtual Appliance, 6.0 release." + ::= { vmwareAgentCapabilities 5 } + +vmwVACapability OBJECT IDENTIFIER ::= { vmwVAAgentCapabilityMIB 1 } + + +-- +-- 2022 Release and follow up patch releases +-- + +vmwVCSA2022x AGENT-CAPABILITIES + PRODUCT-RELEASE + "8.0.x" + STATUS current + DESCRIPTION + "Release 8.0 for VMware Virtual Appliance (VCSA) supporting SNMPv1, SNMPv2c, and SNMPv3. + Changes for this release were bug fixes. + " + 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 10 } + +-- +-- 2020 Release and follow up patch releases +-- + +vmwVCSA2020x AGENT-CAPABILITIES + PRODUCT-RELEASE + "7.0.x" + STATUS current + DESCRIPTION + "Release 7.0 for VMware Virtual Appliance (VCSA) supporting SNMPv1, SNMPv2c, and SNMPv3. + Added REST API configuration/status/test support for appliance similar to vicfg-snmp CLI, + Service is off by default, see 'systemctl status snmpcfgd' and systemctl enable/start to use. + Added a configuration option for HOST-RESOURCES-MIB added for reporting java processes clearly. + Remaining changes for this release were bug fixes. + " + 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 9 } + +-- +-- 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 +-- + +vmwVA2015x AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.0.x" + STATUS current + DESCRIPTION + "Release 2015 aka 6.0 for VMware Virtual Appliance supporting SNMPv1, SNMPv2c, and SNMPv3. + + 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. + + This initial release does not have: UDP-MIB, TCP-MIB modules. + " + 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 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 + + ::= { vmwVACapability 5 } + + + +END + diff --git a/MIBS/vmware/VMWARE-VC-EVENT-MIB b/MIBS/vmware/VMWARE-VC-EVENT-MIB new file mode 100644 index 0000000..786cc27 --- /dev/null +++ b/MIBS/vmware/VMWARE-VC-EVENT-MIB @@ -0,0 +1,251 @@ +-- ********************************************************** +-- Copyright 2008 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-VC-EVENT-MIB DEFINITIONS ::= BEGIN + + IMPORTS + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + SnmpAdminString + FROM SNMP-FRAMEWORK-MIB + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + -- add these for HP SIM + --vmwProductSpecific + --FROM VMWARE-ROOT-MIB; + -- remove these for HP SIM + vmwVC + FROM VMWARE-PRODUCTS-MIB + VmwLongSnmpAdminString + FROM VMWARE-TC-MIB; + + vmwVCMIB MODULE-IDENTITY + LAST-UPDATED "200912150000Z" + 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 identifies vCenter Trap notifications (traps or inform)." +REVISION "200912150000Z" +DESCRIPTION + "Notification vpxdAlarm is now obsolete and is replaced with vpxdAlarmInfo, + new object group vmwVCAlarmGroup is created making the vmwVCAlarmInfoGroup + obsolete, new notification group vmwVCAlarmNotificationGroup is created + making vmwVCNotificationGroup obsolete,new varbinds vmwVpxdTargetObj and + vmwVpxdTargetObjType are added, var binds vmwVpxdHostName, vmwVpxdVMName + and vmwVpxdTrapType have become obsolete." +REVISION "200909080000Z" +DESCRIPTION + "VC SNMP Agent has always used UTF-8 in notifications, + update this MIB module to reflect that." + +REVISION "200905270000Z" +DESCRIPTION + "Updated comments on the alarm trap and parameters with more detail." +REVISION "200904060000Z" +DESCRIPTION + "Swap vmwVpxdNewStatus and vmwVpxdOldStatus to match code implementation." +REVISION "200903170000Z" +DESCRIPTION + "Changed vmwVpxdObjValue be of type vmwLongDisplayString" +REVISION "200802220000Z" +DESCRIPTION + "This is the first revision in SMIv2 format. Prior version was published as SMIv1. + Notifications were formerly in the VMWARE-TRAPS-MIB module." +::= { vmwVC 1 } + + +-- product compatiblity: smilint warning: redefinition of vmwVC in VMWARE-PRODUCTS-MIB +-- The folowing redefinition of vmwVC is a workaround for HP SIM which +-- doesn't process IMPORTS more than one level deep. +-- vmwVC OBJECT IDENTIFIER ::= { vmwProductSpecific 3 } + +vmwVCNotifications OBJECT IDENTIFIER ::= {vmwVC 0 } + +-- ********************************************************** +-- Notifications by an agent that implements this mib module +-- ********************************************************** + +vpxdAlarm NOTIFICATION-TYPE + OBJECTS { vmwVpxdTrapType, vmwVpxdHostName, vmwVpxdVMName, + vmwVpxdOldStatus, vmwVpxdNewStatus, vmwVpxdObjValue } + STATUS obsolete + DESCRIPTION + "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." + ::= { vmwVCNotifications 201 } + +vpxdDiagnostic NOTIFICATION-TYPE + STATUS current + DESCRIPTION + "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." + ::= { vmwVCNotifications 202 } + +vpxdAlarmInfo NOTIFICATION-TYPE + OBJECTS { vmwVpxdTargetObjType, vmwVpxdOldStatus, vmwVpxdNewStatus, vmwVpxdObjValue, vmwVpxdTargetObj } + STATUS current + DESCRIPTION + "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." + ::= { vmwVCNotifications 203 } + +-- ********************************************************** +-- Notification parameters +-- ********************************************************** + +vmwVpxdTrapType OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "This is the alarm notification type." + ::= { vmwVC 301 } + +vmwVpxdHostName OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "This is the name of the vSphere host in the notification." + ::= { vmwVC 302 } + +vmwVpxdVMName OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "This is the name of the VM in the notification." + ::= { vmwVC 303 } + +vmwVpxdOldStatus OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the old status in the notification." + ::= { vmwVC 304 } + +vmwVpxdNewStatus OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the new status in the notification." + ::= { vmwVC 305 } + +vmwVpxdObjValue OBJECT-TYPE + SYNTAX VmwLongSnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the current object value in the notification." + ::= { vmwVC 306 } + +vmwVpxdTargetObj OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the current object in the notification. This may be + one of esx host name, vm name, or other. This value must not be empty." + ::= { vmwVC 307 } + +vmwVpxdTargetObjType OBJECT-TYPE + SYNTAX INTEGER { unknown(1), host(2), vm(3), other(4)} + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the alarm target object type." + ::= { vmwVC 308 } + +-- conformance information +vmwVCMIBConformance OBJECT IDENTIFIER ::= { vmwVCMIB 2 } +vmwVCMIBCompliances OBJECT IDENTIFIER ::= { vmwVCMIBConformance 1 } +vmwVCMIBGroups OBJECT IDENTIFIER ::= { vmwVCMIBConformance 2 } + +-- compliance statements +vmwVCMIBBasicCompliance MODULE-COMPLIANCE + STATUS obsolete + DESCRIPTION + "The compliance statement for entities which implement VMWARE-VC-EVENT-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwVCAlarmInfoGroup, vmwVCNotificationGroup } + ::= { vmwVCMIBCompliances 2 } + +-- compliance statements +vmwVCMIBBasicComplianceRev2 MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement VMWARE-VC-EVENT-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwVCAlarmGroup, vmwVCAlarmNotificationGroup } + ::= { vmwVCMIBCompliances 3 } + +vmwVCAlarmInfoGroup OBJECT-GROUP + OBJECTS { + vmwVpxdTrapType, + vmwVpxdHostName, + vmwVpxdVMName, + vmwVpxdOldStatus, + vmwVpxdNewStatus, + vmwVpxdObjValue + } + STATUS obsolete + DESCRIPTION + "These objects provide alarm notification details." + ::= { vmwVCMIBGroups 1 } + +vmwVCNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vpxdAlarm, + vpxdDiagnostic + } + STATUS obsolete + DESCRIPTION + "Group of objects describing notifications (traps)." + ::= { vmwVCMIBGroups 2 } + +vmwVCAlarmGroup OBJECT-GROUP + OBJECTS { + vmwVpxdTargetObjType, + vmwVpxdOldStatus, + vmwVpxdNewStatus, + vmwVpxdObjValue, + vmwVpxdTargetObj + } + STATUS current + DESCRIPTION + "These objects provide alarm notification details." + ::= { vmwVCMIBGroups 3 } + +vmwVCAlarmNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vpxdAlarmInfo, + vpxdDiagnostic + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps)." + ::= { vmwVCMIBGroups 4 } + +END -- end of VMWARE-VC-EVENT-MIB. diff --git a/MIBS/vmware/VMWARE-VCHA-MIB b/MIBS/vmware/VMWARE-VCHA-MIB new file mode 100644 index 0000000..97d119e --- /dev/null +++ b/MIBS/vmware/VMWARE-VCHA-MIB @@ -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. diff --git a/MIBS/vmware/VMWARE-VCOPS-EVENT-MIB b/MIBS/vmware/VMWARE-VCOPS-EVENT-MIB new file mode 100644 index 0000000..8b9fc65 --- /dev/null +++ b/MIBS/vmware/VMWARE-VCOPS-EVENT-MIB @@ -0,0 +1,1695 @@ +-- ********************************************************** +-- Copyright 2013-2016 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-VCOPS-EVENT-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + SnmpAdminString + FROM SNMP-FRAMEWORK-MIB + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + vmwVCOps + FROM VMWARE-PRODUCTS-MIB; + +vmwVcopsMIB MODULE-IDENTITY + LAST-UPDATED "201610130000Z" + 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 file contains the information that the receiving party needs in order to interpret the SNMP traps sent by vRealize Operations Manager. + + To download VMware MIB modules see http://kb.vmware.com/kb/1013445 + To download OID/MIB module list see http://kb.vmware.com/kb/2054359 +" + REVISION "201610130000Z" + DESCRIPTION + "Add three new notifications: + vmwareTrapProblemActive, vwareTrapProblemClear, and vmwareTrapProblemChange. + Add three new variable bindings to all events: vmwareAlertSubtype, + vmwareAlertMetricName, and vmwareAlertResourceKind." + + REVISION "201302010000Z" + DESCRIPTION + "Corrected vmwVCOps oid assignments." + REVISION "201110190000Z" + DESCRIPTION "Re-named Integrien-Mib to VMWARE-VCOPS-MIB" + REVISION "200901260000Z" + DESCRIPTION + "Rewrite Integrien MIB for Alive v7.0 aka 'Carbon'" + ::= { vmwVCOps 1 } + +-- +-- Top-level MIB groups +-- + +-- Group 0: Alerts sent as traps +vmwareAlertTrap OBJECT-IDENTITY + STATUS obsolete + DESCRIPTION + "This group is actually the prefix one uses when creating + enterprise-specific trap OID's for an SNMPv2 trap. It is + used in the VMware MIB when defining traps." + ::= { vmwVcopsMIB 0 } + + +-- +-- Group 2: Generic data sent in All Alerts +-- Generic data, in var-binds, that is associated with EVERY Alert +-- +vmwareGenericAlertData OBJECT-IDENTITY + STATUS obsolete + DESCRIPTION + "This members of this group are the OIDs for VarBinds + that contain data for ALL Alerts." + ::= { vmwVcopsMIB 2 } + +vmwareAlertAliveServerName OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The name of the vRealize Operations server that generated this alert." + ::= { vmwareGenericAlertData 1 } + +vmwareAlertEntityName OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The Entity name about which this alert was generated." + ::= { vmwareGenericAlertData 2 } + +vmwareAlertEntityType OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The Entity type about which this alert was generated." + ::= { vmwareGenericAlertData 3 } + +vmwareAlertTimestamp OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The timestamp of the alert in UTC format." + ::= { vmwareGenericAlertData 4 } + +vmwareAlertCriticality OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "A text string describing the alert criticality level." + ::= { vmwareGenericAlertData 5 } + +vmwareAlertRootCause OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "A text string describing the root-cause of the alert that was generated." + ::= { vmwareGenericAlertData 6 } + +vmwareAlertURL OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The URL of the 'Alert Summary' page of the alert that was generated." + ::= { vmwareGenericAlertData 7 } + +vmwareAlertID OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The unique vRealize Operations identifier of the alert that was generated." + ::= { vmwareGenericAlertData 8 } + +vmwareAlertMessage OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The info message of the alert that was generated." + ::= { vmwareGenericAlertData 9 } + +vmwareAlertType OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The textual type description of the alert that was generated." + ::= { vmwareGenericAlertData 10 } + + +vmwareAlertSubtype OBJECT-TYPE + SYNTAX OCTET STRING + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The textual subtype description of the alert that was generated." + ::= { vmwareGenericAlertData 11 } + +vmwareAlertHealth OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "Health badge state." + ::= { vmwareGenericAlertData 12 } + +vmwareAlertRisk OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "Risk badge state." + ::= { vmwareGenericAlertData 13 } + +vmwareAlertEfficiency OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "Efficiency badge state." + ::= { vmwareGenericAlertData 14 } + +vmwareAlertMetricName OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The textual metric name of the alert that was generated." + ::= { vmwareGenericAlertData 15 } + +vmwareAlertResourceKind OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "The textual object type of the alert that was generated." + ::= { vmwareGenericAlertData 16 } + +vmwareAlertDefinitionName OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "Alert Definition Name." + ::= { vmwareGenericAlertData 17 } + +vmwareAlertDefinitionDesc OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "Alert Definition Description." + ::= { vmwareGenericAlertData 18 } + +vmwareAlertImpact OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS obsolete + DESCRIPTION + "Alert Impact" + ::= { vmwareGenericAlertData 19 } + + +-- +-- Trap types that correspond to the different types of SmartAlerts +-- that can be generated. The data sent in these traps will be a +-- combination of generic data and trap-specific data, depending +-- on the trap type. +-- These are the enterprise-specific trap codes currently in-use in +-- VMware's software. The final sub-OID of each objects is the code +-- sent in the "specific-trap" field of an SNMPv1 Trap-PDU. +-- +-- The definition of these objects mimics the SNMPv2 convention for +-- sending traps: +-- Take the enterprise OID, append 0, then append the trap code. +-- Trap number usage: +-- Trap code 0 is reserved (by SNMP) +-- Trap codes 1-9 are used for Smart Alerts +-- Trap codes 10-18 are used for Classic Alerts +-- Trap codes 19-27 are used for Badge Health Alerts +-- Trap codes 28-36 are used for Badge Risk Alerts +-- Trap codes 37-42 are used for Badge Efficiency Alerts +-- Trap codes 60-62 are used for Consolidated Alerts +-- Trap codes 101-199 are used for Administrative Alerts +-- Trap code 200 is used for functionality testing +-- +vmwareTrapKPIBreachActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that indicates a KPI Breach condition + became active." + ::= { vmwareAlertTrap 1 } + +vmwareTrapKPIBreachClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that indicates a KPI Breach condition + became inactive." + ::= { vmwareAlertTrap 2 } + +vmwareTrapKPIBreachChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that indicates a KPI Breach condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 3 } + +vmwareTrapKPIPredictionActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that predicts a KPI Breach condition + (also know as 'Fingerprint') became active." + ::= { vmwareAlertTrap 4 } + +vmwareTrapKPIPredictionClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that predicts a KPI Breach condition + (also know as 'Fingerprint') became inactive." + ::= { vmwareAlertTrap 5 } + +vmwareTrapKPIPredictionChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that predicts a KPI Breach condition + (also know as 'Fingerprint') that experiences a change in one or more + of the following values: + - Prediction probability + - Prediction projected time + - Prediction reason." + ::= { vmwareAlertTrap 6 } + +vmwareTrapAggregateAnomalyActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that indicates an Aggregate Anomaly condition + became active." + ::= { vmwareAlertTrap 7 } + +vmwareTrapAggregateAnomalyClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Smart Alert that indicates an Aggregate Anomaly condition + became inactive." + ::= { vmwareAlertTrap 8 } + +vmwareTrapKPIHTBreachActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a KPI HT Breach condition + became active." + ::= { vmwareAlertTrap 10 } + +vmwareTrapKPIHTBreachClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a KPI HT Breach condition + became inactive." + ::= { vmwareAlertTrap 11 } + +vmwareTrapKPIHTBreachChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a KPI HT Breach condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 12 } + +vmwareTrapNotificationActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a Notification condition + became active." + ::= { vmwareAlertTrap 13 } + +vmwareTrapNotificationClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a Notification condition + became inactive." + ::= { vmwareAlertTrap 14 } + +vmwareTrapNotificationChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a Notification condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 15 } + +vmwareTrapAbnormalityActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a Abnormality condition + became active." + ::= { vmwareAlertTrap 16 } + + +vmwareTrapAbnormalityClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a Abnormality condition + became inactive." + ::= { vmwareAlertTrap 17 } + +vmwareTrapAbnormalityChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Classic Alert that indicates a Abnormality condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 18 } + +vmwareTrapWorkloadActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates a Workload condition + became active." + ::= { vmwareAlertTrap 19 } + +vmwareTrapWorkloadClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates a Workload condition + became inactive." + ::= { vmwareAlertTrap 20 } + +vmwareTrapWorkloadChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates a Workload condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 21 } + +vmwareTrapAnomalyActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates an Anomaly condition + became active." + ::= { vmwareAlertTrap 22 } + +vmwareTrapAnomalyClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates an Anomaly condition + became inactive." + ::= { vmwareAlertTrap 23 } + +vmwareTrapAnomalyChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates an Anomaly condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 24 } + +vmwareTrapFaultActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates a Fault condition + became active." + ::= { vmwareAlertTrap 25 } + +vmwareTrapFaultClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates a Fault condition + became inactive." + ::= { vmwareAlertTrap 26 } + +vmwareTrapFaultChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Health Alert that indicates a Fault condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 27 } + +vmwareTrapTimeRemainingActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Time Remaining condition + became active." + ::= { vmwareAlertTrap 28 } + +vmwareTrapTimeRemainingClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Time Remaining condition + became inactive." + ::= { vmwareAlertTrap 29 } + +vmwareTrapTimeRemainingChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Time Remaining condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 30 } + +vmwareTrapCapacityRemainingActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Capacity Remaining condition + became active." + ::= { vmwareAlertTrap 31 } + +vmwareTrapCapacityRemainingClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Capacity Remaining condition + became inactive." + ::= { vmwareAlertTrap 32 } + +vmwareTrapCapacityRemainingChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Capacity Remaining condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 33 } + +vmwareTrapStressActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Stress condition + became active." + ::= { vmwareAlertTrap 34 } + +vmwareTrapStressClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Stress condition + became inactive." + ::= { vmwareAlertTrap 35 } + +vmwareTrapStressChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Stress condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 36 } + +vmwareTrapWasteActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Efficiency Alert that indicates a Waste condition + became active." + ::= { vmwareAlertTrap 37 } + +vmwareTrapWasteClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Efficiency Alert that indicates a Waste condition + became inactive." + ::= { vmwareAlertTrap 38 } + +vmwareTrapWasteChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Efficiency Alert that indicates a Waste condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 39 } + +vmwareTrapDensityActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Efficiency Alert that indicates a Density condition + became active." + ::= { vmwareAlertTrap 40 } + +vmwareTrapDensityClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Efficiency Alert that indicates a Density condition + became inactive." + ::= { vmwareAlertTrap 41 } + +vmwareTrapDensityChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Efficiency Alert that indicates a Density condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 42 } + + vmwareTrapComplianceActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Compliance condition + became active." + ::= { vmwareAlertTrap 43 } + + vmwareTrapComplianceClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Compliance condition + became inactive." + ::= { vmwareAlertTrap 44 } + +vmwareTrapComplianceChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Risk Alert that indicates a Compliance condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 45 } + +vmwareTrapProblemActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertHealth, + vmwareAlertRisk, + vmwareAlertEfficiency, + vmwareAlertMetricName, + vmwareAlertResourceKind, + vmwareAlertDefinitionName, + vmwareAlertDefinitionDesc, + vmwareAlertImpact + } + STATUS obsolete + DESCRIPTION + "A trap describing a Problem Alert that indicates a Abnormality condition + became active." + ::= { vmwareAlertTrap 46 } + +vmwareTrapProblemClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertHealth, + vmwareAlertRisk, + vmwareAlertEfficiency, + vmwareAlertMetricName, + vmwareAlertResourceKind, + vmwareAlertDefinitionName, + vmwareAlertDefinitionDesc, + vmwareAlertImpact + } + STATUS obsolete + DESCRIPTION + "A trap describing a Problem Alert that indicates a Abnormality condition + became inactive." + ::= { vmwareAlertTrap 47 } + +vmwareTrapProblemChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertHealth, + vmwareAlertRisk, + vmwareAlertEfficiency, + vmwareAlertMetricName, + vmwareAlertResourceKind, + vmwareAlertDefinitionName, + vmwareAlertDefinitionDesc, + vmwareAlertImpact + } + STATUS obsolete + DESCRIPTION + "A trap describing a Problem Alert that indicates a Abnormality condition + has changed one of its parameters' value." + ::= { vmwareAlertTrap 48 } + + +-- +-- Trap types that correspond to the different types of Administrative +-- Alerts that can be generated. The data in the Admin. Alerts will be +-- only the generic data. Entity names and types will need to reflect +-- the VCOPs/Collector/Data Source components the alert pertains to. +-- + +vmwareTrapAliveComponentFailureActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing an Administrative Alert that indicates an vRealize Operations Component failure + became active." + ::= { vmwareAlertTrap 101 } + +vmwareTrapAliveComponentFailureClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing an Administrative Alert that indicates an vRealize Operations Component failure + became inactive." + ::= { vmwareAlertTrap 102 } + +vmwareTrapResourceDisconnectedActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing an Administrative Alert that indicates a resource has disconnected + from vRealize Operations." + ::= { vmwareAlertTrap 103 } + +vmwareTrapResourceDisconnectedClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing an Administrative Alert that indicates that a disconnected + resource has re-connected to vRealize Operations." + ::= { vmwareAlertTrap 104 } + +-- Traps for Consolidated Alerts + +vmwareTrapConsolidatedAlertActive NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Consolidated Alert that aggregates similar alerts + has become active" + ::= { vmwareAlertTrap 60 } + +vmwareTrapConsolidatedAlertClear NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Consolidated Alert that aggregates similar alerts + has become inactive" + ::= { vmwareAlertTrap 61 } + +vmwareTrapConsolidatedAlertChange NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "A trap describing a Consolidated Alert that aggregates similar alerts + has changed one of its parameters" + ::= { vmwareAlertTrap 62 } + + +-- Trap for functional testing. +-- + +vmwareTrapTest NOTIFICATION-TYPE + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "Trap for testing purposes." + ::= { vmwareAlertTrap 200 } + +-- conformance information +vmwVCOPSMIBConformance OBJECT IDENTIFIER ::= { vmwVcopsMIB 99 } +vmwVCOPSMIBCompliances OBJECT IDENTIFIER ::= { vmwVCOPSMIBConformance 1 } +vmwVCOPSMIBGroups OBJECT IDENTIFIER ::= { vmwVCOPSMIBConformance 2 } + +-- compliance statements +vmwVCOPSMIBBasicCompliance MODULE-COMPLIANCE + STATUS obsolete + DESCRIPTION + "The compliance statement for entities which implement VMWARE-VCOPS-EVENT-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwVCOPSNotificationInfoGroup1, vmwVCOPSNotificationGroup1 } + ::= { vmwVCOPSMIBCompliances 3 } + +vmwVCOPSNotificationInfoGroup1 OBJECT-GROUP + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind + } + STATUS obsolete + DESCRIPTION + "These objects provide details in vRealize Operations notifications." + ::= { vmwVCOPSMIBGroups 2 } + +vmwVCOPSNotificationGroup1 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwareTrapComplianceActive, + vmwareTrapComplianceClear, + vmwareTrapComplianceChange, + vmwareTrapConsolidatedAlertActive, + vmwareTrapConsolidatedAlertClear, + vmwareTrapConsolidatedAlertChange, + vmwareTrapTest, + vmwareTrapKPIBreachActive, + vmwareTrapKPIBreachClear, + vmwareTrapKPIBreachChange, + vmwareTrapKPIPredictionActive, + vmwareTrapKPIPredictionClear, + vmwareTrapKPIPredictionChange, + vmwareTrapAggregateAnomalyActive, + vmwareTrapAggregateAnomalyClear, + vmwareTrapKPIHTBreachActive, + vmwareTrapKPIHTBreachClear, + vmwareTrapKPIHTBreachChange, + vmwareTrapNotificationActive, + vmwareTrapNotificationClear, + vmwareTrapNotificationChange, + vmwareTrapAbnormalityActive, + vmwareTrapAbnormalityClear, + vmwareTrapAbnormalityChange, + vmwareTrapWorkloadActive, + vmwareTrapWorkloadClear, + vmwareTrapWorkloadChange, + vmwareTrapAnomalyActive, + vmwareTrapAnomalyClear, + vmwareTrapAnomalyChange, + vmwareTrapFaultActive, + vmwareTrapFaultClear, + vmwareTrapFaultChange, + vmwareTrapTimeRemainingActive, + vmwareTrapTimeRemainingClear, + vmwareTrapTimeRemainingChange, + vmwareTrapCapacityRemainingActive, + vmwareTrapCapacityRemainingClear, + vmwareTrapCapacityRemainingChange, + vmwareTrapStressActive, + vmwareTrapStressClear, + vmwareTrapStressChange, + vmwareTrapWasteActive, + vmwareTrapWasteClear, + vmwareTrapWasteChange, + vmwareTrapDensityActive, + vmwareTrapDensityClear, + vmwareTrapDensityChange, + vmwareTrapAliveComponentFailureActive, + vmwareTrapAliveComponentFailureClear, + vmwareTrapResourceDisconnectedActive, + vmwareTrapResourceDisconnectedClear + } + STATUS obsolete + DESCRIPTION + "Group of objects describing notifications (traps, informs)." + ::= { vmwVCOPSMIBGroups 3 } + +vmwVCOPSMIBBasicCompliance2016 MODULE-COMPLIANCE + STATUS obsolete + DESCRIPTION + "Define which events apply to agents implementing VMWARE-VCOPS-EVENT-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwVCOPSNotificationInfoGroup2, vmwVCOPSNotificationGroup2 } + ::= { vmwVCOPSMIBCompliances 4 } + + +vmwVCOPSNotificationInfoGroup2 OBJECT-GROUP + OBJECTS { + vmwareAlertAliveServerName, + vmwareAlertEntityName, + vmwareAlertEntityType, + vmwareAlertTimestamp, + vmwareAlertCriticality, + vmwareAlertRootCause, + vmwareAlertURL, + vmwareAlertID, + vmwareAlertMessage, + vmwareAlertType, + vmwareAlertSubtype, + vmwareAlertMetricName, + vmwareAlertResourceKind, + vmwareAlertHealth, + vmwareAlertRisk, + vmwareAlertEfficiency, + vmwareAlertDefinitionName, + vmwareAlertDefinitionDesc, + vmwareAlertImpact + } + STATUS obsolete + DESCRIPTION + "These objects provide details in vRealize Operations notifications." + ::= { vmwVCOPSMIBGroups 4 } + + +vmwVCOPSNotificationGroup2 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwareTrapComplianceActive, + vmwareTrapComplianceClear, + vmwareTrapComplianceChange, + vmwareTrapConsolidatedAlertActive, + vmwareTrapConsolidatedAlertClear, + vmwareTrapConsolidatedAlertChange, + vmwareTrapTest, + vmwareTrapKPIBreachActive, + vmwareTrapKPIBreachClear, + vmwareTrapKPIBreachChange, + vmwareTrapKPIPredictionActive, + vmwareTrapKPIPredictionClear, + vmwareTrapKPIPredictionChange, + vmwareTrapAggregateAnomalyActive, + vmwareTrapAggregateAnomalyClear, + vmwareTrapKPIHTBreachActive, + vmwareTrapKPIHTBreachClear, + vmwareTrapKPIHTBreachChange, + vmwareTrapNotificationActive, + vmwareTrapNotificationClear, + vmwareTrapNotificationChange, + vmwareTrapAbnormalityActive, + vmwareTrapAbnormalityClear, + vmwareTrapAbnormalityChange, + vmwareTrapWorkloadActive, + vmwareTrapWorkloadClear, + vmwareTrapWorkloadChange, + vmwareTrapAnomalyActive, + vmwareTrapAnomalyClear, + vmwareTrapAnomalyChange, + vmwareTrapFaultActive, + vmwareTrapFaultClear, + vmwareTrapFaultChange, + vmwareTrapTimeRemainingActive, + vmwareTrapTimeRemainingClear, + vmwareTrapTimeRemainingChange, + vmwareTrapCapacityRemainingActive, + vmwareTrapCapacityRemainingClear, + vmwareTrapCapacityRemainingChange, + vmwareTrapStressActive, + vmwareTrapStressClear, + vmwareTrapStressChange, + vmwareTrapWasteActive, + vmwareTrapWasteClear, + vmwareTrapWasteChange, + vmwareTrapDensityActive, + vmwareTrapDensityClear, + vmwareTrapDensityChange, + vmwareTrapAliveComponentFailureActive, + vmwareTrapAliveComponentFailureClear, + vmwareTrapResourceDisconnectedActive, + vmwareTrapResourceDisconnectedClear, + vmwareTrapProblemActive, + vmwareTrapProblemClear, + vmwareTrapProblemChange + } + STATUS obsolete + DESCRIPTION + "Group of objects describing notifications (traps, informs) supported for this + version of this mib modules." + ::= { vmwVCOPSMIBGroups 5 } + +END diff --git a/MIBS/vmware/VMWARE-VMINFO-MIB b/MIBS/vmware/VMWARE-VMINFO-MIB new file mode 100644 index 0000000..2d36bb1 --- /dev/null +++ b/MIBS/vmware/VMWARE-VMINFO-MIB @@ -0,0 +1,704 @@ +-- ********************************************************** +-- Copyright 2008 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-VMINFO-MIB DEFINITIONS ::= BEGIN + + IMPORTS + MODULE-IDENTITY, Integer32, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + DisplayString, PhysAddress + FROM SNMPv2-TC + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + VmwConnectedState + FROM VMWARE-TC-MIB + vmwESXNotifications + FROM VMWARE-ENV-MIB + vmwVirtMachines, vmwTraps + FROM VMWARE-ROOT-MIB; + + vmwVmInfoMIB MODULE-IDENTITY + LAST-UPDATED "201109170000Z" + 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 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." + +REVISION "201109170000Z" +DESCRIPTION + "Remove vmwVmID as it duplicates vmwVmID." + +REVISION "201006220000Z" +DESCRIPTION + "Add managed object vmwVmUUID to vmTable to allow management applications + to identify a VM uniquely over a set of ESX systems. This value is useful when + VMs may move between systems." + +REVISION "200810230000Z" +DESCRIPTION + "Add to comments the Managed Object Browser (MOB) URLs which provide + data this MIB module exposes. + Handle cases in reporting string for managed objects in this mib + where the values depend on additional operator configuration. + Instead of returning an empty string, an error message of the form: + W|E: error description + Add vmNumCpus to vmwVmTable to better report on VSMP virtual machines. + Add vmwVmNetConnected and vmwVmMAC to vmwVmNetTable + VIM Virtual Devices index range values are documented based on ESX 3/4 + implementation, they may change in the future releases. + Update comments to note that CDROM also lists DVDROM virtual devices." + +REVISION "200712270000Z" +DESCRIPTION + "This is the first revision in SMIv2 format. Prior version was published as SMIv1. + Notifications found here were formerly in the VMWARE-TRAPS-MIB module." +::= { vmwVirtMachines 10 } + + +-- the vm inventory for this system + + vmwVmTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwVmEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "A table containing information on virtual machines that have been + configured on the system." + ::= { vmwVirtMachines 1 } + + vmwVmEntry OBJECT-TYPE + SYNTAX VmwVmEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies a registered VM on this ESX system." + INDEX { vmwVmIdx } + ::= { vmwVmTable 1 } + + VmwVmEntry ::= SEQUENCE { + vmwVmIdx Integer32, + vmwVmDisplayName DisplayString, + vmwVmConfigFile DisplayString, + vmwVmGuestOS DisplayString, + vmwVmMemSize Integer32, + vmwVmState DisplayString, + vmwVmVMID Integer32, + vmwVmGuestState DisplayString, + vmwVmCpus Integer32, + vmwVmUUID OCTET STRING + } + + vmwVmIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "An operational identifier given the VM when registered on this ESX system. + The value is not unique across ESX systems and may change upon reboot. + VIM property: ha-vm-folder + MOB: https://esx.example.com/mob/?moid=ha%2dfolder%2dvm + A given Virtual Machine Instance can be queried using this URL: + MOB: https://esx.example.com/mob/?moid=vmwVmIdx" + ::= { vmwVmEntry 1 } + + vmwVmDisplayName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Name by which this vm is displayed. It is not guaranteed to be unique. + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=summary%2eguest" + ::= { vmwVmEntry 2 } + + vmwVmConfigFile OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Path to the configuration file for this vm expressed as a fully + qualified path name in POSIX or DOS extended format + VM Config file File name: + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2efiles + VM Datastore containing the filename: + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2edatastoreUrl" + ::= { vmwVmEntry 3 } + + vmwVmGuestOS OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Operating system running on this vm. This value corresponds to the + value specified when creating the VM and unless set correctly may differ + from the actual OS running. Will return one of the values if set in order: + Vim.Vm.GuestInfo.guestFullName + Vim.Vm.GuestInfo.guestId + Vim.Vm.GuestInfo.guestFamily + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=guest + where moid = vmwVmIdx. + If VMware Tools is not running, value will be of form 'E: error message'" + ::= { vmwVmEntry 4 } + + vmwVmMemSize OBJECT-TYPE + SYNTAX Integer32 + UNITS "megabytes" + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Memory configured for this virtual machine. + Memory > MAX Integer32 is reported as max integer32. + VIM Property: memoryMB + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware" + ::= { vmwVmEntry 5 } + + vmwVmState OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Power state of the virtual machine. + VIM Property: powerState + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=summary%2eruntime" + ::= { vmwVmEntry 6 } + + vmwVmVMID OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "No longer provided, use vmwVmIdx. See vmwVmUUID for cross system, + unique, persistent identifier." + ::= { vmwVmEntry 7 } + + vmwVmGuestState OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Operation mode of guest operating system. Values include: + running - Guest is running normally. + shuttingdown - Guest has a pending shutdown command. + resetting - Guest has a pending reset command. + standby - Guest has a pending standby command. + notrunning - Guest is not running. + unknown - Guest information is not available. + VIM Property: guestState + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=guest" + ::= { vmwVmEntry 8 } + + vmwVmCpus OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Number of virtual CPUs assigned to this virtual machine. + VIM Property: numCPU + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware" + ::= { vmwVmEntry 9 } + + vmwVmUUID OBJECT-TYPE + SYNTAX OCTET STRING (SIZE(36..72)) + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "A unique identifier for this VM. Must be unique across a set of ESX systems + managed by an instance of vSphere Center. + Example value: 564d95d4-bff7-31fd-f20f-db2d808a8b32 + VIM Property: uuid + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config" + ::= { vmwVmEntry 10 } + +-- Host Bus Adapters + + vmwVmHbaTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwVmHbaEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Table of host bus adapters (hba) for all vms in vmwVmTable." + ::= { vmwVirtMachines 2 } + + vmwVmHbaEntry OBJECT-TYPE + SYNTAX VmwVmHbaEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Uniquely identifies a given virtual machine host bus adapter." + INDEX { vmwHbaVmIdx, vmwVmHbaIdx } + ::= { vmwVmHbaTable 1 } + + VmwVmHbaEntry ::= SEQUENCE { + vmwHbaVmIdx Integer32, + vmwVmHbaIdx Integer32, + vmwHbaNum DisplayString, + vmwHbaVirtDev DisplayString + } + + vmwHbaVmIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This number corresponds to the vmwVmIdx in vmwVmTable." + ::= { vmwVmHbaEntry 1 } + + vmwVmHbaIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Uniquely identifies a given Host Bus adapter in this VM. May + change across system reboots." + ::= { vmwVmHbaEntry 2 } + + vmwHbaNum OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The name of the hba as it appears in the VM Settings. + VIM Property: Virtual Device index of 200-299. + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware" + ::= { vmwVmHbaEntry 3 } + + vmwHbaVirtDev OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The oem host bus adapter hardware being emulated to the Guest OS. + MOB: Not visible." + ::= { vmwVmHbaEntry 4 } + +-- Host Bus Adapter Targets + + vmwHbaTgtTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwHbaTgtEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Table of all virtual disks configured for vms in vmwVmTable." + ::= { vmwVirtMachines 3 } + + vmwHbaTgtEntry OBJECT-TYPE + SYNTAX VmwHbaTgtEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies a specific storage disk. Index may change across reboots." + INDEX { vmwHbaTgtVmIdx, vmwHbaTgtIdx } + ::= { vmwHbaTgtTable 1 } + + VmwHbaTgtEntry ::= SEQUENCE { + vmwHbaTgtVmIdx Integer32, + vmwHbaTgtIdx Integer32, + vmwHbaTgtNum DisplayString + } + + vmwHbaTgtVmIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This number corresponds to vmwVmIdx in vmwVmTable." + ::= { vmwHbaTgtEntry 1 } + + vmwHbaTgtIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This value identifies a particular disk." + ::= { vmwHbaTgtEntry 2 } + + vmwHbaTgtNum OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Identifies the disk as seen from the host bus controller + VIM Property: Virtual Device's with index of 2000-2999,3000-3999. + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware" + ::= { vmwHbaTgtEntry 3 } + +-- vm network interfaces + + vmwVmNetTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwVmNetEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Table of network adapters (nic) for all vms in vmwVmTable." + ::= { vmwVirtMachines 4 } + + vmwVmNetEntry OBJECT-TYPE + SYNTAX VmwVmNetEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies a particular nic for the specified vmwVmIdx" + INDEX { vmwVmNetVmIdx, vmwVmNetIdx } + ::= { vmwVmNetTable 1 } + + VmwVmNetEntry ::= SEQUENCE { + vmwVmNetVmIdx Integer32, + vmwVmNetIdx Integer32, + vmwVmNetNum DisplayString, + vmwVmNetName DisplayString, + vmwVmNetConnType DisplayString, + vmwVmNetConnected VmwConnectedState, + vmwVmMAC PhysAddress + } + + vmwVmNetVmIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This number corresponds to vmwVmIdx in vmwVmTable." + ::= { vmwVmNetEntry 1 } + + vmwVmNetIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies a unique network adapter in this table. + Not guaranteed to be the same across system reboots." + ::= { vmwVmNetEntry 2 } + + vmwVmNetNum OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The name of the device as it appears in the VM Settings. + VIM Property: Virtual Device's with index of 4000-4999. + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware" + ::= { vmwVmNetEntry 3 } + + vmwVmNetName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "What this virutal nic is connected to such as a virtual switch portgroup identifier. + VIM Property: Virtual Device's with index of 4000-4999. + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware + then select property 'backing' to how this nic connects. + If no backing was defined by operator, string will start with W: + If unavailable, string will start with E:" + ::= { vmwVmNetEntry 4 } + + vmwVmNetConnType OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS obsolete + DESCRIPTION + "Do not use this value, and should an agent return it discard it." + ::= { vmwVmNetEntry 5 } + + vmwVmNetConnected OBJECT-TYPE + SYNTAX VmwConnectedState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Reports 'true' if the ethernet virtual device is connected to the virtual machine." + ::= { vmwVmNetEntry 6 } + + vmwVmMAC OBJECT-TYPE + SYNTAX PhysAddress + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Reports the configured virtual hardware MAC address. If VMware + Tools is not running, or VM has not yet been powered on for the + first time and mac is to be generated by VM then the value is + zero'd out/empty. VIM Property: Virtual Device's with index of + 4000-4999. MOB: + https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware" + ::= { vmwVmNetEntry 7 } + +-- vm floppy drive details + + vmwFloppyTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwFloppyEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Table of floppy drives for all vms in vmwVmTable." + ::= { vmwVirtMachines 5 } + + vmwFloppyEntry OBJECT-TYPE + SYNTAX VmwFloppyEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies one specific floppy device. May change across system reboots." + INDEX { vmwFdVmIdx, vmwFdIdx } + ::= { vmwFloppyTable 1 } + + VmwFloppyEntry ::= SEQUENCE { + vmwFdVmIdx Integer32, + vmwFdIdx Integer32, + vmwFdName DisplayString, + vmwFdConnected VmwConnectedState + } + + vmwFdVmIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This number corresponds to vmwVmIdx in vmwVmTable." + ::= { vmwFloppyEntry 1 } + + vmwFdIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies one specific virtual floppy device." + ::= { vmwFloppyEntry 2 } + + vmwFdName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "File or Device that this device is connected to, example /dev/fd0. + VIM Property: Virtual Device's with index of 8000-8999. + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware + If no backing was defined by operator, string will start with W: + If unavailable, string will start with E:" + ::= { vmwFloppyEntry 3 } + + vmwFdConnected OBJECT-TYPE + SYNTAX VmwConnectedState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Reports 'true' if the floppy drive virtual device is connected to the virtual machine." + ::= { vmwFloppyEntry 4 } + +-- VM CDROM drive backing + + vmwCdromTable OBJECT-TYPE + SYNTAX SEQUENCE OF VmwCdromEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Table of DVD or CDROM drives for all vms in vmwVmTable." + ::= { vmwVirtMachines 6 } + + vmwCdromEntry OBJECT-TYPE + SYNTAX VmwCdromEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies a specific DVD or CDROM drive. Value may change across system reboots." + INDEX { vmwCdVmIdx, vmwCdromIdx } + ::= { vmwCdromTable 1 } + + VmwCdromEntry ::= SEQUENCE { + vmwCdVmIdx Integer32, + vmwCdromIdx Integer32, + vmwCdromName DisplayString, + vmwCdromConnected VmwConnectedState + } + + vmwCdVmIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This number corresponds to the vmwVmIdx the vmwVmTable." + ::= { vmwCdromEntry 1 } + + vmwCdromIdx OBJECT-TYPE + SYNTAX Integer32 (0..65535) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Identifies the specific DVD or CDROM drive." + ::= { vmwCdromEntry 2 } + + vmwCdromName OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Reports the iso or device this virtual drive has been configured to use + VIM Property: Virtual Device's with index of 3000-3999 (same as disks) + MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware + then select property 'backing' to how this cdrom connects. + If no backing was defined by operator, string will start with W: + If unavailable, string will start with E:" + ::= { vmwCdromEntry 3 } + + vmwCdromConnected OBJECT-TYPE + SYNTAX VmwConnectedState + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "Reports true if the dvd/cdrom is connected to the virtual machine." + ::= { vmwCdromEntry 4 } + +-- +-- Notifications +-- + +vmwVmID OBJECT-TYPE + SYNTAX Integer32 + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This holds the same value as vmwVmVMID of the affected vm generating the trap. + to allow polling of the affected vm in vmwVmTable." + ::= { vmwTraps 101 } + +vmwVmConfigFilePath OBJECT-TYPE + SYNTAX DisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "This is the path to the config file of the affected vm generating the trap + and is same as vmwVmTable vmwVmConfigFile. It is expressed as POSIX pathname." + ::= { vmwTraps 102 } + +vmwVmPoweredOn NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath, vmwVmDisplayName } + STATUS current + 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." + +::= { vmwESXNotifications 1 } + +vmwVmPoweredOff NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath, vmwVmDisplayName } + STATUS current + 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." +::= { vmwESXNotifications 2 } + +vmwVmHBLost NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath, vmwVmDisplayName } + STATUS current + 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." +::= { vmwESXNotifications 3 } + +vmwVmHBDetected NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath, vmwVmDisplayName } + STATUS current + 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." +::= { vmwESXNotifications 4 } + +vmwVmSuspended NOTIFICATION-TYPE + OBJECTS { vmwVmID, vmwVmConfigFilePath, vmwVmDisplayName } + STATUS current + 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." +::= { vmwESXNotifications 5 } + +-- conformance information +vmwVmInfoMIBConformance OBJECT IDENTIFIER ::= { vmwVmInfoMIB 2 } +vmwVmInfoMIBCompliances OBJECT IDENTIFIER ::= { vmwVmInfoMIBConformance 1 } +vmwVmInfoMIBGroups OBJECT IDENTIFIER ::= { vmwVmInfoMIBConformance 2 } + +-- compliance statements +vmwResMIBBasicCompliance MODULE-COMPLIANCE +STATUS current +DESCRIPTION + "The compliance statement for entities which implement the + VMWARE-RESOURCE-MIB." +MODULE -- this module +MANDATORY-GROUPS { vmwVmInfoGroup, vmwVmInfoNotificationGroup } +::= { vmwVmInfoMIBCompliances 2 } + + +vmwVmInfoGroup OBJECT-GROUP + OBJECTS { + vmwVmDisplayName, + vmwVmConfigFile, + vmwVmGuestOS, + vmwVmMemSize, + vmwVmState, + vmwVmGuestState, + vmwHbaNum, + vmwHbaVirtDev, + vmwHbaTgtNum, + vmwVmNetNum, + vmwVmNetName, + vmwVmNetConnected, + vmwVmMAC, + vmwFdName, + vmwFdConnected, + vmwCdromName, + vmwCdromConnected, + vmwVmID, + vmwVmConfigFilePath, + vmwVmCpus, + vmwVmUUID + } + STATUS current + DESCRIPTION + "These objects provide virtual machine details." + ::= { vmwVmInfoMIBGroups 1 } + +vmwVmInfoNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwVmPoweredOn, + vmwVmPoweredOff, + vmwVmHBLost, + vmwVmHBDetected, + vmwVmSuspended + } + STATUS current + DESCRIPTION + "Group of objects describing notifications (traps)." + ::= { vmwVmInfoMIBGroups 2 } + +-- Obsolete details +vmwVmObsoleteGroup OBJECT-GROUP + OBJECTS { + vmwVmVMID, + vmwVmNetConnType + } + STATUS obsolete + DESCRIPTION + "Managed objects that should not be used." + ::= { vmwVmInfoMIBGroups 3 } + + +END -- end of module VMWARE-VMINFO-MIB. diff --git a/MIBS/vmware/VMWARE-VRNI-AGENTCAP-MIB b/MIBS/vmware/VMWARE-VRNI-AGENTCAP-MIB new file mode 100644 index 0000000..c9b63f9 --- /dev/null +++ b/MIBS/vmware/VMWARE-VRNI-AGENTCAP-MIB @@ -0,0 +1,452 @@ +-- ********************************************************** +-- Copyright 2016-2022 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 "202303100000Z" + 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. + It is compatible with vRNI v3.8 and onwards" + + REVISION "202303100000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 6.9 and 6.10 release" + + REVISION "202209070000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 6.7 and 6.8 release" + + REVISION "202203300000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 6.5 and 6.6 release" + + REVISION "202110010000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 6.3 and 6.4 release" + + REVISION "202105240000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 6.2 release" + + REVISION "202005200000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 5.1 and 5.2 release" + + REVISION "201908190000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 5.0 release" + + REVISION "201906060000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 4.2 release" + + REVISION "201903220000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 4.1 release" + + REVISION "201812040000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 4.0 release" + + REVISION "201809120000Z" + DESCRIPTION + "Notifications sent by VRNI as updated in 3.9 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 } + +vmwVRNIAgent2021v670 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.10.0" + STATUS current + DESCRIPTION + "Release 6.10.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 202303100000Z fourteenth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12, + vmwNetworkInsightNotificationGroup13, + vmwNetworkInsightNotificationGroup14, + vmwNetworkInsightNotificationGroup15 + } + ::= { vmwVRNICapability 21 } + +vmwVRNIAgent2021v660 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.8.0" + STATUS current + DESCRIPTION + "Release 6.8.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 202209070000Z fourteenth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12, + vmwNetworkInsightNotificationGroup13, + vmwNetworkInsightNotificationGroup14 + } + ::= { vmwVRNICapability 20 } + +vmwVRNIAgent2021v650 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.6.0" + STATUS current + DESCRIPTION + "Release 6.6.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 202203300000Z thirteenth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12, + vmwNetworkInsightNotificationGroup13 + } + ::= { vmwVRNICapability 19 } + +vmwVRNIAgent2021v640 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.4.0" + STATUS current + DESCRIPTION + "Release 6.4.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 202110010000Z twelth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12 + } + ::= { vmwVRNICapability 18 } + +vmwVRNIAgent2021v620 AGENT-CAPABILITIES + PRODUCT-RELEASE + "6.2.0" + STATUS current + DESCRIPTION + "Release 6.2.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 202105240000Z Eleventh Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11 + } + ::= { vmwVRNICapability 17 } + +vmwVRNIAgent2020v520 AGENT-CAPABILITIES + PRODUCT-RELEASE + "5.2.0" + STATUS current + DESCRIPTION + "Release 5.2.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 202005200000Z Tenth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10 + } + ::= { vmwVRNICapability 16 } + +vmwVRNIAgent2019v500 AGENT-CAPABILITIES + PRODUCT-RELEASE + "5.0.0" + STATUS current + DESCRIPTION + "Release 5.0.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 201908190000Z Ninth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9 + } + ::= { vmwVRNICapability 15 } + +vmwVRNIAgent2019v420 AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.2.0" + STATUS current + DESCRIPTION + "Release 4.2.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 201906060000Z Eighth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8 + } + ::= { vmwVRNICapability 14 } + +vmwVRNIAgent2019v410 AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.1.0" + STATUS current + DESCRIPTION + "Release 4.1.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 201903220000Z Seventh Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7 + } + ::= { vmwVRNICapability 13 } + +vmwVRNIAgent2018v400 AGENT-CAPABILITIES + PRODUCT-RELEASE + "4.0.0" + STATUS current + DESCRIPTION + "Release 4.0.0 for VMware VRNI. + It describes all the notifications sent from this version of VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 201812120000Z Sixth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6 + } + ::= { vmwVRNICapability 12 } + +vmwVRNIAgent2018v390 AGENT-CAPABILITIES + PRODUCT-RELEASE + "3.9.0" + STATUS current + DESCRIPTION + "Release 3.9.0 for VMware VRNI. + It describes all the notifications sent from the VRNI appliance." + REFERENCE + "http://www.vmware.com/products" + -- REVISION 201809120000Z Fifth Version + SUPPORTS VMWARE-VRNI-MIB + INCLUDES { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5 + } + ::= { vmwVRNICapability 11 } + +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
\ No newline at end of file diff --git a/MIBS/vmware/VMWARE-VRNI-MIB b/MIBS/vmware/VMWARE-VRNI-MIB new file mode 100644 index 0000000..c7a8938 --- /dev/null +++ b/MIBS/vmware/VMWARE-VRNI-MIB @@ -0,0 +1,4821 @@ +-- ********************************************************** +-- Copyright 2016 - 2022 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-VRNI-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + SnmpAdminString + FROM SNMP-FRAMEWORK-MIB + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + TEXTUAL-CONVENTION, DateAndTime + FROM SNMPv2-TC + vmwNetworkInsight + FROM VMWARE-ROOT-MIB + VmwLongSnmpAdminString + FROM VMWARE-TC-MIB; + + vmwNetworkInsightMIB MODULE-IDENTITY + LAST-UPDATED "202303100000Z" + 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 is for VMware vRealize Network Insight as described here: + https://www.vmware.com/support/pubs/vrealize-network-insight-pubs.html + " + + REVISION "202303100000Z" + DESCRIPTION + "This is the fifteenth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds four new notifications, see vmwNetworkInsightNotificationGroup15. + " + + REVISION "202209070000Z" + DESCRIPTION + "This is the fourteenth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds eight new notifications, see vmwNetworkInsightNotificationGroup14. + " + + REVISION "202203300000Z" + DESCRIPTION + "This is the thirteenth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds twenty four new notifications, see vmwNetworkInsightNotificationGroup13. + " + + REVISION "202110010000Z" + DESCRIPTION + "This is the twelfth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds five new notifications, see vmwNetworkInsightNotificationGroup12. + " + + REVISION "202105240000Z" + DESCRIPTION + "This is the eleventh revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds nineteen new notifications, see vmwNetworkInsightNotificationGroup11. + " + + REVISION "202005200000Z" + DESCRIPTION + "This is the tenth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds fifty two new notifications, see vmwNetworkInsightNotificationGroup10. + " + + REVISION "201908190000Z" + DESCRIPTION + "This is the ninth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds two new notifications, see vmwNetworkInsightNotificationGroup9. + " + + REVISION "201906060000Z" + DESCRIPTION + "This is the eighth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds two new notifications, see vmwNetworkInsightNotificationGroup8. + " + + REVISION "201903220000Z" + DESCRIPTION + "This is the seventh revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds seventeen new notifications, see vmwNetworkInsightNotificationGroup7. + " + + REVISION "201811270000Z" + DESCRIPTION + "This is the sixth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds fourteen new notifications, see vmwNetworkInsightNotificationGroup6. + " + + REVISION "201809120000Z" + DESCRIPTION + "This is the fifth revision of VMware vRealize Network Insight Manager SNMP notifications. + This revision introduces below changes, some of which are non backward compatible. + a. All event notifications have their varbind contents changed + from : OBJECTS { vmwAffectedObject, vmwEventSeverity, vmwVrniUrl, vmwTimestamp, vmwOperatorDesc, vmwEventName} + to : OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + + b. Syntax changes for TC - VmwVrniSeverity + was { cleared(0), info(1), major(2) } + is now VmwVrniSeverity {Critical, Moderate, Warning, Info and CLEARED} + + c. Support for new events added, see vmwNetworkInsightNotificationGroup5 + " + + REVISION "201709050000Z" + DESCRIPTION + "This is the fourth revision of VMware vRealize Network Insight Manager SNMP notifications. + It adds fourteen new notifications, see vmwNetworkInsightNotificationGroup4. + " + + REVISION "201706010000Z" + DESCRIPTION + "This is the third revision of VMware vRealize Network Insight Manager SNMP notifications. + This version added nineteen new notifications, see vmwNetworkInsightNotificationGroup3 + for complete listing." + + REVISION "201702200000Z" + DESCRIPTION + "This is the second revision of VMware vRealize Network Insight Manager SNMP notifications. + It introduces new notifications, see vmwNetworkInsightNotificationGroup2, + and updates existing notifications to append the vmwEventName managed object." + + + REVISION "201610260000Z" + DESCRIPTION + "This is the first revision of VMware vRealize Network Insight Manager SNMP notifications." + ::= { vmwNetworkInsight 1 } + + +vmwVRNIEvents OBJECT-IDENTITY + STATUS current + DESCRIPTION + "All notifications from vRealize Network Insight fall under this oid." + ::= { vmwNetworkInsightMIB 0 } + +vmwVRNIData OBJECT-IDENTITY + STATUS current + DESCRIPTION + "All variables that are sent in notifications fall under this oid." + ::= { vmwNetworkInsightMIB 1 } + +-- ********************************************************** +-- Type definitions +-- ********************************************************** + + VmwVrniSeverity ::= TEXTUAL-CONVENTION + DISPLAY-HINT "255t" + STATUS current + DESCRIPTION + "Represents Event Severity, the values returned by TC are + Critical - All events which are critical in nature towards overall health of environment, could be show stoppers if not fixed + Moderate - Represents moderate severity, part of functionality could get affected + Warning - Event which may not represent immediate issue but could soon become one if not addressed + Info - Informational notifications + CLEARED - Event was closed by system. + " + SYNTAX OCTET STRING (SIZE (0..255)) + +-- ********************************************************** +-- Notifications by an agent that implements this mib module +-- ********************************************************** + +vmwSnmpTrapsAreConfigured NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Initial trap to notify receiver that vRNI is now configured to send SNMP traps" + ::= { vmwVRNIEvents 101} + + +vmwSnmpTrapsAreDisabled NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Trap to notify receiver that vRNI is no longer configured to send SNMP traps" + ::= { vmwVRNIEvents 102} + + +vmwTestTrap NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Test Trap" + ::= { vmwVRNIEvents 103} + + +vmwEntityDiscoveryChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Discovery Event" + ::= { vmwVRNIEvents 20001} + +vmwEntityPropertiesChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Property Change Event" + ::= { vmwVRNIEvents 20002} + +vmwFirewallNotInstalledOnHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Firewall Not Installed On Host Event" + ::= { vmwVRNIEvents 20003} + +vmwHostWithStaleFirewallRulesEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host With Stale Firewall Rules Event" + ::= { vmwVRNIEvents 20004} + +vmwIpAddressChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Ip Address Change" + ::= { vmwVRNIEvents 20005} + +vmwL2GatewayAnomalyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "L2 Gateway Anomaly Event" + ::= { vmwVRNIEvents 20006} + +vmwL2NetworkAddressAnomalyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "L2 Network Address Anomaly Event" + ::= { vmwVRNIEvents 20007} + +vmwL2NetworkDiameterExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "L2 Network Diameter Exceeded Event" + ::= { vmwVRNIEvents 20008} + +vmwL2NetworkUplinkMissingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "L2 Network Uplink Missing Event" + ::= { vmwVRNIEvents 20009} + +vmwL2NetworkWithNoVMsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "L2 Network With No VMs Event" + ::= { vmwVRNIEvents 20010} + +vmwLayer2NetworkDiameterChangedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Layer2 Network Diameter Changed Event" + ::= { vmwVRNIEvents 20011} + +vmwMTUMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "MTU Mismatch Event" + ::= { vmwVRNIEvents 20012} + +vmwNetworkIsolationEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Network Isolation Event" + ::= { vmwVRNIEvents 20013} + +vmwNoPathEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "No Path Event" + ::= { vmwVRNIEvents 20014} + +vmwSpoofguardDisabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Spoofguard Disabled Event" + ::= { vmwVRNIEvents 20015} + +vmwVMotionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VMotion Event" + ::= { vmwVRNIEvents 20018} + +vmwVMWithDisconnectedVnicsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VM With Disconnected Vnics Event" + ::= { vmwVRNIEvents 20019} + +vmwVMWithMulipleVnicsOnDifferentVxlansEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VM With Multiple Vnics On Different Vxlans Event" + ::= { vmwVRNIEvents 20020} + +vmwVMWithMulipleVnicsOnSameL2Event NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VM With Multiple Vnics On Same L2 Event" + ::= { vmwVRNIEvents 20021} + +vmwVMWithNoIpAddressEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VM With No Ip Address Event" + ::= { vmwVRNIEvents 20022} + +vmwVTEPMissingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VTEP Missing Event" + ::= { vmwVRNIEvents 20023} + +vmwL2Event NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "L2 Event" + ::= { vmwVRNIEvents 20024} + +vmwMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Membership Change" + ::= { vmwVRNIEvents 20025} + +vmwSecurityGroupMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Security Group Membership Change" + ::= { vmwVRNIEvents 20026} + +vmwFirewallRuleMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Firewall Rule Membership Change" + ::= { vmwVRNIEvents 20027} + +vmwVlanMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vlan Membership Change" + ::= { vmwVRNIEvents 20028} + +vmwVxlanMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vxlan Membership Change" + ::= { vmwVRNIEvents 20029} + +vmwDeleteChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Delete Event" + ::= { vmwVRNIEvents 20030} + +vmwVtepFailedPingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VTEP Ping Failure Event" + ::= { vmwVRNIEvents 20031} + +vmwEmptySearchStreamChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Search with no results" + ::= { vmwVRNIEvents 20034} + +vmwSearchStreamMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Search results changed" + ::= { vmwVRNIEvents 20035} + +vmwEmptySearchStreamProblemEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Search with no results (Problem)" + ::= { vmwVRNIEvents 20036} + +vmwSearchStreamMembershipProblemEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Search results changed (Problem)" + ::= { vmwVRNIEvents 20037} + +vmwOspfConfigurationMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "OSPF Mismatch Event" + ::= { vmwVRNIEvents 20038} + +vmwServiceVMNotHealthyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Service VM Not Healthy Event" + ::= { vmwVRNIEvents 20039} + +vmwServiceVMNotPoweredOnEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Service VM Not Powered On Event" + ::= { vmwVRNIEvents 20040} + +vmwServiceVMHighCPUUsageEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Service VM High CPU Usage Event" + ::= { vmwVRNIEvents 20041} + +vmwServiceVMHighMemoryUsageEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Service VM High Memory Usage Event" + ::= { vmwVRNIEvents 20042} + +vmwServiceVMHighDiskUsageEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Service VM High Disk Usage Event" + ::= { vmwVRNIEvents 20043} + +vmwIPSetPropertiesChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "IPSet Change" + ::= { vmwVRNIEvents 20050} + +vmwFirewallRulePropertiesChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Firewall Rule Change" + ::= { vmwVRNIEvents 20051} + +vmwSecurityGroupPropertiesChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Security Group Change" + ::= { vmwVRNIEvents 20052} + +vmwIPSetMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "IPSet Membership Change" + ::= { vmwVRNIEvents 20053} + +vmwFirewallRuleMaskEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Firewall Rule Masked Event" + ::= { vmwVRNIEvents 20054} + +vmwSecurityMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Security Membership Change" + ::= { vmwVRNIEvents 20056} + +vmwSecurityTagPropertiesChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Security Tag Change" + ::= { vmwVRNIEvents 20057} + +vmwSecurityTagMembershipChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Security Tag Membership Change" + ::= { vmwVRNIEvents 20058} + +vmwHostDatastoreChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host datastores changed" + ::= { vmwVRNIEvents 20059} + +vmwVMDatastoreChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VM datastores changed" + ::= { vmwVRNIEvents 20060} + +vmwVMSnapshotChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VM snapshot changed" + ::= { vmwVRNIEvents 20061} + +vmwVMVirtualDiskChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Virtual disk migrated" + ::= { vmwVRNIEvents 20062} + +vmwIPSetDefinitionMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "IPSET Definition Mismatch Event" + ::= { vmwVRNIEvents 20063} + +vmwSegmentMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Segment Mismatch Event" + ::= { vmwVRNIEvents 20064} + +vmwVtepEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vtep Event" + ::= { vmwVRNIEvents 20065} + +vmwVtepConfigurationFaultEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vtep Configuration Fault Event" + ::= { vmwVRNIEvents 20066} + +vmwVtepSubnetMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vtep Subnet Mismatch Event" + ::= { vmwVRNIEvents 20068} + +vmwVtepCountMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vtep Count Mismatch Event" + ::= { vmwVRNIEvents 20069} + +vmwDLRNetworksNotReachableEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "DLR Routing event" + ::= { vmwVRNIEvents 20067} + +vmwEdgeNetworksNotReachableEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Edge Routing event" + ::= { vmwVRNIEvents 20070} + +vmwNiInfraChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NI Infra Change" + ::= { vmwVRNIEvents 20089} + +vmwDataSourceEnabledChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Data Source Enabled" + ::= { vmwVRNIEvents 20090} + +vmwDataSourceDisabledChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Data Source Disabled" + ::= { vmwVRNIEvents 20091} + +vmwDataSourceCreatedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Data Source Created" + ::= { vmwVRNIEvents 20092} + +vmwPlatformCpuCoreChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Platform CPU Change Event" + ::= { vmwVRNIEvents 20093} + +vmwPlatformDiskChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Platform Disk Change Event" + ::= { vmwVRNIEvents 20094} + +vmwPlatformMemoryChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Platform Memory Change Event" + ::= { vmwVRNIEvents 20095} + +vmwPlatformRebootedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Platform Reboot Change Event" + ::= { vmwVRNIEvents 20096} + +vmwProxyCpuCoreChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Collector CPU Change Event" + ::= { vmwVRNIEvents 20097} + +vmwProxyDiskChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Collector Disk Change Event" + ::= { vmwVRNIEvents 20098} + +vmwProxyMemoryChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Collector Memory Change Event" + ::= { vmwVRNIEvents 20099} + +vmwProxyRebootedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Collector Reboot Change Event" + ::= { vmwVRNIEvents 20100} + +vmwNIClusterChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Cluster Change Event" + ::= { vmwVRNIEvents 20101} + +vmwNISystemProxyChangeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "System Proxy Change Event" + ::= { vmwVRNIEvents 20102} + +vmwNIClusterCreateEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Cluster Create Event" + ::= { vmwVRNIEvents 20103} + +vmwThresholdExceededEventCpuReady NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded Cpu Ready" + ::= { vmwVRNIEvents 30001} + +vmwThresholdExceededEventCpuCoStop NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded Cpu Co Stop" + ::= { vmwVRNIEvents 30002} + +vmwThresholdExceededEventDiskCommandAbortRule NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded Disk Command Abort Rule" + ::= { vmwVRNIEvents 30003} + +vmwThresholdExceededEventIODeviceLatencyRule NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded IO Device Latency Rule" + ::= { vmwVRNIEvents 30004} + +vmwThresholdExceededEventIOKernelLatencyRule NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded IO Kernel Latency Rule" + ::= { vmwVRNIEvents 30005} + +vmwThresholdExceededEventMemorySwapInRule NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded Memory Swap In Rule" + ::= { vmwVRNIEvents 30006} + +vmwThresholdExceededEventMemorySwapOutRule NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded Memory Swap Out Rule" + ::= { vmwVRNIEvents 30007} + +vmwThresholdExceededEventNetworkRxDropRule NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded Memory Rx Drop Rule" + ::= { vmwVRNIEvents 30008} + +vmwThresholdExceededEventNetworkTxDropRule NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Threshold Exceeded Memory Tx Drop Rule" + ::= { vmwVRNIEvents 30009} + +vmwAWSRegionSGLimitEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "AWS Region Security Group count near threshold." + ::= { vmwVRNIEvents 30010} + +vmwAWSVPCSGLimitEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "AWS VPC Security Group count near threshold." + ::= { vmwVRNIEvents 30011} + +vmwAWSSGInboundRuleLimitEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "AWS Security Group Inbound Rule count near threshold." + ::= { vmwVRNIEvents 30012} + +vmwAWSSGOutboundRuleLimitEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "AWS Security Group Outbound Rule count near threshold." + ::= { vmwVRNIEvents 30013} + +vmwAWSInterfaceSGLimitEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "AWS VPC Security Group count near threshold." + ::= { vmwVRNIEvents 30014} + +vmwPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Packet Drop Event" + ::= { vmwVRNIEvents 30100} + +vmwSwitchPortPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Switch Port Packet Drop" + ::= { vmwVRNIEvents 30101} + +vmwRouterInterfacePacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Router Interface Packet Drop" + ::= { vmwVRNIEvents 30102} + +vmwVnicPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vnic Packet Drop" + ::= { vmwVRNIEvents 30103} + +vmwVTEPUnderlayPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VTEP Underlay Packet Drop" + ::= { vmwVRNIEvents 30104} + +vmwPnicUnderlyingSwitchPortPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "PNIC Underlying Switch Port Packet Drop" + ::= { vmwVRNIEvents 30105} + +vmwDevicePacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Device Packet Drop" + ::= { vmwVRNIEvents 30106} + +vmwThresholdExceededEventDatastoreFreeSpaceWarning NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "ThresholdExceededEventDatastoreFreeSpaceWarning" + ::= { vmwVRNIEvents 30203} + +vmwThresholdExceededEventDatastoreFreeSpaceCritical NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "ThresholdExceededEventDatastoreFreeSpaceCritical" + ::= { vmwVRNIEvents 30204} + +vmwThresholdExceededEventDatastoreReadLatency NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "ThresholdExceededEventDatastoreReadLatency" + ::= { vmwVRNIEvents 30205} + +vmwThresholdExceededEventDatastoreWriteLatency NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "ThresholdExceededEventDatastoreWriteLatency" + ::= { vmwVRNIEvents 30206} + +vmwDistributedFirewallApplyHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Distributed Firewall Apply Host Event" + ::= { vmwVRNIEvents 35001} + +vmwDistributedFirewallApplyVMEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Distributed Firewall Apply VM Event" + ::= { vmwVRNIEvents 35002} + +vmwNsxEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Event" + ::= { vmwVRNIEvents 35003} + +vmwFeatureImpactedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Feature Impacted Event" + ::= { vmwVRNIEvents 35004} + +vmwClusterFeatureVersionMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Cluster Feature Mismatch Event" + ::= { vmwVRNIEvents 36022} + +vmwHostFeatureVersionMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Feature Mismatch Event" + ::= { vmwVRNIEvents 36023} + +vmwFeatureVersionMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Feature Version Mismatch Event" + ::= { vmwVRNIEvents 36024} + +vmwHostFeatureEnabledMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Feature Enabled Mismatch Event" + ::= { vmwVRNIEvents 36025} + +vmwHostFeatureInstalledMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Feature Installed Mismatch Event" + ::= { vmwVRNIEvents 36026} + +vmwHostVtepNotFoundEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Vtep Not Found Event" + ::= { vmwVRNIEvents 36027} + +vmwHostVtepDisconnectedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Vtep Disconnected Event" + ::= { vmwVRNIEvents 36028} + +vmwHostVtepEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Vtep Event" + ::= { vmwVRNIEvents 36029} + +vmwClusterHostsVtepMTUMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Vtep Mtu Mismatch Event" + ::= { vmwVRNIEvents 36030} + +vmwFeatureUnhealthyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Feature Health Event" + ::= { vmwVRNIEvents 36031} + +vmwEdgeHANotConfiguredEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Edge High Availability is not enabled Event" + ::= { vmwVRNIEvents 36032} + +vmwEdgeInterfacesDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or More NSX Edge Interfaces are down Event" + ::= { vmwVRNIEvents 36033} + +vmwModuleUnhealthyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Module Unhealthy Event" + ::= { vmwVRNIEvents 36041} + +vmwModuleNotLoadedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Module Not Loaded Event" + ::= { vmwVRNIEvents 36042} + +vmwModuleNetworkConnectionFailureEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Module Network Connection Failure Event" + ::= { vmwVRNIEvents 36043} + +vmwHostNetworkControlPlaneMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Control Plane Network Mismatch Event" + ::= { vmwVRNIEvents 36044} + +vmwHostNetworkControlPlaneConnectionFailureEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Control Plane Network Connection Failure Event" + ::= { vmwVRNIEvents 36045} + +vmwHostNetworkControlPlaneNotSyncedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Control Plane Sync Failure Event" + ::= { vmwVRNIEvents 36046} + +vmwNSXControllerClusterMajorityEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Controller Cluster Majority Event" + ::= { vmwVRNIEvents 36047} + +vmwNSXControllersVMOnSameHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Controllers VM On Same Host Event" + ::= { vmwVRNIEvents 36048} + +vmwVxLanRangeExhaustEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vxlan range exhaust Event" + ::= { vmwVRNIEvents 36049} + +vmwNSXFirewallDefaultAllowAllRulesEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Firewall Allow All Rules Event" + ::= { vmwVRNIEvents 36050} + +vmwLogicalRouterNoUplinkEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The NSX DLR is not configured with default route and may prevent external communication. + Check if the router configuration is only for routing between internal networks, or if external access is required. If external access is required, then configure an uplink interface on the NSX distributed logical router. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 36051} + +vmwEdgeNotHAEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Edge not Highly Available Event" + ::= { vmwVRNIEvents 36052} + +vmwEdgeNotDeployedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Edge not deployed Event" + ::= { vmwVRNIEvents 36053} + +vmwEcmpIsEnabledAndStatefulServicesAreUpEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Edge Running with both ECMP and Stateful Edge Services Event" + ::= { vmwVRNIEvents 36054} + +vmwLogicalRouterDeployedOnEcmpEdgeHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Logical Router and ECMP Edge on Same Host Event" + ::= { vmwVRNIEvents 36055} + +vmwEdgeMissingInterfaceOSPFAreaMappingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Edge Interface to OSPF Area Mapping Missing Event" + ::= { vmwVRNIEvents 36056} + +vmwOspfInsecureAuthRouterEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or more OSPF areas on the NSX Edge are using insecure authentication Event" + ::= { vmwVRNIEvents 36057} + +vmwNSXControllersDeployedCountEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Controller count Event" + ::= { vmwVRNIEvents 36058} + +vmwNSXControllerNotActiveCountEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Controller Not Active Event" + ::= { vmwVRNIEvents 36059} + +vmwNSXControllerEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Controller Event" + ::= { vmwVRNIEvents 36060} + +vmwNSXEcmpEdgeDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or more NSX Edges in the ECMP Cluster are currently down" + ::= { vmwVRNIEvents 36061} + +vmwNSXMajorityEcmpEdgesDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The majority of NSX Edges in the ECMP Cluster are currently down" + ::= { vmwVRNIEvents 36062} + +vmwNSXAllEcmpEdgesDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "All NSX Edges in the ECMP Cluster are currently down" + ::= { vmwVRNIEvents 36063} + +vmwNSXEdgeMtuMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The MTU configured on one or more interfaces on the Edge does not match the MTU on the next hop router" + ::= { vmwVRNIEvents 36064} + +vmwNSXEdgeSplitBrainEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Both VMs of Edge HA are in active state" + ::= { vmwVRNIEvents 36065} + +vmwVirtualDistributedRoutingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VDR Port Unset Event" + ::= { vmwVRNIEvents 36066} + +vmwNSXComponentEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Service not running event" + ::= { vmwVRNIEvents 35221} + +vmwNSXBackupEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Backup not configured" + ::= { vmwVRNIEvents 35222} + +vmwNSXBackupAuditLogExcludedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Audit Log excluded from NSX Backup" + ::= { vmwVRNIEvents 35223} + +vmwNSXUnsecureBackupEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Backups not using secure FTP" + ::= { vmwVRNIEvents 35224} + +vmwNSXBackupSystemEventsExcludedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "System Event excluded from NSX Backup" + ::= { vmwVRNIEvents 35225} + +vmwNSXBackupNotScheduledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Scheduled backups are not enabled" + ::= { vmwVRNIEvents 35226} + +vmwNSXBackupNotRecordedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "No backup of the environment has been recorded" + ::= { vmwVRNIEvents 35227} + +vmwNSXNtpServerEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NTP Server not configured" + ::= { vmwVRNIEvents 35228} + +vmwNSXSysLogServerEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Syslog Server not configured" + ::= { vmwVRNIEvents 35229} + +vmwControllerSysLogServerEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Syslog Server not configured" + ::= { vmwVRNIEvents 35230} + +vmwNSXIpV6EnabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "IPv6 is enabled for NSX Manager" + ::= { vmwVRNIEvents 35231} + +vmwNSXOspfNeighborDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or more OSPF Neighbors down" + ::= { vmwVRNIEvents 35232} + +vmwGenericNSXSystemEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX System Event (Warning)" + ::= { vmwVRNIEvents 70000} + +vmwOtherCriticalNSXEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX System Event (Critical)" + ::= { vmwVRNIEvents 71000} + +vmwFilterConfigApplyOnHostFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Filter Config Apply On Host Failed Event" + ::= { vmwVRNIEvents 70001} + +vmwRulesetLoadOnHostFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Ruleset Load On Host Failed Event" + ::= { vmwVRNIEvents 70002} + +vmwConfigUpdateOnHostFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Config Update On Host Failed Event" + ::= { vmwVRNIEvents 70003} + +vmwSpoofguardConfigUpdateOnHostFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Spoofguard Config Update On Host Failed Event" + ::= { vmwVRNIEvents 70004} + +vmwApplyRuleToVnicFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Apply Rule To Vnic Failed Event" + ::= { vmwVRNIEvents 70005} + +vmwContainerConfigUpdateOnVnicFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Container Config Update On Vnic Failed Event" + ::= { vmwVRNIEvents 70006} + +vmwSpoofguardApplyToVnicFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Spoofguard Apply To Vnic Failed Event" + ::= { vmwVRNIEvents 70007} + +vmwHostMessagingConfigurationFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Messaging Configuration Failed Event" + ::= { vmwVRNIEvents 70008} + +vmwHostMessagingConnectionReconfigurationFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Messaging Connection Reconfiguration Failed Event" + ::= { vmwVRNIEvents 70009} + +vmwHostMessagingConfigurationFailedNotificationSkippedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Messaging Configuration Failed Notification Skipped Event" + ::= { vmwVRNIEvents 70010} + +vmwHostMessagingInfrastructureDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host Messaging Infrastructure Down Event" + ::= { vmwVRNIEvents 70011} + +vmwEdgeVMNotRespondingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Edge VM Responding Event" + ::= { vmwVRNIEvents 70012} + +vmwEdgeUnhealthyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Edge Health Event" + ::= { vmwVRNIEvents 70013} + +vmwEdgeVMCommunicationFailureEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Edge communication failure Event" + ::= { vmwVRNIEvents 70014} + +vmwNSXEdgeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Edge Event" + ::= { vmwVRNIEvents 70015} + +vmwPanEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Palo Alto Event" + ::= { vmwVRNIEvents 80000} + +vmwPanNsxNotInRegisteredStateEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Palo Alto NSX Registration Event" + ::= { vmwVRNIEvents 80001} + +vmwPanNsxDynamicUpdateDelayedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Palo Alto NSX Dynamic Update Event" + ::= { vmwVRNIEvents 80002} + +vmwPanDeviceInDisconnectedStateEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Palo Alto Device Disconnect Event" + ::= { vmwVRNIEvents 80003} + +vmwPanNsxServiceApplianceViewMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Palo Alto Service Device Mismatch Event" + ::= { vmwVRNIEvents 80004} + +vmwPanNsxFabricAgentNotFoundOnHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Fabric Agent Not Found Event" + ::= { vmwVRNIEvents 80005} + +vmwPanNsxServiceVMNotFoundOnHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Palo Alto Service VM Not Found Event" + ::= { vmwVRNIEvents 80006} + +vmwCheckpointEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Check Point Event" + ::= { vmwVRNIEvents 80100} + +vmwCheckpointNsxFabricAgentNotFoundOnHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Check Point NSX Fabric Agent Not Found Event" + ::= { vmwVRNIEvents 80102} + +vmwCheckpointNsxServiceVMNotFoundOnHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Check Point Service VM Not Found Event" + ::= { vmwVRNIEvents 80103} + +vmwCheckpointGatewaySicStatusNotCommunicatingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Check Point Gateway Sic Status Not Communicating Event" + ::= { vmwVRNIEvents 80104} + +vmwCheckpointNsxServiceApplianceViewMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Check Point Service VM Mismatch Event" + ::= { vmwVRNIEvents 80105} + +vmwCriticalHostNotAccessibleEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Host with VMs running critical services is not accessible" + ::= { vmwVRNIEvents 40001} + +vmwIndexerLagEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Index Lag Event" + ::= { vmwVRNIEvents 80501} + +vmwIPFIXFlowDPPausedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "IPFIX Flow Data Provider Paused Event" + ::= { vmwVRNIEvents 80502} + +vmwGridProcessingStoppedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Grid Processing Stopped Event" + ::= { vmwVRNIEvents 80503} + +vmwUnableToSendEmailsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Unable to Send Emails Event" + ::= { vmwVRNIEvents 80504} + +vmwSMTPNotConfiguredEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "SMPT Not Configured Event" + ::= { vmwVRNIEvents 80505} + +vmwSNMPNotConfiguredEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "SNMP Not Configured Event" + ::= { vmwVRNIEvents 80506} + +vmwReindexingInProgressEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Redindexing In Process Event" + ::= { vmwVRNIEvents 80507} + +vmwNodesVersionMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Node Version Mismatch Event" + ::= { vmwVRNIEvents 80508} + +vmwNotAllServicesRunningEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Not All Services Running Event" + ::= { vmwVRNIEvents 80509} + +vmwNotAllServicesHealthyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Not All Services Healthy Event" + ::= { vmwVRNIEvents 80510} + +vmwExpandPartitionFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Expand Partition Failed Event" + ::= { vmwVRNIEvents 80511} + +vmwDiskCleanupFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Disk Cleanup Failed Event" + ::= { vmwVRNIEvents 80512} + +vmwVaccumFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Vacuum Failed Event" + ::= { vmwVRNIEvents 80513} + +vmwConfigStoreCleanupFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Config Store Cleanup Failed Event" + ::= { vmwVRNIEvents 80514} + +vmwHBaseRetentionToolFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HBASE Retention Tool Failed Event" + ::= { vmwVRNIEvents 80515} + +vmwMetricStoreUpdaterFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Metric Store Updater Failed Event" + ::= { vmwVRNIEvents 80516} + +vmwCollectorLagEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Collecter Lag Event" + ::= { vmwVRNIEvents 80517} + +vmwCollectionLagEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Collection Lag Event" + ::= { vmwVRNIEvents 80518} + +vmwGridProcessingLagEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Grid Processing Lag Event" + ::= { vmwVRNIEvents 80519} + +vmwConnectionErrorEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Connection Error Event" + ::= { vmwVRNIEvents 80520} + +vmwNodeNotActiveEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Node Not Active Event" + ::= { vmwVRNIEvents 80521} + +vmwHighDiskUtilizationEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "High Disk Utilization Event" + ::= { vmwVRNIEvents 80522} + +vmwIndexingAbortedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Indexing Aborted Event" + ::= { vmwVRNIEvents 80523} + +vmwUpgradeFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Upgrade Failed Event" + ::= { vmwVRNIEvents 80524} + +vmwFlowProcessingSuspendedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Flow Processing Suspended Event" + ::= { vmwVRNIEvents 80525} + +vmwVCNotOnSameProxyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VC_NOT_ON_SAME_PROXY_EVENT" + ::= { vmwVRNIEvents 80643} + +vmwNoDVSAvailableEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NO_DVS_AVAILABLE_EVENT" + ::= { vmwVRNIEvents 80642} + +vmwUnknownInfobloxVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Infoblox version cannot be determined" + ::= { vmwVRNIEvents 80641} + +vmwUnsupportedInfobloxVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The version of Infoblox is not supported" + ::= { vmwVRNIEvents 80640} + +vmwIncorrectInfobloxCredentialEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Invalid credentials or insufficient privileges" + ::= { vmwVRNIEvents 80639} + +vmwInfobloxRecordLimitExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The number of A records fetched from Infoblox exceeds the current limit" + ::= { vmwVRNIEvents 80638} + +vmwWebhookNotRunningEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "WEBHOOK_NOT_RUNNING_EVENT" + ::= { vmwVRNIEvents 80637} + +vmwIncorrectWebhookConfiguredOnAlertEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "INCORRECT_WEBHOOK_CONFIGURED_ON_ALERT_EVENT" + ::= { vmwVRNIEvents 80636} + +vmwWebhookNotEnabledOnAlertEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "WEBHOOK_NOT_ENABLED_ON_ALERT_EVENT" + ::= { vmwVRNIEvents 80635} + +vmwVRNIContentPackNotInstalledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "vRNI_CONTENT_PACK_NOT_INSTALLED_EVENT" + ::= { vmwVRNIEvents 80634} + +vmwUnsupportedVRNIContentPackVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "UNSUPPORTED_vRNI_CONTENT_PACK_VERSION_EVENT" + ::= { vmwVRNIEvents 80633} + +vmwUnsupportedLogInsightVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "UNSUPPORTED_LOG_INSIGHT_VERSION_EVENT" + ::= { vmwVRNIEvents 80632} + +vmwComputeManagersNotAddedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "COMPUTE_MANAGERS_NOT_ADDED_EVENT" + ::= { vmwVRNIEvents 80631} + +vmwComputeManagersNotFoundEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "COMPUTE_MANAGERS_NOT_FOUND_EVENT" + ::= { vmwVRNIEvents 80630} + +vmwUnsupportedNSXTVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "UNSUPPORTED_NSXT_VERSION_EVENT" + ::= { vmwVRNIEvents 80629} + +vmwNotEmptyNodeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NOT_EMPTY_NODE_EVENT" + ::= { vmwVRNIEvents 80628} + +vmwFlowPhysicalNodeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "FLOW_PHYSICAL_NODE_EVENT" + ::= { vmwVRNIEvents 80627} + +vmwFlowCollectionErrorEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "FLOW_COLLECTION_ERROR_EVENT" + ::= { vmwVRNIEvents 8061313} + +vmwAWSThrottlingExceptionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "AWS_THROTTLING_EXCEPTION_EVENT" + ::= { vmwVRNIEvents 8061314} + +vmwAWSFlowLogAccessDeniedExceptionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "AWS_FLOW_LOG_ACCESS_DENIED_EXCEPTION_EVENT" + ::= { vmwVRNIEvents 8061315} + +vmwNSXIPFIXStatusMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX_IPFIX_STATUS_MISMATCH_EVENT" + ::= { vmwVRNIEvents 80626} + +vmwNumVMsOrHostsNotFoundEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NUM_VMS_OR_HOSTS_NOT_FOUND_EVENT" + ::= { vmwVRNIEvents 80625} + +vmwUnsupportedNSXVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "UNSUPPORTED_NSX_VERSION_EVENT" + ::= { vmwVRNIEvents 806100018} + +vmwPwdAuthModeDisabledAristaEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "PWD_AUTH_MODE_DISABLED_ARISTA_EVENT" + ::= { vmwVRNIEvents 806100012} + +vmwHostnameResolutionErrorEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HOSTNAME_RESOLUTION_ERROR_EVENT" + ::= { vmwVRNIEvents 80624} + +vmwPrimaryNSXNotAddedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "PRIMARY_NSX_NOT_ADDED_EVENT" + ::= { vmwVRNIEvents 80623} + +vmwDataProviderNotRunningEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "DATA_PROVIDER_NOT_RUNNING_EVENT" + ::= { vmwVRNIEvents 80622} + +vmwInvalidResponseFromDatasourceEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "INVALID_RESPONSE_FROM_DATASOURCE_EVENT" + ::= { vmwVRNIEvents 80621} + +vmwHostNotReachableEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HOST_NOT_REACHABLE_EVENT" + ::= { vmwVRNIEvents 80620} + +vmwNSXControllerNotFoundEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX_CONTROLLER_NOT_FOUND_EVENT" + ::= { vmwVRNIEvents 80619} + +vmwUnexpectedDSTypeOrVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "UNEXPECTED_DS_TYPE_OR_VERSION_EVENT" + ::= { vmwVRNIEvents 80618} + +vmwWarnConfigEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "WARN_CONFIG_EVENT" + ::= { vmwVRNIEvents 80617} + +vmwInvalidConfigEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "INVALID_CONFIG_EVENT" + ::= { vmwVRNIEvents 80616} + +vmwNotFoundEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NOT_FOUND_EVENT" + ::= { vmwVRNIEvents 80614} + +vmwInsufficientPrivilegesEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "INSUFFICIENT_PRIVILEGES_EVENT" + ::= { vmwVRNIEvents 80613} + +vmwPwdAuthModeDisabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "PWD_AUTH_MODE_DISABLED_EVENT" + ::= { vmwVRNIEvents 80612} + +vmwFailedCredsEncryptEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "FAILED_CREDS_ENCRYPT_EVENT" + ::= { vmwVRNIEvents 80611} + +vmwSNMPConnectionInvalidEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "SNMP_CONNECTION_INVALID_EVENT" + ::= { vmwVRNIEvents 80609} + +vmwUnknownHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "UNKNOWN_HOST_EVENT" + ::= { vmwVRNIEvents 80608} + +vmwInvalidCredentialsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "INVALID_CREDENTIALS_EVENT" + ::= { vmwVRNIEvents 80606} + +vmwIncorrectConnectionStringEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "INCORRECT_CONNECTION_STRING_EVENT" + ::= { vmwVRNIEvents 80605} + +vmwConnectionRefusedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "CONNECTION_REFUSED_EVENT" + ::= { vmwVRNIEvents 80603} + +vmwTimeoutEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "TIMEOUT_EVENT" + ::= { vmwVRNIEvents 80602} + +vmwFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "FAILED_EVENT" + ::= { vmwVRNIEvents 80601} + +vmwNSXTEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Event" + ::= { vmwVRNIEvents 80200} + +vmwNSXTVcNotAddedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VC Not Added As Data Source Event" + ::= { vmwVRNIEvents 80201} + +vmwNSXTStandaloneHostsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Standalone hosts added in NSX-T Event" + ::= { vmwVRNIEvents 80202} + +vmwLargeSdmsDroppedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Data Processing Error" + ::= { vmwVRNIEvents 80526} + +vmwNSXTIPFixDFWStatusNotEnabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSXT_IPFIX_DFW_STATUS_NOT_ENABLED_EVENT" + ::= { vmwVRNIEvents 80650} + +vmwNSXTIPFixPortIncorrectEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSXT_IPFIX_PORT_INCORRECT_EVENT" + ::= { vmwVRNIEvents 80649} + +vmwNSXTIPFixCollectorAndIPFixProfileMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSXT_IPFIX_COLLECTOR_AND_IPFIX_PROFILE_MISMATCH_EVENT" + ::= { vmwVRNIEvents 80648} + +vmwNSXTIPFixIPFixProfilePriorityNotZeroEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSXT_IPFIX_IPFIX_PROFILE_PRIORITY_NOT_ZERO_EVENT" + ::= { vmwVRNIEvents 80647} + +vmwNSXTIPFixNoIPFixProfileEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSXT_IPFIX_NO_IPFIX_PROFILE_EVENT" + ::= { vmwVRNIEvents 80646} + +vmwNSXTIPFixNoNewCollectorProfileCanBeAddedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSXT_IPFIX_NO_NEW_COLLECTOR_PROFILE_CAN_BE_ADDED_EVENT" + ::= { vmwVRNIEvents 80645} + +vmwNSXTIPFixNoCollectorProfileEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSXT_IPFIX_NO_COLLECTOR_PROFILE_EVENT" + ::= { vmwVRNIEvents 80644} + +vmwNSXTSystemEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "These are the alarms/events reported by NSX-T. 'Source Component' specifies the entity emmitting this event. + It can be Manager/Controller/Edge. Combination of fields like Source Component, Event Type, Severity and message can be used to troubleshoot NSX-T appliance. + For further information, log into NSX-T Manager UI and visit Dashboard" + ::= { vmwVRNIEvents 80203} + +vmwNSXTNoUplinkConnectivityEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Tier-1 logical router is disconnected from Tier-0 router. Networks under this router are not reachable from outside and vice versa. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80205} + +vmwNSXTRoutingAdvertisementEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Routing advertisement is disabled for NSX-T Tier-1 logical router. Networks under this router are not reachable from outside. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80206} + +vmwNSXTManagerConnectivityDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Node has lost manager connectivity. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80207} + +vmwNSXTControllerConnectivityDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Node is not able to communicate with one or more controllers. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80208} + +vmwNSXTControllerConnectivityDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Node is not able to communicate with any of the controllers. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80209} + +vmwNSXTMtuMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The MTU configured on interface(s) of Tier-0 logical router do not match with the interface(s) of uplink switch/router from same L2 network. This may impact network performance. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80210} + +vmwNSXEdgeBGPNeighbourDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or more BGP neighbours are not in established state. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 36067} + +vmwAnalyticsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Meta event for Analytics Event + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 37001} + +vmwAnalyticsOutlierEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Meta event for Outlier Events + For more details, please log into vRNI, navigate to Settings -> Events. + " + ::= { vmwVRNIEvents 37002} + +vmwAnalyticsThresholdEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Meta event for Threshold Events + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 37003} + +vmwVMCEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Meta event for VMC Events. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 38001} + +vmwPolicyManagerVrniDfwIPFixCollectorAbsent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Network Insight IPFIX Collector is absent on VMC Policy Manager. + For more details, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80652} + +vmwPolicyManagerNoDfwIPFixProfile NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "DFW IPFIX Profile is absent on VMC Policy Manager. + For more details, please log into vRNI, navigate to Settings -> Events." + ::= { vmwVRNIEvents 80651} + +vmwNSXTExcludedVmFlowEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or more VMs are not protected by NSX-T DFW firewall. Network Insight will not receive IPFIX flows for these VMs. + Remove the relevant logical switches, logical ports or security groups from the NSX-T firewall exclusion list to enable flows. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80211} + +vmwNSXTDoubleVlanTaggingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Communication will be disrupted because Vlan on uplink port of Tier 0 router is different than Vlan on the external gateway. + Vlan is misconfigured on the tier-0 router. Make sure Vlan matches with the Vlan on the external gateway. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80212} + +vmwNSXTNoTzAttachedOnTnEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Transport node is not attached to any transport zone. VMs might loose connectivity because of this. + Ensure that the transport node is attached to some transport zone. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80213} + +vmwNSXTVtepDeleteEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "All vteps are deleted from the transport node. VMs might loose connectivity because of this. + Make sure vteps/vmknics are not deleted from the transport node. You may check all available vteps/vmknics in NSX-T->Fabric Nodes->Transport Node->Monitor of each of the impacted transport nodes. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80214} + +vmwDuplicateL3SwitchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Same Switch or Router is added with different IPs. VM to VM path may not be generated. + Delete duplicate Switches or Routers from Data Source. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80215} + +vmwLBPoolMemberDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when pool member of load balancer is down. + Ensure that pool member has not been disabled by the administrator. + Ensure that pool/pool-member uses the correct Health Monitors which are getting required responses from the backend server. + Ensure that backend server used by this pool member is functional. + For more details, log into Load Balancer UI, navigate to Local Traffic -> Pools -> Pools List. + Also check documentation at https://support.f5.com/csp/article/K12531 + Alternatively, you can log into vRNI UI and search 'Pool Member where state = DISABLED'. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80216} + +vmwLBPoolDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when pool of load balancer is down. + Ensure that pool has at least one functional pool member. + For more details, log into Load Balancer UI, navigate to Local Traffic -> Pools + Also check documentation at https://support.f5.com/csp/article/K12531 + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80217} + +vmwLBPoolEmptyEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when pool of load balancer is empty. + Ensure that pool has at least one pool member. + For more details, log into Load Balancer UI, navigate to Local Traffic -> Pools + Also check documentation at https://support.f5.com/csp/article/K12531 + Alternatively, you can log into vRNI and search 'Pool where PoolMembers Count = 0'. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80218} + +vmwLBPoolMemberVMDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when VM associated with pool member of load balancer is down. + Check if VM associated with pool member is powered on and running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80219} + +vmwLBVirtualServerDisableEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when virtual server of load balancer is disabled. + To enable virtual server, open load balancer GUI and check virtual server state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80220} + +vmwLBServiceNodeIPNotFoundEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when no NIC associated with IP of service node of load balancer is found. + Ensure that VM which has IP of Service Node exist. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80221} + +vmwLBServiceNodeMultipleNicFoundEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when multiple NICs associated with IP of service node of load balancer are found. + For more details about this event, please log into vRNI, navigate to Settings -> Events." + ::= { vmwVRNIEvents 80222} + +vmwKubernetesInsufficientPrivilegesEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or more Kubernetes Cluster Service Accounts do not have sufficient privileges. + Please verify that all Kubernetes Cluster Service Accounts has List and Watch privileges. + Refer - https://kubernetes.io/docs/reference/access-authn-authz/rbac/#service-account-permissions + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80655} + +vmwPKSKubernetesUnknownHostEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Please verify the Kubernetes Cluster API Servers are reachable from Collector VM. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80654} + +vmwDatasourceIdentificationChangedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The data source identity information such as certificate or the key has changed. + Re-verify the identity information on data source page in vRNI. + System will auto accept the new identification. If issue persists for more than an hour, please contact support. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80653} + +vmwArkinApplicationMemberLimitEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Number of members in application exceeds supported limit. + Reduce number of members in the application. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 568} + +vmwNSXTSwitchIpfixEnabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Network Insight does not support the IPFIX flow data from NSX-T Switches. It is configured to send IPFIX data to one of the Network Insight Collector VM. It may have corrupted existing flow data in the system. + Remove Network Insight Collector VM IP Address from the NSX-T Switch collector profiles which are used in NSX-T Switch IPFIX profiles. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80223} + +vmwUANIFileNotProvidedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Configuration file required by Generic Routers & Switches Data Source has not been provided while data source creation. To resolve this issue, please go to vRNI web UI, under settings page, edit intended Generic Routers & Switches Data Source and add configuration file. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80657} + +vmwUANIFileDoesNotExistEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Configuration file required by Generic Routers & Switches Data Source has been deleted manually or moved. To resolve this issue, please go to vRNI web UI, under settings page, edit intended Generic Routers & Switches Data Source and add configuration file. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80658} + +vmwNSXTStandaloneHostsWithoutVcEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "vCenter managing one or more fabric nodes in NSX-T is not added as a data source in vRNI. Virtual Machines on those hosts will not be visible in vRNI. + Please add the vCenter server managing the standalone hosts as a datasource into vRNI at- Settings -> Accounts and Data Sources -> Add Source -> VMware vCenter + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80224} + +vmwApplianceNotConfiguredEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Collector VM configuration is incomplete. + To reconfigure proxy, please run 'setup' CLI from console mode. + https://docs.vmware.com/en/VMware-vRealize-Network-Insight/3.8/com.vmware.vrni.cli.doc/GUID-B48AD03A-5FC8-4396-9C27-9523307C688C.html + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80527} + +vmwSwitchPortOperationalDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Switchport operational status change detected. It is operationally down. This may impact the network traffic on the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30111} + +vmwRouterInterfaceOperationalDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Router interface operational status change detected. It is operationally down. This may impact the network traffic on the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30112} + +vmwUnderlayDeviceGenericEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This is generic representation for events on Underlay device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30114} + +vmwUnderlayDeviceFexOfflineEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A FEX has gone offline on the device. Please check the FEX status on the device. This may impact the network traffic on the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30115} + +vmwUnderlayDeviceFanMalFunctionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A fan on the device is not either removed or not working. It may impact the overheating of the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30116} + +vmwUnderlayDeviceTemperatureThresholdExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A module on the device has reported major/minor temperature alarm. Please check the sensor mentioned in the event message on the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30117} + +vmwUnderlayDeviceFexFanMalFunctionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A fan on the FEX chassis is either removed or not working. It may impact the overheating of the FEX device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30118} + +vmwUnderlayDeviceFexPsMalFunctionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A Power supply on the FEX chassis is either removed or not working. It may impact the FEX device functionality. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30119} + +vmwUnderlayDeviceModuleMalFunctionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A module/line card on the device is either removed or not working. This may impact the network traffic on the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30120} + +vmwUnderlayDevicePsMalFunctionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A Power supply on the device is either removed or not working. It may impact the device functionality. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30121} + +vmwUnderlayDeviceBfdSessionRemovedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A BFD session is deleted on the device. This will result in routing table changes and may impact the network traffic on the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30122} + +vmwUnderlayDeviceLldpNeighbourRemovedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A LLDP neighbour is removed from the device. This will result in the network topology changes and may impact the network traffic on the device. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30123} + +vmwThresholdExceededEventDataSourceCpuUsage NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A threshold-crossing CPU usage detected on host FRUs. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30198} + +vmwThresholdExceededEventDataSourceMemoryUsage NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A threshold-crossing memory usage detected on host FRUs. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30199} + +vmwThresholdExceededEventDataSourceTemperature NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "A threshold-crossing temperature detected on host FRUs. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30200} + +vmwDeploymentDefMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Capacity configuration is mismatched. Please reconfigure. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80532} + +vmwNsxtLatencyServiceConfigMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The Latency Service Config configured on NSX-T is different from this Network Insight deployment. As a result, Network Insight is not receiving Latency information from NSX-T. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80669} + +vmwNsxtLatencyNodeGroupMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The Latency Node Group configured on NSX-T is different from this Network Insight deployment. As a result, Network Insight is not receiving Latency information from NSX-T. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80668} + +vmwNsxtLatencyStatProfileMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The Latency Stat profile configured on NSX-T is different from this Network Insight deployment. As a result, Network Insight is not receiving Latency information from NSX-T. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80667} + +vmwHybridConnectBgpStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when BGP status is Down. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 1279} + +vmwNSXTClusterBackUpDisabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Manager backup is not scheduled. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80256} + +vmwNSXTDFWFirewallDisabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Distributed Firewall is disabled in the NSX-T Manager. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80257} + +vmwNSXTComputeManagerConnectionStatusNotUpEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Compute Manager Connection status is not up. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80255} + +vmwNSXTLogicalSwitchAdminStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Logical Switch Admin Status is 'Down'. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80252} + +vmwNSXTLogicalPortOperationalStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Logical Port Operational Status is 'Down'. This could cause a communication failure between two virtual interfaces (VIFs) that are connected to the same logical switch, for example, you cannot ping one VM from another. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80253} + +vmwNSXTLogicalPortOperationalStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Logical Port Operational Status is 'Unknown'. This could cause a communication failure between two virtual interfaces (VIFs) that are connected to the same logical switch, for example, you cannot ping one VM from another. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80254} + +vmwNSXTLogicalPortReceivedPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Received packets are getting dropped on the NSX-T Logical Port and associated entities might get affected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80258} + +vmwNSXTLogicalPortTransmittedPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Transmitted packets are getting dropped on the NSX-T Logical Port and associated entities might get affected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80259} + +vmwNSXTLogicalSwitchReceivedPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Received packets are getting dropped on the NSX-T Logical Switch and associated entities might get affected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80260} + +vmwNSXTLogicalSwitchTransmittedPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Transmitted packets are getting dropped on the NSX-T Logical Switch and associated entities might get affected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80261} + +vmwNSXTRxPacketDropOnMPNicEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Received packets are getting dropped on NSX-T Management Node's network interface. This may impact the network traffic related to NSX-T management cluster. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80262} + +vmwNSXTRxPacketDropOnEdgeTnNicEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Received packets are getting dropped on NSX-T Edge Node's network interface. This may impact the network traffic of edge cluster. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80263} + +vmwNSXTRxPacketDropOnHostTnNicEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Received packets are getting dropped on NSX-T Host Node's network interface. This may impact the network traffic on ESXi Host. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80264} + +vmwNSXTTxPacketDropOnMPNicEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Transmitted packets are getting dropped on NSX-T Management Node's network interface. This may impact the network traffic related to NSX-T management cluster. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80265} + +vmwNSXTTxPacketDropOnEdgeTnNicEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Transmitted packets are getting dropped on NSX-T Edge Node's network interface. This may impact the network traffic of edge cluster. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80266} + +vmwNSXTTxPacketDropOnHostTnNicEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Transmitted packets are getting dropped on NSX-T Host Node's network interface. This may impact the network traffic on ESXi Host. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80267} + +vmwNSXTMPNodeServiceClusterManagerStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Cluster Manager Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80424} + +vmwNSXTMPNodeServiceCmInventoryStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely CM Inventory Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80402} + +vmwNSXTMPNodeServiceControllerStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Controller Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80403} + +vmwNSXTMPNodeServiceDataStoreStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely DataStore Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80404} + +vmwNSXTMPNodeServiceHttpStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely HTTP Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80405} + +vmwNSXTMPNodeServiceInstallUpgradeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Install Upgrade Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80406} + +vmwNSXTMPNodeServiceLiagentStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely LI Agent Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80407} + +vmwNSXTMPNodeServiceManagerStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Manager Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80408} + +vmwNSXTMPNodeServiceMgmtPlaneBusStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Management Plane Bus Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80409} + +vmwNSXTMPNodeServiceMigrationCoordinatorStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Migration Co-ordinator Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80410} + +vmwNSXTMPNodeServiceNodeMgmtStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Node Management Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80411} + +vmwNSXTMPNodeServiceNodeStatsStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Node Statistics has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80412} + +vmwNSXTMPNodeServiceNSXMessageBusStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Message Bus Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80413} + +vmwNSXTMPNodeServiceNSXPlatformClientStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Platform Client Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80414} + +vmwNSXTMPNodeServiceNSXUpgradeAgentStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Upgrade Agent Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80415} + +vmwNSXTMPNodeServiceNTPStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely NTP Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80416} + +vmwNSXTMPNodeServicePolicyStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Policy Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80417} + +vmwNSXTMPNodeServiceSearchStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Search Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80418} + +vmwNSXTMPNodeServiceSNMPStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely SNMP Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80419} + +vmwNSXTMPNodeServiceSSHStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely SSH Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80420} + +vmwNSXTMPNodeServiceSyslogStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Syslog Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80421} + +vmwNSXTMPNodeServiceTelemetryStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely Telemetry Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80422} + +vmwNSXTMPNodeServiceUIServiceStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One of the Services of the NSX-T Management Node, namely UI Service has stopped running. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80423} + +vmwVMCHostPerClusterLimitExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when the number of Hosts per Cluster in a VMC SDDC exceeds limit. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100053} + +vmwVMCVMPerHostLimitExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when the number of VMs per Host in a VMC SDDC exceeds limits. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100054} + +vmwVMCClusterLimitExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when the number of Clusters in a VMC SDDC exceeds limits. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100055} + +vmwProtectionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This event is raised when any system protection limit is exceeded + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100061} + +vmwSwitchPortUptimeThresholdRecededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Up time of switch is less than expected. + Check the operational status of the specified switch port. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 30110} + +vmwFdbConfigStoreCleanupFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Foundation Database (FDB) Config Store Cleanup Failed Event. + Data Retention (Config Store Maintenance) service is not healthy. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80531} + +vmwDiskAllocationInsufficientEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Appliance Disk not configured according to Disk Guidance. + https://docs.vmware.com/en/VMware-vRealize-Network-Insight/5.1/com.vmware.vrni.using.doc/GUID-C96E9C78-6FA2-49EB-9791-8967A89B7698.html + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80528} + +vmwNSXTControllerNodeToControlClusterConnectivityEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T controller node has no control cluster connectivity. + Check if the node has proper network connectivity with control cluster. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80225} + +vmwNSXTControllerNodeToMgmtPlaneConnectivityEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T controller node has no management plane connectivity. + Check if the node has proper network connectivity with management plane. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80226} + +vmwNSXTMPNodeToMgmtClusterConnectivityEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T management node has no management cluster connectivity. + Check if the node has proper network connectivity with management cluster. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80227} + +vmwBigIpInsufficientShellAccessEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "No access to shell(ssh port 22) for F5 Load Balancer. Network Insight will not be able to fetch any information required for visibility. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80663} + +vmwBigIpInsufficientPartitionAccessEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Insufficient Partition Access for F5 Load Balancer. Network Insight will not be able to fetch any information required for visibility. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80664} + +vmwBigIpInsufficientRoleEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Insufficient Role for F5 Load Balancer. Network Insight will not be able to fetch any information required for visibility. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80665} + +vmwNSXTLatencyCollectorMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The collector configured on NSX-T is different from this Network Insight deployment. As a result, Network Insight is not receiving Latency information from NSX-T. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80662} + +vmwNSXTLatencyNoBFDProfileEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T, no BFD profile configured Event. + BFD profile was deleted on NSX-T Manager after 'Virtual infrastructure Latency' was enabled at Network Insight. As a result, Network Insight is not assigning BFD profile on Transport zone. Network Insight will not receive Latency information from new transport zones. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80661} + +vmwNSXTLatencyMoreBFDProfileEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T, more than one BFD profile configured Event. + There are multiple BFD profiles in the NSX-T Manager. As a result, Network Insight is not assigning correct BFD profile on Transport zone. Network Insight will not receive Latency information from new Transport zones. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80660} + +vmwNSXTLatencyNotEnabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T latency collection is not enabled. + Latency collection was disabled in the NSX-T Manager after it was enabled by Network Insight. As a result, Network Insight is not receiving latency information from the NSX-T. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80659} + +vmwHardwareVTEPMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Hardware Gateway Bindings Mismatch between NSX and switch. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80301} + +vmwHardwareVTEPPortDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Hardware Gateway Binding Switch Port is down. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80302} + +vmwNSXVLatencyNoDataEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Network Insight Collector VM is not receiving network latency metrics from host. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100001} + +vmwKubernetesBaseEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Event reported by kubernetes cluster. This is Kubernetes System Event. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 1510} + +vmwVMCVMLimitExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Number of VMs in VMC SDDC exceeds limit. + This event is raised when the number of VMs in a VMC SDDC exceeds limits. + Delete VMs that are not in use. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100051} + +vmwVMCHostLimitExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Number of Hosts in VMC SDDC exceeds limit. + This event is raised when the number of Hosts in a VMC SDDC exceeds limits. + Contact VMC Support to increase the host limit within the VMC SDDC. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100052} + +vmwVeloCloudEdgeDegradedTransQoeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Edge Transactional QOE has degraded. + Verify that the Edge is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90012} + +vmwVeloCloudEdgeDegradedVideoQoeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Edge Video QOE has Degraded. + Verify that the Edge is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90011} + +vmwVeloCloudEdgeDegradedVoiceQoeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Edge Voice QOE has Degraded. + Verify that the Edge is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90010} + +vmwVeloCloudEdgeDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Edge is not connected. + Verify that the VeloCloud Edge is UP. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90001} + +vmwVeloCloudLinkLostPacketEventRx NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Received Packet Loss observed on VeloCloud Link. + Verify that the Link is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90013} + +vmwVeloCloudLinkDegradedTransQoeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Link Transactional QOE has Degraded. + Verify that the Link is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90009} + +vmwVeloCloudLinkLostPacketEventTx NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Transmitted Packet Loss observed on VeloCloud Link. + Verify that the Link is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90005} + +vmwVeloCloudLinkDegradedVideoQoeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Link Video QOE has Degraded. + Verify that the Link is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90008} + +vmwVeloCloudLinkDegradedVoiceQoeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Link Voice QOE has Degraded. + Verify that the Link is in healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90007} + +vmwVeloCloudLinkDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VeloCloud Edge is not connected. + Verify that the VeloCloud Link is UP. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90002} + +vmwNSXTHostNodeMgmtConnectivityStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node has lost connectivity with NSX-T Manager node. + Please ensure all the interfaces connecting the NSX-T Transport Node to manager are up. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80246} + +vmwNSXTEdgeNodeCtlrConnectivityStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Node Controller connectivity is Unknown. + NSX-T Manager can't determine the status of the Edge Transport Node's connectivity with controller nodes + Please ensure all the interfaces connecting the NSX-T Transport Node to manager are up. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80247} + +vmwNSXTHostNodeCtlrConnectivityStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Node is not able to communicate with any of the controllers. + NSX-T Host Transport Node has lost connectivity with all the controller nodes + Please ensure all the interfaces connecting the NSX-T Transport Node to controller nodes are up. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80248} + +vmwNSXTHostNodeCtlrConnectivityStatusDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Node is not able to to communicate with one or more controllers. + NSX-T Host Transport Node has lost connectivity with some (but not all) of the controller nodes + Please ensure all the interfaces connecting the NSX-T Transport Node to controller nodes are up. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80249} + +vmwNSXTHostNodeCtlrConnectivityStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Node Controller connectivity is Unknown. + NSX-T Manager can't determine the status of the Host Transport Node's connectivity with controller nodes + Please ensure all the interfaces connecting the NSX-T Transport Node to controller nodes are up. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80250} + +vmwNSXTHostNodePnicStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Pnic Status is 'Down'. + All the pNICs of the NSX-T Host transport Node are down. + Please check if all the pNICs are properly connected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80228} + +vmwNSXTHostNodePnicStatusDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Pnic Status is 'Degraded' + Some of the pNICs of the NSX-T Host transport Node are down. + Please check if all the pNICs are properly connected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80229} + +vmwNSXTHostNodePnicStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Pnic Status is 'Unknown'. + NSX-T Manager can't determine the status of some or all of the pNICs of the NSX-T Host Transport Node + Please check if all the pNICs are properly connected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80230} + +vmwNSXTEdgeNodePnicStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Pnic Status is 'Down'. + All the pNICs of the NSX-T Edge transport Node are down. + Please check if all the pNICs are properly connected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80237} + +vmwNSXTEdgeNodePnicStatusDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Pnic Status is 'Degraded'. + Some of the pNICs of the NSX-T Edge transport Node are down. + Please check if all the pNICs are properly connected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80238} + +vmwNSXTEdgeNodePnicStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Pnic Status is 'Unknown'. + NSX-T Manager can't determine the status of some or all of the pNICs of the NSX-T Edge Transport Node + Please check if all the pNICs are properly connected. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80239} + +vmwNSXTHostNodeTunnelStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Tunnel Status is 'Down'. + All the tunnel interfaces associated to the NSX-T Host transport Node are down. + Please check the status of the tunnel interfaces for this NSX-T Transport Node + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80231} + +vmwNSXTHostNodeTunnelStatusDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Tunnel Status is 'Degraded'. + Some of the tunnel interfaces associated to the NSX-T Host transport Node are down. + Please check the status of the tunnel interfaces for this NSX-T Transport Node + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80232} + +vmwNSXTHostNodeTunnelStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Tunnel Status is 'Unknown'. + NSX-T Manager can't determine the status of some or all of the tunnel interfaces associated to the NSX-T Host Transport Node. + Please check the status of the tunnel interfaces for this NSX-T Transport Node + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80233} + +vmwNSXTEdgeNodeTunnelStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Tunnel Status is 'Down'. + All the tunnel interfaces associated to the NSX-T Edge transport Node are down. + Please check the status of the tunnel interfaces for this NSX-T Transport Node + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80240} + +vmwNSXTEdgeNodeTunnelStatusDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Tunnel Status is 'Degraded'. + Some of the tunnel interfaces associated to the NSX-T Edge transport Node are down. + Please check the status of the tunnel interfaces for this NSX-T Transport Node + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80241} + +vmwNSXTEdgeNodeTunnelStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Tunnel Status is 'Unknown'. + NSX-T Manager can't determine the status of some or all of the tunnel interfaces associated to the NSX-T Edge Transport Node + Please check the status of the tunnel interfaces for this NSX-T Transport Node + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80242} + +vmwNSXTHostNodeStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Roll-up Status is 'Down'. + Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Host Transport Node are down. + Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80234} + +vmwNSXTHostNodeStatusDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Roll-up Status is 'Degraded'. + Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Host Transport Node are in degraded state. + Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80235} + +vmwNSXTHostNodeStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Transport Node Roll-up Status is 'Unknown'. + NSX-T Manager can't determine the status of some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Host Transport Node. + Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80236} + +vmwNSXTEdgeNodeStatusDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Roll-up Status is 'Down'. + Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Edge Transport Node are down. + Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80243} + +vmwNSXTEdgeNodeStatusDegradedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Roll-up Status is 'Degraded'. + Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Edge Transport Node are in degraded state. + Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80244} + +vmwNSXTEdgeNodeStatusUnknownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Transport Node Roll-up Status is 'Unknown'. + NSX-T Manager can't determine the status of some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Edge Transport Node. + Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80245} + +vmwNsxiApplianceAvailableEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Intelligence Appliance is deployed within NSX-T. NSX-I data collection on the NSX-T Data source can now be enabled. + Please visit to vRNI -> Settings -> Data Sources -> NSX-T data souces to enable this data collection. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 974} + +vmwNsxiSubscriptionCreateFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Enabling data collection from NSX Intelligence was failed. + Please check the NSX-Intelligence appliance and ensure it is reachable and in a healthy state. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 975} + +vmwNsxiSubscriptionDeleteFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Cleanup of NSX Intelligence appliance failed. + Please check the NSX-Intelligence appliance and ensure it is reachable and in a healthy state + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 976} + +vmwNsxiSubscriptionUpdateFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Failed to initiate data collection from NSX Intelligence. + Please check the NSX-Intelligence appliance and ensure it is reachable and in a healthy state + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 977} + +vmwNsxiSslHandshakeFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX Intelligence SSL Handshake Failed. + Please check the SSL certificates configured on NSX Intelligence Appliance. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 978} + +vmwAnalyticsThresholdCompositeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Alert generated as a result of the specified combination of metric crosses the upper or lower bound specified in the configuration. + Please check details and remediation steps mentioned in alert. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 37004} + +vmwAnalyticsThresholdCompositeProblemEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Alert generated as a result of the specified combination of metric crosses the upper or lower bound specified in the configuration. + Please check details and remediation steps mentioned in alert. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 37006} + +vmwLicenseExpiredEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "License of this appliance has expired. Please apply a valid license to continue the data collection. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80537} + +vmwInGracePeriodEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Applicance license is in Grace Period. Add valid licenses before grace period ends to continue the data collection. + This event will remain open till it is fixed. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80538} + +vmwFailedDatasourceOperationEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Data Source Update Operation Failed. Details of the data source and failed operation are mentioned in the event vmwOperatorDesc field. + Please check correctness of input data while performing update operations to a data source. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80672} + +vmwNsxtNotificationWebhookDisabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The webhook configured to receive push notifications from NSX-T is no longer present in the data source. As a result, notifications received by Network Insight might be delayed. + Please log into NSX-T and enable notifications for vRNI. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80670} + +vmwNatRuleLargeSubnetEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "IP address mentioned in the NAT Rules have a subnet of size greater than 16. Flows will be impacted due to large subnet size. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80270} + +vmwNSXTHostNodeMaintenanceModeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Host Node is in Maintenance Mode. + For uninterrupted operations, please disable Maintenance Mode on this Host Node if maintenance activity is completed. + This event will be closed once host is host is out of maintenance mode. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80272} + +vmwNSXTEdgeNodeMaintenanceModeEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Edge Node is in Maintenance Mode. + For uninterrupted operations, please disable Maintenance Mode on this edge node if maintenance activity is completed. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 80271} + +vmwSDWanLinkTrafficThresholdEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "SD-WAN Link Traffic exceeded the threshold limit configured. Link details are available in event description vmwOperatorDesc field. + Please check the Traffic Utilization section on VeloCloud Edge to get the visibility of Applications and clients for the Link. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 90017} + +vmwVMCCapacityThresholdBreachEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is raised for VMC on AWS when thresholds of an entity e.g Firewall Rule exceeds. + Please log in to VMC, navigate to listings page of entity type mentioned in the event description vmwOperatorDesc field. + Then delete any unused entities to ensure uninterrupted operations. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 100056} + +vmwNativeVlanMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Native VLAN ID configuration of the ports on each link should match. + Please check mismatch mentioned in the event vmwAffectedObject field and correct the configuration. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 110011} + +vmwNativeVlanTaggingMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Native VLAN tagging of the ports on each link should match. + Please check mismatch mentioned in the event and correct the configuration. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 110012} + +vmwSnapshotNotBuildingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Unable to load latest network map. The last successful network map snapshot was taken over 6 hours ago. + Network map functionality may show obsolete state. If this event persists, please contact VMware support. + For more details about this event, please log into vRNI, navigate to Settings -> Events" + ::= { vmwVRNIEvents 110013} + +vmwProtectionActiveEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "VMware vRealize Network Insight is experiencing high-system usage. Safe mode has been turned on automatically to keep the system protected and responsive. + Please contact VMware support to fix the problem. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 110015} + +vmwUnableToSendSNMPTrapsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "vRNI appliance failed to send SNMP Trap. This could be due to temporary network disruption. + If problem persists, please check if SNMP Trap destination is reachable from vRNI appliance. + Please note that this trap is only sent if sendto() or getaddrinfo() fails from vRNI appliance. + To send a test trap, log into vRNI -> Settings -> Alerts and Definition -> SNMP Trap Destinations page and click 'Send Test Trap'. + Also note that ther + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80539} + +vmwStreamProcessingFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Realtime stream processing has failed in vRNI appliance. + Please contact VMware support immediately to resolve the issue. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80540} + +vmwSNOWMandatoryPrivilegesMissingEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Required privileges are missing for the user in ServiceNow. + Please make sure that the user used in vRNI while adding SNOW account has been necessary privileges in SNOW UI. + To check user details, please visit vRNI -> Setting -> Data Sources page. + To check required user permissions, please visit https://docs.vmware.com/en/VMware-vRealize-Network-Insight/6.4/com.vmware.vrni.using.doc/GUID-772EC526-DD22-4B3C-87A5-F55CA90ED5AE.html. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80604} + +vmwVMCSDDCTGWConnectivityFailedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is raised when SDDC within SDDC Group loses connectivity with VTGW(VMware Transit Gateway). + Please contact VMC on AWS Support. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 38003} + +vmwNSXTEdgeDVPGsIPFIXDisabledEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "As a protection mechanism, the flow collection for DVPGs, having NSX-T Edges connected, is disabled. + Please enable DFW IPFIX on NSX-T, if not enabled already. Do not enable IPFIX on DVPGs having NSX-T Edge VMs connected. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80273} + +vmwUnsupportedNsxAlbVersionEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is triggered while adding the NSX ALB data source and if the version of NSX ALB is < 20.1.3. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80700} + +vmwIpfixFlowLagEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is raised to notify users when there are excessive incoming flow records than what can be processed within the stipulated time window, the ipfix processor lags behind. Once the incoming flow records are back within the limits, the alert gets cleared. The time window for each source is defined in ipfix.configuration. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80541} + +vmwNSXALBSystemEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "These are the alarms/events reported by NSXALB platform. + You can see these alerts in NSX ALB platform under Operations -> All alerts. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 3558} + +vmwTkgiKubernetesNotReachableEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is triggered if the Kubernetes Clusters which are managed by TKGI are not reachable from collector. + Please verify the Kubernetes Cluster Master hosts are reachable from Collector VM. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80800} + +vmwTkgiClustersInsufficientPriviledgesEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is triggered if the Kubernetes Clusters which are managed by TKGI doesn't sufficient privileges for fetching the k8s entities. + It must have List and Watch privileges. + For more details about this event, please log into vRNI, navigate to Settings -> Events -> Alert Definitions page" + ::= { vmwVRNIEvents 80801} + +vmwNSXTRouterInterfaceRPFPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is generated when the RPF packet drop ratio exceeds the threshold value of 1%. Check RPF packet drop on the interface." + ::= { vmwVRNIEvents 80274} + +vmwChangeEventsDroppedEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Realtime processing has stopped due to high system load. Some updates may be delayed. It is a temporary condition. The system should recover and clear the error by itself. If this message persists for more than 12 hours, please contact VMware customer support." + ::= { vmwVRNIEvents 80542} + +vmwHcxIXServiceStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HCX Interconnect Service is not Up. Please verify HCX IX Service is in healthy state." + ::= { vmwVRNIEvents 90501} + +vmwHcxNEServiceStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HCX Network Extension Service is not Up. Please verify HCX NE Service is in healthy state." + ::= { vmwVRNIEvents 90503} + +vmwHcxBMServiceStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HCX Bulk Migration Service is not Up. Please verify HCX Bulk Migration Service is in healthy state." + ::= { vmwVRNIEvents 90512} + +vmwHcxVMotionServiceStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HCX vMotion Service is not Up. Please verify HCX VMotion Service is in healthy state." + ::= { vmwVRNIEvents 90513} + +vmwHcxIXApplianceEncryptionTunnelStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Hybrid Interconnect Service Encryption Tunnel Status is not Up. Please verify HCX IX Appliance Encryption Tunnel is in healthy state." + ::= { vmwVRNIEvents 90502} + +vmwHcxNEApplianceEncryptionTunnelStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HCX Network Extension Service Encryption Tunnel Status is not Up. Please verify HCX NE Appliance Encryption Tunnel is in healthy state." + ::= { vmwVRNIEvents 90504} + +vmwHcxIXApplianceServicePipelineStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Hybrid Interconnect Service Pipeline Status is not Up. Please verify Hybrid Interconnect Service Pipeline is in healthy state." + ::= { vmwVRNIEvents 90505} + +vmwHcxNEApplianceServicePipelineStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HCX Network Extension Service Pipeline Status is not Up. Please verify HCX Network Extension Service Pipeline is in healthy state." + ::= { vmwVRNIEvents 90506} + +vmwHcxIXApplianceServiceTransportStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Hybrid Interconnect Service Transport Status is not Up. Please verify Hybrid Interconnect Service Transport is in healthy state." + ::= { vmwVRNIEvents 90507} + +vmwHcxNEApplianceServiceTransportStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Network Extension Service Transport Status is not Up. Please verify Network Extension Service Transport is in healthy state." + ::= { vmwVRNIEvents 90508} + +vmwHcxIXApplianceServiceSystemStateEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Hybrid Interconnect Service System State is not Up. Please verify Hybrid Interconnect Service System is in healthy state." + ::= { vmwVRNIEvents 90509} + +vmwHcxNEApplianceServiceSystemStateEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Network Extension Service System State is not Up. Please verify Network Extension Service System is in healthy state." + ::= { vmwVRNIEvents 90510} + +vmwHcxIXServiceNotRunningEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Hybrid Interconnect Service is not running. Please verify Hybrid Interconnect Service is in healthy state." + ::= { vmwVRNIEvents 90514} + +vmwHcxNEServiceNotRunningEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Network Extension Service is not running. Please verify Network Extension Service is in healthy state." + ::= { vmwVRNIEvents 90515} + +vmwHcxWanOptServiceNotRunningEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "WAN Optimisation Service is not running. Please verify WAN Optimisation Service Service is in healthy state." + ::= { vmwVRNIEvents 90516} + +vmwPanLogInsightDroppedFlowEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Dropped flows are detected on Palo Alto device through VMware vRealize Log Insight. " + ::= { vmwVRNIEvents 80050} + +vmwHcxConnectionRuleViolationEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "HCX Connection Rule is violated for the Firewall Rules. Please verify HCX Applinace Tunnel for the violated firewall rules." + ::= { vmwVRNIEvents 90518} + +vmwHcxApplianceAllTunnelDownEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "No tunnels are in working state on HCX Appliance. Please verify the tunnels are working for the HCX Appliance." + ::= { vmwVRNIEvents 90517} + +vmwHcxMtuMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "MTU doesn't match for uplink network profiles in the HCX Service Mesh. Please correct the MTU values for the uplink network profiles." + ::= { vmwVRNIEvents 90519} + +vmwSwitchPortRPFPacketDropEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "uRPF packet drop ratio is high for switch port. Please check uRPF packet drop on the interface." + ::= { vmwVRNIEvents 30124} + +vmwCPLogInsightDroppedFlowEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Dropped flows are detected on Check Point device through VMware vRealize Log Insight." + ::= { vmwVRNIEvents 80051} + +vmwSNMPTrapEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "This alert is raised when incoming SNMP Trap is received by Network Insight." + ::= { vmwVRNIEvents 110017} + + +vmwServiceRestartCountExceededEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "One or more services restarted multiple times. Please verify the system is in a healthy state." + ::= { vmwVRNIEvents 80544} + +vmwHcxWanOptServiceStatusEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "WAN Optimisation Service is not Up. Please verify HCX WAN Optimisation Service is in healthy state." + ::= { vmwVRNIEvents 90511} + +vmwNsxtIpfixMultipleCollectorConfigurationEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "NSX-T Multiple DFW IPFIX Collectors Configured. Please remove the stale collector IPs from NSX Policy DFW IPFIX collector profile. To automatically remove stale collector IPs from NSX Policy IPFIX collector profile, please uncheck the IPFIX checkbox on the Data Source edit page and check again after 30 minutes." + ::= { vmwVRNIEvents 80275} + +vmwHcxApplianceUnhealthyTunnelsEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "Few tunnels on HCX Appliance are unhealthy. Please verify the tunnels are working for the HCX Appliance." + ::= { vmwVRNIEvents 90520} + +vmwHcxManagerVersionMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The paired HCX Managers are running different software versions. Please upgrade the appropriate HCX Manager so that the paired HCX Managers are running similar version of software." + ::= { vmwVRNIEvents 90521} + +vmwHcxApplianceVersionMismatchEvent NOTIFICATION-TYPE + OBJECTS { vmwEventSeverity, vmwAffectedObject, vmwOperatorDesc, vmwVrniUrl, vmwTimestamp, vmwEventName } + STATUS current + DESCRIPTION + "The paired HCX Appliances are running different software versions. Please upgrade the appropriate HCX Appliance so that the paired HCX Appliances are running similar version of software." + ::= { vmwVRNIEvents 90522} + +-- ********************************************************** +-- Notification parameters +-- ********************************************************** + +vmwAffectedObject OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Object affected by this event" + ::= { vmwVRNIData 102} + + +vmwEventSeverity OBJECT-TYPE + SYNTAX VmwVrniSeverity + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "vRNI Event Severity" + ::= { vmwVRNIData 103} + +vmwVrniUrl OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "URL to vRNI for this exact event" + ::= { vmwVRNIData 104} + + +vmwTimestamp OBJECT-TYPE + SYNTAX DateAndTime + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Time of first detection of event" + ::= { vmwVRNIData 105} + +vmwOperatorDesc OBJECT-TYPE + SYNTAX VmwLongSnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Human readable message of the event" + ::= { vmwVRNIData 106} + +vmwEventName OBJECT-TYPE + SYNTAX VmwLongSnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Event name" + ::= { vmwVRNIData 107} + + +-- conformance information +vmwNetworkInsightMIBConformance OBJECT IDENTIFIER ::= { vmwNetworkInsightMIB 99 } +vmwNetworkInsightMIBCompliances OBJECT IDENTIFIER ::= + { vmwNetworkInsightMIBConformance 1 } +vmwNetworkInsightMIBGroups OBJECT IDENTIFIER ::= { vmwNetworkInsightMIBConformance 2 } + +-- compliance statements +vmwNetworkInsightMIBBasicCompliance MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-NSX-MANAGER-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup1, + vmwNetworkInsightNotificationGroup1 } + ::= { vmwNetworkInsightMIBCompliances 3 } + +vmwNetworkInsightNotificationInfoGroup1 OBJECT-GROUP + OBJECTS { + vmwAffectedObject, + vmwEventSeverity, + vmwVrniUrl, + vmwTimestamp, + vmwOperatorDesc, + vmwEventName + } + STATUS current + DESCRIPTION + "These objects provide details in NSX Manager notifications." + ::= { vmwNetworkInsightMIBGroups 2 } + +vmwNetworkInsightNotificationGroup1 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwSnmpTrapsAreConfigured, + vmwSnmpTrapsAreDisabled, + vmwTestTrap, + vmwEntityDiscoveryChangeEvent, + vmwEntityPropertiesChangeEvent, + vmwFirewallNotInstalledOnHostEvent, + vmwHostWithStaleFirewallRulesEvent, + vmwIpAddressChangeEvent, + vmwL2GatewayAnomalyEvent, + vmwL2NetworkAddressAnomalyEvent, + vmwL2NetworkDiameterExceededEvent, + vmwL2NetworkUplinkMissingEvent, + vmwL2NetworkWithNoVMsEvent, + vmwLayer2NetworkDiameterChangedEvent, + vmwMTUMismatchEvent, + vmwNetworkIsolationEvent, + vmwNoPathEvent, + vmwSpoofguardDisabledEvent, + vmwVMotionEvent, + vmwVMWithDisconnectedVnicsEvent, + vmwVMWithMulipleVnicsOnDifferentVxlansEvent, + vmwVMWithMulipleVnicsOnSameL2Event, + vmwVMWithNoIpAddressEvent, + vmwVTEPMissingEvent, + vmwL2Event, + vmwMembershipChangeEvent, + vmwSecurityGroupMembershipChangeEvent, + vmwFirewallRuleMembershipChangeEvent, + vmwVlanMembershipChangeEvent, + vmwVxlanMembershipChangeEvent, + vmwDeleteChangeEvent, + vmwVtepFailedPingEvent, + vmwEmptySearchStreamChangeEvent, + vmwSearchStreamMembershipChangeEvent, + vmwEmptySearchStreamProblemEvent, + vmwSearchStreamMembershipProblemEvent, + vmwOspfConfigurationMismatchEvent, + vmwServiceVMNotHealthyEvent, + vmwServiceVMNotPoweredOnEvent, + vmwServiceVMHighCPUUsageEvent, + vmwServiceVMHighMemoryUsageEvent, + vmwServiceVMHighDiskUsageEvent, + vmwIPSetPropertiesChangeEvent, + vmwFirewallRulePropertiesChangeEvent, + vmwSecurityGroupPropertiesChangeEvent, + vmwIPSetMembershipChangeEvent, + vmwFirewallRuleMaskEvent, + vmwSecurityMembershipChangeEvent, + vmwSecurityTagPropertiesChangeEvent, + vmwSecurityTagMembershipChangeEvent, + vmwHostDatastoreChangeEvent, + vmwVMDatastoreChangeEvent, + vmwVMSnapshotChangeEvent, + vmwVMVirtualDiskChangeEvent, + vmwIPSetDefinitionMismatchEvent, + vmwSegmentMismatchEvent, + vmwVtepEvent, + vmwVtepConfigurationFaultEvent, + vmwVtepSubnetMismatchEvent, + vmwVtepCountMismatchEvent, + vmwDLRNetworksNotReachableEvent, + vmwEdgeNetworksNotReachableEvent, + vmwThresholdExceededEventCpuReady, + vmwThresholdExceededEventCpuCoStop, + vmwThresholdExceededEventDiskCommandAbortRule, + vmwThresholdExceededEventIODeviceLatencyRule, + vmwThresholdExceededEventIOKernelLatencyRule, + vmwThresholdExceededEventMemorySwapInRule, + vmwThresholdExceededEventMemorySwapOutRule, + vmwThresholdExceededEventNetworkRxDropRule, + vmwThresholdExceededEventNetworkTxDropRule, + vmwPacketDropEvent, + vmwSwitchPortPacketDropEvent, + vmwRouterInterfacePacketDropEvent, + vmwVnicPacketDropEvent, + vmwVTEPUnderlayPacketDropEvent, + vmwPnicUnderlyingSwitchPortPacketDropEvent, + vmwDevicePacketDropEvent, + vmwThresholdExceededEventDatastoreFreeSpaceWarning, + vmwThresholdExceededEventDatastoreFreeSpaceCritical, + vmwThresholdExceededEventDatastoreReadLatency, + vmwThresholdExceededEventDatastoreWriteLatency, + vmwDistributedFirewallApplyHostEvent, + vmwDistributedFirewallApplyVMEvent, + vmwNsxEvent, + vmwFeatureImpactedEvent, + vmwClusterFeatureVersionMismatchEvent, + vmwHostFeatureVersionMismatchEvent, + vmwFeatureVersionMismatchEvent, + vmwHostFeatureEnabledMismatchEvent, + vmwHostFeatureInstalledMismatchEvent, + vmwHostVtepNotFoundEvent, + vmwHostVtepDisconnectedEvent, + vmwHostVtepEvent, + vmwClusterHostsVtepMTUMismatchEvent, + vmwFeatureUnhealthyEvent, + vmwEdgeHANotConfiguredEvent, + vmwEdgeInterfacesDownEvent, + vmwModuleUnhealthyEvent, + vmwModuleNotLoadedEvent, + vmwModuleNetworkConnectionFailureEvent, + vmwHostNetworkControlPlaneMismatchEvent, + vmwHostNetworkControlPlaneConnectionFailureEvent, + vmwHostNetworkControlPlaneNotSyncedEvent, + vmwNSXControllerClusterMajorityEvent, + vmwNSXControllersVMOnSameHostEvent, + vmwVxLanRangeExhaustEvent, + vmwNSXFirewallDefaultAllowAllRulesEvent, + vmwEdgeNotHAEvent, + vmwEdgeNotDeployedEvent, + vmwEcmpIsEnabledAndStatefulServicesAreUpEvent, + vmwLogicalRouterDeployedOnEcmpEdgeHostEvent, + vmwEdgeMissingInterfaceOSPFAreaMappingEvent, + vmwOspfInsecureAuthRouterEvent, + vmwNSXControllersDeployedCountEvent, + vmwNSXControllerNotActiveCountEvent, + vmwNSXControllerEvent, + vmwNSXBackupEvent, + vmwNSXUnsecureBackupEvent, + vmwNSXBackupSystemEventsExcludedEvent, + vmwNSXBackupNotScheduledEvent, + vmwNSXBackupNotRecordedEvent, + vmwNSXNtpServerEvent, + vmwNSXSysLogServerEvent, + vmwControllerSysLogServerEvent, + vmwGenericNSXSystemEvent, + vmwOtherCriticalNSXEvent, + vmwFilterConfigApplyOnHostFailedEvent, + vmwRulesetLoadOnHostFailedEvent, + vmwConfigUpdateOnHostFailedEvent, + vmwSpoofguardConfigUpdateOnHostFailedEvent, + vmwApplyRuleToVnicFailedEvent, + vmwContainerConfigUpdateOnVnicFailedEvent, + vmwSpoofguardApplyToVnicFailedEvent, + vmwHostMessagingConfigurationFailedEvent, + vmwHostMessagingConnectionReconfigurationFailedEvent, + vmwHostMessagingConfigurationFailedNotificationSkippedEvent, + vmwHostMessagingInfrastructureDownEvent, + vmwEdgeVMNotRespondingEvent, + vmwEdgeUnhealthyEvent, + vmwEdgeVMCommunicationFailureEvent, + vmwNSXEdgeEvent, + vmwPanEvent, + vmwPanNsxNotInRegisteredStateEvent, + vmwPanNsxDynamicUpdateDelayedEvent, + vmwPanDeviceInDisconnectedStateEvent, + vmwPanNsxServiceApplianceViewMismatchEvent, + vmwPanNsxFabricAgentNotFoundOnHostEvent, + vmwPanNsxServiceVMNotFoundOnHostEvent +} + STATUS current + DESCRIPTION + "Set of notifications (traps, informs) supported in this version." + ::= { vmwNetworkInsightMIBGroups 3 } + +vmwNetworkInsightMIBBasicCompliance2 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB second version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup2, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2 + } + ::= { vmwNetworkInsightMIBCompliances 30 } + +vmwNetworkInsightNotificationInfoGroup2 OBJECT-GROUP + OBJECTS { + vmwAffectedObject, + vmwEventSeverity, + vmwVrniUrl, + vmwTimestamp, + vmwOperatorDesc, + vmwEventName + } + STATUS deprecated + DESCRIPTION + "These events provide details in NSX Manager notifications." + ::= { vmwNetworkInsightMIBGroups 20 } + +vmwNetworkInsightNotificationGroup2 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwLogicalRouterNoUplinkEvent, + vmwNSXComponentEvent, + vmwNSXBackupEvent, + vmwNSXBackupAuditLogExcludedEvent, + vmwNSXUnsecureBackupEvent, + vmwNSXBackupSystemEventsExcludedEvent, + vmwNSXBackupNotScheduledEvent, + vmwNSXBackupNotRecordedEvent, + vmwNSXNtpServerEvent, + vmwNSXSysLogServerEvent, + vmwControllerSysLogServerEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) since last revision." + ::= { vmwNetworkInsightMIBGroups 30 } + +vmwNetworkInsightMIBBasicCompliance3 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB second version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup2, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3 + } + ::= { vmwNetworkInsightMIBCompliances 35 } + +vmwNetworkInsightNotificationGroup3 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwMTUMismatchEvent, + vmwVMWithMulipleVnicsOnSameL2Event, + vmwMembershipChangeEvent, + vmwSecurityGroupMembershipChangeEvent, + vmwFirewallRuleMembershipChangeEvent, + vmwVlanMembershipChangeEvent, + vmwVxlanMembershipChangeEvent, + vmwSearchStreamMembershipChangeEvent, + vmwIPSetMembershipChangeEvent, + vmwSecurityMembershipChangeEvent, + vmwVtepEvent, + vmwPacketDropEvent, + vmwSwitchPortPacketDropEvent, + vmwRouterInterfacePacketDropEvent, + vmwVnicPacketDropEvent, + vmwVTEPUnderlayPacketDropEvent, + vmwPnicUnderlyingSwitchPortPacketDropEvent, + vmwHostFeatureVersionMismatchEvent, + vmwSpoofguardConfigUpdateOnHostFailedEvent, + vmwNSXEcmpEdgeDownEvent, + vmwNSXMajorityEcmpEdgesDownEvent, + vmwNSXAllEcmpEdgesDownEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) since last revision." + ::= { vmwNetworkInsightMIBGroups 40 } + +vmwNetworkInsightMIBBasicCompliance4 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB second version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup2, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4 + } + ::= { vmwNetworkInsightMIBCompliances 45 } + +vmwNetworkInsightNotificationGroup4 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNSXEdgeSplitBrainEvent, + vmwNSXIpV6EnabledEvent, + vmwNSXOspfNeighborDownEvent, + vmwCheckpointEvent, + vmwNSXEdgeMtuMismatchEvent, + vmwCheckpointNsxFabricAgentNotFoundOnHostEvent, + vmwCheckpointNsxServiceVMNotFoundOnHostEvent, + vmwCheckpointGatewaySicStatusNotCommunicatingEvent, + vmwCheckpointNsxServiceApplianceViewMismatchEvent, + vmwCriticalHostNotAccessibleEvent, + vmwVlanMembershipChangeEvent, + vmwClusterFeatureVersionMismatchEvent, + vmwHostFeatureVersionMismatchEvent, + vmwConfigUpdateOnHostFailedEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) since last revision." + ::= { vmwNetworkInsightMIBGroups 50 } + +vmwNetworkInsightNotificationInfoGroup3 OBJECT-GROUP + OBJECTS { + vmwEventSeverity, + vmwAffectedObject, + vmwOperatorDesc, + vmwVrniUrl, + vmwTimestamp, + vmwEventName + } + STATUS current + DESCRIPTION + "These objects provide details in VRNI notifications." + ::= { vmwNetworkInsightMIBGroups 55 } + +vmwNetworkInsightMIBBasicCompliance5 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5 + } + ::= { vmwNetworkInsightMIBCompliances 60 } + +vmwNetworkInsightMIBBasicCompliance6 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6 + } + ::= { vmwNetworkInsightMIBCompliances 70 } + +vmwNetworkInsightMIBBasicCompliance7 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7 + } + ::= { vmwNetworkInsightMIBCompliances 80 } + +vmwNetworkInsightMIBBasicCompliance8 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8 + } + ::= { vmwNetworkInsightMIBCompliances 90 } + +vmwNetworkInsightMIBBasicCompliance9 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9 + } + ::= { vmwNetworkInsightMIBCompliances 100 } + +vmwNetworkInsightMIBBasicCompliance10 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10 + } + ::= { vmwNetworkInsightMIBCompliances 110 } + +vmwNetworkInsightMIBBasicCompliance11 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11 + } + ::= { vmwNetworkInsightMIBCompliances 120 } + +vmwNetworkInsightMIBBasicCompliance12 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12 + } + ::= { vmwNetworkInsightMIBCompliances 130 } + +vmwNetworkInsightMIBBasicCompliance13 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12, + vmwNetworkInsightNotificationGroup13 + } + ::= { vmwNetworkInsightMIBCompliances 140 } + +vmwNetworkInsightMIBBasicCompliance14 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12, + vmwNetworkInsightNotificationGroup13, + vmwNetworkInsightNotificationGroup14 + } + ::= { vmwNetworkInsightMIBCompliances 150 } + +vmwNetworkInsightMIBBasicCompliance15 MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + VMWARE-VRNI-MIB latest version." + MODULE -- this module + MANDATORY-GROUPS { vmwNetworkInsightNotificationInfoGroup3, + vmwNetworkInsightNotificationGroup1, + vmwNetworkInsightNotificationGroup2, + vmwNetworkInsightNotificationGroup3, + vmwNetworkInsightNotificationGroup4, + vmwNetworkInsightNotificationGroup5, + vmwNetworkInsightNotificationGroup6, + vmwNetworkInsightNotificationGroup7, + vmwNetworkInsightNotificationGroup8, + vmwNetworkInsightNotificationGroup9, + vmwNetworkInsightNotificationGroup10, + vmwNetworkInsightNotificationGroup11, + vmwNetworkInsightNotificationGroup12, + vmwNetworkInsightNotificationGroup13, + vmwNetworkInsightNotificationGroup14, + vmwNetworkInsightNotificationGroup15 + } + ::= { vmwNetworkInsightMIBCompliances 160 } + +vmwNetworkInsightNotificationGroup5 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNiInfraChangeEvent, + vmwDataSourceEnabledChangeEvent, + vmwDataSourceDisabledChangeEvent, + vmwDataSourceCreatedEvent, + vmwPlatformCpuCoreChangeEvent, + vmwPlatformDiskChangeEvent, + vmwPlatformMemoryChangeEvent, + vmwPlatformRebootedEvent, + vmwProxyCpuCoreChangeEvent, + vmwProxyDiskChangeEvent, + vmwProxyMemoryChangeEvent, + vmwProxyRebootedEvent, + vmwNIClusterChangeEvent, + vmwNISystemProxyChangeEvent, + vmwNIClusterCreateEvent, + vmwAWSRegionSGLimitEvent, + vmwAWSVPCSGLimitEvent, + vmwAWSSGInboundRuleLimitEvent, + vmwAWSSGOutboundRuleLimitEvent, + vmwAWSInterfaceSGLimitEvent, + vmwVirtualDistributedRoutingEvent, + vmwIndexerLagEvent, + vmwIPFIXFlowDPPausedEvent, + vmwGridProcessingStoppedEvent, + vmwUnableToSendEmailsEvent, + vmwSMTPNotConfiguredEvent, + vmwSNMPNotConfiguredEvent, + vmwReindexingInProgressEvent, + vmwNodesVersionMismatchEvent, + vmwNotAllServicesRunningEvent, + vmwNotAllServicesHealthyEvent, + vmwExpandPartitionFailedEvent, + vmwDiskCleanupFailedEvent, + vmwVaccumFailedEvent, + vmwConfigStoreCleanupFailedEvent, + vmwHBaseRetentionToolFailedEvent, + vmwMetricStoreUpdaterFailedEvent, + vmwCollectorLagEvent, + vmwCollectionLagEvent, + vmwGridProcessingLagEvent, + vmwConnectionErrorEvent, + vmwNodeNotActiveEvent, + vmwHighDiskUtilizationEvent, + vmwIndexingAbortedEvent, + vmwUpgradeFailedEvent, + vmwFlowProcessingSuspendedEvent, + vmwVCNotOnSameProxyEvent, + vmwNoDVSAvailableEvent, + vmwUnknownInfobloxVersionEvent, + vmwUnsupportedInfobloxVersionEvent, + vmwIncorrectInfobloxCredentialEvent, + vmwInfobloxRecordLimitExceededEvent, + vmwWebhookNotRunningEvent, + vmwIncorrectWebhookConfiguredOnAlertEvent, + vmwWebhookNotEnabledOnAlertEvent, + vmwVRNIContentPackNotInstalledEvent, + vmwUnsupportedVRNIContentPackVersionEvent, + vmwUnsupportedLogInsightVersionEvent, + vmwComputeManagersNotAddedEvent, + vmwComputeManagersNotFoundEvent, + vmwUnsupportedNSXTVersionEvent, + vmwNotEmptyNodeEvent, + vmwFlowPhysicalNodeEvent, + vmwFlowCollectionErrorEvent, + vmwAWSThrottlingExceptionEvent, + vmwAWSFlowLogAccessDeniedExceptionEvent, + vmwNSXIPFIXStatusMismatchEvent, + vmwNumVMsOrHostsNotFoundEvent, + vmwUnsupportedNSXVersionEvent, + vmwPwdAuthModeDisabledAristaEvent, + vmwHostnameResolutionErrorEvent, + vmwPrimaryNSXNotAddedEvent, + vmwDataProviderNotRunningEvent, + vmwInvalidResponseFromDatasourceEvent, + vmwHostNotReachableEvent, + vmwNSXControllerNotFoundEvent, + vmwUnexpectedDSTypeOrVersionEvent, + vmwWarnConfigEvent, + vmwInvalidConfigEvent, + vmwNotFoundEvent, + vmwInsufficientPrivilegesEvent, + vmwPwdAuthModeDisabledEvent, + vmwFailedCredsEncryptEvent, + vmwSNMPConnectionInvalidEvent, + vmwUnknownHostEvent, + vmwInvalidCredentialsEvent, + vmwIncorrectConnectionStringEvent, + vmwConnectionRefusedEvent, + vmwTimeoutEvent, + vmwFailedEvent, + vmwNSXTEvent, + vmwNSXTVcNotAddedEvent, + vmwNSXTStandaloneHostsEvent, + vmwLargeSdmsDroppedEvent, + vmwNSXTIPFixDFWStatusNotEnabledEvent, + vmwNSXTIPFixPortIncorrectEvent, + vmwNSXTIPFixCollectorAndIPFixProfileMismatchEvent, + vmwNSXTIPFixIPFixProfilePriorityNotZeroEvent, + vmwNSXTIPFixNoIPFixProfileEvent, + vmwNSXTIPFixNoNewCollectorProfileCanBeAddedEvent, + vmwNSXTIPFixNoCollectorProfileEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) since last revision." + ::= { vmwNetworkInsightMIBGroups 65 } + + vmwNetworkInsightNotificationGroup6 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNSXTSystemEvent, + vmwNSXTNoUplinkConnectivityEvent, + vmwNSXTRoutingAdvertisementEvent, + vmwNSXTManagerConnectivityDownEvent, + vmwNSXTControllerConnectivityDegradedEvent, + vmwNSXTControllerConnectivityDownEvent, + vmwNSXTMtuMismatchEvent, + vmwNSXEdgeBGPNeighbourDownEvent, + vmwAnalyticsEvent, + vmwAnalyticsOutlierEvent, + vmwAnalyticsThresholdEvent, + vmwVMCEvent, + vmwPolicyManagerVrniDfwIPFixCollectorAbsent, + vmwPolicyManagerNoDfwIPFixProfile + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 4.0.0 release." + ::= { vmwNetworkInsightMIBGroups 75 } + + vmwNetworkInsightNotificationGroup7 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNSXTDoubleVlanTaggingEvent, + vmwNSXTVtepDeleteEvent, + vmwNSXTNoTzAttachedOnTnEvent, + vmwNSXTExcludedVmFlowEvent, + vmwKubernetesInsufficientPrivilegesEvent, + vmwPKSKubernetesUnknownHostEvent, + vmwDatasourceIdentificationChangedEvent, + vmwLBPoolMemberDownEvent, + vmwLBPoolDownEvent, + vmwLBPoolMemberVMDownEvent, + vmwLBServiceNodeIPNotFoundEvent, + vmwLBServiceNodeMultipleNicFoundEvent, + vmwLBVirtualServerDisableEvent, + vmwLBPoolEmptyEvent, + vmwDuplicateL3SwitchEvent, + vmwArkinApplicationMemberLimitEvent, + vmwNSXTSwitchIpfixEnabledEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 4.1.0 release." + ::= { vmwNetworkInsightMIBGroups 85 } + + vmwNetworkInsightNotificationGroup8 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwUANIFileNotProvidedEvent, + vmwUANIFileDoesNotExistEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 4.2.0 release." + ::= { vmwNetworkInsightMIBGroups 95 } + + vmwNetworkInsightNotificationGroup9 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNSXTStandaloneHostsWithoutVcEvent, + vmwApplianceNotConfiguredEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 5.0.0 release." + ::= { vmwNetworkInsightMIBGroups 105 } + + vmwNetworkInsightNotificationGroup10 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwSwitchPortUptimeThresholdRecededEvent, + vmwFdbConfigStoreCleanupFailedEvent, + vmwDiskAllocationInsufficientEvent, + vmwNSXTControllerNodeToControlClusterConnectivityEvent, + vmwNSXTControllerNodeToMgmtPlaneConnectivityEvent, + vmwNSXTMPNodeToMgmtClusterConnectivityEvent, + vmwBigIpInsufficientShellAccessEvent, + vmwBigIpInsufficientPartitionAccessEvent, + vmwBigIpInsufficientRoleEvent, + vmwNSXTLatencyCollectorMismatchEvent, + vmwNSXTLatencyNoBFDProfileEvent, + vmwNSXTLatencyMoreBFDProfileEvent, + vmwNSXTLatencyNotEnabledEvent, + vmwHardwareVTEPMismatchEvent, + vmwHardwareVTEPPortDownEvent, + vmwNSXVLatencyNoDataEvent, + vmwKubernetesBaseEvent, + vmwVMCVMLimitExceededEvent, + vmwVMCHostLimitExceededEvent, + vmwVeloCloudEdgeDegradedTransQoeEvent, + vmwVeloCloudEdgeDegradedVideoQoeEvent, + vmwVeloCloudEdgeDegradedVoiceQoeEvent, + vmwVeloCloudEdgeDownEvent, + vmwVeloCloudLinkLostPacketEventRx, + vmwVeloCloudLinkDegradedTransQoeEvent, + vmwVeloCloudLinkLostPacketEventTx, + vmwVeloCloudLinkDegradedVideoQoeEvent, + vmwVeloCloudLinkDegradedVoiceQoeEvent, + vmwVeloCloudLinkDownEvent, + vmwNSXTHostNodeMgmtConnectivityStatusDownEvent, + vmwNSXTEdgeNodeCtlrConnectivityStatusUnknownEvent, + vmwNSXTHostNodeCtlrConnectivityStatusDownEvent, + vmwNSXTHostNodeCtlrConnectivityStatusDegradedEvent, + vmwNSXTHostNodeCtlrConnectivityStatusUnknownEvent, + vmwNSXTHostNodePnicStatusDownEvent, + vmwNSXTHostNodePnicStatusDegradedEvent, + vmwNSXTHostNodePnicStatusUnknownEvent, + vmwNSXTEdgeNodePnicStatusDownEvent, + vmwNSXTEdgeNodePnicStatusDegradedEvent, + vmwNSXTEdgeNodePnicStatusUnknownEvent, + vmwNSXTHostNodeTunnelStatusDownEvent, + vmwNSXTHostNodeTunnelStatusDegradedEvent, + vmwNSXTHostNodeTunnelStatusUnknownEvent, + vmwNSXTEdgeNodeTunnelStatusDownEvent, + vmwNSXTEdgeNodeTunnelStatusDegradedEvent, + vmwNSXTEdgeNodeTunnelStatusUnknownEvent, + vmwNSXTHostNodeStatusDownEvent, + vmwNSXTHostNodeStatusDegradedEvent, + vmwNSXTHostNodeStatusUnknownEvent, + vmwNSXTEdgeNodeStatusDownEvent, + vmwNSXTEdgeNodeStatusDegradedEvent, + vmwNSXTEdgeNodeStatusUnknownEvent, + vmwSwitchPortOperationalDownEvent, + vmwRouterInterfaceOperationalDownEvent, + vmwUnderlayDeviceGenericEvent, + vmwUnderlayDeviceFexOfflineEvent, + vmwUnderlayDeviceFanMalFunctionEvent, + vmwUnderlayDeviceTemperatureThresholdExceededEvent, + vmwUnderlayDeviceFexFanMalFunctionEvent, + vmwUnderlayDeviceFexPsMalFunctionEvent, + vmwUnderlayDeviceModuleMalFunctionEvent, + vmwUnderlayDevicePsMalFunctionEvent, + vmwUnderlayDeviceBfdSessionRemovedEvent, + vmwUnderlayDeviceLldpNeighbourRemovedEvent, + vmwThresholdExceededEventDataSourceCpuUsage, + vmwThresholdExceededEventDataSourceMemoryUsage, + vmwThresholdExceededEventDataSourceTemperature, + vmwDeploymentDefMismatchEvent, + vmwNsxtLatencyServiceConfigMismatchEvent, + vmwNsxtLatencyNodeGroupMismatchEvent, + vmwNsxtLatencyStatProfileMismatchEvent, + vmwHybridConnectBgpStatusDownEvent, + vmwNSXTClusterBackUpDisabledEvent, + vmwNSXTDFWFirewallDisabledEvent, + vmwNSXTComputeManagerConnectionStatusNotUpEvent, + vmwNSXTLogicalSwitchAdminStatusDownEvent, + vmwNSXTLogicalPortOperationalStatusDownEvent, + vmwNSXTLogicalPortOperationalStatusUnknownEvent, + vmwNSXTLogicalPortReceivedPacketDropEvent, + vmwNSXTLogicalPortTransmittedPacketDropEvent, + vmwNSXTLogicalSwitchReceivedPacketDropEvent, + vmwNSXTLogicalSwitchTransmittedPacketDropEvent, + vmwNSXTRxPacketDropOnMPNicEvent, + vmwNSXTRxPacketDropOnEdgeTnNicEvent, + vmwNSXTRxPacketDropOnHostTnNicEvent, + vmwNSXTTxPacketDropOnMPNicEvent, + vmwNSXTTxPacketDropOnEdgeTnNicEvent, + vmwNSXTTxPacketDropOnHostTnNicEvent, + vmwNSXTMPNodeServiceClusterManagerStatusEvent, + vmwNSXTMPNodeServiceCmInventoryStatusEvent, + vmwNSXTMPNodeServiceControllerStatusEvent, + vmwNSXTMPNodeServiceDataStoreStatusEvent, + vmwNSXTMPNodeServiceHttpStatusEvent, + vmwNSXTMPNodeServiceInstallUpgradeEvent, + vmwNSXTMPNodeServiceLiagentStatusEvent, + vmwNSXTMPNodeServiceManagerStatusEvent, + vmwNSXTMPNodeServiceMgmtPlaneBusStatusEvent, + vmwNSXTMPNodeServiceMigrationCoordinatorStatusEvent, + vmwNSXTMPNodeServiceNodeMgmtStatusEvent, + vmwNSXTMPNodeServiceNodeStatsStatusEvent, + vmwNSXTMPNodeServiceNSXMessageBusStatusEvent, + vmwNSXTMPNodeServiceNSXPlatformClientStatusEvent, + vmwNSXTMPNodeServiceNSXUpgradeAgentStatusEvent, + vmwNSXTMPNodeServiceNTPStatusEvent, + vmwNSXTMPNodeServicePolicyStatusEvent, + vmwNSXTMPNodeServiceSearchStatusEvent, + vmwNSXTMPNodeServiceSNMPStatusEvent, + vmwNSXTMPNodeServiceSSHStatusEvent, + vmwNSXTMPNodeServiceSyslogStatusEvent, + vmwNSXTMPNodeServiceTelemetryStatusEvent, + vmwNSXTMPNodeServiceUIServiceStatusEvent, + vmwVMCHostPerClusterLimitExceededEvent, + vmwVMCVMPerHostLimitExceededEvent, + vmwVMCClusterLimitExceededEvent, + vmwProtectionEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 5.2.0 release." + ::= { vmwNetworkInsightMIBGroups 115 } + + vmwNetworkInsightNotificationGroup11 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxiApplianceAvailableEvent, + vmwNsxiSubscriptionCreateFailedEvent, + vmwNsxiSubscriptionDeleteFailedEvent, + vmwNsxiSubscriptionUpdateFailedEvent, + vmwNsxiSslHandshakeFailedEvent, + vmwAnalyticsThresholdCompositeEvent, + vmwAnalyticsThresholdCompositeProblemEvent, + vmwLicenseExpiredEvent, + vmwInGracePeriodEvent, + vmwFailedDatasourceOperationEvent, + vmwNsxtNotificationWebhookDisabledEvent, + vmwNatRuleLargeSubnetEvent, + vmwNSXTHostNodeMaintenanceModeEvent, + vmwNSXTEdgeNodeMaintenanceModeEvent, + vmwSDWanLinkTrafficThresholdEvent, + vmwVMCCapacityThresholdBreachEvent, + vmwNativeVlanMismatchEvent, + vmwNativeVlanTaggingMismatchEvent, + vmwSnapshotNotBuildingEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 6.2.0 release." + ::= { vmwNetworkInsightMIBGroups 125 } + + vmwNetworkInsightNotificationGroup12 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwProtectionActiveEvent, + vmwUnableToSendSNMPTrapsEvent, + vmwStreamProcessingFailedEvent, + vmwSNOWMandatoryPrivilegesMissingEvent, + vmwVMCSDDCTGWConnectivityFailedEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 6.4.0 release." + ::= { vmwNetworkInsightMIBGroups 135 } + + vmwNetworkInsightNotificationGroup13 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNSXTEdgeDVPGsIPFIXDisabledEvent, + vmwUnsupportedNsxAlbVersionEvent, + vmwIpfixFlowLagEvent, + vmwNSXALBSystemEvent, + vmwTkgiKubernetesNotReachableEvent, + vmwTkgiClustersInsufficientPriviledgesEvent, + vmwNSXTRouterInterfaceRPFPacketDropEvent, + vmwChangeEventsDroppedEvent, + vmwHcxIXServiceStatusEvent, + vmwHcxNEServiceStatusEvent, + vmwHcxBMServiceStatusEvent, + vmwHcxVMotionServiceStatusEvent, + vmwHcxIXApplianceEncryptionTunnelStatusEvent, + vmwHcxNEApplianceEncryptionTunnelStatusEvent, + vmwHcxIXApplianceServicePipelineStatusEvent, + vmwHcxNEApplianceServicePipelineStatusEvent, + vmwHcxIXApplianceServiceTransportStatusEvent, + vmwHcxNEApplianceServiceTransportStatusEvent, + vmwHcxIXApplianceServiceSystemStateEvent, + vmwHcxNEApplianceServiceSystemStateEvent, + vmwHcxIXServiceNotRunningEvent, + vmwHcxNEServiceNotRunningEvent, + vmwHcxWanOptServiceNotRunningEvent, + vmwPanLogInsightDroppedFlowEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 6.6.0 release." + ::= { vmwNetworkInsightMIBGroups 145 } + + vmwNetworkInsightNotificationGroup14 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwHcxConnectionRuleViolationEvent, + vmwHcxApplianceAllTunnelDownEvent, + vmwHcxMtuMismatchEvent, + vmwSwitchPortRPFPacketDropEvent, + vmwCPLogInsightDroppedFlowEvent, + vmwSNMPTrapEvent, + vmwServiceRestartCountExceededEvent, + vmwHcxWanOptServiceStatusEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 6.8.0 release." + ::= { vmwNetworkInsightMIBGroups 155 } + + vmwNetworkInsightNotificationGroup15 NOTIFICATION-GROUP + NOTIFICATIONS { + vmwNsxtIpfixMultipleCollectorConfigurationEvent, + vmwHcxApplianceUnhealthyTunnelsEvent, + vmwHcxManagerVersionMismatchEvent, + vmwHcxApplianceVersionMismatchEvent + } + STATUS current + DESCRIPTION + "Set of added notifications (traps, informs) for 6.10.0 release." + ::= { vmwNetworkInsightMIBGroups 165 } +END
\ No newline at end of file diff --git a/MIBS/vmware/VMWARE-VROPS-AGENTCAP-MIB b/MIBS/vmware/VMWARE-VROPS-AGENTCAP-MIB new file mode 100644 index 0000000..0d434ca --- /dev/null +++ b/MIBS/vmware/VMWARE-VROPS-AGENTCAP-MIB @@ -0,0 +1,51 @@ +-- ********************************************************** +-- Copyright 2018 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-VROPS-AGENTCAP-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY + FROM SNMPv2-SMI + vmwareAgentCapabilities + FROM VMWARE-ROOT-MIB + AGENT-CAPABILITIES + FROM SNMPv2-CONF; +vmwVropsAgentCapabilityMIB MODULE-IDENTITY + LAST-UPDATED "201806270000Z" + 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 vRealize Operations Manager agents by release." + REVISION "201806270000Z" + DESCRIPTION + "Capabilities for vRealize Operations Manager 7.0 releases." + + ::= { vmwareAgentCapabilities 27 } + +vmwVropsCapability OBJECT IDENTIFIER ::= { vmwVropsAgentCapabilityMIB 1 } + +vmwVrops2018-70 AGENT-CAPABILITIES + PRODUCT-RELEASE + "7.0.0" + STATUS current + DESCRIPTION + "Release 7.0.0 for VMware vRealize Operations Manager supporting only SNMPv2c/SNMPv3 trap PDUs. + It describes all the notifications sent from the vRealize Operations Manager. + " + REFERENCE + "http://www.vmware.com/products" + -- REVISION 201806270000Z + SUPPORTS VMWARE-VROPS-MIB + INCLUDES { + vmwVROPSNotificationGroup + } + ::= { vmwVropsCapability 1 } +END diff --git a/MIBS/vmware/VMWARE-VROPS-MIB b/MIBS/vmware/VMWARE-VROPS-MIB new file mode 100644 index 0000000..40212f2 --- /dev/null +++ b/MIBS/vmware/VMWARE-VROPS-MIB @@ -0,0 +1,407 @@ +-- ********************************************************** +-- Copyright 2013-2018 VMware, Inc. All rights reserved. +-- ********************************************************** + +VMWARE-VROPS-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE + FROM SNMPv2-SMI + SnmpAdminString + FROM SNMP-FRAMEWORK-MIB + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF + VmwLongDisplayString + FROM VMWARE-TC-MIB + vmwVrops + FROM VMWARE-PRODUCTS-MIB; + +vmwVropsMIB MODULE-IDENTITY + LAST-UPDATED "201806270000Z" + 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 first versin of VMWARE-VROPS-MIB, it replaces VMWARE-VCOPS-MIB." + REVISION "201806270000Z" + DESCRIPTION + "Initial MIB design." + ::= { vmwVrops 1 } + +-- +-- Top-level MIB groups +-- + +-- Group 0: Alerts sent as traps +vmwAlertTrap OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This group is actually the prefix one uses when creating + enterprise-specific trap OID's for an SNMP trap. It is + used in the VMware MIB when defining traps." + ::= { vmwVropsMIB 0 } +-- +-- Group 2: Generic data sent in All Alerts +-- Generic data, in var-binds, that is associated with EVERY Alert +-- +vmwGenericAlertData OBJECT-IDENTITY + STATUS current + DESCRIPTION + "This members of this group are the OIDs for VarBinds + that contain data for ALL Alerts." + ::= { vmwVropsMIB 2 } + +vmwAlertAliveServerName OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The name of the vRealize Operations server that generated this alert." + ::= { vmwGenericAlertData 1 } + +vmwAlertEntityName OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The resource name on which this alert was generated." + ::= { vmwGenericAlertData 2 } + +vmwAlertEntityType OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The resource kind type on which this alert was generated." + ::= { vmwGenericAlertData 3 } + +vmwAlertTimestamp OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The timestamp of the alert in UTC format." + ::= { vmwGenericAlertData 4 } + +vmwAlertCriticality OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "A text string describing the alert criticality level, + i.e. Info, Warning, Immediate and Critical." + ::= { vmwGenericAlertData 5 } + +vmwAlertRootCause OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "A text string describing the root-cause of the notification that was generated, + i.e. state, date (human readable) and of the alert that was triggered." + ::= { vmwGenericAlertData 6 } + +vmwAlertURL OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The URL of the 'Alert Summary' page of the alert that was generated." + ::= { vmwGenericAlertData 7 } + +vmwAlertID OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The unique vRealize Operations identifier of the alert that was generated." + ::= { vmwGenericAlertData 8 } + +vmwAlertMessage OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The detailed symptom level info message of the alert that was generated, + i.e. Symptom set id, affected object count, + name, criticality and id of the symptom, + metric/property name and violation" + + ::= { vmwGenericAlertData 9 } + +vmwAlertType OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The textual type description of the alert that was generated, + i.e. Application, Virtualization/Hypervisor, Hardware(OSI), Storage or Network" + ::= { vmwGenericAlertData 10 } + + +vmwAlertSubtype OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The textual subtype description of the alert that was generated, i.e. + Performance, Configuration, Availability, Capacity or Compliance" + ::= { vmwGenericAlertData 11 } + +vmwAlertHealth OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Health badge state, i.e. Info, Warning, Immediate and Critical." + ::= { vmwGenericAlertData 12 } + +vmwAlertRisk OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Risk badge state, i.e. Info, Warning, Immediate and Critical." + ::= { vmwGenericAlertData 13 } + +vmwAlertEfficiency OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Efficiency badge state, i.e. Info, Warning, Immediate and Critical." + ::= { vmwGenericAlertData 14 } + +vmwAlertMetricName OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The textual violated metric name of the one of the alarm of the alert that was generated." + ::= { vmwGenericAlertData 15 } + +vmwAlertResourceKind OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Resource kind name of the object on which alert was generated." + ::= { vmwGenericAlertData 16 } + +vmwAlertDefinitionName OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Description of the alert that was triggered" + ::= { vmwGenericAlertData 17 } + +vmwAlertDefinitionDesc OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Detailed description of the alert that was triggered" + ::= { vmwGenericAlertData 18 } + +vmwAlertImpact OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "Badge impact of the alert that was triggered, i.e. Health, Risk or Efficiency + See More: + https://docs-staging.vmware.com/en/vRealize-Operations-Manager/6.7/com.vmware.vcom.metrics.doc/GUID-D04D495F-6FA7-483F-9EC9-C0EC35A6D887.html" + ::= { vmwGenericAlertData 19 } + +vmwAlertNotificationRules OBJECT-TYPE + SYNTAX VmwLongDisplayString + MAX-ACCESS accessible-for-notify + STATUS current + DESCRIPTION + "The notification rules through which notification was generated. + See more; + https://docs-staging.vmware.com/en/vRealize-Operations-Manager/6.7/com.vmware.vcom.config.doc/GUID-A81D8798-46D5-43E6-B717-226769B5A9B0.html" + ::= { vmwGenericAlertData 20 } + +vmwTrapProblemActive NOTIFICATION-TYPE + OBJECTS { + vmwAlertAliveServerName, + vmwAlertEntityName, + vmwAlertEntityType, + vmwAlertTimestamp, + vmwAlertCriticality, + vmwAlertRootCause, + vmwAlertURL, + vmwAlertID, + vmwAlertMessage, + vmwAlertType, + vmwAlertSubtype, + vmwAlertHealth, + vmwAlertRisk, + vmwAlertEfficiency, + vmwAlertMetricName, + vmwAlertResourceKind, + vmwAlertDefinitionName, + vmwAlertDefinitionDesc, + vmwAlertImpact, + vmwAlertNotificationRules + } + STATUS current + DESCRIPTION + "A trap describing a Problem Alert that indicates a Abnormality condition + became active." + ::= { vmwAlertTrap 46 } + +vmwTrapProblemClear NOTIFICATION-TYPE + OBJECTS { + vmwAlertAliveServerName, + vmwAlertEntityName, + vmwAlertEntityType, + vmwAlertTimestamp, + vmwAlertCriticality, + vmwAlertRootCause, + vmwAlertURL, + vmwAlertID, + vmwAlertMessage, + vmwAlertType, + vmwAlertSubtype, + vmwAlertHealth, + vmwAlertRisk, + vmwAlertEfficiency, + vmwAlertMetricName, + vmwAlertResourceKind, + vmwAlertDefinitionName, + vmwAlertDefinitionDesc, + vmwAlertImpact, + vmwAlertNotificationRules + } + STATUS current + DESCRIPTION + "A trap describing a Problem Alert that indicates a Abnormality condition + became inactive." + ::= { vmwAlertTrap 47 } + +vmwTrapProblemChange NOTIFICATION-TYPE + OBJECTS { + vmwAlertAliveServerName, + vmwAlertEntityName, + vmwAlertEntityType, + vmwAlertTimestamp, + vmwAlertCriticality, + vmwAlertRootCause, + vmwAlertURL, + vmwAlertID, + vmwAlertMessage, + vmwAlertType, + vmwAlertSubtype, + vmwAlertMetricName, + vmwAlertResourceKind, + vmwAlertHealth, + vmwAlertRisk, + vmwAlertEfficiency, + vmwAlertDefinitionName, + vmwAlertDefinitionDesc, + vmwAlertImpact, + vmwAlertNotificationRules + } + STATUS current + DESCRIPTION + "A trap describing a Problem Alert that indicates a Abnormality condition + has changed one of its parameters' value." + ::= { vmwAlertTrap 48 } + +-- Trap for functional testing. +-- + +vmwTrapTest NOTIFICATION-TYPE + OBJECTS { + vmwAlertAliveServerName, + vmwAlertEntityName, + vmwAlertEntityType, + vmwAlertTimestamp, + vmwAlertCriticality, + vmwAlertRootCause, + vmwAlertURL, + vmwAlertID, + vmwAlertMessage, + vmwAlertType, + vmwAlertSubtype, + vmwAlertMetricName, + vmwAlertResourceKind, + vmwAlertHealth, + vmwAlertRisk, + vmwAlertEfficiency, + vmwAlertDefinitionName, + vmwAlertDefinitionDesc, + vmwAlertImpact, + vmwAlertNotificationRules + } + STATUS current + DESCRIPTION + "Trap for testing purposes." + ::= { vmwAlertTrap 200 } + +-- conformance information +vmwVROPSMIBConformance OBJECT IDENTIFIER ::= { vmwVropsMIB 99 } +vmwVROPSMIBCompliances OBJECT IDENTIFIER ::= { vmwVROPSMIBConformance 1 } +vmwVROPSMIBGroups OBJECT IDENTIFIER ::= { vmwVROPSMIBConformance 2 } + +-- compliance statements +vmwVROPSMIBBasicCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement VMWARE-VROPS-MIB." + MODULE -- this module + MANDATORY-GROUPS { vmwVROPSNotificationInfoGroup, vmwVROPSNotificationGroup } + ::= { vmwVROPSMIBCompliances 1 } + +vmwVROPSNotificationInfoGroup OBJECT-GROUP + OBJECTS { + vmwAlertAliveServerName, + vmwAlertEntityName, + vmwAlertEntityType, + vmwAlertTimestamp, + vmwAlertCriticality, + vmwAlertRootCause, + vmwAlertURL, + vmwAlertID, + vmwAlertMessage, + vmwAlertType, + vmwAlertSubtype, + vmwAlertMetricName, + vmwAlertResourceKind, + vmwAlertHealth, + vmwAlertRisk, + vmwAlertEfficiency, + vmwAlertDefinitionName, + vmwAlertDefinitionDesc, + vmwAlertImpact, + vmwAlertNotificationRules + } + STATUS current + DESCRIPTION + "These objects provide details in vRealize Operations notifications." + ::= { vmwVROPSMIBGroups 1 } + + +vmwVROPSNotificationGroup NOTIFICATION-GROUP + NOTIFICATIONS { + vmwTrapTest, + vmwTrapProblemActive, + vmwTrapProblemClear, + vmwTrapProblemChange + } + STATUS current + DESCRIPTION + "Group of objects describing traps supported for this + version of this mib modules." + ::= { vmwVROPSMIBGroups 2 } + +END |