Tms Memory Alarms; Tms Pll Alarms - Avaya Media Processing Server 500 Hardware Installation And Maintenance

Operation and Administration

TMS Memory Alarms

TMS supports two types of memory: CPU memory and Voice memory. CPU memory is allocated
and freed in the normal processing of a call. Voice memory is used by player, recorder, and fax
resources.
Any memory allocation alarm indicates that a request made on the part of an application is not
completed. Under certain load scenarios, a TMS can temporarily run out of memory but recover
without any adverse side effect. Applications can cycle then recover on the next call instance.
Situations that can have a temporary affect on memory are system failover and Ethernet problems.
The following modules can cause TMS memory alarms:
• TMS runtime image that uses player, recorder, or fax resources.
The TMS memory can generate alarms due to the following conditions:
• Faulty hardware
• Undetected software error causing memory leak
• Hardware software race condition causing memory leak
• Insufficient memory configuration for software load
• System load
• Ethernet problem
• System failover
Troubleshooting TMS Memory Alarms
Check for the following conditions.
1. If the problem occurred after updating packages or applications, there is a software issue
with the new load or there is insufficient memory on the TMS to support the new images.
2. Use a web interface to the TMS to determine which processes are consuming memory on
the TMS.
3. Check for Ethernet problems on the network.

TMS PLL Alarms

The TMS PLL synchronizes clocking and frame synchronization between the TMS DCC and an
external telephony network.
Configure the system clocks in the tms.cfg file (unique to each installation). Each clock can be
derived from any of the spans on the TMS DCC, although only one span is used at any given time.
Avaya Media Processing Server 500 Hardware Installation and Maintenance
148
Comments? infodev@avaya.com
October 2014