Dynamic Update of DHCPv4 reserved addresses - BlueCat Integrity - 26.1.0

Address Manager Administration Guide

ft:locale
en-US
Product name
BlueCat Integrity
Version
26.1.0

You can enable the Dynamic Update feature for DHCP reserved IPv4 addresses to quickly deploy changes to the Bluecat DNS/DHCP Server (BDDS). This feature is available only at the Network level. For instructions on enabling this feature, refer to Creating a new IPv4 network. For this feature to work, Bluecat Address Manager (BAM) and BDDS must be running the same version.

Dynamic Update is triggered when you:
  • Add, modify, or remove a DHCP reserved address.

  • Add, modify, or remove a DHCP deployment option (except raw option) that has been applied directly to the DHCP reserved address.
    Note: Custom and Vendor options must be assigned and deployed before they can be used as part of Dynamic Update.
Dynamic Update is not triggered when you:
  • Add, modify, or remove DHCP deployment options that are not directly applied to the DHCP reserved address (such as those set at the Configuration level or Block level).
  • Add, modify, or remove raw DHCP deployment options. You must perform a full DHCP deployment to send the information to the BDDS.

  • Assign DHCP deployment options by applying an IPv4 network template.

Note:
  • There is a 30 second delay between the last action performed that would cause Dynamic Update, and the deployment itself. If a new action is performed, the timer restarts at 30 seconds. Therefore, if a DHCP reserved address is added, and a DHCP deployment option is applied before the 30 seconds pass, the timer will restart at 30 seconds. At the end of the last Dynamic Update action, all queued updates are deployed.

  • If Dynamic Update fails due to fatal errors, the Dynamic Update will be suspended. You must perform DHCP deployment manually to resume the dynamic updates.

  • If the same MAC address is used on different networks, Dynamic Update should not be used at all.