Mohnomoreresourcesavailable - Cisco MCS-7825-H3-IPC1 Service Manual

Warning-Level Alarms
SDI
Parameter(s)
Memory Allocation Failure(String)
Recommended Action
Use the Real-Time Monitoring Tool to check the performance counters related to system memory, to
learn whether any memory leaks or spikes in CPU are occurring. Correct any anomalous memory issues
you find. If you do not find any issues with memory, collect the system/application event logs and the
performance (perfmon) logs and report this alarm to the Cisco Technical Assistance Center (TAC).

MohNoMoreResourcesAvailable

No more MOH resources available.
This alarm occurs when allocation of Music On Hold fails for all the registered MOH servers belonging
to the Media Resource Group List and Default List. Each MOH server may fail for different reasons.
Following are some of the reasons that could cause an MOH server allocation to fail: All the resources
of MOH server are already in use; No matching codecs or capability mismatch between the held party
and MOH server; Not enough bandwidth between the held party and MOH source; No audio stream
available for the MOH server.
History
Cisco Unified Communications
Release
8.0(1)
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Recommended Action
If all the resources of the MOH servers are already in use, check to be sure that all the MOH servers that
belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are
configured and registered in all the applicable Unified CM nodes. To check the registration status go to
the Media Resources > Music On Hold Server menu and click the Find button. It will display all the
MOH servers with their status, device pool, and so on.
Check the status field to discover whether it is registered with Unified CM. Note that the display on the
status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified
CM cluster that the Publisher can only write to the Unified CM database and the Publisher goes down.
Because the Subscriber may not be able to write to the database, the devices may still display as
registered in Unified CM Administration after they are actually unregistered. However, if the Publisher
is down that should generate another alarm with higher priority than this alarm.
Cisco Unified Communications Manager Managed Services Guide
6-270
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Action
Severity changed from Error to Warning.
OL-22523-01