one voice operations center alarms monitoring guide ver. 7 · 2020. 10. 2. · notice...

Alarms Monitoring GuideAudioCodes One Voice Operations Center (OVOC)

OVOC

Alarms

Version 7.8

Notice OVOC | Alarms Monitoring Guide

Notice

Information contained in this document is believed to be accurate and reliable at the timeof printing. However, due to ongoing product improvements and revisions, AudioCodescannot guarantee accuracy of printed material after the Date Published nor can it acceptresponsibility for errors or omissions. Updates to this document can be downloaded fromhttps://www.audiocodes.com/library/technical-documents.

This document is subject to change without notice.

Date Published: February-08-2021

WEEE EU DirectivePursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed ofwith unsorted waste. Please contact your local recycling authority for disposal of this product.

Customer SupportCustomer technical support and services are provided by AudioCodes or by an authorizedAudioCodes Service Partner. For more information on how to buy technical support forAudioCodes products and for contact information, please visit our website athttps://www.audiocodes.com/services-support/maintenance-and-support.

Documentation FeedbackAudioCodes continually strives to produce high quality documentation. If you have anycomments (suggestions or errors) regarding this document, please fill out the DocumentationFeedback form on our website at https://online.audiocodes.com/documentation-feedback.

Stay in the Loop with AudioCodes

Related Documentation

Document Name

Mediant 500MSBR User's Manual

Mediant 500L MSBR User's Manual

Mediant 500L Gateway and E-SBC User's Manual

- ii -

https://www.audiocodes.com/library/technical-documentshttps://www.audiocodes.com/services-support/maintenance-and-supporthttps://online.audiocodes.com/documentation-feedbackhttp://www.twitter.com/audiocodeshttp://www.facebook.com/audiocodeshttp://www.linkedin.com/companies/audiocodeshttp://www.youtube.com/user/audiosergehttp://blog.audiocodes.com/


Document Name

Mediant 800B Gateway and E-SBC User’s Manual

Mediant 800B MSBR User’s Manual

Mediant 1000B Gateway and E-SBC User’s Manual

Mediant 1000B MSBR User’s Manual

Mediant 2600 E-SBC User's Manual

Mediant 3000 User’s Manual

Mediant 4000 SBC User's Manual

Mediant 9000 SBC User's Manual

Mediant Software SBC User's Manual

Migration from EMS and SEM Ver. 7.2 to One Voice Operations Center

One Voice Operations Center IOMManual

One Voice Operations Center Product Description

One Voice Operations Center User’s Manual

Device Manager Pro Administrator's Manual

One Voice Operations Center Alarms Monitoring Guide

One Voice Operations Center PerformanceMonitoring Guide

One Voice Operations Center Security Guidelines

One Voice Operations Center Integration with Northbound Interfaces

Device Manager for Third-Party Vendor Products Administrator's Manual

Device Manager Agent Installation and Configuration Guide

ARMUser’s Manual

- iii -


Document Revision Record

LTRT Description

41613 ■ Added Device Alarms: DSP Farms Mismatch Alarm; Metering alarm; FlexLicenseManager alarm

■ Added OVOC Alarms: FlexPool License Usage; Report Schedulers TimeEvent; Report Schedulers Load Alarm; Report Schedulers Execution Event

■ Added Device Manager Pro alarms: VIP Endpoint is not Registered orOffline and "VIP Endpoint is Disconnected

■ Added SmartTAP alarm: Call Recording Error Event

■ Added ARM alarms: Registration Status Resync Threshold and ExternalWeb Service; Changed name for General Alarm to"No Available Routers"

■ Added User Management Pack 365 (UMP) alarms: UMP Tenant LicenseThreshold Alarm; UMPUser License Threshold Alarm; UMP Super AdminAuthentication Fail Event; UMP Azure AD Sync Alarm; UMPOffice 365Failure Alarm; UMPOffice 365 Command Execution Event; UMPUserSettings Fail Event; UMP End User Authentication Fail Event

41614 ■ Added Device alarm: RemoteMonitoring Alarm

■ Updated: Board Resetting Following Software Reset; Media TranscoderSoftware Upgrade Failure; Media Cluster Alarm

■ Correction to OID for the following alarms: FlexPool License Usage; PMHasNo SNMP Connection

41615 ■ ARM: Update to alarms Operation State Changed (Router); External WebService

■ ARM: Added alarm Operation Status Changed (Active MQ)

■ SBC: Added the following SBC alarms: Metering alarm; SDR Server alarm;KPI Threshold Crossing; Clock Configuration alarm; Debug RecordingActivation alarm

41616 ■ Update to SmartTAP: Call Recording Error Event

■ Added ARM: Disk Space Usage Alarm

- iv -

Content OVOC | Alarms Monitoring Guide

Table of Contents

1 Introduction 12 Standard Events 3

Cold Start 3Link Down 3LinkUp 4Entity Configuration Change 5Authentication Failure 5

3 Management Alarms 7EMS Trap Receiver Binding Error 7GWConnection Alarm 7GWMismatch Alarm 8ConfigurationMismatch 10OVOC Server Started 10OVOC Disk Space Alarm 11Software Replaced 12Hardware Replaced 12HTTP/HTTPS AccessDisabled 13PMFile Generated 14PMPolling Error 15Cold Start Missed 16GWBackup Event 16Security Alarm 17Security Event 18TopologyUpdate Event 19Topology File Event 20Synchronizing AlarmsEvent 21Synchronizing Active AlarmsEvent 22OVOC License Key Alarm 22Suppressed Alarm 23OVOC Keep Alive Alarm 24Pre-provisioning Alarm 25Endpoint Publish Alarm 26Disk Space Alarm 26Oracle Disk Space Alarm 27License Alarm 28Synchronizing Alarms 29QoE SipMessage Status Alarm 30Floating License Extended 31Floating License Device Report Alarm 31Floating License Register Successful Event 32

- v -


Floating License Register Failure Alarm 32Floating License Failure to Send Usage Report Alarm 33Floating License Failure to Send Extended Usage Report Alarm 33Floating License Service Shutdown Alarm 34Floating LicenseManage Devices above Allow Maximum 35Floating License Registered DevicesRequests Capacity 35AlarmsOverflow 36Alarms Forward Overflow 37FQDN Resolve Event 37PMTimeout Event 38PMToken Pool is Empty 39PMPolling Status Event 39PMBatchOverflow Alarm 42PMHasNo SNMP Connection 43FlexPool License Usage 43

4 Voice Quality Package Alarms 45OVOC QoE - Failed Calls Alarm 45OVOC QoE – Poor Voice Quality Alarm 46OVOC QoE - Average Call Duration Alarm 48OVOC QoE - License Key Alarm 49OVOC QoE - System Load Alarm 50Call Details Storage Level Change 51Call QualityMonitoring Connection Status Alarm 52OVOC QoE - Skype for Business SQL Server Connection Lost Alarm 53OVOC QoE - Active Directory Server Connection Lost Alarm 54OVOC QoE - Media Bandwidth Alarm 54OVOC QoE - RuleMaxConcurrent Calls Alarm 56Report Schedulers Time Event 57Report Schedulers Load Alarm 58Report Schedulers Execution Event 59

5 Device Manager Alarms 60Registration Failure Alarm 60IP Phone SurvivableMode Start Alarm 60IP Phone Lync Login Failure Alarm 61Endpoint License Alarm 62Endpoint Server Overloaded Alarm 63IP Phone Speaker Firmware Download Failure 63IP Phone Speaker Firmware Upgrade Failure 64IP Phone Conference Speaker Connection Failure 65

65IP PhoneGeneral Local Event 65IP PhoneWeb Successive Login Failure 66

- vi -


67IP Phone Requires Reset 67Jabra Firmware Upgrade Failed 68VIP Endpoint is Not Registered or Offline 68VIP Endpoint is Disconnected 69

6 OVOC Managed Devices Alarms 71Support Matrix 71CommonDevice Alarms 84

Board Fatal Error 84Entity Configuration Change 85Configuration Error 86Initialization Ended 87Board Resetting Following Software Reset 87Feature Key Related Error 88Gateway Administrative State Changed 88No Free Channels Available 90Gatekeeper/Proxy not Found or Registration Failed 91Ethernet Link Down Alarm 93System Component Overloaded 94Active Alarms Table Overflow 95Operation State Change [Node] 96Keep Alive Trap 97NAT Traversal Alarm 98Enhanced BIT Status Trap 99Threshold of PerformanceMonitored Object Exceeded 100HTTP Download Result 100IPv6 101SAS Emergency Mode Alarm 102Software Upgrade Alarm 103NTP Server Status Alarm 103LDAP Lost Connection 104SSH Connection Status [Event] 105OCSP Server Status Alarm 105Media Process Overload Alarm 106Ethernet Group Alarm 106Media Realm BW Threshold Alarm 107Certificate Expiry Notification 108WebUser Access Disabled 109Proxy Connection Lost 109IDS Policy Alarm 111IDS Threshold Cross Notification 112IDS Blacklist Notification 113Proxy Connectivity 114WebUser Activity Log Trap 115

- vii -


HTTP Proxy Service Alarm 116Answer-Seizure Ratio Threshold Alarm 117Average Call Duration Threshold Alarm 118Network Effectiveness Ratio Threshold Alarm 119IP Group NoRoute Alarm 120TLS Certificate Expiry Alarm 121NGINX Configuration is not Valid 123NGINX Process is not Running 124RemoteMonitoring Alarm 124SDR Server Alarm 125KPI Threshold Crossing 126Clock Configuration Alarm 127Debug Recording Activation Alarm 127

Specific Hardware Alarms 128Temperature Alarm 128Fan Tray Alarm 129Power Supply Alarm 130

HA SystemAlarms 132HA System Fault Alarm 132HA System ConfigurationMismatch Alarm 137HA System Switch Over Alarm 138Hitless Software Upgrade Alarm 138Redundant Board Alarm 139HA Network Watchdog Status Alarm 140License Key Hitless Upgrade Alarm 141HA Network Mismatch Alarm 142HA Network Monitor Alarm 143HA Ethernet Group Alarm 144

License Pool Alarms 144License Pool Infra Alarm 144License Pool Application Alarm 146License Pool Over Allocation Alarm 147

Floating License Alarms 148Floating License Alarm - Not EnoughMemory to Allocate 'Custom' Profile 148Cloud LicenseManager Alarm 149Flex LicenseManager Alarm 152

Mediant 2600 E-SBCandMediant 4000 AlarmsSBC 153DSP Farms Mismatch Alarm 153

Mediant 9000 and Software SBC Alarms 154Cluster HA Alarm 154Media Transcoder Network Failure 155Media Transcoder Software Upgrade Failure 156Media Transcoder High Temperature Failure 157Media Transcoder Fan Tray Module Failure 158Media Transcoder Power Supply Module Failure 159

- viii -


Cluster Bandwidth Utilization Alarm 159Media Cluster Alarm 161Remote Interface Alarm 162AWS Security Role Alarm 163CDR Server Alarm 164Metering Alarm 165

MP-1288 Alarms 166Module Service Alarm 166Module Operation Alarm 167Port Service Alarm 168

MSBR Alarms 170WAN Link Alarm 170Power Over Ethernet Status [Event] 170Wireless Cellular Modem Alarm 171Wireless Cellular Modem Status Changed 172Data Interface Status 172NQMConnectivity Alarm 173NQMRTT Alarm 174NQM Jitter Alarm 174NQM Packet Loss Alarm 175NQMMOS CQAlarm 176NQMMOS LQAlarm 177

Mediant 3000 Hardware Alarms 178PEMModule Alarm 178SA ModuleMissing Alarm 179User Input Alarm 180TM Inconsistency 180TM Reference Status 181TM Reference Change 182

PSTN Trunk Alarms 182D-Channel Status 182SONET Section LOF Alarm 183SONET Section LOS Alarm 184SONET Line AIS Alarm 185SONET Line RDI Alarm 186SONET/SDN IF Failure Alarm 186Trunk LOS Alarm 187Trunk LOF Alarm 188Trunk AIS Alarm 189Trunk RAI Alarm 189V5.2 Interface Alarm 190SONET Path STS LOP Alarm 191SONET Path STS AIS Alarm 192SONET Path STS RDI Alarm 192SONET Path Unequipped Alarm 193

- ix -


SONET Path Signal Label Alarm 194DS1 Line Status Alarm 194DS3RAI Alarm 196DS3 AIS Alarm 196DS3 LOF Alarm 197DS3 LOS Alarm 197NFAS Group Alarm 198B Channel Alarm 199

Analog Port Alarms 200Analog Port SPI Out of Service 200Analog Port High Temperature 200Analog Port Ground Fault Out-of-Service Alarm 201Dial Plan File Replaced Trap 201Analog Line Left Off Hook Alarm 202

Microsoft PlatformAlarms 202Component Unreachable 203Component Restart 203Component Performance Counter General 204Component Performance Counter Service 205Component Service Status 206Component Event Viewer 207Component Event Viewer Past Hours 207Component Event Viewer Dropped 208Certificate Expired 209CloudBond Disk Space 210

User Management Pack 365 (UMP) Alarms 211UMP Tenant License Threshold Alarm 211UMP User License Threshold Alarm 211UMP Super Admin Authentication Fail Event 212UMP Azure AD Sync Alarm 213UMP Office 365 Failure Alarm 214UMP Office 365 Command Execution Event 214UMP User Settings Fail Event 215UMP EndUser Authentication Fail Event 216

CloudBond 365 Alarms 216Commit License Failed 216Admin License Expired 217

CCE Appliance Alarms 218Alarm – Admin System Cloud Status 218CCE Appliance Certificate Expired Alarm 219CCEWrongOperating Alarm 220CCEWrong Settings Alarm 221CCE Disk Space Alarm 222CCEWindows License Alarm 223

SBA Alarms 224

- x -


Alarm –CPU Status 224SBA Memory Status 225SBA Disk Space Alarm 226SBA Certificate Expired 227Alarm – Performance Counter 228SBA Services Status Alarm 229

SmartTAP Alarms 230Alarm –Component Unreachable 230SmartTAP Event – Component Restart 231Event – Component Resource Failed 231Alarm - Component Resource Threshold Exceeded 234Alarm –Connection Failure 236Call Recording Error Event 238Alarm –Certificate Expired 241Alarm –Component Event Viewer Dropped 241Alarm –Component Performance Counter General 242Alarm –Component Service Status 244Alarm –Disk Space 246

7 ARM Alarms 247Disk Size Illegal 247Disk Space Usage 247ARMLicense About to Expire 248ARMLicense has Expired 249ARMLicense Session Number 250ARMLicenseMissing 251Quality Change 251ARMConfigurator Reload 252ARMRouter Reload 253ARM Routing RuleMatch 254ARM Configuration Inconsistency 254Operation State Changed (Router) 255Operation Status Changed [Node] 257Operation Status Changed [Peer Connection] 259Operation Status Changed [LDAP Server] 260Operational Status Changed [ActiveMQ] 261Limit Reached 262Router Using Other Configurator 262NTP Sync Status 263No Available Routers 264Registration Status Resync Threshold 265ExternalWeb Service 266Disk Usage Alarm 267

- xi -

CHAPTER 1 Introduction OVOC | Alarms Monitoring Guide

1 IntroductionThis document describes alarms that are raised on OVOC and its managed entities. Thesealarms are displayed in the One Voice Operations Center Web interface Active Alarms table.Supported alarms / events can fall into one of these three categories:

■ Standard traps: traps originated by the media gateway / server - all the standard traps aretreated are events.

■ Proprietary alarms / events: traps originated by the media gateway / server and defined inthe gateway proprietary MIB.

■ OVOC alarms / events: traps originated by OVOC application and defined in the OVOCproprietary MIB.

To determine which traps are defined as Events refer to 'Alarm Name' or 'Alarm Title' fields inthe table. All the events are marked with [Event] prefix in the OVOC Active Alarms table andAlarms History windows.

Each alarm / event described in this section includes the following information:

Alarm Field Description

Alarm Title (Name) The alarm name, as it appears in the OVOC Active Alarms andHistory tables.

Description Documented description of the alarm.

SNMP Trap Name NOTIFICATION-TYPE Name as it appears in theMIB.

SNMPOID NOTIFICATION-TYPE OID as it appears in theMIB. CorrectiveAction Possible corrective action when applicable. - 1

Alarm Source Possible values of sources if applicable to a specific alarm. Thisvalue is displayed from the variable-bindingtgTrapGlobalsSource

Alarm Type Alarm type according to ITU X.733 definition. This value isdisplayed from the variable-binding tgTrapGlobalsType.

Probable Cause Alarm probable cause according to ITU X.733 definition. Thisvalue is displayed from the variable-bindingtgTrapGlobalsProbableCause.

Additional Info Additional information fields provided by MG application,depending on the specific scenario. These values are displayedfrom tgTrapGlobalsAdditionalInfo1,tgTrapGlobalsAdditionalInfo2 andtgTrapGlobalsAdditionalInfo3. The document includes a few

- 1 -

CHAPTER 1 Introduction OVOC | Alarms Monitoring Guide


examples of the possible values of this field.

Alarm Severity Condition TextCorrectiveAction

Possible severity value. This value isdisplayed from thevariable-bindingtgTrapGlobalsSeverity.

Conditionupon whichthe alarm israised forthe specificseverity.There maybe severalconditionsfor eachseverity.

Textual description of specificproblem. This value is displayedfrom the variablebindingtgTrapGlobalsTextualDescription. The document includes a fewexamples of the possible valuesof this field.

Possiblecorrectiveactionwhenapplicable.

- 2 -

CHAPTER 2 Standard Events OVOC | Alarms Monitoring Guide

2 Standard Events

Cold Start


Description SNMPv2-MIB: A coldStart trap signifies that the SNMP entity, supporting anotification originator application, is reinitializing itself and that itsconfiguration may have been altered.

