Description
In some instances, we have seen behavior of email alerts being sent as a notification, regarding alert conditions that are no longer present:
Ex:
Dear customer,
The following list contains all of the currently unresolved alerts in your Access appliance cluster avvess742(00000006846858875796):
- No message available.
- Current node: nbapp896.engba.veritas.com(VTAS9000896)
- Console node : nbapp896
- Time of event: 2020-05-27 19:17:34 (-07:00)
- UMI Event code: V-493-100-8007
- Component Type: Storage
- Component: '{2d155e0c-c459-cf62-bc10-1e748c97e75e}_test_fs'
- Status: File System test_fs is Offline
- State: ERROR
- Additional information about this error is available at following link:
- Current node: nbapp896.engba.veritas.com(VTAS9000896)
In this instance, file system "test_fs" had already been destroyed, but the administrator was still getting alerts regarding the FS being offline.
If an error is present, this will create an alert in the database. If the ManagementConsole switches from one node to the passive node before alert condition is resolved, the alert condition does not send the "resolution" update to the database on the node which is now running the ManagementConsole. As a result, the stale alerts need to be manually cleared from the database.
This issue is likely to occur if a service faults at the same time of the ManagementConsole service group failing over - during a node fault, for example.
Some environments may have stale alerts that require manual clean up operations. Please contact Cohesity Support and ask for assistance with clearing these stale alerts.
NOTE: Please review the internal notes attached to this TN for the procedure to clear these alerts.