claudio/VSC
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Issue

Browse Source 
Code backup
This commit is contained in:
Claudio
2026-05-10 16:59:01 +02:00
commit 368d6fafea
796 changed files with 315310 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Icinga2/_Test/vSan Mib/vmw/BRIDGE-MIB.mib
+1466
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/ENTITY-MIB.mib
+1500
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/HOST-RESOURCES-MIB.mib
+1542
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/HOST-RESOURCES-TYPES.mib
+389
View File
@@ -0,0 +1,389 @@
HOST-RESOURCES-TYPES DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY FROM SNMPv2-SMI
hrMIBAdminInfo, hrStorage, hrDevice FROM HOST-RESOURCES-MIB;
hostResourcesTypesModule MODULE-IDENTITY
LAST-UPDATED "200003060000Z" -- 6 March, 2000
ORGANIZATION "IETF Host Resources MIB Working Group"
CONTACT-INFO
"Steve Waldbusser
Postal: Lucent Technologies, Inc.
1213 Innsbruck Dr.
Sunnyvale, CA 94089
USA
Phone: 650-318-1251
Fax: 650-318-1633
Email: waldbusser@ins.com
In addition, the Host Resources MIB mailing list is dedicated
to discussion of this MIB. To join the mailing list, send a
request message to hostmib-request@andrew.cmu.edu. The mailing
list address is hostmib@andrew.cmu.edu."
DESCRIPTION
"This MIB module registers type definitions for
storage types, device types, and file system types.
After the initial revision, this module will be
maintained by IANA."
REVISION "200003060000Z" -- 6 March 2000
DESCRIPTION
"The original version of this module, published as RFC
2790."
::= { hrMIBAdminInfo 4 }
-- Registrations for some storage types, for use with hrStorageType
hrStorageTypes OBJECT IDENTIFIER ::= { hrStorage 1 }
hrStorageOther OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used when no other defined
type is appropriate."
::= { hrStorageTypes 1 }
hrStorageRam OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for RAM."
::= { hrStorageTypes 2 }
hrStorageVirtualMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for virtual memory,
temporary storage of swapped or paged memory."
::= { hrStorageTypes 3 }
hrStorageFixedDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for non-removable
rigid rotating magnetic storage devices."
::= { hrStorageTypes 4 }
hrStorageRemovableDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for removable rigid
rotating magnetic storage devices."
::= { hrStorageTypes 5 }
hrStorageFloppyDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for non-rigid rotating
magnetic storage devices."
::= { hrStorageTypes 6 }
hrStorageCompactDisc OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for read-only rotating
optical storage devices."
::= { hrStorageTypes 7 }
hrStorageRamDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for a file system that
is stored in RAM."
::= { hrStorageTypes 8 }
hrStorageFlashMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for flash memory."
::= { hrStorageTypes 9 }
hrStorageNetworkDisk OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The storage type identifier used for a
networked file system."
::= { hrStorageTypes 10 }
-- Registrations for some device types, for use with hrDeviceType
hrDeviceTypes OBJECT IDENTIFIER ::= { hrDevice 1 }
hrDeviceOther OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used when no other defined
type is appropriate."
::= { hrDeviceTypes 1 }
hrDeviceUnknown OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used when the device type is
unknown."
::= { hrDeviceTypes 2 }
hrDeviceProcessor OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a CPU."
::= { hrDeviceTypes 3 }
hrDeviceNetwork OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a network interface."
::= { hrDeviceTypes 4 }
hrDevicePrinter OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a printer."
::= { hrDeviceTypes 5 }
hrDeviceDiskStorage OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a disk drive."
::= { hrDeviceTypes 6 }
hrDeviceVideo OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a video device."
::= { hrDeviceTypes 10 }
hrDeviceAudio OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for an audio device."
::= { hrDeviceTypes 11 }
hrDeviceCoprocessor OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a co-processor."
::= { hrDeviceTypes 12 }
hrDeviceKeyboard OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a keyboard device."
::= { hrDeviceTypes 13 }
hrDeviceModem OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a modem."
::= { hrDeviceTypes 14 }
hrDeviceParallelPort OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a parallel port."
::= { hrDeviceTypes 15 }
hrDevicePointing OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a pointing device
(e.g., a mouse)."
::= { hrDeviceTypes 16 }
hrDeviceSerialPort OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a serial port."
::= { hrDeviceTypes 17 }
hrDeviceTape OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a tape storage device."
::= { hrDeviceTypes 18 }
hrDeviceClock OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a clock device."
::= { hrDeviceTypes 19 }
hrDeviceVolatileMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a volatile memory
storage device."
::= { hrDeviceTypes 20 }
hrDeviceNonVolatileMemory OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The device type identifier used for a non-volatile memory
storage device."
::= { hrDeviceTypes 21 }
-- Registrations for some popular File System types,
-- for use with hrFSType.
hrFSTypes OBJECT IDENTIFIER ::= { hrDevice 9 }
hrFSOther OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used when no other
defined type is appropriate."
::= { hrFSTypes 1 }
hrFSUnknown OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used when the type of
file system is unknown."
::= { hrFSTypes 2 }
hrFSBerkeleyFFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Berkeley Fast File System."
::= { hrFSTypes 3 }
hrFSSys5FS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
System V File System."
::= { hrFSTypes 4 }
hrFSFat OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for
DOS's FAT file system."
::= { hrFSTypes 5 }
hrFSHPFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for OS/2's
High Performance File System."
::= { hrFSTypes 6 }
hrFSHFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Macintosh Hierarchical File System."
::= { hrFSTypes 7 }
hrFSMFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Macintosh File System."
::= { hrFSTypes 8 }
hrFSNTFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Windows NT File System."
::= { hrFSTypes 9 }
hrFSVNode OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
VNode File System."
::= { hrFSTypes 10 }
hrFSJournaled OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Journaled File System."
::= { hrFSTypes 11 }
hrFSiso9660 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
ISO 9660 File System for CD's."
::= { hrFSTypes 12 }
hrFSRockRidge OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
RockRidge File System for CD's."
::= { hrFSTypes 13 }
hrFSNFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
NFS File System."
::= { hrFSTypes 14 }
hrFSNetware OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Netware File System."
::= { hrFSTypes 15 }
hrFSAFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Andrew File System."
::= { hrFSTypes 16 }
hrFSDFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
OSF DCE Distributed File System."
::= { hrFSTypes 17 }
hrFSAppleshare OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
AppleShare File System."
::= { hrFSTypes 18 }
hrFSRFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
RFS File System."
::= { hrFSTypes 19 }
hrFSDGCFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Data General DGCFS."
::= { hrFSTypes 20 }
hrFSBFS OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
SVR4 Boot File System."
::= { hrFSTypes 21 }
hrFSFAT32 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Windows FAT32 File System."
::= { hrFSTypes 22 }
hrFSLinuxExt2 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The file system type identifier used for the
Linux EXT2 File System."
::= { hrFSTypes 23 }
END
Icinga2/_Test/vSan Mib/vmw/IANA-ADDRESS-FAMILY-NUMBERS-MIB.mib
+178
View File
@@ -0,0 +1,178 @@
-- https://www.iana.org/assignments/ianaaddressfamilynumbers-mib/ianaaddressfamilynumbers-mib
IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaAddressFamilyNumbers MODULE-IDENTITY
LAST-UPDATED "201409020000Z" -- September 2, 2014
ORGANIZATION "IANA"
CONTACT-INFO
"Postal: Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
USA
Tel: +1 310-301-5800
E-Mail: iana&iana.org"
DESCRIPTION
"The MIB module defines the AddressFamilyNumbers
textual convention."
-- revision history
REVISION "201409020000Z" -- September 2, 2014
DESCRIPTION "Assigned value 16396."
REVISION "201309250000Z" -- September 25, 2013
DESCRIPTION "Assigned values 16391-16395."
REVISION "201307160000Z" -- July 16, 2013
DESCRIPTION "Fixed labels for 16389-16390."
REVISION "201306260000Z" -- June 26, 2013
DESCRIPTION "Added assignments 26-28."
REVISION "201306180000Z" -- June 18, 2013
DESCRIPTION "Added assignments 16384-16390. Assignment
25 added in 2007 revision."
REVISION "200203140000Z" -- March 14, 2002
DESCRIPTION "AddressFamilyNumbers assignment 22 to
fibreChannelWWPN. AddressFamilyNumbers
assignment 23 to fibreChannelWWNN.
AddressFamilyNumers assignment 24 to gwid."
REVISION "200009080000Z" -- September 8, 2000
DESCRIPTION "AddressFamilyNumbers assignment 19 to xtpOverIpv4.
AddressFamilyNumbers assignment 20 to xtpOverIpv6.
AddressFamilyNumbers assignment 21 to xtpNativeModeXTP."
REVISION "200003010000Z" -- March 1, 2000
DESCRIPTION "AddressFamilyNumbers assignment 17 to distinguishedName.
AddressFamilyNumbers assignment 18 to asNumber."
REVISION "200002040000Z" -- February 4, 2000
DESCRIPTION "AddressFamilyNumbers assignment 16 to dns."
REVISION "9908260000Z" -- August 26, 1999
DESCRIPTION "Initial version, published as RFC 2677."
::= { mib-2 72 }
AddressFamilyNumbers ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.
(The latest arrangements can be obtained by
contacting the IANA.)
The enumerations are described as:
other(0), -- none of the following
ipV4(1), -- IP Version 4
ipV6(2), -- IP Version 6
nsap(3), -- NSAP
hdlc(4), -- (8-bit multidrop)
bbn1822(5),
all802(6), -- (includes all 802 media
-- plus Ethernet 'canonical format')
e163(7),
e164(8), -- (SMDS, Frame Relay, ATM)
f69(9), -- (Telex)
x121(10), -- (X.25, Frame Relay)
ipx(11), -- IPX (Internet Protocol Exchange)
appleTalk(12), -- Apple Talk
decnetIV(13), -- DEC Net Phase IV
banyanVines(14), -- Banyan Vines
e164withNsap(15),
-- (E.164 with NSAP format subaddress)
dns(16), -- (Domain Name System)
distinguishedName(17), -- (Distinguished Name, per X.500)
asNumber(18), -- (16-bit quantity, per the AS number space)
xtpOverIpv4(19), -- XTP over IP version 4
xtpOverIpv6(20), -- XTP over IP version 6
xtpNativeModeXTP(21), -- XTP native mode XTP
fibreChannelWWPN(22), -- Fibre Channel World-Wide Port Name
fibreChannelWWNN(23), -- Fibre Channel World-Wide Node Name
gwid(24), -- Gateway Identifier
afi(25), -- AFI for L2VPN information
mplsTpSectionEndpointIdentifier(26), -- MPLS-TP Section Endpoint Identifier
mplsTpLspEndpointIdentifier(27), -- MPLS-TP LSP Endpoint Identifier
mplsTpPseudowireEndpointIdentifier(28), -- MPLS-TP Pseudowire Endpoint Identifier
eigrpCommonServiceFamily(16384), -- EIGRP Common Service Family
eigrpIpv4ServiceFamily(16385), -- EIGRP IPv4 Service Family
eigrpIpv6ServiceFamily(16386), -- EIGRP IPv6 Service Family
lispCanonicalAddressFormat(16387), -- LISP Canonical Address Format (LCAF)
bgpLs(16388), -- BGP-LS
fortyeightBitMacBitMac(16389), -- 48-bit MAC
sixtyfourBitMac(16390), -- 64-bit MAC
oui(16391), -- OUI
mac24(16392), -- MAC/24
mac40(16393), -- MAC/40
ipv664(16394), -- IPv6/64
rBridgePortID(16395), -- RBridge Port ID
trillNickname(16396), -- TRILL Nickname
reserved(65535)
Requests for new values should be made to IANA via
email (iana&iana.org)."
SYNTAX INTEGER {
other(0),
ipV4(1),
ipV6(2),
nsap(3),
hdlc(4),
bbn1822(5),
all802(6),
e163(7),
e164(8),
f69(9),
x121(10),
ipx(11),
appleTalk(12),
decnetIV(13),
banyanVines(14),
e164withNsap(15),
dns(16),
distinguishedName(17), -- (Distinguished Name, per X.500)
asNumber(18), -- (16-bit quantity, per the AS number space)
xtpOverIpv4(19),
xtpOverIpv6(20),
xtpNativeModeXTP(21),
fibreChannelWWPN(22),
fibreChannelWWNN(23),
gwid(24),
afi(25),
mplsTpSectionEndpointIdentifier(26),
mplsTpLspEndpointIdentifier(27),
mplsTpPseudowireEndpointIdentifier(28),
eigrpCommonServiceFamily(16384),
eigrpIpv4ServiceFamily(16385),
eigrpIpv6ServiceFamily(16386),
lispCanonicalAddressFormat(16387),
bgpLs(16388),
fortyeightBitMac(16389),
sixtyfourBitMac(16390),
oui(16391),
mac24(16392),
mac40(16393),
ipv664(16394),
rBridgePortID(16395),
trillNickname(16396),
reserved(65535)
}
END
Icinga2/_Test/vSan Mib/vmw/IANA-ENTITY-MIB.mib
+163
View File
@@ -0,0 +1,163 @@
-- http://www.ietf.org/rfc/rfc6933.txt
IANA-ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC 2579
;
ianaEntityMIB MODULE-IDENTITY
LAST-UPDATED "201304050000Z" -- April 5, 2013
ORGANIZATION "IANA"
CONTACT-INFO
"Internet Assigned Numbers Authority
Postal: ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Phone: +1-310-301-5800
EMail: iana@iana.org"
DESCRIPTION
"This MIB module defines a TEXTUAL-CONVENTION that provides
an indication of the general hardware type of a particular
physical entity.
Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
The initial version of this MIB module was published in
RFC 6933; for full legal notices see the RFC itself."
REVISION "201304050000Z" -- April 5, 2013
DESCRIPTION "Initial version of this MIB as published in
RFC 6933."
::= { mib-2 216 }
-- Textual Conventions
IANAPhysicalClass ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value that provides an indication of the
general hardware type of a particular physical entity.
There are no restrictions as to the number of
entPhysicalEntries of each entPhysicalClass, which must
be instantiated by an agent.
The enumeration 'other' is applicable if the physical
entity class is known but does not match any of the
supported values.
The enumeration 'unknown' is applicable if the physical
entity class is unknown to the agent.
The enumeration 'chassis' is applicable if the physical
entity class is an overall container for networking
equipment. Any class of physical entity, except a stack,
may be contained within a chassis; a chassis may only
be contained within a stack.
The enumeration 'backplane' is applicable if the physical
entity class is some sort of device for aggregating and
forwarding networking traffic, such as a shared
backplane in a modular ethernet switch. Note that an
agent may model a backplane as a single physical entity,
which is actually implemented as multiple discrete
physical components (within a chassis or stack).
The enumeration 'container' is applicable if the
physical entity class is capable of containing one or
more removable physical entities, possibly of different
types. For example, each (empty or full) slot in a
chassis will be modeled as a container. Note that all
removable physical entities should be modeled within
a container entity, such as field-replaceable modules,
fans, or power supplies. Note that all known containers
should be modeled by the agent, including empty
containers.
The enumeration 'powerSupply' is applicable if the
physical entity class is a power-supplying component.
The enumeration 'fan' is applicable if the physical
entity class is a fan or other heat-reduction component.
The enumeration 'sensor' is applicable if the physical
entity class is some sort of sensor, such as a
temperature sensor within a router chassis.
The enumeration 'module' is applicable if the physical
entity class is some sort of self-contained sub-system.
If the enumeration 'module' is removable, then it should
be modeled within a container entity; otherwise, it
should be modeled directly within another physical
entity (e.g., a chassis or another module).
The enumeration 'port' is applicable if the physical
entity class is some sort of networking port, capable
of receiving and/or transmitting networking traffic.
The enumeration 'stack' is applicable if the physical
entity class is some sort of super-container (possibly
virtual) intended to group together multiple chassis
entities. A stack may be realized by a 'virtual' cable,
a real interconnect cable attached to multiple chassis,
or multiple interconnect cables. A stack should not be
modeled within any other physical entities, but a stack
may be contained within another stack. Only chassis
entities should be contained within a stack.
The enumeration 'cpu' is applicable if the physical
entity class is some sort of central processing unit.
The enumeration 'energyObject' is applicable if the
physical entity is some sort of energy object, i.e.,
a piece of equipment that is part of or attached to
a communications network that is monitored, controlled,
or aids in the management of another device for Energy
Management.
The enumeration 'battery' is applicable if the physical
entity class is some sort of battery."
SYNTAX INTEGER {
other(1),
unknown(2),
chassis(3),
backplane(4),
container(5), -- e.g., chassis slot or daughter-card holder
powerSupply(6),
fan(7),
sensor(8),
module(9), -- e.g., plug-in card or daughter-card
port(10),
stack(11), -- e.g., stack of multiple chassis entities
cpu(12),
energyObject(13),
battery (14)
}
END
Icinga2/_Test/vSan Mib/vmw/IANA-RTPROTO-MIB.mib
+100
View File
@@ -0,0 +1,100 @@
-- http://www.iana.org/assignments/ianaiprouteprotocol-mib/ianaiprouteprotocol-mib
IANA-RTPROTO-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaRtProtoMIB MODULE-IDENTITY
LAST-UPDATED "201208300000Z" -- August 30, 2012
ORGANIZATION "IANA"
CONTACT-INFO
" Internet Assigned Numbers Authority
Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Phone: +1 310 301 5800
EMail: iana&iana.org"
DESCRIPTION
"This MIB module defines the IANAipRouteProtocol and
IANAipMRouteProtocol textual conventions for use in MIBs
which need to identify unicast or multicast routing
mechanisms.
Any additions or changes to the contents of this MIB module
require either publication of an RFC, or Designated Expert
Review as defined in RFC 2434, Guidelines for Writing an
IANA Considerations Section in RFCs. The Designated Expert
will be selected by the IESG Area Director(s) of the Routing
Area."
REVISION "201208300000Z" -- August 30, 2012
DESCRIPTION "Added dhcp(19)."
REVISION "201107220000Z" -- July 22, 2011
DESCRIPTION "Added rpl(18) ."
REVISION "200009260000Z" -- September 26, 2000
DESCRIPTION "Original version, published in coordination
with RFC 2932."
::= { mib-2 84 }
IANAipRouteProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A mechanism for learning routes. Inclusion of values for
routing protocols is not intended to imply that those
protocols need be supported."
SYNTAX INTEGER {
other (1), -- not specified
local (2), -- local interface
netmgmt (3), -- static route
icmp (4), -- result of ICMP Redirect
-- the following are all dynamic
-- routing protocols
egp (5), -- Exterior Gateway Protocol
ggp (6), -- Gateway-Gateway Protocol
hello (7), -- FuzzBall HelloSpeak
rip (8), -- Berkeley RIP or RIP-II
isIs (9), -- Dual IS-IS
esIs (10), -- ISO 9542
ciscoIgrp (11), -- Cisco IGRP
bbnSpfIgp (12), -- BBN SPF IGP
ospf (13), -- Open Shortest Path First
bgp (14), -- Border Gateway Protocol
idpr (15), -- InterDomain Policy Routing
ciscoEigrp (16), -- Cisco EIGRP
dvmrp (17), -- DVMRP
rpl (18), -- RPL [RFC-ietf-roll-rpl-19]
dhcp (19) -- DHCP [RFC2132]
}
IANAipMRouteProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The multicast routing protocol. Inclusion of values for
multicast routing protocols is not intended to imply that
those protocols need be supported."
SYNTAX INTEGER {
other(1), -- none of the following
local(2), -- e.g., manually configured
netmgmt(3), -- set via net.mgmt protocol
dvmrp(4),
mospf(5),
pimSparseDense(6), -- PIMv1, both DM and SM
cbt(7),
pimSparseMode(8), -- PIM-SM
pimDenseMode(9), -- PIM-DM
igmpOnly(10),
bgmp(11),
msdp(12)
}
END
Icinga2/_Test/vSan Mib/vmw/IANAifType-MIB.mib
+664
View File
@@ -0,0 +1,664 @@
-- https://www.iana.org/assignments/ianaiftype-mib/ianaiftype-mib
IANAifType-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaifType MODULE-IDENTITY
LAST-UPDATED "201409240000Z" -- September 24, 2014
ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
Tel: +1 310-301-5800
E-Mail: iana&iana.org"
DESCRIPTION "This MIB module defines the IANAifType Textual
Convention, and thus the enumerated values of
the ifType object defined in MIB-II's ifTable."
REVISION "201409240000Z" -- September 24, 2014
DESCRIPTION "Registration of new IANAifType 280."
REVISION "201409190000Z" -- September 19, 2014
DESCRIPTION "Registration of new IANAifType 279."
REVISION "201407030000Z" -- July 3, 2014
DESCRIPTION "Registration of new IANAifTypes 277-278."
REVISION "201405220000Z" -- May 22, 2014
DESCRIPTION "Updated contact info."
REVISION "201205170000Z" -- May 17, 2012
DESCRIPTION "Registration of new IANAifType 272."
REVISION "201201110000Z" -- January 11, 2012
DESCRIPTION "Registration of new IANAifTypes 266-271."
REVISION "201112180000Z" -- December 18, 2011
DESCRIPTION "Registration of new IANAifTypes 263-265."
REVISION "201110260000Z" -- October 26, 2011
DESCRIPTION "Registration of new IANAifType 262."
REVISION "201109070000Z" -- September 7, 2011
DESCRIPTION "Registration of new IANAifTypes 260 and 261."
REVISION "201107220000Z" -- July 22, 2011
DESCRIPTION "Registration of new IANAifType 259."
REVISION "201106030000Z" -- June 03, 2011
DESCRIPTION "Registration of new IANAifType 258."
REVISION "201009210000Z" -- September 21, 2010
DESCRIPTION "Registration of new IANAifTypes 256 and 257."
REVISION "201007210000Z" -- July 21, 2010
DESCRIPTION "Registration of new IANAifType 255."
REVISION "201002110000Z" -- February 11, 2010
DESCRIPTION "Registration of new IANAifType 254."
REVISION "201002080000Z" -- February 08, 2010
DESCRIPTION "Registration of new IANAifTypes 252 and 253."
REVISION "200905060000Z" -- May 06, 2009
DESCRIPTION "Registration of new IANAifType 251."
REVISION "200902060000Z" -- February 06, 2009
DESCRIPTION "Registration of new IANAtunnelType 15."
REVISION "200810090000Z" -- October 09, 2008
DESCRIPTION "Registration of new IANAifType 250."
REVISION "200808120000Z" -- August 12, 2008
DESCRIPTION "Registration of new IANAifType 249."
REVISION "200807220000Z" -- July 22, 2008
DESCRIPTION "Registration of new IANAifTypes 247 and 248."
REVISION "200806240000Z" -- June 24, 2008
DESCRIPTION "Registration of new IANAifType 246."
REVISION "200805290000Z" -- May 29, 2008
DESCRIPTION "Registration of new IANAifType 245."
REVISION "200709130000Z" -- September 13, 2007
DESCRIPTION "Registration of new IANAifTypes 243 and 244."
REVISION "200705290000Z" -- May 29, 2007
DESCRIPTION "Changed the description for IANAifType 228."
REVISION "200703080000Z" -- March 08, 2007
DESCRIPTION "Registration of new IANAifType 242."
REVISION "200701230000Z" -- January 23, 2007
DESCRIPTION "Registration of new IANAifTypes 239, 240, and 241."
REVISION "200610170000Z" -- October 17, 2006
DESCRIPTION "Deprecated/Obsoleted IANAifType 230. Registration of
IANAifType 238."
REVISION "200609250000Z" -- September 25, 2006
DESCRIPTION "Changed the description for IANA ifType
184 and added new IANA ifType 237."
REVISION "200608170000Z" -- August 17, 2006
DESCRIPTION "Changed the descriptions for IANAifTypes
20 and 21."
REVISION "200608110000Z" -- August 11, 2006
DESCRIPTION "Changed the descriptions for IANAifTypes
7, 11, 62, 69, and 117."
REVISION "200607250000Z" -- July 25, 2006
DESCRIPTION "Registration of new IANA ifType 236."
REVISION "200606140000Z" -- June 14, 2006
DESCRIPTION "Registration of new IANA ifType 235."
REVISION "200603310000Z" -- March 31, 2006
DESCRIPTION "Registration of new IANA ifType 234."
REVISION "200603300000Z" -- March 30, 2006
DESCRIPTION "Registration of new IANA ifType 233."
REVISION "200512220000Z" -- December 22, 2005
DESCRIPTION "Registration of new IANA ifTypes 231 and 232."
REVISION "200510100000Z" -- October 10, 2005
DESCRIPTION "Registration of new IANA ifType 230."
REVISION "200509090000Z" -- September 09, 2005
DESCRIPTION "Registration of new IANA ifType 229."
REVISION "200505270000Z" -- May 27, 2005
DESCRIPTION "Registration of new IANA ifType 228."
REVISION "200503030000Z" -- March 3, 2005
DESCRIPTION "Added the IANAtunnelType TC and deprecated
IANAifType sixToFour (215) per RFC4087."
REVISION "200411220000Z" -- November 22, 2004
DESCRIPTION "Registration of new IANA ifType 227 per RFC4631."
REVISION "200406170000Z" -- June 17, 2004
DESCRIPTION "Registration of new IANA ifType 226."
REVISION "200405120000Z" -- May 12, 2004
DESCRIPTION "Added description for IANAifType 6, and
changed the descriptions for IANAifTypes
180, 181, and 182."
REVISION "200405070000Z" -- May 7, 2004
DESCRIPTION "Registration of new IANAifType 225."
REVISION "200308250000Z" -- Aug 25, 2003
DESCRIPTION "Deprecated IANAifTypes 7 and 11. Obsoleted
IANAifTypes 62, 69, and 117. ethernetCsmacd (6)
should be used instead of these values"
REVISION "200308180000Z" -- Aug 18, 2003
DESCRIPTION "Registration of new IANAifType
224."
REVISION "200308070000Z" -- Aug 7, 2003
DESCRIPTION "Registration of new IANAifTypes
222 and 223."
REVISION "200303180000Z" -- Mar 18, 2003
DESCRIPTION "Registration of new IANAifType
221."
REVISION "200301130000Z" -- Jan 13, 2003
DESCRIPTION "Registration of new IANAifType
220."
REVISION "200210170000Z" -- Oct 17, 2002
DESCRIPTION "Registration of new IANAifType
219."
REVISION "200207160000Z" -- Jul 16, 2002
DESCRIPTION "Registration of new IANAifTypes
217 and 218."
REVISION "200207100000Z" -- Jul 10, 2002
DESCRIPTION "Registration of new IANAifTypes
215 and 216."
REVISION "200206190000Z" -- Jun 19, 2002
DESCRIPTION "Registration of new IANAifType
214."
REVISION "200201040000Z" -- Jan 4, 2002
DESCRIPTION "Registration of new IANAifTypes
211, 212 and 213."
REVISION "200112200000Z" -- Dec 20, 2001
DESCRIPTION "Registration of new IANAifTypes
209 and 210."
REVISION "200111150000Z" -- Nov 15, 2001
DESCRIPTION "Registration of new IANAifTypes
207 and 208."
REVISION "200111060000Z" -- Nov 6, 2001
DESCRIPTION "Registration of new IANAifType
206."
REVISION "200111020000Z" -- Nov 2, 2001
DESCRIPTION "Registration of new IANAifType
205."
REVISION "200110160000Z" -- Oct 16, 2001
DESCRIPTION "Registration of new IANAifTypes
199, 200, 201, 202, 203, and 204."
REVISION "200109190000Z" -- Sept 19, 2001
DESCRIPTION "Registration of new IANAifType
198."
REVISION "200105110000Z" -- May 11, 2001
DESCRIPTION "Registration of new IANAifType
197."
REVISION "200101120000Z" -- Jan 12, 2001
DESCRIPTION "Registration of new IANAifTypes
195 and 196."
REVISION "200012190000Z" -- Dec 19, 2000
DESCRIPTION "Registration of new IANAifTypes
193 and 194."
REVISION "200012070000Z" -- Dec 07, 2000
DESCRIPTION "Registration of new IANAifTypes
191 and 192."
REVISION "200012040000Z" -- Dec 04, 2000
DESCRIPTION "Registration of new IANAifType
190."
REVISION "200010170000Z" -- Oct 17, 2000
DESCRIPTION "Registration of new IANAifTypes
188 and 189."
REVISION "200010020000Z" -- Oct 02, 2000
DESCRIPTION "Registration of new IANAifType 187."
REVISION "200009010000Z" -- Sept 01, 2000
DESCRIPTION "Registration of new IANAifTypes
184, 185, and 186."
REVISION "200008240000Z" -- Aug 24, 2000
DESCRIPTION "Registration of new IANAifType 183."
REVISION "200008230000Z" -- Aug 23, 2000
DESCRIPTION "Registration of new IANAifTypes
174-182."
REVISION "200008220000Z" -- Aug 22, 2000
DESCRIPTION "Registration of new IANAifTypes 170,
171, 172 and 173."
REVISION "200004250000Z" -- Apr 25, 2000
DESCRIPTION "Registration of new IANAifTypes 168 and 169."
REVISION "200003060000Z" -- Mar 6, 2000
DESCRIPTION "Fixed a missing semi-colon in the IMPORT.
Also cleaned up the REVISION log a bit.
It is not complete, but from now on it will
be maintained and kept up to date with each
change to this MIB module."
REVISION "199910081430Z" -- Oct 08, 1999
DESCRIPTION "Include new name assignments up to cnr(85).
This is the first version available via the WWW
at: ftp://ftp.isi.edu/mib/ianaiftype.mib"
REVISION "199401310000Z" -- Jan 31, 1994
DESCRIPTION "Initial version of this MIB as published in
RFC 1573."
::= { mib-2 30 }
IANAifType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type is used as the syntax of the ifType
object in the (updated) definition of MIB-II's
ifTable.
The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments. (The
latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via
email (iana&iana.org).
The relationship between the assignment of ifType
values and of OIDs to particular media-specific MIBs
is solely the purview of IANA and is subject to change
without notice. Quite often, a media-specific MIB's
OID-subtree assignment within MIB-II's 'transmission'
subtree will be the same as its ifType value.
However, in some circumstances this will not be the
case, and implementors must not pre-assume any
specific relationship between ifType values and
transmission subtree OIDs."
SYNTAX INTEGER {
other(1), -- none of the following
regular1822(2),
hdh1822(3),
ddnX25(4),
rfc877x25(5),
ethernetCsmacd(6), -- for all ethernet-like interfaces,
-- regardless of speed, as per RFC3635
iso88023Csmacd(7), -- Deprecated via RFC3635
-- ethernetCsmacd (6) should be used instead
iso88024TokenBus(8),
iso88025TokenRing(9),
iso88026Man(10),
starLan(11), -- Deprecated via RFC3635
-- ethernetCsmacd (6) should be used instead
proteon10Mbit(12),
proteon80Mbit(13),
hyperchannel(14),
fddi(15),
lapb(16),
sdlc(17),
ds1(18), -- DS1-MIB
e1(19), -- Obsolete see DS1-MIB
basicISDN(20), -- no longer used
-- see also RFC2127
primaryISDN(21), -- no longer used
-- see also RFC2127
propPointToPointSerial(22), -- proprietary serial
ppp(23),
softwareLoopback(24),
eon(25), -- CLNP over IP
ethernet3Mbit(26),
nsip(27), -- XNS over IP
slip(28), -- generic SLIP
ultra(29), -- ULTRA technologies
ds3(30), -- DS3-MIB
sip(31), -- SMDS, coffee
frameRelay(32), -- DTE only.
rs232(33),
para(34), -- parallel-port
arcnet(35), -- arcnet
arcnetPlus(36), -- arcnet plus
atm(37), -- ATM cells
miox25(38),
sonet(39), -- SONET or SDH
x25ple(40),
iso88022llc(41),
localTalk(42),
smdsDxi(43),
frameRelayService(44), -- FRNETSERV-MIB
v35(45),
hssi(46),
hippi(47),
modem(48), -- Generic modem
aal5(49), -- AAL5 over ATM
sonetPath(50),
sonetVT(51),
smdsIcip(52), -- SMDS InterCarrier Interface
propVirtual(53), -- proprietary virtual/internal
propMultiplexor(54),-- proprietary multiplexing
ieee80212(55), -- 100BaseVG
fibreChannel(56), -- Fibre Channel
hippiInterface(57), -- HIPPI interfaces
frameRelayInterconnect(58), -- Obsolete, use either
-- frameRelay(32) or
-- frameRelayService(44).
aflane8023(59), -- ATM Emulated LAN for 802.3
aflane8025(60), -- ATM Emulated LAN for 802.5
cctEmul(61), -- ATM Emulated circuit
fastEther(62), -- Obsoleted via RFC3635
-- ethernetCsmacd (6) should be used instead
isdn(63), -- ISDN and X.25
v11(64), -- CCITT V.11/X.21
v36(65), -- CCITT V.36
g703at64k(66), -- CCITT G703 at 64Kbps
g703at2mb(67), -- Obsolete see DS1-MIB
qllc(68), -- SNA QLLC
fastEtherFX(69), -- Obsoleted via RFC3635
-- ethernetCsmacd (6) should be used instead
channel(70), -- channel
ieee80211(71), -- radio spread spectrum
ibm370parChan(72), -- IBM System 360/370 OEMI Channel
escon(73), -- IBM Enterprise Systems Connection
dlsw(74), -- Data Link Switching
isdns(75), -- ISDN S/T interface
isdnu(76), -- ISDN U interface
lapd(77), -- Link Access Protocol D
ipSwitch(78), -- IP Switching Objects
rsrb(79), -- Remote Source Route Bridging
atmLogical(80), -- ATM Logical Port
ds0(81), -- Digital Signal Level 0
ds0Bundle(82), -- group of ds0s on the same ds1
bsc(83), -- Bisynchronous Protocol
async(84), -- Asynchronous Protocol
cnr(85), -- Combat Net Radio
iso88025Dtr(86), -- ISO 802.5r DTR
eplrs(87), -- Ext Pos Loc Report Sys
arap(88), -- Appletalk Remote Access Protocol
propCnls(89), -- Proprietary Connectionless Protocol
hostPad(90), -- CCITT-ITU X.29 PAD Protocol
termPad(91), -- CCITT-ITU X.3 PAD Facility
frameRelayMPI(92), -- Multiproto Interconnect over FR
x213(93), -- CCITT-ITU X213
adsl(94), -- Asymmetric Digital Subscriber Loop
radsl(95), -- Rate-Adapt. Digital Subscriber Loop
sdsl(96), -- Symmetric Digital Subscriber Loop
vdsl(97), -- Very H-Speed Digital Subscrib. Loop
iso88025CRFPInt(98), -- ISO 802.5 CRFP
myrinet(99), -- Myricom Myrinet
voiceEM(100), -- voice recEive and transMit
voiceFXO(101), -- voice Foreign Exchange Office
voiceFXS(102), -- voice Foreign Exchange Station
voiceEncap(103), -- voice encapsulation
voiceOverIp(104), -- voice over IP encapsulation
atmDxi(105), -- ATM DXI
atmFuni(106), -- ATM FUNI
atmIma (107), -- ATM IMA
pppMultilinkBundle(108), -- PPP Multilink Bundle
ipOverCdlc (109), -- IBM ipOverCdlc
ipOverClaw (110), -- IBM Common Link Access to Workstn
stackToStack (111), -- IBM stackToStack
virtualIpAddress (112), -- IBM VIPA
mpc (113), -- IBM multi-protocol channel support
ipOverAtm (114), -- IBM ipOverAtm
iso88025Fiber (115), -- ISO 802.5j Fiber Token Ring
tdlc (116), -- IBM twinaxial data link control
gigabitEthernet (117), -- Obsoleted via RFC3635
-- ethernetCsmacd (6) should be used instead
hdlc (118), -- HDLC
lapf (119), -- LAP F
v37 (120), -- V.37
x25mlp (121), -- Multi-Link Protocol
x25huntGroup (122), -- X25 Hunt Group
transpHdlc (123), -- Transp HDLC
interleave (124), -- Interleave channel
fast (125), -- Fast channel
ip (126), -- IP (for APPN HPR in IP networks)
docsCableMaclayer (127), -- CATV Mac Layer
docsCableDownstream (128), -- CATV Downstream interface
docsCableUpstream (129), -- CATV Upstream interface
a12MppSwitch (130), -- Avalon Parallel Processor
tunnel (131), -- Encapsulation interface
coffee (132), -- coffee pot
ces (133), -- Circuit Emulation Service
atmSubInterface (134), -- ATM Sub Interface
l2vlan (135), -- Layer 2 Virtual LAN using 802.1Q
l3ipvlan (136), -- Layer 3 Virtual LAN using IP
l3ipxvlan (137), -- Layer 3 Virtual LAN using IPX
digitalPowerline (138), -- IP over Power Lines
mediaMailOverIp (139), -- Multimedia Mail over IP
dtm (140), -- Dynamic syncronous Transfer Mode
dcn (141), -- Data Communications Network
ipForward (142), -- IP Forwarding Interface
msdsl (143), -- Multi-rate Symmetric DSL
ieee1394 (144), -- IEEE1394 High Performance Serial Bus
if-gsn (145), -- HIPPI-6400
dvbRccMacLayer (146), -- DVB-RCC MAC Layer
dvbRccDownstream (147), -- DVB-RCC Downstream Channel
dvbRccUpstream (148), -- DVB-RCC Upstream Channel
atmVirtual (149), -- ATM Virtual Interface
mplsTunnel (150), -- MPLS Tunnel Virtual Interface
srp (151), -- Spatial Reuse Protocol
voiceOverAtm (152), -- Voice Over ATM
voiceOverFrameRelay (153), -- Voice Over Frame Relay
idsl (154), -- Digital Subscriber Loop over ISDN
compositeLink (155), -- Avici Composite Link Interface
ss7SigLink (156), -- SS7 Signaling Link
propWirelessP2P (157), -- Prop. P2P wireless interface
frForward (158), -- Frame Forward Interface
rfc1483 (159), -- Multiprotocol over ATM AAL5
usb (160), -- USB Interface
ieee8023adLag (161), -- IEEE 802.3ad Link Aggregate
bgppolicyaccounting (162), -- BGP Policy Accounting
frf16MfrBundle (163), -- FRF .16 Multilink Frame Relay
h323Gatekeeper (164), -- H323 Gatekeeper
h323Proxy (165), -- H323 Voice and Video Proxy
mpls (166), -- MPLS
mfSigLink (167), -- Multi-frequency signaling link
hdsl2 (168), -- High Bit-Rate DSL - 2nd generation
shdsl (169), -- Multirate HDSL2
ds1FDL (170), -- Facility Data Link 4Kbps on a DS1
pos (171), -- Packet over SONET/SDH Interface
dvbAsiIn (172), -- DVB-ASI Input
dvbAsiOut (173), -- DVB-ASI Output
plc (174), -- Power Line Communtications
nfas (175), -- Non Facility Associated Signaling
tr008 (176), -- TR008
gr303RDT (177), -- Remote Digital Terminal
gr303IDT (178), -- Integrated Digital Terminal
isup (179), -- ISUP
propDocsWirelessMaclayer (180), -- Cisco proprietary Maclayer
propDocsWirelessDownstream (181), -- Cisco proprietary Downstream
propDocsWirelessUpstream (182), -- Cisco proprietary Upstream
hiperlan2 (183), -- HIPERLAN Type 2 Radio Interface
propBWAp2Mp (184), -- PropBroadbandWirelessAccesspt2multipt
-- use of this iftype for IEEE 802.16 WMAN
-- interfaces as per IEEE Std 802.16f is
-- deprecated and ifType 237 should be used instead.
sonetOverheadChannel (185), -- SONET Overhead Channel
digitalWrapperOverheadChannel (186), -- Digital Wrapper
aal2 (187), -- ATM adaptation layer 2
radioMAC (188), -- MAC layer over radio links
atmRadio (189), -- ATM over radio links
imt (190), -- Inter Machine Trunks
mvl (191), -- Multiple Virtual Lines DSL
reachDSL (192), -- Long Reach DSL
frDlciEndPt (193), -- Frame Relay DLCI End Point
atmVciEndPt (194), -- ATM VCI End Point
opticalChannel (195), -- Optical Channel
opticalTransport (196), -- Optical Transport
propAtm (197), -- Proprietary ATM
voiceOverCable (198), -- Voice Over Cable Interface
infiniband (199), -- Infiniband
teLink (200), -- TE Link
q2931 (201), -- Q.2931
virtualTg (202), -- Virtual Trunk Group
sipTg (203), -- SIP Trunk Group
sipSig (204), -- SIP Signaling
docsCableUpstreamChannel (205), -- CATV Upstream Channel
econet (206), -- Acorn Econet
pon155 (207), -- FSAN 155Mb Symetrical PON interface
pon622 (208), -- FSAN622Mb Symetrical PON interface
bridge (209), -- Transparent bridge interface
linegroup (210), -- Interface common to multiple lines
voiceEMFGD (211), -- voice E&M Feature Group D
voiceFGDEANA (212), -- voice FGD Exchange Access North American
voiceDID (213), -- voice Direct Inward Dialing
mpegTransport (214), -- MPEG transport interface
sixToFour (215), -- 6to4 interface (DEPRECATED)
gtp (216), -- GTP (GPRS Tunneling Protocol)
pdnEtherLoop1 (217), -- Paradyne EtherLoop 1
pdnEtherLoop2 (218), -- Paradyne EtherLoop 2
opticalChannelGroup (219), -- Optical Channel Group
homepna (220), -- HomePNA ITU-T G.989
gfp (221), -- Generic Framing Procedure (GFP)
ciscoISLvlan (222), -- Layer 2 Virtual LAN using Cisco ISL
actelisMetaLOOP (223), -- Acteleis proprietary MetaLOOP High Speed Link
fcipLink (224), -- FCIP Link
rpr (225), -- Resilient Packet Ring Interface Type
qam (226), -- RF Qam Interface
lmp (227), -- Link Management Protocol
cblVectaStar (228), -- Cambridge Broadband Networks Limited VectaStar
docsCableMCmtsDownstream (229), -- CATV Modular CMTS Downstream Interface
adsl2 (230), -- Asymmetric Digital Subscriber Loop Version 2
-- (DEPRECATED/OBSOLETED - please use adsl2plus 238 instead)
macSecControlledIF (231), -- MACSecControlled
macSecUncontrolledIF (232), -- MACSecUncontrolled
aviciOpticalEther (233), -- Avici Optical Ethernet Aggregate
atmbond (234), -- atmbond
voiceFGDOS (235), -- voice FGD Operator Services
mocaVersion1 (236), -- MultiMedia over Coax Alliance (MoCA) Interface
-- as documented in information provided privately to IANA
ieee80216WMAN (237), -- IEEE 802.16 WMAN interface
adsl2plus (238), -- Asymmetric Digital Subscriber Loop Version 2,
-- Version 2 Plus and all variants
dvbRcsMacLayer (239), -- DVB-RCS MAC Layer
dvbTdm (240), -- DVB Satellite TDM
dvbRcsTdma (241), -- DVB-RCS TDMA
x86Laps (242), -- LAPS based on ITU-T X.86/Y.1323
wwanPP (243), -- 3GPP WWAN
wwanPP2 (244), -- 3GPP2 WWAN
voiceEBS (245), -- voice P-phone EBS physical interface
ifPwType (246), -- Pseudowire interface type
ilan (247), -- Internal LAN on a bridge per IEEE 802.1ap
pip (248), -- Provider Instance Port on a bridge per IEEE 802.1ah PBB
aluELP (249), -- Alcatel-Lucent Ethernet Link Protection
gpon (250), -- Gigabit-capable passive optical networks (G-PON) as per ITU-T G.948
vdsl2 (251), -- Very high speed digital subscriber line Version 2 (as per ITU-T Recommendation G.993.2)
capwapDot11Profile (252), -- WLAN Profile Interface
capwapDot11Bss (253), -- WLAN BSS Interface
capwapWtpVirtualRadio (254), -- WTP Virtual Radio Interface
bits (255), -- bitsport
docsCableUpstreamRfPort (256), -- DOCSIS CATV Upstream RF Port
cableDownstreamRfPort (257), -- CATV downstream RF port
vmwareVirtualNic (258), -- VMware Virtual Network Interface
ieee802154 (259), -- IEEE 802.15.4 WPAN interface
otnOdu (260), -- OTN Optical Data Unit
otnOtu (261), -- OTN Optical channel Transport Unit
ifVfiType (262), -- VPLS Forwarding Instance Interface Type
g9981 (263), -- G.998.1 bonded interface
g9982 (264), -- G.998.2 bonded interface
g9983 (265), -- G.998.3 bonded interface
aluEpon (266), -- Ethernet Passive Optical Networks (E-PON)
aluEponOnu (267), -- EPON Optical Network Unit
aluEponPhysicalUni (268), -- EPON physical User to Network interface
aluEponLogicalLink (269), -- The emulation of a point-to-point link over the EPON layer
aluGponOnu (270), -- GPON Optical Network Unit
aluGponPhysicalUni (271), -- GPON physical User to Network interface
vmwareNicTeam (272), -- VMware NIC Team
docsOfdmDownstream (277), -- CATV Downstream OFDM interface
docsOfdmaUpstream (278), -- CATV Upstream OFDMA interface
gfast (279), -- G.fast port
sdci (280) -- SDCI (IO-Link)
}
IANAtunnelType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The encapsulation method used by a tunnel. The value
direct indicates that a packet is encapsulated
directly within a normal IP header, with no
intermediate header, and unicast to the remote tunnel
endpoint (e.g., an RFC 2003 IP-in-IP tunnel, or an RFC
1933 IPv6-in-IPv4 tunnel). The value minimal indicates
that a Minimal Forwarding Header (RFC 2004) is
inserted between the outer header and the payload
packet. The value UDP indicates that the payload
packet is encapsulated within a normal UDP packet
(e.g., RFC 1234).
The values sixToFour, sixOverFour, and isatap
indicates that an IPv6 packet is encapsulated directly
within an IPv4 header, with no intermediate header,
and unicast to the destination determined by the 6to4,
6over4, or ISATAP protocol.
The remaining protocol-specific values indicate that a
header of the protocol of that name is inserted
between the outer header and the payload header.
The assignment policy for IANAtunnelType values is
identical to the policy for assigning IANAifType
values."
SYNTAX INTEGER {
other(1), -- none of the following
direct(2), -- no intermediate header
gre(3), -- GRE encapsulation
minimal(4), -- Minimal encapsulation
l2tp(5), -- L2TP encapsulation
pptp(6), -- PPTP encapsulation
l2f(7), -- L2F encapsulation
udp(8), -- UDP encapsulation
atmp(9), -- ATMP encapsulation
msdp(10), -- MSDP encapsulation
sixToFour(11), -- 6to4 encapsulation
sixOverFour(12), -- 6over4 encapsulation
isatap(13), -- ISATAP encapsulation
teredo(14), -- Teredo encapsulation
ipHttps(15) -- IPHTTPS
}
END
Icinga2/_Test/vSan Mib/vmw/IEEE8021-BRIDGE-MIB.mib
+2038
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/IEEE8021-Q-BRIDGE-MIB.mib
+2332
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/IEEE8021-TC-MIB.mib
+381
View File
@@ -0,0 +1,381 @@
IEEE8021-TC-MIB DEFINITIONS ::= BEGIN
-- =============================================================
-- TEXTUAL-CONVENTIONs MIB for IEEE 802.1
-- =============================================================
IMPORTS
MODULE-IDENTITY, Unsigned32, org
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- RFC 2579
ieee8021TcMib MODULE-IDENTITY
LAST-UPDATED "200810150000Z" -- October 15, 2008
ORGANIZATION "IEEE 802.1 Working Group"
CONTACT-INFO
" WG-URL: http://grouper.ieee.org/groups/802/1/index.html
WG-EMail: stds-802-1@ieee.org
Contact: David Levi
Postal: 4655 GREAT AMERICA PARKWAY
SANTA CLARA, CALIFORNIA
95054
USA
Tel: +1-408-495-5138
E-mail: dlevi@nortel.com"
DESCRIPTION
"Textual conventions used throughout the various IEEE 802.1 MIB
modules.
Unless otherwise indicated, the references in this MIB
module are to IEEE 802.1Q-2005 as amended by IEEE 802.1ad,
IEEE 802.1ak, IEEE 802.1ag and IEEE 802.1ah.
Copyright (C) IEEE.
This version of this MIB module is part of IEEE802.1Q;
see the draft itself for full legal notices."
REVISION "200810150000Z" -- October 15, 2008
DESCRIPTION
"Initial version."
::= { org ieee(111) standards-association-numbers-series-standards(2)
lan-man-stds(802) ieee802dot1(1) 1 1 }
ieee802dot1mibs OBJECT IDENTIFIER
::= { org ieee(111) standards-association-numbers-series-standards(2)
lan-man-stds(802) ieee802dot1(1) 1 }
-- =============================================================
-- Textual Conventions
-- =============================================================
IEEE8021PbbComponentIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The component identifier is used to distinguish between the
multiple virtual bridge instances within a PB or PBB. Each
virtual bridge instance is called a component. In simple
situations where there is only a single component the default
value is 1. The component is identified by a component
identifier unique within the BEB and by a MAC address unique
within the PBBN. Each component is associated with a Backbone
Edge Bridge (BEB) Configuration managed object."
REFERENCE "12.3 l)"
SYNTAX Unsigned32 (1..4294967295)
IEEE8021PbbComponentIdentifierOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The component identifier is used to distinguish between the
multiple virtual bridge instances within a PB or PBB. In simple
situations where there is only a single component the default
value is 1. The component is identified by a component
identifier unique within the BEB and by a MAC address unique
within the PBBN. Each component is associated with a Backbone
Edge Bridge (BEB) Configuration managed object.
The special value '0' means 'no component identifier'. When
this TC is used as the SYNTAX of an object, that object must
specify the its exact meaning for this value."
REFERENCE "12.3 l)"
SYNTAX Unsigned32 (0 | 1..4294967295)
IEEE8021PbbServiceIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The service instance identifier is used at the Customer
Backbone Port of a PBB to distinguish a service instance
(Local-SID). If the Local-SID field is supported, it is
used to perform a bidirectional 1:1 mapping between the
Backbone I-SID and the Local-SID. If the Local-SID field
is not supported, the Local-SID value is the same as the
Backbone I-SID value."
REFERENCE "12.16.3, 12.16.5"
SYNTAX Unsigned32 (256..16777214)
IEEE8021PbbServiceIdentifierOrUnassigned ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The service instance identifier is used at the Customer
Backbone Port of a PBB to distinguish a service instance
(Local-SID). If the Local-SID field is supported, it is
used to perform a bidirectional 1:1 mapping between the
Backbone I-SID and the Local-SID. If the Local-SID field
is not supported, the Local-SID value is the same as the
Backbone I-SID value.
The special value of 1 indicates an unassigned I-SID."
REFERENCE "12.16.3, 12.16.5"
SYNTAX Unsigned32 (1|256..16777214)
IEEE8021PbbIngressEgress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A 2 bit selector which determines if frames on this VIP may
ingress to the PBBN but not egress the PBBN, egress to the
PBBN but not ingress the PBBN, or both ingress and egress
the PBBN."
REFERENCE "12.16.3, 12.16.5, 12.16.6"
SYNTAX BITS {
ingress(0),
egress(1)
}
IEEE8021PriorityCodePoint ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Bridge ports may encode or decode the PCP value of the
frames that traverse the port. This textual convention
names the possible encoding and decoding schemes that
the port may use. The priority and drop_eligible
parameters are encoded in the Priority Code Point (PCP)
field of the VLAN tag using the Priority Code Point
Encoding Table for the Port, and they are decoded from
the PCP using the Priority Code Point Decoding Table."
REFERENCE "12.6.2.6"
SYNTAX INTEGER {
codePoint8p0d(1),
codePoint7p1d(2),
codePoint6p2d(3),
codePoint5p3d(4)
}
IEEE8021BridgePortNumber ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a bridge port, as
specified in 17.3.2.2 of IEEE 802.1ap.
This value is used within the spanning tree
protocol to identify this port to neighbor bridges."
REFERENCE "17.3.2.2"
SYNTAX Unsigned32 (1..65535)
IEEE8021BridgePortNumberOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a bridge port, as
specified in 17.3.2.2 of IEEE 802.1ap. The value 0
means no port number, and this must be clarified in the
DESCRIPTION clause of any object defined using this
TEXTUAL-CONVENTION."
REFERENCE "17.3.2.2"
SYNTAX Unsigned32 (0..65535)
IEEE8021BridgePortType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A port type. The possible port types are:
customerVlanPort(2) - Indicates a port is a C-tag
aware port of an enterprise VLAN aware bridge.
providerNetworkPort(3) - Indicates a port is an S-tag
aware port of a Provider Bridge or Backbone Edge
Bridge used for connections within a PBN or PBBN.
customerNetworkPort(4) - Indicates a port is an S-tag
aware port of a Provider Bridge or Backbone Edge
Bridge used for connections to the exterior of a
PBN or PBBN.
customerEdgePort(5) - Indicates a port is a C-tag
aware port of a Provider Bridge used for connections
to the exterior of a PBN or PBBN.
customerBackbonePort(6) - Indicates a port is a I-tag
aware port of a Backbone Edge Bridge's B-component.
virtualInstancePort(7) - Indicates a port is a virtual
S-tag aware port within a Backbone Edge Bridge's
I-component which is responsible for handling
S-tagged traffic for a specific backbone service
instance.
dBridgePort(8) - Indicates a port is a VLAN-unaware
member of an 802.1D bridge."
REFERENCE "12.16.1.1.3 h4), 12.16.2.1/2,
12.13.1.1, 12.13.1.2, 12.15.2.1, 12.15.2.2"
SYNTAX INTEGER {
none(1),
customerVlanPort(2),
providerNetworkPort(3),
customerNetworkPort(4),
customerEdgePort(5),
customerBackbonePort(6),
virtualInstancePort(7),
dBridgePort(8)
}
IEEE8021VlanIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A value used to index per-VLAN tables: values of 0 and
4095 are not permitted. If the value is between 1 and
4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with
global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095,
then it represents a VLAN with scope local to the
particular agent, i.e., one without a global VLAN-ID
assigned to it. Such VLANs are outside the scope of
IEEE 802.1Q, but it is convenient to be able to manage them
in the same way using this MIB."
REFERENCE "9.6"
SYNTAX Unsigned32 (1..4094|4096..4294967295)
IEEE8021VlanIndexOrWildcard ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A value used to index per-VLAN tables. The value 0 is not
permitted, while the value 4095 represents a 'wildcard'
value. An object whose SYNTAX is IEEE8021VlanIndexOrWildcard
must specify in its DESCRIPTION the specific meaning of the
wildcard value. If the value is between 1 and
4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with
global scope within a given bridged domain (see VlanId
textual convention). If the value is greater than 4095,
then it represents a VLAN with scope local to the
particular agent, i.e., one without a global VLAN-ID
assigned to it. Such VLANs are outside the scope of
IEEE 802.1Q, but it is convenient to be able to manage them
in the same way using this MIB."
REFERENCE "9.6"
SYNTAX Unsigned32 (1..4294967295)
IEEE8021MstIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"In an MSTP Bridge, an MSTID, i.e., a value used to identify
a spanning tree (or MST) instance."
SYNTAX Unsigned32 (1..4094)
IEEE8021ServiceSelectorType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a type (and thereby the format)
of a IEEE8021ServiceSelectorValue. The value can be one of
the following:
ieeeReserved(0) Reserved for definition by IEEE 802.1
recommend to not use zero unless
absolutely needed.
vlanId(1) 12-Bit identifier as described in IEEE802.1Q.
isid(2) 20-Bit identifier as described in IEEE802.1ah.
ieeeReserved(xx) Reserved for definition by IEEE 802.1
xx values can be [3..7].
To support future extensions, the IEEE8021ServiceSelectorType
textual convention SHOULD NOT be sub-typed in object type
definitions. It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
Implementations MUST ensure that IEEE8021ServiceSelectorType
objects and any dependent objects (e.g.,
IEEE8021ServiceSelectorValue objects) are consistent. An
inconsistentValue error MUST be generated if an attempt to
change an IEEE8021ServiceSelectorType object would, for
example, lead to an undefined IEEE8021ServiceSelectorValue value."
SYNTAX INTEGER {
vlanId(1),
isid(2)
}
IEEE8021ServiceSelectorValueOrNone ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a generic MAC service,
or none. Examples of service selectors are a VLAN-ID
(IEEE 802.1Q) and an I-SID (IEEE 802.1ah).
An IEEE8021ServiceSelectorValueOrNone value is always
interpreted within the context of an
IEEE8021ServiceSelectorType value. Every usage of the
IEEE8021ServiceSelectorValueOrNone textual convention is
required to specify the IEEE8021ServiceSelectorType object
that provides the context. It is suggested that the
IEEE8021ServiceSelectorType object be logically registered
before the object(s) that use the
IEEE8021ServiceSelectorValueOrNone textual convention, if
they appear in the same logical row.
The value of an IEEE8021ServiceSelectorValueOrNone object
must always be consistent with the value of the associated
IEEE8021ServiceSelectorType object. Attempts to set an
IEEE8021ServiceSelectorValueOrNone object to a value
inconsistent with the associated
IEEE8021ServiceSelectorType must fail with an
inconsistentValue error.
The special value of zero is used to indicate that no
service selector is present or used. This can be used in
any situation where an object or a table entry MUST either
refer to a specific service, or not make a selection.
Note that a MIB object that is defined using this
TEXTUAL-CONVENTION SHOULD clarify the meaning of
'no service' (i.e., the special value 0), as well as the
maximum value (i.e., 4094, for a VLAN ID)."
SYNTAX Unsigned32 (0 | 1..4294967295)
IEEE8021ServiceSelectorValue ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer that uniquely identifies a generic MAC service.
Examples of service selectors are a VLAN-ID (IEEE 802.1Q)
and an I-SID (IEEE 802.1ah).
An IEEE8021ServiceSelectorValue value is always interpreted
within the context of an IEEE8021ServiceSelectorType value.
Every usage of the IEEE8021ServiceSelectorValue textual
convention is required to specify the
IEEE8021ServiceSelectorType object that provides the context.
It is suggested that the IEEE8021ServiceSelectorType object
be logically registered before the object(s) that use the
IEEE8021ServiceSelectorValue textual convention, if they
appear in the same logical row.
The value of an IEEE8021ServiceSelectorValue object must
always be consistent with the value of the associated
IEEE8021ServiceSelectorType object. Attempts to set an
IEEE8021ServiceSelectorValue object to a value inconsistent
with the associated IEEE8021ServiceSelectorType must fail
with an inconsistentValue error.
Note that a MIB object that is defined using this
TEXTUAL-CONVENTION SHOULD clarify the
maximum value (i.e., 4094, for a VLAN ID)."
SYNTAX Unsigned32 (1..4294967295)
IEEE8021PortAcceptableFrameTypes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Acceptable frame types on a port."
REFERENCE "12.10.1.3, 12.13.3.3, 12.13.3.4"
SYNTAX INTEGER {
admitAll(1),
admitUntaggedAndPriority(2),
admitTagged(3)
}
IEEE8021PriorityValue ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An 802.1Q user priority value."
REFERENCE "12.13.3.3"
SYNTAX Unsigned32 (0..7)
END
Icinga2/_Test/vSan Mib/vmw/IEEE8023-LAG-MIB.mib
+1379
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/IF-MIB.mib
+1832
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/INET-ADDRESS-MIB.mib
+402
View File
@@ -0,0 +1,402 @@
INET-ADDRESS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
inetAddressMIB MODULE-IDENTITY
LAST-UPDATED "200502040000Z"
ORGANIZATION
"IETF Operations and Management Area"
CONTACT-INFO
"Juergen Schoenwaelder (Editor)
International University Bremen
P.O. Box 750 561
28725 Bremen, Germany
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Send comments to <ietfmibs@ops.ietf.org>."
DESCRIPTION
"This MIB module defines textual conventions for
representing Internet addresses. An Internet
address can be an IPv4 address, an IPv6 address,
or a DNS domain name. This module also defines
textual conventions for Internet port numbers,
autonomous system numbers, and the length of an
Internet address prefix.
Copyright (C) The Internet Society (2005). This version
of this MIB module is part of RFC 4001, see the RFC
itself for full legal notices."
REVISION "200502040000Z"
DESCRIPTION
"Third version, published as RFC 4001. This revision
introduces the InetZoneIndex, InetScopeType, and
InetVersion textual conventions."
REVISION "200205090000Z"
DESCRIPTION
"Second version, published as RFC 3291. This
revision contains several clarifications and
introduces several new textual conventions:
InetAddressPrefixLength, InetPortNumber,
InetAutonomousSystemNumber, InetAddressIPv4z,
and InetAddressIPv6z."
REVISION "200006080000Z"
DESCRIPTION
"Initial version, published as RFC 2851."
::= { mib-2 76 }
InetAddressType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a type of Internet address.
unknown(0) An unknown address type. This value MUST
be used if the value of the corresponding
InetAddress object is a zero-length string.
It may also be used to indicate an IP address
that is not in one of the formats defined
below.
ipv4(1) An IPv4 address as defined by the
InetAddressIPv4 textual convention.
ipv6(2) An IPv6 address as defined by the
InetAddressIPv6 textual convention.
ipv4z(3) A non-global IPv4 address including a zone
index as defined by the InetAddressIPv4z
textual convention.
ipv6z(4) A non-global IPv6 address including a zone
index as defined by the InetAddressIPv6z
textual convention.
dns(16) A DNS domain name as defined by the
InetAddressDNS textual convention.
Each definition of a concrete InetAddressType value must be
accompanied by a definition of a textual convention for use
with that InetAddressType.
To support future extensions, the InetAddressType textual
convention SHOULD NOT be sub-typed in object type definitions.
It MAY be sub-typed in compliance statements in order to
require only a subset of these address types for a compliant
implementation.
Implementations must ensure that InetAddressType objects
and any dependent objects (e.g., InetAddress objects) are
consistent. An inconsistentValue error must be generated
if an attempt to change an InetAddressType object would,
for example, lead to an undefined InetAddress value. In
particular, InetAddressType/InetAddress pairs must be
changed together if the address type changes (e.g., from
ipv6(2) to ipv4(1))."
SYNTAX INTEGER {
unknown(0),
ipv4(1),
ipv6(2),
ipv4z(3),
ipv6z(4),
dns(16)
}
InetAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a generic Internet address.
An InetAddress value is always interpreted within the context
of an InetAddressType value. Every usage of the InetAddress
textual convention is required to specify the InetAddressType
object that provides the context. It is suggested that the
InetAddressType object be logically registered before the
object(s) that use the InetAddress textual convention, if
they appear in the same logical row.
The value of an InetAddress object must always be
consistent with the value of the associated InetAddressType
object. Attempts to set an InetAddress object to a value
inconsistent with the associated InetAddressType
must fail with an inconsistentValue error.
When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, STD 58. In this case,
the object definition MUST include a 'SIZE' clause to
limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate."
SYNTAX OCTET STRING (SIZE (0..255))
InetAddressIPv4 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d"
STATUS current
DESCRIPTION
"Represents an IPv4 network address:
Octets Contents Encoding
1-4 IPv4 address network-byte order
The corresponding InetAddressType value is ipv4(1).
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (4))
InetAddressIPv6 ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x"
STATUS current
DESCRIPTION
"Represents an IPv6 network address:
Octets Contents Encoding
1-16 IPv6 address network-byte order
The corresponding InetAddressType value is ipv6(2).
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (16))
InetAddressIPv4z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d%4d"
STATUS current
DESCRIPTION
"Represents a non-global IPv4 network address, together
with its zone index:
Octets Contents Encoding
1-4 IPv4 address network-byte order
5-8 zone index network-byte order
The corresponding InetAddressType value is ipv4z(3).
The zone index (bytes 5-8) is used to disambiguate identical
address values on nodes that have interfaces attached to
different zones of the same scope. The zone index may contain
the special value 0, which refers to the default zone for each
scope.
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (8))
InetAddressIPv6z ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x%4d"
STATUS current
DESCRIPTION
"Represents a non-global IPv6 network address, together
with its zone index:
Octets Contents Encoding
1-16 IPv6 address network-byte order
17-20 zone index network-byte order
The corresponding InetAddressType value is ipv6z(4).
The zone index (bytes 17-20) is used to disambiguate
identical address values on nodes that have interfaces
attached to different zones of the same scope. The zone index
may contain the special value 0, which refers to the default
zone for each scope.
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (20))
InetAddressDNS ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"Represents a DNS domain name. The name SHOULD be fully
qualified whenever possible.
The corresponding InetAddressType is dns(16).
The DESCRIPTION clause of InetAddress objects that may have
InetAddressDNS values MUST fully describe how (and when)
these names are to be resolved to IP addresses.
The resolution of an InetAddressDNS value may require to
query multiple DNS records (e.g., A for IPv4 and AAAA for
IPv6). The order of the resolution process and which DNS
record takes precedence depends on the configuration of the
resolver.
This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair."
SYNTAX OCTET STRING (SIZE (1..255))
InetAddressPrefixLength ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Denotes the length of a generic Internet network address
prefix. A value of n corresponds to an IP address mask
that has n contiguous 1-bits from the most significant
bit (MSB), with all other bits set to 0.
An InetAddressPrefixLength value is always interpreted within
the context of an InetAddressType value. Every usage of the
InetAddressPrefixLength textual convention is required to
specify the InetAddressType object that provides the
context. It is suggested that the InetAddressType object be
logically registered before the object(s) that use the
InetAddressPrefixLength textual convention, if they appear
in the same logical row.
InetAddressPrefixLength values larger than
the maximum length of an IP address for a specific
InetAddressType are treated as the maximum significant
value applicable for the InetAddressType. The maximum
significant value is 32 for the InetAddressType
'ipv4(1)' and 'ipv4z(3)' and 128 for the InetAddressType
'ipv6(2)' and 'ipv6z(4)'. The maximum significant value
for the InetAddressType 'dns(16)' is 0.
The value zero is object-specific and must be defined as
part of the description of any object that uses this
syntax. Examples of the usage of zero might include
situations where the Internet network address prefix
is unknown or does not apply.
The upper bound of the prefix length has been chosen to
be consistent with the maximum size of an InetAddress."
SYNTAX Unsigned32 (0..2040)
InetPortNumber ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents a 16 bit port number of an Internet transport
layer protocol. Port numbers are assigned by IANA. A
current list of all assignments is available from
<http://www.iana.org/>.
The value zero is object-specific and must be defined as
part of the description of any object that uses this
syntax. Examples of the usage of zero might include
situations where a port number is unknown, or when the
value zero is used as a wildcard in a filter."
REFERENCE "STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960"
SYNTAX Unsigned32 (0..65535)
InetAutonomousSystemNumber ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Represents an autonomous system number that identifies an
Autonomous System (AS). An AS is a set of routers under a
single technical administration, using an interior gateway
protocol and common metrics to route packets within the AS,
and using an exterior gateway protocol to route packets to
other ASes'. IANA maintains the AS number space and has
delegated large parts to the regional registries.
Autonomous system numbers are currently limited to 16 bits
(0..65535). There is, however, work in progress to enlarge the
autonomous system number space to 32 bits. Therefore, this
textual convention uses an Unsigned32 value without a
range restriction in order to support a larger autonomous
system number space."
REFERENCE "RFC 1771, RFC 1930"
SYNTAX Unsigned32
InetScopeType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a scope type. This textual convention can be used
in cases where a MIB has to represent different scope types
and there is no context information, such as an InetAddress
object, that implicitly defines the scope type.
Note that not all possible values have been assigned yet, but
they may be assigned in future revisions of this specification.
Applications should therefore be able to deal with values
not yet assigned."
REFERENCE "RFC 3513"
SYNTAX INTEGER {
-- reserved(0),
interfaceLocal(1),
linkLocal(2),
subnetLocal(3),
adminLocal(4),
siteLocal(5), -- site-local unicast addresses
-- have been deprecated by RFC 3879
-- unassigned(6),
-- unassigned(7),
organizationLocal(8),
-- unassigned(9),
-- unassigned(10),
-- unassigned(11),
-- unassigned(12),
-- unassigned(13),
global(14)
-- reserved(15)
}
InetZoneIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A zone index identifies an instance of a zone of a
specific scope.
The zone index MUST disambiguate identical address
values. For link-local addresses, the zone index will
typically be the interface index (ifIndex as defined in the
IF-MIB) of the interface on which the address is configured.
The zone index may contain the special value 0, which refers
to the default zone. The default zone may be used in cases
where the valid zone index is not known (e.g., when a
management application has to write a link-local IPv6
address without knowing the interface index value). The
default zone SHOULD NOT be used as an easy way out in
cases where the zone index for a non-global IPv6 address
is known."
REFERENCE "RFC4007"
SYNTAX Unsigned32
InetVersion ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value representing a version of the IP protocol.
unknown(0) An unknown or unspecified version of the IP
protocol.
ipv4(1) The IPv4 protocol as defined in RFC 791 (STD 5).
ipv6(2) The IPv6 protocol as defined in RFC 2460.
Note that this textual convention SHOULD NOT be used to
distinguish different address types associated with IP
protocols. The InetAddressType has been designed for this
purpose."
REFERENCE "RFC 791, RFC 2460"
SYNTAX INTEGER {
unknown(0),
ipv4(1),
ipv6(2)
}
END
Icinga2/_Test/vSan Mib/vmw/IP-FORWARD-MIB.mib
+1358
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/IP-MIB.mib
+5255
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/IPV6-FLOW-LABEL-MIB.mib
+64
View File
@@ -0,0 +1,64 @@
-- https://www.ietf.org/rfc/rfc3595.txt
IPV6-FLOW-LABEL-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ipv6FlowLabelMIB MODULE-IDENTITY
LAST-UPDATED "200308280000Z" -- 28 August 2003
ORGANIZATION "IETF Operations and Management Area"
CONTACT-INFO "Bert Wijnen (Editor)
Lucent Technologies
Schagen 33
3461 GL Linschoten
Netherlands
Phone: +31 348-407-775
EMail: bwijnen@lucent.com
Send comments to <mibs@ops.ietf.org>.
"
DESCRIPTION "This MIB module provides commonly used textual
conventions for IPv6 Flow Labels.
Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC 3595,
see the RFC itself for full legal notices.
"
-- Revision History
REVISION "200308280000Z" -- 28 August 2003
DESCRIPTION "Initial version, published as RFC 3595."
::= { mib-2 103 }
IPv6FlowLabel ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION "The flow identifier or Flow Label in an IPv6
packet header that may be used to discriminate
traffic flows.
"
REFERENCE "Internet Protocol, Version 6 (IPv6) specification,
section 6. RFC 2460.
"
SYNTAX Integer32 (0..1048575)
IPv6FlowLabelOrAny ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION "The flow identifier or Flow Label in an IPv6
packet header that may be used to discriminate
traffic flows. The value of -1 is used to
indicate a wildcard, i.e. any value.
"
SYNTAX Integer32 (-1 | 0..1048575)
END
Icinga2/_Test/vSan Mib/vmw/LLDP-V2-MIB.mib
+1872
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/LLDP-V2-TC-MIB.mib
+328
View File
@@ -0,0 +1,328 @@
-- http://standards.ieee.org/getieee802/download/802.1AB-2009.pdf
-- modified from original by VMware to pass libsmi syntax checking
LLDP-V2-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
Unsigned32
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
ieee802dot1mibs
FROM IEEE8021-TC-MIB;
lldpV2TcMIB MODULE-IDENTITY
LAST-UPDATED "200906080000Z" -- June 08, 2009
ORGANIZATION "IEEE 802.1 Working Group"
CONTACT-INFO
"WG-URL: http://grouper.ieee.org/groups/802/1/index.html
WG-EMail: STDS-802-1-L@LISTSERV.IEEE.ORG
Contact: Tony Jeffree
Postal: 11a Poplar Grove
Sale
Cheshire M33 3AX
UK
Tel: +44-161-973-4278
E-mail: tony@jeffree.co.uk"
DESCRIPTION
"Textual conventions used throughout the IEEE Std 802.1AB
version 2 and later MIB modules.
Unless otherwise indicated, the references in this
MIB module are to IEEE 802.1AB-2009.
The TCs in this MIB are taken from the original LLDP-MIB,
LLDP-EXT-DOT1-MIB, and LLDP-EXT-DOT3-MIB published in
IEEE Std 802-1D-2005, with the addition of TCs to support
the management address table. They have been made available
as a separate TC MIB module to facilitate referencing from
other MIB modules.
Copyright (C) IEEE (2009). This version of this MIB module
is published as subclause 11.5.1 of IEEE Std 802.1AB-2009;
see the standard itself for full legal notices."
REVISION "200906080000Z" -- June 08, 2009
DESCRIPTION
"Published as part of IEEE Std 802.1AB-2009 revision."
::= { ieee802dot1mibs 12 }
--
-- ***********************************************************
--
-- Textual Conventions
--
-- ***********************************************************
LldpV2ChassisIdSubtype ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the source of a chassis identifier.
The enumeration 'chassisComponent(1)' represents a chassis
identifier based on the value of entPhysicalAlias object
(defined in IETF RFC 4133) for a chassis component (i.e.,
an entPhysicalClass value of 'chassis(3)').
The enumeration 'interfaceAlias(2)' represents a chassis
identifier based on the value of ifAlias object (defined in
IETF RFC 2863) for an interface on the containing chassis.
The enumeration 'portComponent(3)' represents a chassis
identifier based on the value of entPhysicalAlias object
(defined in IETF RFC 4133) for a port or backplane
component (i.e., entPhysicalClass value of 'port(10)' or
'backplane(4)'), within the containing chassis.
The enumeration 'macAddress(4)' represents a chassis
identifier based on the value of a unicast source address
(encoded in network byte order and IEEE 802.3 canonical bit
order), of a port on the containing chassis as defined in
IEEE Std 802.
The enumeration 'networkAddress(5)' represents a chassis
identifier based on a network address, associated with
a particular chassis. The encoded address is actually
composed of two fields. The first field is a single octet,
representing the IANA AddressFamilyNumbers value for the
specific address type, and the second field is the network
address value.
The enumeration 'interfaceName(6)' represents a chassis
identifier based on the value of ifName object (defined in
IETF RFC 2863) for an interface on the containing chassis.
The enumeration 'local(7)' represents a chassis identifier
based on a locally defined value."
SYNTAX INTEGER {
chassisComponent(1),
interfaceAlias(2),
portComponent(3),
macAddress(4),
networkAddress(5),
interfaceName(6),
local(7)
}
LldpV2ChassisId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"This TC describes the format of a chassis identifier string.
Objects of this type are always used with an associated
LldpChassisIdSubtype object, which identifies the format of
the particular LldpChassisId object instance.
If the associated LldpChassisIdSubtype object has a value of
'chassisComponent(1)', then the octet string identifies
a particular instance of the entPhysicalAlias object
(defined in IETF RFC 4133) for a chassis component (i.e.,
an entPhysicalClass value of 'chassis(3)').
If the associated LldpChassisIdSubtype object has a value
of 'interfaceAlias(2)', then the octet string identifies
a particular instance of the ifAlias object (defined in
IETF RFC 2863) for an interface on the containing chassis.
If the particular ifAlias object does not contain any values,
another chassis identifier type should be used
If the associated LldpChassisIdSubtype object has a value
of 'portComponent(3)', then the octet string identifies a
particular instance of the entPhysicalAlias object (defined
in IETF RFC 4133) for a port or backplane component within
the containing chassis.
If the associated LldpChassisIdSubtype object has a value of
'macAddress(4)', then this string identifies a particular
unicast source address (encoded in network byte order and
IEEE 802.3 canonical bit order), of a port on the containing
chassis as defined in IEEE Std 802.
If the associated LldpChassisIdSubtype object has a value of
'networkAddress(5)', then this string identifies a particular
network address, encoded in network byte order, associated
with one or more ports on the containing chassis. The first
octet contains the IANA Address Family Numbers enumeration
value for the specific address type, and octets 2 through
N contain the network address value in network byte order.
If the associated LldpChassisIdSubtype object has a value
of 'interfaceName(6)', then the octet string identifies
a particular instance of the ifName object (defined in
IETF RFC 2863) for an interface on the containing chassis.
If the particular ifName object does not contain any values,
another chassis identifier type should be used.
If the associated LldpChassisIdSubtype object has a value of
'local(7)', then this string identifies a locally assigned
Chassis ID."
SYNTAX OCTET STRING (SIZE (1..255))
LldpV2PortIdSubtype ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the source of a particular type of port
identifier used in the LLDP MIB.
The enumeration 'interfaceAlias(1)' represents a port
identifier based on the ifAlias MIB object, defined in IETF
RFC 2863.
The enumeration 'portComponent(2)' represents a port
identifier based on the value of entPhysicalAlias (defined in
IETF RFC 4133) for a port component (i.e., entPhysicalClass
value of 'port(10)'), within the containing chassis.
The enumeration 'macAddress(3)' represents a port identifier
based on a unicast source address (encoded in network
byte order and IEEE 802.3 canonical bit order), which has
been detected by the agent and associated with a particular
port (IEEE Std 802).
The enumeration 'networkAddress(4)' represents a port
identifier based on a network address, detected by the agent
and associated with a particular port.
The enumeration 'interfaceName(5)' represents a port
identifier based on the ifName MIB object, defined in IETF
RFC 2863.
The enumeration 'agentCircuitId(6)' represents a port
identifier based on the agent-local identifier of the circuit
(defined in RFC 3046), detected by the agent and associated
with a particular port.
The enumeration 'local(7)' represents a port identifier
based on a value locally assigned."
SYNTAX INTEGER {
interfaceAlias(1),
portComponent(2),
macAddress(3),
networkAddress(4),
interfaceName(5),
agentCircuitId(6),
local(7)
}
LldpV2PortId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"This TC describes the format of a port identifier string.
Objects of this type are always used with an associated
LldpPortIdSubtype object, which identifies the format of the
particular LldpPortId object instance.
If the associated LldpPortIdSubtype object has a value of
'interfaceAlias(1)', then the octet string identifies a
particular instance of the ifAlias object (defined in IETF
RFC 2863). If the particular ifAlias object does not contain
any values, another port identifier type should be used.
If the associated LldpPortIdSubtype object has a value of
'portComponent(2)', then the octet string identifies a
particular instance of the entPhysicalAlias object (defined
in IETF RFC 4133) for a port or backplane component.
If the associated LldpPortIdSubtype object has a value of
'macAddress(3)', then this string identifies a particular
unicast source address (encoded in network byte order
and IEEE 802.3 canonical bit order) associated with the port
(IEEE Std 802).
If the associated LldpPortIdSubtype object has a value of
'networkAddress(4)', then this string identifies a network
address associated with the port. The first octet contains
the IANA AddressFamilyNumbers enumeration value for the
specific address type, and octets 2 through N contain the
networkAddress address value in network byte order.
If the associated LldpPortIdSubtype object has a value of
'interfaceName(5)', then the octet string identifies a
particular instance of the ifName object (defined in IETF
RFC 2863). If the particular ifName object does not contain
any values, another port identifier type should be used.
If the associated LldpPortIdSubtype object has a value of
'agentCircuitId(6)', then this string identifies a agent-local
identifier of the circuit (defined in RFC 3046).
If the associated LldpPortIdSubtype object has a value of
'local(7)', then this string identifies a locally
assigned port ID."
SYNTAX OCTET STRING (SIZE (1..255))
LldpV2ManAddrIfSubtype ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC defines an enumeration value that identifies
the interface numbering method used for defining the
interface number associated with a management address.
An object with this syntax defines the format of an
interface number object.
The enumeration 'unknown(1)' represents the case where the
interface is not known. In this case, the corresponding
interface number is of zero length.
The enumeration 'ifIndex(2)' represents interface identifier
based on the ifIndex MIB object.
The enumeration 'systemPortNumber(3)' represents interface
identifier based on the system port numbering convention."
REFERENCE
"8.5.9.5"
SYNTAX INTEGER {
unknown(1),
ifIndex(2),
systemPortNumber(3)
}
LldpV2ManAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"The value of a management address associated with the LLDP
agent that may be used to reach higher layer entities to
assist discovery by network management.
It should be noted that appropriate security credentials,
such as SNMP engineId, may be required to access the LLDP
agent using a management address. These necessary credentials
should be known by the network management and the objects
associated with the credentials are not included in the
LLDP agent."
SYNTAX OCTET STRING (SIZE (1..31))
LldpV2SystemCapabilitiesMap ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the system capabilities.
The bit 'other(0)' indicates that the system has capabilities
other than those listed below.
The bit 'repeater(1)' indicates that the system has repeater
capability.
The bit 'bridge(2)' indicates that the system has bridge
capability.
The bit 'wlanAccessPoint(3)' indicates that the system has
WLAN access point capability.
The bit 'router(4)' indicates that the system has router
capability.
The bit 'telephone(5)' indicates that the system has telephone
capability.
The bit 'docsisCableDevice(6)' indicates that the system has
DOCSIS Cable Device capability (IETF RFC 4639 & 2670).
The bit 'stationOnly(7)' indicates that the system has only
station capability and nothing else.
The bit 'cVLANComponent(8)' indicates that the system has
C-VLAN component functionality.
The bit 'sVLANComponent(8)' indicates that the system has
S-VLAN component functionality.
The bit 'twoPortMACRelay(10)' indicates that the system has
Two-port MAC Relay (TPMR) functionality."
SYNTAX BITS {
other(0),
repeater(1),
bridge(2),
wlanAccessPoint(3),
router(4),
telephone(5),
docsisCableDevice(6),
stationOnly(7),
cVLANComponent(8),
sVLANComponent(9),
twoPortMACRelay(10)
}
LldpV2DestAddressTableIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An index value, used as the index to the table of destination
MAC addresses used both as the destination addresses on
transmitted LLDPDUs and on received LLDPDUs. This index value
is also used as a secondary index value in tables indexed
by fields of type ifIndex, in order to associate
a destination address with each row of the table."
SYNTAX Unsigned32(1..4096)
LldpV2LinkAggStatusMap ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the link aggregation status.
The bit 'aggCapable(0)' indicates the link is capable of being
aggregated.
The bit 'aggEnabled(1)' indicates the link is currently in
aggregation."
SYNTAX BITS {
aggCapable(0),
aggEnabled(1)
}
LldpV2PowerPortClass ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC describes the Power over Ethernet (PoE) port class."
SYNTAX INTEGER {
pClassPSE(1),
pClassPD(2)
}
END
Icinga2/_Test/vSan Mib/vmw/P-BRIDGE-MIB.mib
+1217
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/Q-BRIDGE-MIB.mib
+2490
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/README
+52
View File
@@ -0,0 +1,52 @@
Date: Fri Mar 27 09:39:18 PDT 2020
Company: VMware, Inc
Subject: VMWARE SNMP MIB MODULES
This directory contains mib modules
for VMWARE products in SMIv2 (RFC 2578) compliant format.
MIB module files may also be distributed by the individual VMware products.
Use the REVISION clause in the MIB module to determine which is the latest
version to install. MIB modules are always backward compatible.
To load these into various management stations
software use this suggested order to prevent any lookup
errors.
For any given VMware product (ESXi, Virtual Center, NSX-MANAGER, ...)
and version release, to find the set of MIB modules it supports
please review the agent capability *-AGENTCAP-MIB file.
ESXi
VMWARE-ESX-AGENTCAP-MIB.mib -- describes the ESXi agent since ESX 5.1 (2009)
Virtual Center Management
VMWARE-VA-AGENTCAP-MIB.mib -- describes SNMPv1/v2/v3 agent since VSPHERE 6.0 (2015)
NSX Manager
VMWARE-NSX-MANAGER-AGENTCAP-MIB.mib -- describes the SNMPv2c trap only agent in NSX-Manager (2016)
VROPS
VMWARE-VROPS-AGENTCAP-MIB.mib -- describesthe SNMPv2c trap only agent in VCenter Operations (2018)
VRNI
VMWARE-VRNI-AGENTCAP-MIB.mib -- describes the SNMPv2c trap only vRealise Log Insight Appliance (2018)
VTSA
VMWARE-TUNNEL-SERVER-AGENTCAP-MIB.mib -- describes the SNMPv1/v2c/v3 agent in VMware Tunnel Server (2018)
Note: loading the latest version of any given mib module should provide backward compatiblity
for prior releases. Only one MIB module (NSX-MANAGER) presently may not follow SNMP backward
compatiblity rules.
Knowledge Base articles:
* OID List http://kb.vmware.com/kb/2054359
* Downloading MIB modules http://kb.vmware.com/kb/1013445
* Debugging notifications (trap/inform) reception http://kb.vmware.com/kb/2035445
* Reverse Poll Feature akaSNMP Trap is repeated every 5 minutes http://ikb.vmware.com/kb/2020271
* Timeouts and SNMP https://ikb.vmware.com/kb/2100602
* Timeouts in ESXi snmp in storage apis: https://ikb.vmware.com/kb/2105674
* Understanding Layer 2 networking as reported by ESXi SNMP http://kb.vmware.com/kb/2118059
* Monitoring VCSA using SNMP (2145018) http://kb.vmware.com/kb/2145018
End of document
Icinga2/_Test/vSan Mib/vmw/RMON-MIB.mib
+4190
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/RMON2-MIB.mib
+6020
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/SNMP-FRAMEWORK-MIB.mib
+526
View File
@@ -0,0 +1,526 @@
SNMP-FRAMEWORK-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
OBJECT-IDENTITY,
snmpModules FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
snmpFrameworkMIB MODULE-IDENTITY
LAST-UPDATED "200210140000Z"
ORGANIZATION "SNMPv3 Working Group"
CONTACT-INFO "WG-EMail: snmpv3@lists.tislabs.com
Subscribe: snmpv3-request@lists.tislabs.com
Co-Chair: Russ Mundy
Network Associates Laboratories
postal: 15204 Omega Drive, Suite 300
Rockville, MD 20850-4601
USA
EMail: mundy@tislabs.com
phone: +1 301-947-7107
Co-Chair &
Co-editor: David Harrington
Enterasys Networks
postal: 35 Industrial Way
P. O. Box 5005
Rochester, New Hampshire 03866-5005
USA
EMail: dbh@enterasys.com
phone: +1 603-337-2614
Co-editor: Randy Presuhn
BMC Software, Inc.
postal: 2141 North First Street
San Jose, California 95131
USA
EMail: randy_presuhn@bmc.com
phone: +1 408-546-1006
Co-editor: Bert Wijnen
Lucent Technologies
postal: Schagen 33
3461 GL Linschoten
Netherlands
EMail: bwijnen@lucent.com
phone: +31 348-680-485
"
DESCRIPTION "The SNMP Management Architecture MIB
Copyright (C) The Internet Society (2002). This
version of this MIB module is part of RFC 3411;
see the RFC itself for full legal notices.
"
REVISION "200210140000Z" -- 14 October 2002
DESCRIPTION "Changes in this revision:
- Updated various administrative information.
- Corrected some typos.
- Corrected typo in description of SnmpEngineID
that led to range overlap for 127.
- Changed '255a' to '255t' in definition of
SnmpAdminString to align with current SMI.
- Reworded 'reserved' for value zero in
DESCRIPTION of SnmpSecurityModel.
- The algorithm for allocating security models
should give 256 per enterprise block, rather
than 255.
- The example engine ID of 'abcd' is not
legal. Replaced with '800002b804616263'H based
on example enterprise 696, string 'abc'.
- Added clarification that engineID should
persist across re-initializations.
This revision published as RFC 3411.
"
REVISION "199901190000Z" -- 19 January 1999
DESCRIPTION "Updated editors' addresses, fixed typos.
Published as RFC 2571.
"
REVISION "199711200000Z" -- 20 November 1997
DESCRIPTION "The initial version, published in RFC 2271.
"
::= { snmpModules 10 }
-- Textual Conventions used in the SNMP Management Architecture ***
SnmpEngineID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "An SNMP engine's administratively-unique identifier.
Objects of this type are for identification, not for
addressing, even though it is possible that an
address may have been used in the generation of
a specific value.
The value for this object may not be all zeros or
all 'ff'H or the empty (zero length) string.
The initial value for this object may be configured
via an operator console entry or via an algorithmic
function. In the latter case, the following
example algorithm is recommended.
In cases where there are multiple engines on the
same system, the use of this algorithm is NOT
appropriate, as it would result in all of those
engines ending up with the same ID value.
1) The very first bit is used to indicate how the
rest of the data is composed.
0 - as defined by enterprise using former methods
that existed before SNMPv3. See item 2 below.
1 - as defined by this architecture, see item 3
below.
Note that this allows existing uses of the
engineID (also known as AgentID [RFC1910]) to
co-exist with any new uses.
2) The snmpEngineID has a length of 12 octets.
The first four octets are set to the binary
equivalent of the agent's SNMP management
private enterprise number as assigned by the
Internet Assigned Numbers Authority (IANA).
For example, if Acme Networks has been assigned
{ enterprises 696 }, the first four octets would
be assigned '000002b8'H.
The remaining eight octets are determined via
one or more enterprise-specific methods. Such
methods must be designed so as to maximize the
possibility that the value of this object will
be unique in the agent's administrative domain.
For example, it may be the IP address of the SNMP
entity, or the MAC address of one of the
interfaces, with each address suitably padded
with random octets. If multiple methods are
defined, then it is recommended that the first
octet indicate the method being used and the
remaining octets be a function of the method.
3) The length of the octet string varies.
The first four octets are set to the binary
equivalent of the agent's SNMP management
private enterprise number as assigned by the
Internet Assigned Numbers Authority (IANA).
For example, if Acme Networks has been assigned
{ enterprises 696 }, the first four octets would
be assigned '000002b8'H.
The very first bit is set to 1. For example, the
above value for Acme Networks now changes to be
'800002b8'H.
The fifth octet indicates how the rest (6th and
following octets) are formatted. The values for
the fifth octet are:
0 - reserved, unused.
1 - IPv4 address (4 octets)
lowest non-special IP address
2 - IPv6 address (16 octets)
lowest non-special IP address
3 - MAC address (6 octets)
lowest IEEE MAC address, canonical
order
4 - Text, administratively assigned
Maximum remaining length 27
5 - Octets, administratively assigned
Maximum remaining length 27
6-127 - reserved, unused
128-255 - as defined by the enterprise
Maximum remaining length 27
"
SYNTAX OCTET STRING (SIZE(5..32))
SnmpSecurityModel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "An identifier that uniquely identifies a
Security Model of the Security Subsystem within
this SNMP Management Architecture.
The values for securityModel are allocated as
follows:
- The zero value does not identify any particular
security model.
- Values between 1 and 255, inclusive, are reserved
for standards-track Security Models and are
managed by the Internet Assigned Numbers Authority
(IANA).
- Values greater than 255 are allocated to
enterprise-specific Security Models. An
enterprise-specific securityModel value is defined
to be:
enterpriseID * 256 + security model within
enterprise
For example, the fourth Security Model defined by
the enterprise whose enterpriseID is 1 would be
259.
This scheme for allocation of securityModel
values allows for a maximum of 255 standards-
based Security Models, and for a maximum of
256 Security Models per enterprise.
It is believed that the assignment of new
securityModel values will be rare in practice
because the larger the number of simultaneously
utilized Security Models, the larger the
chance that interoperability will suffer.
Consequently, it is believed that such a range
will be sufficient. In the unlikely event that
the standards committee finds this number to be
insufficient over time, an enterprise number
can be allocated to obtain an additional 256
possible values.
Note that the most significant bit must be zero;
hence, there are 23 bits allocated for various
organizations to design and define non-standard
securityModels. This limits the ability to
define new proprietary implementations of Security
Models to the first 8,388,608 enterprises.
It is worthwhile to note that, in its encoded
form, the securityModel value will normally
require only a single byte since, in practice,
the leftmost bits will be zero for most messages
and sign extension is suppressed by the encoding
rules.
As of this writing, there are several values
of securityModel defined for use with SNMP or
reserved for use with supporting MIB objects.
They are as follows:
0 reserved for 'any'
1 reserved for SNMPv1
2 reserved for SNMPv2c
3 User-Based Security Model (USM)
"
SYNTAX INTEGER(0 .. 2147483647)
SnmpMessageProcessingModel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "An identifier that uniquely identifies a Message
Processing Model of the Message Processing
Subsystem within this SNMP Management Architecture.
The values for messageProcessingModel are
allocated as follows:
- Values between 0 and 255, inclusive, are
reserved for standards-track Message Processing
Models and are managed by the Internet Assigned
Numbers Authority (IANA).
- Values greater than 255 are allocated to
enterprise-specific Message Processing Models.
An enterprise messageProcessingModel value is
defined to be:
enterpriseID * 256 +
messageProcessingModel within enterprise
For example, the fourth Message Processing Model
defined by the enterprise whose enterpriseID
is 1 would be 259.
This scheme for allocating messageProcessingModel
values allows for a maximum of 255 standards-
based Message Processing Models, and for a
maximum of 256 Message Processing Models per
enterprise.
It is believed that the assignment of new
messageProcessingModel values will be rare
in practice because the larger the number of
simultaneously utilized Message Processing Models,
the larger the chance that interoperability
will suffer. It is believed that such a range
will be sufficient. In the unlikely event that
the standards committee finds this number to be
insufficient over time, an enterprise number
can be allocated to obtain an additional 256
possible values.
Note that the most significant bit must be zero;
hence, there are 23 bits allocated for various
organizations to design and define non-standard
messageProcessingModels. This limits the ability
to define new proprietary implementations of
Message Processing Models to the first 8,388,608
enterprises.
It is worthwhile to note that, in its encoded
form, the messageProcessingModel value will
normally require only a single byte since, in
practice, the leftmost bits will be zero for
most messages and sign extension is suppressed
by the encoding rules.
As of this writing, there are several values of
messageProcessingModel defined for use with SNMP.
They are as follows:
0 reserved for SNMPv1
1 reserved for SNMPv2c
2 reserved for SNMPv2u and SNMPv2*
3 reserved for SNMPv3
"
SYNTAX INTEGER(0 .. 2147483647)
SnmpSecurityLevel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A Level of Security at which SNMP messages can be
sent or with which operations are being processed;
in particular, one of:
noAuthNoPriv - without authentication and
without privacy,
authNoPriv - with authentication but
without privacy,
authPriv - with authentication and
with privacy.
These three values are ordered such that
noAuthNoPriv is less than authNoPriv and
authNoPriv is less than authPriv.
"
SYNTAX INTEGER { noAuthNoPriv(1),
authNoPriv(2),
authPriv(3)
}
SnmpAdminString ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255t"
STATUS current
DESCRIPTION "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 (SIZE (0..255))
-- Administrative assignments ***************************************
snmpFrameworkAdmin
OBJECT IDENTIFIER ::= { snmpFrameworkMIB 1 }
snmpFrameworkMIBObjects
OBJECT IDENTIFIER ::= { snmpFrameworkMIB 2 }
snmpFrameworkMIBConformance
OBJECT IDENTIFIER ::= { snmpFrameworkMIB 3 }
-- the snmpEngine Group ********************************************
snmpEngine OBJECT IDENTIFIER ::= { snmpFrameworkMIBObjects 1 }
snmpEngineID OBJECT-TYPE
SYNTAX SnmpEngineID
MAX-ACCESS read-only
STATUS current
DESCRIPTION "An SNMP engine's administratively-unique identifier.
This information SHOULD be stored in non-volatile
storage so that it remains constant across
re-initializations of the SNMP engine.
"
::= { snmpEngine 1 }
snmpEngineBoots OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of times that the SNMP engine has
(re-)initialized itself since snmpEngineID
was last configured.
"
::= { snmpEngine 2 }
snmpEngineTime OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of seconds since the value of
the snmpEngineBoots object last changed.
When incrementing this object's value would
cause it to exceed its maximum,
snmpEngineBoots is incremented as if a
re-initialization had occurred, and this
object's value consequently reverts to zero.
"
::= { snmpEngine 3 }
snmpEngineMaxMessageSize OBJECT-TYPE
SYNTAX INTEGER (484..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The maximum length in octets of an SNMP message
which this SNMP engine can send or receive and
process, determined as the minimum of the maximum
message size values supported among all of the
transports available to and supported by the engine.
"
::= { snmpEngine 4 }
-- Registration Points for Authentication and Privacy Protocols **
snmpAuthProtocols OBJECT-IDENTITY
STATUS current
DESCRIPTION "Registration point for standards-track
authentication protocols used in SNMP Management
Frameworks.
"
::= { snmpFrameworkAdmin 1 }
snmpPrivProtocols OBJECT-IDENTITY
STATUS current
DESCRIPTION "Registration point for standards-track privacy
protocols used in SNMP Management Frameworks.
"
::= { snmpFrameworkAdmin 2 }
-- Conformance information ******************************************
snmpFrameworkMIBCompliances
OBJECT IDENTIFIER ::= {snmpFrameworkMIBConformance 1}
snmpFrameworkMIBGroups
OBJECT IDENTIFIER ::= {snmpFrameworkMIBConformance 2}
-- compliance statements
snmpFrameworkMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for SNMP engines which
implement the SNMP Management Framework MIB.
"
MODULE -- this module
MANDATORY-GROUPS { snmpEngineGroup }
::= { snmpFrameworkMIBCompliances 1 }
-- units of conformance
snmpEngineGroup OBJECT-GROUP
OBJECTS {
snmpEngineID,
snmpEngineBoots,
snmpEngineTime,
snmpEngineMaxMessageSize
}
STATUS current
DESCRIPTION "A collection of objects for identifying and
determining the configuration and current timeliness
values of an SNMP engine.
"
::= { snmpFrameworkMIBGroups 1 }
END
Icinga2/_Test/vSan Mib/vmw/SNMP-MPD-MIB.mib
+154
View File
@@ -0,0 +1,154 @@
-- http://www.ietf.org/rfc/rfc3412.txt
SNMP-MPD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE,
snmpModules, Counter32 FROM SNMPv2-SMI;
snmpMPDMIB MODULE-IDENTITY
LAST-UPDATED "200210140000Z"
ORGANIZATION "SNMPv3 Working Group"
CONTACT-INFO "WG-EMail: snmpv3@lists.tislabs.com
Subscribe: snmpv3-request@lists.tislabs.com
Co-Chair: Russ Mundy
Network Associates Laboratories
postal: 15204 Omega Drive, Suite 300
Rockville, MD 20850-4601
USA
EMail: mundy@tislabs.com
phone: +1 301-947-7107
Co-Chair &
Co-editor: David Harrington
Enterasys Networks
postal: 35 Industrial Way
P. O. Box 5005
Rochester NH 03866-5005
USA
EMail: dbh@enterasys.com
phone: +1 603-337-2614
Co-editor: Jeffrey Case
SNMP Research, Inc.
postal: 3001 Kimberlin Heights Road
Knoxville, TN 37920-9716
USA
EMail: case@snmp.com
phone: +1 423-573-1434
Co-editor: Randy Presuhn
BMC Software, Inc.
postal: 2141 North First Street
San Jose, CA 95131
USA
EMail: randy_presuhn@bmc.com
phone: +1 408-546-1006
Co-editor: Bert Wijnen
Lucent Technologies
postal: Schagen 33
3461 GL Linschoten
Netherlands
EMail: bwijnen@lucent.com
phone: +31 348-680-485
"
DESCRIPTION "The MIB for Message Processing and Dispatching
Copyright (C) The Internet Society (2002). This
version of this MIB module is part of RFC 3412;
see the RFC itself for full legal notices.
"
REVISION "200210140000Z" -- 14 October 2002
DESCRIPTION "Updated addresses, published as RFC 3412."
REVISION "199905041636Z" -- 4 May 1999
DESCRIPTION "Updated addresses, published as RFC 2572."
REVISION "199709300000Z" -- 30 September 1997
DESCRIPTION "Original version, published as RFC 2272."
::= { snmpModules 11 }
-- Administrative assignments ***************************************
snmpMPDAdmin OBJECT IDENTIFIER ::= { snmpMPDMIB 1 }
snmpMPDMIBObjects OBJECT IDENTIFIER ::= { snmpMPDMIB 2 }
snmpMPDMIBConformance OBJECT IDENTIFIER ::= { snmpMPDMIB 3 }
-- Statistics for SNMP Messages *************************************
snmpMPDStats OBJECT IDENTIFIER ::= { snmpMPDMIBObjects 1 }
snmpUnknownSecurityModels OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The total number of packets received by the SNMP
engine which were dropped because they referenced a
securityModel that was not known to or supported by
the SNMP engine.
"
::= { snmpMPDStats 1 }
snmpInvalidMsgs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The total number of packets received by the SNMP
engine which were dropped because there were invalid
or inconsistent components in the SNMP message.
"
::= { snmpMPDStats 2 }
snmpUnknownPDUHandlers OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The total number of packets received by the SNMP
engine which were dropped because the PDU contained
in the packet could not be passed to an application
responsible for handling the pduType, e.g. no SNMP
application had registered for the proper
combination of the contextEngineID and the pduType.
"
::= { snmpMPDStats 3 }
-- Conformance information ******************************************
snmpMPDMIBCompliances OBJECT IDENTIFIER ::= {snmpMPDMIBConformance 1}
snmpMPDMIBGroups OBJECT IDENTIFIER ::= {snmpMPDMIBConformance 2}
-- Compliance statements
snmpMPDCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for SNMP entities which
implement the SNMP-MPD-MIB.
"
MODULE -- this module
MANDATORY-GROUPS { snmpMPDGroup }
::= { snmpMPDMIBCompliances 1 }
snmpMPDGroup OBJECT-GROUP
OBJECTS {
snmpUnknownSecurityModels,
snmpInvalidMsgs,
snmpUnknownPDUHandlers
}
STATUS current
DESCRIPTION "A collection of objects providing for remote
monitoring of the SNMP Message Processing and
Dispatching process.
"
::= { snmpMPDMIBGroups 1 }
END
Icinga2/_Test/vSan Mib/vmw/SNMPv2-CONF.mib
+318
View File
@@ -0,0 +1,318 @@
SNMPv2-CONF DEFINITIONS ::= BEGIN
IMPORTS ObjectName, NotificationName, ObjectSyntax
FROM SNMPv2-SMI;
-- definitions for conformance groups
OBJECT-GROUP MACRO ::=
BEGIN
TYPE NOTATION ::=
ObjectsPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
ObjectsPart ::=
"OBJECTS" "{" Objects "}"
Objects ::=
Object
| Objects "," Object
Object ::=
value(ObjectName)
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in [2]
Text ::= value(IA5String)
END
-- more definitions for conformance groups
NOTIFICATION-GROUP MACRO ::=
BEGIN
TYPE NOTATION ::=
NotificationsPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
NotificationsPart ::=
"NOTIFICATIONS" "{" Notifications "}"
Notifications ::=
Notification
| Notifications "," Notification
Notification ::=
value(NotificationName)
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in [2]
Text ::= value(IA5String)
END
-- definitions for compliance statements
MODULE-COMPLIANCE MACRO ::=
BEGIN
TYPE NOTATION ::=
"STATUS" Status
"DESCRIPTION" Text
ReferPart
ModulePart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
ModulePart ::=
Modules
Modules ::=
Module
| Modules Module
Module ::=
-- name of module --
"MODULE" ModuleName
MandatoryPart
CompliancePart
ModuleName ::=
-- identifier must start with uppercase letter
identifier ModuleIdentifier
-- must not be empty unless contained
-- in MIB Module
| empty
ModuleIdentifier ::=
value(OBJECT IDENTIFIER)
| empty
MandatoryPart ::=
"MANDATORY-GROUPS" "{" Groups "}"
| empty
Groups ::=
Group
| Groups "," Group
Group ::=
value(OBJECT IDENTIFIER)
CompliancePart ::=
Compliances
| empty
Compliances ::=
Compliance
| Compliances Compliance
Compliance ::=
ComplianceGroup
| Object
ComplianceGroup ::=
"GROUP" value(OBJECT IDENTIFIER)
"DESCRIPTION" Text
Object ::=
"OBJECT" value(ObjectName)
SyntaxPart
WriteSyntaxPart
AccessPart
"DESCRIPTION" Text
-- must be a refinement for object's SYNTAX clause
SyntaxPart ::= "SYNTAX" Syntax
| empty
-- must be a refinement for object's SYNTAX clause
WriteSyntaxPart ::= "WRITE-SYNTAX" Syntax
| empty
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement),
-- a textual convention (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative
AccessPart ::=
"MIN-ACCESS" Access
| empty
Access ::=
"not-accessible"
| "accessible-for-notify"
| "read-only"
| "read-write"
| "read-create"
-- a character string as defined in [2]
Text ::= value(IA5String)
END
-- definitions for capabilities statements
AGENT-CAPABILITIES MACRO ::=
BEGIN
TYPE NOTATION ::=
"PRODUCT-RELEASE" Text
"STATUS" Status
"DESCRIPTION" Text
ReferPart
ModulePart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
Status ::=
"current"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
ModulePart ::=
Modules
| empty
Modules ::=
Module
| Modules Module
Module ::=
-- name of module --
"SUPPORTS" ModuleName
"INCLUDES" "{" Groups "}"
VariationPart
ModuleName ::=
-- identifier must start with uppercase letter
identifier ModuleIdentifier
ModuleIdentifier ::=
value(OBJECT IDENTIFIER)
| empty
Groups ::=
Group
| Groups "," Group
Group ::=
value(OBJECT IDENTIFIER)
VariationPart ::=
Variations
| empty
Variations ::=
Variation
| Variations Variation
Variation ::=
ObjectVariation
| NotificationVariation
NotificationVariation ::=
"VARIATION" value(NotificationName)
AccessPart
"DESCRIPTION" Text
ObjectVariation ::=
"VARIATION" value(ObjectName)
SyntaxPart
WriteSyntaxPart
AccessPart
CreationPart
DefValPart
"DESCRIPTION" Text
-- must be a refinement for object's SYNTAX clause
SyntaxPart ::= "SYNTAX" Syntax
| empty
WriteSyntaxPart ::= "WRITE-SYNTAX" Syntax
| empty
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement),
-- a textual convention (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative
AccessPart ::=
"ACCESS" Access
| empty
Access ::=
"not-implemented"
-- only "not-implemented" for notifications
| "accessible-for-notify"
| "read-only"
| "read-write"
| "read-create"
-- following is for backward-compatibility only
| "write-only"
CreationPart ::=
"CREATION-REQUIRES" "{" Cells "}"
| empty
Cells ::=
Cell
| Cells "," Cell
Cell ::=
value(ObjectName)
DefValPart ::= "DEFVAL" "{" Defvalue "}"
| empty
Defvalue ::= -- must be valid for the object's syntax
-- in this macro's SYNTAX clause, if present,
-- or if not, in object's OBJECT-TYPE macro
value(ObjectSyntax)
| "{" BitsValue "}"
BitsValue ::= BitNames
| empty
BitNames ::= BitName
| BitNames "," BitName
BitName ::= identifier
-- a character string as defined in [2]
Text ::= value(IA5String)
END
END
Icinga2/_Test/vSan Mib/vmw/SNMPv2-MIB.mib
+855
View File
@@ -0,0 +1,855 @@
-- http://www.ietf.org/rfc/rfc3418.txt
SNMPv2-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
TimeTicks, Counter32, snmpModules, mib-2
FROM SNMPv2-SMI
DisplayString, TestAndIncr, TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF;
snmpMIB MODULE-IDENTITY
LAST-UPDATED "200210160000Z"
ORGANIZATION "IETF SNMPv3 Working Group"
CONTACT-INFO
"WG-EMail: snmpv3@lists.tislabs.com
Subscribe: snmpv3-request@lists.tislabs.com
Co-Chair: Russ Mundy
Network Associates Laboratories
postal: 15204 Omega Drive, Suite 300
Rockville, MD 20850-4601
USA
EMail: mundy@tislabs.com
phone: +1 301 947-7107
Co-Chair: David Harrington
Enterasys Networks
postal: 35 Industrial Way
P. O. Box 5005
Rochester, NH 03866-5005
USA
EMail: dbh@enterasys.com
phone: +1 603 337-2614
Editor: Randy Presuhn
BMC Software, Inc.
postal: 2141 North First Street
San Jose, CA 95131
USA
EMail: randy_presuhn@bmc.com
phone: +1 408 546-1006"
DESCRIPTION
"The MIB module for SNMP entities.
Copyright (C) The Internet Society (2002). This
version of this MIB module is part of RFC 3418;
see the RFC itself for full legal notices.
"
REVISION "200210160000Z"
DESCRIPTION
"This revision of this MIB module was published as
RFC 3418."
REVISION "199511090000Z"
DESCRIPTION
"This revision of this MIB module was published as
RFC 1907."
REVISION "199304010000Z"
DESCRIPTION
"The initial revision of this MIB module was published
as RFC 1450."
::= { snmpModules 1 }
snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 }
-- ::= { snmpMIBObjects 1 } this OID is obsolete
-- ::= { snmpMIBObjects 2 } this OID is obsolete
-- ::= { snmpMIBObjects 3 } this OID is obsolete
-- the System group
--
-- a collection of objects common to all managed systems.
system OBJECT IDENTIFIER ::= { mib-2 1 }
sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the entity. This value should
include the full name and version identification of
the system's hardware type, software operating-system,
and networking software."
::= { system 1 }
sysObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The vendor's authoritative identification of the
network management subsystem contained in the entity.
This value is allocated within the SMI enterprises
subtree (1.3.6.1.4.1) and provides an easy and
unambiguous means for determining `what kind of box' is
being managed. For example, if vendor `Flintstones,
Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
it could assign the identifier 1.3.6.1.4.1.424242.1.1
to its `Fred Router'."
::= { system 2 }
sysUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized."
::= { system 3 }
sysContact OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The textual identification of the contact person for
this managed node, together with information on how
to contact this person. If no contact information is
known, the value is the zero-length string."
::= { system 4 }
sysName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An administratively-assigned name for this managed
node. By convention, this is the node's fully-qualified
domain name. If the name is unknown, the value is
the zero-length string."
::= { system 5 }
sysLocation OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The physical location of this node (e.g., 'telephone
closet, 3rd floor'). If the location is unknown, the
value is the zero-length string."
::= { system 6 }
sysServices OBJECT-TYPE
SYNTAX INTEGER (0..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value which indicates the set of services that this
entity may potentially offer. The value is a sum.
This sum initially takes the value zero. Then, for
each layer, L, in the range 1 through 7, that this node
performs transactions for, 2 raised to (L - 1) is added
to the sum. For example, a node which performs only
routing functions would have a value of 4 (2^(3-1)).
In contrast, a node which is a host offering application
services would have a value of 72 (2^(4-1) + 2^(7-1)).
Note that in the context of the Internet suite of
protocols, values should be calculated accordingly:
layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., supports the IP)
4 end-to-end (e.g., supports the TCP)
7 applications (e.g., supports the SMTP)
For systems including OSI protocols, layers 5 and 6
may also be counted."
::= { system 7 }
-- object resource information
--
-- a collection of objects which describe the SNMP entity's
-- (statically and dynamically configurable) support of
-- various MIB modules.
sysORLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time of the most recent
change in state or value of any instance of sysORID."
::= { system 8 }
sysORTable OBJECT-TYPE
SYNTAX SEQUENCE OF SysOREntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the capabilities of
the local SNMP application acting as a command
responder with respect to various MIB modules.
SNMP entities having dynamically-configurable support
of MIB modules will have a dynamically-varying number
of conceptual rows."
::= { system 9 }
sysOREntry OBJECT-TYPE
SYNTAX SysOREntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the sysORTable."
INDEX { sysORIndex }
::= { sysORTable 1 }
SysOREntry ::= SEQUENCE {
sysORIndex INTEGER,
sysORID OBJECT IDENTIFIER,
sysORDescr DisplayString,
sysORUpTime TimeStamp
}
sysORIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The auxiliary variable used for identifying instances
of the columnar objects in the sysORTable."
::= { sysOREntry 1 }
sysORID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An authoritative identification of a capabilities
statement with respect to various MIB modules supported
by the local SNMP application acting as a command
responder."
::= { sysOREntry 2 }
sysORDescr OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the capabilities identified
by the corresponding instance of sysORID."
::= { sysOREntry 3 }
sysORUpTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this conceptual
row was last instantiated."
::= { sysOREntry 4 }
-- the SNMP group
--
-- a collection of objects providing basic instrumentation and
-- control of an SNMP entity.
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
snmpInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of messages delivered to the SNMP
entity from the transport service."
::= { snmp 1 }
snmpInBadVersions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of SNMP messages which were delivered
to the SNMP entity and were for an unsupported SNMP
version."
::= { snmp 3 }
snmpInBadCommunityNames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of community-based SNMP messages (for
example, SNMPv1) delivered to the SNMP entity which
used an SNMP community name not known to said entity.
Also, implementations which authenticate community-based
SNMP messages using check(s) in addition to matching
the community name (for example, by also checking
whether the message originated from a transport address
allowed to use a specified community name) MAY include
in this value the number of messages which failed the
additional check(s). It is strongly RECOMMENDED that
the documentation for any security model which is used
to authenticate community-based SNMP messages specify
the precise conditions that contribute to this value."
::= { snmp 4 }
snmpInBadCommunityUses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of community-based SNMP messages (for
example, SNMPv1) delivered to the SNMP entity which
represented an SNMP operation that was not allowed for
the SNMP community named in the message. The precise
conditions under which this counter is incremented
(if at all) depend on how the SNMP entity implements
its access control mechanism and how its applications
interact with that access control mechanism. It is
strongly RECOMMENDED that the documentation for any
access control mechanism which is used to control access
to and visibility of MIB instrumentation specify the
precise conditions that contribute to this value."
::= { snmp 5 }
snmpInASNParseErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of ASN.1 or BER errors encountered by
the SNMP entity when decoding received SNMP messages."
::= { snmp 6 }
snmpEnableAuthenTraps OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the SNMP entity is permitted to
generate authenticationFailure traps. The value of this
object overrides any configuration information; as such,
it provides a means whereby all authenticationFailure
traps may be disabled.
Note that it is strongly recommended that this object
be stored in non-volatile memory so that it remains
constant across re-initializations of the network
management system."
::= { snmp 30 }
snmpSilentDrops OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Confirmed Class PDUs (such as
GetRequest-PDUs, GetNextRequest-PDUs,
GetBulkRequest-PDUs, SetRequest-PDUs, and
InformRequest-PDUs) delivered to the SNMP entity which
were silently dropped because the size of a reply
containing an alternate Response Class PDU (such as a
Response-PDU) with an empty variable-bindings field
was greater than either a local constraint or the
maximum message size associated with the originator of
the request."
::= { snmp 31 }
snmpProxyDrops OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Confirmed Class PDUs
(such as GetRequest-PDUs, GetNextRequest-PDUs,
GetBulkRequest-PDUs, SetRequest-PDUs, and
InformRequest-PDUs) delivered to the SNMP entity which
were silently dropped because the transmission of
the (possibly translated) message to a proxy target
failed in a manner (other than a time-out) such that
no Response Class PDU (such as a Response-PDU) could
be returned."
::= { snmp 32 }
-- information for notifications
--
-- a collection of objects which allow the SNMP entity, when
-- supporting a notification originator application,
-- to be configured to generate SNMPv2-Trap-PDUs.
snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 }
snmpTrapOID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The authoritative identification of the notification
currently being sent. This variable occurs as
the second varbind in every SNMPv2-Trap-PDU and
InformRequest-PDU."
::= { snmpTrap 1 }
-- ::= { snmpTrap 2 } this OID is obsolete
snmpTrapEnterprise OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The authoritative identification of the enterprise
associated with the trap currently being sent. When an
SNMP proxy agent is mapping an RFC1157 Trap-PDU
into a SNMPv2-Trap-PDU, this variable occurs as the
last varbind."
::= { snmpTrap 3 }
-- ::= { snmpTrap 4 } this OID is obsolete
-- well-known traps
snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 }
coldStart NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"A coldStart trap signifies that the SNMP entity,
supporting a notification originator application, is
reinitializing itself and that its configuration may
have been altered."
::= { snmpTraps 1 }
warmStart NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"A warmStart trap signifies that the SNMP entity,
supporting a notification originator application,
is reinitializing itself such that its configuration
is unaltered."
::= { snmpTraps 2 }
-- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 }
-- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 }
-- are defined in RFC 2863 [RFC2863]
authenticationFailure NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"An authenticationFailure trap signifies that the SNMP
entity has received a protocol message that is not
properly authenticated. While all implementations
of SNMP entities MAY be capable of generating this
trap, the snmpEnableAuthenTraps object indicates
whether this trap will be generated."
::= { snmpTraps 5 }
-- Note the egpNeighborLoss notification is defined
-- as { snmpTraps 6 } in RFC 1213
-- the set group
--
-- a collection of objects which allow several cooperating
-- command generator applications to coordinate their use of the
-- set operation.
snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 }
snmpSetSerialNo OBJECT-TYPE
SYNTAX TestAndIncr
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An advisory lock used to allow several cooperating
command generator applications to coordinate their
use of the SNMP set operation.
This object is used for coarse-grain coordination.
To achieve fine-grain coordination, one or more similar
objects might be defined within each MIB group, as
appropriate."
::= { snmpSet 1 }
-- conformance information
snmpMIBConformance
OBJECT IDENTIFIER ::= { snmpMIB 2 }
snmpMIBCompliances
OBJECT IDENTIFIER ::= { snmpMIBConformance 1 }
snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 }
-- compliance statements
-- ::= { snmpMIBCompliances 1 } this OID is obsolete
snmpBasicCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the SNMPv2 MIB.
This compliance statement is replaced by
snmpBasicComplianceRev2."
MODULE -- this module
MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
snmpBasicNotificationsGroup }
GROUP snmpCommunityGroup
DESCRIPTION
"This group is mandatory for SNMPv2 entities which
support community-based authentication."
::= { snmpMIBCompliances 2 }
snmpBasicComplianceRev2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which
implement this MIB module."
MODULE -- this module
MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
snmpBasicNotificationsGroup }
GROUP snmpCommunityGroup
DESCRIPTION
"This group is mandatory for SNMP entities which
support community-based authentication."
GROUP snmpWarmStartNotificationGroup
DESCRIPTION
"This group is mandatory for an SNMP entity which
supports command responder applications, and is
able to reinitialize itself such that its
configuration is unaltered."
::= { snmpMIBCompliances 3 }
-- units of conformance
-- ::= { snmpMIBGroups 1 } this OID is obsolete
-- ::= { snmpMIBGroups 2 } this OID is obsolete
-- ::= { snmpMIBGroups 3 } this OID is obsolete
-- ::= { snmpMIBGroups 4 } this OID is obsolete
snmpGroup OBJECT-GROUP
OBJECTS { snmpInPkts,
snmpInBadVersions,
snmpInASNParseErrs,
snmpSilentDrops,
snmpProxyDrops,
snmpEnableAuthenTraps }
STATUS current
DESCRIPTION
"A collection of objects providing basic instrumentation
and control of an SNMP entity."
::= { snmpMIBGroups 8 }
snmpCommunityGroup OBJECT-GROUP
OBJECTS { snmpInBadCommunityNames,
snmpInBadCommunityUses }
STATUS current
DESCRIPTION
"A collection of objects providing basic instrumentation
of a SNMP entity which supports community-based
authentication."
::= { snmpMIBGroups 9 }
snmpSetGroup OBJECT-GROUP
OBJECTS { snmpSetSerialNo }
STATUS current
DESCRIPTION
"A collection of objects which allow several cooperating
command generator applications to coordinate their
use of the set operation."
::= { snmpMIBGroups 5 }
systemGroup OBJECT-GROUP
OBJECTS { sysDescr, sysObjectID, sysUpTime,
sysContact, sysName, sysLocation,
sysServices,
sysORLastChange, sysORID,
sysORUpTime, sysORDescr }
STATUS current
DESCRIPTION
"The system group defines objects which are common to all
managed systems."
::= { snmpMIBGroups 6 }
snmpBasicNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { coldStart, authenticationFailure }
STATUS current
DESCRIPTION
"The basic notifications implemented by an SNMP entity
supporting command responder applications."
::= { snmpMIBGroups 7 }
snmpWarmStartNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { warmStart }
STATUS current
DESCRIPTION
"An additional notification for an SNMP entity supporting
command responder applications, if it is able to reinitialize
itself such that its configuration is unaltered."
::= { snmpMIBGroups 11 }
snmpNotificationGroup OBJECT-GROUP
OBJECTS { snmpTrapOID, snmpTrapEnterprise }
STATUS current
DESCRIPTION
"These objects are required for entities
which support notification originator applications."
::= { snmpMIBGroups 12 }
-- definitions in RFC 1213 made obsolete by the inclusion of a
-- subset of the snmp group in this MIB
snmpOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Messages which were
passed from the SNMP protocol entity to the
transport service."
::= { snmp 2 }
-- { snmp 7 } is not used
snmpInTooBigs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field was
`tooBig'."
::= { snmp 8 }
snmpInNoSuchNames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field was
`noSuchName'."
::= { snmp 9 }
snmpInBadValues OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were
delivered to the SNMP protocol entity and for
which the value of the error-status field was
`badValue'."
::= { snmp 10 }
snmpInReadOnlys OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number valid SNMP PDUs which were delivered
to the SNMP protocol entity and for which the value
of the error-status field was `readOnly'. It should
be noted that it is a protocol error to generate an
SNMP PDU which contains the value `readOnly' in the
error-status field, as such this object is provided
as a means of detecting incorrect implementations of
the SNMP."
::= { snmp 11 }
snmpInGenErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were delivered
to the SNMP protocol entity and for which the value
of the error-status field was `genErr'."
::= { snmp 12 }
snmpInTotalReqVars OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of MIB objects which have been
retrieved successfully by the SNMP protocol entity
as the result of receiving valid SNMP Get-Request
and Get-Next PDUs."
::= { snmp 13 }
snmpInTotalSetVars OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of MIB objects which have been
altered successfully by the SNMP protocol entity as
the result of receiving valid SNMP Set-Request PDUs."
::= { snmp 14 }
snmpInGetRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Get-Request PDUs which
have been accepted and processed by the SNMP
protocol entity."
::= { snmp 15 }
snmpInGetNexts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Get-Next PDUs which have been
accepted and processed by the SNMP protocol entity."
::= { snmp 16 }
snmpInSetRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Set-Request PDUs which
have been accepted and processed by the SNMP protocol
entity."
::= { snmp 17 }
snmpInGetResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Get-Response PDUs which
have been accepted and processed by the SNMP protocol
entity."
::= { snmp 18 }
snmpInTraps OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Trap PDUs which have been
accepted and processed by the SNMP protocol entity."
::= { snmp 19 }
snmpOutTooBigs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were generated
by the SNMP protocol entity and for which the value
of the error-status field was `tooBig.'"
::= { snmp 20 }
snmpOutNoSuchNames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were generated
by the SNMP protocol entity and for which the value
of the error-status was `noSuchName'."
::= { snmp 21 }
snmpOutBadValues OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were generated
by the SNMP protocol entity and for which the value
of the error-status field was `badValue'."
::= { snmp 22 }
-- { snmp 23 } is not used
snmpOutGenErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP PDUs which were generated
by the SNMP protocol entity and for which the value
of the error-status field was `genErr'."
::= { snmp 24 }
snmpOutGetRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Get-Request PDUs which
have been generated by the SNMP protocol entity."
::= { snmp 25 }
snmpOutGetNexts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Get-Next PDUs which have
been generated by the SNMP protocol entity."
::= { snmp 26 }
snmpOutSetRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Set-Request PDUs which
have been generated by the SNMP protocol entity."
::= { snmp 27 }
snmpOutGetResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Get-Response PDUs which
have been generated by the SNMP protocol entity."
::= { snmp 28 }
snmpOutTraps OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS obsolete
DESCRIPTION
"The total number of SNMP Trap PDUs which have
been generated by the SNMP protocol entity."
::= { snmp 29 }
snmpObsoleteGroup OBJECT-GROUP
OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames,
snmpInBadValues, snmpInReadOnlys, snmpInGenErrs,
snmpInTotalReqVars, snmpInTotalSetVars,
snmpInGetRequests, snmpInGetNexts, snmpInSetRequests,
snmpInGetResponses, snmpInTraps, snmpOutTooBigs,
snmpOutNoSuchNames, snmpOutBadValues,
snmpOutGenErrs, snmpOutGetRequests, snmpOutGetNexts,
snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps
}
STATUS obsolete
DESCRIPTION
"A collection of objects from RFC 1213 made obsolete
by this MIB module."
::= { snmpMIBGroups 10 }
END
Icinga2/_Test/vSan Mib/vmw/SNMPv2-SMI.mib
+352
View File
@@ -0,0 +1,352 @@
SNMPv2-SMI DEFINITIONS ::= BEGIN
-- the path to the root
org OBJECT IDENTIFIER ::= { iso 3 } -- "iso" = 1
dod OBJECT IDENTIFIER ::= { org 6 }
internet OBJECT IDENTIFIER ::= { dod 1 }
directory OBJECT IDENTIFIER ::= { internet 1 }
mgmt OBJECT IDENTIFIER ::= { internet 2 }
mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
transmission OBJECT IDENTIFIER ::= { mib-2 10 }
experimental OBJECT IDENTIFIER ::= { internet 3 }
private OBJECT IDENTIFIER ::= { internet 4 }
enterprises OBJECT IDENTIFIER ::= { private 1 }
security OBJECT IDENTIFIER ::= { internet 5 }
snmpV2 OBJECT IDENTIFIER ::= { internet 6 }
-- transport domains
snmpDomains OBJECT IDENTIFIER ::= { snmpV2 1 }
-- transport proxies
snmpProxys OBJECT IDENTIFIER ::= { snmpV2 2 }
-- module identities
snmpModules OBJECT IDENTIFIER ::= { snmpV2 3 }
-- Extended UTCTime, to allow dates with four-digit years
-- (Note that this definition of ExtUTCTime is not to be IMPORTed
-- by MIB modules.)
ExtUTCTime ::= OCTET STRING(SIZE(11 | 13))
-- format is YYMMDDHHMMZ or YYYYMMDDHHMMZ
-- where: YY - last two digits of year (only years
-- between 1900-1999)
-- YYYY - last four digits of the year (any year)
-- MM - month (01 through 12)
-- DD - day of month (01 through 31)
-- HH - hours (00 through 23)
-- MM - minutes (00 through 59)
-- Z - denotes GMT (the ASCII character Z)
--
-- For example, "9502192015Z" and "199502192015Z" represent
-- 8:15pm GMT on 19 February 1995. Years after 1999 must use
-- the four digit year format. Years 1900-1999 may use the
-- two or four digit format.
-- definitions for information modules
MODULE-IDENTITY MACRO ::=
BEGIN
TYPE NOTATION ::=
"LAST-UPDATED" value(Update ExtUTCTime)
"ORGANIZATION" Text
"CONTACT-INFO" Text
"DESCRIPTION" Text
RevisionPart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
RevisionPart ::=
Revisions
| empty
Revisions ::=
Revision
| Revisions Revision
Revision ::=
"REVISION" value(Update ExtUTCTime)
"DESCRIPTION" Text
-- a character string as defined in section 3.1.1
Text ::= value(IA5String)
END
OBJECT-IDENTITY MACRO ::=
BEGIN
TYPE NOTATION ::=
"STATUS" Status
"DESCRIPTION" Text
ReferPart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in section 3.1.1
Text ::= value(IA5String)
END
-- names of objects
-- (Note that these definitions of ObjectName and NotificationName
-- are not to be IMPORTed by MIB modules.)
ObjectName ::=
OBJECT IDENTIFIER
NotificationName ::=
OBJECT IDENTIFIER
-- syntax of objects
-- the "base types" defined here are:
-- 3 built-in ASN.1 types: INTEGER, OCTET STRING, OBJECT IDENTIFIER
-- 8 application-defined types: Integer32, IpAddress, Counter32,
-- Gauge32, Unsigned32, TimeTicks, Opaque, and Counter64
ObjectSyntax ::=
CHOICE {
simple
SimpleSyntax,
-- note that SEQUENCEs for conceptual tables and
-- rows are not mentioned here...
application-wide
ApplicationSyntax
}
-- built-in ASN.1 types
SimpleSyntax ::=
CHOICE {
-- INTEGERs with a more restrictive range
-- may also be used
integer-value -- includes Integer32
INTEGER (-2147483648..2147483647),
-- OCTET STRINGs with a more restrictive size
-- may also be used
string-value
OCTET STRING (SIZE (0..65535)),
objectID-value
OBJECT IDENTIFIER
}
-- indistinguishable from INTEGER, but never needs more than
-- 32-bits for a two's complement representation
Integer32 ::=
INTEGER (-2147483648..2147483647)
-- application-wide types
ApplicationSyntax ::=
CHOICE {
ipAddress-value
IpAddress,
counter-value
Counter32,
timeticks-value
TimeTicks,
arbitrary-value
Opaque,
big-counter-value
Counter64,
unsigned-integer-value -- includes Gauge32
Unsigned32
}
-- in network-byte order
-- (this is a tagged type for historical reasons)
IpAddress ::=
[APPLICATION 0]
IMPLICIT OCTET STRING (SIZE (4))
-- this wraps
Counter32 ::=
[APPLICATION 1]
IMPLICIT INTEGER (0..4294967295)
-- this doesn't wrap
Gauge32 ::=
[APPLICATION 2]
IMPLICIT INTEGER (0..4294967295)
-- an unsigned 32-bit quantity
-- indistinguishable from Gauge32
Unsigned32 ::=
[APPLICATION 2]
IMPLICIT INTEGER (0..4294967295)
-- hundredths of seconds since an epoch
TimeTicks ::=
[APPLICATION 3]
IMPLICIT INTEGER (0..4294967295)
-- for backward-compatibility only
Opaque ::=
[APPLICATION 4]
IMPLICIT OCTET STRING
-- for counters that wrap in less than one hour with only 32 bits
Counter64 ::=
[APPLICATION 6]
IMPLICIT INTEGER (0..18446744073709551615)
-- definition for objects
OBJECT-TYPE MACRO ::=
BEGIN
TYPE NOTATION ::=
"SYNTAX" Syntax
UnitsPart
"MAX-ACCESS" Access
"STATUS" Status
"DESCRIPTION" Text
ReferPart
IndexPart
DefValPart
VALUE NOTATION ::=
value(VALUE ObjectName)
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement),
-- a textual convention (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative
UnitsPart ::=
"UNITS" Text
| empty
Access ::=
"not-accessible"
| "accessible-for-notify"
| "read-only"
| "read-write"
| "read-create"
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
IndexPart ::=
"INDEX" "{" IndexTypes "}"
| "AUGMENTS" "{" Entry "}"
| empty
IndexTypes ::=
IndexType
| IndexTypes "," IndexType
IndexType ::=
"IMPLIED" Index
| Index
Index ::=
-- use the SYNTAX value of the
-- correspondent OBJECT-TYPE invocation
value(ObjectName)
Entry ::=
-- use the INDEX value of the
-- correspondent OBJECT-TYPE invocation
value(ObjectName)
DefValPart ::= "DEFVAL" "{" Defvalue "}"
| empty
Defvalue ::= -- must be valid for the type specified in
-- SYNTAX clause of same OBJECT-TYPE macro
value(ObjectSyntax)
| "{" BitsValue "}"
BitsValue ::= BitNames
| empty
BitNames ::= BitName
| BitNames "," BitName
BitName ::= identifier
-- a character string as defined in section 3.1.1
Text ::= value(IA5String)
END
-- definitions for notifications
NOTIFICATION-TYPE MACRO ::=
BEGIN
TYPE NOTATION ::=
ObjectsPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
VALUE NOTATION ::=
value(VALUE NotificationName)
ObjectsPart ::=
"OBJECTS" "{" Objects "}"
| empty
Objects ::=
Object
| Objects "," Object
Object ::=
value(ObjectName)
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in section 3.1.1
Text ::= value(IA5String)
END
-- definitions of administrative identifiers
zeroDotZero OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A value used for null identifiers."
::= { 0 0 }
END
Icinga2/_Test/vSan Mib/vmw/SNMPv2-TC.mib
+786
View File
@@ -0,0 +1,786 @@
SNMPv2-TC DEFINITIONS ::= BEGIN
IMPORTS
TimeTicks FROM SNMPv2-SMI;
-- definition of textual conventions
TEXTUAL-CONVENTION MACRO ::=
BEGIN
TYPE NOTATION ::=
DisplayPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
"SYNTAX" Syntax
VALUE NOTATION ::=
value(VALUE Syntax) -- adapted ASN.1
DisplayPart ::=
"DISPLAY-HINT" Text
| empty
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in [2]
Text ::= value(IA5String)
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative
END
DisplayString ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
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.)
Any object defined using this syntax may not exceed 255
characters in length."
SYNTAX OCTET STRING (SIZE (0..255))
PhysAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"Represents media- or physical-level addresses."
SYNTAX OCTET STRING
MacAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x:"
STATUS current
DESCRIPTION
"Represents an 802 MAC address represented in the
`canonical' order defined by IEEE 802.1a, i.e., as if it
were transmitted least significant bit first, even though
802.5 (in contrast to other 802.x protocols) requires MAC
addresses to be transmitted most significant bit first."
SYNTAX OCTET STRING (SIZE (6))
TruthValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a boolean value."
SYNTAX INTEGER { true(1), false(2) }
TestAndIncr ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents integer-valued information used for atomic
operations. When the management protocol is used to specify
that an object instance having this syntax is to be
modified, the new value supplied via the management protocol
must precisely match the value presently held by the
instance. If not, the management protocol set operation
fails with an error of `inconsistentValue'. Otherwise, if
the current value is the maximum value of 2^31-1 (2147483647
decimal), then the value held by the instance is wrapped to
zero; otherwise, the value held by the instance is
incremented by one. (Note that regardless of whether the
management protocol set operation succeeds, the variable-
binding in the request and response PDUs are identical.)
The value of the ACCESS clause for objects having this
syntax is either `read-write' or `read-create'. When an
instance of a columnar object having this syntax is created,
any value may be supplied via the management protocol.
When the network management portion of the system is re-
initialized, the value of every object instance having this
syntax must either be incremented from its value prior to
the re-initialization, or (if the value prior to the re-
initialization is unknown) be set to a pseudo-randomly
generated value."
SYNTAX INTEGER (0..2147483647)
AutonomousType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents an independently extensible type identification
value. It may, for example, indicate a particular sub-tree
with further MIB definitions, or define a particular type of
protocol or hardware."
SYNTAX OBJECT IDENTIFIER
InstancePointer ::= TEXTUAL-CONVENTION
STATUS obsolete
DESCRIPTION
"A pointer to either a specific instance of a MIB object or
a conceptual row of a MIB table in the managed device. In
the latter case, by convention, it is the name of the
particular instance of the first accessible columnar object
in the conceptual row.
The two uses of this textual convention are replaced by
VariablePointer and RowPointer, respectively."
SYNTAX OBJECT IDENTIFIER
VariablePointer ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A pointer to a specific object instance. For example,
sysContact.0 or ifInOctets.3."
SYNTAX OBJECT IDENTIFIER
RowPointer ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a pointer to a conceptual row. The value is the
name of the instance of the first accessible columnar object
in the conceptual row.
For example, ifIndex.3 would point to the 3rd row in the
ifTable (note that if ifIndex were not-accessible, then
ifDescr.3 would be used instead)."
SYNTAX OBJECT IDENTIFIER
RowStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of [2].)
The status column has six defined values:
- `active', which indicates that the conceptual row is
available for use by the managed device;
- `notInService', which indicates that the conceptual
row exists in the agent, but is unavailable for use by
the managed device (see NOTE below); 'notInService' has
no implication regarding the internal consistency of
the row, availability of resources, or consistency with
the current state of the managed device;
- `notReady', which indicates that the conceptual row
exists in the agent, but is missing information
necessary in order to be available for use by the
managed device (i.e., one or more required columns in
the conceptual row have not been instanciated);
- `createAndGo', which is supplied by a management
station wishing to create a new instance of a
conceptual row and to have its status automatically set
to active, making it available for use by the managed
device;
- `createAndWait', which is supplied by a management
station wishing to create a new instance of a
conceptual row (but not make it available for use by
the managed device); and,
- `destroy', which is supplied by a management station
wishing to delete all of the instances associated with
an existing conceptual row.
Whereas five of the six values (all except `notReady') may
be specified in a management protocol set operation, only
three values will be returned in response to a management
protocol retrieval operation: `notReady', `notInService' or
`active'. That is, when queried, an existing conceptual row
has only three states: it is either available for use by
the managed device (the status column has value `active');
it is not available for use by the managed device, though
the agent has sufficient information to attempt to make it
so (the status column has value `notInService'); or, it is
not available for use by the managed device, and an attempt
to make it so would fail because the agent has insufficient
information (the state column has value `notReady').
NOTE WELL
This textual convention may be used for a MIB table,
irrespective of whether the values of that table's
conceptual rows are able to be modified while it is
active, or whether its conceptual rows must be taken
out of service in order to be modified. That is, it is
the responsibility of the DESCRIPTION clause of the
status column to specify whether the status column must
not be `active' in order for the value of some other
column of the same conceptual row to be modified. If
such a specification is made, affected columns may be
changed by an SNMP set PDU if the RowStatus would not
be equal to `active' either immediately before or after
processing the PDU. In other words, if the PDU also
contained a varbind that would change the RowStatus
value, the column in question may be changed if the
RowStatus was not equal to `active' as the PDU was
received, or if the varbind sets the status to a value
other than 'active'.
Also note that whenever any elements of a row exist, the
RowStatus column must also exist.
To summarize the effect of having a conceptual row with a
status column having a SYNTAX clause value of RowStatus,
consider the following state diagram:
STATE
+--------------+-----------+-------------+-------------
| A | B | C | D
| |status col.|status column|
|status column | is | is |status column
ACTION |does not exist| notReady | notInService| is active
--------------+--------------+-----------+-------------+-------------
set status |noError ->D|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndGo |inconsistent- | | |
| Value| | |
--------------+--------------+-----------+-------------+-------------
set status |noError see 1|inconsist- |inconsistent-|inconsistent-
column to | or | entValue| Value| Value
createAndWait |wrongValue | | |
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError
column to | Value| entValue| |
active | | | |
| | or | |
| | | |
| |see 2 ->D|see 8 ->D| ->D
--------------+--------------+-----------+-------------+-------------
set status |inconsistent- |inconsist- |noError |noError ->C
column to | Value| entValue| |
notInService | | | |
| | or | | or
| | | |
| |see 3 ->C| ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status |noError |noError |noError |noError ->A
column to | | | | or
destroy | ->A| ->A| ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4 |noError |noError |see 5
column to some| | | |
value | | see 1| ->C| ->D
--------------+--------------+-----------+-------------+-------------
(1) goto B or C, depending on information available to the
agent.
(2) if other variable bindings included in the same PDU,
provide values for all columns which are missing but
required, and all columns have acceptable values, then
return noError and goto D.
(3) if other variable bindings included in the same PDU,
provide legal values for all columns which are missing but
required, then return noError and goto C.
(4) at the discretion of the agent, the return value may be
either:
inconsistentName: because the agent does not choose to
create such an instance when the corresponding
RowStatus instance does not exist, or
inconsistentValue: if the supplied value is
inconsistent with the state of some other MIB object's
value, or
noError: because the agent chooses to create the
instance.
If noError is returned, then the instance of the status
column must also be created, and the new state is B or C,
depending on the information available to the agent. If
inconsistentName or inconsistentValue is returned, the row
remains in state A.
(5) depending on the MIB definition for the column/table,
either noError or inconsistentValue may be returned.
(6) the return value can indicate one of the following
errors:
wrongValue: because the agent does not support
notInService (e.g., an agent which does not support
createAndWait), or
inconsistentValue: because the agent is unable to take
the row out of service at this time, perhaps because it
is in use and cannot be de-activated.
(7) the return value can indicate the following error:
inconsistentValue: because the agent is unable to
remove the row at this time, perhaps because it is in
use and cannot be de-activated.
(8) the transition to D can fail, e.g., if the values of the
conceptual row are inconsistent, then the error code would
be inconsistentValue.
NOTE: Other processing of (this and other varbinds of) the
set request may result in a response other than noError
being returned, e.g., wrongValue, noCreation, etc.
Conceptual Row Creation
There are four potential interactions when creating a
conceptual row: selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any
objects for which the agent does not supply a default; and,
making the conceptual row available for use by the managed
device.
Interaction 1: Selecting an Instance-Identifier
The algorithm used to select an instance-identifier varies
for each conceptual row. In some cases, the instance-
identifier is semantically significant, e.g., the
destination address of a route, and a management station
selects the instance-identifier according to the semantics.
In other cases, the instance-identifier is used solely to
distinguish conceptual rows, and a management station
without specific knowledge of the conceptual row might
examine the instances present in order to determine an
unused instance-identifier. (This approach may be used, but
it is often highly sub-optimal; however, it is also a
questionable practice for a naive management station to
attempt conceptual row creation.)
Alternately, the MIB module which defines the conceptual row
might provide one or more objects which provide assistance
in determining an unused instance-identifier. For example,
if the conceptual row is indexed by an integer-value, then
an object having an integer-valued SYNTAX clause might be
defined for such a purpose, allowing a management station to
issue a management protocol retrieval operation. In order
to avoid unnecessary collisions between competing management
stations, `adjacent' retrievals of this object should be
different.
Finally, the management station could select a pseudo-random
number to use as the index. In the event that this index
was already in use and an inconsistentValue was returned in
response to the management protocol set operation, the
management station should simply select a new pseudo-random
number and retry the operation.
A MIB designer should choose between the two latter
algorithms based on the size of the table (and therefore the
efficiency of each algorithm). For tables in which a large
number of entries are expected, it is recommended that a MIB
object be defined that returns an acceptable index for
creation. For tables with small numbers of entries, it is
recommended that the latter pseudo-random index mechanism be
used.
Interaction 2: Creating the Conceptual Row
Once an unused instance-identifier has been selected, the
management station determines if it wishes to create and
activate the conceptual row in one transaction or in a
negotiated set of interactions.
Interaction 2a: Creating and Activating the Conceptual Row
The management station must first determine the column
requirements, i.e., it must determine those columns for
which it must or must not provide values. Depending on the
complexity of the table and the management station's
knowledge of the agent's capabilities, this determination
can be made locally by the management station. Alternately,
the management station issues a management protocol get
operation to examine all columns in the conceptual row that
it wishes to create. In response, for each column, there
are three possible outcomes:
- a value is returned, indicating that some other
management station has already created this conceptual
row. We return to interaction 1.
- the exception `noSuchInstance' is returned,
indicating that the agent implements the object-type
associated with this column, and that this column in at
least one conceptual row would be accessible in the MIB
view used by the retrieval were it to exist. For those
columns to which the agent provides read-create access,
the `noSuchInstance' exception tells the management
station that it should supply a value for this column
when the conceptual row is to be created.
- the exception `noSuchObject' is returned, indicating
that the agent does not implement the object-type
associated with this column or that there is no
conceptual row for which this column would be
accessible in the MIB view used by the retrieval. As
such, the management station can not issue any
management protocol set operations to create an
instance of this column.
Once the column requirements have been determined, a
management protocol set operation is accordingly issued.
This operation also sets the new instance of the status
column to `createAndGo'.
When the agent processes the set operation, it verifies that
it has sufficient information to make the conceptual row
available for use by the managed device. The information
available to the agent is provided by two sources: the
management protocol set operation which creates the
conceptual row, and, implementation-specific defaults
supplied by the agent (note that an agent must provide
implementation-specific defaults for at least those objects
which it implements as read-only). If there is sufficient
information available, then the conceptual row is created, a
`noError' response is returned, the status column is set to
`active', and no further interactions are necessary (i.e.,
interactions 3 and 4 are skipped). If there is insufficient
information, then the conceptual row is not created, and the
set operation fails with an error of `inconsistentValue'.
On this error, the management station can issue a management
protocol retrieval operation to determine if this was
because it failed to specify a value for a required column,
or, because the selected instance of the status column
already existed. In the latter case, we return to
interaction 1. In the former case, the management station
can re-issue the set operation with the additional
information, or begin interaction 2 again using
`createAndWait' in order to negotiate creation of the
conceptual row.
NOTE WELL
Regardless of the method used to determine the column
requirements, it is possible that the management
station might deem a column necessary when, in fact,
the agent will not allow that particular columnar
instance to be created or written. In this case, the
management protocol set operation will fail with an
error such as `noCreation' or `notWritable'. In this
case, the management station decides whether it needs
to be able to set a value for that particular columnar
instance. If not, the management station re-issues the
management protocol set operation, but without setting
a value for that particular columnar instance;
otherwise, the management station aborts the row
creation algorithm.
Interaction 2b: Negotiating the Creation of the Conceptual
Row
The management station issues a management protocol set
operation which sets the desired instance of the status
column to `createAndWait'. If the agent is unwilling to
process a request of this sort, the set operation fails with
an error of `wrongValue'. (As a consequence, such an agent
must be prepared to accept a single management protocol set
operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.) Otherwise,
the conceptual row is created, a `noError' response is
returned, and the status column is immediately set to either
`notInService' or `notReady', depending on whether it has
sufficient information to (attempt to) make the conceptual
row available for use by the managed device. If there is
sufficient information available, then the status column is
set to `notInService'; otherwise, if there is insufficient
information, then the status column is set to `notReady'.
Regardless, we proceed to interaction 3.
Interaction 3: Initializing non-defaulted Objects
The management station must now determine the column
requirements. It issues a management protocol get operation
to examine all columns in the created conceptual row. In
the response, for each column, there are three possible
outcomes:
- a value is returned, indicating that the agent
implements the object-type associated with this column
and had sufficient information to provide a value. For
those columns to which the agent provides read-create
access (and for which the agent allows their values to
be changed after their creation), a value return tells
the management station that it may issue additional
management protocol set operations, if it desires, in
order to change the value associated with this column.
- the exception `noSuchInstance' is returned,
indicating that the agent implements the object-type
associated with this column, and that this column in at
least one conceptual row would be accessible in the MIB
view used by the retrieval were it to exist. However,
the agent does not have sufficient information to
provide a value, and until a value is provided, the
conceptual row may not be made available for use by the
managed device. For those columns to which the agent
provides read-create access, the `noSuchInstance'
exception tells the management station that it must
issue additional management protocol set operations, in
order to provide a value associated with this column.
- the exception `noSuchObject' is returned, indicating
that the agent does not implement the object-type
associated with this column or that there is no
conceptual row for which this column would be
accessible in the MIB view used by the retrieval. As
such, the management station can not issue any
management protocol set operations to create an
instance of this column.
If the value associated with the status column is
`notReady', then the management station must first deal with
all `noSuchInstance' columns, if any. Having done so, the
value of the status column becomes `notInService', and we
proceed to interaction 4.
Interaction 4: Making the Conceptual Row Available
Once the management station is satisfied with the values
associated with the columns of the conceptual row, it issues
a management protocol set operation to set the status column
to `active'. If the agent has sufficient information to
make the conceptual row available for use by the managed
device, the management protocol set operation succeeds (a
`noError' response is returned). Otherwise, the management
protocol set operation fails with an error of
`inconsistentValue'.
NOTE WELL
A conceptual row having a status column with value
`notInService' or `notReady' is unavailable to the
managed device. As such, it is possible for the
managed device to create its own instances during the
time between the management protocol set operation
which sets the status column to `createAndWait' and the
management protocol set operation which sets the status
column to `active'. In this case, when the management
protocol set operation is issued to set the status
column to `active', the values held in the agent
supersede those used by the managed device.
If the management station is prevented from setting the
status column to `active' (e.g., due to management station
or network failure) the conceptual row will be left in the
`notInService' or `notReady' state, consuming resources
indefinitely. The agent must detect conceptual rows that
have been in either state for an abnormally long period of
time and remove them. It is the responsibility of the
DESCRIPTION clause of the status column to indicate what an
abnormally long period of time would be. This period of
time should be long enough to allow for human response time
(including `think time') between the creation of the
conceptual row and the setting of the status to `active'.
In the absence of such information in the DESCRIPTION
clause, it is suggested that this period be approximately 5
minutes in length. This removal action applies not only to
newly-created rows, but also to previously active rows which
are set to, and left in, the notInService state for a
prolonged period exceeding that which is considered normal
for such a conceptual row.
Conceptual Row Suspension
When a conceptual row is `active', the management station
may issue a management protocol set operation which sets the
instance of the status column to `notInService'. If the
agent is unwilling to do so, the set operation fails with an
error of `wrongValue' or `inconsistentValue'. Otherwise,
the conceptual row is taken out of service, and a `noError'
response is returned. It is the responsibility of the
DESCRIPTION clause of the status column to indicate under
what circumstances the status column should be taken out of
service (e.g., in order for the value of some other column
of the same conceptual row to be modified).
Conceptual Row Deletion
For deletion of conceptual rows, a management protocol set
operation is issued which sets the instance of the status
column to `destroy'. This request may be made regardless of
the current value of the status column (e.g., it is possible
to delete conceptual rows which are either `notReady',
`notInService' or `active'.) If the operation succeeds,
then all instances associated with the conceptual row are
immediately removed."
SYNTAX INTEGER {
-- the following two values are states:
-- these values may be read or written
active(1),
notInService(2),
-- the following value is a state:
-- this value may be read, but not written
notReady(3),
-- the following three values are
-- actions: these values may be written,
-- but are never read
createAndGo(4),
createAndWait(5),
destroy(6)
}
TimeStamp ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of the sysUpTime object at which a specific
occurrence happened. The specific occurrence must be
defined in the description of any object defined using this
type.
If sysUpTime is reset to zero as a result of a re-
initialization of the network management (sub)system, then
the values of all TimeStamp objects are also reset.
However, after approximately 497 days without a re-
initialization, the sysUpTime object will reach 2^^32-1 and
then increment around to zero; in this case, existing values
of TimeStamp objects do not change. This can lead to
ambiguities in the value of TimeStamp objects."
SYNTAX TimeTicks
TimeInterval ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A period of time, measured in units of 0.01 seconds."
SYNTAX INTEGER (0..2147483647)
DateAndTime ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"
STATUS current
DESCRIPTION
"A date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes:
- the value of year is in network-byte order
- daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone
information (fields 8-10) is not present."
SYNTAX OCTET STRING (SIZE (8 | 11))
StorageType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Describes the memory realization of a conceptual row. A
row which is volatile(2) is lost upon reboot. A row which
is either nonVolatile(3), permanent(4) or readOnly(5), is
backed up by stable storage. A row which is permanent(4)
can be changed but not deleted. A row which is readOnly(5)
cannot be changed nor deleted.
If the value of an object with this syntax is either
permanent(4) or readOnly(5), it cannot be written.
Conversely, if the value is either other(1), volatile(2) or
nonVolatile(3), it cannot be modified to be permanent(4) or
readOnly(5). (All illegal modifications result in a
'wrongValue' error.)
Every usage of this textual convention is required to
specify the columnar objects which a permanent(4) row must
at a minimum allow to be writable."
SYNTAX INTEGER {
other(1), -- eh?
volatile(2), -- e.g., in RAM
nonVolatile(3), -- e.g., in NVRAM
permanent(4), -- e.g., partially in ROM
readOnly(5) -- e.g., completely in ROM
}
TDomain ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a kind of transport service.
Some possible values, such as snmpUDPDomain, are defined in
the SNMPv2-TM MIB module. Other possible values are defined
in other MIB modules."
REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
SYNTAX OBJECT IDENTIFIER
TAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a transport service address.
A TAddress value is always interpreted within the context of a
TDomain value. Thus, each definition of a TDomain value must
be accompanied by a definition of a textual convention for use
with that TDomain. Some possible textual conventions, such as
SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM
MIB module. Other possible textual conventions are defined in
other MIB modules."
REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
SYNTAX OCTET STRING (SIZE (1..255))
END
Icinga2/_Test/vSan Mib/vmw/TCP-MIB.mib
+830
View File
@@ -0,0 +1,830 @@
-- http://www.ietf.org/rfc/rfc4022.txt
TCP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32,
Gauge32, Counter32, Counter64, IpAddress, mib-2
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
InetAddress, InetAddressType,
InetPortNumber FROM INET-ADDRESS-MIB;
tcpMIB MODULE-IDENTITY
LAST-UPDATED "200502180000Z" -- 18 February 2005
ORGANIZATION
"IETF IPv6 MIB Revision Team
http://www.ietf.org/html.charters/ipv6-charter.html"
CONTACT-INFO
"Rajiv Raghunarayan (editor)
Cisco Systems Inc.
170 West Tasman Drive
San Jose, CA 95134
Phone: +1 408 853 9612
Email: <raraghun@cisco.com>
Send comments to <ipv6@ietf.org>"
DESCRIPTION
"The MIB module for managing TCP implementations.
Copyright (C) The Internet Society (2005). This version
of this MIB module is a part of RFC 4022; see the RFC
itself for full legal notices."
REVISION "200502180000Z" -- 18 February 2005
DESCRIPTION
"IP version neutral revision, published as RFC 4022."
REVISION "9411010000Z"
DESCRIPTION
"Initial SMIv2 version, published as RFC 2012."
REVISION "9103310000Z"
DESCRIPTION
"The initial revision of this MIB module was part of
MIB-II."
::= { mib-2 49 }
-- the TCP base variables group
tcp OBJECT IDENTIFIER ::= { mib-2 6 }
-- Scalars
tcpRtoAlgorithm OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- none of the following
constant(2), -- a constant rto
rsre(3), -- MIL-STD-1778, Appendix B
vanj(4), -- Van Jacobson's algorithm
rfc2988(5) -- RFC 2988
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The algorithm used to determine the timeout value used for
retransmitting unacknowledged octets."
::= { tcp 1 }
tcpRtoMin OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum value permitted by a TCP implementation for
the retransmission timeout, measured in milliseconds.
More refined semantics for objects of this type depend
on the algorithm used to determine the retransmission
timeout; in particular, the IETF standard algorithm
rfc2988(5) provides a minimum value."
::= { tcp 2 }
tcpRtoMax OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value permitted by a TCP implementation for
the retransmission timeout, measured in milliseconds.
More refined semantics for objects of this type depend
on the algorithm used to determine the retransmission
timeout; in particular, the IETF standard algorithm
rfc2988(5) provides an upper bound (as part of an
adaptive backoff algorithm)."
::= { tcp 3 }
tcpMaxConn OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The limit on the total number of TCP connections the entity
can support. In entities where the maximum number of
connections is dynamic, this object should contain the
value -1."
::= { tcp 4 }
tcpActiveOpens OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that TCP connections have made a direct
transition to the SYN-SENT state from the CLOSED state.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 5 }
tcpPassiveOpens OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times TCP connections have made a direct
transition to the SYN-RCVD state from the LISTEN state.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 6 }
tcpAttemptFails OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that TCP connections have made a direct
transition to the CLOSED state from either the SYN-SENT
state or the SYN-RCVD state, plus the number of times that
TCP connections have made a direct transition to the
LISTEN state from the SYN-RCVD state.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 7 }
tcpEstabResets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that TCP connections have made a direct
transition to the CLOSED state from either the ESTABLISHED
state or the CLOSE-WAIT state.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 8 }
tcpCurrEstab OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of TCP connections for which the current state
is either ESTABLISHED or CLOSE-WAIT."
::= { tcp 9 }
tcpInSegs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments received, including those
received in error. This count includes segments received
on currently established connections.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 10 }
tcpOutSegs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments sent, including those on
current connections but excluding those containing only
retransmitted octets.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 11 }
tcpRetransSegs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments retransmitted; that is, the
number of TCP segments transmitted containing one or more
previously transmitted octets.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 12 }
tcpInErrs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments received in error (e.g., bad
TCP checksums).
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 14 }
tcpOutRsts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of TCP segments sent containing the RST flag.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 15 }
-- { tcp 16 } was used to represent the ipv6TcpConnTable in RFC 2452,
-- which has since been obsoleted. It MUST not be used.
tcpHCInSegs OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments received, including those
received in error. This count includes segments received
on currently established connections. This object is
the 64-bit equivalent of tcpInSegs.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 17 }
tcpHCOutSegs OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of segments sent, including those on
current connections but excluding those containing only
retransmitted octets. This object is the 64-bit
equivalent of tcpOutSegs.
Discontinuities in the value of this counter are
indicated via discontinuities in the value of sysUpTime."
::= { tcp 18 }
-- The TCP Connection table
tcpConnectionTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpConnectionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information about existing TCP
connections. Note that unlike earlier TCP MIBs, there
is a separate table for connections in the LISTEN state."
::= { tcp 19 }
tcpConnectionEntry OBJECT-TYPE
SYNTAX TcpConnectionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row of the tcpConnectionTable containing
information about a particular current TCP connection.
Each row of this table is transient in that it ceases to
exist when (or soon after) the connection makes the
transition to the CLOSED state."
INDEX { tcpConnectionLocalAddressType,
tcpConnectionLocalAddress,
tcpConnectionLocalPort,
tcpConnectionRemAddressType,
tcpConnectionRemAddress,
tcpConnectionRemPort }
::= { tcpConnectionTable 1 }
TcpConnectionEntry ::= SEQUENCE {
tcpConnectionLocalAddressType InetAddressType,
tcpConnectionLocalAddress InetAddress,
tcpConnectionLocalPort InetPortNumber,
tcpConnectionRemAddressType InetAddressType,
tcpConnectionRemAddress InetAddress,
tcpConnectionRemPort InetPortNumber,
tcpConnectionState INTEGER,
tcpConnectionProcess Unsigned32
}
tcpConnectionLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type of tcpConnectionLocalAddress."
::= { tcpConnectionEntry 1 }
tcpConnectionLocalAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local IP address for this TCP connection. The type
of this address is determined by the value of
tcpConnectionLocalAddressType.
As this object is used in the index for the
tcpConnectionTable, implementors should be
careful not to create entries that would result in OIDs
with more than 128 subidentifiers; otherwise the information
cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3."
::= { tcpConnectionEntry 2 }
tcpConnectionLocalPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local port number for this TCP connection."
::= { tcpConnectionEntry 3 }
tcpConnectionRemAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type of tcpConnectionRemAddress."
::= { tcpConnectionEntry 4 }
tcpConnectionRemAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The remote IP address for this TCP connection. The type
of this address is determined by the value of
tcpConnectionRemAddressType.
As this object is used in the index for the
tcpConnectionTable, implementors should be
careful not to create entries that would result in OIDs
with more than 128 subidentifiers; otherwise the information
cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3."
::= { tcpConnectionEntry 5 }
tcpConnectionRemPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The remote port number for this TCP connection."
::= { tcpConnectionEntry 6 }
tcpConnectionState OBJECT-TYPE
SYNTAX INTEGER {
closed(1),
listen(2),
synSent(3),
synReceived(4),
established(5),
finWait1(6),
finWait2(7),
closeWait(8),
lastAck(9),
closing(10),
timeWait(11),
deleteTCB(12)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The state of this TCP connection.
The value listen(2) is included only for parallelism to the
old tcpConnTable and should not be used. A connection in
LISTEN state should be present in the tcpListenerTable.
The only value that may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an agent
to return a `badValue' response if a management station
attempts to set this object to any other value.
If a management station sets this object to the value
deleteTCB(12), then the TCB (as defined in [RFC793]) of
the corresponding connection on the managed node is
deleted, resulting in immediate termination of the
connection.
As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note,
however, that RST segments are not sent reliably)."
::= { tcpConnectionEntry 7 }
tcpConnectionProcess OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system's process ID for the process associated with
this connection, or zero if there is no such process. This
value is expected to be the same as HOST-RESOURCES-MIB::
hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some
row in the appropriate tables."
::= { tcpConnectionEntry 8 }
-- The TCP Listener table
tcpListenerTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information about TCP listeners. A
listening application can be represented in three
possible ways:
1. An application that is willing to accept both IPv4 and
IPv6 datagrams is represented by
a tcpListenerLocalAddressType of unknown (0) and
a tcpListenerLocalAddress of ''h (a zero-length
octet-string).
2. An application that is willing to accept only IPv4 or
IPv6 datagrams is represented by a
tcpListenerLocalAddressType of the appropriate address
type and a tcpListenerLocalAddress of '0.0.0.0' or '::'
respectively.
3. An application that is listening for data destined
only to a specific IP address, but from any remote
system, is represented by a tcpListenerLocalAddressType
of an appropriate address type, with
tcpListenerLocalAddress as the specific local address.
NOTE: The address type in this table represents the
address type used for the communication, irrespective
of the higher-layer abstraction. For example, an
application using IPv6 'sockets' to communicate via
IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would
use InetAddressType ipv4(1))."
::= { tcp 20 }
tcpListenerEntry OBJECT-TYPE
SYNTAX TcpListenerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A conceptual row of the tcpListenerTable containing
information about a particular TCP listener."
INDEX { tcpListenerLocalAddressType,
tcpListenerLocalAddress,
tcpListenerLocalPort }
::= { tcpListenerTable 1 }
TcpListenerEntry ::= SEQUENCE {
tcpListenerLocalAddressType InetAddressType,
tcpListenerLocalAddress InetAddress,
tcpListenerLocalPort InetPortNumber,
tcpListenerProcess Unsigned32
}
tcpListenerLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type of tcpListenerLocalAddress. The value
should be unknown (0) if connection initiations to all
local IP addresses are accepted."
::= { tcpListenerEntry 1 }
tcpListenerLocalAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local IP address for this TCP connection.
The value of this object can be represented in three
possible ways, depending on the characteristics of the
listening application:
1. For an application willing to accept both IPv4 and
IPv6 datagrams, the value of this object must be
''h (a zero-length octet-string), with the value
of the corresponding tcpListenerLocalAddressType
object being unknown (0).
2. For an application willing to accept only IPv4 or
IPv6 datagrams, the value of this object must be
'0.0.0.0' or '::' respectively, with
tcpListenerLocalAddressType representing the
appropriate address type.
3. For an application which is listening for data
destined only to a specific IP address, the value
of this object is the specific local address, with
tcpListenerLocalAddressType representing the
appropriate address type.
As this object is used in the index for the
tcpListenerTable, implementors should be
careful not to create entries that would result in OIDs
with more than 128 subidentifiers; otherwise the information
cannot be accessed, using SNMPv1, SNMPv2c, or SNMPv3."
::= { tcpListenerEntry 2 }
tcpListenerLocalPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local port number for this TCP connection."
::= { tcpListenerEntry 3 }
tcpListenerProcess OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system's process ID for the process associated with
this listener, or zero if there is no such process. This
value is expected to be the same as HOST-RESOURCES-MIB::
hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some
row in the appropriate tables."
::= { tcpListenerEntry 4 }
-- The deprecated TCP Connection table
tcpConnTable OBJECT-TYPE
SYNTAX SEQUENCE OF TcpConnEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"A table containing information about existing IPv4-specific
TCP connections or listeners. This table has been
deprecated in favor of the version neutral
tcpConnectionTable."
::= { tcp 13 }
tcpConnEntry OBJECT-TYPE
SYNTAX TcpConnEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"A conceptual row of the tcpConnTable containing information
about a particular current IPv4 TCP connection. Each row
of this table is transient in that it ceases to exist when
(or soon after) the connection makes the transition to the
CLOSED state."
INDEX { tcpConnLocalAddress,
tcpConnLocalPort,
tcpConnRemAddress,
tcpConnRemPort }
::= { tcpConnTable 1 }
TcpConnEntry ::= SEQUENCE {
tcpConnState INTEGER,
tcpConnLocalAddress IpAddress,
tcpConnLocalPort Integer32,
tcpConnRemAddress IpAddress,
tcpConnRemPort Integer32
}
tcpConnState OBJECT-TYPE
SYNTAX INTEGER {
closed(1),
listen(2),
synSent(3),
synReceived(4),
established(5),
finWait1(6),
finWait2(7),
closeWait(8),
lastAck(9),
closing(10),
timeWait(11),
deleteTCB(12)
}
MAX-ACCESS read-write
STATUS deprecated
DESCRIPTION
"The state of this TCP connection.
The only value that may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an agent
to return a `badValue' response if a management station
attempts to set this object to any other value.
If a management station sets this object to the value
deleteTCB(12), then the TCB (as defined in [RFC793]) of
the corresponding connection on the managed node is
deleted, resulting in immediate termination of the
connection.
As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note,
however, that RST segments are not sent reliably)."
::= { tcpConnEntry 1 }
tcpConnLocalAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The local IP address for this TCP connection. In the case
of a connection in the listen state willing to
accept connections for any IP interface associated with the
node, the value 0.0.0.0 is used."
::= { tcpConnEntry 2 }
tcpConnLocalPort OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The local port number for this TCP connection."
::= { tcpConnEntry 3 }
tcpConnRemAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The remote IP address for this TCP connection."
::= { tcpConnEntry 4 }
tcpConnRemPort OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The remote port number for this TCP connection."
::= { tcpConnEntry 5 }
-- conformance information
tcpMIBConformance OBJECT IDENTIFIER ::= { tcpMIB 2 }
tcpMIBCompliances OBJECT IDENTIFIER ::= { tcpMIBConformance 1 }
tcpMIBGroups OBJECT IDENTIFIER ::= { tcpMIBConformance 2 }
-- compliance statements
tcpMIBCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems that implement TCP.
A number of INDEX objects cannot be
represented in the form of OBJECT clauses in SMIv2 but
have the following compliance requirements,
expressed in OBJECT clause form in this description
clause:
-- OBJECT tcpConnectionLocalAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- This MIB requires support for only global IPv4
-- and IPv6 address types.
--
-- OBJECT tcpConnectionRemAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- This MIB requires support for only global IPv4
-- and IPv6 address types.
--
-- OBJECT tcpListenerLocalAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2) }
-- DESCRIPTION
-- This MIB requires support for only global IPv4
-- and IPv6 address types. The type unknown also
-- needs to be supported to identify a special
-- case in the listener table: a listen using
-- both IPv4 and IPv6 addresses on the device.
--
"
MODULE -- this module
MANDATORY-GROUPS { tcpBaseGroup, tcpConnectionGroup,
tcpListenerGroup }
GROUP tcpHCGroup
DESCRIPTION
"This group is mandatory for systems that are capable
of receiving or transmitting more than 1 million TCP
segments per second. 1 million segments per second will
cause a Counter32 to wrap in just over an hour."
OBJECT tcpConnectionState
SYNTAX INTEGER { closed(1), listen(2), synSent(3),
synReceived(4), established(5),
finWait1(6), finWait2(7), closeWait(8),
lastAck(9), closing(10), timeWait(11) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, nor is support for the value
deleteTCB (12)."
::= { tcpMIBCompliances 2 }
tcpMIBCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for IPv4-only systems that
implement TCP. In order to be IP version independent, this
compliance statement is deprecated in favor of
tcpMIBCompliance2. However, agents are still encouraged
to implement these objects in order to interoperate with
the deployed base of managers."
MODULE -- this module
MANDATORY-GROUPS { tcpGroup }
OBJECT tcpConnState
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { tcpMIBCompliances 1 }
-- units of conformance
tcpGroup OBJECT-GROUP
OBJECTS { tcpRtoAlgorithm, tcpRtoMin, tcpRtoMax,
tcpMaxConn, tcpActiveOpens,
tcpPassiveOpens, tcpAttemptFails,
tcpEstabResets, tcpCurrEstab, tcpInSegs,
tcpOutSegs, tcpRetransSegs, tcpConnState,
tcpConnLocalAddress, tcpConnLocalPort,
tcpConnRemAddress, tcpConnRemPort,
tcpInErrs, tcpOutRsts }
STATUS deprecated
DESCRIPTION
"The tcp group of objects providing for management of TCP
entities."
::= { tcpMIBGroups 1 }
tcpBaseGroup OBJECT-GROUP
OBJECTS { tcpRtoAlgorithm, tcpRtoMin, tcpRtoMax,
tcpMaxConn, tcpActiveOpens,
tcpPassiveOpens, tcpAttemptFails,
tcpEstabResets, tcpCurrEstab, tcpInSegs,
tcpOutSegs, tcpRetransSegs,
tcpInErrs, tcpOutRsts }
STATUS current
DESCRIPTION
"The group of counters common to TCP entities."
::= { tcpMIBGroups 2 }
tcpConnectionGroup OBJECT-GROUP
OBJECTS { tcpConnectionState, tcpConnectionProcess }
STATUS current
DESCRIPTION
"The group provides general information about TCP
connections."
::= { tcpMIBGroups 3 }
tcpListenerGroup OBJECT-GROUP
OBJECTS { tcpListenerProcess }
STATUS current
DESCRIPTION
"This group has objects providing general information about
TCP listeners."
::= { tcpMIBGroups 4 }
tcpHCGroup OBJECT-GROUP
OBJECTS { tcpHCInSegs, tcpHCOutSegs }
STATUS current
DESCRIPTION
"The group of objects providing for counters of high speed
TCP implementations."
::= { tcpMIBGroups 5 }
END
Icinga2/_Test/vSan Mib/vmw/TOKEN-RING-RMON-MIB.mib
+2565
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/UDP-MIB.mib
+580
View File
@@ -0,0 +1,580 @@
-- http://www.ietf.org/rfc/rfc4113.txt
UDP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, Counter64,
Unsigned32, IpAddress, mib-2 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
InetAddress, InetAddressType,
InetPortNumber FROM INET-ADDRESS-MIB;
udpMIB MODULE-IDENTITY
LAST-UPDATED "200505200000Z" -- May 20, 2005
ORGANIZATION
"IETF IPv6 Working Group
http://www.ietf.org/html.charters/ipv6-charter.html"
CONTACT-INFO
"Bill Fenner (editor)
AT&T Labs -- Research
75 Willow Rd.
Menlo Park, CA 94025
Phone: +1 650 330-7893
Email: <fenner@research.att.com>
John Flick (editor)
Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557
Roseville, CA 95747
Phone: +1 916 785 4018
Email: <john.flick@hp.com>
Send comments to <ipv6@ietf.org>"
DESCRIPTION
"The MIB module for managing UDP implementations.
Copyright (C) The Internet Society (2005). This
version of this MIB module is part of RFC 4113;
see the RFC itself for full legal notices."
REVISION "200505200000Z" -- May 20, 2005
DESCRIPTION
"IP version neutral revision, incorporating the
following revisions:
- Added udpHCInDatagrams and udpHCOutDatagrams in order
to provide high-capacity counters for fast networks.
- Added text to the descriptions of all counter objects
to indicate how discontinuities are detected.
- Deprecated the IPv4-specific udpTable and replaced it
with the version neutral udpEndpointTable. This
table includes support for connected UDP endpoints
and support for identification of the operating
system process associated with a UDP endpoint.
- Deprecated the udpGroup and replaced it with object
groups representing the current set of objects.
- Deprecated udpMIBCompliance and replaced it with
udpMIBCompliance2, which includes the compliance
information for the new object groups.
This version published as RFC 4113."
REVISION "199411010000Z" -- November 1, 1994
DESCRIPTION
"Initial SMIv2 version, published as RFC 2013."
REVISION "199103310000Z" -- March 31, 1991
DESCRIPTION
"The initial revision of this MIB module was part of
MIB-II, published as RFC 1213."
::= { mib-2 50 }
-- the UDP group
udp OBJECT IDENTIFIER ::= { mib-2 7 }
udpInDatagrams OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams delivered to UDP
users.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by discontinuities in the
value of sysUpTime."
::= { udp 1 }
udpNoPorts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of received UDP datagrams for which
there was no application at the destination port.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by discontinuities in the
value of sysUpTime."
::= { udp 2 }
udpInErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of received UDP datagrams that could not be
delivered for reasons other than the lack of an
application at the destination port.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by discontinuities in the
value of sysUpTime."
::= { udp 3 }
udpOutDatagrams OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams sent from this
entity.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by discontinuities in the
value of sysUpTime."
::= { udp 4 }
udpHCInDatagrams OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams delivered to UDP
users, for devices that can receive more than 1
million UDP datagrams per second.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by discontinuities in the
value of sysUpTime."
::= { udp 8 }
udpHCOutDatagrams OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams sent from this
entity, for devices that can transmit more than 1
million UDP datagrams per second.
Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at
other times as indicated by discontinuities in the
value of sysUpTime."
::= { udp 9 }
--
-- { udp 6 } was defined as the ipv6UdpTable in RFC2454's
-- IPV6-UDP-MIB. This RFC obsoletes RFC 2454, so { udp 6 } is
-- obsoleted.
--
-- The UDP "Endpoint" table.
udpEndpointTable OBJECT-TYPE
SYNTAX SEQUENCE OF UdpEndpointEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information about this entity's UDP
endpoints on which a local application is currently
accepting or sending datagrams.
The address type in this table represents the address
type used for the communication, irrespective of the
higher-layer abstraction. For example, an application
using IPv6 'sockets' to communicate via IPv4 between
::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use
InetAddressType ipv4(1).
Unlike the udpTable in RFC 2013, this table also allows
the representation of an application that completely
specifies both local and remote addresses and ports. A
listening application is represented in three possible
ways:
1) An application that is willing to accept both IPv4
and IPv6 datagrams is represented by a
udpEndpointLocalAddressType of unknown(0) and a
udpEndpointLocalAddress of ''h (a zero-length
octet-string).
2) An application that is willing to accept only IPv4
or only IPv6 datagrams is represented by a
udpEndpointLocalAddressType of the appropriate
address type and a udpEndpointLocalAddress of
'0.0.0.0' or '::' respectively.
3) An application that is listening for datagrams only
for a specific IP address but from any remote
system is represented by a
udpEndpointLocalAddressType of the appropriate
address type, with udpEndpointLocalAddress
specifying the local address.
In all cases where the remote is a wildcard, the
udpEndpointRemoteAddressType is unknown(0), the
udpEndpointRemoteAddress is ''h (a zero-length
octet-string), and the udpEndpointRemotePort is 0.
If the operating system is demultiplexing UDP packets
by remote address and port, or if the application has
'connected' the socket specifying a default remote
address and port, the udpEndpointRemote* values should
be used to reflect this."
::= { udp 7 }
udpEndpointEntry OBJECT-TYPE
SYNTAX UdpEndpointEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular current UDP endpoint.
Implementers need to be aware that if the total number
of elements (octets or sub-identifiers) in
udpEndpointLocalAddress and udpEndpointRemoteAddress
exceeds 111, then OIDs of column instances in this table
will have more than 128 sub-identifiers and cannot be
accessed using SNMPv1, SNMPv2c, or SNMPv3."
INDEX { udpEndpointLocalAddressType,
udpEndpointLocalAddress,
udpEndpointLocalPort,
udpEndpointRemoteAddressType,
udpEndpointRemoteAddress,
udpEndpointRemotePort,
udpEndpointInstance }
::= { udpEndpointTable 1 }
UdpEndpointEntry ::= SEQUENCE {
udpEndpointLocalAddressType InetAddressType,
udpEndpointLocalAddress InetAddress,
udpEndpointLocalPort InetPortNumber,
udpEndpointRemoteAddressType InetAddressType,
udpEndpointRemoteAddress InetAddress,
udpEndpointRemotePort InetPortNumber,
udpEndpointInstance Unsigned32,
udpEndpointProcess Unsigned32
}
udpEndpointLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type of udpEndpointLocalAddress. Only
IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
unknown(0) if datagrams for all local IP addresses are
accepted."
::= { udpEndpointEntry 1 }
udpEndpointLocalAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local IP address for this UDP endpoint.
The value of this object can be represented in three
possible ways, depending on the characteristics of the
listening application:
1. For an application that is willing to accept both
IPv4 and IPv6 datagrams, the value of this object
must be ''h (a zero-length octet-string), with
the value of the corresponding instance of the
udpEndpointLocalAddressType object being unknown(0).
2. For an application that is willing to accept only IPv4
or only IPv6 datagrams, the value of this object
must be '0.0.0.0' or '::', respectively, while the
corresponding instance of the
udpEndpointLocalAddressType object represents the
appropriate address type.
3. For an application that is listening for data
destined only to a specific IP address, the value
of this object is the specific IP address for which
this node is receiving packets, with the
corresponding instance of the
udpEndpointLocalAddressType object representing the
appropriate address type.
As this object is used in the index for the
udpEndpointTable, implementors of this table should be
careful not to create entries that would result in OIDs
with more than 128 subidentifiers; else the information
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3."
::= { udpEndpointEntry 2 }
udpEndpointLocalPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local port number for this UDP endpoint."
::= { udpEndpointEntry 3 }
udpEndpointRemoteAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type of udpEndpointRemoteAddress. Only
IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
unknown(0) if datagrams for all remote IP addresses are
accepted. Also, note that some combinations of
udpEndpointLocalAdressType and
udpEndpointRemoteAddressType are not supported. In
particular, if the value of this object is not
unknown(0), it is expected to always refer to the
same IP version as udpEndpointLocalAddressType."
::= { udpEndpointEntry 4 }
udpEndpointRemoteAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The remote IP address for this UDP endpoint. If
datagrams from any remote system are to be accepted,
this value is ''h (a zero-length octet-string).
Otherwise, it has the type described by
udpEndpointRemoteAddressType and is the address of the
remote system from which datagrams are to be accepted
(or to which all datagrams will be sent).
As this object is used in the index for the
udpEndpointTable, implementors of this table should be
careful not to create entries that would result in OIDs
with more than 128 subidentifiers; else the information
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3."
::= { udpEndpointEntry 5 }
udpEndpointRemotePort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The remote port number for this UDP endpoint. If
datagrams from any remote system are to be accepted,
this value is zero."
::= { udpEndpointEntry 6 }
udpEndpointInstance OBJECT-TYPE
SYNTAX Unsigned32 (1..'ffffffff'h)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The instance of this tuple. This object is used to
distinguish among multiple processes 'connected' to
the same UDP endpoint. For example, on a system
implementing the BSD sockets interface, this would be
used to support the SO_REUSEADDR and SO_REUSEPORT
socket options."
::= { udpEndpointEntry 7 }
udpEndpointProcess OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The system's process ID for the process associated with
this endpoint, or zero if there is no such process.
This value is expected to be the same as
HOST-RESOURCES-MIB::hrSWRunIndex or SYSAPPL-MIB::
sysApplElmtRunIndex for some row in the appropriate
tables."
::= { udpEndpointEntry 8 }
-- The deprecated UDP Listener table
-- The deprecated UDP listener table only contains information
-- about this entity's IPv4 UDP end-points on which a local
-- application is currently accepting datagrams. It does not
-- provide more detailed connection information, or information
-- about IPv6 endpoints.
udpTable OBJECT-TYPE
SYNTAX SEQUENCE OF UdpEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"A table containing IPv4-specific UDP listener
information. It contains information about all local
IPv4 UDP end-points on which an application is
currently accepting datagrams. This table has been
deprecated in favor of the version neutral
udpEndpointTable."
::= { udp 5 }
udpEntry OBJECT-TYPE
SYNTAX UdpEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"Information about a particular current UDP listener."
INDEX { udpLocalAddress, udpLocalPort }
::= { udpTable 1 }
UdpEntry ::= SEQUENCE {
udpLocalAddress IpAddress,
udpLocalPort Integer32
}
udpLocalAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The local IP address for this UDP listener. In the
case of a UDP listener that is willing to accept
datagrams for any IP interface associated with the
node, the value 0.0.0.0 is used."
::= { udpEntry 1 }
udpLocalPort OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The local port number for this UDP listener."
::= { udpEntry 2 }
-- conformance information
udpMIBConformance OBJECT IDENTIFIER ::= { udpMIB 2 }
udpMIBCompliances OBJECT IDENTIFIER ::= { udpMIBConformance 1 }
udpMIBGroups OBJECT IDENTIFIER ::= { udpMIBConformance 2 }
-- compliance statements
udpMIBCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems that implement
UDP.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, but
for which we have the following compliance
requirements, expressed in OBJECT clause form in this
description clause:
-- OBJECT udpEndpointLocalAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3),
-- ipv6z(4) }
-- DESCRIPTION
-- Support for dns(5) is not required.
-- OBJECT udpEndpointLocalAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
-- OBJECT udpEndpointRemoteAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3),
-- ipv6z(4) }
-- DESCRIPTION
-- Support for dns(5) is not required.
-- OBJECT udpEndpointRemoteAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
"
MODULE -- this module
MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup }
GROUP udpHCGroup
DESCRIPTION
"This group is mandatory for systems that
are capable of receiving or transmitting more than
1 million UDP datagrams per second. 1 million
datagrams per second will cause a Counter32 to
wrap in just over an hour."
::= { udpMIBCompliances 2 }
udpMIBCompliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for IPv4-only systems that
implement UDP. For IP version independence, this
compliance statement is deprecated in favor of
udpMIBCompliance2. However, agents are still
encouraged to implement these objects in order to
interoperate with the deployed base of managers."
MODULE -- this module
MANDATORY-GROUPS { udpGroup }
::= { udpMIBCompliances 1 }
-- units of conformance
udpGroup OBJECT-GROUP
OBJECTS { udpInDatagrams, udpNoPorts,
udpInErrors, udpOutDatagrams,
udpLocalAddress, udpLocalPort }
STATUS deprecated
DESCRIPTION
"The deprecated group of objects providing for
management of UDP over IPv4."
::= { udpMIBGroups 1 }
udpBaseGroup OBJECT-GROUP
OBJECTS { udpInDatagrams, udpNoPorts, udpInErrors,
udpOutDatagrams }
STATUS current
DESCRIPTION
"The group of objects providing for counters of UDP
statistics."
::= { udpMIBGroups 2 }
udpHCGroup OBJECT-GROUP
OBJECTS { udpHCInDatagrams, udpHCOutDatagrams }
STATUS current
DESCRIPTION
"The group of objects providing for counters of high
speed UDP implementations."
::= { udpMIBGroups 3 }
udpEndpointGroup OBJECT-GROUP
OBJECTS { udpEndpointProcess }
STATUS current
DESCRIPTION
"The group of objects providing for the IP version
independent management of UDP 'endpoints'."
::= { udpMIBGroups 4 }
END
Icinga2/_Test/vSan Mib/vmw/UUID-TC-MIB.mib
+94
View File
@@ -0,0 +1,94 @@
-- http://www.ietf.org/rfc/rfc6933.txt
UUID-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC 2579
;
uuidTCMIB MODULE-IDENTITY
LAST-UPDATED "201304050000Z" -- April 5, 2013
ORGANIZATION "IETF Energy Management Working Group"
CONTACT-INFO "WG Email: eman@ietf.org
Mailing list subscription info:
http://www.ietf.org/mailman/listinfo/eman
Dan Romascanu
Avaya
Park Atidim, Bldg. #3
Tel Aviv, 61581
Israel
Phone: +972-3-6458414
Email: dromasca@avaya.com
Juergen Quittek
NEC Europe Ltd.
Network Research Division
Kurfuersten-Anlage 36
Heidelberg 69115
Germany
Phone: +49 6221 4342-115
Email: quittek@neclab.eu
Mouli Chandramouli
Cisco Systems, Inc.
Sarjapur Outer Ring Road
Bangalore 560103
India
Phone: +91 80 4429 2409
Email: moulchan@cisco.com"
DESCRIPTION
"This MIB module defines TEXTUAL-CONVENTIONs
representing Universally Unique IDentifiers
(UUIDs).
Copyright (c) 2013 IETF Trust and the persons
identified as authors of the code. All rights
reserved.
Redistribution and use in source and binary forms,
with or without modification, is permitted
pursuant to, and subject to the license terms
contained in, the Simplified BSD License set forth
in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201304050000Z" -- April 5, 2013
DESCRIPTION "Initial version of this MIB as published in
RFC 6933."
::= { mib-2 217 }
-- Textual Conventions
UUID ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4x-2x-2x-1x1x-6x"
STATUS current
DESCRIPTION
"Universally Unique Identifier information. The syntax must
conform to RFC 4122, Section 4.1."
SYNTAX OCTET STRING (SIZE (16))
UUIDorZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4x-2x-2x-1x1x-6x"
STATUS current
DESCRIPTION
"Universally Unique Identifier information. The syntax must
conform to RFC 4122, Section 4.1.
The semantics of the value zero-length OCTET STRING are
object-specific and must therefore be defined as part of
the description of any object that uses this syntax."
SYNTAX OCTET STRING (SIZE (0|16))
END
Icinga2/_Test/vSan Mib/vmw/VMWARE-CIMOM-MIB.mib
+80
View File
@@ -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
Icinga2/_Test/vSan Mib/vmw/VMWARE-ENV-MIB.mib
+836
View File
@@ -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.
Icinga2/_Test/vSan Mib/vmw/VMWARE-ESX-AGENTCAP-MIB.mib
+2380
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/VMWARE-HEARTBEAT-MIB.mib
+80
View File
@@ -0,0 +1,80 @@
-- **********************************************************
-- Copyright 2016 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-HEARTBEAT-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF
sysUpTime
FROM SNMPv2-MIB
vmwProductSpecific
FROM VMWARE-ROOT-MIB;
vmwHBMIB MODULE-IDENTITY
LAST-UPDATED "201602100000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://communities.vmware.com/community/developer/forums/managementapi
"
DESCRIPTION
"This MIB module provides a reverse poll for systems that do not yet support polling.
See http://kb.vmware.com/kb/2020271 for details on reverse polling in VMware SNMP agents."
REVISION "201602100000Z"
DESCRIPTION
"First version."
::= { vmwHb 66 }
vmwHb OBJECT IDENTIFIER
::= { vmwProductSpecific 190 }
vmwHbNotifications OBJECT IDENTIFIER
::= {vmwHb 0 }
vmwHbHeartbeat NOTIFICATION-TYPE
OBJECTS { sysUpTime }
STATUS current
DESCRIPTION
"This notification, if the agent is so configured, will be sent
on a periodic basis to indicate cimom indication delivery is functioning."
::= { vmwHbNotifications 401 }
-- conformance information
vmwHbMIBConformance
OBJECT IDENTIFIER ::= { vmwHb 2 }
vmwHbMIBCompliances
OBJECT IDENTIFIER ::= { vmwHbMIBConformance 1 }
vmwHbMIBGroups OBJECT IDENTIFIER ::= { vmwHbMIBConformance 2 }
-- compliance statements
vmwHbMIBBasicCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement the
VMWARE-HEARTBEAT-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwHbNotificationGroup }
GROUP vmwHbNotificationGroup
DESCRIPTION
"This group is mandatory for systems without polling enabled."
::= { vmwHbMIBCompliances 4 }
vmwHbNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
vmwHbHeartbeat
}
STATUS current
DESCRIPTION
"Notifications related to snmp agent reverse poll feature."
::= { vmwHbMIBGroups 2 }
END
Icinga2/_Test/vSan Mib/vmw/VMWARE-NSX-MANAGER-AGENTCAP-MIB.mib
+194
View File
@@ -0,0 +1,194 @@
-- **********************************************************
-- Copyright 2016-2018 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 "201805310000Z"
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 "201805310000Z"
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 }
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
Icinga2/_Test/vSan Mib/vmw/VMWARE-NSX-MANAGER-MIB.mib
+6852
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/VMWARE-OBSOLETE-MIB.mib
+578
View File
@@ -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
Icinga2/_Test/vSan Mib/vmw/VMWARE-PRODUCTS-MIB.mib
+103
View File
@@ -0,0 +1,103 @@
-- **********************************************************
-- Copyright 2007-2018 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 "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 MIB module provides the OID identifiers
which are returned from SNMPv2-MIB sysObjectId for
agents in specific VMware products.
"
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 }
oidESX OBJECT IDENTIFIER
::= { vmwOID 1 }
END -- end of module VMWARE-PRODUCTS-MIB.
Icinga2/_Test/vSan Mib/vmw/VMWARE-RESOURCES-MIB.mib
+269
View File
@@ -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
Icinga2/_Test/vSan Mib/vmw/VMWARE-ROOT-MIB.mib
+182
View File
@@ -0,0 +1,182 @@
-- **********************************************************
-- 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 "201808300000Z"
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 "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 }
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
Icinga2/_Test/vSan Mib/vmw/VMWARE-SRM-EVENT-MIB.mib
+299
View File
@@ -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
Icinga2/_Test/vSan Mib/vmw/VMWARE-SYSTEM-MIB.mib
+130
View File
@@ -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.
Icinga2/_Test/vSan Mib/vmw/VMWARE-TC-MIB.mib
+188
View File
@@ -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
Icinga2/_Test/vSan Mib/vmw/VMWARE-TUNNEL-SERVER-AGENTCAP-MIB.mib
+96
View File
@@ -0,0 +1,96 @@
-- **********************************************************
-- Copyright 2018-2019 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 "201910300000Z"
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 Tunnel Server by 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 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
Icinga2/_Test/vSan Mib/vmw/VMWARE-TUNNEL-SERVER-MIB.mib
+471
View File
@@ -0,0 +1,471 @@
-- **********************************************************
-- Copyright 2018-2019 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 "201910300000Z"
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 Tunnel Server.
VMware Tunnel is part of Workspace ONE by VMware:
https://www.vmware.com/products/workspace-one.html
For more information about VMware Tunnel, please see
Architecture->Tunnel in the latest documentation of
VMware Workspace ONE UEM:
https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/
"
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) }
--
-- 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 }
vmwTunnelNumWhiteListedDevices OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of white-listed devices."
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 }
vmwTunnelNumNotInWhitelist OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of devices failed to connect due to not in whitelist.
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 }
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 }
--
-- 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 }
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 }
--
-- 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,
vmwTunnelNumWhiteListedDevices,
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 {
vmwTunnelNumNotInWhitelist,
vmwTunnelNumNonCompliant,
vmwTunnelNumNonManaged
}
STATUS current
DESCRIPTION
"A collection of VMware Tunnel Server runtime values."
::= { vmwTunnelServerMIBGroups 3 }
--
-- Compliance
--
vmwTunnelServerMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for VMware Tunnel Server SNMP
interface."
MODULE
MANDATORY-GROUPS { vmwTunnelServerStatGroup,
vmwTunnelServerInfoGroup,
vmwTunnelServerStatGroup2 }
::= { vmwTunnelServerMIBCompliances 1 }
END
Icinga2/_Test/vSan Mib/vmw/VMWARE-VA-AGENTCAP-MIB.mib
+718
View File
@@ -0,0 +1,718 @@
-- **********************************************************
-- Copyright 2008-2017 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 "201710130000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://communities.vmware.com/community/developer/forums/managementapi
"
DESCRIPTION
"This module defines agent capabilities for deployed VMware Virtual Appliance agents
by release."
REVISION "201710130000Z"
DESCRIPTION
"Capabilities for VMware VSphere (Release 6.7) ESXi 2017 added."
REVISION "201604220000Z"
DESCRIPTION
"Agent updates for 6.5 Release."
REVISION "201501120000Z"
DESCRIPTION
"Capabilities for VMware Virtual Appliance, 6.0 release."
::= { vmwareAgentCapabilities 5 }
vmwVACapability OBJECT IDENTIFIER ::= { vmwVAAgentCapabilityMIB 1 }
--
-- 2017 Release and follow up patch releases
--
vmwVCSA2017x AGENT-CAPABILITIES
PRODUCT-RELEASE
"6.7.x"
STATUS current
DESCRIPTION
"Release 6.7 for VMware Virtual Appliance (VCSA) supporting SNMPv1, SNMPv2c, and SNMPv3.
Changes for this release were primarily bug fixing related.
"
REFERENCE
"http://www.vmware.com/products"
-- RFC 3418
SUPPORTS SNMPv2-MIB
INCLUDES {
snmpGroup,
systemGroup,
snmpCommunityGroup,
snmpBasicNotificationsGroup,
snmpWarmStartNotificationGroup
-- groups not supported; snmpSetGroup, snmpNotificationGroup
}
VARIATION snmpSetSerialNo
ACCESS not-implemented
DESCRIPTION "Agent provides read-only view of system information."
VARIATION snmpTrapOID
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpTrapEnterprise
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpEnableAuthenTraps
SYNTAX INTEGER { disabled(2) }
ACCESS read-only
DESCRIPTION "Agent does not support authentication traps. Poll snmpInBadCommunityNames for same info."
-- which implies:
-- VARIATION authenticationFailure
-- ACCESS not-implemented
-- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled."
-- ********************* ************ ************ *************** ***
-- RFC 2863
SUPPORTS IF-MIB
INCLUDES {
ifGeneralInformationGroup,
linkUpDownNotificationsGroup
}
VARIATION ifAdminStatus
ACCESS read-only
DESCRIPTION "Agent provides read-only view of administrative state for each physical interface."
VARIATION ifLinkUpDownTrapEnable
ACCESS read-only
DESCRIPTION "Agent provides read-only view of system information."
VARIATION ifAlias
ACCESS read-only
DESCRIPTION "ifIndexes may only change across reboot."
VARIATION ifInUnknownProtos
ACCESS not-implemented
DESCRIPTION "This counter always returns 0."
-- ifRcvAddressGroup is interface/media specific
VARIATION ifRcvAddressStatus
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
VARIATION ifRcvAddressType
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
-- ********************* ************ ************ *************** ***
-- RFC 4293
SUPPORTS IP-MIB
INCLUDES {
ipSystemStatsGroup,
ipAddressGroup,
ipNetToPhysicalGroup,
ipDefaultRouterGroup,
icmpStatsGroup,
ipSystemStatsHCOctetGroup,
ipSystemStatsHCPacketGroup,
ipv4GeneralGroup,
ipv4IfGroup,
ipv4SystemStatsGroup,
ipv4SystemStatsHCPacketGroup,
ipv6GeneralGroup2,
ipv6IfGroup,
ipAddressPrefixGroup,
ipv6RouterAdvertGroup,
ipLastChangeGroup
}
-- VARIATION ipv6ScopeGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- RFC 4292
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS IP-FORWARD-MIB
INCLUDES {
inetForwardCidrRouteGroup
}
-- RFC 4113
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS UDP-MIB
-- The next two 32 bit counters will be fixed per bug report PR 890894
-- VARIATION udpInDatagrams
-- ACCESS not-implemented, use udpHCInDatagrams
-- VARIATION udpOutDatagrams
-- ACCESS not-implemented, use udpHCOutDatagrams
INCLUDES {
udpBaseGroup,
udpEndpointGroup
}
-- RFC 4022
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS TCP-MIB
INCLUDES {
tcpBaseGroup,
tcpConnectionGroup,
tcpListenerGroup
}
-- RFC 2790
-- NOTE: For storage larger than Integer32 (Terabyte) this agent will report INT_MAX
SUPPORTS HOST-RESOURCES-MIB
INCLUDES {
hrSystemGroup,
hrStorageGroup,
hrDeviceGroup,
hrSWRunGroup,
hrSWRunPerfGroup,
hrSWInstalledGroup -- updates once an hour
}
VARIATION hrSystemNumUsers
ACCESS read-only
DESCRIPTION "Value reports number of active appliace shell sessions"
VARIATION hrSystemDate
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadDevice
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadParameters
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrStorageSize
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSWRunStatus
ACCESS read-only
DESCRIPTION "agent provides read only access"
-- hrDeviceStatus reports unknown for: cpu, nic either running/unknown.
-- disk reports running, warning, down, unknown
-- device error counters do not account for all failure cases
VARIATION hrSWOSIndex
ACCESS not-implemented
DESCRIPTION "No operatingSystem entry exists in hrSWRunGroup hrSWRunTable"
VARIATION hrFSLastFullBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrFSLastPartialBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterStatus
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterDetectedErrorState
ACCESS not-implemented
DESCRIPTION "is not implemented"
-- ********************* ************ ************ *************** ***
-- RFC 4133
SUPPORTS ENTITY-MIB
INCLUDES {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup
}
-- VARIATION entityNotificationsGroup
-- ACCESS not-implemented
-- VARIATION entityMappingGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201008020000Z
SUPPORTS VMWARE-SYSTEM-MIB
INCLUDES {
vmwSystemGroup
}
-- VARIATION vmwProdUpdate
-- ACCESS not-implemented
-- VARIATION vmwProdPatch
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201602030000Z
SUPPORTS VMWARE-VCHA-MIB
INCLUDES {
vmwVchaNotificationInfoGroup,
vmwVchaNotificationGroup
}
::= { vmwVACapability 7 }
--
-- 2016 Release and follow up patch releases
--
vmwVCSA2016x AGENT-CAPABILITIES
PRODUCT-RELEASE
"6.5.x"
STATUS current
DESCRIPTION
"Release 6.5 for VMware Virtual Appliance supporting SNMPv1, SNMPv2c, and SNMPv3.
Adds VMWARE-VCHA-MIB module support.
This agent supports read-only protocol operations, shares same configuration file as VMware ESXi agent.
This implies that configuring the SNMPv3 Agent can not be done via SET operations or use SET PDU to
discover engine id. Hence IETF standard SNMPv3 agent configuration mibs are not provided.
The SNMPv3 protocol is fully supported once configured via the CLI command interface, run
appliancesh shell using the 'snmp' command set. Lastly this SNMP agent provides one read-only view of
the entire system to which all SNMPv3 users configured are assigned.
"
REFERENCE
"http://www.vmware.com/products"
-- RFC 3418
SUPPORTS SNMPv2-MIB
INCLUDES {
snmpGroup,
systemGroup,
snmpCommunityGroup,
snmpBasicNotificationsGroup,
snmpWarmStartNotificationGroup
-- groups not supported; snmpSetGroup, snmpNotificationGroup
}
VARIATION snmpSetSerialNo
ACCESS not-implemented
DESCRIPTION "Agent provides read-only view of system information."
VARIATION snmpTrapOID
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpTrapEnterprise
ACCESS not-implemented
DESCRIPTION "Agent does not proxy other agents RFC1157 Trap-PDUs."
VARIATION snmpEnableAuthenTraps
SYNTAX INTEGER { disabled(2) }
ACCESS read-only
DESCRIPTION "Agent does not support authentication traps. Poll snmpInBadCommunityNames for same info."
-- which implies:
-- VARIATION authenticationFailure
-- ACCESS not-implemented
-- DESCRIPTION "Agent does not provide this notification. snmpEnableAuthenTraps will return disabled."
-- ********************* ************ ************ *************** ***
-- RFC 2863
SUPPORTS IF-MIB
INCLUDES {
ifGeneralInformationGroup,
linkUpDownNotificationsGroup
}
VARIATION ifAdminStatus
ACCESS read-only
DESCRIPTION "Agent provides read-only view of administrative state for each physical interface."
VARIATION ifLinkUpDownTrapEnable
ACCESS read-only
DESCRIPTION "Agent provides read-only view of system information."
VARIATION ifAlias
ACCESS read-only
DESCRIPTION "ifIndexes may only change across reboot."
VARIATION ifInUnknownProtos
ACCESS not-implemented
DESCRIPTION "This counter always returns 0."
-- ifRcvAddressGroup is interface/media specific
VARIATION ifRcvAddressStatus
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
VARIATION ifRcvAddressType
ACCESS not-implemented
DESCRIPTION "Required if media specific mib modules are implemented."
-- ********************* ************ ************ *************** ***
-- RFC 4293
SUPPORTS IP-MIB
INCLUDES {
ipSystemStatsGroup,
ipAddressGroup,
ipNetToPhysicalGroup,
ipDefaultRouterGroup,
icmpStatsGroup,
ipSystemStatsHCOctetGroup,
ipSystemStatsHCPacketGroup,
ipv4GeneralGroup,
ipv4IfGroup,
ipv4SystemStatsGroup,
ipv4SystemStatsHCPacketGroup,
ipv6GeneralGroup2,
ipv6IfGroup,
ipAddressPrefixGroup,
ipv6RouterAdvertGroup,
ipLastChangeGroup
}
-- VARIATION ipv6ScopeGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- RFC 4292
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS IP-FORWARD-MIB
INCLUDES {
inetForwardCidrRouteGroup
}
-- RFC 4113
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS UDP-MIB
-- The next two 32 bit counters will be fixed per bug report PR 890894
-- VARIATION udpInDatagrams
-- ACCESS not-implemented, use udpHCInDatagrams
-- VARIATION udpOutDatagrams
-- ACCESS not-implemented, use udpHCOutDatagrams
INCLUDES {
udpBaseGroup,
udpEndpointGroup
}
-- RFC 4022
-- supports SNMPv2/3 Contexts for multiple instances
SUPPORTS TCP-MIB
INCLUDES {
tcpBaseGroup,
tcpConnectionGroup,
tcpListenerGroup
}
-- RFC 2790
-- NOTE: For storage larger than Integer32 (Terabyte) this agent will report INT_MAX
SUPPORTS HOST-RESOURCES-MIB
INCLUDES {
hrSystemGroup,
hrStorageGroup,
hrDeviceGroup,
hrSWRunGroup,
hrSWRunPerfGroup,
hrSWInstalledGroup -- updates once an hour
}
VARIATION hrSystemNumUsers
ACCESS read-only
DESCRIPTION "Value reports number of active appliace shell sessions"
VARIATION hrSystemDate
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadDevice
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSystemInitialLoadParameters
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrStorageSize
ACCESS read-only
DESCRIPTION "agent provides read only access"
VARIATION hrSWRunStatus
ACCESS read-only
DESCRIPTION "agent provides read only access"
-- hrDeviceStatus reports unknown for: cpu, nic either running/unknown.
-- disk reports running, warning, down, unknown
-- device error counters do not account for all failure cases
VARIATION hrSWOSIndex
ACCESS not-implemented
DESCRIPTION "No operatingSystem entry exists in hrSWRunGroup hrSWRunTable"
VARIATION hrFSLastFullBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrFSLastPartialBackupDate
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterStatus
ACCESS not-implemented
DESCRIPTION "is not implemented"
VARIATION hrPrinterDetectedErrorState
ACCESS not-implemented
DESCRIPTION "is not implemented"
-- ********************* ************ ************ *************** ***
-- RFC 4133
SUPPORTS ENTITY-MIB
INCLUDES {
entityPhysicalGroup,
entityPhysical2Group,
entityPhysical3Group,
entityGeneralGroup
}
-- VARIATION entityNotificationsGroup
-- ACCESS not-implemented
-- VARIATION entityMappingGroup
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201008020000Z
SUPPORTS VMWARE-SYSTEM-MIB
INCLUDES {
vmwSystemGroup
}
-- VARIATION vmwProdUpdate
-- ACCESS not-implemented
-- VARIATION vmwProdPatch
-- ACCESS not-implemented
-- ********************* ************ ************ *************** ***
-- REVISION 201602030000Z
SUPPORTS VMWARE-VCHA-MIB
INCLUDES {
vmwVchaNotificationInfoGroup,
vmwVchaNotificationGroup
}
::= { vmwVACapability 6 }
--
-- 2015 Release and follow up patch releases
--
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
Icinga2/_Test/vSan Mib/vmw/VMWARE-VC-EVENT-MIB.mib
+251
View File
@@ -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.
Icinga2/_Test/vSan Mib/vmw/VMWARE-VCHA-MIB.mib
+589
View File
@@ -0,0 +1,589 @@
-- **********************************************************
-- Copyright 2015-2016 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-VCHA-MIB DEFINITIONS::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InetAddress, InetAddressType
FROM INET-ADDRESS-MIB
vmwVCHA
FROM VMWARE-ROOT-MIB
TEXTUAL-CONVENTION, TruthValue
FROM SNMPv2-TC;
vmwVchaMIB MODULE-IDENTITY
LAST-UPDATED "201607190000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://communities.vmware.com/community/developer/forums/managementapi
"
DESCRIPTION
"This MIB module describes the vCenter High Availability Service (VCHA).
A VCHA cluster consists of three VMs identified by a single instance UUID.
One is the Active vCenter VM that serves client requests. Second is the
Passive VM that is identical to the Active vCenter VM in terms of database
and filesystem state. Passive VM constantly receives updates from Active
VM and takes over the role of Active vCenter VM in the event of a
failover. Third is the Witness VM that acts as a quorum VM in a VCHA
cluster. The sole purpose of Witness VM is to avoid classic split-brain
problem in a VCHA cluster.
client
+
|
|
+----------------v---+ +--------------------+
| Public IP | |
| | | |
| Active vCenter | | Passive vCenter |
| | | |
+---Private-IP+------+ +------+Private-IP---+
^ <--------------------------> ^
| DB & File replication |
+ +
+ +
+ +
+------> <----------+
+----Private-IP----+
| |
| Witness vCenter |
| (Quorum) |
| |
+------------------+
All events will not be repeated for the duration of a given state entered.
It is highly recommended that the administrator links the SNMP trap receiver
to both public network and vCenter HA cluster network, so that the
monitoring system is able to get notified as long as one of the
networks is up.
"
REVISION "201607190000Z"
DESCRIPTION
"Removed vmwVchaFileReplicationEventQueueOverflowed and cleaned up a few
descriptions. Fixed vCenter HA related terminologies and typos."
REVISION "201604060000Z"
DESCRIPTION
"Aggregate vmwVchaFileWatchFailed, vmwVchaFileReplicationFailed and
vmwVchaFileResyncSucceeded into vmwVchaFileReplicationStateChanged
notification. Add three more notification for failover failure cases.
Combine syncPeerStarted and syncPeerCompleted into a single state: sync."
REVISION "201602030000Z"
DESCRIPTION
"Add two more notifications vmwVchaFailoverSucceeded and
vmwVchaContinueAsActive to indicate whether a failover succeeds. Also add
one more parameter to vmwVchaNodeJoined and vmwVchaNodeLeft to distinguish
between the role of sender node and target node."
REVISION "201601270000Z"
DESCRIPTION
"Change the terminology from DB replication mode to DB replication state
and add one more state to it. Also use past tense for all notification
names."
REVISION "201601150000Z"
DESCRIPTION
"Add two more notifications vmwVchaClusterStateChange and
vmwVchaFileReplicationEventQueueOverflowed."
REVISION "201601040000Z"
DESCRIPTION
"This is the first version of this MIB module."
::= { vmwVCHA 1 }
vmwVCHANotifications OBJECT IDENTIFIER ::= { vmwVCHA 0 }
-- Definition of roles for VCHA, see RFC 4133 entLogicalType
vmwVchaActive OBJECT IDENTIFIER ::= { vmwVCHA 250 }
vmwVchaPassive OBJECT IDENTIFIER ::= { vmwVCHA 255 }
vmwVchaWitness OBJECT IDENTIFIER ::= { vmwVCHA 260 }
-- **********************************************************
-- Enumerations for notification parameters
-- **********************************************************
VmwVchaNodeRoleType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent the role each node in the cluster is running as.
active (1) Active vCenter serves client requests.
passive (2) Passive node is identical to the Active node in
terms of database and filesystem state. Passive
node constantly receives updates from the Active
node and takes over the role of Active node in the
event of a failover.
witness (3) Witness node acts as a quorum node in a vCenter HA
cluster. Sole purpose of Witness VM is to avoid
the classic split-brain problem in a VCHA cluster.
unknown (4) Node without any role assigned."
SYNTAX INTEGER { active(1), passive(2), witness(3), unknown(4) }
VmwVchaClusterModeType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent VCHA cluster modes: enabled, disabled or maintenance:
enabled (1) State replication between Active and Passive nodes
is enabled and automatic failover happens if the
Active node fails while the VCHA cluster is healthy.
disabled (2) All three nodes are part of VCHA cluster but the
state replication and automatic failover are
disabled.
maintenance (3) All three nodes are part of VCHA cluster but
automatic failover is disabled while state
replication continues. The Active node continues to
serve client requests even if Passive and Witness
nodes are lost."
SYNTAX INTEGER { enabled(1), disabled(2), maintenance(3) }
VmwVchaClusterStateType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent the health state of the vCenter HA cluster.
healthy (1) All three nodes in a VCHA cluster are healthy and
connected. State replication between the Active and
Passive nodes is working and both nodes are in-sync.
degraded (2) A VCHA cluster is said to be in degraded state when
it has lost one of the three nodes. Node loss can
be due to various reasons and as a result, the lost
node is not visible to other two nodes. If the
Active node is lost, the Passive node will take the
role of the Active node. If the Passive or Witness
node is lost, the Active node will continue to serve
requests. A VCHA cluster can also be in degraded
state if state replication fails between the Active
and Passive nodes.
isolated (3) All three nodes are isolated from each other. If
this happens when VCHA cluster is in enabled mode,
the Active node stops serving client requests. If
nodes are isolated in a disabled VCHA cluster mode,
the Active node continues to serve client requests."
SYNTAX INTEGER { healthy(1), degraded(2), isolated(3) }
VmwVchaDbReplicationStateType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent DB replication states: sync, async or no replication.
noReplication (1) There is no DB replication between the Active
and Passive nodes. This could happen when
vPostgres is not running on the Passive node.
sync (3) In sync state, the Passive vCenter keeps the
up-to-date state with the Active vCenter.
async (4) Async state replication makes the state of
Passive node fall behind the Active vCenter.
This causes a data loss when an automatic
failover happens."
SYNTAX INTEGER { noReplication(1), sync(3), async(4) }
VmwVchaFileReplicationProviderType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represent the file replication providers.
serviceConfig (1) This provider maintains the replication of
service configuration files, which are small in
size.
serviceState (2) This provider maintains the replication of
service state files, which are large in size."
SYNTAX INTEGER { serviceConfig(1), serviceState(2) }
-- **********************************************************
-- Notifications by an agent that implements this MIB module
-- **********************************************************
vmwVchaNodeJoined NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressType,
vmwVchaPrivateAddressAddr,
vmwVchaTargetNodeRole
}
STATUS current
DESCRIPTION
"This informative notification is sent from the Active node when it
notices a peer node rejoin the cluster. It is sent only once."
::= { vmwVCHANotifications 100 }
vmwVchaNodeLeft NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressType,
vmwVchaPrivateAddressAddr,
vmwVchaTargetNodeRole
}
STATUS current
DESCRIPTION
"This warning notification is sent from the Active node when it notices
a peer node has left the cluster. This is sent only once. Operator
should check the liveness and connectivity of the departed node and try
to bring it back by either rebooting the appliance or resolving the
network problem."
::= { vmwVCHANotifications 105 }
vmwVchaNodeIsolated NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressType,
vmwVchaPrivateAddressAddr,
vmwVchaTargetNodeRole
}
STATUS current
DESCRIPTION
"This warning notification is sent when a node is network isolated from
the cluster. This notification can only be sent from the isolated node,
not by other nodes in the cluster. After being isolated, the node will
reboot itself trigging coldStart notification. In case of Active node
failure, the cluster will trigger a reelection and every slave node will
be declared as isolated temporarily before the cluster re-election
completes."
::= { vmwVCHANotifications 110 }
vmwVchaClusterStateChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaClusterState
}
STATUS current
DESCRIPTION
"This notification is sent only once from the Active node when vCenter
HA cluster state changes to either healthy, degraded or isolated. Please
see VmwVchaClusterStateType for detailed description of each state. And
administrator should receive another notification describing the state
change of cluster subsystem (cluster membership, DB replication or file
replication) which is trigger of cluster state change."
::= { vmwVCHANotifications 130 }
vmwVchaClusterModeChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaClusterMode
}
STATUS current
DESCRIPTION
"This notification is sent only once from the Active node when vCenter
HA cluster mode changes to either enabled, maintenance or disabled."
::= { vmwVCHANotifications 150 }
vmwVchaPublicIpUp NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPublicAddressType,
vmwVchaPublicAddressAddr
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the public IP
address is brought up on the Active node. At this time, the Active node
is reachable from the client and will be able to serve client requests
when services are up and running."
::= { vmwVCHANotifications 205 }
vmwVchaPublicIpDown NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPublicAddressType,
vmwVchaPublicAddressAddr
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the public
network interface is brought down on the Active node. This can happen
when InitiateFailover is invoked on the Active node or vcha process
gracefully shuts down resulting in a reboot of the appliance (triggered
by network isolation). During this time, clients cannot connect to
vCenter Server and users will experience downtime until the public
network interface is brought up. In either case, users should not
expect more than five minutes of downtime. If VCHA cluster is still not
connectable, the operator should verify the reachability of each node
through the cluster network."
::= { vmwVCHANotifications 206 }
vmwVchaFailoverTriggered NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaIsPlannedFailover
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when a failover is
triggered from the Active node to Passive node. Passive node should
take over the Active role if the cluster is in healthy state."
::= { vmwVCHANotifications 210 }
vmwVchaFailoverSucceeded NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the Passive node
takes over the Active role and brings up the public network interface."
::= { vmwVCHANotifications 220 }
vmwVchaFailoverFailedDisabledMode NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This warning notification is sent only once when the Active node fails
to initiate a failover because the cluster is in disabled mode."
::= { vmwVCHANotifications 225 }
vmwVchaFailoverFailedNodeLost NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This warning notification is sent only once when the Active node fails
to initiate a failover because the cluster does not have all three
nodes connected."
::= { vmwVCHANotifications 226 }
vmwVchaFailoverFailedPassiveNotReady NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This warning notification is sent only once when the Active node fails
to initiate a failover because vPostgres service on the Passive node is
not ready to take over."
::= { vmwVCHANotifications 227 }
vmwVchaContinueAsActive NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid
}
STATUS current
DESCRIPTION
"This informative notification is sent only once when the last Active
node continue as the Active node to servce client's request. This can
happen in many scenarios:
1. After triggering a planned failover, DB or file replicator failed to
flush data to the Passive node and failover didn't proceed because of
data loss.
2. After triggering a planned or forced failover, Passive node failed to
pick up the Active role for reasons like: auto failover cannot happen in
maintenance mode or cluster is in disabled mode."
::= { vmwVCHANotifications 230 }
vmwVchaDbReplicationStateChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaDbReplicationState
}
STATUS current
DESCRIPTION
"This informative notification is sent only once from the Active node
when database replication state changes to sync, async or no
replication. Database replication is not healthy when it is in async or
no replication state. Reasons include large network delays or vPostgres
service becoming unresponsive on the Passive node."
::= { vmwVCHANotifications 300 }
vmwVchaFileReplicationStateChanged NOTIFICATION-TYPE
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaFileReplicationProvider,
vmwVchaIsFileProviderInSync
}
STATUS current
DESCRIPTION
"This informative notification is sent only once from the Active node
when file replication state changes to in-sync or out-of-sync. File
replication state is out-of-sync when VCHA fails to set a watch on a
file at the Active node or fails to replicate a file from the Active
node to Passive. Administrators should check the corresponding KB
article for recovery action."
::= { vmwVCHANotifications 350 }
-- **********************************************************
-- Notification variables
-- **********************************************************
vmwVchaInstanceUuid OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"A string that uniquely identify the vCenter HA cluster. This is the same
as instance UUID of the active vCenter Server."
::= { vmwVCHA 5 }
vmwVchaPrivateAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The type of cluster network interface: ipv4 or ipv6."
::= { vmwVCHA 11 }
vmwVchaPublicAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The type of public network interface: ipv4 or ipv6."
::= { vmwVCHA 12 }
vmwVchaPrivateAddressAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This is the IP address of each node in cluster network that is used to
communicate with other nodes in the cluster and transfer data between
the Active node and the Passive node."
::= { vmwVCHA 15 }
vmwVchaPublicAddressAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The IP address of a node in public network that serves client's request."
::= { vmwVCHA 16 }
vmwVchaTargetNodeRole OBJECT-TYPE
SYNTAX VmwVchaNodeRoleType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Represents the role of node being affected by the given event. See MIB
module general description for detailed expalanation for each role."
::= { vmwVCHA 20 }
vmwVchaClusterState OBJECT-TYPE
SYNTAX VmwVchaClusterStateType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"vCenter HA cluster states: healthy, degraded or isolated."
::= { vmwVCHA 25 }
vmwVchaClusterMode OBJECT-TYPE
SYNTAX VmwVchaClusterModeType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"vCenter HA cluster modes: enabled, maintenance or disabled."
::= { vmwVCHA 30 }
vmwVchaIsPlannedFailover OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"For planned failover, the Active node flushes all the state to the Passive
node, waits for the flush to complete before causing a failover.
After the failover, the Passive node starts without any data loss.
For unplanned failover, the failover is initiated immediately and may
result in data loss."
::= { vmwVCHA 40 }
vmwVchaDbReplicationState OBJECT-TYPE
SYNTAX VmwVchaDbReplicationStateType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"Database replication states: sync, async or no replication."
::= { vmwVCHA 50 }
vmwVchaIsFileProviderInSync OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"This variable represents the file replication provider state. When it is
false, the service configuration and state files are out of sync between
the Passive and Active nodes. This could result from file replication
failures."
::= { vmwVCHA 55 }
vmwVchaFileReplicationProvider OBJECT-TYPE
SYNTAX VmwVchaFileReplicationProviderType
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"File replication providers: service-config or service-state."
::= { vmwVCHA 60 }
-- conformance information
vmwVchaMIBConformance OBJECT IDENTIFIER ::= { vmwVchaMIB 2 }
vmwVchaMIBCompliances OBJECT IDENTIFIER ::= { vmwVchaMIBConformance 1 }
vmwVchaMIBGroups OBJECT IDENTIFIER ::= { vmwVchaMIBConformance 2 }
vmwVchaMIBBasicComplianceRev2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement VMWARE-VCHA-MIB."
MODULE -- this module
MANDATORY-GROUPS { vmwVchaNotificationInfoGroup, vmwVchaNotificationGroup }
::= { vmwVchaMIBCompliances 3 }
vmwVchaNotificationInfoGroup OBJECT-GROUP
OBJECTS {
vmwVchaInstanceUuid,
vmwVchaPrivateAddressAddr,
vmwVchaPrivateAddressType,
vmwVchaPublicAddressAddr,
vmwVchaPublicAddressType,
vmwVchaTargetNodeRole,
vmwVchaClusterState,
vmwVchaClusterMode,
vmwVchaIsPlannedFailover,
vmwVchaDbReplicationState,
vmwVchaIsFileProviderInSync,
vmwVchaFileReplicationProvider
}
STATUS current
DESCRIPTION
"These objects provide notification details."
::= { vmwVchaMIBGroups 1 }
vmwVchaNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
vmwVchaNodeJoined,
vmwVchaNodeLeft,
vmwVchaNodeIsolated,
vmwVchaClusterStateChanged,
vmwVchaClusterModeChanged,
vmwVchaPublicIpUp,
vmwVchaPublicIpDown,
vmwVchaFailoverTriggered,
vmwVchaFailoverSucceeded,
vmwVchaFailoverFailedDisabledMode,
vmwVchaFailoverFailedNodeLost,
vmwVchaFailoverFailedPassiveNotReady,
vmwVchaContinueAsActive,
vmwVchaDbReplicationStateChanged,
vmwVchaFileReplicationStateChanged
}
STATUS current
DESCRIPTION
"Group of objects describing notifications (traps)."
::= { vmwVchaMIBGroups 2 }
END -- end of VMWARE-VCHA-MIB.
Icinga2/_Test/vSan Mib/vmw/VMWARE-VCOPS-EVENT-MIB.mib
+1695
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/VMWARE-VMINFO-MIB.mib
+704
View File
@@ -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.
Icinga2/_Test/vSan Mib/vmw/VMWARE-VRNI-AGENTCAP-MIB.mib
+235
View File
@@ -0,0 +1,235 @@
-- **********************************************************
-- Copyright 2016-2017 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-VRNI-AGENTCAP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI
vmwareAgentCapabilities
FROM VMWARE-ROOT-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF;
vmwVRNIAgentCapabilityMIB MODULE-IDENTITY
LAST-UPDATED "201906060000Z"
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 "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 }
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
Icinga2/_Test/vSan Mib/vmw/VMWARE-VRNI-MIB.mib
+2902
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/VMWARE-VROPS-AGENTCAP-MIB.mib
+51
View File
@@ -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
Icinga2/_Test/vSan Mib/vmw/VMWARE-VROPS-MIB.mib
+407
View File
@@ -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
Icinga2/_Test/vSan Mib/vmw/incompatible/VMWARE-VRNI-AGENTCAP-MIB.mib
+134
View File
@@ -0,0 +1,134 @@
-- **********************************************************
-- Copyright 2016-2017 VMware, Inc. All rights reserved.
-- **********************************************************
VMWARE-VRNI-AGENTCAP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY
FROM SNMPv2-SMI
vmwareAgentCapabilities
FROM VMWARE-ROOT-MIB
AGENT-CAPABILITIES
FROM SNMPv2-CONF;
vmwVRNIAgentCapabilityMIB MODULE-IDENTITY
LAST-UPDATED "201710130000Z"
ORGANIZATION "VMware, Inc"
CONTACT-INFO
"VMware, Inc
3401 Hillview Ave
Palo Alto, CA 94304
Tel: 1-877-486-9273 or 650-427-5000
Fax: 650-427-5001
Web: http://kb.vmware.com/kb/1013445
"
DESCRIPTION
"WARNING: these VRNI releases up to v3.5 are incompatibile with newer releases
so do not try to add both to one mgmt system.
This module defines agent capabilities for deployed VRNI agents by release."
REVISION "201710130000Z"
DESCRIPTION
"Change vmwVRNIAgentCapabilityMIB root oid to fix duplicate oid."
REVISION "201709050000Z"
DESCRIPTION
"Notifications send by VRNI as updated in 3.5 release"
REVISION "201706010000Z"
DESCRIPTION
"Notifications send by VRNI as updated in 3.4 release"
REVISION "201703020000Z"
DESCRIPTION
"Notifications send by VRNI as updated in 3.3 release"
REVISION "201611220001Z"
DESCRIPTION
"Describe SNMP agent capabilities for each VRNI appliance release."
::= { vmwareAgentCapabilities 125 }
vmwVRNICapability OBJECT IDENTIFIER ::= { vmwVRNIAgentCapabilityMIB 10 }
vmwVRNIAgent2016v350 AGENT-CAPABILITIES
PRODUCT-RELEASE
"3.5.0"
STATUS obsolete
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 obsolete
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 obsolete
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 obsolete
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
Icinga2/_Test/vSan Mib/vmw/incompatible/VMWARE-VRNI-MIB.mib
+1618
View File
File diff suppressed because it is too large Load Diff
Icinga2/_Test/vSan Mib/vmw/list-ids-diagnostics.txt
+7
View File
@@ -0,0 +1,7 @@
IP-FORWARD-MIB.mib:230: index element `inetCidrRoutePolicy' of row `inetCidrRouteEntry' should but cannot have a size restriction
VMWARE-VMON-MIB.mib: No such file or directory
smidump: cannot locate module `VMWARE-VMON-MIB.mib'
VMWARE-NSX-MIB.mib: No such file or directory
smidump: cannot locate module `VMWARE-NSX-MIB.mib'
VMWARE-HCX-MIB.mib: No such file or directory
smidump: cannot locate module `VMWARE-HCX-MIB.mib'
Icinga2/_Test/vSan Mib/vmw/notifications.txt
+273
View File
@@ -0,0 +1,273 @@
Document: SNMP Agent Notifications for VROPS, VRNI, NSX Manager, and ESXi and Virtual Center
Security: none
Author: mrm@vmware.com <Michael R. MacFaden>
Date: : Mon Dec 16 10:29:18 PST 2019
Version: 1.15
Source: http://kb.vmware.com/kb/2054359
Introduction:
Notifications on VROPS, VRNI, ESXi, NSX, TUNNEL, and VCSA are composed from IETF standard
and VMWARE enterprise MIB module documents. ESXi may also generate 3rd party notifications
from any vib/CIM providers installed. They may generate OEM events using their enterprise oids.
VRNI MIB modules were reimplemented in 3.9 release and reused existing oids are are thus
not backward compatible and will conflict if both versions of mib modules are imported into same managment
system. The obsolete/ directory contains prior VRNI mib modules.
VROPS MIB modules switched to new oids in 7.0 release and replaced
VMWARE-VCOPS-EVENT-MIB.mib which is now obsolete.
VMWARE-TUNNEL-MIB and its snmp agent capability mib are described here:
https://docs.vmware.com/en/Unified-Access-Gateway/3.6/com.vmware.uag-36-deploy-config.doc/GUID-F71E6283-E24B-49F5-8AC6-D28915CD41AD.html
All ESX VMware MIB modules are compatible back to ESX 2.0, always load the latest set to
manage all vesions of ESXi and ESX Classic. The VMWARE-OBSOLETE-MIB contains any obsolete
objects and would be loaded when running older versions of software. See the VMWARE-*-AGENTCAP-MIB
for which releases of code provide what versions of MIB modules.
Virtual Center has two snmp agents in Virtual Center Appliance starting in 6.x release cycle.
VC Daemon presently only supports SNMPv1. VCSA supports SNMPv1/v2c/v3.
Here is a summary of the MIB modules that define notifications which are sent on the wire
as either SNMPv1 Trap Protocol data units (PDUs) or SNMPv3 Trap PDU for VCSA and ESXi,
NSX only supports V2c traps in its first release. See their VMWARE-NSX-AGENTCAP-MIB for details.
Example output is also provided.
Configuring notifications:
William Lam wrote up how to configure trap/inform here for ESXi.
http://blogs.vmware.com/vsphere/2012/11/configuring-snmp-v1v2cv3-using-esxcli-5-1.html
Documentation for VCSA SNMP agent:
VCSA https://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.vcsa.doc/GUID-3695CE84-C6DF-497E-BA4E-2B341CC366C5.html
Documentation, 5.1, 5.5, 6.0 for CLI
http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.monitoring.doc%2FGUID-346CDDC6-8928-466F-A356-C8DAA6112439.html
Configuring NSX: https://www.vmware.com/support/pubs/nsx_pubs.html
Current VMware KB Aricles on SNMP:
* Downloading MIB modules http://kb.vmware.com/kb/1013445
* Listing of all OIDs by type, mib module and name: http://kb.vmware.com/kb/2054359
* Debugging notification (trap/inform) reception http://kb.vmware.com/kb/2035445
* Configuring SNMPv3 inform remotre users in ESXi SNMP agent: http://kb.vmware.com/kb/2033377
* Reverse Poll Feature aka SNMP Trap is repeated every 5 minutes http://ikb.vmware.com/kb/2020271
* Timeouts and SNMP https://ikb.vmware.com/kb/2100602
* Timeouts in ESXi snmp in storage apis: https://ikb.vmware.com/kb/2105674
* Understanding Layer 2 networking as reported by ESXi SNMP http://kb.vmware.com/kb/2118059
* Monitoring VCSA using SNMP (2145018) http://kb.vmware.com/kb/2145018
VMworld 2016 information:
http://blogs.vmware.com/vsphere/2016/08/vmworld-2016-vcenter-server-sessions.html
Session Title: Understand the role SNMP agents play in a VSPHERE Stack
http://vmware.mediasite.com/mediasite/Play/4eab4abb038344f98c2c1e6ef8b7e2fa1d?catalog=dbf1ec28-2557-4dd3-a381-e5fe4ceabc40
Since ESXi 5.x, snmp agent should now be configured with 'esxcli system snmp' instead of vicfg-snmp
script. the vicfg-snmp script is found on VCSA appliance in the bash shell and snmp.set command
in the appliancesh shell.
vicfg-snmp will continue to work. The vicfg-snmp uses VIM API objects will only ever support SNMPv1.
The command line flags have been preserved from the RCLI to esxcli
this allows for easy substitution of 'vicfg-snmp' to 'esxcli system snmp' for example:
esxcli system snmp --hwsrc sensor
esxcli system snmp --no traps <oid[,oid]> # see list of oids in Appendix A below
esxcli system snmp set -t 192.0.2.1/mytesttrapcom --enable 1 # turn on snmp agent and sent traps to one destination.
# SNMPv3 support for informs has been available since ESX 5.1, with no security (noAuthNoPriv)
# is equivalent to SNMPv1
# To define a user and inform target for that user
esxcli system snmp set -u john_doe/-/-/none -i 192.0.2.1@1162/john_doe/none/inform
Configuring notifications with RCLI command (ESX 3.x to ESX 5.0):
First one provides a backward compatibility switch for VMWARE-ENV-MIB for ESX
releases prior to 5.0 use the cmd:
vicfg-snmp --hwsrc sensors # switch to pre-ESXi 5.0 notifcation format
Second, one can now filter out/stop sending notifications. Just provide the
oid in the form enterprise.0.trapid
vicfg-snmp --notraps 1.3.6.1.4.1.6876.1.0.302,1.3.6.1.4.1.6876.1.0.303
ESXi NOTIFICATIONS:
SNMPv2-MIB (http://www.ietf.org/rfc/rfc3418.txt)
coldStart -- sent when ESX reboots
warmStart -- sent when vmware-hostd process restarts
IF-MIB (http://www.ietf.org/rfc/rfc2863.txt)
linkDown -- Physical interface changed to down state
linkUp -- Physical interface changed to down state
When one receives these notifications, they will contain the ifIndex which
when used to poll the ifTable shall see the following
managed objects change state: ifLastChange, ifSpeed, ifOperStatus change state)
VMWARE-VMINFO-MIB
vmPoweredOn TRAP-TYPE
VARIABLES { vmID, vmConfigFile, vmDisplayName }
DESCRIPTION
"This trap is sent when a virtual machine is powered on from a suspended
or a powered off state. The origin of this event can be several:
for instance may be operator initiated, existing vmx process reconnects to control subsystem.
NOTE: vms powered up due to VMotion are not reported. Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status."
::= 1
vmPoweredOff TRAP-TYPE
VARIABLES { vmID, vmConfigFile, vmDisplayName }
DESCRIPTION
"This trap is sent when a virtual machine is powered off. The origin of this event can be several:
for instance may be operator initiated, vmx process terminating abnormally. NOTE: vms powered down due
to VMotion are not reported. Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status."
::= 2
vmHBLost TRAP-TYPE
VARIABLES { vmID, vmConfigFile, vmDisplayName }
DESCRIPTION
"This trap is sent when a virtual machine detects a loss in guest heartbeat. The Guest heartbeat
is only sent if VMware Tools are installed in the Guest OS. Control process will send this event whenever it
determines the number of guest heartbeats for a given period of time have not been received.
Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status."
::= 3
vmHBDetected TRAP-TYPE
VARIABLES { vmID, vmConfigFile, vmDisplayName }
DESCRIPTION
"This trap is sent when a virtual machine detects or regains the required number of guest heartbeats
for a given period of time. This is only sent if VMware tools are installed in the Guest OS.
Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status."
::= 4
vmSuspended TRAP-TYPE
VARIABLES { vmID, vmConfigFile, vmDisplayName }
DESCRIPTION
"This trap is sent when a virtual machine is suspended. The origin of this event may be several: operator
initiated, by software api clients, and by other means.
Upon receiving this notification client applications should
poll the vmwVmTable to obtain current status."
::= 5
VMWARE-CIMOM-MIB
The sfcbd agent in ESXi starting in ESX 5.0 will send a heartbeat once every
5 minutes. This duration can be changed or disabled within sfcbd or filtered
at the snmp agent (see Appendix A)
vmwCimOmHeartbeat TRAP-TYPE
VARIABLES { vmwEnvIndicationTime }
DESCRIPTION
"This notification, if the agent is so configured, will be sent
on a periodic basis to indicate cimom indication delivery is functioning."
::= { vmwCimOmNotifications 401 }
Update the sfcbc configuration etc/sfcb/sfcb.cfg" and add the key "heartbeatInterval"
to the number of seconds it should be sent.
VMWARE-ENV-MIB
Starting with ESXi 5.0, VMware enterprise hardware related notifcations are reported in
the specific identifier field of SNMPv1 trap PDU as follow:
VMWARE-ENV-MIB vmwEnvHardwareEvent notification 1.3.6.1.4.1.6876.0.301
VMWARE-ENV-MIB vmwESXEnvHardwareEvent notification 1.3.6.1.4.1.6876.4.1.0.301
VMWARE-ENV-MIB vmwESXEnvHardwareAlert notification 1.3.6.1.4.1.6876.4.1.0.302
VMWARE-ENV-MIB vmwESXEnvBatteryAlert notification 1.3.6.1.4.1.6876.4.1.0.303
VMWARE-ENV-MIB vmwESXEnvChassisAlert notification 1.3.6.1.4.1.6876.4.1.0.304
VMWARE-ENV-MIB vmwESXEnvThermalAlert notification 1.3.6.1.4.1.6876.4.1.0.305
VMWARE-ENV-MIB vmwESXEnvDiskAlert notification 1.3.6.1.4.1.6876.4.1.0.306
VMWARE-ENV-MIB vmwESXEnvPowerAlert notification 1.3.6.1.4.1.6876.4.1.0.307
VMWARE-ENV-MIB vmwESXEnvProcessorAlert notification 1.3.6.1.4.1.6876.4.1.0.308
VMWARE-ENV-MIB vmwESXEnvMemoryAlert notification 1.3.6.1.4.1.6876.4.1.0.309
VMWARE-ENV-MIB vmwESXEnvBIOSAlert notification 1.3.6.1.4.1.6876.4.1.0.310
An example:
2010-06-11 19:59:34 promc-2n-dhcp119.eng.vmware.com [10.20.104.119] (via UDP: [10.20.104.119]:50569) TRAP, SNMP v1, community mrm-pc
.1.3.6.1.4.1.6876.4.1 Enterprise Specific Trap (302)
Uptime: 0:22:06.22
.1.3.6.1.4.1.6876.4.30.10 = STRING: RawIpmiProvider
.1.3.6.1.4.1.6876.4.30.9 = STRING: 44454c4c-5700-1035-8038-b4c04f594231
.1.3.6.1.4.1.6876.4.30.8 = Wrong Type (should be INTEGER): 2
.1.3.6.1.4.1.6876.4.30.7 = STRING: root/cimv2:OMC_DiscreteSensor.DeviceID="81.0.32.2",CreationClassName="OMC_DiscreteSensor",SystemName="44454c4c-5700-1035-8038-b4c04f594231",SystemCreationClassName="O MC_UnitaryComputerSystem"
.1.3.6.1.4.1.6876.4.30.6 = STRING: OMC_UnitaryComputerSystem
.1.3.6.1.4.1.6876.4.30.5 = Wrong Type (should be INTEGER): 5
.1.3.6.1.4.1.6876.4.30.4 = Wrong Type (should be INTEGER): 0
.1.3.6.1.4.1.6876.4.30.3 = STRING: 12848-49-55,48:55:49.49,148:515552534648555648505143484848
.1.3.6.1.4.1.6876.4.30.2 = STRING: 12848-49-55,48:55:49.49,148:515653544648484848484843484848
.1.3.6.1.4.1.6876.4.30.1 = STRING: Assert + Event Logging Disabled Log area reset/cleared
Environmental/hardware related notifications in VMWARE-ENV-MIB are the same content as found in ESXi CIM Indications.
Prior to ESXi 5.0, this is the trap one would get:
vmwEnvHardwareEvent TRAP-TYPE
VARIABLES { vmwSubsystemType, vmwHardwareStatus, vmwEventDescription, vmwEnvHardwareTime }
DESCRIPTION
"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"
::= 301
This generic notification depends on the CIM subsystem mappings to discrete IPMI sensors.
For example on a Dell R805, one might see one or more alarms as follows:
2007-11-01 16:15:42 esx014.eng.vmware.com [10.17.21.14] (via 10.17.21.14) TRAP, SNMP v1, community private
SNMPv2-SMI::VMWARE-PRODUCTS-MIB::vmwESX Enterprise Specific Trap (301) Uptime: 0:00:06.76
VMWARE-ENV-MIB::vmwSubsystemType.1 = INTEGER: unknown(1)
VMWARE-ENV-MIB::vmwHardwareStatus.1 = INTEGER: critical(4)
VMWARE-ENV-MIB::vmwEventDescription.1 = STRING: "USB Over-current 65 for BIOS 1"
VMWARE-ENV-MIB::vmwEnvHardwareTime.1 = Timeticks: (675) 0:00:06.75
External RAID enclosure configured to RAID 5, pull cable from one of the disk and this is sent:
2007-11-14 10:11:15 scho1-dev.eng.vmware.com [10.20.110.134] (via 10.20.110.134) TRAP, SNMP v1, community private
VMWARE-PRODUCTS-MIB::vmwESX Enterprise Specific Trap (301) Uptime: 0:03:11.14
VMWARE-ENV-MIB::vmwSubsystemType.1 = INTEGER: raidController(9)
VMWARE-ENV-MIB::vmwHardwareStatus.1 = INTEGER: marginal(3)
VMWARE-ENV-MIB::vmwERING: "RAID1 Virtual Disk 0 of Controller 0"
VMWARE-ENV-MIB::vmwEnvHardwareTime.1 = Timeticks: (19114) 0:03:11.14
NOTE: Given the specific hardware above for example
one would next consult the Dell R805 Dell's documentation
on IPMI messages for the majority of those listed (not all):
http://support.dell.com/support/edocs/software/svradmin/5.5/en/MSG/html/msgch30.htm
EXAMPLES:
2007-11-01 16:14:11 NET-SNMP version 5.1.2 Started.
# hostd is rebooted while ESX is up, a warmStart trap is sent...
2007-11-01 16:14:36 esx014.eng.vmware.com [10.17.21.14] (via 10.17.21.14) TRAP, SNMP v1, community private
SNMPv2-SMI::VMWARE-PRODUCTS-MIB::vmwESX Warm Start Trap (0) Uptime: 0:00:00.02
vSPHERE Center Server Notifications
VMWARE-VC-EVENT-MIB:
vmwVCNotifications OBJECT IDENTIFIER ::= {vmwVC 0}
vpxdAlarm NOTIFICATION-TYPE
OBJECTS { vmwVpxdTrapType, vmwVpxdHostName, vmwVpxdVMName,
vmwVpxdOldStatus, vmwVpxdNewStatus, vmwVpxdObjValue }
STATUS current
DESCRIPTION
"This trap is sent when entity alarm status changed."
::= { vmwVCNotifications 201 }
vpxdDiagnostic NOTIFICATION-TYPE
STATUS current
DESCRIPTION
"This trap 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."
::= { vmwVCNotifications 202 }
The vpxdAlarm notification is transmitted from vCenter Server on changes in
alarm state, dictated by the trigger and notification configuration of the
alarm.
The vpxdDiagnostic notification is used for generating test traps as well as
generating coldStart traps for vCenter Server starts/restarts.
The transmission of test traps can be configured through the vCenter Server
OptionManager interface, or through the vCenter configuration file (vpxd.cfg),
using the following keys:
snmp.testTrap.periodic.enable ("true"/"false")
snmp.testTrap.periodic.period (defaults to 300) (Number of milliseconds)
snmp.coldStartTrap.enable (defaults to "true") ("true"/"false")
# end of Document
Icinga2/_Test/vSan Mib/vmw/vc-alarms-65.csv
+1
View File
File diff suppressed because one or more lines are too long