Standard view Table view

AV-SME-PLATFORM-MIB

        Avaya IP Office MIBs OID tree.
        
This MIB module defines the root items for MIBs for
use with Avaya SME Embedded Platform.
Source file
AV-SME-PLATFORM-MIB
Last revised
Identity
avSMEPlatformMIB
Base OID
1.3.6.1.4.1.6889.2.48
Imported Objects
AVAYAGEN-MIB mibs
IF-MIB ifIndex
ITU-ALARM-TC-MIB ItuPerceivedSeverity
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE NOTIFICATION-GROUP OBJECT-GROUP
SNMPv2-MIB sysDescr
SNMPv2-SMI MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE
SNMPv2-TC DateAndTime
Net-SNMP examples using the avaya MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'AV-SME-PLATFORM-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AV-SME-PLATFORM-MIB::avSMEPlatformMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'AV-SME-PLATFORM-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AV-SME-PLATFORM-MIB::avSMEPlatformMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (14)
avSMEPlatformMIB
.1.3.6.1.4.1.6889.2.48
smepGeneric
.1.3.6.1.4.1.6889.2.48.1
smepGenMibs
.1.3.6.1.4.1.6889.2.48.1.1
smepGenTraps
.1.3.6.1.4.1.6889.2.48.1.2
smepGTEvents
.1.3.6.1.4.1.6889.2.48.1.2.0
smepGTObjects
.1.3.6.1.4.1.6889.2.48.1.2.1
smepGTEventStdSeverity
ITU-ALARM-TC-MIBItuPerceivedSeverity
 .1.3.6.1.4.1.6889.2.48.1.2.1.1
smepGTEventDateTime
SNMPv2-TCDateAndTime
 .1.3.6.1.4.1.6889.2.48.1.2.1.2
smepGTEventDevID
OctetString
 .1.3.6.1.4.1.6889.2.48.1.2.1.3
smepGTEventAppEntity
Enumeration
 .1.3.6.1.4.1.6889.2.48.1.2.1.4
smepGTEventAppEvent
Enumeration
 .1.3.6.1.4.1.6889.2.48.1.2.1.5
smepGenConformance
.1.3.6.1.4.1.6889.2.48.1.3
smepGenCompliances
.1.3.6.1.4.1.6889.2.48.1.3.1
smepGenGroups
.1.3.6.1.4.1.6889.2.48.1.3.2
Dependencies (9) 8 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. AVAYAGEN-MIBavaya
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. ITU-ALARM-TC-MIBrfc
  9. SNMP-FRAMEWORK-MIBrfc
  10. AV-SME-PLATFORM-MIBavayaselected
Conformance Groups (3)
smepGenNotificationObjectsGroup
smepGTEventStdSeverity smepGTEventDevID smepGTEventDateTime smepGTEventAppEntity smepGTEventAppEvent
Objects that are contained in SME Embedded Platform wide
notifications.
 .1.3.6.1.4.1.6889.2.48.1.3.2.1
smepGenEntGenNotificationsGroup
smepGenColdStartEvent smepGenWarmStartEvent smepGenLinkDownEvent smepGenLinkUpEvent smepGenAuthFailureEvent
SME Embedded Platform Enterpise versions of the generic traps
as defined RFC1215 that provide more identification of the entity
concerned.
 .1.3.6.1.4.1.6889.2.48.1.3.2.2
smepGenAppNotificationsGroup
smepGenAppEvent
The service notifications which indicate specific changes in
the state of Applications on the SME Embedded Platform.
 .1.3.6.1.4.1.6889.2.48.1.3.2.3
Compliance Statements (1)

OID .1.3.6.1.4.1.6889.2.48.1.3.1.1
The compliance statement for SME Embedded Platform agents
which implement this MIB.
Required groups
mandatory smepGenNotificationObjectsGroup
mandatory smepGenEntGenNotificationsGroup
mandatory smepGenAppNotificationsGroup
Notifications / Traps (6)
NameOIDDescription
smepGenColdStartEvent
smepGTEventStdSeverity smepGTEventDateTime smepGTEventDevID SNMPv2-MIBsysDescr
.1.3.6.1.4.1.6889.2.48.1.2.0.1
Enterprise version of standard coldstart trap featuring
device identification information. A coldStart trap
signifies that the sending protocol entity is reinitializing
itself such that the agent's configuration or the protocol
entity implementation may be altered.
smepGenWarmStartEvent
smepGTEventStdSeverity smepGTEventDateTime smepGTEventDevID SNMPv2-MIBsysDescr
.1.3.6.1.4.1.6889.2.48.1.2.0.2
Enterprise version of standard warmstart trap featuring
device identification information. A warmStart trap
signifies that the sending protocol entity is reinitializing
that neither the agent configuration nor the protocol entity
implementation is altered.
smepGenLinkDownEvent
smepGTEventStdSeverity smepGTEventDateTime smepGTEventDevID SNMPv2-MIBsysDescr IF-MIBifIndex
.1.3.6.1.4.1.6889.2.48.1.2.0.3
Enterprise version of standard linkDown trap featuring device
identification information. A linkDown trap signifies that
the sending protocol entity recognizes a failure in one of
the communication links represented in the agent's
configuration.
smepGenLinkUpEvent
smepGTEventStdSeverity smepGTEventDateTime smepGTEventDevID SNMPv2-MIBsysDescr IF-MIBifIndex
.1.3.6.1.4.1.6889.2.48.1.2.0.4
Enterprise version of standard linkUp trap featuring device
identification information. A linkUp trap signifies that the
sending protocol entity recognizes that one of the
communication links represented in the agent's configuration
has come up.
smepGenAuthFailureEvent
smepGTEventStdSeverity smepGTEventDateTime smepGTEventDevID SNMPv2-MIBsysDescr
.1.3.6.1.4.1.6889.2.48.1.2.0.5
Enterprise version of standard authenticationFailure trap
featuring device identification information. An
authenticationFailure trap signifies that the sending
protocol entity is the addressee of a protocol message that
is not properly authenticated. While implementations of the
SNMP must be capable of generating this trap, they must also
be capable of suppressing the emission of such traps via an
implementation- specific mechanism.
smepGenAppEvent
smepGTEventStdSeverity smepGTEventDateTime smepGTEventDevID SNMPv2-MIBsysDescr smepGTEventAppEntity smepGTEventAppEvent
.1.3.6.1.4.1.6889.2.48.1.2.0.6
A smepGenAppEvent notification is generated whenever a
application entity of the SME Embedded Platform experiences an
event. It signifies that the SNMP entity, acting as a proxy
for the application, has detected an event on the application
entity.

The event severity varies dependent upon the event condition.