Error Aria | Error Code: LCMVRAVACONFIG590003

 Error Code: LCMVRAVACONFIG590003

Cluster initialization failed on VMware Aria Automation.
VMware Aria Automation virtual appliance initialization failed on Login to VMware Aria Automation and check /var/log/deploy.log file for more information about the failure. If it is a VMware Aria Automation high availability and the load balancer has to be reset, set the 'isLBRetry' to 'true' and enter a valid load balancer hostname.

Error Source vCenter Server has unsupported version of host profiles

 Issue -: If you are getting below error during vCenter upgrade pre-check.

Error Source vCenter Server has unsupported version of host profiles

Host profiles with versions lower than 6.7 are not supported by vCenter Server 8.0.0 Upgrade the 1 host profiles listed below to version 6.7 or later before proceeding with the upgrade of vCenter server upgrade the host profile before upgrading all hosts with versions lower than 6.7 for more information see KB52932 list of unsupported host profiles.

Solution -: You need to check Host profile created in vCenter and delete unsupported Host profiles.

Failed to send http data” while installing vRealize Easy Installer

If you are seeing below error while vRealize Aria Suit using vRealize Easy Installer

Error “Failed to send http data” while installing vRealize Easy Installer


A general system error occurred:  PBM error occurred during PreCreateCheckCallback: HTTP error response: Service Unavailable

 PBM error occurred during PreCreateCheckCallback: HTTP error response: Service Unavailable

Solution -:

1. Make sure VMware vSphere Profile-Driven Storage Service is running.

2. Make Sure ESXI host and vCenter FQDN is resolving with name and IP

Steps to Upgrade VxRail vCenter.

Before starting VxRail infra upgrade you need to go with pre-validation test using vCenter and command line using VxRail Manager.


Please take some time to review the Customer Preparation Guide KB: 


VxRail Engineering performed a data analysis, which has shown that 92% of upgrades complete with no issue when the ESXi nodes are proactively rebooted. This will identify VM's with potential vMotion issues, ESXi maintenance mode issues, reboot issues and refreshes all ESXi services.  

Therefore, RPS are recommending customers to perform a rolling reboot on the ESXi nodes, several days before the VxRail Upgrade (Customer Task).

If a customer has any issues during the reboots, they can open an SR with the VxRail Support team to address an issue.
Additionally, your Upgrade Engineer will also reboot all Service VM's (VxRail Manager, vCenter** & PSC**) and reset iDRAC on all nodes prior to starting the upgrade.
**Only if VxRail Managed. 


 1.      Run Skyline Health

Login to Vxrail vCenter -> Cluster -> Monitor

Under the vSAN Run Skyline



2. Check Resyncing Objects

Login to VxRail vCenter -> Cluster -> Monitor

Under the vSAN -> Resyncing Objects

If all object has already resync then it’s fine if not, then run the Resync from Configuration.



3.      Change VxRail cluster heartbeat duration to repair Object, default it is set to 60 Minutes.

Change it to 300Minutes or more to avoid object sync during node isolation.


Login to VxRail vCenter -> Cluster -> Configuration

Under the vSAN -> Service -> Advanced Option

Click Edit and set Object repair timer.




4.      Enable VxRail health Monitoring.



Login to VxRail vCenter using root credentials and below command to check health status.

Command -> vsan.whatif_host_failures 0



Download vxverify_XXX_XX_XXX.phy file



Open vxverify_XXX_XXX_XX file using phython


Once you will run this command, VxRail manager will start collecting health report like below.



 In preparation for your upcoming upgrade event, note the below known items:

Schedule the upgrade for a time outside of your peak I/O load, as performance degradation may occur during the migration of VMs while individual nodes or hosts are being upgraded.

Since VMs are vMotioned as part of the upgrade, ensure that VMs are available to be vMotioned in advance. Examples of issues which may prevent vMotion:

VM with an ISO mounted.

VM with external storage locally mounted

VM pinned to a host (Affinity rules)


Download the latest ISO from dell portal for VxRail upgrade.

Mount the ISO in VxRail cluster

Login to vCenter -> Select Cluster -> Configuration

Under VxRail -> Updates -> Local Updates 

Select Update Bundle and Upload

Once ISO Image upload complete click start.

Once you click start it will go with Precheck -> Scan and then Update.

Now all the tasks will complete auto. first will upgrade vCenter -> ESXI host.

It will prompt to enter Temp IP that will be assign temporarily to vCenter during upgrade. 

