AV-CORE-SERVICES-MIB

All MIBs › AV-CORE-SERVICES-MIB

Organization: Avaya, Inc.

Last Updated: 2013-03-05

Category: Telephony and VoIP, Vendor: Avaya

Description: Monitors Avaya core communication services including platform availability and critical process health status.

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-CORE-SERVICES-MIB?

AV-CORE-SERVICES-MIB is a vendor-specific MIB from Avaya Inc. supporting the "Core Services" component of its unified communications/telephony platforms. It exposes alarm and notification objects — centered on csAlarmSeverity and csNotifications — used to report the health of core platform services and processes running on Avaya communication systems. Its monitoring emphasis is squarely on software/process and platform health: it lets administrators detect when a critical Avaya core service process degrades or fails and learn the severity of that condition, functioning much like a software-service watchdog rather than a hardware sensor MIB. It is organized under Avaya's standard enterprise product/MIB registration tree (avaya/products/mibs), suggesting reliance on Avaya's broader common alarm/notification conventions across its MIB family. It is deployed on Avaya communication servers and platforms (such as Avaya Aura components) running the Core Services software layer in enterprise unified communications environments, and administrators can download the AV-CORE-SERVICES-MIB file to load into their MIB browser for reference.

IPNetwork Monitor allows you to monitor SNMP objects defined in AV-CORE-SERVICES-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 communication server / Unified Communications platform (Core Services component)

Monitoring Examples

An administrator would subscribe to csNotifications and poll the associated csAlarmSeverity object to learn when a core Avaya platform service degrades, using the severity level to triage whether the event is a minor warning or a critical service outage. A csNotifications alarm reporting a critical csAlarmSeverity for a core process would indicate that platform service has failed and needs immediate remediation to restore call/communication functionality.

What Can Be Monitored

core service alarm severity
core service fault notifications
platform/process health status

Imported Objects

From APPLICATION-MIB

applSrvName

OBJECT-TYPE

From ENTITY-MIB

entPhysicalAssetID

OBJECT-TYPE

From IP-MIB

ipAdEntAddr

OBJECT-TYPE

From ITU-ALARM-MIB

ituAlarmAdditionalText

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-MIB

sysName

