sm71sp5outsidediscmissingfqdn

SAP Solution Manager 7.1 SP05

Outside Discovery

Missing FQDN Issue

Version 1.0 - November 2012

OUTSIDE DISCOVERY

MISSING FQDN ISSUE

Typographic Conventions Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Type Style Represents

Example

Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation.

Example

text Emphasized words or

phrases in body text, graphic

titles, and table titles.

EXAMPLE

TEXT Technical names of system

objects. These include report

names, program names,

transaction codes, table

names, and key concepts of

a programming language

when they are surrounded

by body text, for example,

SELECT and INCLUDE.

Example

text Output on the screen. This

includes file and directory

names and their paths,

messages, names of

variables and parameters,

source text, and names of

installation, upgrade and

database tools.

Example

text Exact user entry. These are

words or characters that you

enter in the system exactly

as they appear in the

documentation.

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE

TEXT Keys on the keyboard, for

example, F2 or ENTER.

OUTSIDE DISCOVERY

MISSING FQDN ISSUE

Contents

1 Purpose ................................................................................................................................................ 4

2 Pre-requisites ...................................................................................................................................... 4

3 Host Types Definition .......................................................................................................................... 5

3.1 Physical Host ................................................................................................................................ 5

3.1.1 Physical Host in Landscape Browser ....................................................................................... 6

3.1.2 Physical Host in System Landscape Host ................................................................................ 7

3.2 Virtual Host .................................................................................................................................... 8

3.2.1 Virtual Host in Landscape Browser .......................................................................................... 8

3.3 Logical Host .................................................................................................................................. 9

3.3.1 Logical host in Landscape Browser .......................................................................................... 9

3.3.2 Logical host discovery .............................................................................................................. 9

4 Troubleshooting Missing FQDN Issue ............................................................................................. 10

4.1 Step 1 Checking Diagnostics Agent Administration application .......................................... 10

4.2 Step 2 Checking SAP Host Agent FQDN data ........................................................................ 11

4.3 Step 3 Checking SAP Profile ................................................................................................... 12

Outside Discovery 4

Missing FQDN Issue SolMan 7.1 SP05

SAP AG 2008

1 Purpose

This document is intended to explain how the Outside Discovery works when retrieving the Full Qualified Domain

Name (FQDN) for any kind of hosts (Physical, Virtual and Logical). It should help identifying the source of the

problem in order to get correctly the FQDN.

In most of the case the missing FQDN issue is directly related to a network configuration issue. Although Outside

Discovery may get the FQDN from different sources, the network should be properly configured in order to avoid some

manual settings/workaround (as described in SAP Note 1626853 Solution Manager 7.1 Outside Discovery FQDN

Customization) and to get the full benefit of running Outside Discovery process.

2 Pre-requisites

In order to get all information related to a Host, the Outside Discovery process should complete without any error.

The log process can be checked directly from the Landscape Browser Application Host view Host Status

Icon

For any exception found in this screen, please refer to the following SAP Note:

- SAP Note 1611483 - SolutionManager7.1 - Outside Discovery common error messages

Outside Discovery 5


SAP AG 2008

3 Host Types Definition

In order to understand how the FQDN is retrieved by Outside Discovery, we have to define each type of hosts that are

available in LMDB:

- Physical host

- Virtual host

- Logical host

3.1 Physical Host

A physical host is identified by a unique identifier: short name. This short name is provided by the SAP Host Agent

process. There is a one to one relation between a Physical host and a SAP Host Agent instance.

Depending on the network configuration, the Physical Host may have one or more FQDN/IP addresses defined.

The SAP Host agent does not return a unique FQDN/IP for a physical host this means any FQDN/IP may

be a valid from Outside Discovery process point of view.

As of following release/patch:

- Solution Manager 7.1 SP07,

- Solution Manager 7.1 SP06,

- Solution Manager 7.1 SP05 Patch 2,

- Solution Manager 7.1 SP04 Patch 05,

We have introduced logic in order to get the most relevant FQDN/IP out of the list provided by SAP Host Agent.

Outside Discovery 6


SAP AG 2008

3.1.1 Physical Host in Landscape Browser

Information retrieved by the Outside Discovery process is available in the Landscape Browser application.

Field Name Description

sld_id Unique Identifier of the Physical Host (one to one relation with SAP Host Agent).

full_name FQDN provided by Outside Discovery (selected from the full_names list provided by SAP Host

Agent).

type Host type (P: Physical, V:Virtual, L: Logical)

ip IP provided by Outside Discovery (selected from the ips list provided by SAP Host Agent).

full_names List of FQDN defined on the physical host (network configuration) provided by SAP Host

Agent

ips List of IP defined on the physical host (network configuration) provided by SAP Host Agent

Outside Discovery 7


SAP AG 2008

3.1.2 Physical Host in System Landscape Host

Information retrieved by the Outside Discovery process is also available in the System Landscape Host application.

Field Name in System Landscape Host Corresponding field name in Landscape Browser

Host name sld_id

Fully Qualified Domain Name full_name

IP Address Ip

Alternative Hostnames full_names/ips

Outside Discovery 8


SAP AG 2008

3.2 Virtual Host

A virtual host has exactly the same properties as a physical host. The only exception is that a virtual host is running

inside a virtualized solution (e.g. VMware ).

Regarding SAP Host Agent, same rule as physical host applies: only one SAP Host Agent can be installed on a

virtual host. There is a one to one relation between virtual host and SAP Host Agent.

