Owner's Manual

810 Alarms
The Advisory Text panel lets you enter any advisory text needed to accompany the selected alarm.
NOTE:
To export alarms to a file, create an alarm report, then save it in the appropriate format.
Causes and Impacts for Links and Service Alarms
In addition to the typical Reference Tree nodes that appear for all alarms, sub-components appear
with
Reference Tree nodes displaying Causes and Impacts for links, and for services when you have
OpenManage Network Manager’s service applications installed. These nodes catalog alarms related
to links or services or their subcomponents
Figure 33-7. Causes and Impacts for Service Alarms
For Causes, these display subnodes with the equipment source(s) of the alarm. Impacts also shows
the links’ or services’ configured connection to customers.
Archiving Alarms
To ensure your database does not fill up with Alarms, you can archive them with a Database Aging
Policy. See Chapter 25, DB Aging for details. The default database aging policy (DAP) exists for
Events in Event History, but is not scheduled, again by default. Events can come into the system at
fairly high rates, and as a result can consume space in the database at similar rates. Review the
default DAP and default schedule to ensure that it is aggressive enough for your deployed system.
Self Management / EMS Alarms
The Self Management layout displays alarms for the Element Management System (EMS) only.
These are alarms for internal events like a user’s logon. See the Events that contain
ems in the
Event Definitions.
To open this screen and see this set of internal alarms, select the
Self Management layout at the top
of the client window. The display is like what is appears in Alarm Manager on page 804.