Analysis and monitoring of a system redundancy group occur automatically when the redundancy group is created and its member objects are inserted into the group. The state of the redundancy group is based on the status of its member objects.
Events for a system redundancy group lists the events that are detected for a system redundancy group and exported to the Global Manager as event notifications.
| Event |
Description |
|---|---|
| AllComponentsDown |
None of the member objects in the redundancy group are responsive or operational. |
| AtRisk |
The number of responsive or operational members in the redundancy group is less than or equal to the AtRiskThreshold value (set to 1 by default) but is not zero.
Note:
If the number of responsive or operational members is zero, an AllComponentsDown event occurs. For example, and assuming AtRiskThreshold = 1, the state of a three-member redundancy group that has one responsive or operational member (and two unresponsive or non-operational members) is AtRisk. |
| ReducedRedundancy |
The number of responsive or operational members in the redundancy group is greater than the AtRiskThreshold value but is less than the total number of members in the redundancy group. For example, and assuming AtRiskThreshold = 1, the state of a three-member redundancy group that has two responsive or operational members (and one unresponsive or non-operational member) is ReducedRedundancy. |
As shown in Events for a system redundancy group, the state of a redundancy group is based on the status of its member objects and the value of the AtRiskThreshold attribute (set to 1 by default). If all members of a redundancy group are responsive or operational, the state of the redundancy group is Normal.
Through impact analysis, Network Protocol Manager for EIGRP also links system redundancy group events to root-cause problems received from IP Availability Manager.
