Table of Contents
Advertisement
Troubleshooting System Initialization
Alarm Categories
System failure can be categorized as either runtime failure or system startup failure. Startup or
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 loads its 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, where possible, whether the problem is
related to system configuration or hardware (for example, it is hard to isolate a boot failure).
Runtime errors and faults indicate that a problem at an interface occurred. An interface is any
hardware component or subcomponent within the TMS including all external interfaces to the TMS.
Internal interfaces include memory, DSPs, Time Space Switches (TSS), driver errors, and so on.
External interfaces include Ethernet, spans, clocking, power supplies, and so on.
Monitoring TMS System Alarms
System alarms are designed to aid in fault detection and isolation of TMS hardware and software
components. Any fault detected that affects the call processing ability of a module generates a
system alarm. Alarms are announced to the alarm viewer in MPS Manager.
System alarms supplement the alarms logged by the TMS and NIC. The information contained in
the TMS and NIC alarms is accessible for engineering diagnostics through event tracing.
Depending on the alarm condition, a fault system alarm can be self clearing. Alarm conditions that
include span alarms and clock loss are self-clearing. Examples of alarms that are not self-clearing
are hardware and system boot failures. These require you or a field engineer to take corrective
action.
Alarm Retrieval
As alarm conditions change, the system automatically sends an alarm to the alarm viewer in MPS
Manager. The hardware also stores the states of the alarms and this information can be retrieved
through the common component in a vshell window.
Two commands are provided: the first retrieves only active alarms on the system; the second
retrieves all alarms, active and inactive. This full report maintains a history of how many times an
October 2014
Avaya Media Processing Server 500 Hardware Installation and Maintenance
Comments? infodev@avaya.com
Troubleshooting System Initialization
143
Advertisement
Table of Contents
