21.5 Post-Migration Procedures

  1. In the /etc/dhcpd.conf file, change ldap-base-dn to reflect the context of the migrated DHCP Server and change ldap-dhcp-server-cn to reflect the name of the migrated DHCP Server.

  2. Check the lease file at the /var/lib/dhcp/db/dhcpd.leases folder.

  3. To use DDNS after a subnet-level migration, add the following settings to the DHCP Server Object:

    • ddns-rev-domainname in-addr.arpa

    • ddns-update-style interim

    • client-updates deny

    • update-optimization false

    NOTE:DDNS updates are required only when you migrate to an existing DHCP server.

  4. Start the OES2 SP3 Linux DHCP server by using the rcnovell-dhcpd start command.

  5. Continue with Section 21.5.1, Cluster Migration from NetWare to Linux and Section 21.5.2, Running a Preexisting DHCP Server as necessary.

21.5.1 Cluster Migration from NetWare to Linux

On the node where you ran the migration:

  1. Open the <mountpath>/etc/dhcpd.conf file.

    The <mountpath> parameter indicates the target directory in the shared volume where DHCP-specific directories are created.

    Inside the /etc/dhcpd.conf file, which is located in the shared volume, change the ldap-dhcp-server-cn attribute to the migrated server cn.

  2. Copy the migrated_server.leases file from the /var/lib.dhcp/bd folder to the <mountpath> var/lib/dhcp/db/ folder and rename it to dhcpd.leases.

21.5.2 Running a Preexisting DHCP Server

After migration, the DHCP server and service objects are created in the tree. You can run a preexisting DHCP server along with the migrated NetWare server's configuration.

  1. Log in to the tree by using iManager.

  2. Click to expand DHCP (OES Linux).

  3. Select the service.

  4. Select View/Modify service.

  5. Select the service object that was created after migrating the NetWare server. The name of this service starts with the string dhcpservice.

  6. Associate this service object with the existing DHCP server.