You can use the alarm acknowledgement mechanism to distinguish handled alarms from alarms that are not handled. In addition, you can add alarm maintenance experiences for each alarm, facilitating system maintenance and sharing experiences.
You can use the alarm acknowledgement mechanism to distinguish handled alarms from alarms that are not handled.
In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
The Information dialog box is displayed.
Status of selected alarms changes to Acknowledged.
After receiving the alarm acknowledgement command, eReplication records the operator, refreshes alarm information, and updates the alarm in the database.
Cancel the acknowledgement of acknowledged alarms.
In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
The Information dialog box is displayed.
Status of selected alarms changes to Unacknowledged.
In some special situations, for example, the communication between the NMS and an NE is interrupted, cleared alarms may be lost. In such a condition, these alarms cannot be cleared automatically if the NE does not support the alarm verification function. To solve this problem, eReplication supports the ability to manually clear alarms. In other words, manually change the status of the uncleared alarms to cleared. Some alarms cannot be manually cleared.
In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
The Information dialog box is displayed.
All the selected alarms are removed from the current alarm list to the historical alarm list. The NMS records the operator and time, refreshes alarm information, and updates the alarm database.
You can export some alarms to a file for administrators to locate and analyze problems. In the following example, alarms are exported in Internet Explorer.
If a default security policy is configured for Internet Explorer, a message indicating "To help protect you security, Internet Explorer blocked this site from downloading file to your computer" is displayed when you export alarms. You need to right-click the message and choose Download File from the shortcut menu that is displayed. After the eReplication page is refreshed, export alarms again.
The Save As dialog box is displayed.
The selected alarms are exported to the specified local path.
You can export all the current alarms to a file for administrators to locate and analyze problems. In the following example, alarms are exported in Google Chrome.
A maximum of 20,000 alarms can be exported at a time. You need to export alarms in batches if the total number of alarms exceeds 20,000.
All the current alarms are exported to the specified local path.
You can select a refresh policy from the drop-down list. The policy can be Refresh every 15 seconds, Refresh every 30 seconds, Refresh every 60 seconds, or Stop refreshing.
Refresh every 15 seconds is selected by default. This means that the NMS performs a round robin every 15 seconds. Once a new alarm occurs, the NMS will refresh it to the current alarm list. Or you can click
in the upper right corner of the Current Alarms page to refresh the current alarm list.
Set the criteria to search for desired alarms. You can search for alarms by alarm severity, type, acknowledgement status, source, and occurrence time.
You can delete the maintenance experiences.
Maintenance experience is a common experience. All users can modify and delete maintenance experience.
According to the alarm notification type, you can determine whether the alarm is a new alarm, manually cleared alarm, or automatically cleared alarm.