print_snapshot_report -l1 -d -err
Entity Limit Exceeded
" is seen. There may be additional information about the current entity count, and the supported limit (which will be 20000 or less). See image for an example:
VMware vRealize Network Insight 6.8.0
This issue is fixed in Aria Operations for Networks version 6.9.0.
Workaround:
Check the value assigned to the key "veriflowEntityCoun
t" in the configuration file /etc/vnera/deployment/deployment.def
If the value is not 20000, we first need a change in brick size or the deployment def to raise the limit to 20000.
Specifically, the highest value on a 1XL is 5000, so a cluster is needed.
On a cluster with 3 VMs or greater, there is at least one deployment configuration that allows 20000 entities. If the limit was originally less than 20000, then bringing it up to 20000 may be sufficient in itself to resolve the issue.
If that doesn't suffice, the limit needs to be raised further by setting an override. That can be done by running the following command in vRNI rdb debugger.
set_policy -key "platform.veriflowEntityCountOverride" -ns policy -val "50000"
The above example sets the limit to 50000.
The limit should not be set to any value higher than 100000. If the current entity count is known from the snapshot report (say 30000), then set the limit to a value higher than the count, not too much higher (say 35000).
If the entity count is higher than 100000, the full network map in cannot be supported in 6.8.
The underlay should be added as data sources in order to get value from the network map.
These changes can take 1 hour or more to take effect fully; wait for some time before checking the UI/RDB again for network map/snapshot errors. These changes can be rolled back by setting the override back to 0.
set_policy -key "platform.veriflowEntityCountOverride" -ns policy -val "0"