Flows (including flow metrics) under Data retention Interval shows "0 months" in VCF Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

Flows (including flow metrics) under Data retention Interval shows "0 months" in VCF Operations for Networks

 

 

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

The number of months shown to the right of the Flows (including flow metrics) in the GUI is derived by dividing the value of an internal setting called "configurationRetentionDaysMax" by the value 31, using integer division.  

If this value has been changed in an environment to be less than 31, the result of that integer division will be "0". 

Different internal settings may also have been previously set to be values less than 31.  Examples include "flowRetentionDays" and "flowRetentionDaysMin".

In deployments of VCF Operations for Networks that were done via SaaS, these values may have been set to values less than 31.  

Resolution

For deployments of VCF Operations for Networks that were done after SaaS, the values of these settings must be 31.

To execute such internal setting changes, Broadcom support personnel in the VCF Operations for Networks support team must execute some commands using the rdb tool after logging into the platform1 node using the support user and then switching to the Ubuntu user with the ub command.  This is often done in a change window.  

If you wish Broadcom support to do this, please open a case with the VCF Operations for Networks team using the instructions at Creating and managing Broadcom support request (SR) cases 

 

HOWEVER:  Before you do, please note that changing this value can have undesirable performance outcomes due to resources required to process and store flows.

 

At the start of the change window, the first step will be to establish a revert point by taking a powered off VM snapshot of the platform1 node.  

IMPORTANT NOTES REGARDING THE REVERT POINT ESTABLISHMENT:

STANDALONE (NON CLUSTERED) Deployments:

1. Shut down the guest Collector VM(s) using vCenter
   
   
2. Shut down the guest Platform VM using vCenter 
   
   
3. Take a powered off VM snapshot of the Platform VM.
   
   
4. Power on the Platform VM.
   
   
5. Log into the Platform VM using the support user and switch to the Ubuntu user with the ub command. 
   
   
6. Proceed to allow the Broadcom support personnel in the VCF Operations for Networks support team access to the command line so that they can enter the required commands.

 

CLUSTERED DEPLOYMENTS:

1. Follow the steps in Best practices to shutdown Aria Operations for Networks Clustered deployments.  Make sure that the steps are followed exactly, and in the exact order specified, skipping no steps and introducing no other steps. 
   
   
2. Take a powered off VM snapshot of the Platform1 VM.
   
   
3. Power on the Platform1 VM.
   
   
4. Log into the Platform VM using the support user and switch to the Ubuntu user with the ub command.
   
   
5. Proceed to allow the Broadcom support personnel in the VCF Operations for Networks support team access to the command line so that they can enter the required commands.