IZ95725: METHODS TO DETERMINE FQDN

APAR status

• Closed as documentation error.

Error description

• After FP4
  You can configure a preferred method of determining the fully
  qualified domain name (FQDN) for each discovered system.
  For a Level 1 discovery, the FQDN is the result of a reverse
  lookup of the IP address. This lookup uses the resolver library
  provided by the operating system and it uses any configuration
  provided there.
  For example, if, at the operating system level, the host file is
  preferred over DNS, information in the hosts file is considered
  first.
  
  For a Level 2 discovery, TADDM performs a reverse lookup of all
  discovered IP addresses using the resolver library provided by
  the operating system. Again, the operating system configuration
  dictates from where the reverse lookup gets information. If DNS
  is not configured, or the DNS returns unwanted FQDNs, you can
  use the hosts file to override it.
  After the discovered IP addresses have been looked up, an
  attempt is made to match an FQDN to the computer system.
  There are a number of different ways to get an FQDN and each
  method is attempted, in a predefined order, until a valid FQDN
  is found.
  You can modify the order so that your preferred method has a
  higher priority.
  The following methods are available:
  
  Method 1
  TADDM selects the FQDN of an IP interface where the host portion
  of the FQDN matches the host name of the discovered system. If
  there are multiple matches, the selected FQDN depends on the
  property com.collation.platform.os.FqdnPriorities.
  Method 2
  The property com.collation.platform.os.command.fqdn specifies an
  external command on the TADDM server that is used to do the
  reverse lookup.
  Method 3
  The property com.collation.platform.os.command.hostOfHostname
  specifies an external command on the target system that is used
  to provide the FQDN.
  Method 4
  The FQDN of the primary interface is used.
  Method 5
  The IP address of the primary interface is used.
  Method 6
  The name of the computer system is used.
  
  You can define the order in which these methods are attempted by
  setting the com.collation.platform.os.fqdnSearchOrder property.
  The value of this property is a comma-separated list of the
  numbers of the methods. The default value is 1,2,3,4,5.
  In this case, TADDM first tries to use method 1. If it does not
  return a valid FQDN, it tries method 2, and so on until it gets
  a valid FQDN and stops.
  
  This solution is also applicable for computer systems that are
  discovered through the use of SNMP sensors. You can define which
  solutions have a higher priority and therefore could be used to
  find an FQDN more quickly.
  
  In all cases, properly configured DNS is the preferred way of
  setting host names. If DNS cannot be used, use the hosts file.
  The use of DNS or the hosts file are the standard ways of
  providing name resolution for IP addresses. TADDM provides ways
  to override these but because any other methods are unique to
  TADDM, they might lead to names that are inconsistent with names
  in other management systems.
  

Local fix

• Technote has been created
  Technote link:
  http://www-01.ibm.com/support/docview.wss?uid=swg21469072
  

Problem summary

• After FP4 You can configure a preferred method of determining t
  qualified domain name (FQDN) for each discovered system. For a
  Level 1 discovery,
  the FQDN is the result of a reverse lookup of the IP address.
  This lookup uses
  the resolver library provided by the operating system and it
  uses any
  configuration provided there. For example, if, at the operating
  system level, the
  host file ispreferred over DNS, information in the hosts file is
  considered
  first. For a Level 2 discovery, TADDM performs a reverse lookup
  of all discovered
  IP addresses using the resolver library provided by the
  operating system. Again,
  the operating system configuration dictates from where the
  reverse lookup gets
  information. If DNS is not configured, or the DNS returns
  unwanted FQDNs, you can
  use the hosts file to override it. After the discovered IP
  addresses have been
  looked up, an attempt is made to match an FQDN to the computer
  system. There are
  a number of different ways to get an FQDN and each method is
  attempted, in a
  predefined order, until a valid FQDN is found. You can modify
  the order so that
  your preferred method has a higher priority. The following
  methods are available:
  Method 1 TADDM selects the FQDN of an IP interface where the
  host portionof the
  FQDN matches the host name of the discovered system. If there
  are multiple
  matches, the selected FQDN depends on the property
  com.collation.platform.os.FqdnPriorities. Method 2 The property
  com.collation.platform.os.command.fqdn specifies anexternal
  command on the TADDM
  server that is used to do the reverse lookup. Method 3 The
  property
  com.collation.platform.os.command.hostOfHostname specifies an
  external command on
  the target system that is used to provide the FQDN. Method 4 The
  FQDN of the
  primary interface is used. Method 5 The IP address of the
  primary interface is
  used. Method 6 The name of the computer system is used. You can
  define the order
  in which these methods are attempted bysetting the
  com.collation.platform.os.fqdnSearchOrder property. The value of
  this property is
  a comma-separated list of the numbers of the methods. The
  default value is
  1,2,3,4,5. In this case, TADDM first tries to use method 1. If
  it does not return
  a valid FQDN, it tries method 2, and so on until it gets a valid
  FQDN and stops.
  This solution is also applicable for computer systems that are
  discovered through
  the use of SNMP sensors. You can define whichsolutions have a
  higher priority and
  therefore could be used to find an FQDN more quickly. In all
  cases, properly
  configured DNS is the preferred way of setting host names. If
  DNS cannot be used,
  use the hosts file. The use of DNS or the hosts file are the
  standard ways of
  providing name resolution for IP addresses. TADDM provides ways
  to override these
  but because any other methods are unique to TADDM, they might
  lead to names that
  are inconsistent with namesin other management systems.
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  | Fix Pack | 7.2.0.0-TIV-ITADDM-FP0005
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels