AV-SME-PLATFORM-MIB: View SNMP OID List / Download MIB

VENDOR: AVAYA COMMUNICATION


 Home MIB: AV-SME-PLATFORM-MIB
Download as:   
SNMPv2-CONF, IF-MIB, AVAYAGEN-MIB, SNMP-FRAMEWORK-MIB, SNMPv2-SMI, ITU-ALARM-TC-MIB, SNMPv2-TC, SNMPv2-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 avSMEPlatformMIB 1.3.6.1.4.1.6889.2.48
Avaya IP Office MIBs OID tree. This MIB module defines the root items for MIBs for use with Avaya SME Embedded Platform.
       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
                   smepGenColdStartEvent 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 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 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 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 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 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.
               smepGTObjects 1.3.6.1.4.1.6889.2.48.1.2.1
                   smepGTEventStdSeverity 1.3.6.1.4.1.6889.2.48.1.2.1.1 ituperceivedseverity no-access
Severity of the event that has occurred. The event severity depends upon the type of entity/notification that the operational state change event relates to. The severity values that are normally used are detailed below: The enterprise versions of standard SNMP traps all have a severity of major (4). GenAppEvents: Severity depends on event condition crash - severity is critical (3)
                   smepGTEventDateTime 1.3.6.1.4.1.6889.2.48.1.2.1.2 dateandtime no-access
Date and time of the occurence of the event.
                   smepGTEventDevID 1.3.6.1.4.1.6889.2.48.1.2.1.3 snmpadminstring no-access
A unique textual identifier of the alarming device.
                   smepGTEventAppEntity 1.3.6.1.4.1.6889.2.48.1.2.1.4 integer no-access
The SME Embedded Platform application to which a notification/trap relates. Enumeration: 'voiceMailPro': 1, 'onex': 2, 'jade': 4, 'webmanagement': 5, 'ipOffice': 3.
                   smepGTEventAppEvent 1.3.6.1.4.1.6889.2.48.1.2.1.5 integer no-access
SME Embedded Platform application event states. The associated event severity of the notification/trap the object is carried in varies depending upon the event condition. The appropriate severity is detailed against event enumeration. Enumeration: 'crash': 1.
           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
                   smepGenCompliance 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.
               smepGenGroups 1.3.6.1.4.1.6889.2.48.1.3.2
                   smepGenNotificationObjectsGroup 1.3.6.1.4.1.6889.2.48.1.3.2.1
Objects that are contained in SME Embedded Platform wide notifications.
                   smepGenEntGenNotificationsGroup 1.3.6.1.4.1.6889.2.48.1.3.2.2
SME Embedded Platform Enterpise versions of the generic traps as defined RFC1215 that provide more identification of the entity concerned.
                   smepGenAppNotificationsGroup 1.3.6.1.4.1.6889.2.48.1.3.2.3
The service notifications which indicate specific changes in the state of Applications on the SME Embedded Platform.