LDAP-UX Client Services B.04.00.03 Release Notes

LDAP-UX Client Services Release Notes
Known Problems and Workarounds
Chapter 1 19
A single entry representing a host/computer in an LDAP directory
can contain multiple IP addresses for each hostname record. The
/etc/hosts file, however, requires a separate entry for each IP address.
If the system has been configured with multiple IP addresses for the
same hostname, then the migration script migrate_host.pl will
create multiple entries in its resulting LDIF file with the same
distinguished name for hostname for each of the IP address. Since
distinguished name need to be unique in an LDAP directory, users
need to first manually merge the IP addresses with one designated
host record and delete the duplicate records in their LDIF file. A
resulting entry might look as follows:
dn: cn=machineA, ou=devices, ou=hp.com
objectClass: top
objectClass: ipHost
objectClass: device
ipHostNumber: 15.13.130.72
ipHostNumber: 15.13.104.4
ipHostNumber: 15.13.95.92
cn: machineA
cn: hpma01.cup.hp.com
Also, because LDAP server hosts are sometimes stored using the
host name in LDAP referrals, all the LDAP server host information
for your network must be stored in the /etc/hosts file if you use
referrals, and wish to use LDAP-UX for resolving host names.
• Services
When migrating Services data into the LDAP directory, users should
keep in mind that only multiple protocols can be associated with one
service name, but not multiple service ports. For example: the
following two lines of data can be stored into server.
chargen 19/tcp ttytst source
chargen 19/udp ttytst source
however, only one of the following entries can be stored in to an
LDAP server:
netdist 2101/tcp
-or-
netdist 2102/tcp