ESXI host upgrade failing with error the VIB cannot be satisfied within the ImageProfile | Missing_Dependency_VIBs_error

When upgrading the ESXI host from 6.7 to 7.0 or 8.0 it is failing with error the VIB cannot be satisfied within the ImageProfile

VIB Dell_bootbank_dell-configuration-vib

VIB qlc_bootbank_qedi

VIB DellEMC_bootbank_dellemc-osname-idrac

VIB QLogic_bootbank_net-qlge


You may perform below command to remove failed VIB.

Command -: esxcli software vib remove -n XXXXXXX(VIB name)

esxcli software vib remove -n dell-configuration-vib

esxcli software vib remove --vibname=vmware-perccli-007.0529.0000.0000_007.0529.0000.0000-01

Amazon S3 bucket Mount as Performance and Capacity Tier Storage Repository and Scale-Out Backup Repository.


Amazon S3 bucket Mount as Performance and Capacity Tier Storage Repository and Scale-Out Backup Repository


Login to Veeam Backup Server -> Backup Infrastructure


Click Add Repository


Click Object Storage



Click Amazon S3



Click Amazon S3


Give the Storage Repository Name -> Click Next


Account -: Click Add to enter Access key ID & Secret access key.

Connection Mode -: Direct


Click Next


Data Center -: Select the nearest Datacenter.

Bucket-: Type the Bucket Name that Amazon team have shared.

Folder-: Browse and create folder under Bucket.

Check mark on Make recent backups Immutable and set the date for the same.

Check mark on Use infrequent access storage class (May result in higher cost if you will use in 30day Infrequent)



Click Next

Mount Server: - Specify the mount server.

Change the Instant recovery write cache folder if needed or let it be on default setting.

Check mark on Enable vPower NFS service on the mount Server.



Click Next



Click Apply

Now S3 bucket has been mounted in Backup Repository.









Scale-Out Backup Repository-> We use SOBR to setup performance, Capacity and Archival Tier.


To Scale-Out Backup Repository.

Go to Backup Infrastructure -: Click Scale-Out Backup Repository


Give Scale-Out Backup Repository Name


Click Next


Performance Tier -> Click Add and select Primary Tier that you want to use as Performance Tier.




Click Next

Capacity Tier -: Check mark on Extend Scale-Out backup repository capacity with object storage.

Click Choose and select to second tier that you are going to use as capacity tier.


Note-: Based on your requirement you can set whether you want to copy or move your backup file to object storage or not.

1.       Check mark on Copy backups to object storage as soon as they are created.

2.       Move backups to object storage as they age out of the operation restore window.

3.       Encrypt data uploaded to object storage.



Click Next

Archive Tier -: Check mark on Archive GFS full backups to object storage.

Click add the Object storage that you are going to use as Archive Tier.

As this is POC environment so we are not going to keep backup data for so long time so not need to setup Archive Tier.



Click Apply and Finish.


Now Scale-Out Backup Repository has created.







How to create Dashboard in VMware Aria Operation for log for Login and Logout user session

Login to VMWare Aria Operations for Logs

Click Explore Logs

Select time slot

Click ADD Filter

Display query as text -> Drop down and select event_type -> Contains -> Event ID (I have given both event id for session login and logout)

Click on the search box, now you will see the events generated for login and logout session, like below.

Now click on right side three dots ->Click Add to Dashboard

Now go to Dashboard you will see newly created Dashboard

Create Symptom Definition & Alert if Snapshot is older than XXX Days in VMware Aria Operation

A Symptom Definition allows the administrator to describe a situation that is NOT normal within a given environment. vROPs come pre-configured with many symptom definitions that are set to values which are a good starting point for “most” environments.

Create Symptom Definition & Alert if Snapshot is older than 60 Days VMware Aria/ vRealize Operation

Login to vROPS console

Under Configuration -> Alert -> Symptom Definitions

Click Add

Select Base object, Symptom type 

Now create Alert definition

Under Configure -> Alert -> Add -> Give Alert Definitions Name

Base Object Type-> Drop down vCenter -> Virtual Machine

Click Next

Select Symptoms

In filter Type Symptom Name that you have already created and want to integrate with Alert Definition –:  Drag and drop in Symptoms/Conditions


Recommendation -> Select the recommendation 

Next -> Select Policies

Click Create

Featured Post

HPE MSA 2040 configuration step by step

HPE MSA 2040 configuration Default IP range for HP SAN storage MSA 2040 is You need to connect your laptop and storage with...