SNMP Alarm coldStart

SNMPOID 1.3.6.1.6.3.1.1.5.1

Alarm Title [Event] Cold Start

Alarm Source -

Alarm Type Communication Alarm

ProbableCause

Other

Severity Clear

AdditionalInfo1,2,3

-

CorrectiveAction

-

Link Down


Description SNMPv2-MIB: A linkDown trap signifies that the SNMP entity, acting in anagent role, has detected that the ifOperStatus object for one of itscommunication links is about to enter the down state from some otherstate (but not from the notPresent state). This other state is indicated bythe included value of ifOperStatus.

SNMP Alarm [Event] linkDown

- 3 -



SNMPOID 1.3.6.1.6.3.1.1.5.3

Alarm Title Link Down


Alarm Source -

ProbableCause

Other

Severity Major

AdditionalInfo1,2,3

-

CorrectiveAction

-

Link Up


Description SNMPv2-MIB: A linkUp trap signifies that the SNMP entity, acting in anagent role, has detected that the ifOperStatus object for one of itscommunication links left the down state and transitioned into someother state (but not into the notPresent state). This other state isindicated by the included value of ifOperStatus.

SNMP Alarm [Event] linkUp

SNMPOID 1.3.6.1.6.3.1.1.5.4

Alarm Title Link Up

Alarm Source -


ProbableCause

Other

Severity Clear

Additional -

- 4 -



Info1,2,3

CorrectiveAction

-

Entity Configuration Change


Description Entity-MIB: An entConfigChange notification is generated when the valueof entLastChangeTime changes.

SNMP Alarm [Event] entConfigChange

SNMPOID 1.3.6.1.2.1.47.2.0.1

Alarm Title Entity Configuration Change

Alarm Type Equipment Alarm

Alarm Source -

ProbableCause

Other

Severity Info

AdditionalInfo1,2,3

-

CorrectiveAction

-

Authentication Failure


Description SNMPv2-MIB: An authenticationFailure trap signifies that the SNMP entityhas received a protocol message that is no properly authenticated. Whileall implementations of SNMP entities MAY be capable of generating thistrap, the snmpEnableAuthenTraps object indicates whether this trap willbe generated.

- 5 -



SNMP Alarm [Event] authenticationFailure

SNMPOID 1.3.6.1.6.3.1.1.5.5

Alarm Title Authentication Failure

Alarm Source -


ProbableCause

Other

Severity Major

AdditionalInfo1,2,3

-

CorrectiveAction

-

- 6 -

CHAPTER 3 Management Alarms OVOC | Alarms Monitoring Guide

3 Management Alarms

EMS Trap Receiver Binding Error


Description This alarm is generated during server startup if an erroroccurs indicating that the SNMP trap receiver port isalready taken.

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.1

SNMP Alarm acEMSSnmpCannotBindError

Alarm Title [Event] EMS Trap Receiver Binding Error

Alarm Source OVOC Mgmt

Alarm Type Environmental Alarm

Probable Cause Application Subsystem Failure

Severity Critical

Additional Info -

Corrective Action Run netstats command to verify which application usesthe alarms reception port (by default UDP post 162).

■ OVOC application: If it's busy, check which applicationuses this port. If it's not freed by OVOC application,restart the OVOC server application as described inthe OVOC Server IOM.

■ Other network management application: changeOVOC application and all managed gateways' defaultalarm reception ports.

Media Gateways All the gateways managed by OVOC

GW Connection Alarm


Description Originated by OVOC when an SNMP Timeout occurs for the first timein theMedia Gateway.

- 7 -



SNMP Alarm acEMSNodeConnectionLostAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.3

Alarm Title GW Connection Alarm

Alarm Source Media Gateway

Alarm Type Communications Alarm

Probable Cause Communications Subsystem Failure

Severity Critical

Additional Info When an SBA is configured, displays the 'SBA Description' field.

Corrective Action Communication problem: Try to ping the gateway to check if thereis network communication.

■ Default gateway alive: Open the network screen. Check thedefault gateway IP address and ping it.

■ SNMP Community Strings: Verify that the community stringdefined in OVOC for the gateway matchs the actual gatewaycommunity strings. To check the community string, right-clickon the gateway, select the 'Details' menu. Default communitystrings: read = public, write = private.

■ Hardware Problem: Check that the gateway is alive according tothe LEDs. Verify that network and power cables are in place andplugged in.

Media Gateways All the gateways managed by OVOC

GWMismatch Alarm


Description Activated when OVOC detects a hardware, software, predefine orconfiguration mismatch.

■ SoftwareMismatch: Activated when OVOC detects a softwareversion mismatch between the actual and the previous definition oftheMedia Gateway (for example, Version 4.0.353 instead of thepreviously defined 4.0.278). This is also the case when the newversion is not defined in the SoftwareManager.

- 8 -



■ HardwareMismatch: Activated when OVOC detects a hardwaremismatch between the actual and the previous definition of a MediaGateway.

■ Configuration Mismatch: Activated when OVOC detects aconfiguration mismatch between the actual parameter valuesprovisioned and previous parameter values provisioned.

SNMP Alarm acEMSNoMismatchNodeAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.9

Alarm Title GWMismatch Alarm

Alarm Source ■ Media Gateway/Software

■ Media Gateway/Hardware

■ Media Gateway/Configuration


ProbableCause

Other

Severity Clear

Additional Info -

CorrectiveAction

■ SoftwareMismatch:

✔ Define the detected version in the OVOC SoftwareManager

✔ Perform a Software Upgrade on the gateway with one of thesupported versions.

■ HardwareMismatch:

✔ Perform remove / add a device in order to resync OVOC and thegateway status

✔ Verify in the SoftwareManager that an appropriate versionexists for the hardware type displayed in the error message

■ Configuration Mismatch:

✔ Run Configuration Verification command in order to compareOVOC configuration and actual MG configuration:

-MG configuration is incorrect: use configuration download toupdate MGwith correct configuration saved in OVOC database.

- 9 -



-MG is correct, OVOC is not updated: use configuration uploadto save a correct MG configuration in OVOC database.

■ Check the Actions Journal for recent updates of the gateway.

MediaGateways

All the gateways managed by OVOC.

Configuration Mismatch


Description This alarm is raised when there are missing or incorrect parametersvalues received from a managed entity.

SNMP Alarm acEMSConfigurationMismatchNodeAlarm

SNMPOID .1.3.6.1.4.1.5003.9.20.3.2.0.7

Alarm Title Configuration Mismatch


Alarm Type Other

ProbableCause

Other

Severity Minor

Additional Info -

CorrectiveAction

-

OVOC Server Started


Description Event raised each time the OVOC server is started or restarted (warmboot/reboot) by the OVOC Watchdog Process.

SNMPOID acEMSServerStartup- 1.3.6.1.4.1.5003.9.20.3.2.0.11

- 10 -



AlarmTitle [Event] OVOC Server Started

AlarmSource Management


Probable Cause Other

Severity Major

Additional Info -

CorrectiveAction

-

Media Gate-ways


OVOC Disk Space Alarm


Description The usage size (in %) on the disk partition of the #application type #ap-plication name is ‘Dangerously High’ or ‘Almost Full’.

SNMP Alarm acEMSNotEnoughDiskSpaceAlarm

SNMP OID .1.3.6.1.4.1.5003.9.20.3.2.0.12

AlarmTitle Disk Space Alarm

AlarmType Equipment Alarm

AlarmSource OVOC Mgmt

Probable Cause Storage Capacity Problem

Severity ■ More than 70% -minor

■ 80-90 – major

■ More than 90 - critical

Alarm Text {0}% of the disk is used in data partition. Free some disk space to avoidsystem failure.

- 11 -



Additional Info

CorrectiveAction

Free disk space

Software Replaced


Description Originates when OVOC discovers a software version replace betweenboard versions, for example, from V4.6.009.004 to V4.6.152.003 (whenboth versions are managed by OVOC ). Software Replace old version : new version .

SNMP Alarm acEMSSoftwareReplaceAlarm-

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.14

Alarm Title [Event] Software Replaced



ProbableCause

Other

Severity Info

Additional Info If you initiated a performance measurements polling process beforeyou initiated the software replacement process, the polling process isstopped.

CorrectiveAction

No action should be taken; this is an information alarm.

MediaGateways


Hardware Replaced


Description Originated when OVOC discovers a different gateway (according to the

- 12 -



MAC address) to what was initially defined, while the Hardware Typeremains the same.

Hardware Replace is discovered by theMAC address and performedduring Board Started trap.

SNMP Alarm acEMSHardwareReplaceAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.15

Alarm Title [Event] Hardware Replaced


Alarm Source Media Gateway

ProbableCause

Other

Severity Major

AdditionalInfo

-

CorrectiveAction

-

MediaGateways

MediaPacks, Mediant 1000, Mediant 2000, Mediant 3000

HTTP/HTTPS Access Disabled


