The WAS_ACTIVE and SUSPENDED event states

The WAS_ACTIVE event state is used to identify those notifications that are active under two conditions:

• A Global Manager disconnects from the underlying domain that is the event source. In this case, all active notifications from the disconnected domain are marked WAS_ACTIVE.

• A Global Manager is started from a saved repository file. In this case, all active notifications are marked WAS_ACTIVE.

  Notifications marked as WAS_ACTIVE remain in the WAS_ACTIVE state until the Global Manager can verify their status.

  If the Global Manager is not able to reconnect to the underlying domains that generated these notifications in 1800 seconds (30 minutes), the value of the Severity attribute is set to 4 (“Severity” on page 217 provides additional information), changing the color of the notification in a Notification Log to blue. The value of 1800 seconds is referred to as the detachTime.

  When the connection between the Global Manager and the underlying domains is reestablished, the Global Manager does the following:

• Notifications that are still active in the underlying domain have their Event State changed to ACTIVE and their Severity value updated accordingly. The Last Change attribute is assigned the current time and the Last Notify attribute value remains unchanged.

• Notifications that have cleared in the underlying domain remain in the WAS_ACTIVE state until the attachTime has elapsed. The default value of attachTime is 6000 seconds (100 minutes). However, the actual value that is used to calculate when to clear the notifications is determined as follows:

  • When the uptime for the underlying domain is greater than the attachTime, then the value is 240 seconds plus the smoothing interval. The smoothing interval is specified in the corresponding Domain Type. This typically occurs when the server was restarted.

  • When the uptime for the underlying servers is less than the attachTime, the value is attachTime minus uptime plus the smoothing interval plus 20 minutes. For temporary disconnects, this value is typically used to determine the state of WAS_ACTIVE notifications. This typically occurs when the server was restarted and there was a disconnect.

    The SUSPENDED state indicates that the Global Manager is no longer able to retrieve information about an active notification. When an underlying Domain Manager is not able to get to the source of a notification, it suspends the notification. The Domain Manager sends this message to the Global Manager, which in turn suspends the notification. A Domain Manager may not be able to get to the source of a notification because an SNMP agent is not responding or because it received unexpected error values in an SNMP request.

    Notifications suspended by the Global Manager have the value of the Severity attribute set to 4, changing the color of the notification in a Notification Log to blue.