This monitor alerts when the total number of the free addresses of all scopes for the specified superscope fall below the defined threshold
Microsoft Windows DHCP Server Library Scope Monitoring, returns a property bag containing the number of free in the specified scope / superscope.
These are the parameters that we could override, if need it:
IntervalSeconds: Amount of Seconds for each execution
SyncTime: Time expressed with this format: "hh:mm" since you will like to start the execution.
TimeoutSeconds: Amount of seconds to wait until cancel execution for "timeout reasons."
DebugFlag: Use "true" or "false" to record different events in the Operation Manager Event Logs for tracking purposes.
If the DHCP server does not have IP addresses available to provide to its clients, they could fail to obtain new assigned IPs. When this occurs, consider the following possible solutions:
Use scope extension to expand the address range for the current scope.
Reduce the lease duration and decrease the cleanup interval. This can help tospeed the reclaiming of expired scope IP addresses.
Extend the DHCP scope
If you already have a DHCP scope and the Start Address and End Address do not currently include all addresses for yourspecific subnet, you can increase the number of addresses in the scope by extending the Start Address or End Address in the scope properties.
To increase the number of addresses available to clients:
At the DHCP server, click Start, point to Administrative Tools, and then click DHCP.
In the console tree, right-click the scope you want to extend, and then click Properties.
ChangeStart IP Address and End IP Address to extend the scope.
Reduce the lease duration
To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.
Toreduce the lease duration:
At the DHCP server, click Start, point to Administrative Tools, and then click DHCP.
In the DCHP console tree, right-click the scope you want to configure, and then click Properties.
On the General tab, under Lease duration for DHCP clients, type the new lease duration.
Decreasethe cleanup interval
To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.
To use a Netsh command to set the cleanup interval time:
At the DHCP server, click Start, click Run, type cmd, and then press ENTER.
Type netsh dhcp set databasecleanupinterval "NewInterval" (where "NewInterval" is the amount of time in minutes between DHCP database cleanups).
Example
In the following example, this command sets the database cleanup interval to 10,080 minutes (every seven days).
netsh dhcp set databasecleanupinterval 10080
Target | Microsoft.Windows.DHCPServer.Library.Superscope | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | StateCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Windows.DHCPServer.Library.MonitorType.ScopeSpaceAvailable | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Microsoft.Windows.DHCPServer.Library.ActionAccount |
<UnitMonitor ID="Microsoft.Windows.DHCPServer.Library.Superscope.UnitMonitor.ScopeSpaceAvailable" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.DHCPServer.Library.Superscope" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.DHCPServer.Library.MonitorType.ScopeSpaceAvailable" ConfirmDelivery="false" RunAs="Microsoft.Windows.DHCPServer.Library.ActionAccount">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="Microsoft.Windows.DHCPServer.Library.Superscope.UnitMonitor.ScopeSpaceAvailable_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="Microsoft.Windows.DHCPServer.Library.Superscope"]/Name$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="ScopeAddressesAvailable" MonitorTypeStateID="ScopeAddressesAvailable" HealthState="Success"/>
<OperationalState ID="ScopeAddressesLow" MonitorTypeStateID="ScopeAddressesLow" HealthState="Warning"/>
<OperationalState ID="ScopeAddressesExhausted" MonitorTypeStateID="ScopeAddressesExhausted" HealthState="Error"/>
</OperationalStates>
<Configuration>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
<TimeoutSeconds>300</TimeoutSeconds>
<TargetComputer>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</TargetComputer>
<Name>$Target/Property[Type="Microsoft.Windows.DHCPServer.Library.Superscope"]/Name$</Name>
<Threshold>10</Threshold>
</Configuration>
</UnitMonitor>