2 of 2 people found this helpful
Unfortunately, IP address information for LoadBalancerServices cannot be synchronized into the CMDB. The BMC_IPEndpoint CI has to be related with a BMC_HostedAccessPoint relationship to a subclass of BMC_System. The LoadBalancerService is mapped to a BMC_LogicalSystemComponent, which is not a subclass of BMC_System.
The name attribute contains the configured name of the service. You could choose to populate Name, ShortDescription or Description of the BMC_LogicalSystemComponent CI with the IP address and port instead, but there is unfortunately no good place to put the information separately.
Just ran into this issue as well. Did you ever come up with a workaround strategy George?
Also, why does "the BMC_IPEndPoint CI HAS to be related with a BMC_HostedAccessPoint relationship to a subclass of BMC_System" ?
I'm pretty sure I can go create an IP address CI called "184.108.40.206" and not relate it to anything. I concur THAT would be a bad CI, but it seems like BMC Discovery has enough information to make a pretty good IPEndPoint CI, even if it's not related to a System ? Seems better than leaving out hundreds of IP addresses, which is a big use case of the CMDB?
What would be my options for getting these IP addresses in?
This goes into a deeper conversation my area is having around the Load Balancer / VIP / DNS entries. They have been the source of MIMs and PBIs , and CMDB is not very helpful because of the lack of representation. I'm strongly considering just creating a new System subclass, even though it's not entirely true, so I can relate these to IP Addresses and Applications to show impacts / dependencies.
I can understand why BMC wouldn't suggest this to customers or have it out of the box. So what would the Discovery/CMDB experts unofficial suggestion be on this, fully understanding there is no perfect answer?