Some notifications from particular events can be transmitted to recipients even though these event notifications are not configurable, such as "UPS: Passed Self test." Majority of these events are referred to as clearing events.

A clearing event notification is sent when a certain condition is cleared so to avoid an end user from missing these events, they are left out of the normal event configuration list.

For example, take Critical -UPS: On battery due to an input power problem - event code 0x0109. The clearing event is Informational -UPS: No longer on battery due to an input power problem -event code 0x010A. By default, an end user will be notified when the UPS goes to battery, and if the UPS comes off of battery, they'll be notified. If the UPS: No longer on battery event in the Informational event list but a recipient is only set to receive critical events, an end user will receive the Critical - UPS: On battery due to an input power problem notification but not the clearing event - Informational -UPS: No longer on battery due to an input power problem notification. They may think that the UPS is still on battery and will take any appropriate actions necessary for an extended on battery event.

For Informational: UPS: Self test passed, this message is sent anytime the UPS successfully completes its battery self test, which by default, is every two weeks and at UPS start up. Some users may not want to receive this event until the self test fails and notifies you with UPS: Self Test Failed event. This may be acceptable but please note that if you address and clear the self test issue and the self test passes subsequently, you will not be notified and may still be under the impression that the UPS is in a fault state.

Resolution

With these considerations in mind, please review the attached document details how to enable or disable these clearing notifications, if needed.Note: Newer UPS's that use the MicroLink protocol (such as SMT/SMX/SRT units) do not use the "self test failed" event code, instead they use the "self test passed" event with extra data to generate the failure event - this gives enhanced information about what caused the self test to fail.