192.168.4.71 192.168.4.71 Feb 10,2004 09:06:51 PM Node clear No failu Major IF-kernel-solaris kemel-solaris Feb 10,2004 09:02:15 PM Interface failure Major kemel-solaris kemel-solaris Feb 10,2004 09:02:15 PM Node failure This Major IF-nms-e1 nms-e1 Feb 10,2004 09:02:27 PM Interface failure Major nms-e1 nms-e1 Feb 10,2004 09:02:27 PM Node failure This Major IF-nms-customer nms-customer Feb 10,2004 09:03:01 PM Interface failure Sta Major nms-customer nms-customer Feb 10,2004 09:03:01 PM Node failure This Done. Figure 12.18 Alarms list client. Clear Alert counts by severity Category Clear Topology Clear Categories-Total Totals Clear Done. Figure 12.19 Alerts counter according to severity level. Table 12.3 Alarm details. Property Description Message Stores additional information about the alarm Failure object The entity which has caused the alarm within the source Source Source of the alarm Owner Owner with whom the alarm is associated Category Alarm category Created Date and time when the alarm was first created Modified Date and time when the alarm was last modified Group Group of which the alarm is a member Severity Criticality of the alarm Other alarms in this group Other alarms present in this group 12 Fault Management A AdventNet Alarm details for advrouter Status Update Message Failure object: advrouter Source advrouter Owner Category: Topology Created : Jun 21,2001 01:44:03A Modified Jun 21,2001 01:44:03 Group: Severity: Major Previous severity: Other alarms in this group: Annotations for this alert Pick Up Annotate Refresh Properties View history Merge Close Figure 12.20 Alarm details screen for an object that has experienced failure. enables other users to solve the same problem with less effort, by just reading the "Alarm Annotate". System or user actions on the alarm are also recorded automati- cally. User actions such as annotating and selecting appear under "Alarm Annotate". The status of alarms added, updated or deleted can be viewed in the alarm history. The FMS fault management system automatically h