AV-SME-PLATFORM-MIB
The AV-SME-PLATFORM-MIB provides the root OID tree for monitoring and managing the Avaya SME Embedded Platform, serving as the foundational structure for accessing specific hardware and software metrics such as system health, resource utilization, and service states within Avaya IP Office environments.
Imported Objects
Objects
24 total| Object Name |
|---|
avSMEPlatformMIBAvaya IP Office MIBs OID tree. This MIB module defines the root items for MIBs for use with Avaya SME Embedded Platform. MODULE-IDENTITY .1.3.6.1.4.1.6889.2.48 |
smepGeneric OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1 |
smepGenMibs OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1.1 |
smepGenTraps OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1.2 |
smepGTEvents OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1.2.0 |
smepGenColdStartEventEnterprise 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. NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.48.1.2.0.1 |
smepGenWarmStartEventEnterprise 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. NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.48.1.2.0.2 |
smepGenLinkDownEventEnterprise 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. NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.48.1.2.0.3 |
smepGenLinkUpEventEnterprise 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. NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.48.1.2.0.4 |
smepGenAuthFailureEventEnterprise 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. NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.48.1.2.0.5 |
smepGenAppEventA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.6889.2.48.1.2.0.6 |
smepGTObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1.2.1 |
smepGTEventStdSeveritySeverity 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)ro ItuPerceivedSeverity (ITU-ALARM-TC-MIB) .1.3.6.1.4.1.6889.2.48.1.2.1.1 |
smepGTEventDateTimeDate and time of the occurence of the event.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.6889.2.48.1.2.1.2 |
smepGTEventDevIDA unique textual identifier of the alarming device.ro SnmpAdminString .1.3.6.1.4.1.6889.2.48.1.2.1.3 |
smepGTEventAppEntityThe SME Embedded Platform application to which a notification/trap relates.ro Enumeration .1.3.6.1.4.1.6889.2.48.1.2.1.4 |
smepGTEventAppEventSME 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.ro Enumeration .1.3.6.1.4.1.6889.2.48.1.2.1.5 |
smepGenConformance OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1.3 |
smepGenCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1.3.1 |
smepGenComplianceThe compliance statement for SME Embedded Platform agents which implement this MIB.deprecated Unknown .1.3.6.1.4.1.6889.2.48.1.3.1.1 |
smepGenGroups OBJECT IDENTIFIER .1.3.6.1.4.1.6889.2.48.1.3.2 |
smepGenNotificationObjectsGroupObjects that are contained in SME Embedded Platform wide notifications. Unknown .1.3.6.1.4.1.6889.2.48.1.3.2.1 |
smepGenEntGenNotificationsGroupSME Embedded Platform Enterpise versions of the generic traps as defined RFC1215 that provide more identification of the entity concerned. Unknown .1.3.6.1.4.1.6889.2.48.1.3.2.2 |
smepGenAppNotificationsGroupThe service notifications which indicate specific changes in the state of Applications on the SME Embedded Platform. Unknown .1.3.6.1.4.1.6889.2.48.1.3.2.3 |
More MIBs from Avaya
Browse all AvayaMIBs →Standard SNMP MIB module defining data structures for G3-AVAYA-MIB.
SNMP MIB module
The Avaya-96xxIPTelephone-MIB enables SNMP-based monitoring and management of Avaya 96xx series IP telephones running Release S3.1, providing access to device-specific operational metrics such as call session states, network interface statistics, hardware status indicators, and firmware versioning data.
The Avaya-46xxIPTelephone-MIB facilitates SNMP-based monitoring and management of Avaya 46xx series IP telephones (firmware through Release 2.8) by exposing device status, port statistics, call session states, and power consumption metrics compliant with COMPAS 75441 standards.
The Avaya_46xxIPTelephone-MIB enables SNMP-based monitoring and management of Avaya 46xx series IP telephones (up to Release 2.8) by exposing device operational status, port statistics, and call session metrics defined in the COMPAS 75441 specification.
The IPO-PROD-MIB module registers specific sysObjectID values to uniquely identify Avaya IP Office telephone switches within an SNMP management station, enabling the differentiation of these hardware devices from other network elements during monitoring and polling operations.