Adding or removing scopes from an ISC DHCP failover relationship - User Guide - Micetro - 25.2.0

Micetro Admin Guide

ft:locale
en-US
Product name
Micetro
Version
25.2.0

Failover relationships initially appear as Empty and must be activated by adding a scope to the relationship from the IPAM page. You can either create a new scope or select an existing one. Once you have added a scope, the failover peer statement will automatically be added to any existing pools within the scope. If the failover relationship was previously empty, it will be created on the ISC DHCP server.

ISC DHCP scopes participating in failover relationships are grouped and labeled as such in the Authority column on the IPAM page. The Failover relationship column displays the name of the failover relationship to which the scope belongs.

Note: Micetro supports only one failover relationship per scope. In cases where a scope has multiple pools with different failover peers, Micetro only displays and operates on the failover peer found in the first pool.

Adding scopes to failover relationships

There are three ways to add scopes to a failover relationship, either in the Web Application or through the API.

Note: At least one pool must exist in the scope before you can add it to the failover relationship.

To add scopes to the relationship:

  1. On the IPAM page, locate the scope in the data grid.
  2. Use either the Action or Row ... menu to select Add scope to failover.
  3. In the dropdown, select a failover relationship to add the scope to.

  4. Select Confirm.

-OR-

  1. Create a new scope and select the failover relationship during scope creation:

-OR-

  1. Use the API AdsdDHCPScopesFromDHCPFailoverRelationship, which adds scopes to failover relationships. Specify a reference to the DHCP scope and the failover relationship name.

If the failover relationship was empty before the scope was added to it, the status will change from Empty to Normal.



Removing scopes from failover relationships

There are three ways to remove scopes from a failover relationship, either in the Web Application or through the API.

To remove a scope from a failover relationship:

  1. Locate the specific scope on the IPAM page.
  2. Use either the Action or Row menu to select Remove from failover.

After the scope is removed from the failover relationship:

  • Decide whether to delete or disable the secondary scope.
  • Upon removal, the failover peer statement is cleared from each pool in the scope.
  • If the scope was the only one with the failover peer statement in its pools, the failover peer definition is removed.
  • The failover relationship is marked as Empty, to be used later or removed.

-OR-

  1. Locate the specific scope on the IPAM page.
  2. Use either the Action or Row menu to select Manage scope instances.
  3. In the dialog, use the Row ... menu for the relevant server to select Remove scope instance.

  4. Select Save.

-OR-

  • Use the API command RemoveDHCPScopesFromDHCPFailoverRelationship, which removes scopes from failover relationships. Specify a reference to the DHCP scope, the failover relationship name, and the proper deconfigure action.