Tms Spans - Avaya Media Processing Server 1000 Hardware Installation And Maintenance

Operation and Administration
because its operation can be unpredictable. When 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. The
only action available to recover resources is to restart the TMS card.
The following modules can be affected:
• DCC
• MDM
• TMS
• PLI
The TMS resources do not respond due to the following conditions:
1. faulty hardware
2. undetected software error
3. hardware or software race condition
4. faulty protocol
5. system configuration
Troubleshooting
The only method of recovering resources is to restart the TMS card. Depending on the number of
faulty resources and system load, a restart of the card can be scheduled at a convenient time.
However, prior to restarting the card, determine the source of the fault.
1. Is this a new patch, package, or protocol? (There is possibly an error with image.)
2. The Error log provides information about a problem
3. If resources are marked out of service 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? (Are all resources on a device affected then possible
hardware fault)

TMS Spans

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, it is
possible to mask span alarms as necessary.
The following modules can be affected:
• PLI
Avaya Media Processing Server 1000 Hardware Installation and Maintenance
178
Comments? infodev@avaya.com
October 2014