To manage DHCP scopes in the Management console, see DHCP Scopes - Management Console (obsolete).
This section shows you how to perform specific actions in Micetro associated with maintaining your DHCP scopes, such as creating and modifying reservations, setting scope options and working with split scopes.
You can view all of the existing DHCP scopes at once, regardless of the server to which they belong. On the IPAM page, select DHCP scopes in the filtering sidebar on the left.
The Utilization column in the scope list shows the utilization of available addresses within the address pool(s) of each scope.
Disabled scopes appear dimmed. The number of unassigned addresses is always shown as zero for disabled scopes.
Adiministrators can view DHCP scopes that reside on individual DHCP Servers that are being managed by Micetro. On the Admin page, select the relevant DHCP server in the filtering sidebar under DHCP Services. On the Action menu, select View scopes. You can also select this option on the Row menu (…).
Unlike DHCPv4 scopes which display all the addresses within a scope, a DHCPv6 scope will only display addresses in use or which have been recently used. At the bottom of the view, you will see how many active IP addresses are being shown. If there is an IP address with the status of free, that IP address has recently been used. To see more information, select View History for that address.
Creating a scope on a Kea server configured for load balancing high availability, Micetro will automatically split the scope evenly between primary and secondary servers. See Kea DHCP High Availability.
This section describes how to create and edit DHCP scopes with the new DHCP Scope Creation Wizard.
Whenever you create a new scope, Micetro automatically checks whether the new scope conflicts with an existing scope or an IPAM range.
The Wizard has additional steps, or skips over some steps, depending on the type of DHCP server the scope is being created on, and whether the AD Sites and Subnets integration has been enabled.
To create a new scope on the MS DHCP server, do the following:
In Create action and select DHCP scope from the dropdown.use the
Edit the options for the DHCP scope.
DHCP server: The DHCP server for the scope.
Enabled: If selected, the DHCP scope will start allocating IP addresses immediately. Clear this option if you want to configure the scope further.
Start/end of address pool: Adjust the first and last IP address in the pool.
Active Directory Site selection. If you have enabled AD Sites and Subnets, the Wizard will ask you which AD site the new DHCP Scope should be associated to.
Leave it empty for no AD site.
Summary. The changes the Wizard will perform are summarized here and applied once the user clicks “Finish”.
Micetro supports DHCPv6 for Microsoft and Kea DHCP
Under IPAM click on Create and select DHCP Scope..
Enter the network information and click Next.
Enter the DHCP Server name and the preference, and put a check next to Enabled if you’d like to enable this scope on this server. Click Next.
The preference value is a new parameter required by Microsoft for DHCPv6 scopes. If the scope is assigned to multiple servers, the lowest preference assignment will be selected by the DHCP client
Enter the title as an identifier for this scope as well as the description and click Next.
Verify the information is correct and click Finish.
When managing exclusions within a DHCPv6 pool it is possible to specify a percentage of a DHCPv6 scope rather than specifying a From address and To address
Select a DHCP scope while under IPAM >> DHCP scopes.
Click Action, and then select Manage DHCP Exclusions.
Click Add Exclusion.
A new pop up will appear. Choose to either create the exclusion range by Manual Entry or Percentage.
If you choose manual entry, enter the From address and To address for the range you’d like to exclude from the DHCP scope.
If you choose percentage, drag the percentage bar to the correct percentage of addresses you’d like to exclude, and enter a From address only.
If the exclusion range doesn’t have the space to accomodate the percentage of IP addresses specified, it will not allow you to add this exclusion range until you pick an appropriate From address or lower the percentage.
For complete details on this function, refer to Access Management.
Refer to Object folders for details on this function.
Applies to MS DHCP Servers only.
Use this function to fix inconsistencies between information in the registry and the DHCP database.
Go to the IPAM page.
Select DHCP Scopes
Select one or multiple DHCP Scopes from Microsoft Servers
Click on the ellipsis (or meatball) menu on the scope(s).
Click on Reconcile DHCP Scopes
If there are inconsistencies, a list will be presented. Click Fix to fix the inconsistincies.
For more information see the Microsoft documentation.
At any time, you can modify the properties for a scope. Simply locate the item, and from the Row menu (…) select Edit network properties. For split scopes, the scope contents can be examined individually on each server.
To delete a lease in a DHCP scope, do the following:
Open the scope containing the lease you want to delete.
Select the lease and on the Row menu (…) select Release DHCP lease or use .
The IP Address details window contains all information pertaining to an IP Address in Micetro, including DNS records, DHCP reservations, and custom properties. To access the IP address details select an IP address in the DHCP scope dialog, and all information is displayed in the Inspector, including information on any DNS and DHCP data associated with the IP address. A reservation can be created by clicking the + button in the Related DHCP data section of the Inspector.
You can change the name and/or description of a scope in Micetro.
Locate and select the DHCP Scope you want to rename.
On the Row menu (…), select Edit network properties.
Enter the Title, and any other value you wish to change.
With this feature, you can see when hosts were last seen on your network. There are two methods you can use for host discovery – using ping or querying routers for host information.
When host discovery is enabled, two columns are added to the range or scope view.
This column identifies when a host was last seen on the network and which method was used to discover the host.
This column shows the MAC address used by the host the last time it was seen on the network. This column is only populated if the host was seen using a router query.
Select one or more scopes.
on the Row menu (…), select Set discovery Schedule.
Select the Enable option.
Frequency: Click the drop-down list and select the frequency (e.g., 1, 2, etc.).
Every: Enter the frequency unit for discovery (e.g. days, weeks, etc.).
Next run: Select the start date and time.
Once the schedule options have been set and saved, two columns - Last Seen and Last Known MAC Address - are added to the range or scope grid. The Last Seen column identifies when a host was last seen on the network.
Host responded to the last PING request. The date and time are shown.
Host has responded in the past, but did not respond to the last PING request. The date and time of last response is shown.
Host has never responded to a PING request. The text Never is shown.
At any time if you wish to disable host discovery, do the following:
Select the object(s) for which you want to disable discovery.
On the Row menu (…) , select Set discovery schedule.
Clear the Enable option.
The DHCP scope window will show every instance of the split scope in a separate tab, making it possible to work with all instances of the split scope in a single window.
The Overview and Statistics tab in the DHCP scope window will show a graphical overview for all of the split scope instances.
Reservations are managed automatically. All changes to reservations (creation, modification, and deletion) are applied to all instances of the split scope.
The servers listed in this dialog box all contain the scope to which the user was applying the change. By pressing the Enable button, all instances of the scope would be enabled.
Split scopes are only supported on MS DHCP and ISC Kea servers.
When creating scopes on Kea servers configured in load balancing mode for high availability, Micetro will split the available pool evenly between primary and secondary servers.
Select a DHCPv6 scope under IPAM >> DHCP Scopes
Click Action, and then Manage Scope Instances
In the drop-down menu select a second server to manage the DHCP scope, and then click Add. Enable the servers on which the split-scope should reside.
You can change the preference of the servers by clicking and dragging on the hamburger icon (three lines to the left of the server) to change the order of the servers. The second server will always have a preference of the First Server Preference + 1 and each additional server will increment by 1.
On the same scope, click the Action menu and then select Manage DHCP Exclusions
Click on Add Exclusion for the first server and select the percentage for which you’d like to exclude from the first server and click Add
Click on Add Exclusion for the second server and select the percentage for which you’d like to exclude from the second server and click Add
DHCPv4 and DHCPv6 scopes inherit DHCP and DDNS Options from the parent DHCP server. DHCPv4 and DHCPv6 reservation inherit DHCP and DDNS options from the DHCP scope. However these options may be changed by editing the options for the specific scope or reservation.
Select the DHCP scope in the networks list.
On the Action menu, select Edit scope options. You can also select this option on the Row menu (…).
A dialog box is displayed. Note that in order to see the options that have inherited values, you need to select the Show inherited options checkbox.
Hovering over an option in the Edit Scope dialog box will display a trash can icon to the right of the option.
Clicking the trash can will remove the option.
Some DHCP options, such as DHCP option 43 (Vendor specific info) require the value to be in HEX format. In this case the UI offers the value to be viewed both as HEX and ASCII by selecting each option in tabs above the field, as seen in the figure below.