Reconfigure vRNI 6.2 Cluster Deployment to enable flow based discovery on large number of VMs (> 3K)
search cancel

Reconfigure vRNI 6.2 Cluster Deployment to enable flow based discovery on large number of VMs (> 3K)

book

Article ID: 324428

calendar_today

Updated On:

Products

VMware Aria Operations for Networks

Issue/Introduction

Symptoms:
NA

Environment

VMware vRealize Network Insight 6.2.x

Resolution

Perform the Below steps to validate the current configuration from vRNI UI

1) Go to setting page ->  Overview and Updates -> Platform Capacity -> Check capacity of Devices

Refer to UI as per the below screenshot:

image.png

  1.  If capacity > 50 then do nothing => Existing deployment support Flow-Based Application Discovery for the large number of VMs (>3 K) => No action required.
  2. If capacity <=50 then follow the below mentioned steps to reconfigure the deployment


Follow below steps to do vRNI deployment reconfiguration:

  • SSH login as support user to platform1
    • These steps can be performed only from P1
  • Change user to ubuntu (sudo su ubuntu)
  • Run following command - python3 /home/ubuntu/build-target/deploymentmanager/change_deployment_config.py
    • This will execute an interactive program with the following options
1. Enter deployment def ID to apply
2. List deployment defs for current config
3. List deployment defs for another config
4. exit
    • Choose the option to list available configs (Option 2)
      • This will list currently applied config as well as configs that can be applied (see sample output)
      • The list also has a description of the config to help in understanding the status of service and limits in the config
    • Get the id of config available to be applied (e.g. PX3C3E in sample output)
    • Apply the config and wait for the completion (Option 1)
      • It takes around 5 to 10 minutes
  • Logs of this process are present in file: /home/ubuntu/logs/deployment_change.log

See the Sample output of changing config on a 3XL setup:

support@platform1:~$ sudo su ubuntu
ubuntu@platform1:/home/support$ python3 /home/ubuntu/build-target/deploymentmanager/change_deployment_config.py
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Enter deployment def ID to apply
2. List deployment defs for current config
3. List deployment defs for another config
4. exit
Please choose one option(enter number): 2

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Following deployment defs are available to apply:
ID:  PX3C3E
Description:  Enterprise, App-Discovery and veriflow services running, NodeManager stopped on platform3
numVMs:  12000  activeFlows:  3000000  numDevices:  300

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Current active def:
ID:  PX3C1ED
Description:  Default Role, Enterprise, App-Discovery and Veriflow running in basic mode
numVMs:  18000  activeFlows:  6000000  numDevices:  50

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Enter deployment def ID to apply
2. List deployment defs for current config
3. List deployment defs for another config
4. exit
Please choose one option(enter number): 1

Please enter the ID you want to apply: PX3C3E
Are you sure you want apply deployment def PX3C3E?(y/n): y
active
active
active
active
active
active
inactive
inactive
inactive
active
active
active
active
active
active
inactive
inactive
inactive
active
inactive
active
active
active
inactive
inactive
Created symlink /etc/systemd/system/hadoop-yarn-nodemanager.service → /dev/null.
inactive
active
active
inactive
Created symlink /etc/systemd/system/batch-analytics.service → /dev/null.
Removed /etc/systemd/system/batch-analytics.service.
enabled
inactive
inactive
active
inactive
inactive
enabled
active
inactive
inactive
enabled
active
inactive
inactive
inactive
Created symlink /etc/systemd/system/samzajobs.service → /dev/null.
inactive
inactive
inactive
inactive
inactive
inactive
inactive
inactive
inactive
enabled
enabled
masked
inactive
inactive
inactive
inactive
active
active
enabled
masked
enabled
inactive
inactive
inactive
inactive
active
active
enabled
masked
enabled
deactivating
active
deactivating
active
ubuntu@platform1:/home/support$


Additional Information

More details on FDAB on vRNI 6.2 Documentation below:

https://docs.vmware.com/en/VMware-vRealize-Network-Insight/6.2/com.vmware.vrni.using.doc/GUID-D72D7697-F33F-44A2-8F94-7F803823A1D7.html