Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

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):

  • No labels

8 Comments

  1. Former Member

    Hi Jakob, 

    can you add a example screenshot to this?

    Thanks in advance.

    Best regards,

    Mike

  2. Former Member

     === Ignore my comment below, I understand now, however the solution did not work so I eneded up altering the LMDB manually ++

    Hi,

    Please could you provide a screenshot for showing how to provide a FQDN only. For example, if the IP address is registered OK in the LMDB but the system cannot report the FQDN, I am struggling to understand what is meant by " 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."

    best regards,

    Andrew

  3. Former Member

    hello Jakob,

     

    need your assistant 

    my SID is PRD

    and ip is 192.168.0.1

     

    logicalhost.L = fqdn=prd.com,ip=192.168.0.1           is right ?


    br,

    Atif

    1. Former Member

      Yes, provided that prd.com is the desired FQDN and you substitute the logical host name for L.

  4. Former Member

    My personal hint for troubleshooting:

    Looks like that SAP outside discovery reads only the first two entries in every /etc/hosts line correctly. Everything else gets discarded.

    A typical /etc/hosts line consists of:

    IP1     hostname1a  hostname1b hostname1c

    IP2     hostname2a  hostname2b  hostname2c

    Only IP1+IP2 and hostname 1a and hostname 2a are read. The rest seems to be discarded.

    So If you need to pass a special hostname (e.g. the FQDN) to the Solution Manager: Be sure that it's on the second position.If several hostnames have to be matched to the same IP: Create new lines for each of them.

    Regards

     

    Ralf

     

     

    1. Hi Ralf

      That is incorrect. The hosts file is evaluated as a whole. However, most issues occur if the host file is not maintained according to the standard defined in the RFC's. 

      Please do not create a new line for the same IP address.

      For more information please see: SAP Note 962955

      Best Regards
      Roland

  5. Hello Ralf,

    Thanks for the hints.

    It helps me as well.

    I used to put the following in /etc/hosts

    IP   Short-Hostname FQDN

     

    I then made it to

    IP FQDN Short-Hostname

    and I am able to see the FQDN in Agent Administration.

     

    The syntax was indeed specified in the /etc/hosts file.

    # IP-Address  Full-Qualified-Hostname  Short-Hostname

    Thank you very much.

    Regards,

    Chiwo

  6. Former Member

    Hello Roland,

    I absolutely agree. It is not desired to assign several logical/physical host names to the same ip adress.

    But I have to deal with a bunch of SAP installations running on servers where logical and virtual hostnames share the same ip. This design is more than a decade old and originating from times, where our data center had only a small ip-range available for SAP systems.

    Regards Ralf.