DHCP IPv4 Scope BOOTP Full Monitor

Microsoft.Windows.DHCPServer.Library.IPv4Scope.UnitMonitor.BOOTPScopeFull (UnitMonitor)

There are no available IPv4 addresses available for BOOTP clients

Knowledge Base article:

Resolutions

If the DHCP server does not have IP addresses available to provide to the Bootstrap Protocol (BOOTP) service for its clients, BOOTP fails. When this occurs, consider the following possible solutions:

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:

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:

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:

Example

In the following example, this command sets the database cleanup interval to 10,080 minutes (every seven days).

netsh dhcp set databasecleanupinterval 10080

Element properties:

TargetMicrosoft.Windows.DHCPServer.Library.IPv4Scope
Parent MonitorSystem.Health.AvailabilityState
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.SingleEventLogManualReset2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
DHCP IPv4 Scope BOOTP Full Alert
{0}
RunAsMicrosoft.Windows.DHCPServer.Library.ActionAccount

Source Code:

<UnitMonitor ID="Microsoft.Windows.DHCPServer.Library.IPv4Scope.UnitMonitor.BOOTPScopeFull" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.DHCPServer.Library.IPv4Scope" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.SingleEventLogManualReset2StateMonitorType" ConfirmDelivery="false" RunAs="Microsoft.Windows.DHCPServer.Library.ActionAccount">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="Microsoft.Windows.DHCPServer.Library.IPv4Scope.UnitMonitor.BOOTPScopeFull_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="EventRaised" MonitorTypeStateID="EventRaised" HealthState="Error"/>
<OperationalState ID="ManualResetEventRaised" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-DHCP-Server</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">DHCPServer</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">1064</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</Configuration>
</UnitMonitor>