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

Any software initialization or load error detected affects the usability of the TMS card. Software
initialization errors can prevent the TMS from loading its run-time image or configure resources as
required by the application.
The following hardware can be involved in software initialization and loading errors:
• TMS base
• TMDM
• DCC
• PLI
The TMS does not initialize or load due to the following conditions:
1. defective hardware
2. files corrupt or unreachable by TMS
3. hardware or software versions incompatible (cardtypes.cfg)
4. network configuration or connectivity
5. bootp file incorrect
6. defective or missing Ethernet hub (NIC or ESC)
Troubleshooting
Use serial console output to isolate a configuration error from defective hardware. The tip console
determines if the problem is a hardware or software loading issue.
If the TMS fails to tftp load its image then:
1. Verify bootp entry is correct for TMS
2. Check that the TMS image is available
3. Check the network connections
4. Verify 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 functions include spans, DSP resources for tone
detection and generation recording, playing items, and so on. Each configured resource must
respond in a predetermined manner to commands from the embedded TMS software. When a
resource fails to respond to a command that 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
October 2014 Avaya Media Processing Server 1000 Hardware Installation and Maintenance
Comments? infodev@avaya.com
TMS Runtime Alarms
177