AV-SME-PLATFORM-MIB

All MIBs › AV-SME-PLATFORM-MIB

Organization: Avaya Inc.

Last Updated: 2013-01-11

Description: MIB for Avaya IP Office SME Embedded Platform, defining the root OID tree and generic event/notification objects for platform-wide monitoring

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is AV-SME-PLATFORM-MIB?

AV-SME-PLATFORM-MIB defines the root OID tree for Avaya's SME (Small/Medium Enterprise) Embedded Platform within Avaya IP Office, along with a generic, platform-wide event/notification object model. Rather than exposing detailed per-subsystem metrics itself, it supplies shared event fields - severity, timestamp, device ID, application entity, and application-specific event code - used consistently across other IP Office MIBs to report faults. Its main monitoring role is as the fault/notification layer for the whole embedded platform, letting an operator detect abnormal software/application events across multiple embedded services on the appliance via a common trap structure. Other, more specific Avaya IP Office component MIBs depend on and plug into this root tree and generic event object model. It is deployed on Avaya IP Office SME Embedded Platform appliances/servers in small-to-medium business telephony environments. Engineers can download the AV-SME-PLATFORM-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in AV-SME-PLATFORM-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Avaya IP Office SME Embedded Platform appliance

Monitoring Examples

An NMS would trap on smepGTEvents and inspect smepGTEventStdSeverity, smepGTEventDateTime, smepGTEventDevID, and smepGTEventAppEntity/smepGTEventAppEvent to identify which embedded application raised a fault and how severe it is. A burst of high-severity events sharing the same smepGTEventAppEntity would indicate one particular subsystem on the platform is failing repeatedly.

What Can Be Monitored

platform event severity
event timestamp
originating device/application ID
application-specific event code

Imported Objects

From AVAYAGEN-MIB

avayaMibs

OBJECT-IDENTITY

From IF-MIB

ifIndex

OBJECT-TYPE

From ITU-ALARM-TC-MIB

ItuPerceivedSeverity

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-MIB

sysDescr

OBJECT-TYPE

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DateAndTime

OIDs

OID symbolic	OID numeric	Type	Access	Description
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
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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.
NTF 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
ITU smepGTEventStdSeverity	1.3.6.1.4.1.6889.2.48.1.2.1.1	ItuPerceivedSeverity	accessible-for-notify	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)
DAT smepGTEventDateTime	1.3.6.1.4.1.6889.2.48.1.2.1.2	DateAndTime	accessible-for-notify	Date and time of the occurence of the event.
STR smepGTEventDevID	1.3.6.1.4.1.6889.2.48.1.2.1.3	SnmpAdminString	accessible-for-notify	A unique textual identifier of the alarming device.
INT smepGTEventAppEntity	1.3.6.1.4.1.6889.2.48.1.2.1.4	INTEGER	accessible-for-notify	The SME Embedded Platform application to which a notification/trap relates.
INT smepGTEventAppEvent	1.3.6.1.4.1.6889.2.48.1.2.1.5	INTEGER	accessible-for-notify	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.
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.

RFC description

Defines OID tree and platform-level metrics for Avaya SME (Small/Medium Enterprise) embedded systems.

Start monitoring Avaya IP Office SME Embedded Platform appliances with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download AV-SME-PLATFORM-MIB

What Is AV-SME-PLATFORM-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description