
Status Monitoring
# P0602484 Ver: 2.7 Page 55
b. Select Choose Log in the Alarm Filter window to select user
defined Historical Alarm Log files.
Specific alarm log files must be selected before they can be displayed in the Alarm
Viewer.
3. Start the Alarm Viewer.
a. <L
EFT> click on the Alarm Viewer icon.
Live alarms display as the generated alarms are received by the Alarm Viewer from
alarm daemons.
Default alarm log files display in the order in which they are selected in the Logged
Alarms Filter. See the PeriView Reference Manual for a complete description of the
Alarm Viewer.
Alarms are generated by the alarmd daemon. If alarm filtering has been instituted at
this level or that of alarmf (an intermediate filter daemon), the Alarm Viewer only
receives those alarms that pass the filtering criteria. For detailed information see the
Media Processing Server Series System Reference Manual.
see To Monitor Components on page 59.
The log file for each component can also be accessed from the Media Pro-
cessing Server shell. Both the default log file and its backup are in the
directory $MPSHOME/common/log, where the files for the specific
components are identified in the format
alarm.component_type.component_number.log. The
default log is .log and its backup is .log.bak. The .log file is cre-
ated when the system boots. The .log.bak file is created when the pre-
configured file size is exceeded. Use standard commands or editors to
view and/or edit these files.
Refer to the Alarm Reference Manual for detailed description of the
Alarm conditions, error causes, and remedial actions.
The alarms that the Media Processing Server generates can be customized
by modifying records in the alarm database, located in $MPSHOME/
common/etc. Additional information concerning the alarm database
can also be found in the PeriView Reference Manual.
Comentarios a estos manuales