The Appliance that hosts an Engine (a secondary) is identified by two lists of names. The names can be one or more DNS names, one or more IP addresses, or a mix of the two.
External IP/DNS name
The list of names (FQDN) and IP addresses of the Engine as seen by the Collectors, by the Finder, and by clients of the Web API. If you replace the default certificates, these names must be included as SANs in the server certificate of the Portal.
Warning: When providing multiple names, keep in mind that rule-based Collector assignment addresses each Engine by the first specified external DNS name only.
Internal DNS name
The list of names (FQDN) and IP addresses of the Engine as seen by the primary Appliance. This field must be correctly set before federating the Engine.
The two names can in fact be the same if the Engine offers the same interface both internally and externally.
Setting the names of an Engine
To specify the fully qualified domain names (or IP addresses) of an Engine:
Log in to the Web Console of an Appliance hosting the Engine as admin.
Click the Appliance tab at the top of the Web Console.
Select Network parameters from the left-hand side menu.
Under the DNS section:
Type in the external name of the Engine in External IP/DNS name (e.g.
To specify more than one name, separate each name or IP from another with a space character (e.g.
myengine.example.com192.0.2.11). Remember that only the first external name is used by rule-based Collector assignment to communicate with each Engine.
For the Internal IP/DNS name, either:
Tick the option same as external DNS name to use the same name set as the external interface.
Type in an internal name different from the external name.
Type in the hostname of the Engine in Hostname (e.g.
Type in the domain part of the Engine name in Domain (e.g.
Optional: Type in the addresses of up to four name servers in DNS servers.
Click Save changes to store your changes.