F5 Load Balancer pattern - F5 - SNMP Cluster extension creates duplicate records in cmdb_ci_cluster table, as the cluster_id is too long due to duplicated entries in sysCmTrafficGroupStatusEntry variable - Known Error

F5 Load Balancer pattern - F5 - SNMP Cluster extension creates duplicate records in cmdb_ci_cluster table, as the cluster_id is too long due to duplicated entries in sysCmTrafficGroupStatusEntry variable Description F5 Load Balancer pattern - F5 - SNMP Cluster extension creates duplicate records in cmdb_ci_cluster table, as the cluster_id is too long due to duplicated entries in sysCmTrafficGroupStatusEntry variable

Steps to Reproduce

> Run discovery to F5 Load Balancer, make sure F5 - SNMP Cluster extension completes > Review cmdb_ci_cluster created, check cluster_id field, there are duplicated entries, e.g. node01.demo.com_node01.demo.com_node01.demo.com_... > Sometimes the cluster_id field gets too long due to the duplicated names, it exceeds the max size of the cluster_id field, as a result it's trucated. And when pattern runs again, duplicate records are created

Workaround Open Pattern F5 Load Balancer, open extension section: F5 - SNMP Cluster

Create a new step below 1.1 Get traffic group information:

Operation is Set Parameter Value

Name is $tmp

Value is Eval(), then click on "Edit" button, and paste in below:

var tableWithoutDuplicates = ''; tableWithoutDuplicates = DuplicateRemover.removeDuplicates(${sysCmTrafficGroupStatusEntry},["sysCmTrafficGroupStatusDeviceName"]); CTX.setAttribute("sysCmTrafficGroupStatusEntry", tableWithoutDuplicates);

Click on Save button, and save it to library.