Description Originated when HTTP access is disabled by OVOC hardening; howeverOVOC manages media gateways that require HTTP access for softwareupgrade. Originated on server startup.

SNMP Alarm acEMSHTTPDisabled

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.16

Alarm Title [Event] HTTP/HTTPS Access Disabled

Alarm Type Environmental Alarm

- 13 -




ProbableCause

Application Subsystem Failure

Severity Major

AdditionalInfo

-

CorrectiveAction

Separate the gateways between two OVOC servers (secured &unsecured)

MediaGateways

Gateways using the HTTP server for the software upgrade procedure:MediaPacks, Mediant 1000, Mediant 2000, Mediant 3000

PM File Generated


Description Originated when a PM file is generated in the OVOC server, and it can beretrieved by a higher level management system.

SNMP Alarm acEMSPmFileGenerate

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.18

Alarm Title [Event] PM File Generated


Alarm Type Other

ProbableCause

Other

Severity Info

AdditionalInfo

The performance summary data from to of media gateway was saved in PMfile .

CorrectiveAction

-

- 14 -



MediaGateways

All Gateways

PM Polling Error


Description Originated when a History PM stops collecting performance summarydata from MG. Possible reasons are: NTP synchronization lost,Connection Loss, SWMismatch, etc.

SNMP Alarm acEMSPmHistoryAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.19

Alarm Title [Event] PM Polling Error


Alarm Type Other

ProbableCause

Other

Severity Minor

Additional Info -

CorrectiveAction

Verify in the 'Description' (see above) the reason why the PM historystopped.

■ When the reason is 'NTP synchronization lost', verify that thegateway and the OVOC server machine are synchronized to the sameNTP server and have accurate time definitions.

■ When the reason is 'Software Mismatch', you can stop the PMhistory collection until the new version is added to the SoftwareManager.

■ When the reason is 'Connection Loss' between the OVOC server andthe gateway, polling continues automatically when the connection isre-established; the purpose of the alarm in this case is to informusers of missing samples.

Note: The alarm continues to activate every 15minutes unless you fixthe problem or manually stop PM polling of the gateway.

- 15 -



Media Gate-ways

All Gateways

Cold Start Missed


Description Originated when Carrier Grade Alarm System recognizes coldStart traphas been missed.

SNMP Alarm acEMSNodeColdStartMissedEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.20

Alarm Title [Event] Cold Start Missed

Alarm Source -

Alarm Type Other

ProbableCause

Receive failure

Severity Clear

AdditionalInfo

-

CorrectiveAction

-

MediaGateways

All the managed Gateways

GW Backup Event


Description This alarm is raised when an AudioCodes device configuration filecannot be retrieved due to insufficient disk space or periodic backupoperation failure.

SNMP Alarm acEMSMGBackupEvent

- 16 -



SNMPOID .1.3.6.1.4.1.5003.9.20.3.2.0.21

Alarm Title GW Backup Event

Alarm Source

Alarm Type Other


Additional Info -


Minor periodic backupfailed due toinsufficient diskspace

Backup file from IP:{0} with MGname: {1} was not retrieveddue to low OVOC Mgmt diskspace.

Check disk andfree somespace.

Minor periodicbackupbackupfailed

Periodic Backup operationfailed for MG {0}

with IP:{1}

Indeterminate periodic backupsuccess

backup file: {file} from ip: {ip}with mg name: {name} wassuccessfully retrieved.

Security Alarm


Description Activated when one or more RADIUS servers are not reachable. Whennone of the RADIUS servers can be reached, a Critical Severity alarm isgenerated.

SNMP Alarm acEMSSecurityAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.23

Alarm Title Security Alarm

Alarm Source OVOC Mgmt/ Radius

- 17 -



Alarm Type Processing Error Alarm

ProbableCause

Other

Severity Minor, Major, Critical

AdditionalInfo

-

CorrectiveAction

-

Media Gate-ways

-

Security Event


Description This event is generated when a specific user is blocked after reaching themaximum number of login attempts, or when the OVOC failed to syncOVOC and Mediant 5000 / 8000 users.

SNMP Alarm acEMSSecurityEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.24

Alarm Title [Event] Security Event

Alarm Source OVOC Mgmt/ User Name,

OVOC Mgmt/ User Sync

Alarm Type Other

ProbableCause

Other

Severity Indeterminate

AdditionalInfo

-

CorrectiveAction

-

- 18 -



Media Gate-ways

-

Topology Update Event


Description This event is issued by OVOC when a Gateway or Region isadded/removed/updated in OVOC and includes the followinginformation:

■ Action: Add / Remove / Update GW or Region

■ Region Name

■ GW Name

■ GW IP

Note: For opening an EMS client in theMG context, the gateway IPaddress should be provided.

SNMP Alarm acEMSTopologyUpdateEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.25

Alarm Title [Event] Topology Update


Alarm Type Other



Additional Info Additional Info 1 field will include following details:

Region: X1 'X2' [GW: Y1 'Y2' 'Y3' 'Y4']

X1 = Region ID (unique identifier in the OVOC data base used for regionidentification)

X2 = Region name as it defined by OVOC operator

Y1 = GW ID (unique identifier in the OVOC data base used for GWidentification)

Y2 = GW Name as it defined by OVOC operator

Y3 = GW IP as it defined by OVOC operator

Y4 = GW Type as it identified by OVOC during the first connection to the

- 19 -



gateway. If first connection was not successful during the addoperation, it will trigger an 'Add GW' event with Unknown GW type, and'Update GW' event once the initial connection to the gateway has beensuccess full. The following gateways will be supported: MP,M1K, M2K,M3K, M5K, M8K

Region details will always be part of the alarm, while GW info will bedisplayed when event is gateway-related.

All the fields related to the gateway will always be displayed to alloweasy parsing.

Examples:

(Description=Add Region) Region: 7 'Test Lab'

(Description=Update Region) Region: 7 'My Updated Region'

(Description=Add GW) Region: 7 'My Updated Region', GW: 22'MG14' '1.2.3.4' 'Unknown', PM Polling: disabled

(Description=Update GW) Region: 7 'My Updated Region', GW: 22'My MG 15' '4.5.6.7' 'M3K'

(Description=Update GW) Region: 7 'My Updated Region', GW: 22'My MG 15' '4.5.6.7', PM Polling: enabled

(Description=Remove GW) Region: 7 'My Updated Region', GW: 22'My MG 15' '4.5.6.7' 'M3K', Polling: enabled

(Description=Remove Region) Region: 7 'My Updated Region'

CorrectiveAction

-

Media Gate-ways

-

Topology File Event


Description This event is issued by OVOC when the Topology File is updated on theOVOC server machine. The Topology file is automatically updated uponthe addition /removal of a Media Gateway or upon updates to theMediaGateway properties. For more information, refer to the NorthboundIntegration Guide.

SNMPName acEMSTopologyFileEvent-

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.26

- 20 -



Alarm Title [Event] Topology File


Alarm Type Other

ProbableCause

Other


AdditionalInfo

File Name: MGsTopologyList.csv

CorrectiveAction

-

Media Gate-ways

-

Synchronizing Alarms Event


Description This event is issued when the OVOC is not able to retrieve the entiremissing alarms list from the History table. Information regarding thenumber of retrieved alarms, and number of alarms OVOC failed toretrieve is provided in the Additional Info field.

SNMP Alarm acEMSSyncAlarmEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.27

Alarm Title [Event] Synchronizing Alarms


Alarm Type Other


ProbableCause

Other

Additional Info Retrieved x missed alarms, failed to retrieve y alarms.

- 21 -



CorrectiveAction

-

MediaGateways

-

Synchronizing Active Alarms Event


Description This event is issued when OVOC is not able to perform synchronizationwith the History alarms table, and instead performs synchronizationwith the Active Alarms Table.

SNMP Alarm acEMSSyncActiveAlarmEvent -

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.28

Alarm Title [Event] Synchronizing Active Alarms


Alarm Type Other

ProbableCause

Other


Additional Info -

CorrectiveAction

-

Media Gate-ways

-

OVOC License Key Alarm


Description This alarm is raised when the OVOC License key has expired or the OVOCmanagement license (License key) on the device is missing.

- 22 -



SNMP Alarm acEMSLicenseKeyAlarm

SNMPOID .1.3.6.1.4.1.5003.9.20.3.2.0.29

Alarm Title OVOC License Key Alarm

Alarm Source OVOC Mgmt/license

Alarm Type other

ProbableCause

keyexpired

AdditionalInfo

In case the OVOC license expires:

OVOC license key expiration date:

CorrectiveAction

In case the OVOC license expires:

■ Contact AudioCodes for new license

In case of the missing license in device:

■ If required, contact AudioCodes for new license

AlarmSeverity

Condition TextCorrectiveAction

Critical expired OVOC Mgmt ApplicationLicense is expired

Major Month before OVOC Mgmt ApplicationLicense will be expired withinone month

Critical Device not haveOVOCmanagementlicense

GWmanagement is notcovered by current OVOCMgmt Application License

Suppressed Alarm


