Whether a separate class for your scenario is the best way, I cannot say.
But to sync data into your new class you have to create a sync pattern. Of course DISCO does not know this oob.
2 of 2 people found this helpful
If you do add a new class, it is confusing to give it a BMC_ prefix, because it is not a class defined by BMC. Give it a prefix that corresponds to your organization.
LoadBalancerMember nodes are used just for the linkage from the LoadBalancerPool to the Hosts (or occasionally other LoadBalancerServices) that are providing the service. Do you not have linked Hosts in your case?
3 of 3 people found this helpful
1) create the new Class in the CMDB, using the Class Manager
2) restart Discovery services after making changes to the CMDB class definitions
3) Write and test your custom syncmapping