Table of Contents
Advertisement
Operation and Administration
alarm condition occurred even if it is not currently active. Therefore, if a system is experiencing
problems with clocking or spans the full report indicates how often this error occurred.
Alarm Categories
System failure can be categorized as either runtime failure or system startup failure. Startup and
initialization errors indicate that either a hardware or configuration problem exists on a platform.
Runtime errors are any faults detected that occur after the TMS and NICs load their images.
System startup problems can be attributed to several components or subcomponents of a platform.
Errors during system startup are typically due to either hardware failure or system configuration
errors. Any alarm generated on startup clearly identifies (when possible) whether the problem is
system configuration or hardware related. For example, it is hard to isolate a boot failure.
Runtime errors and faults indicate a problem at an interface occurred. The interface can be any
hardware component or subcomponent within the TMS, including all external interfaces to the TMS.
Internal interfaces include memory, DSPs, Time Space Switch (TSS), driver errors, and so on.
External interfaces include Ethernet, spans, clocking power supplies, and so on.
TMS Alarm Categories
Initialization and loading errors include the following:
• hardware initialization fault
• software initialization faults
• system boot fail
• configuration errors
• image loading errors
Runtime errors including the following:
• spans not available
• clock source not available
• resources not responding
• temperature above threshold
• power supplies above or below operating threshold (temperature, voltage, and current)
• memory allocation failing
Avaya Media Processing Server 500 Hardware Installation and Maintenance
144
Comments? infodev@avaya.com
October 2014
Advertisement
Table of Contents