Description This alarm is sent when the OVOC suppresses alarms (of the same alarmtype and alarm source), once the number of such alarms reaches aconfigured threshold level in a configured interval (configured in the

- 23 -



OVOC Alarms Settings screen). When this alarm is sent, such alarms arenot added to the OVOC database and are not forwarded to configureddestinations.

SNMP Alarm acEMSAlarmSuppression

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.42

Alarm Title The name of the suppressed alarm

Alarm Source OVOC Mgmt or OVOC QoE/

Alarm Text Alarm Suppression activated

Alarm Type Other

ProbableCause

Threshold crossed.


StatusChanges

The alarm is cleared when in the subsequent interval, the number ofsuch alarms falls below the configured threshold. Once the alarm iscleared, then these alarms are once more added to the OVOC databaseand forwarded to configured destinations.

Additional Info -

CorrectiveAction

Investigate the recurrence of such alarms.

OVOC Keep Alive Alarm


Description This alarm indicates that an SNMP Keep-alive trap has been sent fromOVOC to a third-party destination such as a Syslog server to indicateOVOC liveness (configured in the OVOC Alarms Settings window).

SNMP Alarm EMSKeepAliveAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.45

Alarm Title OVOC Keep Alive Alarm

- 24 -




Alarm Text Management Keep-Alive

DefaultSeverity

Indeterminate

Alarm Type Other

ProbableCause

Other

CorrectiveAction

-

Pre-provisioning Alarm


Description This alarm is generated when the operation for pre-provisioning thedevice upon initial connection to OVOC fails.

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.46

AlarmTitle Pre-Provisioning


AlarmType operational/Violation

Probable Cause The template file could not be applied to the device because there was amismatch between the template file and the device’s existing ini file orthere was a mismatch between the device type and the firmware fileapplied to the device.

Severity Critical

Additional Info -

CorrectiveAction

■ When this alarm is raised, you cannot reload configuration orfirmware files to the device as it has already been connected toOVOC. Instead download these files to the device using the SoftwareManager and then use the 'Software Upgrade' action.

OR

- 25 -



■ Remove the device from OVOC and then reconnect it i.e. repeat thepre-provisioning process.

Media Gate-ways

All gateways managed by OVOC.

Endpoint Publish Alarm


Description This alarm is raised when problems arise with the SIP Publish reportingfor voice quality metrics (port 5060) from endpoints (RFC 6035).

■ When a SIP Publish message is missing mandatory parameter/srequired by OVOC to handle this message.

■ When SIP Publish message time is not synchronized with OVOCserver.

SNMP Alarm acEndpointPublishAlarm

SNMPOID .1.3.6.1.4.1.5003.9.20.3.2.0.47

Alarm Title Endpoint Publish Alarm

Alarm Source OVOC_QoE/

Alarm Type Communications alarm

Alarm Text Bad Publish Message. Device IP: {ip}, Device MAC: {mac}.

ProbableCause

Communications protocol error

AdditionalInfo

Possible reasons:

Mandatory Field/s Missing.

Endpoint Server and Device Synchronization Error.

Severity Minor

Disk Space Alarm

Alarm Fields Description

Description This alarm is issued in one of the following cases:

- 26 -



■ The Archive Logs directory capacity has reached {0}%.

■ The Oracle partition capacity has reached {0}%.

SNMP Alarm acEMSDiskSpaceAlarmCheck

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.51

AlarmTitle Disk Space Alarm




Severity ■ 70%






Severity ■ 70%



AlarmSeverity

Condition Corrective Action

Critical The licenseexpirationdate is lessthan equal to7 days.

■ OVOCLicense isabout to expirein {0} days.

■ OVOC License isabout to expirein 1 day.

■ OVOC LicenseWill ExpireToday

Contact your AudioCodes part-ner ASAP. Note that when noti-fication that this license hasexpired is received, the serverremains connected for a fewminutes in order to allow the for-warding traps to northbounddestinations.

Major The licenseexpirationdate is morethan 7 daysand less thanequal to 30days.

OVOC License isabout to expire in{0} days.

Clear The licenseexpirationdate isgreater than30 days.

Synchronizing Alarms


Description This event is sent out to an SMMPNBI using user defined alarmsforwarding rules once the NMS has activated the ReSync Alarms feature.

SNMP Alarm ac OCReSyncEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.58

Alarm Title [Event] Synchronizing Alarms


Alarm Type Other

- 29 -




ProbableCause

Other

AdditionalInfo

-

CorrectiveAction

-

MediaGateways

-

QoE Sip Message Status Alarm


Description Alarm is raised when device notify OVOC that it stop sending SIPmes-sages. cleared when it notify that it continue sending SIPmessages

SNMP Alarm acSEMSipMessageStatusAlarm

SNMP OID .1.3.6.1.4.1.5003.9.20.3.2.0.60

AlarmTitle QoE: Sip Message Status Alarm

AlarmType OVOC QOE/

AlarmSource Communications Alarm

Probable Cause Communications Subsystem Failure

Severity Critical

Alarm Text Device Stopped Sending Sip Ladder Messages

Additional Info

CorrectiveAction

- 30 -


Floating License Extended


Description This alarm is raised when IP phones are added to OVOC and as a resultlicenses are extended beyond the pre-existing tenant allocation; wherethere are insufficient licenses currently allocated to the phone’sdesignated tenant. In this case, OVOC checks the number of freeavailable licenses (licensees that are not assigned to any tenant) andthen takes 5% of the current tenant allocation (a minimum of five, or theremaining licenses) and dynamically adds them to the phone’s tenant.The licenses are taken from the OVOC License “Managed Endpoints”feature license if the endpoint is managed by IP PhoneManager Pro orfrom the “Voice Quality Endpoints" feature if the phones are managed inthe OVOC for Voice Quality (“QOE Supported” in OVOC Web). If both ofthese license features are managed for the endpoint, the license is takenaccording to the license availability for the respective tenant licenseallocation. For example, if the endpoint is licensed for both of thesecategories and there also insufficient licenses allocated for bothcategories, then the dynamic license allocation is separately executedand therefore separate events are raised.

SNMP Alarm floatingLicenseExtended

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.61

Alarm Title Floating License Extended

Alarm Source The tenant on which the license is extended.

Alarm Type Other

Severity Indeterminate (info)

ProbableCause

Other

Floating License Device Report Alarm

Alarm Field Details

Description This alarm is raised when the device does not send a usage report for[calc duration] minutes or more to OVOC.

SNMP Alarm acClmDeviceReportAlarm

- 31 -


Alarm Field Details

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.62

Alarm Title Floating license Device missing report

Alarm Source Floating license/Device#[Device Id]

Alarm Type Communication

Severity Major

ProbableCause

Other

Floating License Register Successful Event


Description This alarm is raised when OVOC successfully registers to Floating Licenseat [DNS address].

SNMP Alarm acClmRegisterSuccessfulEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.63

Alarm Title Floating license Cloud Service registration successful

Alarm Source Floating license


Severity Info

ProbableCause

Other

Floating License Register Failure Alarm


Description This alarm is raised when OVOC fails to register to Floating License CloudService at [DNS address], Reason: [Error description or timeout]

SNMP Alarm acClmRegisterFailureAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.64

- 32 -



Alarm Title Fail to register to Cloud Service



Severity Critical

ProbableCause

Communications Protocol Error

Floating License Failure to Send Usage Report Alarm


Description This alarm is raised when OVOC fails in two attempts to send usagereport to Floating LIcense Cloud Service Service. This service shuts downif the problem not fixed by the configured period (default 90 days).

Note: this time period is configured by AudioCodes on the FloatingLicense Service.

SNMP Alarm acClmFailToSendUsageReportAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.65

Alarm Title Failed to send usage report to Cloud Service



Severity Major

ProbableCause


Floating License Failure to Send Extended Usage Report Alarm


Description This alarm is raised when OVOC fails to send usage reports to theFloating License Cloud Service . This alarm is raised one week prior to theshutdown date (default 90 days).

Note: this time period is configured by AudioCodes on the Floating

- 33 -



License Service.

SNMP Alarm acClmFailToSendUsageReportExtendedAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.66

Alarm Title Failed to send usage report to Floating License Cloud Service



Alarm Text OVOC failed to send usage report to Floating License Cloud Service.Service will shutdown if problem not fixed by 90 days

Severity Critical

ProbableCause


Floating License Service Shutdown Alarm


Description Floating License service shutdown, reason: failure to communicate withcloud service for [(ovocNoResponseHours-144) *60/ovocReportIntervalMin] minutes.

SNMP Alarm acClmServiceShutdownAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.67

Alarm Title Service Shutdown



Severity Critical

ProbableCause

Application Subsystem Failure

- 34 -


Floating License Manage Devices above Allow Maximum


Description This alarm is raised when the maximum number of devices managed bythe floating license is reduced to less than the currently registered count(the number of devices that have registered to OVOC and the FloatingLicense service and are currently managed by the floating license). Forexample, if there are 30 devices registered and are currently managed bythe floating license in OVOC, and then the maximum number of devicessupported by the license is reduced to 20 devices, then this alarm will beraised.

