Tms Runtime Alarms; Tms Resource Errors - Avaya Media Processing Server 500 Hardware Installation And Maintenance

Operation and Administration
If the TMS fails to tftp load its image:
1. Verify that the bootp entry is correct for the TMS.
2. Check that the TMS image is available.
3. Check the network connections.
4. Verify that there are no address conflicts (IP or MAC).

TMS Runtime Alarms

TMS Resource Errors

Resources are configured on the TMS card to provide various call processing functions as specified
in the customer requirements. Typically, these include spans, DSP resources for tone detection and
generation recording, playing items, and so on. Each of these configured resources must respond in
a predetermined manner to commands from the embedded TMS software. When a resource fails to
respond to a command the TMS embedded software generates, an alarm indicates a resource is
not responding and it is tagged as faulty. The TMS marks the resource faulty because its operation
can be unpredictable. After a resource is tagged as faulty, it no longer is available for future call
processing services. Therefore, no resource must ever be marked as faulty.
A loss of resources affects the call processing ability of the TMS. The severity of the problem
depends on the number of resources and system load. Typically, a fault affects many resources and
the only action available is to restart the TMS card.
The following modules can cause TMS resource errors:
• DCC
• MDM
• TMS
• PLI
The TMS resources does not respond due to the following conditions:
• Faulty hardware
• Undetected software error
• Hardware software race condition
• Faulty protocol
• System configuration
Avaya Media Processing Server 500 Hardware Installation and Maintenance
146
Comments? infodev@avaya.com
October 2014