The legacy Association Requestor requires that the IP address of the Association Acceptor not change dynamically because it lacks the ability to utilize DNS to obtain the current IP address of the Association Acceptor. The legacy Association Requestor also requires that the AE-title of the Association Acceptor be provided manually.
The DHCP server should be configurable with a database of hostname, IP, and MAC address relationships. The DHCP server can be configured to provide the same IP address every time that a particular machine requests an IP address. This is a common requirement for Association Acceptors that obtain IP addresses from DHCP. The Association Acceptor may be identified by either the hardware MAC address or the hostname requested by the Association Acceptor.
The IP address can be permanently assigned as a static IP address so that legacy Association Requestor can be configured to use that IP address while managed Association Requestor can utilize the DNS services to obtain its IP address.
No specific actions are needed, although see below for the potential that the DHCP server does not perform DDNS updates.
Although the managed Association Acceptor may obtain information from the LDAP server, the legacy Association Requestor will not. This means that the legacy mechanisms for establishing AE-Titles and related information on the Association Requestor will need to be coordinated manually. Most LDAP products have suitable GUI mechanisms for examining and updating the LDAP database. These are not specified by this standard.
An LDAP entry for the Association Requestor should be manually created, although this may be a very abbreviated entry. It is needed so that the AE-Title mechanisms can maintain unique AE-titles. There must be entries created for each of the AEs on the legacy Association Requestor.
The legacy Association Requestor will need to be configured based on manual examination of the LDAP information for the server and using the legacy procedures for that Association Requestor.