SNMP Alarm acClmMaxDeviceMismatchEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.68

Alarm Title Floating license Manage devices above allowmaximum


Alarm Type Other

AlarmSeverity

Info

ProbableCause

Other

AdditionalInfo

-

CorrectiveAction

-

Floating License Registered Devices Requests Capacity


Description This alarm is raised when there is an attempt to register a device forfloating license management that is above the OVOC maximum floatinglicense capacity.

SNMP Alarm acClmMaxDeviceCapacityAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.69

- 35 -



Alarm Title Floating license registered devices requests capacity.


Alarm Type Other

AlarmSeverity

Critical

ProbableCause

Other

AdditionalInfo

-

CorrectiveAction

-

Alarms Overflow


Description This alarm is raised when one of the alarm processing queues reachedtheir threshold which prevented the receiving of new alarms.

SNMP Alarm acAlarmsOverflow

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.71

Alarm Title Alarms Overflow


Alarm Type Other

ProbableCause

Threshold Crossed

Severity Major

AdditionalInfo

-

CorrectiveAction

-

- 36 -


Alarms Forward Overflow


Description This alarm is raised when one of the alarms forwarding processingqueues reached their threshold prevented the forwarding of new alarms

SNMP Alarm acAlarmsFwOverflow

SNMPOID .1.3.6.1.4.1.5003.9.20.3.2.0.72

Alarm Title Alarms Forward Overflow


Alarm Type Other

Severity Major

ProbableCause

Threshold Crossed

AdditionalInfo

-

CorrectiveAction

-

FQDN Resolve Event


Description This alarm is raised when the FQDN for logging into the device cannot beresolved.

SNMP Alarm acEMSFQDNResolveEvent

SNMPOID .1.3.6.1.4.1.5003.9.20.3.2.0.73

Alarm Title FQDN Resolve Event

Alarm Source Device IP

Alarm Type Other

ProbableCause

Other

- 37 -



AdditionalInfo

CorrectiveAction

Check if another device with the same IP already exists in OVOC (same asthe resolved configured FQDN).

AlarmSeverity

Condition Text Corrective Action

Major FQDN : resolved to IP: .

IP address already exist .

IP address for node name changed to emptyvalue

Major FQDN : resolved to IP: .

IP address for node name changed to

PM Timeout Event


Description This system event is raised when the polling interval has expired and notall of the parameters that were defined in the assigned PM profile wereyet polled.

SNMP Alarm acPmTimeOutEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.74

Alarm Source OVOC Mgmt/ PMHandler

Alarm Title PM Timeout Event

Alarm Type Other

ProbableCause

Other

EventSeverity

Condition CorrectiveAction

- 38 -



Critical The polling interval hasexpired and not all of theparameters that weredefined in the PM profilewere yet polled.

Message: PM Timeout ;startTime= 12:00 ;endTime= 12:15 ;currentTime= 12:14:30 ;timeout= 30 sec beforeendTime

Check networkperformance.

Cleared - -

PM Token Pool is Empty


Description This system event is raised when the number of parameters polled forthe current interval has reached its maximum capacity.

SNMP Alarm acPMTokenPooisEmpty

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.75

Alarm Source OVOC Mgmt/ PM Token Pool Handler

Alarm Title PM Token Pool is Empty-Event

Alarm Type Other

ProbableCause

Other

AlarmSeverity

Condition Corrective Action

Critical The number ofparameters polledfor this intervalhas reached itsmaximumcapacity.

Message: 500,000tokens have alreadybeen used, no more DBtransactions is allowedon this pm iteration.

Check the number ofparameters and devicesconfigured in thePM Profile and reducethe load accordingly.

PM Polling Status Event

Alarm Details Description

Description This event is raised per managed polled entity under the following

- 39 -



circumstances:

■ When a specific device is successfully polled.

■ For the failure scenarios described below.

This event is sent only when the 'Send Event per Interval'parameter is enabled in the PerformanceMonitoring profile.

SNMP Alarm acDevicePmPollingEvent

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.76

Alarm Title PM Polling Status Event

Alarm Source OVOC Mgmt/ PMHandle

Alarm Type Other


Alarm Severity Condition Corrective Action

Indeterminate Raised when thedevice issuccessfullypolled.

Success: PM pollingoperation was successfullyfinished.deviceName=Device Name ;deviceIp= 1.1.1.1 ;pollingTimeStamp= 12:15

-

Major The time formatfor the device'ssystem clock isin a differentformat to thetime settings forthe OVOC serverclock.

Device time has not validformat

Synchronize thetime settings.

Deviceconnectiontimeout

Device timeout Troubleshoot thedevice connection.

Deviceconfiguration is

Device is not Sync Download updatedconfiguration to

- 40 -



notsynchronized

the device.

Device is polledwhen the tokenpool did nothave sufficientallocations.

Token pool has not enoughallocations

Analyze the pollingload.

The device doesnot have a validMIB version.

Device has not valid MIBversion

Verify the device'sMIB version.

The device's MIBversion is notsupported forthePM parameter.

Device's MIB version is notsupporting PM, currentversion= v7.0

Refer to thePerformanceMonitoring Guidefor the supportedMIB version for thePM parameter.

The OVOCserverPerformanceMonitoringSNMP processused to managethe connectionwith themanaged devicehas failed.

Device has no SNMPconnection with OVOC.

Check theSNMP connectionbetween thedevice and theOVOC server.

A PM profile hasnot beenassigned to thedevice.

Device is not attached toany PM profile.

Assign a PM profileto the device.

The Token pooldoes not havesufficientallocations.

Token pool has not enoughallocations

Check the numberof parameters anddevices configuredin the PM Profileand reduce the loadaccordingly.

The device was Device was restarted less Wait at least 15

- 41 -



restarted lessthan 15minutesago.

than 15minutes ago minutes for thepolling operationto recommence.

The last pollingreason type wasunknown.

UnknownLastPollingFailReasonTypefailure

-

Cleared - - -

PM Batch Overflow Alarm


Description This system alarm is raised when the database buffer for the polledinterval has reached its maximum capacity.

SNMP Alarm acPmBatchOverFlowAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.77

Alarm Source OVOC Mgmt/ PM Batch Handler

Alarm Title PM Batch OverFlow Alarm

Alarm Type Other

ProbableCause

Other

AlarmSeverity


Critical The PM batchhandler bufferhas reachedmaximumcapacity.

PM's batch handler reached his maxbuffer capacity= 15000, while hiscurrent size= 15000. Polling operationwill be stopped until the buffer will becleared.

-.

Cleared - -

- 42 -


PM Has No SNMP Connection


Description This system event is raised when the internal SNMP process for managingthe polling operation fails.

SNMP Alarm acPmHasNoSnmpConnection

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.78

Alarm Source OVOC Mgmt/ PM Token Pool Handler

Alarm Title PMHas No SNMP Connection

Alarm Type Other

ProbableCause

Other

AlarmSeverity


Critical The internalSNMP process formanaging the pollingoperation has failed.

PM process has no SNMP con-nection to theMain SNMP service; startTime= 12:00 ; endTime=12:15 ; currentTime= 12:01

-

Cleared - -

FlexPool License Usage


Description This alarm is raised when a FlexPool License parameter is approachingor has reached its maximum value.

SNMP Alarm acFlexPoolLicenseUsage

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.85

Alarm Title FlexPool license parameter license usage

Alarm Source FlexPool/[license parameter name]

Alarm Type Other

- 43 -



ProbableCause

Other

AlarmSeverity


Critical FlexPool license parameter hasexceeded its maximum value.

FlexPoollicenseparameter[name] is overlicense limit.

Renew floatinglicense or reducecurrentconsumption.

Minor FlexPool license parameter isapproaching its maximumvalue according to the settingfor the Flex Pool OVOC WebConfiguration parameter"Alarm Threshold Percentage"(default 85%).

FlexPoollicenseparameter[name] isapproachingmaximumutilization.

Renew floatinglicense or reducecurrentconsumption.

- 44 -

CHAPTER 4 Voice Quality Package Alarms OVOC | Alarms Monitoring Guide

4 Voice Quality Package Alarms

OVOC QoE - Failed Calls Alarm


Description This alarm is raised when the % number of failed calls forthe managed node or link crosses the threshold and iscleared when the failed calls ratio returns below thethreshold value. The description field includes the info:Failed X1% of calls, X2 of X3 calls.

The threshold for this alarm is set in the QoE Status andAlarms Details window.

SNMP OID acVoice QualityRuleFailedCallsAlarm

SNMP Alarm 1.3.6.1.4.1.5003.9.20.3.2.0.30

Alarm Title Voice Quality - Failed Calls Alarm

Alarm Source OVOC QoE/Device/Link/Site/Endpoint

Alarm Type Quality of service alarm.

ProbableCause

The minimum or maximum threshold is crossed.

Additional Info Critical or Major severity threshold is Y%:

■ Critical Threshold: 10 % of calls (default)

■ Major Threshold: 2 % of calls (default)

