Configuring PSM Alarm Severities
Use this procedure to configure the severities of PSM-generated alarms.
The updated alarm severity appears in subsequent alarms generated by PSM. Severities of existing PSM alarms are not affected by this procedure.
- Edit the
- Find the alarm you want to change and edit the severity.
For example, to set the NE_BACKUP alarm severity to CRITICAL, change the alarm as follows:
<alarm-definition name="NE_BACKUP" service-affecting="false" severity="CRITICAL"/>
- Save and close the file.
- Track changes to the
alarm-meta-psm.xmlfile with Git by committing this update to the Git repository.
[user ~]# cd /usr/local/ems9001/resources/deviceMetadata [user deviceMetadata]# git commit -m "Set NE_BACKUP alarm severity to CRITICAL. By email@example.com." alarm-meta-psm.xml
This update can now be seen in the Git log. For more information on Git, see Using Git to Track override-common.properties.
- Changes made to the
alarm-meta-psm.xmlfile do not take effect until the PSM server is restarted. To restart the server, enter the following command:
The restart command successfully completes when the 'Ems-' processes all change to the running state. Type <ctrl> c to exit the Linux watch command window.