Alert Assigned deployment definition is not matching the expected one see for VCF Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

• Alert Assigned deployment definition is not matching the expected one see for VCF Operations for Networks 9.0.0 under VCF Operations 9.0.0 GUI
  
  
• This alert is seen under VCF Operations Inventory Objects. Navigating to Inventory on the GUI and selecting the Object Operations for Networks and then click on Alerts.
  
  Refer to screenshot below:
  
   
• When navigate to On VCF Aria Operations for Networks Infrastructure and update page on the GUI a toast message for Capacity Mismatch  and  Reconfigure button is seen.
• Alerts generated shows DEPLOYMENT_DEF_MISMATCH_EVENT
• VCF Operations for Networks platform appliances have Small brick size.

Environment

• VCF Operations for Networks 9.0.0
• VCF Operations 9.0.0

Cause

This is alert is a configuration alerts for the VCF Operations for Networks appliances where these appliances have a capacity mismatch due to incorrect CPU/Memory capacities configured.

These CPU/Memory or disk capacities are not matching with Brick size hence these alerts seen are expected on VCF Operations and VCF Operations for Networks GUI. 

 In a clustered deployment then the brick Size can be either Large or XLarge. 

Resolution

To fix this issue ensure the VCF Operations for Networks appliance in the deployment are using correct resources as per Brick size. See System Recommendations and Requirements.

1. For Simple deployment Of VCF Operations for Networks (Non Clustered) then perform a Shut down the Collector and platform noes from vCenter Power Options>Shutdown Guest OS.
2. For Clustered deployment of VCF Operations for Networks use steps mentioned in KB Best practices to shutdown VCF Operations for Networks Clustered deployments.
3. Validate the VCF Operations for Networks appliances have shutdown from vCenter.
4. Add CPU/Memory to the Nodes as per Brick Size. See Increase the Brick Size of Your Setup.
5. Power on the Collector Node(s).
6. Power on the Platform Node.
7. If you have a Clustered deployment then see procedure mentioned in KB Best practices to shutdown VCF Operations for Networks Clustered deployments
8. Once all the VCF Operations for Networks appliances are powered on then login to VCF Operations for Networks GUI.
9. Navigate to VCF Operations for Networks GUI under  under infrastructure and update page, validate that each shows shows correct cpu, memory size and Brick Size 
10. From VCF Operations for Networks GUI Click on Reconfigure button to trigger reconfiguration.
11. Reconfiguration takes minimum 30 to maximum 45 minutes to complete.
12. Post Reconfiguration is completed Login to VCF Operations for Networks GUI to ensure that Capacity Mismatch toast message is not seen and all should be green as per below screenshot.
    
    
    
    
13. Alerts should be cleared from the platform nodes as well.
14. Navigate to VCF Operations 9.0 GUI and validate the alerts are cleared up.