Steps to archive all Alerts in VCF Operations for Networks
search cancel

Steps to archive all Alerts in VCF Operations for Networks

book

Article ID: 381434

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

This article provides steps to archive alerts which can occur due to multiple system failures.

 

NOTE:  VCF Operations for Networks was formerly named Aria Operations for Networks (AON), and prior to that was named vRealize Network Insight (vRNI).

Environment

VCF Operations for Networks 6.x

 

 

 

 

 

Cause

After logging into the VCF Operations for Networks GUI, under Dashboard --> My Home you observe a number of Critical and/or Warning alerts greater than zero.  

When you click the "Critical" or "Warning" links to the right of the Alerts Circular icon, in the panel to the right you observe the age of the alert, and if it is longer than a few minutes, you would like to clear the error and see if the error returns.  This will keep the display more useful, since old alerts should probably be archived to avoid unnecessary concerns.  

Resolution

Follow the following steps to resolve the issue:

Step 1:  SSH into the Platform 1 VM with Support user, then enter the following commands:

  • ub (to change to the ubuntu user ID)
  • rdb (to invoke the data base process)
  • customerId   (Entering the command "customerId" will cause a reply of the customer ID for the installation.  Note that the "I" is capitalized and all other characters are lower case.)
  • exit (To exit the data base process)

Step 2: Execute the following commands

  • sudo su consoleuser (To change to the consoleuser ID)
  • close-all-alerts -cid <your customer id from above> (To clear the alerts)

You will be presented with the following message:

Running this command will promptly change the status of all currently open alerts to closed without generating notifications. Please note that this action cannot be undone.
There will be no effect on new alerts which will continue to be raised.
The operation typically requires approximately 10 minutes to complete. In the event of an interruption, you have the option to rerun the command to close any remaining alerts.
Kindly be aware that only one instance of this command can be executed at a time, and there must be a minimum 1-hour gap between consecutive runs.
Are you certain you wish to proceed? [y/n]

If you answer "y", you should see the following messages:

Started closing all open alerts...
Successfully closed all open alerts.

When you return to the GUI, refresh the screen and you should see all of the previous alerts are no longer showing.  

This will close out all alerts currently active in the GUI. If there is an issue that is still occurring, a new alert will become active.