After an attempted increase in size of the platform node to Extra Large in VCF Operations for Networks, services "running but not healthy"

Products

• VCF Operations for Networks

Issue/Introduction

After scaling up the platform node to Extra Large (commonly, to enable the network mapping feature) in VCF Operations for Networks, one or more services are shown as "running but not healthy"

After logging into the Platform node with the support user, changing to the Ubuntu user with the ub command, and running the command ./check-service-health.sh -p -d you observe output including one or more of the following:

HMaster is running but not healthy

HRegionServer is running but not healthy

NodeManager is running but not healthy

FlinkContainer is running but not healthy

 

 

 

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

Cause

There can be a number of causes for these symptoms. 

However, if the scaling up process described at Increase the Brick Size of Your Setup was not followed precisely, this can be a cause.  

Resolution

If these symptoms were observed directly after an attempt to scale up the setup, and the process described at Increase the Brick Size of Your Setup was not followed precisely, and you have just built the environment initially, you may wish to simply delete the deployment and re-deploy using the desired brick size.  

In all other cases, please open a Support Case using the instructions at Creating and managing Broadcom support cases