The alarms alarm.VmwarePgArchiverHealthAlarm and alarm.FailoverFailedAlarm cannot be found in the "Alarm Definitions" of the vCenter Server upgraded from vCenter Server 6.5.
search cancel

The alarms alarm.VmwarePgArchiverHealthAlarm and alarm.FailoverFailedAlarm cannot be found in the "Alarm Definitions" of the vCenter Server upgraded from vCenter Server 6.5.

book

Article ID: 383148

calendar_today

Updated On:

Products

VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

- The alarms alarm.VmwarePgArchiverHealthAlarm and alarm.FailoverFailedAlarm cannot be found in the "Alarm Definitions" of the vCenter Server.

- The vCenter Server was upgraded from version 6.5.

Environment

vCenter Server 7.0
vCenter Server 8.0

Cause

This issue occurs due to dependencies on the alarm settings in vCenter Server 6.5, which is already EOS, hence the alarms need to be created manually

Resolution

To resolve this, please follow the below steps to run the attached script via powercli.

  1. Download the script attached to this article.

  2. Use PowerCLI to connect to the target vCenter Server and execute the script downloaded in step 1.
    1. Connect to the vCenter Server.

      Command example:
      PS C:\Administrator> connect-viserver -server [FQDN of vCenter Server] -force -password XXXXXX -user "[email protected]"

      Output example:
      Name                           Port  User
      ----                           ----  ----
      [FQDN of vCenter Server]       443   VSPHERE.LOCAL\Administrator

    2. Execute the script.

      Command example:
      PS C:\Users\Administrator> .\createAlarms.ps1

      Output example:
      Type  Value
      ----  -----
      Alarm alarm-517
      Alarm alarm-518

      Note:
      If PowerCLI is not installed on your system, you need to install it first.
      For instructions on installing PowerCLI, refer to the link below:

      PowerCLI Installation Guide 

  3. Disconnect from the vCenter Server.

    Command example:
    PS C:\Administrator> disconnect-viserver -confirm:$false

  4. Log out and log in in to the vSphere Client, then navigate to the vCenter Server object’s [Configure] -> [Alarm Definitions] to verify that the following alarms exist:

    - PostgreSQL Archiver Service Health Alarm
    - Failover Failed Alarm

Attachments

createAlarms.ps1 get_app