Host mappings are based on the data that the Monitoring retrieves on a regular interval. Ops Manager regenerates the entries on the Host Mappings page after each retrieval.
Host mappings are displayed in three-column rows:
The preferred hostname and port for the deployment.
One alternative hostname or address and port for the deployment.
The timestamp when the host mapping was updated.
If a host has multiple aliases, each mapping of host to alias is listed in its own row.
The preferred hostname also appears in the Name column of the Deployment page. This hostname can be a hostname, an FQDN, an IPv4 address, or an IPv6 address. If you want a different preferred hostname than what Ops Manager chose, regenerate the list of mappings in one of the following ways:
Specify constraints on how Ops Manager picks a preferred hostname. For more information, see Preferred Hostnames in Edit Project Settings.
Reset the mapping list. For more information, see Reset Duplicates in Edit Project Settings.
Resetting duplicates and setting constraints on the selection of a preferred hostname cause Ops Manager to lose the monitoring history for affected hosts. Chart data based on this history is also lost.
Depending on what Ops Manager obtains from a monitored host, the alias may be in any one of the following forms:
Fully qualified domain name (FQDN)
External IPv4 or IPv6 address
Internal IPv4 or IPv6 address
To prevent naming conflicts, Ops Manager does not use
similiar local designations for new or remapped hosts unless no
other hostname option is possible.