Where Y% is the % failed calls per managed node or linkthat is measured for a total time of 180minutes period(three hours) and according to “Monitoring FrequencyMin”. For example, if this parameter is set to 15minutes,sampling is performed at 15:15 (from 12:15 to 15:30) andthen at 15:30 (from 12:30 to 15:30) and so on.


Critical This alarm is raisedwhen Y % of calls (rep-resenting the con-figured critical

Y% of failedcalls hascrossed the"Critical"

Investigatethe source(device or link)of the failed

- 45 -



threshold) made bythe managed node orlink for the sampledperiod fail (see above).

threshold calls.

Major This alarm is raisedwhen Y % of calls (rep-resenting the con-figured majorthreshold) made bythe managed node orlink for the sampledperiod fail (see above).

Y% number offailed calls forhas crossedthe "Major"threshold.

Clear Cleared when thefailed calls ratioreturns below thethreshold value forthe sampled period.

-

OVOC QoE – Poor Voice Quality Alarm


Description This alarm is raised when the % number of poor qualitycalls polled for the managed node or link crosses thethreshold and is cleared when the poor quality calls ratioreturns below the threshold value. The description fieldincludes the info: Poor Quality X1% of calls, X2 of X3 calls.


SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.31

SNMP Alarm acVoiceQualityRulePoorQualityCallsAlarm

Alarm Title Voice Quality – Voice Quality Alarm


Alarm Type Quality of service alarm

ProbableCause


- 46 -



Additional Info Critical or Major severity threshold is Y%:

■ Critical Threshold: 10% of calls (default).

■ Major Threshold: 2% of calls (default)

Where Y% is the % poor quality calls per managed node orlink that is measured for a total time of 180minutesperiod (three hours) and according to “MonitoringFrequency Min”. For example, if this parameter is set to 15minutes, sampling is performed at 15:15 (from 12:15 to15:15) and then at 15:30 (from 12:30 to 15:30) and so on.


Critical This alarm is raisedwhen Y% (representingthe configured criticalthreshold) of callsmade by the managednode or link for thesampled period (seeabove) are of poorquality.

Y% calls havecrossed the"Critical"threshold.

Investigatethe source(device or link)of the poorquality calls.

Major This alarm is raisedwhen Y %(representing theconfigured majorthreshold) of calls bythe managed node orlink for the sampledperiod (see above) areof poor quality.

Y% calls havecrossed the"Major"threshold.

Clear Cleared when the poorquality calls ratioreturns below thethreshold value for thesampled period (seeabove).

-

- 47 -


OVOC QoE - Average Call Duration Alarm


Description This alarm is raised when the average call duration timethreshold for the managed node or link is crossed and iscleared when the average call duration time ratio returnsbelow the threshold value. The description field includesthe info: Average Call Duration is Y sec.


SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.32

SNMP Alarm acVoice QualityRuleAvrgCallDurationAlarm

Alarm Title Voice Quality – Average Call Duration Alarm



ProbableCause


Additional Info ■ Critical Threshold: average call duration of 3 seconds(default).

■ Major Threshold: average call duration of 5 seconds(default)

Where measured per managed node or link for a totaltime of 180minutes period (three hours) and according to“Monitoring Frequency Min”. For example, if thisparameter is set to 15minutes, sampling is performed at15:15 (from 12:15 to 15:15) and then at 15:30 (for 12:30-15:30) and so on.


Critical This alarm is raisedwhen the average callduration for themanaged node or linkfor the sampled period(see above) falls to theconfigured critical

Average CallDuration"Critical"thresholdhas beenreached.

Investigatethe source(device orlink)reporting theexcessiveaverage call

- 48 -



threshold value. duration.

Major This alarm is raisedwhen the average callduration for themanaged node or linkfor the sampled period(see above) falls to theconfigured majorthreshold value.

Average CallDuration"Major"thresholdhas beenreached.

Clear Cleared when theaverage call durationreturns below thethreshold value for thesampled period (seeabove)

-

OVOC QoE - License Key Alarm


Description This alarm is sent in the following circumstances:

■ When the number of devices connected to the OVOC approaches orreaches license capacity (shown as 'Devices Number' in OVOC serverManager License screen).

■ When the number of sessions running on the OVOC approaches orreaches license capacity (shown as 'Voice Quality Sessions' in theOVOC Server Manager License screen).

SNMP Alarm acVoice QualityLicenseKeyAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.33

Alarm Title Voice Quality License key alarm

AlarmsSource

OVOC QoE

Alarm Type Other

ProbableCause

Key Expired

- 49 -



AdditionalInfo

CorrectiveAction

Contact your AudioCodes representitve to obtain the required licensekey.

AlarmSeverity


Critical The number of currently running ses-sions/devices has reached 100% of theVoice Quality servers license capacity.

Currentserver loadreached100% ofVOICEQUALITYLicense capa-city.

-

Major The number of currently runningsessions/devices has reached 80% ofVoice Quality servers license capacity.

Currentserver loadreached80% ofVoiceQualityLicensecapacity.

-

Clear The number of currently runningsessions/devices has dropped below80% of Voice Quality servers licensecapacity.

Clearingcurrentlyactivedevicealarm.

-

OVOC QoE - System Load Alarm


Description This alarm is sent when the Voice Quality system capacity is high and thesystem consequently becomes overloaded. Three levels are supported:

■ Major -> Events are not stored. Trend Info will not be displayed.

■ Critical -> Green calls are not stored.

■ Minor - > Events are not stored for green calls. Trend Info will not be

- 50 -



displayed.

SNMP Alarm acVoice QualityCallDroppedAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.34

Alarm Title ■ Voice Quality – System Load Alarm

Alarm Source OVOC QoE


ProbableCause

AlarmProbableCauseType.THRESHOLDCROSSED

Severity MINOR/ MAJOR/ CRITICAL

AdditionalInfo

■ Medium load level is reached - {0}%, {1} calls of {2}. /

■ High load level is reached - {0}%, {1} calls of {2}. /

■ Approaching maximal system capacity - {0}%, {1} calls of {2}.

CorrectiveAction

Reduce the system load.

Call Details Storage Level Change


Description This alarm is sent when the operator changes the Call Details StorageLevel from one level to another.

SNMP Alarm acVoice QualityClientLoadFlagAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.35

Alarm Title Voice Quality – Call Details Storage Level has been changed.

Alarm Source OVOC QoE


ProbableCause

Threshold crossed

- 51 -




AdditionalInfo

-

CorrectiveAction

-

Call Quality Monitoring Connection Status Alarm


Description This alarm is sent when connectivity is lost between the managed deviceand Voice Quality Package server.

SNMP Alarm acSEMConnectionStatusAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.36

Alarm Title Voice Quality – OVOC QoE - Connection Status Alarm

Alarm Source OVOC QoE/Device

Alarm Type communicationsAlarm

ProbableCause

communicationsSubsystemFailure

AdditionalInfo

One of the following reasons will appear:

■ Server Time: {0}, Device Time: {1}.

■ Please check your NTP Configuration in Device.

■ NTP Servers are not configured in the Device.

■ Please make sure that time in OVOC QoE Server and Device isproperly synchronized.

■ NTP configuration is correct, please check your network conditions(Firewalls, Ports, etc .) and make sure that NTP sync of OVOC QoEServer and/or Devices is performed correctly.

■ You have complex network configuration in OVOC Mgmt/OVOC QoEserver. Please refer to OVOC Mgmt client / Help menu / OVOC MgmtConfiguration frame to verify network configuration.

Alarm Condition Text CorrectiveAction

- 52 -



Severity

Critical Insufficientmemory buffer.

There isn't enoughbuffer size toallocate for mainmessages queue ofthis board.

The OVOC server hasreached its maximummanagement capacity.Contact AudioCodesCustomer Support.

Connection lossbetween OVOCand the device.

OVOC QoEconnection lost.

Check your networkconfiguration on both thedevice and OVOC server.

Clear Server and Deviceare notsynchronized.

Server Time: {0},Device Time: {1}.

Check your NTPConfiguration in device.

Connection isestablishedbetween thedevice and OVOC.

OVOC QoEconnectionestablished. Serverand Device are nowSynchronized.

-

Synchronizationbetween serverand device.

Server and Deviceare nowSynchronized.

-

OVOC QoE - Skype for Business SQL Server Connection LostAlarm


Description This alarm is sent when there is no connectivity with the Lync SQL Serverdatabase.

SNMP Alarm acMSLyncConnectionAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.37

Alarm Title Voice Quality AD Lync Connection Alarm

Alarm Source OVOC QoE/Device


- 53 -



ProbableCause

Communications sub-system failure

Severity Critical

AdditionalInfo

-

CorrectiveAction

Check the Lync SQL server for problems.

OVOC QoE - Active Directory Server Connection Lost Alarm


Description This alarm is sent when there is no connectivity with the Active DirectoryLDAP server.

SNMP Alarm acVoice QualityMSLyncADServerAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.38

Alarm Title Voice Quality MS Lync AD Server Alarm

