UIM FQDN for robots?
Article ID: 122720
Updated On:
Products
Issue/Introduction
Internal need to convert short name to FQDN automatically for the robots in OC.
Environment
UIM 20.3 and higher
Resolution
UIM cannot "force" discovery_server to always use the FQDN.
This is because using the FQDN when one has been discovered, is the 'default' behavior; therefore, if a robot/machine is NOT showing up with FQDN it generally means we were unable to discover the FQDN in the first place.
Examine discovery_server.cfg - there is a key called reconciliation/display_name_priority
you will see that the third entry is:
other.PrimaryDnsName.
Values include:
"other.RobotName,other.PrimaryDnsName,other.SysName,other.VMName,other.ComputerName,other.label,other.PrimaryIPV4Address,other.PrimaryIPV6Address,mon_config_service.PrimaryDnsName,mon_config_service.RobotName,mon_config_service.SysName,mon_config_service.VMName,mon_config_service.ComputerName,mon_config_service.label,mon_config_service.PrimaryIPV4Address,mon_config_service.PrimaryIPV6Address"
If you moved that to the front, and cold start the discovery_server, as soon as we have a FQDN for a device, that should be the name the device gets but if and only if the FQDN is available.
If not, discovery will look at whether the device has any of the 'other' attributes.
The first one (other.RobotName), ANY of the CM_DEVICE entries for the CM_COMPUTER_SYSTEM, will be used to name the entries.
IF you make this change it would ONLY be applied to NEW devices but there is a callback on discovery that you can use to trigger a reevaluation of all devices. Its called -> "reimport_devices_by_cs_ids”
Recorrelation is part of the official documentation and you can find it here:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/discovery-server-discovery-server/device-correlation-configuration.html
It's presented, at least for re-correlation/correlation troubleshooting but it's a good way/safe way with no downsides for accomplishing this goal as we don't test it for the purpose mentioned, but it is worth testing it out in a given TEST/DEV environment to be safe.
Additional Information
By default the robot name displayed in IM & AC will be the short name and there isn't a way to have it use the FQDN by default. However if an xml file is used for deploying a robot the FQDN for that system can be specified. For info on installing robots via xml see:
Feedback
