Configuring Monitoring Scenarios in the Windows DHCP Management Pack

  • Article

Table 6 lists the configurable monitoring scenarios and indicates which elements of a monitoring scenario can be modified. The table also indicates whether additional configuration is necessary to use the monitoring scenario.

Table 6 Configurable Monitoring Scenarios

Scenario

Configurable Elements

Additional Configuration Required?

DHCP Performance Monitoring

Enable the Performance Threshold: Irregularly high volumes of DHCP requests are being received. Possible denial of service attack in progress rule in the following rule groups:

  • Windows 2000 DHCP Server/Core Service

  • Windows 2003 DHCP Server/Core Service

Click Edit on the Alert tab to configure the severity and threshold according to the DHCP requests volume in your organization.

Yes

Monitoring Scopes and Superscopes Free Addresses

You can configure the threshold for the number of free addresses, under which you want to be alerted.

You can use the following event parameters to configure the threshold:

  • Parameter 2 - The absolute number of free addresses.

  • Parameter 3 - The absolute number of addresses in use.

  • Parameter 4- The percentage of free addresses.

  • Parameter 5 - Indicates whether or not the scope is a member of a superscope. This parameter applies only to Windows Server 2003.

  • By default, the threshold is configured using Parameter 2, which is set to 0. This means that if the absolute number of free addresses is 0, a "Critical Error" alert is raised.

To configure this threshold, do the following:

  1. In the Administrator console, right-click the DHCP Scope is running low or out of available Addresses rule in the Windows 2000 DHCP Server/State Monitoring and Discovery" rule group or in the Windows 2003 DHCP Server/State Monitoring and Discovery" rule group.

  2. Select Properties.

  3. In the Event Rule Properties dialog box, select the Alert tab, and click Edit.

  4. In the Alert Severity Calculation for State Rule dialog box, using any of the parameters described above, you can add and edit alert severity conditions.

No

Including and Excluding Scopes and Superscopes forMonitoring

For monitoring, you can include and exclude specific scopes and superscopes by configuring script parameters as follows:

  • For scopes configuration, configure the DHCP Server 2000 - Scope Monitoring script parameters in the Windows 2000 DHCP Server/State Monitoring and Discovery/DHCP Scope Monitoring rule.

  • For scopes and superscopes, configure the DHCP Server 2003 - Scope Monitoring script parameters in the Windows 2003 DHCP Server/State Monitoring and Discovery/DHCP Scope Monitoring rule.

No

Many of the monitoring scenarios are configured by changing parameters of scripts that are associated with an event rule. If it is necessary to change a script parameter, you must change the script parameter within the event rule rather than making the change directly to the script that is listed under the Scripts node in the MOM Administrator console. Changing a parameter of a script within the Scripts node does not change the value of the parameter for event rules that are associated with the script.

Note

    The DHCP Management Pack uses a [Subnet] Name format for scope identification. On Windows Server 2000 and Windows Server 2003, the Windows netsh.exe utility, which is used to monitor scopes, might truncate the Name portion and expose only the first 21 characters of a scope name. Therefore, on those servers, ensure that scope names contain 21 or less characters.

Note

If you configure the IncludeScopes or ExcludeScopes parameters of the DHCP Server 2000 - Scope Monitoring and the DHCP Server 2003 - Scope Monitoring scripts with scope names that contain more than 21 characters, the respective scope will not be included or excluded for monitoring as expected. This issue has no impact on scope names specified with the '*' character.

Committing Configuration Changes

After making configuration changes to the DHCP Management Pack, you can deploy the changes to managed computers immediately by committing the configuration changes manually. Otherwise, changes are deployed to managed computers after the rule change polling interval (five minutes by default) and the agent configuration interval (one minute by default).

To commit configuration changes

  1. In the MOM Administrator console, navigate to Management Packs.

  2. Right-click Management Packs, and click Commit Configuration Change.