Tms Span Alarms - Avaya Media Processing Server 500 Hardware Installation And Maintenance

Troubleshooting TMS Resource Errors
You can only recover resources by restarting the TMS card. Depending on the number of faulty
resources and system load, you can schedule a restart of the card at a convenient time. However,
prior to restarting the card, determine the source of the fault. Check for the following conditions.
1. Is this a new patch, package, or protocol? (Possible error with image.)
2. The Error log provides information as to the nature of a problem.
3. If resources are marked out of service, you can use vshell commands to determine the
number of resources affected.
4. Does the problem exist on several TMS running the same protocol and applications? (This
can suggest a software bug or a hardware fault.)
5. How many resources are affected? (If all resources on a device are affected, then a
hardware fault is possible.)

TMS Span Alarms

The spans on a TMS provide the connection from the TMS to an external telephone network. The
status of TMS spans directly affects the ability to process calls. For maintenance support, you can
mask span alarms as necessary.
The following modules can cause TMS span alarms:
• PLI
• DCC
• TMS
The TMS SPANS can generate alarms due to the following conditions:
• cabling problem
• network equipment (for example, the far end is out of service)
• hardware problem
• protocols are incompatible
• spans are not enabled or are taken out of service
Troubleshooting TMS Span Alarms
Check the system alarm report. It detects any span that is not in service (green).
October 2014 Avaya Media Processing Server 500 Hardware Installation and Maintenance
Comments? infodev@avaya.com
TMS Span Alarms
147