Outside Discovery: Overriding IP Address or FQDN for Agent Nodes

As a prerequisite please first verify the "Hosts File" format has correctly been define on the host following the Mandatory Standard. See https://wiki.scn.sap.com/wiki/x/i4IjIQ

The feature described in this page exists in Solution Manager versions 7.1 SP 12 and upwards and works with an Agent On the Fly setup only (https://wiki.scn.sap.com/wiki/x/DgRgE). It applies to Diagnostics Agent Nodes (cf. https://service.sap.com/~sapidb/011000358700001120362013E.pdf), where the Outside Discovery cannot determine correct network domain names or IP addresses for the logical hosts these Agent Nodes are associated to. If such problems cannot be cured by applying the measures of the document “Outside Discovery — Missing FQDN Issue” attached to SAP Note 1611483, a workaround is to set these values manually in the Agent Administration application of the Solution Manager, which goes as follows:

Assume we have a physical host P with a Diagnostics Agent that has the Nodes Controller feature enabled, which means that it creates “on-the-fly” Diagnostics Agent Nodes for logical hosts emerging on P, and deletes them if them if these logical hosts vanish. For fixing IP address or FQDN (the host name qualified by the network domain name, like “server1.acme.com” for host name “server1” and domain name “acme.com”) for some logical host of short name L (lower case!) on P, no matter whether L currently exists on P or not, one can do the following:

In the “Applications Configuration” tab of the Agent Administration application, choose the Diagnostics Agent for P and the e2edcc Agent Application. There one creates a new property of name “logicalhost.L”, the value of which is a comma-separated sequence of “equations” of the form “keyword=value”, where keyword is one of “fqdn” or “ip” and the value is some character string without comma or equals sign (leading and trailing whitespace gets truncated), which will then be reported as the FQDN od IP address, respectively, of the logical host L. The value for the keyword “fqdn” has to start with “L.”, otherwise it would not be accepted by the landscape database.

Example 1: The logical host name is “NV3”, therefore L = “nv3”. The FQDN is to be forced to be “nv3.acme.com”. Then one would enter a property of name “logicalhost.nv3” and value “fqdn=nv3.acme.com”. If in addition the IP address is to be forced to be 74.65.222.200, one would give this property the value “fqdn=nv3.acme.com,ip=74.65.222.200”. And if the FQDN is not problematic, and only the IP address is to be fixed, the value would be, of course, “ip=74.65.222.200”.

Example 2: An IPv6 address is forced for the logical host log1 on the physical host wdflbmd6895 (the client of the Agent Administration application you see here is Microsoft Internet Explorer 9 with English as preferred language):