OBJECT-TYPE

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
avaya	1.3.6.1.4.1.6889
products	1.3.6.1.4.1.6889.1
avCoreServicesProd	1.3.6.1.4.1.6889.1.18
mibs	1.3.6.1.4.1.6889.2
avCoreServicesMibs	1.3.6.1.4.1.6889.2.18
csmib	1.3.6.1.4.1.6889.2.18.1			A MIB to support Core Services Copyright (c) 2009-2013 by Avaya Inc. All rights reserved. Redistribution and use in source and binary forms of the software (Software), without modification, are permitted provided that the following conditions are met: (a) Redistributions of source code must retain the above copyright notice and the entire license. (b) Redistributions in binary form must reproduce the above copyright notice and this entire license in the documentation and/or other materials provided with the distribution. (c) Redistribution of the Software is solely for the purpose of managing and servicing Avaya products and solutions. (d) BY USING AND REDISTRIBUTING THE SOFTWARE, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU USE THE SOFTWARE AGREE TO ALL THE TERMS AND CONDITIONS OF THIS LICENSE AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. THIS SOFTWARE IS PROVIDED BY AVAYA INC. 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL AVAYA INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
csNotifications	1.3.6.1.4.1.6889.2.18.1.1
csDiskNotifications	1.3.6.1.4.1.6889.2.18.1.1.1
csDiskNotificationsPfx	1.3.6.1.4.1.6889.2.18.1.1.1.0
NTF csDiskStatusTimedOut	1.3.6.1.4.1.6889.2.18.1.1.1.0.1			sda status timed out (MAJOR)
NTF csDiskNotReady	1.3.6.1.4.1.6889.2.18.1.1.1.0.2			Harddrive not ready (MAJOR)
NTF csDiskResetTimedOut	1.3.6.1.4.1.6889.2.18.1.1.1.0.3			Harddrive reset timed out (MAJOR)
NTF csDiskResetMasterError	1.3.6.1.4.1.6889.2.18.1.1.1.0.4			Error reseting master (MAJOR)
NTF csDiskLostInterrupt	1.3.6.1.4.1.6889.2.18.1.1.1.0.5			Lost interrupt (MAJOR)
NTF csDiskFailed	1.3.6.1.4.1.6889.2.18.1.1.1.0.6			Disk failed (CRITICAL)
NTF csDiskStatusError	1.3.6.1.4.1.6889.2.18.1.1.1.0.7			Status error (MAJOR)
NTF csDiskUsageThreshold	1.3.6.1.4.1.6889.2.18.1.1.1.0.8			Disk usage has exceeded 80% (MAJOR)
NTF csDiskFull	1.3.6.1.4.1.6889.2.18.1.1.1.0.9			Disk is full (MAJOR)
NTF csDiskMBEDetected	1.3.6.1.4.1.6889.2.18.1.1.1.0.10			MBE detected (MAJOR)
csCPUNotifications	1.3.6.1.4.1.6889.2.18.1.1.2
csCPUNotificationsPfx	1.3.6.1.4.1.6889.2.18.1.1.2.0
NTF csCPUUtilization	1.3.6.1.4.1.6889.2.18.1.1.2.0.1			CPU utilization is at least 90% (MINOR).
csSecurityNotifications	1.3.6.1.4.1.6889.2.18.1.1.3
csSecurityNotificationsPfx	1.3.6.1.4.1.6889.2.18.1.1.3.0
NTF csSecurityLoginLockout	1.3.6.1.4.1.6889.2.18.1.1.3.0.1			Login lockout interval begins (MAJOR). This happens on the third consecutive unsuccessful login attempt. The lockput will be for 30 minutes.
NTF csSecurityLoginCorrupt	1.3.6.1.4.1.6889.2.18.1.1.3.0.2			Corrupt or expired authentication data (MAJOR).
NTF csSecurityLoginFailed	1.3.6.1.4.1.6889.2.18.1.1.3.0.3			Linux login failure - access through illegal port (MAJOR).
NTF csSecurityFileModified	1.3.6.1.4.1.6889.2.18.1.1.3.0.4			File modified. There are 3 different severities. MINOR: non-critical files of minimal security impact. MAJOR: non-critical files of significant security impact. CRIT : critical files of significant security impact.
NTF csSecurityFileRemoved	1.3.6.1.4.1.6889.2.18.1.1.3.0.5			File removed. There are 3 different severities. MINOR: non-critical files of minimal security impact. MAJOR: non-critical files of significant security impact. CRIT : critical files of significant security impact.
NTF csSecurityFileAdded	1.3.6.1.4.1.6889.2.18.1.1.3.0.6			File added. There are 3 different severities. MINOR: non-critical files of minimal security impact. MAJOR: non-critical files of significant security impact. CRIT : critical files of significant security impact.
NTF csSecurityInitFailed	1.3.6.1.4.1.6889.2.18.1.1.3.0.7			Failed initialization of Tripwire database (CRITICAL)
csWatchdogNotifications	1.3.6.1.4.1.6889.2.18.1.1.4
csWatchdogNotificationsPfx	1.3.6.1.4.1.6889.2.18.1.1.4.0
NTF csWatchdogAppStartFailed	1.3.6.1.4.1.6889.2.18.1.1.4.0.1			Application could not be started after 3 tries (MAJOR).
NTF csWatchdogInitTimedOut	1.3.6.1.4.1.6889.2.18.1.1.4.0.2			Timedout waiting for request server to initialize (MINOR).
NTF csWatchdogAppConfigParmError	1.3.6.1.4.1.6889.2.18.1.1.4.0.3			Application not started due to parameters error in configuration file (MAJOR).
NTF csWatchdogConfigError	1.3.6.1.4.1.6889.2.18.1.1.4.0.4			Application not started due to configuration file error (MAJOR).
NTF csWatchdogRollingReboot	1.3.6.1.4.1.6889.2.18.1.1.4.0.5			Watchdog detects a rolling reboot (MAJOR).
NTF csWatchdogUnintentionalDown	1.3.6.1.4.1.6889.2.18.1.1.4.0.6			Application failed unintentionally. Watchdog is bringing the system down because an application failed to start correctly (MAJOR).
NTF csWatchdogHiMonReboot	1.3.6.1.4.1.6889.2.18.1.1.4.0.7			Watchdog hi-monitor thread is rebooting the system because low-monitor thread is missing heartbeats. (MAJOR).
NTF csWatchdogStopHWTickle	1.3.6.1.4.1.6889.2.18.1.1.4.0.8			Watchdog hi-monitor thread is stopping tickling of HW (MAJOR).
NTF csWatchdogProcessSick	1.3.6.1.4.1.6889.2.18.1.1.4.0.9			Process is in a sick state (MAJOR).
NTF csWatchdogProcessUp	1.3.6.1.4.1.6889.2.18.1.1.4.0.10			Process is up (MINOR).
NTF csWatchdogProcessDown	1.3.6.1.4.1.6889.2.18.1.1.4.0.11			Process is down (MINOR).
NTF csWatchdogProcessDead	1.3.6.1.4.1.6889.2.18.1.1.4.0.12			Process is dead (MAJOR).
csModemNotifications	1.3.6.1.4.1.6889.2.18.1.1.5
csModemNotificationsPfx	1.3.6.1.4.1.6889.2.18.1.1.5.0
NTF csModemChatError	1.3.6.1.4.1.6889.2.18.1.1.5.0.1			Chat failed/interrupted (MAJOR).
csBackupNotifications	1.3.6.1.4.1.6889.2.18.1.1.6
csBackupNotificationsPfx	1.3.6.1.4.1.6889.2.18.1.1.6.0
NTF csBackupTerminated	1.3.6.1.4.1.6889.2.18.1.1.6.0.1			Scheduled backup has been terminated (MINOR)
csUpgradeNotifications	1.3.6.1.4.1.6889.2.18.1.1.7
csUpgradeNotificationsPfx	1.3.6.1.4.1.6889.2.18.1.1.7.0
NTF csUpgradeNoCommit	1.3.6.1.4.1.6889.2.18.1.1.7.0.1			An upgrade has not been committed (MAJOR). This alarm is raised if after 30 minutes, an upgrade has not been committed.
NTF csUpgradeCommit	1.3.6.1.4.1.6889.2.18.1.1.7.0.2			An upgrade has been committed (MAJOR).
NTF csUnknownNotification	1.3.6.1.4.1.6889.2.18.1.1.999			Unknown notification
csObjects	1.3.6.1.4.1.6889.2.18.1.2
csNotifyObj	1.3.6.1.4.1.6889.2.18.1.2.3
INT csAlarmSeverity	1.3.6.1.4.1.6889.2.18.1.2.3.1	INTEGER	read-only	Alarm severities are based on ITUPerceivedSeverity (RFC 3877)
csConformance	1.3.6.1.4.1.6889.2.18.1.3
csMIBCompliances	1.3.6.1.4.1.6889.2.18.1.3.1
csMIBCompliance	1.3.6.1.4.1.6889.2.18.1.3.1.1			The compliance statement for Core Services entities
csMIBGroups	1.3.6.1.4.1.6889.2.18.1.3.2
csObjGroup	1.3.6.1.4.1.6889.2.18.1.3.2.1			Core Services objects
csNotificationGroup	1.3.6.1.4.1.6889.2.18.1.3.2.2			Core Services Notifications

RFC description

Supports Avaya core services monitoring with alarm severity notifications and application service tracking.

Start monitoring Avaya communication servers 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-CORE-SERVICES-MIB

What Is AV-CORE-SERVICES-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description