09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Communication Manager Maintenance Object Repair Procedures<br />

PROC-SAN (Process Sanity Audits)<br />

MO Name in Log Alarm<br />

Level<br />

Initial Command to Run Full Name of MO<br />

PROC-SAN none none Process Sanity Audits<br />

The Process Sanity Audits MO is responsible for monitoring the sanity of software processes in<br />

the system. If the Process Sanity Audits MO detects that a process has gone insane (does not<br />

respond to a sanity message within an allotted time period), the process will be restarted. If the<br />

Process Sanity Audits MO detects that multiple processes (or a single key process) do not<br />

respond to sanity messages within an allotted time period, a system recovery action will be<br />

initiated.<br />

The Process Sanity Audits MO has no alarms and no tests. Certain errors are logged to the<br />

Error Log for information purposes only.<br />

Error log entries and recommended actions<br />

Table 312: PROC-SAN Error Log Entries<br />

Error<br />

Type<br />

Aux<br />

Data<br />

Associated<br />

Test<br />

Alarm<br />

Level<br />

On/Off<br />

Board<br />

0 0 Any Any Any none<br />

10 (a) 0 none none none none<br />

204 (a) any none none none none<br />

Recommended<br />

Action<br />

Note:<br />

a. Error Type 10, 204: a system recovery action was taken because one or more software<br />

processes failed to respond to a sanity audit in a timely fashion. As a result of the recovery<br />

action, the system may have temporarily suspended service for a period of time<br />

surrounding the error.<br />

1152 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!