Monitoring Scenarios
The Dynamic Host Configuration Protocol Management Pack manages the logical parts of Dynamic Host Configuration Protocol (DHCP) that an operator or administrator is interested in monitoring, configuring, or reporting on. Each of the following components is critical to the DHCP infrastructure.
| Component | Component Description |
|---|---|
DHCP Server |
A DHCP server is a computer running the DHCP Server service that holds information about available IP addresses and related configuration information (as defined by the DHCP administrator) and responds to requests from DHCP clients. |
DHCP NAP Components |
Network Access Protection (NAP) is a health policy creation, enforcement, and remediation technology that is included in Windows Vista and Windows Server 2008. With NAP, system administrators can enforce health requirements, which can include software requirements, security update requirements, required computer configurations, and other settings. DHCP enforcement includes a DHCP NAP enforcement server component and a DHCP NAP enforcement client component. By using DHCP enforcement, DHCP servers can enforce health policy requirements any time a computer attempts to lease or renew an IP address configuration on the network. DHCP enforcement is the easiest enforcement to deploy because all DHCP client computers must lease IP addresses. DHCP NAP requires proper NPS/RADIUS configuration. |
DHCP Scopes |
A DHCP scope is the consecutive range of possible IP addresses that the DHCP server can lease to clients on a subnet. Scopes typically define a single physical subnet on your network to which DHCP services are offered. Scopes are the primary way for the DHCP server to manage the distribution and assignment of IP addresses and any related configuration parameters to DHCP clients on the network. |
DHCP Runtime |
DHCP runtime includes the normal operating functions of the DHCP server. Examples of these functions include lease issuance and rogue detection |
DHCP Database |
DHCP service database is a dynamic database that is updated as DHCP clients are assigned or as they release their TCP/IP configuration parameters. The DHCP server database can be backed up and restored or migrated to another server. |
DHCP Service |
DHCP Server service is a process that runs in the background on a computer running Windows Server and provides IP addresses to clients. |
DHCPv6 Runtime |
Dynamic Host Configuration Protocol version 6 (DHCPv6) runtime includes normal operating functions of the DHCPv6 server. Examples of these functions include lease issuance and rogue detection. |
DHCPv6 Scopes |
A Dynamic Host Configuration Protocol version 6 (DHCPv6) scope is the consecutive range of possible Internet Protocol version 6 (IPv6) addresses that the DHCP server can lease to clients on a subnet. Scopes typically define a single physical subnet on your network to which DHCP Server services are offered. Scopes are the primary way for the DHCP server to manage distribution and assignment of IP addresses and any related configuration parameters to DHCP clients on the network. |
DHCPv6 Service |
The DHCPv6 Server service is a process that runs in the background on a computer running Windows Server and that provides IPv6 addresses to clients. |
DHCP Client |
With a DHCP server installed and configured on your network, DHCP-enabled clients can obtain their IP address and related configuration parameters dynamically each time they start and join your network. DHCP servers provide this configuration in the form of an address-lease offer to requesting clients. |
The following sections describe the aspects (operations or types of functionality that a component is designed to perform) and the health states of each component in the Dynamic Host Configuration Protocol Management Pack, as listed in the previous table. This management pack includes monitoring capabilities for detecting the yellow and red health states in the listed components.
Health states are indicated by color:
- Green: normal operation
- Yellow: degraded operation
- Red: failure
Each health state is related to an Aspect (an aspect represents an operation or the type of functionality that a Managed Entity is designed to perform). Health states are detected by Detection Rules.
Although the Dynamic Host Configuration Protocol Management Pack has the ability to detect transitions to specific health states, not all rules in the management pack have been designed to take advantage of the State feature of MOM. In these cases, transitions to specific health states are exposed only through the generation of Alerts and the relevant health state change is not reflected on the DHCP Role and related State Views.
For more information about aspects, see the Errors and Events page in the Windows Server 2008 Technical Library
(https://go.microsoft.com/fwlink/?LinkId=107564).
DHCP Server
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCP Interface Configuration |
Not applicable |
The DHCP server interface and bindings must be configured correctly. The correct configuration of a static interface is required. |
Dynamic Host Configuration Protocol (DHCP) NAP Components
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCP NAP: NPS Availability |
DHCP cannot reach the NPS server to determine the client NAP access state. The client has limited access to network resources until NPS can verify the health state of the client. |
Not applicable |
DHCP Scopes
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCP Scope Configuration |
DHCP has orphaned database entries due to the deletion of a class or an option definition. Reconciling the DHCP scope will ensure database consistency and prevent future database corruption. DHCP will continue to function, but performance may become degraded over time if the scope is not reconciled. |
Not applicable |
DHCP Client Option Configuration |
DHCP received an unknown option from a client. The option will not be set for the client until the DHCP server is configured to recognize the option, but the client might still be able to obtain an address. |
Not applicable |
DHCP Lease Availability |
DHCP has determined that a scope is nearing capacity. If the scope becomes full, the DHCP server cannot lease additional IP addresses. Client computers that cannot obtain new leases from the DHCP server will not have network connectivity. |
DHCP has determined that a scope is at capacity. The DHCP server cannot lease additional addresses until the scope is expanded or clients give up their leases. Client computers may not be able to obtain new leases from the DHCP server and may not have network connectivity. |
DHCP BOOTP Configuration |
Not applicable |
DCHP has determined that there are no IP addresses available for BOOTP clients in the scope. BOOTP clients cannot obtain an IP address from the DHCP server and may not have network connectivity until the scope is extended or clients give up their leases. |
DHCP Runtime
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCP Audit Logging |
DHCP has determined that the audit log cannot be written to because it is full or cannot be accessed. The DHCP server will continue to function properly, but audit events cannot be recorded until the log is writable. You cannot monitor DHCP server events until the audit log is accessible. |
Not applicable |
DHCP Backup/Restore |
DHCP was unable to back up the server registry configuration. The registry configuration is in danger of being lost if a successful backup is not obtained. |
DHCP was unable to restore the server registry configuration. The server cannot function until the backup is restored successfully. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Lease Issuance |
DHCP was unable to contact the client before leasing an IP address. Because the server received no reply from the client, the server assumed there is no conflict and leased the address to another client. This will not impact server or client functionality. |
Not applicable |
DHCP BOOTP Boot File Configuration |
Not applicable |
DHCP was unable to read the BOOTP file table from the registry. The DHCP service cannot respond to BOOTP requests that specify the boot file name until entries that contain the MAC address of the clients that are making BOOTP requests are manually added to the BOOTP table. BOOTP client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Server Communication |
DHCP could not find the domain to which it is joined. The server cannot lease IP addresses until it can find the domain. Client computers might not be able to obtain new leases from the DHCP server and might not have network connectivity. |
DHCP has encountered a network error. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Authorization and Conflicts |
DHCP cannot determine if the server is authorized on the domain. The server cannot lease IP addresses to clients until it determines that it is authorized. Client computers might not be able to obtain new leases from the DHCP server and might not have network connectivity. |
DHCP has determined that the server is unauthorized to lease to clients on the domain or that there is a conflict with another authorized DHCP server in the workgroup. The server cannot lease IP addresses until it is authorized on the domain or the workgroup conflict is resolved. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Server Active Directory Availability |
Not applicable |
DHCP cannot contact the domain because the directory service or domain controller is unavailable. The server cannot service clients until the directory service and domain controller are available. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP General Availability |
DHCP has encountered an exception to the DLL callout. The exception will be ignored and the DHCP server will continue to function normally. |
DHCP is unavailable because it cannot find the domain, load its DLLs, or gain authorization. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Server DNS Registration |
DHCP failed to impersonate the credentials necessary for DNS registrations and DNS dynamic update protocol. DHCP server security might be compromised. |
Not applicable |
DHCP Server Interface Change Notification |
Not applicable |
DHCP failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCP service. Client computers might not be able to obtain new leases from the DHCP server and might not have network connectivity. |
DHCP Users Group Configuration |
Not applicable |
DHCP was unable to find or create the DHCP Users group or the DHCP Administrators local group. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Server Rogue Detection |
DHCP has detected another DHCP server on the network. There can only be one authorized DHCP server on a network segment. The DHCP server will continue to function normally. |
DHCP cannot authorize the server. The server must be authorized in Active Directory Domain Services. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Service Initialization |
Not applicable |
The DHCP Server service failed to initialize. The server cannot initialize until it has a static IP address configured and proper configuration parameters. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Database
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCP Backup and Restore |
DHCP failed to find and back up the database. The backup will fail until the correct backup directory path is specified. If the database becomes corrupted and a database backup does not exist, the DHCP server will become irreparable. |
DHCP failed to restore the database. The database might be corrupt. You might have to repair the original database, back it up, and then try to restore it again. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Database Migration |
DHCP has determined that the database you are trying to migrate is not compatible with the Windows 2000 format. No action is required. The database converts automatically. |
DHCP has determined that the database being used in this migration is incompatible with the DHCP version you are using. The database needs to be converted to a version after Windows NT 3.51. Migration cannot continue until the database is converted to a compatible version. |
DHCP Database Integrity |
DHCP has detected inconsistencies in the Jet database. If the database becomes corrupted because of these inconsistencies, it may have to be restored from a backup. If the database becomes corrupted and a backup of the database does not exist, the DHCP server will become irreparable. |
DHCP failed to initialize the Jet database. The server cannot lease IP addresses to clients until the database is initialized. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Service
| Aspect | Yellow health state | Red health state |
|---|---|---|
Dependent Service Availability |
Not applicable |
DHCP cannot initialize because one or more services that it depends on failed. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCPv6 Runtime
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCPv6 Audit Logging |
DHCPv6 has determined that the audit log cannot be written to because it is full or cannot be accessed. The DHCP server will continue to function properly, but audit events will not be recorded until the log is writable. |
Not applicable |
DHCPv6 Scopes
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCPv6 Lease Availability |
IPv6 addresses in the DHCP scope are nearing depletion. Expand the scope to allow clients to continue leasing. If the scope is not expanded and it becomes depleted, client computers will not be able to obtain new leases from the DHCP server and will not have network connectivity. |
DHCP has no IPv6 addresses available to lease in the scope. Additional IPv6 addresses cannot be leased until the scope is expanded or clients give up their leases. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCPv6 Service
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCPv6 Server Service |
Not applicable |
DHCP failed to initialize one of its components. The DHCP Server service cannot start. Client computers cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Client
| Aspect | Yellow health state | Red health state |
|---|---|---|
DHCP Client Lease Validity |
Not applicable |
DHCP denied the client an IP address. The client will continue to try to obtain an IP address automatically from the DHCP server. This client computer cannot obtain new leases from the DHCP server and will not have network connectivity. |
DHCP Client IPv6 Availability |
Not applicable |
DHCP IPv6 initialization failed on the computer. The DHCP service will start with IPv4 only. Client computers will have network connectivity but applications that require IPv6 will not function. |
DHCP Client Service Availability |
Not applicable |
DHCP shut down the DHCP Client service. The DHCP Client service will not function until it is restarted. This client computer will not have network connectivity. |
DHCP Client Address Conflicts |
DHCP has detected that the IP address that this computer is using is already in use on the network. This computer will automatically attempt to obtain a different IP address. This client computer will not have network access until a unique address is obtained from the DHCP server. |
DHCP has determined that a computer on the network has an identical IP address and that this computer has lost its lease. The client will attempt to obtain another IP address automatically, but it will not have network connectivity until it obtains a new lease. |
DHCP Client Configuration |
Not applicable |
DHCP was unable to initialize the network interface. The client cannot obtain a lease from the server until the network interface is initialized. This client computer will not have network connectivity. |
DHCP Client Network Errors |
DHCP encountered a network error when trying to send a message. This will not impact the functionality of this client computer. |
Not applicable |