Alarm Source OVOC QoE/Active Directory


ProbableCause

Communications sub-system failure

Severity Critical

AdditionalInfo

■ Voice Quality - AD Lync connection alarm

CorrectiveAction

Check theMS Lync AD server for problems.

OVOC QoE - Media Bandwidth Alarm


Description This alarm is sent when the media bandwidth for the node

- 54 -



or link falls below or exceeds the threshold values con-figured in the QoE Status and Alarms Details window.

SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.43

SNMP Alarm acVoice QualityRuleBandwidthAlarm

Alarm Title Voice Quality Rule Bandwidth Alarm

Alarm Source VOC QoE/Device/Link/Site/Endpoint


ProbableCause

Threshold crossed

Additional Info ■ Critical Threshold: 10 Kb/ sec (default).

■ Major Threshold: 5 Kb/ sec (default)

Where measured per managed node or link for a totaltime of 180minutes period (three hours) and accordingto “Monitoring Frequency Min” For example, if thisparameter is set to 15minutes, sampling is performed at15:15 (from 12:15 to 15:15) and then at 15:30 (for 12:30-15:30) and so on.


Critical This alarm is raisedwhen the maximumbandwidth for thesampled period (seeabove) reaches theconfigured criticalthreshold value.

MaximumBandwidth ofX Kb/sec

Check thenode's orlink's max-imum band-width capacitymatches therequired capa-city.

Major This alarm is raisedwhen the maximumbandwidth for thesampled period (seeabove) reaches theconfigured majorthreshold value.

MaximumBandwidth ofX Kb/sec

- 55 -



Clear Cleared when the max-imum bandwidth forthe sampled periodincreases above theconfigured thresholdsfor the sampled period(see above).

-

OVOC QoE - Rule Max Concurrent Calls Alarm


Description This alarm is sent when the maximum concurrent calls forthe node or link falls below or exceeds the threshold val-ues configured in QoE Status and Alarms Details window.

SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.44

SNMP Alarm acVoice QualityRuleMaxConcurrentCallsAlarm

Alarm Title Rule Max Concurrent Calls Alarm

Alarm Source OVOC QoE/Node/Link/Site/Endpoint


ProbableCause

Threshold crossed

Additional Info ■ Critical Threshold: 10 Calls (default).

■ Major Threshold: 5 Calls (default)

Where measured per managed node or link for a totaltime of 180minutes period (three hours) and accordingto “Monitoring Frequency Min”. For example, if thisparameter is set to 15minutes, sampling is performed at15:15 (from 12:15 to 15:15) and then at 15:30 (from 12:30to 15:30) and so on.


Critical This alarm is raisedwhen the number of

Max Con-current Calls of

Check that thenode's or link's

- 56 -



concurrent callsreaches the con-figured criticalthreshold for thesampled period (seeabove).

X maximum num-ber of con-current callsmatches therequired capa-city.

Major This alarm is raisedwhen the number ofconcurrent callsreaches the con-figured majorthreshold for thesampled period (seeabove)..

Max Con-current Calls ofX

Clear This alarm is raisedwhen the number ofconcurrent calls fallswithin the configuredthreshold for thesampled period (seeabove).

-

Report Schedulers Time Event


Description This event is raised when the Reports Scheduler misses a scheduledexecution time.

SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.82

SNMP Alarm acReportSchedulersTimeEvent

Alarm Title Report Schedulers Time Event

Alarm Source OVOC QoE/Report Scheduler

Alarm Type Other

ProbableCause

Other

- 57 -




Major The sched-uler missesthe exe-cution time.

Example : Scheduler ZAdmin_pre-defined Has Missed his ExecutionTime, Schedulers Next Run: 2019-12-22 05:00:00.0, While Current Time:Sun Dec 22 05:00:20 GMT 2019

-

Report Schedulers Load Alarm


Description This alarm is raised when the Report Scheduler's buffer reachesmaximum it's capacity.

SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.83

SNMP Alarm acReportSchedulersLoadAlarm

Alarm Title Report Schedulers Load Alarm


Alarm Type Other

ProbableCause

Other


CRITICAL Schedulers Exe-cution Queuehas reached max-imum buffercapacity.

Schedulers Queue HasReached His Max BufferCapacity= ,New Schedulers Will NotBe Executed

Reduce thenumber ofscheduledreports.

MAJOR Schedulers Exe-cution Queuehas reached 80%of its maximumbuffer capacity.

Schedulers Queue HasReached 80%Of His MaxBuffer Capa-city= , His Cur-rent QueueSize=

- 58 -


Report Schedulers Execution Event


Description This event is raised when the execution of the report that is attachedto the Scheduler fails.

SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.84

SNMP Alarm acReportSchedulersExecutionEvent

Alarm Title Report Schedulers Execution Event


Alarm Type Other

ProbableCause

Other


Critical Execution ofreport whichis attachedto the sched-uler fails.

Example: SchedulerExecuter: Cal-culation of report result has beenfailed ; schedulerName=Test_Topo-logy_Trend ; reportName=TestTrend_Report ; executionTime=Wed Dec 1106:46:00 GMT 2019 ; actu-alRunTime=Wed Dec 11 06:46:00 GMT2019

-

- 59 -

CHAPTER 5 Device Manager Alarms OVOC | Alarms Monitoring Guide

5 Device Manager Alarms

Registration Failure Alarm


Description This alarm is raised when a SIP registration (with a PBX) for the IP Phonefails.

SNMP Alarm IPPhoneRegisterFailure

SNMP OID 1.3.6.1.4.1.5003.9.20.3.2.0.39

Alarm Title Registration Failure

Alarm Source IP Phone

Alarm Type communicationsAlarm(1)

ProbableCause

communicationsProtocolError(5)

Severity Critical

CorrectiveAction

The problem is typically not related to the phone, however to the server.The user/phone may not be defined, or may be incorrectly defined, ormay previously have been defined but the username (for example) mayhave been changed, causing the registration to fail. Make sure theusername and password credentials are identical in the server andphone, and weren't changed; server-phone credentials must besynchronized. Make sure the server is responsive.

IP Phone Survivable Mode Start Alarm


Description This alarm is raised when the IP Phone enters Survivable mode state withlimited services in theMicrosoft Lync environment.

SNMP Alarm IPPhoneSurvivableModeStart

OID 1.3.6.1.4.1.5003.9.20.3.2.0.40

Alarm Title Survivable Mode Start

- 60 -




Alarm Type Other(0)

ProbableCause

other (0)

Severity Major

CorrectiveAction

The problem is typically not related to the phone, but to the server ornetwork. Make sure all servers in the enterprise's network are up. If oneis down, limited service will result.

IP Phone Lync Login Failure Alarm


Description This alarm is raised when the IP Phone fails to connect to Microsoft LyncServer during sign in.

SNMP Alarm IPPhoneLyncLoginFailure

OID 1.3.6.1.4.1.5003.9.20.3.2.0.41

Alarm Title Lync Login Failure


Alarm Type communicationsAlarm(1)

ProbableCause

communicationsProtocolError(5)

Severity Critical

AdditionalInfo

TlsConnectionFailure

NtpServerError

CorrectiveAction

This alarm may typically occur if the user is not registered - or isregistered incorrectly - in the Lync Server. Make sure that username,password and PIN code are correctly configured and valid in the LyncServer. Try resetting them. Try redefining the user.

- 61 -


Endpoint License Alarm

Table 5-1: Endpoint License Alarm


Description This alarm is issued for the following scenarios:

■ When the number of endpoints currently running on the VoiceQuality server (shown as 'IP Phones Number' under 'Voice Quality' inthe OVOC Server Manager License screen) approaches or reaches itslicense capacity.

■ When the number of managed endpoints currently running on theOVOC server (shown in the License screen License screen)approaches or reaches its license capacity.

SNMP Alarm acEndpointLicenseAlarm

SNMPOID 1.3.6.1.4.1.5003.9.20.3.2.0.48

Alarm Title Endpoint License Alarm

Alarm Source Voice Quality/Management

Alarm Type Other

ProbableCause

Key Expired

AdditionalInfo

Endpoint License capacity {0} devices.

CorrectiveAction

Contact your AudioCodes partner ASAP

Alarm Severity Condition Text Corrective Action

Critical Currently connecteddevices are equivelant to100% of EndpointsLicense capacity.

Currently runningdevices reached100% of EndpointsLicense capacity.

-

Major Currently connecteddevices are equivelant to reached 80% of EndpointsLicense capacity.

Currently runningdevices reached80% of EndpointsLicense capacity.

-

Clear Clearing currently active Clear - Clearing -

- 62 -



alarm currently activealarm.

Endpoint Server Overloaded Alarm


Description This alarm is issued when the Voice Quality Endpoint server process isoverloaded with RFC 6035 Publish messages. This causes new RFC 6035SIP PUBLISH messages () to be dropped from the queue for this process.

SNMP Alarm acEndpointServerOverlo

one voice operations center alarms monitoring guide ver. 7 · 2020. 10. 2. · notice...

Documents