Importing Windows DHCP failover relationships - BlueCat Address Manager - 8.3.1

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
8.3.1

Customers with DDW servers in Read-Only mode can leverage the migration functionality of Address Manager to import all pre-existing DHCP failover relationships from managed Windows Servers into Address Manager.

Note: This section applies only to Windows Servers in Read-Only mode.

To import Windows DHCP failover relationships:

  1. Select the My IPAM tab. From the configuration drop-down menu, select a configuration.
  2. Select the Servers tab. Tabs remember the page you last worked on, so select the Servers tab again to ensure you are working with the Configuration information page.
  3. Under Servers, click one of the managed R/O Windows servers configured with a Windows DHCP Failover Relationship. The server’s Details tab opens.
  4. Click the server name menu button, then select Import. The Import Configuration Details page opens.
  5. Under General, select the Import DHCP configuration check box.
  6. Click Import. The server’s Details tab opens.
  7. To verify the import completed successfully, click the server name menu button, then select View DHCP Import Log. If necessary, refresh the page to view the contents of the log file.
    Note: Importing DHCP failover relationships
    • If Address Manager encounters a server or interface that is not known to Address Manager, Address Manager will skip that DHCP Failover relationship and all associated roles during the import. The skipped elements will be logged in the import log file.
    • If Address Manager identifies a DHCP Failover Relationship between a Windows Server in Read-Only mode and a Windows Server in Read-Write mode, it will skip importation of that DHCP Failover Relationship, its associated roles, networks, and any associated network level options. The skipped elements will be logged in the import log file.
    • If Address Manager encounters a conflict during import, such that:
      • the particular scope is configured as a split scope in Address Manager
      • the import data reveals that a DHCP failover is configured for the same scope

    Upon detection of such a conflict, Address Manager will skip the import for the subnet and log a notification that this import was skipped. The previous configuration will be retained in Address Manager until you manually delete the subnet for which the conflict was detected then re-import the configuration.

    Note: Do not switch single R/O Windows Servers with imported DHCP failover relationships to R/W mode

    If your managed Read-Only Windows Servers are configured with DHCP failover relationships, DO NOT switch single servers to Read-Write mode. This can cause data inconsistencies between the Microsoft Management Console (MMC) and Address Manager and result in misconfiguration.

    • Example scenario 1—If you delete the DHCP Failover Relationship from the MMC after switching one of the Windows Servers to R-W mode, this relationship will continue to exist in Address Manager until you explicitly delete or overwrite the relationship.
    • Example scenario 2—If you edit a DHCP Failover Relationship (R1) configured between Server 1 (S1) and Server 2 (S2) to be configured between Server 1 and Server 3 (S3), but Server 3 is either undefined, not connected, or in R/W mode, Address Manager will delete relationship R1 (S1, S2) and its associated roles when a subsequent import from S1 is initiated and it will not create relationship R1 with S1 and S3.

    Errors and skipped elements for both of these scenarios will be logged in the import log file.