From a discovery point of view, we are not able to discover the physical host that is hosting the virtual host.

3.2.1 Virtual Host in Landscape Browser

From a modeling point of view, virtual host can be seen as physical host with following additional properties

Field Name Description

type Host type - V:Virtual

Virtual_sol_name Technical name of the virtualization solution

Virtual_sol_type Type of virtualization

Virtual_sol_vers Version of virtualization

Outside Discovery 9


SAP AG 2008

3.3 Logical Host

Any other aliases/network adapters defined on a physical/virtual host are considered as logical host:

- A physical/virtual host can have one or many logical hosts.

- From a landscape point of view, Outside Discovery process is able to make a connection between a

logical host and a physical/virtual host. At any time, the landscape knows which physical/virtual host

is hosting a logical host.

- In case of HA configuration, if a logical host moves from one physical/virtual host to another

physical/virtual host, the change is reflected in the landscape browser.

- A logical host inherit properties from the hosting physical/virtual host (Operating System, )

3.3.1 Logical host in Landscape Browser

Within the Landscape Browser we may identify which physical/virtual host is hosting the logical host.

3.3.2 Logical host discovery

Outside discovery process is using 2 sources in order to discover Logical host:

- SAP Instances: SAP Host agent is returning a list of SAP Instances running on the physical/virtual host.

This list is used to create Logical host in LMDB with following information: Short host name, FQDN and

IP.

If the FQDN is not reported correctly then the property SAPLOCALHOSTFULL= in the SAP

Profile should be adjusted in order to match your network configuration.

- Diagnostics Agents: there are some cases where we do not have any SAP Instances reported:

Standalone Database

Diagnostics Agent with agent-on-the-fly feature (only the controller is reported as a SAP

Instance)

Non-SAP products

In such cases, the outside discovery is using each diagnostics agent configuration as a source for

discovering a Logical Host this includes information for host name, FQDN and IP.

Outside Discovery 10


SAP AG 2008

4 Troubleshooting Missing FQDN Issue

Most of the missing FQDN issues are related to an incorrect network configuration. This section will help finding the

root cause of the issue.

4.1 Step 1 Checking Diagnostics Agent Administration application

Opening the Diagnostics Agent Administration application should already give an idea on which

physical/virtual/logical hosts have an issue with FQDN.

From the screenshot above, we may identify 2 main issues:

- for diagnostics agent wdfd00291023a and gwyn60221837a, the JAVA Network API is returning the IP

address instead of the Full Qualified Domain Name.

- for diagnostics agent eemdevrobot1 and lu246166, the JAVA Network API is returning the short name

instead of the Full Qualified Domain Name.

The recommended solution is to check if the hosts are correctly defined within hosts file (/etc/hosts file for Unix

and :Windows\System32\drivers\etc\hosts for Windows). Format of the hosts file should be:

#IP Full Qualified Domain Name short name

10.79.0.12 ld8xxx.wdf.sap.corp ld8xxx



SAP AG 2008

4.2 Step 2 Checking SAP Host Agent FQDN data

In order to check FQDN/IP information returned by the SAP Host Agent, the log of outside discovery process should

be set in debug mode:

- Within the Diagnostics Agent Administration Agent Log Viewer select specific agent, log file

e2edcc_host.log should be set in debug level mode:

- Following debug log line are available:

Debug [PhysicalHostPushJob:getComputerSystem] [Name][hostA]

Unique identifier of the physical/virtual host returned by SAP Host Agent.

Debug [PhysicalHostPushJob:getComputerSystem] [Hostnames][localhost;hostA.wdf.sap.corp;hostA;]

Debug [PhysicalHostPushJob:getComputerSystem] [IPAdresses][127.0.0.1;127.0.0.2;10.18.112.167;]

List of FQDN/IP returned by SAP Host Agent if Hostnames only contains short name, this indicates that

SAP Host Agent is not able to get FQDN correctly from the network configuration.

Debug [PhysicalHostPushJob:getComputerSystem] Physical Host Name [hostA]

Debug [PhysicalHostPushJob:getComputerSystem] resolveFQDNandIP [hostA]

Debug [PhysicalHostPushJob:getComputerSystem] resolveFQDNandIP successfully

[FQDN:hostA.wdf.sap.corp][IP:127.0.0.2]

Outside Discovery is using the short host name to select the most relevant FQDN from the list provided

by SAP Host Agent.



SAP AG 2008

4.3 Step 3 Checking SAP Profile

FQDN and IP for Logical hosts are reported using the SAP Instances.

If the Full Qualified Domain Name is not reported correctly then the property SAPLOCALHOSTFULL= in

the SAP Profile should be modified manually in order to match your network configuration.

Example of SAP profile

#.*************************************************************************************

#.*

#.* Default profile DEFAULT

#.*

#.* Version = 000068

#.* Generated by user = C5069322

#.*************************************************************************************

#parameter created

rslg/max_diskspace/central = 12000000

#parameter created

rslg/max_diskspace/local = 3000000

#parameter created

rec/client = OFF

SAPSYSTEMNAME = SD7

SAPGLOBALHOST = hostA

SAPLOCALHOST = hostA

system/type = DS

SAPDBHOST = hostdb7

SAPFQDN = wdf.sap.corp

SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)

sm71sp5outsidediscmissingfqdn

Documents

example text words

physical host

example text keys

example text output

menu names

system landscape host

virtual host

logical host discovery