After upgrading to vCenter Server 8.x, some alarm definitions are displayed with empty alarm names

Products

• VMware vCenter Server

Issue/Introduction

After upgrading to vCenter Server 8.x, you may see alarm definitions with empty alarm name in the alarm definitions list, as shown in the screenshot below.

Environment

• VMware vCenter Server 8.0.x

Cause

When upgrading to vCenter Server 8.x, alarm definitions that exist by default in the source vCenter Server are migrated.
If any of these default alarms have been removed from the default alarms by vCenter Server 8.x, the alarm name and description fields will appear blank.

 

The alarm names for the alarms that have been confirmed to have the potential to cause this issue are as follows:

Note: Identifiers included in alarm rules, etc., are written in parentheses ().

• Virtual machine encryption integrity check failed  (com.vmware.vc.crypto.IntegrityCheckFailed)
• VDFS daemon health  (vsan.health.test.fileservice.vdfsd)
• Root FS health  (vsan.health.test.fileservice.rootfs)
• Active Directory Service Health  (vsan.health.test.fileservice.adservice)
• vSAN health alarm 'CMK is not in enabled state in AWS KMS service'  (vsan.health.test.encryption.awskmscmk)
• vSAN health alarm 'Data-in-transit encryption configuration check'  (vsan.health.test.ditencryption.awskmscmk)
• vSAN health alarm 'vSAN Build Recommendation Engine Health'  (vsan.health.test.vum)
• vSAN online health alarm 'vSAN Critical Alert vSAN Advanced Configuration Check'  (vsan.health.test.cloudhealth.lilyadvparametercheck)
• vSAN health alarm 'Current cluster situation'  (vsan.health.test.limits.limit0hf)
• vSAN hardware compatibility alarm 'vSAN firmware version recommendation'  (vsan.health.test.hcl.fwrecommendation)
• vSAN health alarm 'Online health connectivity'  (vsan.health.test.cloudhealth.vsancloudhealthconnectionexception)
• vSAN online health alarm 'Controller utility is installed on host'  (vsan.health.test.cloudhealth.vendortoolpresence)

 

 

 

Resolution

The listed alarms will not trigger in vCenter Server 8.x, so please ignore or consider to delete them.