We have observed that interface groups are not getting refreshed as per the group definition filters.
New devices are discovered, but the groups don't reflect them.
Deactivating and activating udm_manager seems to restore the functionality temporarily.
Release : 20.3
Component :
In many environments, the default settings for udm_manager are too conservative and will cause the probe to struggle to populate interface/inventory data.
Using Raw Configure you should set the values for udm_manager to be as follows -- any configuration key which is not present in your current config should be added as seen below.
The following represents our current "best practice" configuration and in a future update these will be the default settings for udm_manager:
<setup>
loglevel = 3
logfile = udm_manager.log
logsize = 5000
host =
schema_connection_timeout_
schema_transact_retries = 5000
<datomic>
port = 4334
memory_index_max = 512m
memory_index_threshold = 64m
object_cache_max = 256m
</datomic>
</setup>
<startup>
<opt>
java_mem_init = -Xms1024m
java_mem_max = -Xmx2048m
java_opts = -server -XX:ErrorFile=./hs_err_pid.log -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
</opt>
</startup>
https://knowledge.broadcom.com/external/article/8163/the-udm_manager-process-is-going-down-da.html