User guide

Setting Up Fault Management Alarm Propagation
943
AlliedView NMS Administration Guide
9.8.2.1 Example 1 - Parent Object set to Max for Polling-Based Alarms (default)
• The administrator sets the Tester attribute for interfaces (IF) in the MO Property Form to PING or SNMPPING, so if an
interface fails, a major alarm is reported by the interface.
• For the parent node, the administrator sets the Tester attribute to Max.
The result of this set up is as follows:
• If an interface fails, the alarm is reported at the node level, with the text of the alarm “one or more interfaces have
failed.”
• Since an alarm at the interface level will result in an alarm at the node level, the node level alarm is not cleared until all
interface alarms have been set to CLEAR by the AlliedView NMS.
• If the parent node has a failure of higher severity, the parent node will take precedence.
Note that this concept of propagating alarms up the hierarchy works at both the Node and Network level; the node reports
among the interfaces the highest level of alarm, while at the network level, MAX means the network reports among the
nodes the highest level of alarm. Alarms at the node level would be propagated to the network object with the text “One or
more Nodes have a Major Alarm.”
9.8.2.2 Example 2 - Parent Object set to PING/SNMPPING (not Max) for Polling-Based Alarms
In this scenario, the higher level object is not set to Max, but to PING/SNMPPING. The following occurs:
• The higher level object will only poll the primary IP interface of its child object.
• There is less “sensitivity” of the higher level object to lower level alarms, since other alarms at the lower level are not
reported to the higher object.
9.8.2.3 Example 3 - Parent Object set to Max for Trap-Based Alarms
Note: The function of the MAX value for objects that use traps to produce alarms is the same of those produced by traps. This is
made a separate example to highlight certain differences.
• For a port, the administrator does not use the Tester attribute, since alarms are reported by the unsolicited trap.
• For the parent node, the administrator sets the Tester attribute to Max.
The result of this set up is as follows:
• If a port has a trap, the alarm is reported at the node level.
• When a port has recovered and a Link UP trap is received by the AlliedView NMS, this is still a trap and therefore the
CLEAR status “alarm” would be reported to the parent level.
• When a port has recovered on the device and a Link UP trap is not received by the AlliedView NMS, the node would still
show an alarm.
• If the parent node has a failure, the parent node will take precedence.