Professional Documents
Culture Documents
Getting Started
Supporting
PATROL KM for Microsoft Windows Operating System 3.9 PATROL KM for Microsoft Windows Active Directory 1.6 PATROL KM for Microsoft Windows Domain Services 1.5 PATROL KM for Microsoft Cluster Server 1.6 PATROL Cluster Configuration Wizard 1.5 PATROL KM for Microsoft COM+ 1.3 PATROL KM for Microsoft Message Queue 1.4 PATROL KM for Event Management 2.7 PATROL KM for Log Management 2.3 PATROL Wizard for Microsoft Performance Monitor and WMI 2.0 PATROL Adapter for Microsoft Office 1.1 PATROL Agent 3.6
March 2007
www.bmc.com
Copyright 2007 BMC Software, Inc., as an unpublished work. All rights reserved. DB2 is a registered trademark of International Business Machines Corporation. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.
Customer support
You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.
Support website
You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can
I I I I I I I
read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
I I I
sequence of events leading to the issue commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
Contents
Chapter 1 Product components and capabilities 15 16 16 16 17 17 18 18 19 25 26 26 27 27 28 29 30 30 30 31 31 31 32 33 35 35 35 37 39 45 46 46 46 47 47 47 48 49
5
PATROL for Windows Servers features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Centralized event filtering and notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ability to deploy configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Built-in recovery actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predefined rulesets for common server types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Windows Operating System . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Windows Active Directory . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Windows Domain Services . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Cluster Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Message Queue (MSMQ). . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft COM+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Wizard for Microsoft Performance Monitor and WMI. . . . . . . . . . . . . . PATROL History Loader KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Adapter for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Installing and migrating PATROL for Windows Servers
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional component-specific requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual machine support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking for product patches or fixes before installing . . . . . . . . . . . . . . . . . . . . . Determining how to install products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . Determining where to install the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . Determining where to install KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Assessing and implementing a different security level . . . . . . . . . . . . . . . . . . . . . . 49 Default and custom installation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 First-time installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Installing for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 First-time installation using Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Distribution Server features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Importing a CD or customized installation package into Distribution Server . . . 56 Installing with the Distribution Server (overview) . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Upgrading from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Automatic migration of console and agent customizations . . . . . . . . . . . . . . . . . . 58 Determining whether you can migrate KM customizations . . . . . . . . . . . . . . . . . . 58 Conditions for upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Determining the location of PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 PATROL for Windows Servers upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Upgrading without saving KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Upgrading and preserving KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Preparing to upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Migrating customizations with the PATROL Configuration Manager . . . . . . . . . 64 Creating an installation package of the migrated and merged KM . . . . . . . . . . . . 64 Moving files from the PATROL_CACHE directories. . . . . . . . . . . . . . . . . . . . . . . . 65 Migrating customizations manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Installing PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 External cluster-level agent architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Internal cluster-level agent architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 How to Install the PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . 70 Considerations for using online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Browser version required for viewing PATROL Console for UNIX Help . . . . . . 71 Additional considerations for using online Help for UNIX . . . . . . . . . . . . . . . . . . 72 Uninstalling PATROL for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Uninstalling PATROL for Windows Servers on Windows . . . . . . . . . . . . . . . . . . . 74 Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Chapter 3 Loading and configuring PATROL for Microsoft Windows Servers 81
Preparing to use PATROL for Windows Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Loading and preloading KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Loading the PATROL for Microsoft Windows Servers KMs . . . . . . . . . . . . . . . . . 85 Preloading KMs on the PATROL Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Requirements for configuring from the PATROL Console . . . . . . . . . . . . . . . . . . . 91 Configuring the PATROL KM for Microsoft Windows OS . . . . . . . . . . . . . . . . . . . . . . 95 Enabling and disabling system monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuring Windows events monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuring service monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Configuring process monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Creating custom parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Viewing event logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Configuring recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 About recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Built-in native recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6 PATROL for Microsoft Windows Servers Getting Started
Configuring built-in native recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Configuring e-mail notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Using notification scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Defining notification servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Assigning notification servers for the remote agents. . . . . . . . . . . . . . . . . . . . . . . 129 Assigning notification targets for a PATROL alert. . . . . . . . . . . . . . . . . . . . . . . . . 131 Configuring the PATROL KM for Microsoft Active Directory . . . . . . . . . . . . . . 132 Creating new parameters with the PATROL Wizard for Microsoft Performance Monitor and WMI . . . . . . . . . . . . . 133 Loading the PATROL Wizard for Microsoft Performance Monitor and WMI . 133 Creating performance monitor parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Setting alarm thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Creating WMI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Configuring the PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Stop and start monitoring all default log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Stop monitoring a log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Start monitoring a log file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Change the setup of a monitored file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Filter log file messages (create a search string) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Generate a custom event when a search string is identified . . . . . . . . . . . . . . . . . 143 Configure recovery actions for a log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Configuring the PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . 146 Using the PATROL Adapter for Microsoft Office to view reports . . . . . . . . . . . . . . . 147 Displaying PATROL data by using the PATROL Adapter for Microsoft Office 148 How to use the PATROL Adapter for Microsoft Office . . . . . . . . . . . . . . . . . . . . 149 Built-in report templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Removing KMs from your console and agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Unloading KMs from a PATROL console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Stopping preloaded KMs from running on the PATROL Agent . . . . . . . . . . . . . 154 Chapter 4 Using the PATROL Cluster Configuration Wizard 155 156 156 157 157 157 158 163 163 163 164 164 164 164 165 166 169 169 170
7
Using the PATROL Cluster Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing to use the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access requirements for running the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . Starting the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to use the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-PCC configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually configuring the PATROL Agent for clustering . . . . . . . . . . . . . . . . . . . . . . Install the application on each cluster node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the PATROL Agent on each cluster node . . . . . . . . . . . . . . . . . . . . . . . . . . Assign a unique port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribute license file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define the PATROL cluster-specific environment variables . . . . . . . . . . . . . . . . Create and register a new service for the PATROL Agent . . . . . . . . . . . . . . . . . . Define the PATROL Agent as a member of the group . . . . . . . . . . . . . . . . . . . . . PATROL cluster-specific environment variables for history and configuration . . . Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Chapter 5 Troubleshooting PATROL for Microsoft Windows Servers 173
PATROL KM for Microsoft Windows OS problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Process or job object data not displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 PATROL Generates Event 560 and 562 in the Windows security event log . . . . 175 Event filter parameters not automatically acknowledged . . . . . . . . . . . . . . . . . . . 175 Newly installed protocols are not discovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Event log summary instance cannot be removed . . . . . . . . . . . . . . . . . . . . . . . . . . 176 PATROL KM for Event Management problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Too many e-mail alerts are being generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Parameters settings lost after agent restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 PATROL KM for Event Management not working as expected. . . . . . . . . . . . . . 179 AS_AVAILABILITY application not displayed. . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Problems with all other KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Cannot add performance monitor counters with alarm ranges less than 1 . . . . 180 AdPerfCollector parameter display error message. . . . . . . . . . . . . . . . . . . . . . . . . 181 Recovery action problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Recovery actions do not execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Even though I select Do not ask me again PATROL prompts before running recovery action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Gathering diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Locations where you can find diagnostic information. . . . . . . . . . . . . . . . . . . . . . 183 Installation logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Determining PATROL KM version number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Appendix A Accessing menu commands, InfoBoxes, and online Help 185
Accessing KM commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Appendix B Agent configuration variables and rulesets 189
Managing configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 PATROL for Windows Servers configuration variables. . . . . . . . . . . . . . . . . . . . . . . . 190 PATROL KM for Microsoft Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 PATROL KM for Microsoft Windows Domain Services . . . . . . . . . . . . . . . . . . . . 205 PATROL KM for Microsoft Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 PATROL KM for Microsoft Windows Message Queue . . . . . . . . . . . . . . . . . . . . . 216 PATROL KM for Microsoft COM+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 PATROL Wizard for Microsoft Performance Monitor and WMI . . . . . . . . . . . . . 218 PATROL for Microsoft Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 PATROL for Microsoft Windows Servers rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 PATROL KM for Event Management required. . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Using PATROL Configuration Manager to apply rulesets . . . . . . . . . . . . . . . . . . 220 Server roles with predefined rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Ruleset reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Using PATROL Configuration Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Using PCM to apply configurations changes to other agents. . . . . . . . . . . . . . . . 232 Manually creating or changing configuration variables . . . . . . . . . . . . . . . . . . . . 233 Appendix C PATROL for Windows .kml files 243 244 244 245 247 248 249 249 250 250 251 251 251 257
PATROL for Microsoft Windows Servers .kml files . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Windows Active Directory . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Windows Domain Services . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft COM+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Microsoft Message Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Wizard for Microsoft Performance Monitor and WMI. . . . . . . . . . . . . PATROL History Loader KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KM for Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL for Microsoft Windows Servers rulesets. . . . . . . . . . . . . . . . . . . . . . . . . Index
Contents
10
Figures
Upgrading overview for PATROL for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . 61 PATROL KM for Microsoft Cluster Server with external CLA configuration . . . . . . 69 PATROL KM for Microsoft Cluster Server with internal CLA configuration . . . . . . 69 Shipped rulesets in PATROL Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . 222 Using the child_list and variable_list variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Figures
11
12
Tables
Monitored events - DNS name registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Core Active Directory service monitored events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 File replication service/group policy monitored events . . . . . . . . . . . . . . . . . . . . . . . . 24 Time synchronization service monitored events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Kerberos monitored events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Netlogon monitored events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 PATROL for Microsoft Windows Servers Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 System requirements for installing and using PATROL for Windows Servers . . . . 36 Advanced user rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Removing rights and admin group membership from the PATROL Agent . . . . . . . 42 Versions that you can migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Choosing an upgrade procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Default values for PATROL location variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 KM file naming patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Monitoring configuration options for PATROL KM for Microsoft Cluster Server . . 68 PATROL for Microsoft Windows Servers .kml files . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Console functionality that requires local admin rights . . . . . . . . . . . . . . . . . . . . . . . . . 91 PATROL KM for Microsoft Windows OS configuration tasks . . . . . . . . . . . . . . . . . . 96 Enabling and disabling system monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Event filter events:example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Event filter options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Default service monitoring flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Service monitoring options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Configuration variable and service restart: combinations . . . . . . . . . . . . . . . . . . . . . 110 Process monitoring options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Regular expression syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Process control options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Event details displayed in the Windows Event Viewer dialog box . . . . . . . . . . . . . 117 Built-in recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Selecting a recovery action instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Recovery action configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Notification script location on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Requirements for notification server when using Windows e-mail clients . . . . . . . 125 Quick Config - Notification Server dialog box properties . . . . . . . . . . . . . . . . . . . . . 128 Notification server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 PATROL Wizard for Microsoft Performance Monitor and WMI Tasks . . . . . . . . . . 133 Reports for PATROL KM for Microsoft Windows OS . . . . . . . . . . . . . . . . . . . . . . . . 149 Reports for PATROL KM for Microsoft Windows Domain Services . . . . . . . . . . . . 150 Reports for PATROL KM for Microsoft Message Queue . . . . . . . . . . . . . . . . . . . . . . 151 Reports for PATROL for Microsoft COM+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Tables 13
Information required by PCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Cluster administration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 PATROL cluster-specific environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Operation of configuration and history environment variables . . . . . . . . . . . . . . . . . 170 Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 PATROL KM for Microsoft Windows OS variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 PATROL KM for Windows Domain Services variables . . . . . . . . . . . . . . . . . . . . . . . 205 PATROL KM for Microsoft Active Directory variables . . . . . . . . . . . . . . . . . . . . . . . . 208 PATROL KM for Microsoft Cluster Server variables . . . . . . . . . . . . . . . . . . . . . . . . . . 211 PATROL KM for Windows Message Queue variables . . . . . . . . . . . . . . . . . . . . . . . . 216 PATROL KM for Windows COM+ variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 PATROL Wizard for Performance Monitor and WMI variables . . . . . . . . . . . . . . . . 218 PATROL for Microsoft Windows Servers variables . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Server roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Configuration variable locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Application server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Terminal server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Remote access / VPN server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Print server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Domain controller ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 File server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Mail server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 DNS server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 WINS server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 DHCP server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Streaming media server ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 SMS primary site ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 SMS site ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Special characters required for pconfig variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Example: adding a service to monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Example: adding a process to monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Example: adding an event filter to monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Example: changing parameter thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Understanding the THRESHOLDS rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Example: Inactivating or deactivating a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 PATROL KM for Log Management .kml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 PATROL KM for Microsoft Windows OS NT_LOAD.kml file . . . . . . . . . . . . . . . . . . 245 PATROL KM for Microsoft Windows OS NT_BASE.kml file . . . . . . . . . . . . . . . . . . 246 PATROL KM for Microsoft Windows Active Directory .kml file . . . . . . . . . . . . . . . 247 PATROL KM for Microsoft Windows Domain Services .kml file . . . . . . . . . . . . . . . 248 PATROL KM for Microsoft Cluster Server .kml file . . . . . . . . . . . . . . . . . . . . . . . . . . 249 PATROL KM for Microsoft COM+ .kml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 PATROL KM for Microsoft Message Queue .kml file . . . . . . . . . . . . . . . . . . . . . . . . . 250 PATROL Wizard for Microsoft Performance Monitor and WMI .kml file . . . . . . . . 250 PATROL History Loader KM .kml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 PATROL KM for Event Management .kml files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 PATROL for Windows Ruleset .kml files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
14
Chapter
1
16 16 16 17 17 18 18 19 25 26 26 27 27 28 29 30 30 30 31 31 31
15
16
terminating a run-away process clearing the temp directory backing-up and clearing event logs restarting processes restarting failed services increasing available DFS connections when utilization is high increasing share connections when utilization is high initiating WINS scavenging when replication fails restarting the Windows Management Instrumentation (WINMGMT.exe) service to ensure that WMI data is available restarting a PATROL Agent on a remote server
For more information about specific recovery actions, see the online Help, which you can access from the PATROL console, or see Configuring recovery actions on page 117.
17
Product components
Product components
The PATROL for Windows Servers product includes components and Knowledge Modules (KMs) that manage and monitor elements of your server environment. A KM is a set of instructions that the PATROL Agent uses to monitor objects in your enterprise. PATROL for Windows Servers includes the following components and KMs, which are described in the sections that follow.
I I I I I I I I I I I I I
PATROL KM for Microsoft Windows Operating System PATROL KM for Microsoft Windows Active Directory PATROL KM for Microsoft Windows Domain Services PATROL Cluster Configuration Wizard PATROL KM for Microsoft Cluster Server PATROL KM for Microsoft COM+ PATROL KM for Microsoft Message Queue PATROL KM for Event Management PATROL KM for Log Management PATROL Wizard for Microsoft Performance Monitor and WMI PATROL Adapter for Microsoft Office PATROL Agent PATROL History Loader KM
disk space disk drive usage disk quotas and mount points cache CPU usage memory usage Windows event logs Windows services Window processes printer status registry values
18
Product components
With the PATROL KM for Microsoft Windows OS you can also perform the following functions:
I I I
monitor and manage services monitor system Stop errors and manage dump files create custom composite parameters that are based on existing parameters
For information about configuring these features, see Configuring the PATROL KM for Microsoft Windows OS on page 95.
I I I I I
detect and notify if Microsoft Windows Active Directory generates errors or performs slowly monitor performance of system resources plan for capacity and availability monitor all domain controllers within a site monitor all domain controllers between sites anticipate and eliminate problems before they become apparent to users of the monitored Active Directory environments
For a brief description of product features, see the sections that follow. For more detailed information about how to use the product and complete descriptions of the application classes and parameters, see the product online Help.
Managed systems
PATROL KM for Microsoft Windows Active Directory monitors the performance of managed systems in a Microsoft Windows Active Directory environment. A PATROL KM for Microsoft Windows Active Directory managed system is a Windows domain controller onto which PATROL for Windows Servers has been installed. A managed system provides a view of its Microsoft Windows Active Directory environment. Each managed system is responsible for monitoring Microsoft Windows Active Directorys key indicators that are required to ensure and maintain the consistency of the Directory data and the desired level of service throughout the Microsoft Windows Active Directory forest.
19
Product components
Replication monitoring
PATROL KM for Microsoft Windows Active Directory monitors the Microsoft Windows Active Directory replication for errors and latency (to verify that replication occurs within a reasonable time), both within a site (intrasite) and between sites (intersite) in the configuration naming context and/or the domain context of the current domain controller. Directory replication is monitored at each managed system (domain controller). This functionality includes monitoring basic replication by creating synthetic transactions and verifying the replication of those transactions.
20
Product components
FSMO monitoring
PATROL KM for Microsoft Windows Active Directory monitors the availability of the forest-wide and domain-wide flexible single master operations (FSMO) roles.
LDAP monitoring
PATROL KM for Microsoft Windows Active Directory monitors Lightweight Directory Access Protocol (LDAP) locally at each monitored system for connection availability and response time. The AD_AD_LDAP application class monitors the performance of these LDAP requests.
SAM monitoring
PATROL KM for Microsoft Windows Active Directory monitors the Security Account Manager (SAM). SAM provides legacy NT authentication support. The AD_AD_SAM application class monitors these security requests.
Authentication monitoring
PATROL KM for Microsoft Windows Active Directory monitors Kerberos and NTLM authentication requests made against the Microsoft Windows Active Directory server. The AD_AD_AUTHENTICATION application class monitors these requests.
Chapter 1 Product components and capabilities 21
Product components
Event monitoring
To measure the overall health of the domain controllers, PATROL KM for Microsoft Windows Active Directory configures the PATROL KM for Microsoft Windows OS to monitor various events pertaining to
I I I I I I
DNS name registration Core Active Directory service File replication service and group policy Time synchronization service Kerberos Netlogon
22
Product components
System
NETLOGON
5774
Product components
Table 3
Event log FRS
Application
Application
SCECLI
Severity = error
Kerberos
To identify events that many indicate problems with Kerberos, the default authentication protocol, PATROL KM for Microsoft Windows Active Directory monitors the event shown in Table 5 Table 5
Event Log System
Net Logon
To identify events that may indicate problems with Net Logon service and protocol, which is required for proper domain controller functionality, PATROL KM for Microsoft Windows Active Directory monitors the events shown in Table 6 on page 25.
24
Product components
Table 6
Event log System
Distributed File System (DFS) Dynamic Host Configuration Protocol (DHCP) service availability and lease usage Domain Name Service (DNS) remote server connectivity replicated directories shared directories trust relationships Windows Internet Naming Service (WINS)
For instructions on how to monitor these features, see the PATROL KM for Microsoft Windows Domain Services online Help system.
25
Product components
all clusters in a domain (only available when the agent is outside of the cluster) individual clusters cluster communication networks cluster network interfaces cluster nodes cluster objects and resources cluster groups workload data group resources quorum device
For more information about specific functionality that supports these features see the PATROL KM for Microsoft Cluster Server online Help.
26
Product components
MSMQ service MSMQ queues MSMQ messages MSMQ roundtrip message time
For instructions on how to monitor these features, see the PATROL KM for Microsoft Message Queue KM online Help system.
monitors the COM+ run-time environment monitors the status of COM+ applications manages the MS DTC service by providing the ability to start or stop the service monitors Windows COM+ log events monitors Windows log events related to the Microsoft Distributed Transaction Coordinator (MS DTC) service and monitors the MSDTC service status
For instructions on how to use these features, see the PATROL KM for Microsoft COM+ KM online Help system.
27
Product components
automatically monitors key log files monitors files that do not currently exist on the system monitors log files with dynamic names using wild card characters monitors the size of log files monitors the growth rate of log files monitors the content of log files monitors the state of log files monitors the age of the log files monitors log files using numeric comparisons
The PATROL KM for Log Management also provides the following management features:
I
triggers alerts when a log file exceeds a specified size triggers alerts when a text string or regular expression is discovered within a log file creates automated recovery actions when a log file exceeds an acceptable size or growth rate configures log searches to ignore subsequent alerts for a specified number of polling cycles if the search finds a matching string or regular expression in a log file override an ignored alert if the search finds a matching string or regular expression more than n times before the ignore setting is completed specify the number of log scan cycles after which a WARN or ALARM state is automatically changed to OK
creates robust searches by using NOT and AND statements with the text strings or regular expressions in the log search alerts for log file age sets multiple polling schedules per log file disables/enables default log monitoring
28
Product components
You can set up the following predefined recovery actions to execute when monitored log files exceed a specified size or growth rate.
I I I
clear and back up log files delete files run in attended and unattended modes
To get started with the PATROL KM for Log Management, see Configuring the PATROL KM for Log Management on page 135. For detailed instructions, see the PATROL KM for Log Management User Guide and the PATROL KM for Log Management online Help system.
configure notification (email, paging, trouble-ticket, or custom) for PATROL alerts configure PATROL to send notifications to an enterprise console configure recovery actions for alarm, warning, and information events reword notification messages and customize message content specify the maximum number of events displayed in the console use wildcards to represent instance names when setting up parameters configure PATROL to monitor the availability of hosts manage PATROL parameter thresholds and polling schedules configure blackout periods for notification and for availability monitoring integrate with the AlarmPoint notification software using provided scripts integrate with any command line email client, paging solution, compiled executable, or script. Sample scripts are provided.
To get started with the PATROL KM for Event Management, see Configuring e-mail notification on page 121. For more detailed instructions and reference information, see the PATROL KM for Event Management User Guide.
29
Product components
30
Services
PATROL Agent
PATROL for Windows Servers includes the PATROL Agent. The PATROL Agent monitors a system according to the instructions provided by loaded PATROL KMs. You can display the information gathered by the PATROL Agent on the PATROL Console. For more information, see the PATROL Agent Reference Manual.
Services
The PATROL for Microsoft Windows Servers product uses the following services: Table 7
Service PatrolAgent The PATROL MCS Monitor Service
Related documentation
For additional information about PATROL for Windows Servers, see the online Help for the component of interest and refer to the PATROL for Microsoft Windows Servers release notes. For information about the PATROL for Windows Servers parameters, see the product Help or the PATROL Parameter Reference Manual. For additional information about PATROL, see the following documentation:
I I
To view the complete PATROL documentation library, visit the support page on the BMC Software Web site at http://www.bmc.com/support_home. Log on and select a product to access the related documentation. To log on if you are a first-time user and have purchased a product, you can request a permanent user name and password by registering at the Customer Support page. To log on if you are a first-time user and have not purchased a product, you can request a temporary user name and password from your BMC Software sales representative.
31
how to load and configure the components using a Chapter 3, Loading and configuring PATROL for PATROL console Microsoft Windows Servers troubleshooting configuration problems Chapter 5, Troubleshooting PATROL for Microsoft Windows Servers
PATROL for Windows Servers agent configuration Appendix B, Agent configuration variables and variables and predefined rulesets rulesets KMs included in each PATROL for Windows Servers .KML file Appendix C, PATROL for Windows .kml files
32
Chapter
This chapter provides the information that you need to install PATROL for Windows Servers. For additional information about the PATROL installation process, see the PATROL Installation Reference Manual. The following topics are discussed in this chapter: Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional component-specific requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual machine support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking for product patches or fixes before installing . . . . . . . . . . . . . . . . . . . . . Determining how to install products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . Determining where to install the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . Determining where to install KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assessing and implementing a different security level . . . . . . . . . . . . . . . . . . . . . . Default and custom installation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First-time installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First-time installation using Distribution Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution Server features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing a CD or customized installation package into Distribution Server. . . Installing with the Distribution Server (overview) . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic migration of console and agent customizations . . . . . . . . . . . . . . . . . . Determining whether you can migrate KM customizations. . . . . . . . . . . . . . . . . . Conditions for upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the location of PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL for Windows Servers upgrade scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 Installing and migrating PATROL for Windows Servers
35 35 35 37 39 45 46 46 46 47 47 47 48 49 49 49 50 50 55 55 56 57 58 58 58 59 60 61
33
Upgrading without saving KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Upgrading and preserving KM customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Preparing to upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Migrating customizations with the PATROL Configuration Manager . . . . . . . . . 64 Creating an installation package of the migrated and merged KM . . . . . . . . . . . . 64 Moving files from the PATROL_CACHE directories. . . . . . . . . . . . . . . . . . . . . . . . 65 Migrating customizations manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Installing PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 External cluster-level agent architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Internal cluster-level agent architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 How to Install the PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . 70 Considerations for using online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Browser version required for viewing PATROL Console for UNIX Help . . . . . . 71 Additional considerations for using online Help for UNIX . . . . . . . . . . . . . . . . . . 72 Uninstalling PATROL for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Uninstalling PATROL for Windows Servers on Windows . . . . . . . . . . . . . . . . . . . 74
34
Installation overview
Installation overview
This chapter contains instructions for installing PATROL for Windows Servers. For additional installation instructions, see the following documents:
Component PATROL KM for Event Management PATROL KM for Log Management PATROL History Loader KM See PATROL KM for Event Management User Guide PATROL KM for Log Management User Guide PATROL History Loader Knowledge Module User Guide
PATROL Perform Agent for Microsoft Getting Started with PATROL for Microsoft Windows Windows Servers Servers Performance
system requirements requirements for specific PATROL for Microsoft Windows Servers components account requirements
System requirements
Verify that the target computer meets the installation requirements listed in Table 8 on page 36. These requirements apply to all PATROL for Windows Servers components.
Chapter 2
35
Table 8
Resource operating systems
System requirements for installing and using PATROL for Windows Servers (Part 1 of 2)
Requirements For an updated list of supported operating systems, see the PATROL for Microsoft Windows Servers Release Notes. All security levels are supported. For more information about PATROL security, see PATROL Security levels on page 48. The PATROL Security Level is set during the installation of the PATROL infrastructure components. If your product contains the PATROL Agent, you are able to select the security level. Make sure that the level that you select is compatible with the rest of your enterprises PATROL installation. Comments
security levels
For an updated list of supported operating systems, see the PATROL for Microsoft Windows Servers Release Notes. You must have a valid demonstration license (typically good for 30 days) or a permanent license to run your PATROL products. If you are installing an agent or console with PATROL for Windows Servers, you must specify the port number to connect to all the agent computers. If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department. The default port number for agents is 3181. The default port number for the RTServer is 2059.
ports (UDP/TCP)
(UNIX only) browser to support online Help for PATROL Console for UNIX browsers
Use Netscape Navigator version 3.014.78 to use Browser version required for viewing online Help with PATROL for UNIX. PATROL Console for UNIX Help on page 71
This product uses an installation utility that requires a browser. For a list of supported browsers, see the PATROL Installation Reference Manual.
disk space 151 MB for an agent needed to install (without components and KMs) 151 MB for a console (without components and KMs) 242 MB for an agent (with all solution components and KMs) 116 MB for a console (with all solution components and KMs) Monitor (for Console) 256-color display 800 x 600 resolution
36
Table 8
Resource File system Network
System requirements for installing and using PATROL for Windows Servers (Part 2 of 2)
Requirements FAT or NTFS TCP/IP network protocol Comments
NT_DHCP parameters WpReplicationFailures parameter executing the WINS Database Scavenging menu command
As a default, the SNMP service is configured to accept SNMP packets from any host. If the service is configured to accept packets from hosts, then the local host IP address or hostname must be added to the list of hosts. It is not sufficient to add localhost or the loopback address 127.0.0.1. At a minimum, the SNMP community string must have READ permissions. To initiate the WINS Database Scavenging menu command, the community string must have WRITE permissions as well. On Windows 2000 servers, the community string must be an ASCII character string. Microsoft Windows 2000 does not support non-ASCII characters in community strings. For the NT_DHCP application class to work, the default PATROL Agent account must have full access to %PATROL_HOME% and all subdirectories. On Windows 2003 and later, the default PATROL Agent account must also be a member of the DHCP Users group.
Chapter 2
37
Process monitoring
To monitor processes, the PATROL Agent must have access to the following hive and all sub-keys: HKLM\SOFTWARE\Microsoft\WindowsNT\perflib
38
Monitoring replication within the domain naming context requires that the PATROL Agent defaultAccount have sufficient Active Directory permissions to create a container object and child container objects in the domain naming context of the domain in which the domain controller resides. The account must have full control of the created objects. The PATROL Agent defaultAccount must be granted permission to Create Container Objects in each Domain NC and to give Full Control to the created container object and its children.
Accounts
This section describes how to set up a PATROL installation account for Windows.
Chapter 2
39
Stand-alone workgroup servers must use a local user account as a PATROL Agent default account. Servers that are trusted members of a domain can use either a local or a domain account. Domain controllers must use a PATROL Agent default account that is also a domain account.
KM functions performed
The PATROL Agent uses the PATROL Agent default account to perform the following KM functions:
I I I I I I I
collect information from performance counters collect information from the Windows event log self-tune for peak performance and non-intrusive use of the processor access system-level information make debug-level output available from the PATROL KM applications access the command interpreter for operating-system-level commands create and remove processes in the process table for collecting performance data
Advanced User Right Act as part of operating system Debug programs Increase quotas
40
Table 9
Advanced User Right Log on as a service Log on locally (Windows 2000) Allow log on locally (Windows 2003) Manage auditing and security log Profile system performance Replace a process level token
Administrative rights
BMC Software recommends that you make the PATROL Agent default account a member of the local Administrators group of the computer where the agent will reside. On a domain controller, BMC Software recommends that you make the account a member of the domain Administrators group. However, you can choose to remove the PATROL Agent default account from the local or domain Administrators group. You could also remove the advanced user rights described in Table 9 on page 40. However, if you do so, the PATROL Agent cannot perform all of its tasks. Table 10 on page 42 shows the PATROL for Microsoft Windows Servers tasks that the Agent cannot perform when the following restrictions are placed on the PATROL Agent default account:
I
The account is in a domain user group or local user group, but is not in the domain or local administrators group. The account does not have all of the advanced user rights noted in Table 9 on page 40.
Chapter 2
41
Table 10
KM
Removing rights and admin group membership from the PATROL Agent (Part 1 of 3)
Effect Restart Service recovery action does not execute. Message in system output window indicates access denied and inability to restart service. If the PATROL Agent default account lacks the Debug Programs right, cannot monitor the status of processes. The Terminate Process and Restart Process recovery actions do not work. Backup Event Log and Clear Event Log recovery action does not work. Workaround and notes The PATROL Agent default account must be in the local or domain Admins group. Granting a specific user right is not a valid workaround. Add the Debug Programs right to the PATROL Agent default account. Membership in the Administrators group not needed. Add the Debug Programs right to the PATROL Agent default account. Add the user right Backup files and directories to the PATROL Agent default account. For the security event log, you must also add the user right Manage auditing and security log. The PATROL Agent default account must be in the local or domain Admins group. Assign read/write permissions on the temp directory to the PATROL Agent Default account. Add the user right Manage auditing and security log to the PATROL Agent default account. The PATROL Agent default account must be in the local or domain Admins group. Granting a specific user right is not a valid workaround.
Logical disk quotas and mount points do not work. The Clean Temporary Directories recovery action does not execute. Unable to monitor the security event log. The NT_EVENTLOG application displays a message in the _CollectionStatus parameter. Blue Screen KM unable to detect a blue screen condition.
42
Table 10
KM
Removing rights and admin group membership from the PATROL Agent (Part 2 of 3)
Effect AD disk space used does not work. Workaround and notes Grant the PATROL Agent default account the following permission on the DSA Working Directory and its subdirectories: List Folder Contents/Read Data. The KM reads the registry to obtain the DSA Working Directory. It needs access to the following registry keys and subkeys: HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\NTDS Configuration NC replication checking does not work. Grant the PATROL Agent default account sufficient Active Directory permissions to create a container object and child container objects in the configuration naming context of the forest in which the domain controller resides. Grant the PATROL Agent defaultAccount permission to Create Container Objects in the Configuration NC and to give Full Control to the created container object and its children. Domain NC replication checking does not work. Grant the PATROL Agent default account sufficient Active Directory permissions to create a contained ccountancy object and child container objects in the domain naming context of the domain in which the domain controller resides. Grant the PATROL Agent defaultAccount permission to Create Container Objects in each Domain NC and to give Full Control to the created container object and its children.
The cluster KM does not function. No authentication to the cluster can be performed.
To be fully functional, the agent outside of the cluster can be in the admin group and contain all of its rights, while the agents within the cluster are removed from the administrators group and do not have the seven advanced user rights.
Chapter 2
43
Table 10
KM
Removing rights and admin group membership from the PATROL Agent (Part 3 of 3)
Effect Shares are not monitored. Parameters are not discovered. Workaround and notes Add the PATROL Agent default account to the Account Operators, Print Operators, or Server Operators built-in group. Add the PATROL Agent default account to the Account Operators, Print Operators, or Server Operators built-in group. Grant the advanced user right log on locally to the PATROL Agent default account. Add the PATROL Agent default account to the DHCP Users group.
The Increase connections allowed o Share recovery action associated with the ShConnPercent parameter does not work. DFSRootReplica does not work when checking alternate domain controller. Parameters are unavailable and in alarm. On Windows 2003, the NT_DHCP application class does not work.
WARNING
Do not use a built-in Windows domain or local Administrator account as the PATROL default account. Such account usage causes files created by PATROL to be owned by the Administrator, which could result in security or file access problems.
cluster account must be a domain account cluster account must have access permission to the cluster all local agents in the cluster must use the same port number
An external CLA configuration requires a user-defined cluster account separate from the PATROL default account. This account must have cluster administrative privileges. The PATROL MCS Monitor Service (McsService.exe) also runs under this account.
44
An internal CLA configuration can use either a separate user-defined cluster account (a domain account with cluster administrative privileges) or, when certain requirements are met, it can use the PATROL default account. When installed, if the PATROL KM for Microsoft Cluster Server does not discover a separate cluster account, it checks the PATROL agent default account for the following required characteristics:
I I
If these requirements are in place, the Cluster KM uses the PATROL agent default account to access the cluster and to communicate with the agents running on all other nodes in the cluster, and the PATROL MCS Service runs under this account. This account information is not replicated to other nodes so, if you want the Cluster KM to use the PATROL agent default account to monitor the cluster, these requirements must exist for every PATROL agent default account on every node in the cluster.
Chapter 2
45
determine how to install products (see page 46) ensure you are using the appropriate version of the installation utility (see page 47) understand where to install the PATROL Agent and KMs (see page 47) choose between Default and Custom installation options (see page 49) understand PATROL security options (page 48)
46
1 Open a command prompt. 2 Navigate to the directory where the installation utility is located. 3 Enter Setup.exe -v (Windows) or setup sh -v (UNIX).
Computers hosting a PATROL Agent Each computer that you want to monitor should, at a minimum, have the PATROL Agent and the PATROL KM for Microsoft Windows OS. You might want to install other KMs to monitor specific server types such as Exchange Servers, Microsoft SQL Servers, Domain Controllers, Cluster Servers, Terminal Servers, and so on. When installing these KMs on the PATROL Agent computer, select Managed System as the system role during the installation.
Chapter 2
47
Computers hosting a PATROL console Install every KM that you want to use on each PATROL console computer. When installing these KMs on a PATROL console computer, select Console Systems as the system role during the installation.
Computers hosting a PATROL Console Server If you use the PATROL Console Server, install every KM that you want to use on the PATROL Console Server computer. Install the same KM and the same version of the KM that is running on the PATROL Agents. When installing these KMs on a PATROL Console Server computer, select Common Services as the system role during the installation.
For more information about the PATROL consoles and PATROL Console Server or RTserver, see the products respective online help systems and the following documents:
I I I I I I
PATROL Central Operator - Web Edition Getting Started PATROL Central Operator - Microsoft Windows Edition Getting Started PATROL Console Server and RTserver Getting Started PATROL Configuration Manager User Guide PATROL Console for UNIX User Guide PATROL Console for Microsoft Windows User Guide - Understanding the Basics of PATROL, Volume 1, 2, and 3
48
1 From the command line switch to the path on the computer that you want to check:
%BMC_ROOT%\common\security\bin\Windows-x86
2 Run the following command to display the security policy of the current machine:
esstool policy -a
The security level is displayed in the security level field of the output.
The Default installation type uses default values for all optional configuration information. It prompts you only for mandatory configuration information. This type is for any or all of the following situations: You are new to the PATROL product that you are installing and you have an agent or console already installed in the default directories. You are performing a first-time installation (you are not upgrading), and you are installing into the default product installation directories.
NOTE
If you are installing PATROL for Windows Servers to an existing PATROL Agent or Console environment that is not in the default installation directory, use Custom. Do not use Default. Default will automatically install the agent or console with PATROL for Windows Servers and overwrite your existing installation.
Chapter 2
49
First-time installation
With the Custom installation type, you can install individual components of the product. It requires that you specify all configuration information. This type is for any or all of the following situations: You want to install individual components rather than the entire product. You want to specify the following settings: I the port numbers that components use to communicate with each other I a security level greater than basic security I any other product settings that a user might want to change You are upgrading PATROL for Windows Servers from a previously installed version. You are installing into an existing PATROL environment that is not in the default installation directory.
With each installation type, you can always deselect any components that you do not want to install.
First-time installation
The installation utility offers two types of installations: Default and Custom. For a description of the two types of installations, see Default and custom installation types on page 49.
NOTE
By default, the Default installation type configures the PATROL Agent to connect through port 3181. If you want to connect the agent from a different port, you must use the Custom installation type.
You first should install on a limited number of computers in the test environment, test the installation thoroughly, and then install in your production environment. You must have created the PATROL default account.
50
First-time installation
If you want to install PATROL for Windows Servers on a computer running Windows 2000 with Citrix Metaframe, you must have access to a second computer that runs a browser that is supported by the installation utility.
To install using the default installation type 1 Close the Service Control Manager window and the Control Panel window. 2 From the PATROL for Microsoft Windows Servers CD or from an installation
image that has been electronically downloaded from an EPD site and extracted, run setup.exe. When installing on a Windows Server in application mode or with Citrix Metaframe installed, perform the following steps to launch the installation utility:
A From a command line, change to the directory where the installation utility is
located and enter the following command to change to installation mode:
change user/install
A message box is displayed that shows the URL to use to connect to the installation Web server.
C On another computer with a browser, start the browser. D Connect to the installation Web server from the browser to start the installation
utility by using the URL that is displayed in the message box on the computer on which you are installing the product.
3 In the Welcome to the Installation Utility window, click Next to begin your
installation.
4 Review the license agreement, select Accept, and click Next to continue. 5 In the Select Installation Option window, select I want to install products on this
computer now and click Next to continue.
6 In the Select Type of Installation window, select Default and click Next to continue. 7 In the Specify Installation Directory window, accept the default directory and click
Next to continue.
Chapter 2
51
First-time installation
8 In the Select System Roles window, select any or all of the following roles to
indicate the components that you want to install and click Next:
I
If you are installing to a computer that hosts or will host only a PATROL Console for Windows, select Console Systems. If you are installing to a computer that hosts or will host a PATROL Agent, select Managed Systems. If you are installing to a computer that hosts or will host the PATROL Central Operator Web Edition, or the PATROL Console Server select Common Services.
9 From the Select Products and Components to Install window, select components
that you want to install or accept the defaults and click Next.
10 In the PATROL Default Account Properties window, enter the user name and
password that you want to use for your PATROL default account and click Next. This window is displayed only when you are installing a product that requires a PATROL logon. You should have created this account manually before you began to install PATROL. (For more information, see Accounts on page 39.)
11 In the Review Selections and Install window, review your selections and, to make
changes, click Back or, to start installing, click Start Install. A status window opens that contains current messages, current milestones, and percentage complete.
12 When the status window reports that the installation is 100% complete, click Next
to view the results window. (Next does not appear until the installation is 100% complete.)
13 (Optional) In the results window, click View Log to review the details of the
installation.
14 Click Finish to close the installation utility. To install using the custom installation type 1 Close the Service Control Manager window and the Control Panel window. 2 From the PATROL for Microsoft Windows Servers CD or from an installation
image that has been electronically downloaded from an EPD site and extracted, run setup.exe.
52
First-time installation
When installing on a Windows Server in application mode or with Citrix Metaframe installed, perform the following steps to launch the installation utility:
A From a command line, change to the directory where the installation utility is
located and enter the following command to change to installation mode:
change user/install
A message box is displayed that shows the URL to use to connect to the installation Web server.
C On another computer with a browser, start the browser. D Connect to the installation Web server from the browser to start the installation
utility by using the URL that is displayed in the message box on the computer on which you are installing the product.
3 In the Welcome to the Installation Utility window, click Next. 4 In the Review License Agreement window, review the license agreement, select
Accept and click Next.
5 In the Select Installation Option window, select I want to install products on this
computer now and click Next.
6 From the Select Type of Installation Window, select Custom and click Next. 7 In the Specify Installation Directory window, enter the directory where the
products that you select will be installed and click Next. The PATROL product directory is appended to the path that you enter in this step. You will specify the PATROL product directory in step 10 on page 54.
8 In the Select System Roles window, select any or all of the following roles to
indicate the components that you want to install and click Next:
I
If you are installing to a computer that hosts or will host a PATROL Console, select Console System. If you are installing to a computer that hosts or will host a PATROL Agent, select Managed System. If you are installing to a computer that hosts or will host the PATROL Central Operator Web Edition or the PATROL Console Server, select Common Services.
Chapter 2 Installing and migrating PATROL for Windows Servers 53
First-time installation
For more information about the PATROL consoles and PATROL Console Server or RTserver, see the following documents:
I I I
PATROL Central Operator Web Edition Getting Started PATROL Central Operator Microsoft Windows Edition Getting Started PATROL Console Server and RTserver Getting Started
9 From the Select Products and Components to Install window, select the items that
you want to install, and click Next.
10 In the Provide the PATROL 3.x Product Directory window, enter in the PATROL
3.x Product Directory field the directory in which you want to install PATROL for Windows Servers as appropriate for your installation. This directory is appended to the base directory path that is shown in the BMC Products Installation Directory field entered in step 7 on page 51.
11 If the PATROL Default Account Properties window appears, enter the user name
and password that you want to use for your PATROL default account and click Next. This window is displayed only when you are installing a product that requires a PATROL logon. You should have created this account manually before you started the installation process. (For more information, see Accounts on page 39.)
12 In the Complete the Confirm BMC Product Startup Information window, perform
the following steps (this window does not appear if you are not installing into a managed system):
A In the Specify the Current Agent Port Number field, enter the port number that
you want the PATROL Agent to use. The default is 3181.
NOTE
If your previous installation used a different port number, change the default to the current port number for the PATROL Agent.
B In the Restart the PATROL agent automatically? field, click Yes or No. 13 In the Review Selections and Start Install window, review the selections and, to
make changes, click Back or, to start installing, click Start Install.
14 When the status window reports that the installation is 100% complete, click Next
to view the results window. (Next does not appear until the installation is 100% complete.)
54
15 (Optional) In the results window, click View Log to review the details of the
installation.
Install, uninstall, upgrade, and reinstall products on remote systems from one central location. Create collections of products and system groups to distribute multiple products to multiple systems in one distribution. Schedule a distribution for a specific date and time. Maintain multiple product versions to be distributed. View reports to check distribution status, gather distribution data, and diagnosis problems.
To import PATROL for Windows Servers into the Distribution Server, perform the following tasks: Importing a CD or customized installation package into Distribution Server on page 56.
Chapter 2
55
The customized installation packages that resulted from Creating an installation package of the migrated and merged KM on page 64 must be accessible to the Distribution Server. Ensure that you use the Distribution Server version 7.1.01 or later.
To import components in to the Distribution Server 1 Using the Distribution Server Manager, connect to the Distribution Server. 2 In the Distribution Server tab area, click the Components tab. 3 In the list area, click the Import button. 4 Navigate to the location where the components are located and click Next. 5 Select the directory that contains the Products directory (do not select the Products
directory itself). If the components are not accessible on a local drive, you can specify them by using the NFS name and path.
EXAMPLE
Assuming that you copied the CD image into a directory called merged_CD and then, after migrating your customizations and creating a customized installation package, you copied the updated package to the directory containing the CD image, the resultant directory structure would resemble merged_CD\Products\pokchm. You would select the directory merged_CD.
6 Select the check boxes for the components that you want to import and click OK. 7 Click Import to import the selected components.
56
To set up products 1 Import components into the Distribution Server repository on the Components tab
of the Distribution Manager.
3 Configure the collections on the Configurations tab of the Distribution Manager. To set up systems 1 Create accounts in the operating system of the computers to which you want to
distribute PATROL for Windows Servers.
2 Add accounts and create profiles for the systems on the Systems tab of the
Distribution Manager.
3 Add the systems and install the Distribution Client on the Systems tab of the
Distribution Manager.
4 Arrange systems in system groups on the Systems tab of the Distribution Manager. To distribute products 1 Distribute configurations of collections to system groups on the Distributions tab of
the Distribution Manager.
2 Run reports to review distributions on the Reports tab of the Distribution Manager.
For detailed instructions about how to perform remote installations with the Distribution Server, see the Distribution Server Getting Started Guide.
Chapter 2
57
Upgrading without saving KM customizations on page 62 Upgrading and preserving KM customizations on page 62
Figure 1 on page 61 describes the general process of upgrading to a new version of PATROL for Windows Servers and migrating any customizations.
agentsstored in the agent configuration file consolesstored in the console cache files
NOTE
Customized Knowledge Modules and PSL files are also stored in the cache but they are not automatically preserved and incorporated.
58
Table 11
Component
PATROL KM for Microsoft Windows Active Directory PATROL History Loader KM PATROL KM for Microsoft Message Queue PATROL KM for Microsoft Cluster Server PATROL KM for Microsoft COM+ PATROL Wizard for Microsoft Performance Monitor and WMI
When the PATROL KM for Microsoft Windows Active Directory is installed on a server that has PATROL KM for Windows Domain Services 1.3.00, 1.4.00, or 1.4.01 installed, the application classes that begin with NT_AD are automatically disabled. These disabled application classes are recorded in the configuration variable /AgentSetup/disabledKMs.
have not made any customizations to the KM files in your previous version of PATROL for Windows Servers want to overwrite customizations you made to the KM files with the default values of the new version of PATROL for Windows Servers have a currently installed version of PATROL for Windows Servers that cannot be migrated (See Table 11 on page 58)
made customizations to the KM files in your previously installed version of PATROL for Windows Servers and want to save those customizations and migrate them to the new version of PATROL for Windows Servers
Chapter 2
59
Using the control panel 1 Select Control Panel using one of the following menu paths:
I I
Start => Settings => Control Panel. Start => Control Panel.
2 Open the System application. 3 Select the Advanced tab. 4 Click Environment Variables. 5 Scroll through the System Variable list box to view the variables.
The System application displays PATROL_CACHE only if it is set to a value other than its default value.
60 PATROL for Microsoft Windows Servers Getting Started
not migrating customizations migrating customizations manually migrating customizations then installing the product using one of the following tools: Common Installation Utility for local installations Distribution Server for remote installations
Figure 1
Saving customizations?
No
Yes
Yes No
No
Migrating customizations manually on page 66 Back up PATROL_HOME and PATROL_CACHE directories and note all customizations. Shut down agent and console, remove previous version of the product from PATROL_CACHE and PATROL_HOME directories on agent and console computers. Install PATROL for Windows Servers using instructions in on page 50. Manually change settings or PSL files to match your customizations for the previous version.
Chapter 2
61
NOTE
Customizations applied using PATROL Configuration Manager or operator overrides are automatically saved in the agent configuration database. They will take effect automatically unless the parameter name or application name has changed. In either of those cases, you must reapply the customizations.
When installing PATROL for Microsoft Windows Servers over an existing version, if you stop PATROL services manually (not normally required) before running the installation program, stop the PatrolAgent service (PatrolAgent.exe) first, followed by any other PATROL services.
NOTE
To upgrade and preserve customizations, you must either migrate your customizations manually or use the PATROL Migration Tools version 3.5 to create a customized installation package. If you are using the Distribution Server to install the merged customization package, ensure that you have the latest version of the product installed as well as any available patches.
62
Preparing to upgrade
Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the current installation. If the .kml file or any of the .km files for the new version of PATROL for Windows Servers has a different file name from the previous version, you must remove those files from the list of KMs that are preloaded on the PATROL Agent.
1 Shut down any PATROL Agents, consoles, and related services that are currently
running.
2 Ensure that no one is accessing any PATROL files or directories. 3 Perform a full backup of the directories where PATROL files are typically stored.
These directories are listed in the following table:
File type executables and data console customizations Directory PATROL_HOME for agent and console installation directories PATROL_CACHE for the console working cache
Chapter 2
63
If you have localized parameters or global parameters that have customized poll times or thresholds, use the AS_CHANGESPRING KM to migrate these customizations into PATROL Configuration Manager rulesets as described in the PATROL Configuration Manager User Guide. If you have created custom recovery actions, follow these steps: 1. Ensure that you have made a record of your customizations and have backed up the customized files in the PATROL_HOME and PATROL_CACHE directories. 2. Uninstall the old version of PATROL for Microsoft Windows Servers. 3. Install the new version of PATROL for Microsoft Windows Servers as described in the section Installing for the first time on page 50. 4. Ensure that you have made a record of your custom recovery actions. 5. Use the Recovery Action Event Management commands as described in the PATROL Configuration Manager User Guide to migrate your custom recovery actions to the PATROL Configuration Manager.
1 Copy the entire contents of the PATROL for Windows Servers CD to a temporary
directory on a hard drive on a server. You can delete this temporary directory after you have successfully created an installable image.
2 Navigate to the packaged_results directory for the merged package and open the
.ppf file with a text editor. Write down the file name in the first line of the .ppf file. This file name is the name of the directory that you will look for in the Products
3 Rename the packaged_results directory with the file name that you found in the .ppf
file in the previous step.
EXAMPLE
If pokckm/8.5.00/030107-233044 was listed in the first line of the .ppf file, you would use pokckm as the directory name.
4 Copy the renamed directory to the Products directory of the temporary directory
that you used in Step 1. You will be replacing the files there with the merged files that contain your customizations.
5 Copy the PATROL for Windows Servers CD image to the server that you will use
to install PATROL for Windows Servers.
Remove the files in the PATROL_CACHE directory by following the instructions in Moving files from the PATROL_CACHE directories. Install PATROL for Windows Servers from the target server by following the instructions in Installing for the first time on page 50. Import the customized version of PATROL for Windows Servers into the Distribution Server by following the instructions in Importing a CD or customized installation package into Distribution Server on page 56.
Chapter 2
65
Table 14
Component
PATROL KM for Microsoft Message Queue PATROL KM for Microsoft Windows Domain Services
MQ* MSMQ* MSDM* NT_* NTD_* AD* MWD* MCS* AS* EVENT* LOG* PMG* H*.km H*.psl History-* History_Loader* Hist* COM_DEB_* COM_STAT_* NT_WMI* NT_PERFMON*
I I I
PATROL KM for Microsoft Windows Active Directory PATROL for Microsoft Cluster Server PATROL KM for Event Management PATROL KM for Log Management PATROL History Loader KM
I I I I I I I I I I I I I I
I I
To migrate customizations to KM files manually 1 Ensure that you have made a record of your customizations and have backed up
the customized files in the PATROL_HOME and PATROL_CACHE directories.
2 Uninstall the old version of PATROL for Windows Servers. 3 Install the new version of PATROL for Windows Servers as described in the
section Installing for the first time on page 50.
4 Identify and record the coding changes, which represent your customizations, in
PATROL for Windows Servers by comparing the content of the ASCII files in the newly installed PATROL for Windows Servers version with the content of the customized ASCII files with the same name that is saved in the directory to which you moved the old version.
66 PATROL for Microsoft Windows Servers Getting Started
A Restart the PATROL console. B Load the newly installed PATROL for Windows Servers. C Using a PATROL developer console, enter the customizations that you
identified in step 4 on page 66, one by one.
If you modified .psl files that were shipped by BMC Software, you must manually re-edit the PSL code in the new KM by using a PATROL developer console to reapply your changes. If you modified PSL code embedded in a .km file, that code will be overwritten when you install a new version of the product. You must manually edit the new .km files by using a PATROL developer console to reapply your changes. If you created a new PSL file (not shipped by BMC Software) outside of a .km file, Installing PATROL for Microsoft Cluster Server
Chapter 2
67
Table 15
allows you to use the same CLA to monitor multiple clusters maintains both the configuration and history files outside of the cluster; history is not interrupted during a failover requires a CLA computer that resides outside of the cluster
internal CLA
I I I I
monitors only the underlying cluster does not provide an uninterrupted history; configuration and history files are stored on a local drive and, therefore, are not shared with the new quorum owner after a Cluster Group failover automatically replicates the configuration information to all the nodes in the cluster does not require a computer that resides outside of the cluster to run the CLA allows the KM to use the PATROL agent default account when certain requirements are satisfied easier to set up and configure
68
Figure 2
Cluster 1 Node 1
Install the PATROL KM for Microsoft Cluster Server and a PATROL Console here. Cluster 2 Node 1 Cluster-level agent computer
Install the PATROL KM for Microsoft Cluster Server, PATROL Agent, and OS KM here. Node 2
Install the PATROL KM for Microsoft Cluster Server, and PATROL Agent here.
Install the PATROL KM for Microsoft Cluster Server, PATROL Agent, and OS KM here. Node 2
Install the PATROL KM for Microsoft Cluster Server, PATROL Agent, and OS KM here.
Install the PATROL KM for Microsoft Cluster Server, PATROL Agent, and OS KM here.
Cluster 1
Node 1 - quorum owner Install the Agent, MCS KM, and Microsoft Windows OS KM on all nodes in the cluster
Node 2
While the PATROL KM for Microsoft Cluster Server (MCS KM) is loaded on all of the agents on all of the nodes in the cluster, only the MCS KM on the quorum-owning node actively monitors the cluster.
Chapter 2
69
know the user name and password of the cluster connection account installed the PATROL KM for Microsoft Windows OS and loaded the
NT_BASE.kml
Installation process
The PATROL KM for Microsoft Cluster Server installation process consists of the following tasks:
WARNING
Do not load the PATROL KM for Microsoft Cluster Server on a virtual agent.
PATROL Agent PATROL KM for Microsoft Cluster Server PATROL KM for Microsoft Windows
70
2 This task is only required if you are using an external CLA. Install the following
components on each computer that contains an external cluster-level agent:
I I
3 Install the PATROL KM for Microsoft Cluster Server on the computer that has
your PATROL Console. This component can exist on the same computer as the external cluster-level agent or on a cluster node.
Browser version required for viewing PATROL Console for UNIX Help
The appropriate one of the following browsers is required to view PATROL Help in PATROL version 3.x:
I I
UNIX: Netscape Navigator version 3.01 through 4.78 Red Hat Linux: Netscape Navigator version 4.x
Installation requirement
You must install Netscape Navigator on the computer where the PATROL console resides. You can install Netscape anywhere on your UNIX computer as long as the binary is in the path.
Download location
Netscape Navigator is supplied by Netscape Communications Corp. You can locate the browser at http://home.netscape.com/download.
Chapter 2
71
Netscape Navigator displays warning messages when it is invoked multiple times within the same user account because of its file-locking mechanism. It will, however, continue functioning. By default, when Netscape Navigator starts, it uses a private color map. As a result, you might experience color flashing on your workstation. If so, you can set the value of PATROL_BROWSER so that the colormap option is not specified. However, some subsequent color requests might fail and the online Help will be improperly displayed. The Exceed for Windows product by Hummingbird Communication Ltd. may not always display the Help files properly.
Consult your Netscape Navigator documentation for specific platform requirements and restrictions.
LANG variable
The UNIX LANG environment variable must be set to C so that Netscape Navigator will work properly. Otherwise, you might experience product failures.
Type of shell Bourne Korn C Export command for LANG variable LANG=C export LANG export LANG=C setenv LANG=C
72
PATH variable
The PATROL user account PATH variable must contain the location of the directory containing the Netscape files. If the directory containing the Netscape files is not in the path, add the directory to the PATROL user account path. This requirement applies only to the PATROL user account on the PATROL console computer.
Type of shell Bourne Korn C Export command for PATH variable PATH=$PATH:/netscape_location export PATH export PATH=$PATH:/netscape_location setenv PATH=$PATH:/netscape_location
PATROL_BROWSER variable
When PATROL starts the Help browser, it uses the command in the PATROL_BROWSER environment variable. As a default, the PATROL_BROWSER environment variable contains the following command:
Type of shell Bourne Korn C Export command for PATROL_BROWSER variable PATROL_BROWSER=netscape -display $DISPLAY -install -iconic export LANG export PATROL_BROWSER=netscape -display $DISPLAY -install iconic setenv PATROL_BROWSER=netscape -display $DISPLAY -install iconic
To use different arguments, set the value of PATROL_BROWSER to the appropriate string.
EXAMPLE
For a Korn shell: export PATROL_BROWSER=/usr/local/bin/netscape -raise
Chapter 2
73
WARNING
If you use a different version of the installation program to uninstall the product than the version that you used to install the product, you might remove files that are needed to perform uninstallation of other BMC Software products.
74
To uninstall individual products 1 From the Uninstall directory in your BMC Software product installation directory,
double-click uninstall.exe to launch the installation utility in uninstall mode.
NOTE
As an option, you can launch the installation utility in uninstall mode by choosing Start => Settings => Control Panel => Add/Remove Programs and double-clicking BMC Software Tools in the Add/Remove Programs Properties dialog box.
When installing on a Windows Server in application mode or with Citrix Metaframe installed, perform the following steps to launch the installation utility in uninstall mode:
A From a command line, change to the directory where the installation utility is
located and enter the following command to change to installation mode:
change user/install
B Change to the Uninstall directory and enter the following command to start the
installation Web server:
uninstall.exe -serveronly
A message box is displayed that shows the URL to use to connect to the installation Web server.
C On another machine with a browser, start the browser. D Connect to the installation Web server from the browser to start the installation
utility by using the URL that is displayed in the message box. The Welcome window is displayed. Click Next.
2 Select the installation directory from which you want to remove a product, and
click Next.
3 Select the product or products that you want to uninstall, and click Next. 4 Review your selections and click Uninstall.
After the uninstallation is complete, a window is displayed that tells you whether the uninstallation was successful.
Chapter 2
75
3 Open the uninstall.ctl file in a text editor, and edit the /BMC/Base variable to specify
the name of the directory from which you removed the products in step 1.
Use the following table to help determine the log file and output log file locations:
Option -log Description sends the log information to a standard log file This file contains all installation status information. -output sends the log information to an output log file Value any valid path and file name (with a .txt extension) If a space exists in the path, the entire path must be enclosed in quotation marks. any valid path and file name (with a .txt extension)
This file contains all messages about the If a space exists in the path, the entire path must be enclosed in quotation progress of the installation that are marks. normally sent to standard output.
76
Example
If C:\Program Files\BMC Software is your product installation directory, you would change to the C:\Program Files\BMC Software\Uninstall\ Install\instbin directory and enter the following command:
thorinst.exe -uninstall C:\Program Files\BMC Software\Uninstall\Install\instdata\uninstall.ctl -log Z:\NetworkLogs\MyLogs.txt -output Z:\NetworkLogs\MyLogs.out
This action would remove all installation files and directories except those that are used by the utility at the time the uninstallation was performed. Log files, configuration files, and user-modified files would also be retained.
3 Open the uninstall-all.ctl file in a text editor, and edit the /BMC/Base variable to
specify the name of the directory from which you removed the products in step 1.
Chapter 2
77
Use the following table to help determine the log file and output log file locations:
Option -log Description Value
sends the log information to a standard any valid path and file name (with a .txt extension) log file This file contains all installation status information. If a space exists in the path, the entire path must be enclosed in quotation marks. any valid path and file name (with a .txt extension)
-output
This file contains all messages about the If a space exists in the path, the entire progress of the installation that are path must be enclosed in quotation normally sent to standard output. marks.
Example
If C:\Program Files\BMC Software is your product installation directory, you would change to the C:\Program Files\BMC Software\Uninstall\ Install\instbin directory and enter the following command:
thorinst.exe -uninstall C:\Program Files\BMC Software\Uninstall\Install\instdata\uninstall-all.ctl -log Z:\NetworkLogs\MyLogs.txt -output Z:\NetworkLogs\MyLogs.out
This action would remove all installation files and directories. The files that were used to perform the uninstallation will be marked for deletion and will be removed when the computer on which the products were uninstalled is rebooted.
78
setting up and configuring PATROL for Chapter 3, Loading and configuring PATROL for Windows Servers Microsoft Windows Servers, and PATROL for Windows Servers component online Help instructions about how to access the KM menu commands, InfoBoxes and online Help information about PATROL for Windows Servers configuration variables and predefined rulesets listing of the KM included with each PATROL for Windows Servers component step-by-step procedures and detailed descriptions of the applications, parameters, and InfoBoxes Appendix A, Accessing menu commands, InfoBoxes, and online Help Appendix B, Agent configuration variables and rulesets Appendix C, PATROL for Microsoft Windows Servers .kml files PATROL for Windows Servers component online Help
Chapter 2
79
80
Chapter
This chapter provides information about how to begin using and configuring the PATROL for Microsoft Windows Servers components. The following topics are discussed in this chapter: Preparing to use PATROL for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Determining which KMs to load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Determining which KMs to preload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Loading the PATROL for Microsoft Windows Servers KMs . . . . . . . . . . . . . . . . . 85 Preloading KMs on the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Using wpconfig to remove KMs from the Agent preload list . . . . . . . . . . . . . . . . 89 Requirements for configuring from the PATROL Console. . . . . . . . . . . . . . . . . . . 91 Configuring the PATROL KM for Microsoft Windows OS. . . . . . . . . . . . . . . . . . . . . . 95 Enabling and disabling system monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Configuring Windows events monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Configuring service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Configuring process monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Creating custom parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Viewing event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Configuring recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 About recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Built-in native recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Configuring built-in native recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Configuring e-mail notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Using notification scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Defining notification servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Assigning notification servers for the remote agents. . . . . . . . . . . . . . . . . . . . . . . 128 Assigning notification targets for a PATROL alert. . . . . . . . . . . . . . . . . . . . . . . . . 130 Configuring the PATROL KM for Microsoft Active Directory . . . . . . . . . . . . . . . . . . 131 Creating new parameters with the PATROL Wizard for Microsoft Performance Monitor and WMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Loading the PATROL Wizard for Microsoft Performance Monitor and WMI . 132 Creating performance monitor parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Creating WMI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Chapter 3 Loading and configuring PATROL for Microsoft Windows Servers 81
Configuring the PATROL KM for Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Stop and start monitoring all default log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Stop monitoring a log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Start monitoring a log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Change the setup of a monitored file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Filter log file messages (create a search string) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Generate a custom event when a search string is identified . . . . . . . . . . . . . . . . . 142 Configure recovery actions for a log file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Configuring the PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . 145 To configure the PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . 146 Using the PATROL Adapter for Microsoft Office to view reports . . . . . . . . . . . . . . . 147 Displaying PATROL data by using the PATROL Adapter for Microsoft Office 147 How to use the PATROL Adapter for Microsoft Office . . . . . . . . . . . . . . . . . . . . . 148 Built-in report templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Unloading KMs from a PATROL console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Stopping preloaded KMs from running on the PATROL Agent . . . . . . . . . . . . . 154
82
If PATROL for Windows Servers has not been installed, see Chapter 2, Installing and migrating PATROL for Windows Servers. After installing, return to this section for information about how to configure the components. Before configuring the PATROL for Windows Servers components, you should verify that the following software requirements are met:
I
A supported version of a PATROL Console version 3.x and PATROL for Windows Servers must be installed on the computer you want to use for the PATROL Console. A supported version of the PATROL Agent and PATROL for Windows Servers must be installed on the computer you want to monitor and manage. If you are using PATROL Central Operator Microsoft Windows Edition or PATROL Central Operator Web Edition, the KMs that you want to use must be installed on the computer hosting the PATROL Console Server.
NOTE
For supported versions of PATROL products, see the release notes for the version of PATROL for Microsoft Windows Servers that you are installing.
You should also verify that you have access to all required information about the monitored domain controllers or Windows servers.
EXAMPLE
If you want to monitor the operating system, ensure that you have the PATROL Console and the PATROL KM for Windows OS installed on the console machine and the PATROL Agent and the PATROL KM for Windows OS installed on the agent machine.
83
Loading the PATROL for Microsoft Windows Servers KMs on page 85 Preloading KMs on the PATROL Agent on page 88
Table 16
.kml file COM.kml
84
Table 16
.kml file
MWD_ACTIVE_Dire PATROL KM for Windows Active ctory_MN.kml Directory NTD.kml MCS_Load.kml PATROL KM for Windows Domain Services
PATROL KM for Microsoft Cluster Server loads application classes that are used to monitor Microsoft server clusters loads application classes that are required to use the PATROL PerfMon and WMI Wizard loads application classes required to configure alerts, such as e-mail or paging notifications loads application classes required to configure log monitoring
NT_PERFMON_WIZ PATROL Wizard for Microsoft ARD.kml Performance Monitor and WMI EVENT_MANAGEM PATROL KM for Event Management ENT.kml LOG.kml PATROL KM for Log Management
I I
the components that you want to load on the agent and console computers are installed the agents to which you want to load components are running the PATROL Console is running
To load KMs on the PATROL Console for Windows Servers 1 Choose File => Load KM from the PATROL Console menu bar. 2 Select one or more of the .kml files in Table 16 on page 84 that correspond to the
components that you want to load. For detailed information about the application classes that are loaded with these .kml files, see PATROL for Microsoft Windows Servers .kml files on page 244.
3 Click OK.
85
NOTE
If you have installed PATROL KM for Microsoft Windows OS over a previous version, the first time you load the KM, several minutes may be required to migrate forward existing configuration settings. If the KM icons do not appear within 10 minutes, open and read the information in the PATROL system output window.
NOTE
Unless you are an advanced PATROL user, use the .kml files to load product component files. Loading individual .km files can break the interdependencies between the .km files.
To load the KM on a PATROL Console for UNIX 1 Choose File => Load KM from the PATROL Console menu bar. 2 Select one or more of the .kml files in Table 16 on page 84 that correspond to the
components that you want to load. For detailed information about the application classes that are loaded with these .kml files, see PATROL for Microsoft Windows Servers .kml files on page 244.
NOTE
Unless you are an advanced PATROL user, use the .kml files to load product component files. Loading individual .km files can break the interdependencies between the .km files.
To load the KM on PATROL Central Operator - Windows Edition 1 In the Common Tasks tab of the Operator Console Module Taskpad, click the Load
Knowledge Module(s) icon.
86
3 From the Managed System screen, select the managed system that you want to
load KMs on.
4 From the Knowledge Modules screen, select the KMs that you want to load. For
detailed information about the application classes that are loaded with these .kml files, see PATROL for Microsoft Windows Servers .kml files on page 244.
5 Click Finish.
The KMs that you selected are loaded on the managed system, added to your management profile, and displayed in the PATROL Central Operator tab.
1 From the Monitored Systems page, click the Load/Unload KMs button.
The Load KMs page opens, listing each computer on which a PATROL Agent has been installed.
2 Select the computers on which you want to load KMs, and click Next.
The Load KMs page displays a list of available .km and .kml files. If you selected more than one computer, the only .km and .kml files that are listed are the ones that have been installed on all of the selected computers. If a particular .km or .kml file was installed only on one computer, you must choose that computer by itself to load the file.
3 Select the .km or .kml files that you want to load. 4 Click Finish.
PATROL loads the selected KMs on the selected computers.
NOTE
If you want to load a .km or .kml file that was not listed in Step 2, ensure that the KM is installed on the appropriate computer and select only that computer in Step 2.
87
use the PATROL Configuration Manager to apply one of the predefined rulesets to the PATROL Agent (see PATROL for Microsoft Windows Servers rulesets on page 219) using the wpconfig or xpconfig utility
The PATROL Agent must be running. The wpconfig utility must be installed on a computer that can access machines that are running the PATROL Agent over the network. You must have permission to modify the configuration change file (.cfg).
To use wpconfig to preload a KM from the PATROL Console for Microsoft Windows 1 From a Windows command window, type wpconfig.
The wpconfig window is displayed.
3 In the Host Name field, enter the name of a computer that is hosting the PATROL
Agent and click OK. The wpconfig utility gets the PATROL Agents configuration.
88
5 Scroll down the variable list and double-click the preloadedKMs variable.
The Modify Variable dialog box is displayed.
7 In the Type field, leave REPLACE. 8 In the Value field, use the comma-separated format without spaces to type the
names of the .kml files that you want to preload. See Appendix C, PATROL for Windows .kml files for a list of the KMs that are available in this product. For example, a valid and typical preloaded KMs list is as follows:
NT_BASE.kml,COM.kml,NT_PERFMON_WIZARD.kml
9 Click OK.
The Change Entry dialog box closes.
10 In the Modify Variable dialog box, click OK to close the box. 11 From the Tools menu, choose Apply Configuration.
The Apply Configuration dialog box is displayed, listing the PATROL Agent host name to which you are connected.
12 Click OK to apply your updated configuration to the PATROL Agent. 13 Save your changes to the configuration change file by clicking the Save button. 14 Close the wpconfig window.
89
The PATROL Agent must be running. The wpconfig utility must be installed on a computer that can access machines that are running the PATROL Agent over the network. You must have permission to modify the configuration change file (.cfg).
To use wpconfig to remove a KM from the preload list in the PATROL Console for Microsoft Windows 1 From a Windows command window, type wpconfig.
The wpconfig window is displayed.
3 In the Host Name field, enter the name of a computer hosting the PATROL Agent
and click OK. The wpconfig utility gets the PATROL Agents configuration.
5 Scroll down the variable list and double-click the preloadedKMs variable.
The Modify Variable dialog box is displayed.
7 In the Type field, leave REPLACE. 8 In the Value field, delete the .kml file names that you want to remove from the
preload list. See Appendix C, PATROL for Windows .kml files for a list of the KMs that are available in this product.
9 Click OK to close the Change Entry dialog box. 10 Click OK to close the Modify Variable dialog box.
90
12 Click OK to apply your updated configuration to the PATROL Agent. 13 Save your changes to the configuration change file by clicking the Save button. 14 Close the wpconfig window.
is a member of the local Administrators group on the agent computer has the right Log on as a Batch Job assigned
If the console connection account does not meet these requirements, the features described in Table 17 are not available. Table 17
KM PATROL KM for Microsoft Active Directory
91
Table 17
KM
PATROL KM for Running an Windows Domain availability report Services with the Remote Servers KM Running a Server Information report with the Remote Servers KM Displaying information about a user using the Users KM Stopping or Starting the WINS service
92
Table 17
KM
PATROL KM for Starting or stopping Windows Domain the DFS Replica Services, continued service Disconnecting DFS users
93
Table 17
KM
Viewing application properties PATROL KM for MSMQ Starting or stopping the MSMQ service
94
configure service monitoring From the PATROL Console, access the Services application and choose the KM menu command Configure Service Monitoring. configure process monitoring configure built-in recovery actions create custom parameters From the PATROL Console, access the Processes application and choose the KM menu command Configure Manual Process Monitoring.
107
109
From the PATROL Console, access the host application and 120 choose the KM menu command Configure Recovery Actions. From the PATROL Console, access the CompositesColl application and choose the KM menu command Create Expressions. From the PATROL Console, access the Windows Event application and choose the KM menu command Windows Event Viewer. 115
115
95
Monitored by default
all processors discovered on the From the PATROL Console, access the Processors application system and choose the KM menu command Enable-Disable Processor Monitoring. all physical disks discovered on From the PATROL Console, access the Physical Disks the system application and choose the KM menu command Enable-Disable Physical Disk Monitoring. all logical disks discovered on the system From the PATROL Console, access the Logical Disk application and choose the KM menu command Enable-Disable Logical Disk Monitoring. To monitor logical disks, PerfMon counters must be enabled. For more information, see Monitoring logical or physical disk drives.
pagefiles
all pagefiles discovered on the system all event logs listed in the registry
From the PATROL Console, access the Pagefiles application and choose the KM menu command Enable-Disable Pagefile Monitoring. From the PATROL Console, access the Windows Events application and choose the KM menu command Enable-Disable Windows Event Log Monitoring. To monitor the security event log, the PATROL Agent default account must have the user right Manage auditing and security log.
event logs
all network protocols that are installed on the system all network interfaces discovered on the system all printers discovered on the system
From the PATROL Console, access the Network Protocols application and choose the KM menu command Enable-Disable Protocol Monitoring. From the PATROL Console, access the Network Interfaces application and choose the KM menu command Enable-Disable Network Interface Monitoring. From the PATROL Console, access the Printers application and choose the KM menu command Enable-Disable Printer Monitoring.
job objects
all job objects discovered on the From the PATROL Console, access the Job Objects application system and choose the KM menu command Enable-Disable Job Object Monitoring.
96
diskperf -yv for Windows 2000 (restart required) diskperf -y for Windows Server 2003 (no restart required)
For the platforms shown above, Microsoft requires that you restart the system after running the diskperf command. For more information, see Microsoft Knowledge Base article Q262937, PRB: RegQueryValueEx() May Not Return Disk Performance Counters.
Enable and disable monitoring of Windows events on page 98 Display events with unregistered sources on page 98 Example: creating an event filter to monitor WinMgmt events on page 99 Event filter options on page 99 Turning off an event filter on page 106
97
1 Using the Configure Windows Event Log Monitoring => Create Filter menu
command, create a new filter. In the Create Filter dialog box, select the Filter Property - Source, and deselect the option to Automatically include new sources. This sets the following agent configuration variable to 0:
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config//EventLogMonitoring/eventlog/Ev entFilters/filtername/IncludeAllSources
2 Using PATROL Configuration Manager or the wpconfig utility, manually add the
unregistered event source to the following agent configuration variable.
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config//EventLogMonitoring/eventlog/Ev entFilters/filtername/SourceList/list
98
Error
WinMgmt
None
41
Error
WinMgmt
None
61
You want to be notified immediately when these particular events occur. However, you want to be notified only when the event is related to the perfproc.dll performance library, not any other performance counter libraries. In addition, you do not want to be flooded with events, so if these events are generated multiple times within a short period, you want to be notified only once. Finally, if these events are detected, you want PATROL to remain in alarm until the alarm is acknowledged by an operator. Using the Event filter options presented in the Configuring Windows Event Monitoring => Create Filter dialog boxes, you can create a filter with all of the properties proposed in this example.
99
Table 21
Option
Filter name
Description
A description of the event filter. You can change the description at any time.
Report the number If you select this option, PATROL monitors the number of of events.... events that match the filter criteria during each collection cycle. Depending on which event types the filter monitors, the following parameters are used to report this data:
I I I I I I I
EventReport
NA If you select this option, PATROL immediately updates the appropriate parameter when an event matches the filter criteria. Depending on which event types the filter monitors, the following parameters are displayed in an alarm state when an event matches the filter:
I I I
ELMErrorNotification ELMFailureAuditNotification ELMNotification (This parameter is active only when you have selected both of the following options: Notify immediately and consolidate event types. For more information, see the description in Event Type tab section of this table.) ELMWarningNotification
For more information about these parameters, see the PATROL KM for Microsoft Windows OS online Help. Source filter properties Source Select/Deselect source(s) for this filter Registered sources for which events can be monitored applications running on the server that PATROL is currently monitoring NA SourceList/list
100
Table 21
Option
Automatically Include New Sources Disable Case Sensitivity Select Event Types to monitor Consolidate event types...
If you select this option, this event filter automatically monitors IncludeAllSources any new applications that are added to the system If you select this option, the event filter makes filter comparisons FilterDisableCase in a case-independent manner the Windows event types monitored by this event filter If you select this option, events of different types (Warning, Information, and Error, for example) are reported using one parameter: ELMStatus (or ELMNotification if you have also chosen to be notified immediately when the event occurs). If you want to have separate parameters for each event type that can alarm independently, deselect this option. EventType ConsolidateEventTy pes
Event ID filter properties EventIdList/list Enter a Windows The Microsoft Windows event IDs that you want to monitor Event ID or a range with this filter. of IDs To specify a range of event IDs, separate the beginning and ending of the range with a dash. For example, to monitor events 100 through 200, enter 100-200. Include all specifies that all of the Windows event IDs in the list are Windows event IDs monitored by the event filter in the list IncludeAllEventIds
IncludeAllEventIds specifies that all of the Windows event IDs except those in the Include all Windows event IDs list are monitored by the event filter except those in the Select this option when there are certain event IDs that you are list not interested in monitoring and you want to exclude them from the event filter. Event Handling filter properties Annotate graph parameter... annotates the PATROL parameter graphs associated with this event filter with information about the event You can display the annotations by placing the cursor over the graph data points. Annotation
Chapter 3
101
Table 21
Option
EvRptOfError EvRptOfFailureAudit EvRptOfInformation EvRptOfStatus EvRptOfSuccessAudit EvRptOfWarning ELMRptOfOtherTypes ELMRptOfNotification (This parameter is active only when you have selected both of the following options: Notify immediately and consolidate event types. For more information, see the description in Event Type tab section of this table.)
For more information about these parameters, see the PATROL KM for Microsoft Windows OS online Help. Use event details... saves information about the event in the agent configuration variable RetainEventDescriptions so that you can use this information in recovery actions For example, if you create a recovery action that generates an e-mail when the event filter alarms, you could include the event description in the e-mail. If you do not use recovery actions or do not plan to use them, deselect this option to limit use of the agent database space. RetainEventDescripti ons
102
Table 21
Option
Chapter 3
103
Table 21
Option
Acnowledge Alarms
Automatically change state to OK ... If you select this option, PATROL returns the filter to an OK state if the events you are monitoring do not occur during the next collection cycle.
Remain in alarm until ... If you select this option, PATROL keeps the filter in alarm until an operator manually acknowledges the alarm.
Change state when the following event ... If you select this option, PATROL changes the filter state from an alarm state to an OK state when the criteria of a second event filter are met. Requirements for using: You must create an event filter that monitors for the required event and select that event filter from the drop-down list. In addition, the event filter must be configured to notify PATROL immediately when an event matches the filter criteria.
Advanced properties - Users UserList/list Enter the user the user ID of a user whose events you want to monitor associated with the event The user name cannot include commas. When entering a user whose name includes special characters that are used in regular expressions, such as a dollar sign ($), a period (.), a parenthesis (), or a slash (/), you must escape each special character with a slash. For example, if the user name is $Smith, you must enter the category as \$Smith. Include all users in specifies that all of the user IDs in the list are monitored by the the list event filter Include all users except those in the list specifies that all of the user IDs except those in the list are monitored by the event filter Select this option when there are certain user IDs that you are not interested in monitoring and you want to exclude them from the event filter. Disable Case Sensitivity If you select this option, the event filter makes filter comparisons FilterDisableCase in a case-independent manner IncludeAllUsers
104
Table 21
Option
Advanced properties -- Category Enter the category the event category that you want to monitor with this event associated with the filter event Categories are defined by the application that generates the event. The category name cannot include commas. When entering a category whose name includes special characters that are used in regular expressions, such as a dollar sign, a period, or a parenthesis, you must escape each special character with a slash. For example, if the category name is (100), you must enter the category as \(100\). Include all categories in the list Include all categories except those in the list specifies that all of the categories in the list are monitored by the IncludeAllCategories event filter specifies that all of the categories except those in the list are monitored by the event filter Select this option when there are certain categories that you are not interested in monitoring and you want to exclude them from the event filter. Disable Case Sensitivity Enter strings If you select this option, the event filter makes filter comparisons FilterDisableCase in a case-independent manner The text strings that you want to monitor with this event filter The text string cannot include commas. When entering strings which include special characters that are used in regular expressions, such as a dollar sign ($), a period (.), a parenthesis (), or a slash (/), you must escape each special character with a slash. For example, if the user name is $Smith, you must enter the category as \$Smith. Include all strings in the list Include all strings except those in the list specifies that all of the strings in the list are monitored by the event filter specifies that all of the strings except those in the list are monitored by the event filter Select this option when there are certain strings that you are not interested in monitoring and you want to exclude them from the event filter. Disable Case Sensitivity If you select this option, the event filter makes filter comparisons FilterDisableCase in a case-independent manner StringList/list IncludeAllStrings StringList/list IncludeAllCategories
Chapter 3
105
Table 21
Option
Advanced properties - Enter a Regular Expression for Source Enter a Regular Expression for Source
For example, if the sources are Norton AntiVirus Client or Symantec AntiVirus Client, the regular expression should be configured as ^(Norton|Symantec) AntiVirus Client.
For more information about using regular expressions, see Using regular expressions on page 110. Advanced properties - Enter a Regular Expression for Event ID Enter a Regular the regular expression that is used as a criteria for including or Expression for Event excluding event IDs to be monitored with the Windows event ID filter. If you have configured the event IDs for the filter and an event occurs, the event is matched with the configured event ID list. If the event ID does not exist in the configured list, the event ID is compared with the specified regular expression. For more information about using regular expressions, see Using regular expressions on page 110. EventIdList/list
To turn off an existing event filter 1 Using the PATROL Configuration Manager or the pconfig utility, access the
following agent configuration variable:
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config//EventLogMonitoring/ event log/EventFilters/filter/FilterEnabled
106
Startup type
To change the default settings for services, choose the Configure Service Monitoring menu command from a Services application instance to perform the following tasks:
I
To add services to the list of monitored services, choose the Configure Service Monitoring => Add Service menu command. To remove services to the list of monitored services, choose the Configure Service Monitoring => Remove Service menu command. To configure monitored services, choose Configure Service Monitoring => Configure Service menu command.
By default, the Windows KM monitors all services with startup type as automatic or manual.
I
If you want to monitor a disabled service, add the service by using the Configure Service Monitoring => Add Service menu command. The Monitor pconfig variable for the service is set to 1. If you add a disabled service and later remove the service by using the Configure Service Monitoring => Remove Service menu command, the Monitor pconfig variable is not set to 0. However, the removedServiceList pconfig variable is updated to contain this particular service.
Chapter 3
107
Thus, Windows KM monitors a service only if the Monitor pconfig variable for the service is set to 1 and the service is not included in the list of the removedServiceList pconfig variable.
Yes If you select this option, PATROL automatically attempts to restart the service when it is stopped (only for services with a startup type of Automatic). To use this option, you must also select the option Generate a PATROL Alarm/Warn when the service is stopped. Yes (Alarm) By default, when a service is stopped, PATROL generates an Alarm. However, for a particular service, you can specify a Warning instead. This feature is only for services with a startup type of Automatic. By default, PATROL monitors only whether services No are available. To monitor how much memory and CPU a service executable consumes, you must enable process monitoring for the service. When you enable process monitoring, PATROL monitors the service executable process and displays the monitored process beneath the NT_SERVICE application. This feature is available for advanced users who have No developed custom executables that can determine the status of a service. If you provide such an executable, the value returned by the executable is assigned to the SvcNotResponding parameter. To ensure that an alarm is generated when the service is not responding, you must set the alarm ranges for the SvcNotResponding parameter to correspond to the appropriate value returned by the executable. For example, if the executable returns the value 1 when the service is not responsive, enable the SvcNotResponding Alarm2 as an Alarm and set the alarm range as 1 to 1.
Generate a PATROL Alarm/Warn when the service is stopped Enable process monitoring for this service
WarningAlarm
MonitorProcess
MonitorNotResp ond
108
Service configuration variable DisableServiceRestart (global) AutoRestart (local) OverrideGlobalServiceRestart (local) Service is restarted? (yes/no)
For more information about these configuration variables, see Appendix B, Agent configuration variables and rulesets.
Chapter 3
109
literal character matching character repetition clause alternation clause sub pattern grouped with parenthesis
[]
delimits a set of characters; the range is specified as [x-y] If the first character in the set is ^, there is a match only when the remaining characters in the set are not present.
^ $
anchors the pattern to the beginning of the string; this character must be the first character in the set anchors the pattern to the end of the string; this character must be the last character in the set
To configure manual process monitoring 1 Access the NT_PROCESS application menu (labeled Processes) as described in
Accessing KM commands and InfoBoxes on page 186, and choose the KM menu command Configure Manual Process Monitoring => Add
2 Select (highlight) the process that you want to monitor or, if the process is not
currently running, enter the process name and any appropriate command-line arguments.
110
You can enter the process name using a regular expression. For more information about regular expressions, see Using regular expressions on page 110.
TIP
If you are specifying a process name and you want to ensure that only that specific process is monitored (and not other processes that have that process name as part of their name), use the ^ and the $ regular expression characters to enclose the process name, as shown below. ^processname$ For more information about using regular expression characters, see Using regular expressions on page 110.
NOTE
If you enter multiple regular expressions that match the same process, multiple process instances are created for that process.
WARNING
When entering the process name, omit the extension. For example, enter processname argument. Do not enter processname.exe. Example: svchost -k rpcss In addition, when entering a process whose name includes special characters that are used in regular expressions, such as a dollar sign ($), or a period (.), you must escape each special character with a slash. For example, if the process name is $abc.exe, you must enter the process name as \$abc.
monitor the process(es) only when it is running with the command line arguments shown monitor any occurrence of the selected process(es), regardless of the command-line arguments
4 Click Apply.
PATROL performs the following actions:
I
The processes you selected are removed from the list of running processes and are added to the list of monitored processes that are shown on the left pane of the Configure Process Monitoring window.
Chapter 3
111
The processes you selected are added to the PATROL console, beneath the NT_PROCESS application (labeled Processes). The PATROL Agent begins monitoring the process.
To configure how the process is monitored and managed, see To configure process control on page 113. You can also perform the following functions using the Configure Manual Process
Monitoring menu command:
I
To modify a monitored process, select Configure Manual Process Monitoring => Process Settings.
To configure automatic process monitoring 1 Access the NT_PROCESS application menu (labeled Processes) as described in
Accessing KM commands and InfoBoxes on page 186, and choose the KM menu command Configure Automatic Process Monitoring.
3 Click Apply.
When any process consumes high CPU for a period longer than what you specified, PATROL begins monitoring the process and adds the process to the PATROL console, beneath the NT_PROCESS application (labeled Processes).
If a problem occurs
If the Processes folder is not displaying or it does not contain any processes, see Event filter parameters not automatically acknowledged on page 175.
2 For the length of time specified for high CPU utilization, enter any negative
number.
3 Click Apply. To configure process control 1 Access the NT_PROCESS application menu (labeled Processes) as described in
Accessing KM commands and InfoBoxes on page 186 and choose the KM menu command Configure Process Monitoring.
2 From the Configure Process Monitoring window, select the monitored process that
you want to configure.
3 Select the appropriate options, described in Table 27 on page 113, and then click
Apply.
Table 27
Option
Restart the process using the specified command when the process is stopped Terminate the process when the process CPU% utilization exceeds the defined PATROL threshold
If you check this option, PATROL terminates the No process when it appears to be in a run away state. This state is defined by the following criteria:
I
TimeLimitForKillR unAwayProcess
the CPU% utilization exceeds the threshold specified by the agent configuration variable AlarmThreshold. For more information about this variable, see AlarmThreshold on page 191. the process exceeds this threshold for the specified length of time
When the process exceeds the threshold for the specified length of time, the process is terminated during the next collection cycle, whose scheduling is determined by the parameter PROCProcessColl. By default, PROCProcessColl collects data every 5 minutes.
Chapter 3
113
Table 27
Option
Generate a PATROL Alarm If you select this option, the PATROL Yes when the process is NT_PROCESS parameter PROCStatus enters an terminated alarm state when the process is terminated. Generate a PATROL Alarm If you select this option, the PATROL No when the process is started NT_PROCESS parameter PROCStatus enters an alarm state when the process is started.
114
To create custom parameters using the expression entry wizard 1 Access the NT_CompositesColl application menu as described in Accessing KM
commands and InfoBoxes on page 186, and choose the KM menu command Create Expressions.
2 From the Create Expressions dialog box, enter a name for the expression
(parameter).
3 Follow the instructions provided in the wizard. For more information, click the
Help button.
After you complete the wizard, the new composite parameter is displayed on the console beneath the NT_Composites application (labeled Composites).
Chapter 3
115
4 From the Select Event Range list, select the range for the number of events to
display. The details of the latest events are displayed in the Windows Event Viewer dialog box, as described in Table 28.
NOTE
For optimizing performance of event retrievals, the Windows Event Viewer dialog box displays a maximum of 100 events at a time. By default, the Windows Event Viewer dialog box retrieves the latest 100 events for the selected event type. If you select the range for the events, the Windows Event Viewer dialog box retrieves the latest events for the selected event type, based on the range.
5 To view details pertaining to a particular event, select the event in the Windows
Event Viewer dialog box and click View. Table 28
Field Type
Other
date of the event time stamp of the event application that triggered the event ID for the event category of the event user account from which the event is generated computer from which the event is generated
116
Chapter 3
117
Recovery action Backup and Clear Event Log (PATROL KM for Microsoft Windows OS) Start Windows Management Instrumentation Service Check (PATROL KM for Microsoft Windows OS) Clean Temporary Directories (PATROL KM for Microsoft Windows OS) Terminate Process (PATROL KM for Microsoft Windows OS) Restart Process (PATROL KM for Microsoft Windows OS)
NT_EVLOGFILES\ELMEvFileF Backs up the event log file reeSpacePercent and clears all events.
NT_HEALTH\WMIAvailability Restarts the WINMGMT service when PATROL determines that it is unavailable.
Yes
No
NT_PROCESS\PROCProcessor TimePercent
No
NT_PROCESS\PROCStatus
Attempts to restart the process. Note: The process is restarted under the PATROL Agent default account, even if the process was previously started under a different account.
Yes
NT_SERVICES\ServiceStatus
Yes
NT_REMOTE_SERVERS\MsPat Attempts to restart the Restarting a PATROL PATROL Agent on the Agent on a remote server rolAgentStatus remote machine after recovery action alarming for 2 collection cycles. (PATROL KM for Windows Domain)
No
118
Table 29
Recovery action Increase connections to DFS root recovery action (PATROL KM for Windows Domain)
NT_DFS_ROOT\DfsConnection Increases the connection Percent share limit to DFS Root after alarming for 2 collection cycles.
NT_WINS_PARTNER\WpRepli Cleans up the WINS No Replication Failure: database after alarming for 2 Initiate WINS Scavenging cationFailures collection cycles. (PATROL KM for Windows Domain) Increase connections allowed to share (PATROL KM for Windows Domain) PAWorkRateExecsMin Recovery Action (PATROL KM for Microsoft Windows OS) NT_Shares\ShConnPercent Increases the share connection limit after the ShConnPercent parameter alarms for 2 consecutive collection cycles. No
PATROL_NT\PAWorkRateExec sets the scheduling policy sMin value to 9 (Schedule Force Delta and Schedule From End). When the parameter goes out of the alarm state, the scheduling policy value returns to the default value of 1.
Yes
Chapter 3
119
To configure recovery actions 1 Access the host application menu as described in Accessing KM commands and
InfoBoxes on page 186 and choose the KM menu command Configure Recovery
Actions.
2 From the list of recovery actions, highlight the desired recovery action and click
Accept.
3 From the list of recovery action instances, highlight the instance and click Edit. For
information about which instance to select, see Table 30. Table 30
Purpose configure the recovery action for a specific instance (for example, a monitored process)
configure the recovery action for all instances (for the recovery action that displays an example, all monitored processes) asterisk (*) in the INSTANCE column
4 From the Edit Recovery Action dialog box, choose from the settings described in
Table 31 on page 120. Table 31
Setting Run automatically
Run only with If you select this mode, PATROL prompts you operator confirmation before running the recovery action. Note: If you select this option, be sure to keep a console connected to the PATROL Agent on the managed machine. If you have no console connection, PATROL is unable to prompt you.
120
Table 31
Setting
If the recovery action is configured in Run Attended Wait mode, this setting specifies the amount of time PATROL waits for confirmation to run the recovery action. If you do not provide confirmation within the allotted time, PATROL does not run the recovery action.
NOTE
For more information about the recovery action and its configuration options, click the Help button.
NOTE
The PATROL KM for Event Management also provides you with the ability to configure other types of notification, such as trouble-tickets or other custom alerts. You can also use it to forward events to an enterprise console. For more detailed information about the functionality provided by the PATROL KM for Event Management, see the PATROL KM for Event Management User Guide.
1. Define the notification script and edit as necessary. 2. Define the notification servers. 3. Assign notification servers to the remote agents. 4. Define notification targets for PATROL alerts.
a Windows batch file that you must edit before use, which can send any of the following types of notification: SMTP e-mail message by means of a Visual Basic (VB) script (provided) MAPI e-mail message by means of a Visual Basic (VB) script (provided) SMTP e-mail message by means of Blat (not provided) Blat is a free command-line e-mail client, that you can download from the Web. You can also use any other SMTP-based, command-line e-mail client if you edit the batch file accordingly. For more information, see Editing scripts on page 124.
NOTE
The PATROL for Microsoft Windows Servers has been tested with Blat version 1.7.
122
Table 32
Script
MAPI VB Script
send_mapi.vbs This VB script is called from AS_EVSLocalAlertNotify.bat. This script uses an ActiveX control.
Perl Script
AS_EVSLocalAlertNotify.pl
Script requirements
To use these Windows scripts, the server sending the notification must meet the requirements shown in Table 33 on page 123. Table 33
Script Batch File Script
Perl Script
Chapter 3
123
Editing scripts
Before using the sample scripts, you must edit them.
If you use a third-party command-line e-mail client or if you want to use the script to perform other types of notification, such as paging or trouble tickets, you must add the code to the script that calls the e-mail client or appropriate notification utility.
124
' Enter the Mail Server name [FQDN/IP Address] iConf.Fields("http://schemas.microsoft.com/cdo/configuration/smtpserver") ="mail.bmc.com" ' Enter the SMTP Server Port number iConf.Fields("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
which servers will send notifications (act as notification servers) to whom e-mail or paging notifications are sent (targets) which servers will monitor the notification servers for availability which notification servers will be monitored for availability where to place notification rules (notification server or monitored agent)
Once you have configured a primary and backup notification server, you can use the PATROL Configuration Manager to copy the settings to the other notification servers. If you use this method, make sure that you use the same notification script file name and directory path on all notification servers.
Providing security
To improve security, create an operating system account on the notification server systems to be used specifically for remote notification. This configuration avoids having to use the PATROL login, which may be common throughout your environment. You can configure the notification server so that it is unable to fully login to the notification server system by using the operating system. For example, on UNIX, give the notification server login an invalid login shell, such as /bin/false.
To configure a notification server 1 From the PATROL console, access the managed system you are using as your
notification server and display the KM menu commands as described in Accessing KM commands and InfoBoxes on page 186.
126
3 Use the Quick Config - Notification Server dialog box to specify the notification
server properties. These properties are described in Table 34: Table 34
Property Default Email Account
the complete path and filename of the notification script or command used to send notifications specifies whether you want to perform an alert test after the changes are accepted If this is your first time using the PATROL for Microsoft Windows Servers, you should perform an alert test and verify that the notifications are received.
4 Define the notification server properties and click Accept. 5 Repeat this task for the server you are using as the backup notification server.
Chapter 3
127
NOTE
Notification servers are not required. Remote agents can send their own notifications. However, there are considerable benefits to using notification servers. For more information, see Why use a notification server? on page 125.
NOTE
You must use the PATROL KM for Event Management to complete this task. This functionality is not available in PATROL Configuration Manager. However, once you configure one notification server, you can use the PATROL Configuration Manager to copy your configuration to other notification servers. The configuration settings are stored in the following variables:
I I I I
To assign notification servers to remote agents 1 From the PATROL console, access the remote agent menu commands, as described
in Accessing KM commands and InfoBoxes on page 186.
2 Choose the KM menu command Event Management => Quick Config => Remote
Agent.
4 Use the Primary Notification Server Settings dialog box to specify the properties of
the primary notification server for the managed system. The properties are described in Table 35 on page 129.
128
Table 35
Property
Notification Server Hostname the hostname or IP address of the primary notification server for the selected managed system To avoid DNS resolution problems, use the IP address. Notification Server Agent Port Notification Server User Name the port number of the notification server that the selected managed system will use the user name that the selected managed system will use to connect to the notification server
Notification Server Password the password that the selected managed system will use to connect to the notification server Verify Password Make Connection Persistent verify the password that the selected managed system will use to connect to the notification server indicates that the remote agent maintains a persistent connection with the notification server agent so that the remote agent does not need to create a new connection each time it sends an event to the notification server
5 Define the primary notification server properties, and click Accept. 6 Click BACKUP NOTIFICATION SERVER SETTINGS.
Use the Backup Notification Server Settings dialog box to specify the properties of the backup notification server for the managed system. The properties are described on Table 35.
7 Enter the backup notification server properties, and click Accept. 8 Repeat this task for each remote agent.
Use the PATROL Configuration Manager to quickly configure all remote agents at one time. See the PATROL Configuration Manager User Guide for more information about the PATROL Configuration Manager.
Chapter 3
129
To assign notification targets 1 From the PATROL console, access the host KM menu commands, as described in
Accessing KM commands and InfoBoxes on page 186.
2 Choose the menu command Event Management => Alert Settings => Notification
Targets => Email => Local Targets ANY STATUS => Set For Parameters.
3 Select the application class of the parameter and click Accept. 4 Select the application instance of the parameter and click Accept. 5 Select the parameter and click Accept. 6 Enter the e-mail address of the target for this alert and click Accept.
You can set other types of notification targets using the same procedure, but you choose a different menu command in Step 2. For example, Paging instead of Email.
If a problem occurs
If you have problems configuring e-mail notification, see the PATROL KM for Event Management User Guide. This document contains detailed configuration instructions, usage scenarios, and troubleshooting information.
130
replication context names of the domain controllers that failed to replicate or that did not replicate in a timely manner
For example:
Replication Context: CN=Configuration,DC=cookies,DC=inc Domain controllers that failed to replicate data to the local domain controller: chocolate.factory.cookies.inc lemon.factory.cookies.inc pecan.cookies.inc
Replication Context: DC=factory,DC=cookies,DC=inc Domain controllers that failed to replicate data to the local domain controller: lemon.factory.cookies.inc
Chapter 3
131
Creating new parameters with the PATROL Wizard for Microsoft Performance Monitor and WMI
Creating new parameters with the PATROL Wizard for Microsoft Performance Monitor and WMI
The PATROL Wizard for Microsoft Performance Monitor and WMI allows you to quickly create your own parameters based on Microsofts Performance Monitor (PerfMon) counters or Windows Management Instrumentation (WMI) data. You may want to create a new parameter if you are interested in monitoring something for which no PATROL parameter currently exists. The tasks associated with the PATROL Wizard for Microsoft Performance Monitor and WMI are listed in Table 33 on page 123. Table 36
Task Loading the PATROL Wizard for Microsoft Performance Monitor and WMI Creating performance monitor parameters Setting alarm thresholds Creating WMI parameters
Loading the PATROL Wizard for Microsoft Performance Monitor and WMI
Before you can create new parameters by using the PATROL Wizard for Microsoft Performance Monitor and WMI, you must load the KM files on your PATROL console. Load the NT_PERFMON_WIZARD.kml file as described in the Loading the PATROL for Microsoft Windows Servers KMs on page 85. The Performance Monitor Wizard and WMI Wizard application icons appear in the console.
NOTE
After you have created new parameters on a particular PATROL Agent, other PATROL console users will not be able to see the new parameters that you created until they load the NT_PERFMON_WIZARD.kml file.
132
Creating new parameters with the PATROL Wizard for Microsoft Performance Monitor and WMI
2 Choose the Create Parameter menu command to display the Create Performance
Monitor Parameter dialog box.
3 From the Select Performance Object to monitor dialog box, choose a Performance
Object from the list, and click Next.
Counters and instances for the selected performance object display in the Available Counters and Available Instances tables.
4 Select the counters you want to monitor from the Available Counters table by
clicking the counter names. Selected counters appear highlighted.
5 Select the instances you want to monitor from the Available Instances table by
clicking the instance names. Selected instances appear highlighted.
6 Click Create to display the Select Performance Object to Monitor dialog box. 7 Click Done to create the parameters.
The dialog box closes and PATROL creates your new parameters. If you want to create new parameters over again, click Next. Continue with step 3.
Chapter 3
133
Creating new parameters with the PATROL Wizard for Microsoft Performance Monitor and WMI
2 For the parameters that need thresholds, perform the following actions:
I I I I
Type the lower-bound warning value in the Warning Minimum field. Type the upper-bound warning value in the Warning Maximum field. Type the lower-bound alarm value in the Alarm Minimum field. Type the upper-bound alarm value in the Alarm Maximum field.
3 Click OK.
If a problem occurs
When monitoring a Performance Monitor counter whose value is normally less than 1, you cannot specify meaningful alarm ranges since alarm ranges must be integers. However, you can customize the parameter so that the value displayed in PATROL is an integer. For more information, see Recovery actions do not execute on page 182.
2 Choose the Create Parameter menu command to display the Create WMI Parameter
dialog box.
3 Type a name for the WMI-based parameter you want to create in the Parameter
Name field.
4 Type a valid select statement in the Please Enter a WQL Query field.
The query must return a numerical value.
EXAMPLE
select NumberOfProcesses from Win32_OperatingSystem or select CurrentSize from Win32_Registry
134
5 Click Next to set alarm thresholds for the parameter that you are creating.
The Set Alarm Thresholds dialog box is displayed.
Type the lower-bound warning value in the Warning Minimum field. Type the upper-bound warning value in the Warning Maximum field. Type the lower-bound alarm value in the Alarm Minimum field. Type the upper-bound alarm value in the Alarm Maximum field.
7 Click Create to create the parameter according to the SQL Query that you entered
and close the dialog box.
If the PATROL KM for Microsoft Windows OS is loaded and the PATROL KM for Log Management is loaded, the PATROL KM for Log Management will begin collecting data immediately. For each log file, the KM monitors the following attributes:
I I I I
file size - stored in the LOGFileSize parameter growth rate - stored in the LOGGrowthRate parameter content age
Chapter 3
135
The default list of monitored files may be added to or removed completely depending on your needs. The PATROL KM for Log Management supports the following four types of files:
I
Text Files Text files are only read if they have been modified since the last scan. Command Scripts Command scripts are executed each scan cycle and the resulting output is treated as a log file. Named Pipe (or FIFO) Named pipes are opened and kept open for reading. Only blocking pipes are supported. The data is read from the pipe a line at a time and accumulated in a secondary log file. This secondary file is treated like a normal log file. Binary Files Binary files are read with the use of a user-specified filter program. Binary files are only read if they have been modified since the last scan.
This section describes how to configure the PATROL KM for Log Management so you can begin monitoring log files in your environment. The following table lists the topics covered in this section. Task
Stop and start monitoring all default log files Stop monitoring a log file Start monitoring a log file Change the setup of a monitored file Filter log file messages (create a search string) Generate a custom event when a search string is identified Configure recovery actions for a log file
Page
136 137 137 139 140 142 144
136
3 To stop monitoring the default log file, deselect the Enable Default Log File
Monitoring checkbox.
NOTE
The Default Monitoring dialog box only enables and disables monitoring for the log files that the PATROL KM for Log Management monitors by default. This dialog box does not control monitoring for log files that you add to the list of monitored files. To add or remove log files to the list of monitored files, see Start monitoring a log file on page 137 and Stop monitoring a log file.
3 From the List of Monitored Files, select the log files that you no longer want to
monitor.
3 In the File Label field, enter a label for the log file that you want to start monitoring
The log icon label must be 20 characters or less and cannot contain any spaces.
Chapter 3
137
5 In the File Path field, enter the full path and file name for the log file you want to
monitor.
NOTE
To monitor log files that have dynamic names, use the * and ? wild card characters in the file label. For example, if a log file is named backup_date.log, where date changes each day, enter the log file name as backup_*.log. However, if you are entering the label of a named pipe, regular expression characters are not supported.
6 In the Search String area, configure a search string to define what type of messages
the KM should search for. When the search string is identified, the KM generates an alarm. For more information about configuring search strings, see Filter log file messages (create a search string) on page 140.
7 From the Filter Type area, select the radio button that corresponds to the type of log
file that you want to monitor.
8 If you are monitoring a binary log file, enter the name of the program that
translates the file to ASCII text in the Filter Program field. If you specify a filter program, PATROL periodically dumps the log file into the program for scanning.
9 If desired, configure automatic recovery actions for a log file to determine how the
KM should respond when the file reaches a defined size. For more information about configuring recovery actions for a log file, see Configure recovery actions for a log file on page 144.
10 From the Scan Priority drop-down list, select a scan priority: Normal, High, or Low. 11 Click Apply.
A confirmation dialog box is displayed that lists the log file name and path. The dialog box asks if you want to add the file to the list of monitored log files.
138
12 If you do not want to add any more log files to be monitored, click Close.
PATROL displays the Log Files dialog box with the new log file name in the List of Monitored Files area.
13 Click Close.
2 Select Manage List of Monitored Files. 3 From the list of monitored files, select the log file for which you want to adjust the
setup options.
4 Select the Change radio button and click Apply. 5 Make any desired changes to the setup options for the selected log file. 6 Click Apply.
A confirmation dialog box is displayed that lists the log file name and path. The dialog box asks if you want to change the file.
7 Click Close.
PATROL displays the Log Files dialog box and updates the changes you have made to the log file monitoring setup.
8 Click Close.
Chapter 3
139
text string or pattern numeric values number of string matches per scan of the log file corresponding alert severity (OK, WARN, or ALARM) when the specified string or pattern is found
String attributes
The search string can consist of one or two regular expressions and/or a numeric comparison. The results of these criteria are combined to determine a match. The maximum length for a string is 400 characters.
If you are adding a new log file to be monitored, follow the steps in Start monitoring a log file on page 137. If you want to define a search string for an existing log file, follow the steps in Change the setup of a monitored file on page 139.
140
1 In Add File for Label dialog box or the Change File for Label dialog box, enter a
search string or regular expression in the String 1 field. Select the NOT checkbox next to the String 1 field if you want to identify log file entries in which the string is not found. You can search for a literal word or phrase or you can use regular expressions to search for a type of message that has an identifiable format or pattern.
2 If desired, in the String 2 field, enter a search string or regular expression. Select the
NOT option button next to the field if you want to identify log files in which the string is not found.
less than, < greater than, > equal, = less than or equal, <= greater than or equal, >=
Chapter 3
141
4 Fill out or modify the rest of the dialog box fields as described in Start monitoring
a log file on page 137.
1 In the First number field, enter 500. 2 From the Op drop-down list to the right of the First number field, select <. 3 In the Begin token field, enter 5. 4 In the End token field, enter 7.
The completed Search String section appears.
Event class LOGGeneral Event type WARN Event severity 3 Event origin LOGMON.inst.fname, where inst is the user-defined label of the log file and fname is the log file name.
Text entered in the Custom Event Message field can also be included in the event. Part or all of the matching log entries can be included in the custom event message.
142
The words of the message (represented by tokens separated by white space) will be identified by their ordinal position in the matched log file line, numbered left to right starting with 1. Word substitution will be identified in the custom event message text by using the % character. Ranges of words can be included, and are entered following a single % (for example, %2-5 would identify tokens 2 through 5 inclusive).
NOTE
If you want to have the % character appear in the message, enter %%. For example, entering Disk %3 is %5 %% full displays the 3rd and 5th strings in the match line, such as Disk /dev/sd0 is 45 % full.
For example, you might want to create a custom event message that would display when a service fails to initialize. To see how you would set up a custom event message for this example, see Example: defining a search string for print queue length on page 142.
NOTE
If you do not create a custom event message, you will still receive the standard event generated by the LOGErrorLvl parameter when your search string is found.
If you are adding a new log file to be monitored, follow the steps in Start monitoring a log file on page 137. If you want to set up a custom message for an existing log file, follow the steps in Change the setup of a monitored file on page 139.
1 In the Custom Event Message field, enter the text that you want to display when
your search string conditions are satisfied. The custom event message Origin field will begin with the text LOGMON.
Chapter 3
143
Example: creating a custom event message that displays when a service fails to initialize
This example shows you how to create a custom event message to display the following event message when a service fails to initialize:
GX6 component <ITD> failed initializing service it_execd,. See logfile \var\opt\GX6\log\it_execd.log, for details.
The sample log file entry looks similar to this (with the exception that a real log file entry would fit on one line):
"20030508_124352 <ITD> ExecInitialize failed (szServicesEntry: it_execd, szAccessControlList:\opt\GX6\etc\it_execd.acl, szLogFile: \var\opt\GX6\log\it_execd.log, usllSrv: 7)"
To create the custom event message, in the Custom Event Message Field, enter:
GX6 component %2 failed initializing service %6. See logfile %10 for details.
reduce the log file to 0 MB by deleting all the messages in the log file when the file reaches the size limit backup the file into the pmg_backup subdirectory located in the same directory as the monitored log file and reduce the log file to 0 MB
Each time the file is backed up, the backup file is written to the same directory with an incremental number appended to the log file name. For example, the first time that the error_log.txt reaches its size limit, PATROL creates a backup file named error_log.txt1. The next time that it reaches its limit, PATROL creates a backup file named error_log.txt2 and so on.
NOTE
BMC Software recommends that you periodically move the backup files to another location. The PATROL recovery action checks to make sure that the backup file name is not already in use. If hundreds or even thousands of backup files exist in the log directory, PATROL may take some time to complete this recovery action.
144
Recovery actions run automatically by default; however, you can configure them to require user confirmation if the Run Attended option button is set to Yes.
If you are adding a new log file to be monitored, follow the steps in Start monitoring a log file on page 137. If you want to configure a recovery action for an existing log file, follow the steps in Change the setup of a monitored file on page 139.
1 Type a value in the Size Limit field (the value is in bytes for example, 100 equals
100 bytes).
2 Select an Action option button to specify a recovery action for PATROL to take
when the log file reaches the specified size limit
I
NothingPATROL continues monitoring the log file but does not attempt to reduce its size. DeletePATROL reduces the log file to 0 MB by deleting all the messages in the log file when the file reaches the size limit. Backup and Delete PATROL backs up the existing log file and reduces the log
file to 0 MB
3 Click the Yes or No button to indicate whether PATROL runs attended (prompt an
operator for confirmation before performing a recovery action).
Chapter 3
145
These configurations each offer advantages and disadvantages. To decide which configuration best suits your environment, see Table 15 on page 68. Before configuring the PATROL for Microsoft Cluster Server components, you should verify that the software products are installed correctly. To verify that you have installed the appropropriate software on the appropriate computers, see Installing PATROL KM for Microsoft Cluster Server on page 67.
1 From the PATROL Console, add the managed system that corresponds to your
cluster by choosing Host => Add.
2 From the PATROL Console, load MCS_Load.kml. For instructions on how to load
KMs, see Loading the PATROL for Microsoft Windows Servers KMs on page 85.
3 If the KM is not already configured, Microsoft Clusters - Setup appears as the label
under the MCS_Clusters application instance icon.
5 In the Authorized Account dialog box, enter an account that is a member of the
Administrators group on the local computer or cluster node. This account allows the cluster-level agent and external executables to access the cluster nodes you want to monitor. For internal cluster-level agents configurations, when requirements are met, the KM can use the PATROL agent default account. For more information about setting up the Cluster account, see PATROL KM for Microsoft Cluster Server account on page 44.
146
Displaying PATROL data by using the PATROL Adapter for Microsoft Office
This task describes how to start the PATROL Adapter for Microsoft Excel so that you can view server-based PATROL reports.
Microsoft Excel 97 (SR1, SR2, and SR2b) Microsoft Excel 2000 (SR1a, SP2, and SP3) Microsoft Excel Office XP (SP1, SP2, and SP3) Microsoft Excel Office 2003 (SP1)
To start the PATROL Adapter for Microsoft Office from Microsoft Excel 1 Start Microsoft Excel. 2 Choose File => New. 3 Choose the Spreadsheet Solutions tab. 4 Choose the Patrol Report.xlt template. 5 Click OK.
Chapter 3 Loading and configuring PATROL for Microsoft Windows Servers 147
The New dialog box is dismissed and the Microsoft Excel macros message appears.
7 See the PATROL Adapter for Microsoft Office User Guide for instructions on
generating a report.
NOTE
History reports are not available for PATROL Agents that are version 3.2.09. Please see the PATROL Adapter for Microsoft Office User Guide for more information regarding requirements and limitations of PATROL Adapter for Microsoft Office.
Report Name CPU Util - Weekly History CPU Util - Daily History
148
Table 37
I I I I
Report Name
Logical Disk - Weekly History percentage of free space available on the selected logical disk drive (the Logical Disk - Daily History value reported by the parameter LDldFreeSpacePercent) Memory - Weekly History Memory - Daily History number of megabytes of physical memory currently available to processes (the value reported by the parameter MEMmemAvailableBytes)
Report name DHCP Lease Availability Daily History Report DHCP Lease Availability Monthly History Report DHCP Lease Availability Weekly History Report DHCP Server Utilization Daily History Report DHCP Server Utilization Monthly History Report DHCP Server Utilization Weekly History Report DNS Server Response Time Daily History Report DNS Server Response Time Monthly History Report DNS Server Response Time Weekly History Report DNS Server Utilization Daily History Report DNS Server Utilization Monthly History Report DNS Server Utilization Weekly History Report
NT_REMOTE_SERVERS reports regarding Remote Servers Connect Response Time Daily History daily, weekly, or monthly connection response Report times of remote domain servers Remote Servers Connect Response Time Monthly History Report Remote Servers Connect Response Time Weekly History Report Remote Servers Connection Status Daily Outage Report Remote Servers Connection Status Monthly Outage Report Remote Servers Connection Status Weekly Outage Report Shares Disk Usage Daily History Report Shares Disk Usage Monthly History Report Shares Disk Usage Weekly History Report NT_REMOTE_SERVERS reports regarding daily, weekly, or monthly connection outages of remote domain servers
I I I
I I I
NT_SHARES reports regarding daily, weekly, or monthly usage of network shares on the managed server
Chapter 3
149
Table 38
I I I I I I
Report name Trust Domain Connectivity Daily Outage Report Trust Domain Connectivity Monthly Outage Report Trust Domain Connectivity Weekly Outage Report WINS Server Utilization Daily History Report WINS Server Utilization Monthly History Report WINS Server Utilization Weekly History Report
Report name MSMQ Message Rate - Daily History Report MSMQ Service Availability - Weekly History Report MSMQ Sessions - Daily History Report MSMQ Sessions - Weekly History Report MSMQ Total Msgs. Waiting - Weekly History Report
Report name Process Count Daily Summary Package Status Daily Summary Package Status 30-Day Summary
150
Table 40
Report name Active Packages Daily Summary Aborted Transaction Daily Summary Aborted Transaction 30-Day Summary
Chapter 3
151
To unload KMs with the PATROL Console for Microsoft Windows Servers 1 From the KM tab of the tree view, right-click the application class name that you
want to delete and choose Delete from the pop-up menu.
3 Repeat Step 1 and Step 2 until you have deleted all of the application classes
associated with the KM that you want to delete.
4 From the console menu bar, choose File => Save KM to save your changes.
152 PATROL for Microsoft Windows Servers Getting Started
To unload KMs with the PATROL Console for UNIX 1 From the PATROL Main window, choose Attributes => Application Classes. 2 From the Lists of Application Classes window, click the name of the application
class that you want to delete.
3 From the List of Application Classes menu bar, choose Edit => Delete.
The application class is removed from your cache directory and your console session file. The PATROL Console removes the application class name from the List of Application Classes.
4 Repeat Step 2 and Step 3 until you have deleted all of the application classes
associated with the KM that you want to delete.
5 From the List of Application Classes menu bar, choose File => Save KM to save
your changes.
To Unload KMs with PATROL Central Operator - Windows Edition 1 In the Common Tasks tab of the Operator Console Module Taskpad, click the
Unload Knowledge Module(s) icon.
2 To start the wizard, click Next. 3 From the Managed System screen, select the managed system. 4 From the Knowledge Modules screen, select the KMs that you want to unload. For
a description of the PATROL for Microsoft Windows Servers KMs, see Table 16PATROL for Microsoft Windows Servers .kml files on page 84.
5 Click Finish.
Chapter 3
153
1 From the Managed Systems page, click the Load/Unload KMs button.
The Load KMs page opens, listing each computer on which a PATROL Agent has been installed.
2 Select the computers from which you want to unload .km files, and click Next.
The Load KMs page displays a list of .km files. Currently loaded .km files are highlighted in the list.
3 Cancel the selection of the .km files that you want to unload. 4 Click Finish.
The console removes the .km files that you specified. These .km files will no longer be in the current management profile.
154
Chapter
4
156 156 157 157 157 158 163 163 163 164 164 164 164 165 166 169 169 170 171
This chapter provides you with information that you will need to use the PATROL Cluster Configuration Wizard (also referred to as PCC). The following topics are discussed: Using the PATROL Cluster Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing to use the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access requirements for running the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . Starting the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to use the PCC Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-PCC configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually configuring the PATROL Agent for clustering . . . . . . . . . . . . . . . . . . . . . . Install the application on each cluster node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the PATROL Agent on each cluster node . . . . . . . . . . . . . . . . . . . . . . . . . . Assign a unique port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribute license file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define the PATROL cluster-specific environment variables . . . . . . . . . . . . . . . . Create and register a new service for the PATROL Agent . . . . . . . . . . . . . . . . . . Define the PATROL Agent as a member of the group . . . . . . . . . . . . . . . . . . . . . PATROL cluster-specific environment variables for history and configuration . . . Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
Overview
The PCC Wizard allows you to easily configure the PATROL Agent to monitor cluster-aware applications such as Microsoft Exchange Server. It does this by
I
configuring the agent to operate on a virtual server name and separate port storing the agent history and configuration data on cluster-shared media
Thus, in the event of a node failure, the agent will failover to another node with the monitored application, while providing a consistent view of the data being collected. For example, the history data is kept intact. The Wizard does not enable the monitoring of clustered resources. That functionality is handled by the PATROL Agent and the PATROL KM for Microsoft Cluster Server. The Wizard automates and simplifies cluster configuration of the PATROL Agent, and eliminates configuring the agent manually.
156
install PCC on any computer in the cluster domain install PATROL Agent on all nodes in the cluster know the user name and password of a cluster administrator account identify a group to install the PATROL virtual Agent into; this group will need to contain the following (at a minimum): Physical disk The PATROL virtual Agent stores history and configuration data on a standard cluster-shared disk which, if possible, should not be the quorum disk. Network name A network name resource provides an identity to the group in the form of a unique network name and IP address. This identity makes the group or the PATROL virtual agent accessible from the PATROL Console.
NOTE
The node that you run the PCC Wizard from should be the current owner of the group you select. This recommendation prevents some caution pop-up windows from appearing.
For information about how the PATROL Agent supports an application in a cluster environment and what type of failover tolerance it provides, see the PATROL Agent Reference Manual.
From Windows Start menu, choosing Start => Programs => BMC PATROL => PATROL Cluster Configuration Wizard. typing pcc from the Run command.
157
Service Name
Network Name
Port Number
Shared Drive
History Path
158
Table 41
RTSERVERS variable
Node(s)
creates a registry entry for the PATROL Agent service on each cluster node you select.
159
If you are installing the first resource, select Add one or multiple PATROL Agent resource(s). Adding a PATROL Agent as a cluster resource performs the following actions:
I I
Sets the required environment variables Registers the PATROL Agent with a new service name Adds the PATROL Agent to the cluster as a Generic Service resource type and sets the resource properties
3. Select the groups to which you want to add the agent and click Next.
You can select multiple groups. In most cases, the groups will correspond to the applications you want to monitor.
160
Dialog box
Notes If you do not know what names to use, accept the defaults. The port number must be a port that is not in use by any other process.
5. Verify that all nodes that you want to configure are selected and click OK. You are returned to the PATROL Agent configuration screen. Click Next.
You can select or deselect nodes by clicking on the node. All nodes are selected by default.
161
Dialog box
Notes
Your configuration of the PATROL Agent using PCC performs the following actions:
I
I I I I
I I I I
Registers the PATROL Agent service with a new service name within the Service Control Manager. Sets the registry parameters and port number. Sets the service startup to manual. Creates the resource of type Generic Service in the cluster. Sets the Generic Service resource properties to restart without affecting the cluster group; remaining properties have default values. Sets the service name parameter of the Generic Service and enables use Network Name for computer name. Creates PATROL Agent history and configuration files on shared disk. Creates environment variables for cluster nodes. Brings the newly created resource online if the selection box is checked. Sets resource dependencies on the specified Physical Disk and Network Name.
162
Post-PCC configuration
Post-PCC configuration
Now that you have finished using PCC to configure multiple PATROL Agents, you must perform some post-wizard configuration. Each of the group agents in the cluster need to monitor resources that are a only part of that group. The node agents should not monitor group resources. This generally requires using wpconfig to modify the disabledKMs list for each group agent, and configuring the remaining KMs to monitor only resources that are instances of that group. This also means that you only need to modify the preloadedKMs list using wpconfig to preload KMs that are appropriate for that node or group agent.
The information in this section provides a general idea of the processes involved in setting up a Windows cluster environment and integrating PATROL into that environment. Procedures and steps describing how to set up third-party software are intended as a general outline of the process for that product and are not intended as step-by-step instructions. Setting up PATROL to run in a Windows cluster environment consists of several standard tasks. The standard cluster administration tasks and the PATROL-specific tasks are described in general terms. This section provides a high-level overview of building a Windows cluster and integrating PATROL into that environment. The manual process defined in this chapter requires you to run multiple PATROL Agent executables on your CPU to monitor more than one application on the cluster.
163
one to monitor the nodes operating system one to monitor the cluster application
Install the agent once. Include only those Knowledge Modules that support the application and the operating system. Then see Create and register a new service for the PATROL Agent on page 165 for information about setting up a second agent to monitor the cluster application.
164
1 From the Windows Taskbar, select Start => Settings => Control Panel. 2 Double-click the System icon and select the Environment tab. 3 Enter the variable name and value in the appropriate fields and click Set. The
variables and their values are listed below. Repeat this step for the remaining variables. PATROL_VIRTUALNAME_PORT=VirtualServerName PATROL_HISTORY_PORT=Drive:\History_Directory PATROL_CONFIG_PORT=Drive:\Config_Directory For more information about specific variables, see PATROL cluster-specific environment variables for history and configuration on page 169.
1 Copy the PatrolAgent.exe in %PATROL_HOME%\bin directory. 2 Rename the executable. Use a name that indicates that the agent is an executable
dedicated to monitoring an application.
PatrolAgent-application_name.exe
Tue MON DD HH:MM:SS CCYY PatrolAgent-application_name PID 318 Success 1000: The PatrolAgent Service was successfully installed. The PatrolAgent COM Server registered sucessfully
NOTE
The PatrolAgent COM Server can be registered only once. Additional attempts to register it will fail; however, the multiple agent processes will run.
5 From the Windows Taskbar, select Start => Settings => Control Panel. 6 Double-click the Services icon and select application_name service from the list box.
Click Startup.
7 In the Startup Type pane, select the Manual radio button and click OK. The service
displays Manual in the Startup column.
NOTE
This task description uses Windows Cluster Management Software as an example. The steps describing how to set up the software are intended as a general outline of the process and are not intended as step-by-step instructions.
Perform the following task on only the master node of the cluster. The cluster software provides two methods for binding a service to a cluster: GUI or command line. Regardless of the method you choose, you must provide the information listed in Table 42. Table 42
Arguments cluster.exe clusterName RES "PatrolAgent for MyApplication" /ADDEP
/CREATE /Group: /TYPE: Create a group and assign it a resource type. Establish a dependency between the service and the cluster.
166
Table 42
Arguments
NOTE
For each command, you must reenter the name of the cluster executable, the name of the cluster, the resource option, and the service name.
1 From the command line, issue the following command to name the service,
designate it as a resource of the cluster, create a group, and assign it a resource type of Generic Service.
cluster.exe clusterName RES "PatrolAgent for MyApplication" /CREATE /Group:MyGroup /TYPE:"Generic Service"
2 Add the disk that stores the PATROL Agent configuration and history information
as a dependency. This command instructs the cluster software to bring up the disk with configuration information before it attempts to start the PATROL Agent.
cluster.exe clusterName RES "PatrolAgent for MyApplication" /ADDDEP:"Disk MyGroupDisk"
167
3 Set the restart action. This command determines what the cluster does if an
application fails and is unable to restart. A value of one (1) indicates that if the application is unable to restart, the cluster will continue to run.
cluster.exe clusterName RES "PatrolAgent for MyApplication" /Prop:RestartAction=1
4 Identify the service name to the cluster software. The service name must be
identical to the service name assigned to the PATROL Agent executable on each cluster node.
cluster.exe clusterName RES "PatrolAgent for MyApplication" /Priv ServiceName="PatrolAgent-application_name"
5 Set the port number for the PATROL Agent bound to the cluster application. This
number must be the same as the number assigned as a suffix to the PATROL cluster-specific environment variables. For details about the PATROL cluster-specific environment variables, see Define the PATROL cluster-specific environment variables on page 164.
cluster.exe clusterName RES "PatrolAgent for MyApplication" /Priv StartupParameters="-p Port#"
168
Variables
Table 43 describes the purpose of PATROL cluster-specific environment variables. Table 43 PATROL cluster-specific environment variables
Description the location of history files If this variable is empty or doesnt exist, the agent writes the history files to PATROL_HOME\log\history\ host\portnumber. PATROL_VIRTUALNAME PATROL_VIRTUALNAME_PORTa an alias for the host name If this variable is empty or doesnt exist, the agent uses the host name to identify history data within the history files. PATROL_CONFIG PATROL_CONFIG_PORTa the location of the configuration files If this variable is empty or doesnt exist, the agent stores the configuration file in PATROL_HOME\config.
a
To manage multiple PATROL Agents running on separate ports, append the port number to the variable name. This situation occurs when PATROL Agents are bound to individual applications such as Oracle, Exchange, Sybase, etc. Each agent uses a separate port number.
169
Operation
When searching for configuration information and creating and writing to the history database, the PATROL Agent uses the following logic to check for the existence of PATROL cluster-specific variables. Table 44 Operation of configuration and history environment variables
Exists? Description yes PATROL_VIRTUALNAME_8888 exists, the agent writes history using the virtual name as the host name. Using the virtual name provides continuous history for an application regardless of which host the application is running on. The agent also uses the virtual host name to identify the configuration file changes and the history database. Configuration file changes are written to PATROL_HOME\config\config_virtualname_port.cfg. The history database is written to the subdirectory structure history\virtualname\port, which will be located in the directory pointed to by PATROL_HISTORY_PORT. no The agent writes history using the actual host name. If the application fails over, the agent writes history using the new agents name. Using the actual hostname creates gaps in the results of any dump_hist commands because the command does not recognize that the same application ran on different hosts. PATROL_CONFIG_8888 exists, then the agent reads configuration information from the location specified by this variable. The agent reads from the default directory, PATROL_HOME\config\config_virtualname or hostname-port PATROL_HISTORY_8888 exists, then the agent writes history to the location specified by this variable the agent writes to the default directory, PATROL_HOME\log\history\virtualname or hostname\port\
Configuration File
yes no
History Database
yes no
170
Example
The following example illustrates how the environment variables would be named for a host using port 8888. It also depicts the directory structure and file location.
Environment variables
PATROL_HISTORY=K:\doc\work\histdir PATROL_VIRTUALNAME=AliasHostName PATROL_CONFIG=K:\doc\work\config
Directory structure
For the values provided in the Environment Variables section of this example, the PATROL Agent stores configuration information and records the history data in the following directory structure:
K:\doc\work\histdir\AliasHostName\8888\annotate.dat K:\doc\work\histdir\AliasHostName\8888\param.hist K:\doc\work\config\config_AliasHostName-8888
If these variables do not exist or they are empty, the PATROL Agent stores configuration information and records the history data in the following directory structure:
%PATROL_HOME%\log\history\HostName\8888\annotate.dat %PATROL_HOME%\log\history\HostName\8888\param.hist %PATROL_HOME%\config\config_HostName-8888
171
172
Chapter
This chapter contains information for troubleshooting PATROL for Microsoft Windows Servers. This chapter contains the following topics: PATROL KM for Microsoft Windows OS problems. . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Process or job object data not displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 PATROL Generates Event 560 and 562 in the Windows security event log. . . . 175 Event filter parameters not automatically acknowledged . . . . . . . . . . . . . . . . . . 175 Newly installed protocols are not discovered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Event log summary instance cannot be removed . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Windows event log does not work if the /AgentSetup/defaultAccount pconfig variable is blank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 PATROL KM for Event Management problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Too many e-mail alerts are being generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Parameters settings lost after agent restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 PATROL KM for Event Management not working as expected . . . . . . . . . . . . . 179 AS_AVAILABILITY application not displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Problems with all other KMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Cannot add performance monitor counters with alarm ranges less than 1 . . . . 180 AdPerfCollector parameter display error message . . . . . . . . . . . . . . . . . . . . . . . . 181 Recovery action problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Recovery actions do not execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Even though I select Do not ask me again PATROL prompts before running recovery action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Gathering diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Locations where you can find diagnostic information . . . . . . . . . . . . . . . . . . . . . 183 Installation logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Determining PATROL KM version number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Chapter 5
173
Paage
174 175 175 175 176 176
174
PATROL Generates Event 560 and 562 in the Windows security event log
PATROL generates the following events in the Windows security event log:
I I
Explanation PATROL generates these events during normal data collection if success auditing is enabled for object access.
Explanation
These parameters cannot be Deselect the option to notify PATROL immediately when an event that automatically acknowledged. matches the filter occurs. You cannot use the auto-acknowledge feature if the event filter is configured to notify immediately. For more information about this setting, see Configuring Windows events monitoring on page 97.
Chapter 5
175
Explanation The PATROL Agent does not detect the new performance objects.
Windows event log does not work if the /AgentSetup/defaultAccount pconfig variable is blank
The Windows event log does not work correctly if the /AgentSetup/defaultAccount pconfig variable is blank. The Agent default account credentials are stored in the /AgentSetup/defaultAccount agent pconfig variable.
Explanation The /AgentSetup/defaultAccount pconfig variable is blank. Solution
Set the PATROL default account so that the /AgentSetup/defaultAccount agent pconfig variable is not blank.
176
The rule Set the rule /AS/EVENTSPRING/ALERT/arsAction to 0. /AS/EVENTSPRING/ALERT/a rsAction is set to 4. If the arsAction rule is set to 4 for all PATROL objects, notifications are sent for all events. Instead, you may want to disable notification for all PATROL objects, by setting /AS/EVENTSPRING/arsAction to 0 at the remote agent. Then, enable notification only for the desired applications, instances, or parameters. When you enable notification for a specific PATROL object, the following configuration variable is created: /AS/EVENTSPRING/ALERT/object/arsAction
Chapter 5
177
The allowsendparamonly variable exists in Remove the allowsendparamonly variable.For %PATROL_HOME%\common\patrol.d\PATROL.conf instructions, see Removing the file and is set to true. allowsendparamonly variable. If this variable exists and is set to True, then state change events for applications and instances are not generated. This reduces network traffic, but it also prevents the PATROL KM for Event Management from detecting when parameters become active after an agent restart. Thus, the PATROL KM or Event Management threshold and poll time settings are not applied. etc/patrol.d/PATROL.conf does not exist. If Patrol.conf file doesn't exist then all the agent variables get set to TRUE. To resolve this problem, obtain a copy of the file Patrol.conf and remove the allowsendparamonly variable, if it exists, as described in Removing the allowsendparamonly variable. To obtain the Patrol.conf file, copy it from another computer or contact BMC Software Support.
Removing the allowsendparamonly variable 1 Move patrol.conf from %PATROL_HOME%\common\patrol.d to a secure location. 2 Using the PACFG (PATROL Agent Configuration) utility, specify that secured
location.
3 Using Notepad (with word wrap disabled) or Wordpad, open patrol.conf. 4 Underneath the [AGENT] stanza, remove the following line:
allowsendparamonly=true
178
It does not send events. The NotifiedEvents parameter is offline. Errors are displayed in the console system output window Parameter thresholds are not applied.
Solution On Windows platforms, if the PATROL Agent is installed after the PATROL KM for Event Management, a PATROL KM for Event Management catalog file is overwritten. The PATROL KM for Event Management must be installed after the PATROL Agent for the PATROL KM for Event Management to function. If you are running PATROL KM for Event Management 2.5.x and you do not want to upgrade to version 2.6.00, you must ensure that you are using the correct event catalog file. For more information, see To Ensure the PATROL KM for Event Management 2.5x uses Correct Event Catalog File.
Explanation The PATROL KM for Event Management catalog file has been overwritten.
To Ensure the PATROL KM for Event Management 2.5x uses Correct Event Catalog File 1 Stop the PATROL Agent service. 2 Rename %PATROL_HOME%\lib\knowledge\StdEvents.ctg to
%PATROL_HOME%\lib\knowledge\StdEvents.ctg.bak
3 Rename %PATROL_HOME%\lib\knowledge\StdEvents.ctg.date_PID to
%PATROL_HOME%\lib\knowledge\StdEvents.ctg ensuring that the correct backup file that corresponds to the PATROL Agent installation is renamed.
Availability targets have Add availability targets. For more information, see the PATROL KM for Event not been added. Management User Guide. The AS_AVAILABILITY application class instantiates only when availability targets have been defined.
Chapter 5
179
Cannot add performance monitor counters with alarm ranges less than 1
The PATROL Wizard for Performance Monitor and WMI does not allow decimal alarm ranges that are less than one, yet the Performance Monitor counters values are normally in this range.
Explanation This problem is due to a PATROL limitation. See the suggested solution. Solution To resolve this problem, you can manually multiply or divide the PerfMon counter to get appropriate values for display so that you can set appropriate alarm ranges. For more information, see Customizing performance monitor counters.
To customize performance counters 1 Use the PATROL Wizard for Performance Monitor and WMI to create parameters
for a Performance Monitor counter, as described in Creating performance monitor parameters on page 133.
180
3 Edit the configuration variable value by adding, after the counter name, *multiplier,
where multiplier is the numerical value by which you want to multiply the reported value. For example, to multiple the reported value of the counter Active Threads by 100, add *100 to the variable, as shown: Active Threads*100. If you are monitoring multiple counters for the object, you can also multiple the other counters by a multiplier. For example: counter1*100,counter2,counter3*0.1
WARNING
When entering a multiplier that is less than 1, you must include a leading zero. For example, you must enter 0.1, and not .1.
The required Microsoft Follow the instructions in Microsoft Knowledge Base Article 266416 to dredge Performance Counters are not the performance counters from the registry and make them available in WMI. available in WMI.
Chapter 5
181
Even though I select Do not ask me again PATROL prompts before running recovery action
Even though you select the option Do not ask me again, PATROL prompts you again before running a recovery action. For example, you configure the recovery action that terminates a runaway process and specify that the recovery action runs only with operator confirmation. When the recovery action is triggered, PATROL prompts you whether to terminate the process. You enable the recovery action and select the option Do not ask me again. The next time that the process is triggered to be terminated, it runs with a different PID and, therefore, PATROL prompts you again before terminating the process.
Explanation The process runs with a different PID (process identification) number and appears to PATROL as a different process. Solution This is a known issue. As a workaround, you can configure the recovery action to run automatically instead of with operator confirmation. For more information about configuring recovery actions, see Configuring recovery actions on page 117.
182
System Output See the documentation for your PATROL The system output window contains messages Window console. relating to the operation of KMs, including error messages. PATROL From the PATROL console, right-click Event Manager the host and select Event Manager. The PATROL Event Manager shows all of the PATROL related events for the host. You can check here to determine if NOTIFY_EVENTS are being generated. PATROL Diags provides a variety of information about your environment that support requires.
PATROL Diags
From the PATROL console, load KM PSX_APPLICATION_DEBUG and right-click Application Trace icon => KM Commands => Create Diagnostic Report
Installation logs
One log file is created each time the installer is run. The name of the log file is a combination of the computer name and a time stamp. The log file is located in the %USERPROFILE%\Application Data\BMCINSTALL\ directory. For example, a log file for user bhunter on a Windows Server computer BHUNT_1 could be:
C:\WINNT\Profiles\bhunter\Application Data\BMCinstall\BHUNT_1-1005340189.log.
Chapter 5
183
To determine the PATROL KM version 1 From the PATROL console, access the top-level KM application. 2 Right-click the application and select the menu command InfoBox and described in
Accessing KM commands and InfoBoxes on page 186. The PATROL KM version is displayed next to KM Version.
184
Appendix
BMC Software offers several PATROL consoles from which you can view a PATROL Knowledge Module (KM). Because of the different environments in which these consoles run, each one uses a different method to display and access information in the KM. This appendix provides instructions for accessing the KM menu commands, InfoBoxes, and online Help on each of the PATROL consoles. See the PATROL for Windows Servers online Help for more detailed information about navigation in the PATROL Consoles. Accessing KM commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Appendix A
185
In the navigation pane, right-click a In the navigation pane, right-click a PATROL object and choose managed system or application InfoBox from the pop-up menu. icon and choose Knowledge Module Commands from the pop-up menu. In the tree view area, right-click an In the tree view area, right-click a PATROL object and choose application icon and choose Infobox from the pop-up menu. Knowledge Module Commands from the pop-up menu.
186
NOTE
If you are trying to access Help from a UNIX console, see the PATROL Installation Reference Manual for specific instructions about installing and setting up a browser in the UNIX environment.
Table 46
Console
Right-click a parameter icon and choose Help On from the pop-up menu. Double-click a parameter icon; click the ? icon or Help button in the parameter display window. Double-click a parameter in the KM tab of the console; from the properties dialog box, click the Help tab; then click Show Help.
From the console menu bar, choose Help On => Knowledge Modules.
Choose Attributes => Application Classes and double-click the application name. Click Show Help in the Application Definition dialog box. In the Operator tab of the navigation pane, select an application icon and press F1.
From the console menu bar, choose Help => Help Topics. In the Contents tab, click the name of your product.
In the Operator tab of the navigation pane, select a parameter icon and press F1.
In the upper right corner of In the tree view, right-click In the tree view, right-click an application class and a parameter and choose PATROL Central, click Help. Help and choose PATROL choose Help. KM Help.
Appendix A
187
188
Appendix
The variables described in this appendix are PATROL for Windows Servers agent configuration variables that are set in the PATROL Agent. To view these variables, use the PATROL Configuration Manager or the wpconfig utility. Information about using PATROL Configuration Manager is included in this appendix. This appendix also describes the PATROL Configuration Manager rulesets that are provided for PATROL for Microsoft Windows Servers.
WARNING
Changing any of these agent configuration variables can prevent some functions from working properly and can affect your entire installation. Before you change a variable, make a record of the original setting.
Managing configuration variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 PATROL for Windows Servers configuration variables . . . . . . . . . . . . . . . . . . . . . . . 190 PATROL KM for Microsoft Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 PATROL KM for Microsoft Windows Domain Services . . . . . . . . . . . . . . . . . . . . 205 PATROL KM for Microsoft Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 PATROL KM for Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 PATROL KM for Microsoft Windows Message Queue. . . . . . . . . . . . . . . . . . . . . 216 PATROL KM for Microsoft COM+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 PATROL Wizard for Microsoft Performance Monitor and WMI. . . . . . . . . . . . . 218 PATROL for Microsoft Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 PATROL for Microsoft Windows Servers rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Server roles with predefined rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Using PATROL Configuration Manager to apply rulesets . . . . . . . . . . . . . . . . . . 220 Server roles with predefined rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Ruleset reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Using PATROL Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Using PCM to apply configurations changes to other agents. . . . . . . . . . . . . . . . 232 Manually creating or changing configuration variables . . . . . . . . . 233 on page 232
Appendix B
189
NOTE
For information about the PATROL KM for Event Management agent configuration variables, see the PATROL KM for Event Management User Guide.
190
Table 47
Migrate37
specifies whether the KM migrates the configurations from the registry at every discovery cycle the alarm threshold used when automatic monitoring is enabled the length of time that a process can exceed the AlarmThreshold before the KM automatically monitors the process
0, 1
NA
CollectionCount
the number of processes that the KM integer greater collects performance data for at one than 0 time specifies whether the KM automatically creates instances for the PATROL group Note: You must also remove the instances from the list of monitored instances using the Configure Manual Process Monitoring => Remove Processes menu command.
I I
DisablePatrolGroup
DisablePatrolRestart
specifies whether the PATROL agent 0, 1 restarts if it exceeds the processor% threshold specifies how many processes the KM displays in the View Process Status dialog box the column that is used for sorting the View Process Status dialog box
I I
empty
StatusNumberofProcessesToDisplay
StatusSortKey StatusSelectedColumns/list
an existing column
comma-separated list of columns the User%,Memory NA KM displays in the View Process Usage,VM Status dialog box size,Page Faults/sec,Hand les,Threads,Arg uments
Appendix B
191
Table 47
/ProcessMonitoring/ProcessConfigurationList/instance
TimeLimitForKillRunAwayProcess
empty
list of the groups to which the process belongs list of arguments for the configured process specifies whether the process is a user-defined process enables and disables the automatic resetting of specific service monitoring flags specifies whether annotations are enabled or disabled for the NT_SERVICES application parameters global setting that specifies restart properties for all services. For more information about using this variable, see Ensuring that services are restarted as desired on page 109.
NA NA Yes
I I
0 = disabled empty 1 = enabled 0 or blank = empty enabled 1 = disabled 0 = yes, automatic restart 1 = no automatic restart 0
DisableAnnotation
I I
DisableServiceRestart
192
Table 47
Default empty
MonitorManualServices
specifies whether manual services are monitored contains a list of services that have been removed by the PATROL user Note: The default value NULL indicates that no services are removed.
I I
empty
removedServiceList
NULL
UseBackwardCompatibleName
enables you to remove the SERVICES prefix from NT_SERVICES instance names Note: You must enter this variable manually; the KM does not create it. In version 3.9.00 of PATROL KM for Microsoft Windows OS, the NT_SERVICES instance names were changed; they were prefixed with SERVICES. This naming convention is not fully backward compatible.
I I
Appendix B
193
Table 47
Default
/ServiceMonitoring/ServiceList/service name 0 = no alarm NA 1 = yes, alarm 0 = no restart 1 = yes, restart 0 = yes, automatic reset 1 = no automatic reset 0 = no monitoring 1 = yes, monitor NA
AutoRestart
I I
IgnoreAutoResetConfig
specifies whether the global auto reset feature applies to this service This variable can be set only through PATROL Configuration Manager.
Monitor
specifies whether to monitor the service By default, only automatic and running manual services are monitored.
I I
NA
MonitorProcess
specifies whether the process associated with the service is monitored specifies whether the KM runs the command specified by the NotRespondCmd variable
I I
0 = no 1 = yes 0 = no 1 = yes
MonitorNotRespond
I I
NotRespondCmd
the path to an executable that the path to an KM runs if the variable executable MonitorNotRespond has a value of 1
NA
194
Table 47
Default
OverrideGlobalServiceMonitoring
specifies whether the MonitorProcess variable for the monitored service overrides the global DisableServiceMonitoring variable You can set this variable only by using PATROL Configuration Manager.
I I
specifies whether the service triggers a warning instead of an alarm specifies the location of the backup directory for the event log
I I
0 = alarm 0 1 = warning NA
directory path
Example: Note: If the directory entered for the D:\temp backup directory does not exist, the Backup and Clear Eventlog recovery action fails. IncludeAll specifies whether all event logs are discovered or only those configured to be monitored specifies whether to automatically activate and automatically inactivate event log parameters based on the current configuration You can also use this variable to inactivate or activate other parameters. For example, you could use the following variable to inactivate the NT_HEALTH parameters: .../HealthMonitoring/OverridePara meterAutoActivate
I I I I
OverrideParameterAutoActivate
Appendix B
195
Table 47
Default
UseCheckPoint
specifies whether the event log uses a checkpoint value to guarantee that no events are missed if the PATROL Agent is not running or the KM is not loaded for a period of time This is a global setting that can be overridden by individual event log configurations.
I I
MaxResourceIdleRetainPeriod
the maximum amount of time, since greater than 0 last accessed, that an event description resource DLL is held in cache list of event logs that are monitored list of event logs that are not monitored specifies whether to disable information events generated by XPC (psx_server.xpc).
300 seconds
TogglePEMOriginData
determines whether the event is displayed in the event log name format or the detailed format in PEM (PATROL Event Manager) specifies whether all occurring events are sent to PEM (PATROL Event Manager) specifies whether all events that match the configured event filters for the event log are sent to PEM (PATROL Event Manager)
I I
0 = event log 0 name format 1 = detailed format 0 = do not send 1 = send 0 = do not send 1 = send 0
ForwardFilteredNTEventstoPEM
196
Table 47
Default
0 0 = do not override (create) 1 = yes, override (do not create) 0 = use auto 0 configure 1 = do not use auto configure
OverrideParameterFileFreeSpacePct AutoActivate
specifies whether the parameter ELMEvFileFreeSpacePercent automatically activates and inactivates based on the current configuration This variable applies to a specific event log. You can also apply this variable globally to all event logs.
I I
UseCheckPoint
specifies whether the event log uses a checkpoint value to guarantee that no events are missed if the PATROL Agent is not running or the KM is not loaded for a period of time the last event log record that was successfully recorded a list that details the defined event filters specifies whether the event filter is enabled Disabled event filters are not discovered and do not collect events.
I I
CheckPoint EventFilters/child_list
0 Summar y 1
CreateInstance
specifies whether an application instance is created for the event filter An application instance is not required to collect data. However, if an instance is not created, the only way to retrieve the data collected by the event filter is too subscribe to the event filter data.
I I
ParentInstance
allows the parent application instance of an event filter to be changed. If this value is set, the event filter instance is created with the specified parent instance.
NA
Appendix B
197
Table 47
Annotation
specifies whether the parameter data point is annotated with event text specifies whether event types are consolidated
I I
ConsolidateEventTypes
I I
ConsolidationNumber
number of events that occur within a integer less than 1 specified time and are reported as 35791394 one event the time period in which events must occur to satisfy the consolidation criteria specifies whether event descriptions are reported by means of a text parameter specifies the type of events that are filtered 1 = Error 2 = Warning 4 = Information 8 = AuditSuccess 16 = AuditFailure 32= OtherType A valid value is any summation of these types. For example, to monitor both Warning and AuditFailure events, use a value of 18 (2 +16). integer less than 0 35791394
I I
ConsolidationTime
EventReport
EventType
FilterDescription
no restrictions
NA
198
Table 47
Default 1
CategoryList/list
list of event a list of event categories that are categories included or excluded from monitoring, depending on the value of the variable IncludeAllCategories specifies whether all event IDs are monitored If all event IDs are monitored (1), then the EventIdList variable represents an exclusion list. Otherwise, it represents an inclusion list.
I I
NA
IncludeAllEventIds
EventIdList/list
list of event IDs a list of event categories that are included or excluded from monitoring, depending on the value of the variable IncludeAllEventIds specifies whether all sources are monitored If all sources are monitored (1), then the SourceList variable represents an exclusion list. Otherwise, it represents an inclusion list.
I I
NA
IncludeAllSources
SourceList/list
a list of sources that are included or excluded from monitoring, depending on the value of the variable IncludeAllSources specifies whether all text strings are monitored If all text strings are monitored (1), then the StringList variable represents an exclusion list. Otherwise, it represents an inclusion list.
NA
IncludeAllStrings
I I
Appendix B
199
Table 47
IncludeAllUsers
UserList/list
a list of users that are included or excluded from monitoring, depending on the value of the variable IncludeAllUsers specifies whether event descriptions are stored in the PATROL Agent namespace for retrieval the type of collection used for collecting event data
NA
RetainEventDescriptions
I I I I I
Scheduling
MaxRecords
the maximum number of records that are held in psx_server.xpc memory for the filter lists the subscriptions that exist for the parent event log and filter
greater than 0
3010
SubscriberList/list DisplayName
subscribers
empty NA
specifies the label that the KM places label for filter under the filter instance Note: You must manually enter this variable; the KM does not create it. Setting this variable does not change the instance name/namespace. This variable is read only at initial filter creation or parent instance change.
FilterDisableCase
specifies whether the filter comparisons are made in a caseindependent manner This variable has four bit values, depending upon case sensitivity, one bit corresponding to each of Source, User, Category, and String, respectively. If any bit value is 1, a case-independent filter comparison is made for the corresponding field.
200
Table 47
/EventLogMonitoring/eventlog/Subscribers/subscriber
Function
function name
empty
Library
library name
empty
/EventLogMonitoring/_TUNING_/ EventForwardingHeartbeat 30000 specifies the heartbeat configuration number that is that is passed to the PEM API calculated using valid values: 5000 <= x <= 1800000 specifies the number of times the KM attempts to send an event 4 number that is calculated using valid values: 2 <= x <= 10 30000 number that is calculated using valid values: 5000 <= x <= 1800000 number > 0 3010
EventForwardingRetries
EventForwardingTimeout
MaxFilterRecords
specifies the maximum number of records that the KM holds in XPC (psx_server.xpc) memory for any filter specifies whether the KM obtains account names from the SID
ReportAccountName
0, 1
Appendix B
201
Table 47
Default 0
ManualAcknowledge
0 0 = auto acknowledg e 1= manually acknowledg e 0 = do not monitor 1 = monitor 0 = only configured objects 1 = all 1
MonitorProcess
whether job object assigned processes are monitored whether all job objects are discovered or only the job objects specifically configured to be monitored the job objects that are monitored the job objects that are excluded from monitoring number of processes for which performance data is collected at one time whether the PROCStatus parameter is annotated specifies whether to destroy acknowledged process instances specifies whether the parameter NT_CPU/CPUprcrProcessorTimePe rcent for the _Total instance is annotated with the top N CPUconsuming processes
I I
IncludeAll
I I I I
1 1
I I
AnnotateProcCount
number of top processes to include integer greater than 0 when annotating the NT_CPU/CPUprcrProcessorTimePe rcent parameter specifies whether annotations are enabled or disabled for the NT_CPU (icon labled Processor) application parameters the processors that are excluded from monitoring
I I
10
DisableAnnotation
ExclusionList/list
list of processors NA
202
Table 47
Default 1
0 = no 1 = yes
InclusionList/list
list of processors NA
the last count of the processors that are monitored whether all network interfaces (less those excluded) are monitored the pagefiles that are monitored This variable is ignored unless the /PagefileMonitoring/IncludeAll variable is set to 0.
integer
I I
0 = no 1 = yes
1 NA
list of pagefiles
the pagefiles that are excluded from monitoring whether all network interfaces (less those excluded) are monitored the network interfaces that are monitored This variable is ignored unless the /NetworkInterfaceMonitoring/Incl udeAll variable is set to 0.
list of pagefiles
NA
I I
0 = no 1 = yes
1 NA
NA
the physical disks that are monitored list of device numbers the physical disks that are excluded from monitoring whether all physical disks are discovered specifies the maximum number of times that the KM can issue the %RELOAD_COUNTERS command whether the NT_FTP KM is activated list of device numbers
I I
0 = no 1 = yes
integer > 0
/NetworkProtocolMonitoring/ FTP/Active
I I
0 = no 1 = yes
Appendix B
203
Table 47
Directory path and variable ICMP/Active IP/Active IPX/Active NETBEUI/Active NETBIOS/Active TCP/Active UDP/Active /LogicalDiskMonitoring/ InclusionList/list ExclusionList/list IncludeAll MaxReloadCounters
Default 1 1 1 1 1 1 1
0 = no 1 = yes
integer > 0
0 = no 1 = yes
0 = no 1 = yes 0 = no 1 = yes
0 to 100
30
204
Table 47
Default 80 0
0 = auto configure 1 = do not auto configure 0 = auto correct 1 = do not auto correct
OverrideAutoConfigUpdate
I I
HighThresholdOnEvents
greater than 0
2000000
ServerIPAddress
text string
the number of times to perform a DNS test comma-separated list of IP addresses to attempt during DNS test
10 NA
Appendix B
205
Table 48
text string 1 = TCP 0 = UDP 0 = no 1 = yes 0 = no 1 = yes 0 = no 1 = yes 0 = no 1 = yes 0 = no 1 = yes 0 = no 1 = yes
raises a PATROL event when a DHCP Scope is added raises a PATROL event when a DHCP Scope is removed raises a PATROL event when the DHCP database is backed up raises a PATROL event when a new master browser is elected raises a PATROL event when a member server is added to the domain raises a PATROL event when a member server is removed from the domain
0 0 0
0 0
MBRDEL
raises a PATROL event when a BDC 0 = no server is added to the domain 1 = yes raises a PATROL event when a BDC 0 = no server is removed from the domain 1 = yes raises a PATROL event when a 0 = no DHCP server is added to the domain 1 = yes raises a PATROL event when a DHCP server is removed from the domain 0 = no 1 = yes
0 0 0 0
WINSADD WINSDEL
raises a PATROL event when a 0 = no WINS server is added to the domain 1 = yes raises a PATROL event when a WINS server is removed from the domain the number of minutes a server is inactive before it is considered idle 0 = no 1 = yes
0 0
206
Table 48
/DomainKM/Shares/ MaxShares the maximum number of shares that string can be discovered by NT_SHARES Note: Increasing this value above 300 may affect PATROL Agent performance. ShareExcludeList comma-separated list of shared directories that should not be discovered by NT_SHARES comma-separated list of trust relationships that should not be discovered by NT_TRUST maximum number of user accounts that can be discovered by NT_USERS Note: Increasing this value above 300 may affect PATROL Agent performance. UserExcludeList comma-separated list of user accounts that should not be discovered by NT_USERS string NA string NA 300
Appendix B
207
minimum percentage of size for the number > 0 < 100 20 (percentage) percent Active Directory database if the database and log files reside on separate logical drives This value is used by the AdDiskSpaceAvailable parameter.
DbRequiredSpace
minimum amount of free space required in kilobytes for the logical drive that holds the database file enables/disables parameter annotation. By default annotation is enabled. To disable annotation for all PATROL KM for Active Directory parameters, add this variable to pconfig and set the value to 1. controls the creation of the old format (1.5.x) Active Directory event filters
500000 kilobytes 0
DisableAnnotations
DisableEventConfig
I I
DisableObsoleteEventFilters
I I
number of hours 12 hours DomainNamingMasterConnStatus interval for checking LDAP greater than 0 Sched connectivity to the domain controller that is the FSMO Domain Naming Master EnableRA determines whether the KM executes the Restart File Replication Service recovery action that is associated with the AdFrsSidResolution parameter determines the Active Directory object types that the KM monitors for replication collisions
I I
IncludedCNFObjectTypes
208
Table 49
LdapGcConnStatusSched
number of 3600 seconds between seconds collections (1 hour) percentage > 0 but < 100 20 percent
LogRequiredPercent
LogRequiredSpace
minimum amount of space required number of in kilobytes for the Active Directory kilobytes > 0 log files if the log files and the database reside on the same logical drive This value is used by the AdDiskSpaceAvailable parameter
200000 kilobytes
PDCEmulatorConnStatusSched
interval for checking LDAP connectivity to the domain controller that is the FSMO PDC Emulator
number of hours 1 hour RelativeIDMasterConnStatusSched interval for checking LDAP greater than 0 connectivity to the domain controller that is the FSMO Relative ID Master ReplMonConfigNC determines whether configuration naming context replication monitoring is enabled determines whether domain naming context replication monitoring is enabled interval for checking LDAP connectivity to the domain controller that is the FSMO Schema Master
I I
ReplMonDomainNC
I I
SchemaMasterConnStatusSched
Appendix B
209
Table 49
/ActiveDirectory/Configuration/fully-qualified-server-name_
PingTimeout
provides a way to configure (on a per-server basis) the timeout that is used when a server is pinged for availability - servers that are connected through a slower link may need this value increased
5,000
PingCount
number of pings 3 provides a way to configure (on a greater than 0 per-server basis) the number of times that a server is pinged to test its availability - servers that are connected through a slower link may need this value increased (a server is considered available if any one ping is successful) indicates whether the KM overrides the check point enabling for the FRS event log This value is used by the AdFrsRpcConnectivity parameter.
I I
MaxWaitTime
number > 0 indicates the maximum amount of time the KM waits in seconds for a 13509 FRS event to occur after a 13508 FRS occurs before considering the 13508 FRS event an issue This value is used by the AdFrsRpcConnectivity parameter
14400 seconds
Do not manually change the values of the following variables. These variables contain state information that is used internally by the product. If you change these variables manually, the product cannot operate correctly. /ActiveDirectory/AgentSiteInfo prevDCName contains the last known qualified domain name of the domain controller Do not manually change the value of this variable.
prevDCSiteName
contains the name of the last known Do not manually change the site where the domain controller value of this variable. resided
210
Table 49
/ActiveDirectory/ReplConfig/replication context replication source/ contains information that specifies a ConfigNC DomainNC configuration naming context or a domain naming context, for example, /ActiveDirectory/ReplConfig/Con figNCwaternoose.monsters.inc/first NonResponse contains the UTC time when the KM Do not manually change the determined that the replication source value of this variable. was non-responsive contains the UTC time when the replication source last updated its replication object Do not manually change the value of this variable.
firstNonResponse
lastChangeTime
origChangeTime
contains the UTC time when the KM Do not manually change the determined that the replication source value of this variable. might have failed to replicate contains the last known version of an object; the KM uses this information to determine whether or not a change was replicated Do not manually change the value of this variable.
prevObjectVersion
ClaInsideCluster DisableServiceAutoRestart
1 0
indicates whether the McsService is 0, 1 automatically started and stopped by the KM indicates whether the MCS_Clusters parameters, McsGwConAvailable, McsGatewayStatus, and McsServiceStatus, are automatically activated and inactivated by the KM 0, 1
DisableParmOverrides
Appendix B
211
Table 50
ServiceCollWaitTime
60
applicationClass_AnnotationMode
NA
The annotation mode is set through the PATROL Admin => Configure Annotation Mode menu command. clusterInstance_CluDBBackupPath stores backup path for the Cluster database. The path is not set by default, and therefore the BackupClusterDatabase parameter is offline. The path is set through the Quorum Admin (MCS_Quorum) => Set Backup Path menu command. list of file clusterInstance_FileShareExclusion stores excluded file shares. If a file List share has been excluded, then it will shares not be monitored by the FileShareUnAvailable parameter. Excluded file shares are displayed in the Desktop tree and data is collected from them by the ResourceStatus parameter. You can exclude file shares through the PATROL Admin (MCS_Groups) => Maintain Exclusion List => Exclude File Shares menu command. NA directory path NA
212
Table 50
clusterInstance_ResourceExclusion stores excluded resources. If a List resource has been excluded, then the resource is not monitored and an instance is not created. You can exclude resources through the PATROL Admin (MCS_Groups) => Maintain Exclusion List => Exclude Resources menu command. clusterInstance_UpTimeBaseLine stores the start date and time for the ClusterAvailability parameter. You can set the start date and time through the PATROL Admin (MCS_Cluster) => Set Available Start Date menu command.
list of resources NA
time in seconds NA
Appendix B
213
Table 50
hostName_LogMonKeyAlarm
stores keywords that the KM searches list of for in the cluster log file. If any of the keywords keywords are found, the ClusterLogFileError parameter sends an alarm. Define the keywords through the PATROL Admin (MCS_Nodes) => Maintain Keywords menu command. By default, no keywords are defined, and the parameter is offline.
NA
hostName_LogMonKeyDate
time in seconds NA stores the date from which the KM searches for defined keywords in the cluster log file. If any of the keywords are found, the ClusterLogFileError parameter sends an alarm or warning. Define the date and keywords through the PATROL Admin (MCS_Nodes) => Maintain Keywords menu command. By default, no date or keywords are defined, and the parameter is offline.
214
Table 50
MenuCmdROMode
NA
MonitoredClusterList
NA
UptimeCollWaitTime
300
Appendix B
215
ScheduledServers
/MQ_QUEUES/ JournalMsgCountThreshold JournalMsgSizeThreshold QueueMsgCountThreshold QueueMsgSizeThreshold the number of messages currently in 0-999999 the queue the number of kilobytes used by all messages in the queue the number of messages in the journal queue the size in kilobytes of all messages in the journal queue 0-2000000 0-999999 0-2000000 450000 1600000 450000 1600000
216
Appendix B
217
/Perfmon/NT_PERFMON_WIZARD/object/counter AlarmMax AlarmMin WarnMax WarnMin /Perfmon/NT_WMI/ Parameters /Perfmon/NT_WMI/name Query AlarmMax AlarmMin WarnMax WarnMin WQL query used in the created NT_WMI parameter string NA NA NA NA NA comma-separated list of NT_WMI parameters comma separated list NA the upper-level alarm threshold for a any integer specific counter instance the lower-level alarm threshold for a any integer specific counter instance the upper-level warning threshold for a specific counter instance the lower-level warning threshold for a specific counter instance any integer any integer NA NA NA NA
the upper-level alarm threshold for a any integer specific NT_WMI parameter the lower-level alarm threshold for a any integer specific NT_WMI parameter the upper-level warning threshold for a specific NT_WMI parameter the lower-level warning threshold for a specific NT_WMI parameter any integer any integer
218
/RecoveryActions/application class/instance/parameter/ text description NA NA NA Help topic ID associated with the recovery integer action. This variable is used internally. The mode under which the recovery action 1, 2, 3 runs:
I I I
Run automatically (1) Run only with operator confirmation (2) Do not execute (3)
For more information about these modes, see Configuring built-in native recovery actions on page 120. Suspend whether to temporarily pause the recovery 0 = no action 1 = yes the amount of time PATROL waits for confirmation to run the recovery action. If you do not provide confirmation within the allotted time, PATROL does not run the recovery action. number of seconds NA
Wait
NA
Appendix B
219
These PATROL for Microsoft Windows Servers predefined rulesets include the following configuration settings:
I I I I I
preloaded KMs services whose process monitoring is enabled processes that are monitored Windows events that are monitored additional Windows Performance Monitor counters that are monitored (added as parameters beneath the NT_PERFMON_WIZARD application class)
NOTE
PATROL automatically monitors services whose startup property is automatic. However, PATROL monitors only whether the service is available. When process monitoring is enabled for the service, PATROL also monitors how much memory and CPU a service executable consumes. In the ruleset descriptions in this chapter, the services whose process monitoring is enabled are noted.
220
To edit SMS rulesets before applying 1 In a text editor, open the files Primary_Site_Role.cfg and Site_Role.cfg. 2 Replace all occurrences of %SITECODE% with the uppercase 3-character SMS site
code.
For SMS 2.x Servers cimv2\\sms For SMS 2003 Servers sms
Rulesets are provided for the server roles shown in Table 55. Figure 4 on page 222 shows these rulesets as they appear in the PATROL Configuration Manager interface. Table 55
Role File server ruleset Print server ruleset Application server ruleset Mail server ruleset Terminal server ruleset
Appendix B
221
Table 55
Role
Remote access/VPN PRU_RasVpnServer.cfg server ruleset DNS server ruleset Streaming media server ruleset PRU_DNSServer.cfg PRU_MediaServer.cfg
Figure 4
222
Ruleset reference
The following section describes the ruleset configuration settings. The rulesets define monitoring that is enabled beyond what is enabled by default in the KM. The configuration variables (rules) for each type of ruleset are stored in the agent configuration database in the location shown in Table 56. For more information about the specific configuration variables associated with each type of configuration setting, see the page referenced in Table 56. Table 56 Configuration variable locations
Location of configuration variable(s) (rules) \AgentSetup\preloadedKMs See also NA
.
Configuration setting Preloaded KMs Services with process monitoring enabled Processes monitored Windows events monitored Additional Windows PerfMon counters or WMI objects monitored
\PSX_P4WinSrvs\PWK_PKMforMSWinOS_config\ServiceMonitori page 192 ng\ServiceList\servicename on page 192 \PSX_P4WinSrvs\PWK_PKMforMSWinOS_config\ProcessMonitori page 191 ng\ProcessConfigurationList\processname \PSX_P4WinSrvs\PWK_PKMforMSWinOS_config\EventLogMonit oring\eventlog\EventFilters\filtername \PerfMon\NT_PERFMON_WIZARD\countername (The default polling interval for all added PerfMon or WMI parameters is 10 minutes, unless otherwise noted.) page 195 page 218
NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH
Appendix B
223
NOTE
An asterisk indicates that all KMs that start with the stem are included. For example, NT_CPU* indicates both NT_CPU and NT_CPU_CONTAINER.
COM_* NT_EV* NT_PERFMON* World Wide Web Publishing Service (process monitoring enabled) IIS Admin Service Simple Mail Transport Protocol (SMTP) Service FTP Publishing Service Network News Transfer Protocol (NNTP) Service Distributed Transaction Coordinator COM+ System Application (process monitoring enabled) COM+ Event Service (process monitoring enabled) Remote Services (COM and RPC) inetinfo.exex Error events from .NET Runtime source (application event log) Error and warning events from ASP.NET (application event log) Active Server Pages Errors/Sec ASP.NET Requests Rejected ASP.NET Requests Queued ASP.NET Application Errors Unhandled During Execution/Sec ASP.NET Application Errors Total/Sec .NET CLR Data Sqlclient: Total # failed commands .NET CLR Exceptions # of Exceps Thrown/sec .NET CLR Jit Standard Jit Failures .NET CLR Loading Rate of Load Failures Web Service Current Blocked Async I/O Requests Web Service Locked Errors/sec Web Service Not Found Errors/sec
Services with Process Monitoring Enabled Processes Monitored Windows Events Monitored
I I I I I I I I I I I I I I I
I I
224
Preloaded KMs (PRU_TerminalServe r.kml) Services with Process Monitoring Enabled Processes Monitored Windows Events Monitored Additional Perfmon Counters Monitored
NT_EV* NT_PERFMON* Terminal Services (process monitoring enabled) Terminal Services Session Directory (process monitoring enabled)
I I
None
I I I I I I I
Error and warning events from TermService (system event log) Error and warning events from TermServLicensing (system event log) Error and warning events from TermServDevices (system event log) Terminal Services Active Sessions Terminal Services Inactive Sessions Terminal Services Total Sessions System Processes
Preloaded KMs (PRU_RasVpnServer.kml) Services with Process Monitoring Enabled Processes Monitored Windows Events Monitored Additional Perfmon Counters Monitored
NT_EV* NT_PERFMON*
Remote Access Service (process monitoring enabled) None Error and warning events from Remote Access (system event log)
I I
Appendix B
225
Preloaded KMs (PRU_PrintServer.kml) Services with Process Monitoring Enabled Processes Monitored Windows Events Monitored Additional Perfmon Counters Monitored
NT_EV* NT_PRINT*
Spooler spoolsv.exe Error and warning events from Print source (system event log) None
Preloaded KMs (PRU_DomainServer.kml) Services with Process Monitoring Enabled Processes Monitored
I I
Error and warning events from NT File Replication Service (file replication service event log) Error and warning events from source LSASERV (system event log) Error and warning events from source SAM (system event log) Error and warning events from source NetLogon (system event log) Error and warning events from source Windows Time (system event log) Error and warning events from source KDC (system event log) Error and warning events from source UserEnv (application event log) Error and warning events from DNS API (system event log)
None
226
I I I I I I
NT_DFS* NT_EV* NT_DOMAIN NT_MEMBER_SERVER NT_PHYSICAL_DISKS* Netlogon dmserver services.exe lsass.exe svchost.exe (with any argument) Error and Warning events from DfsSvc (system event log) Error and Warning events from NtFrs (file replication service event log)
Processes Monitored
I I I
None
NT_EV* NT_PERFMON* NntpSvc Pop3Svc (process monitoring enabled) RpcSs (process monitoring enabled) SMTPSVC (process monitoring enabled) Error and warning events from Pop3Svc (application event log) Error and warning events from SMTPSvc (system event log) POP3 Service Messages delivered/sec POP3 Service Sockets in use SMTP NTFS Store Driver Messages in the queue directory SMTP Server Connection Errors/sec SMTP Server Outbound Connections Refused
Services with Process Monitoring Enabled Processes Monitored Windows Events Monitored
I I
None
I I I I I
I I
Appendix B
227
Preloaded KMs (PRU_DNSServer.kml) Additional Active Parameters Services with Process Monitoring Enabled Processes Monitored
I I
I I I I
Error and warning events from source DNS (DNS event log) Error and warning events from source DNS API (system event log) Error and warning events from source DNS Cache (system event log) DNS Caching memory DNS Dynamic Update Received/sec DNS Total Query Received/sec DNS Database Node Memory DNS Dynamic Update Written to Database/sec
I I
Preloaded KMs (PRU_WinsServer.kml) Additional Active Parameters Services with Process Monitoring Enabled Processes Monitored Windows Events Monitored Additional Perfmon Counters Monitored
I I
None WINS None Error and warning events from WINS (system event log) None
228
Preloaded KMs (PRU_DhcpServer.kml) Additional Active Parameters Services with Process Monitoring Enabled Processes Monitored Windows Events Monitored Additional Perfmon Counters Monitored
I I
None DHCPServer None Error and Warning from DHCPServer (system event log) None
NT_EV* NT_PERFMON*
None
Services with Process Monitoring WMServer Enabled Processes Monitored Windows Events Monitored None Error and Warning from WMServer (Application Event log)
I I I I
Windows Media Services Current Streaming Players Windows Media Service Current Connected Players Windows Media Services Current Connection Queue Length Windows Media Services Current Stream Error Rate
Appendix B
229
Table 68
MSSQLSERVER SMS Executive SMS Site Backup Services with Process Monitoring SMS Site Component Manager SMS SQL Monitor Enabled sitecomp.exe (with any argument) smsdbmon.exe (with any argument) smsexec.exe (with any argument) sqlservr.exe (with any argument) Error, warning, and information events from source SMS (application event log)
I I I I I I I I I I I I I I I I I I I I I I
SMS Discovery Data Manager Total DDRs Enqueued SMS Discovery Data Manager Total DDRs Processed SMS Discovery Data Manager DDRs Processed/minute SMS In-Memory Queues Total Objects Dequeued SMS In-Memory Queues Total Objects Enqueued SMS Inventory Data Loader Total MIFs Enqueued SMS Inventory Data Loadaer Total MIFs Processed SMS Inventory Data Loader MIFs Processed/minute SMS Software Inventory Processor Total SINVs Enqueued SMS Software Inventory Processor Total SINVs Processed SMS Software Inventory Processor SINVs Processed/minute SMS Standard Sender Average Bytes/sec SMS Standard Sender Sending Thread Count SMS Standard Sender Total Bytes Attempted SMS Status Messages Written to SMS Database SMS Status Messages Reported to Application Event Log SMS Status Messages Replicated at Normal Priority SMS Status Messages Replicated at Low Priority SMS Status Messages Replicated at High Priority SMS Status Messages Received SMS Status Messages Processed/sec SMS Status Messages Corrupt
I I
SMS Advertisements Failed SMS Advertisements Total SMS Errors SMS Informationals SMS Machines Total SMS Packages Failed SMS Programs Failed SMS Warnings
230
SMS Executive Services with Process Monitoring SMS Site Backup Enabled SMS Site Component Manager Processes Monitored Windows Events Monitored sitecomp.exe (with any argument) smsexec.exe (with any argument) Error, warning, and information events from source SMS (application event log)
I I I I I I I I I I I I I I I I
SMS Discovery Data Manager Total DDRs Enqueued SMS Discovery Data Manager Total DDRs Processed SMS Discovery Data Manager DDRs Processed/minute SMS In-Memory Queues Total Objects Dequeued SMS In-Memory Queues Total Objects Enqueued SMS Standard Sender Average Bytes/sec SMS Standard Sender Sending Thread Count SMS Standard Sender Total Bytes Attempted SMS Status Messages Written to SMS Database SMS Status Messages Reported to Application Event Log SMS Status Messages Replicated at Normal Priority SMS Status Messages Replicated at Low Priority SMS Status Messages Replicated at High Priority SMS Status Messages Received SMS Status Messages Processed/sec SMS Status Messages Corrupt
Appendix B
231
NOTE
To use the PATROL Configuration Manager to view or manage a PATROL agent configuration, the PATROL KM for Event Management must be loaded on the PATROL Agent machine. For more information about loading KMs, see Loading the PATROL for Microsoft Windows Servers KMs on page 85.
To copy configuration changes using PCM 1 Using the PATROL Configuration Manager, perform a get on the PATROL Agent. 2 Configure the PATROL Agent as desired. 3 Using the PATROL Configuration Manager, perform a get to obtain the new
PATROL Agent configuration.
4 In PATROL Configuration Manager, compare the last 2 configurations. 5 Save the differences between the 2 agent configuration as a new rule set. 6 Apply this rule set to the other PATROL Agents.
For more detailed information about using the PATROL Configuration Manager, see the PATROL Configuration Manager User Guide or the PATROL KM for Event Management User Guide.
232
WARNING
When creating rules manually within PATROL Configuration Manager, you must follow the syntax guidelines discussed here and avoid typos. Failure to do so could result in unpredictable behavior.
Syntax guidelines
When manually creating rules, you must substitute special codes for certain characters when those characters are part of a configuration variable name or value. These characters are used for specific purposes within pconfig. For example, the comma is used to separate values. For more information, see Table 70. Table 70
Character comma (,)
slash (/)
(SL)
(EQ)
double quote ()
(QU)
Appendix B
233
234
variable_list = FilterEnabled,FilterDescription,EventType,Annotation,EventReport, RetainEventDescriptions,Scheduling,AcknowledgeBy,ConsolidationNumber,ConsolidationTi me,ConsolidateEventTypes,IncludeAllSources,IncludeAllEventIds,IncludeAllUsers,IncludeA llCategories,IncludeAllStrings,CreateInstance If you are unsure how or when to use the variable_list variable, use a PATROL console to configure monitoring and then examine the variable_list rules that are created.
1 Right-click the folder where you want to add the rule and select New => Ruleset.
A new ruleset is created called NewRuleSet.
2 Rename the ruleset. 3 Right-click the new ruleset and select New Rule. 4 From the Ruleset dialog, enter the ruleset, operation, and variable. For more
information about what to enter, see the examples that follow.
monitor the DHCP Client service restart the start the service when it stops generate a PATROL Warning when the service is stopped enable the monitoring of the process associated with this service
Appendix B
235
To manually create this configuration, you would create the rules shown in Table 71. For more information about the configuration variable specified in these rules, see PATROL for Windows Servers configuration variables on page 190. Table 71
Rule
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonitoring/ Replace ParentDefinedProcessList/child_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonitoring/ Replace child_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ServiceMonitoring/ Replace ServiceList/Dhcp/Alarm /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ServiceMonitoring/ Replace ServiceList/Dhcp/Monitor /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ServiceMonitoring/ Replace ServiceList/Dhcp/variable_list
monitor rtserver process with argument -service terminate the process when the process CPU% exceeds a threshold value (defined by the AlarmThreshold variable) for 15 minutes generate a PATROL alarm when the process is not running do not generate a PATROL alarm when the process is running
236
To manually create this configuration, you would create the rules shown in Table 72. For more information about the configuration variable specified in these rules, see PATROL for Windows Servers configuration variables on page 190 Table 72
Rule
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/ArgumentList /list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/ArgumentList /variable_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/ProcessName /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/child_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/variable_list
list
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/child_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/EnableAlarmI fProcessDown /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/EnableAlarmI fProcessStarts /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ProcessMonito Replace ring/ProcessConfigurationList/RTSERVER_SERVICE/TimeLimitFor KillRunAwayProcess
15
Appendix B
237
create an event filter named Example with the description Event Filter Example monitor only Warning and Error event types; do not consolidate event types when reporting. Report Warning and Error events separately. monitor events from application sources PerfDisk and PerfProc monitor event IDs 100 through 154 monitor events generated under the username of bhunter monitor events that have the test string missing in the event text monitor events in any event category choose the option to write event details to a text parameter choose the option to report multiple events as one event when 5 or more events occur within 30 seconds choose the option to notify PATROL immediately when an event filter matches the filter criteria when in alarm, remain in alarm until acknowledged by an operator
238
To manually create this configuration, you would create the rules shown in Table 73. For more information about the configuration variable specified in these rules, see PATROL for Windows Servers configuration variables on page 190. Table 73
Rule
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/AcknowledgeBy /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/Annotation /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/ConsolidateEventTypes /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/ConsolidationNumber /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/ConsolidationTime /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/CreateInstance /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/EventIdList/list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/EventIdList/variable_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/EventReport /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/EventType /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/FilterDescription /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/FilterEnabled /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/IncludeAllCategories /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/IncludeAllEventIds /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/IncludeAllSources /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/IncludeAllStrings /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/IncludeAllUsers /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/RetainEventDescriptions /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/Scheduling /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/SourceList/variable_list Appendix B
239
Table 73
Rule
/PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/StringList/list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/StringList/variable_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/UserList/list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/UserList/variable_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/child_list /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/EventLogMonit Replace oring/Application/EventFilters/Example/variable_list
240
To manually create this configuration, you would create the rules shown in Table 74.
NOTE
When you change parameter thresholds through the PATROL Configuration Manager or through PATROL KM for Event Management, the changes are stored externally in the pconfig database, not in the KM. To change parameter thresholds or poll times in this manner, you must have the PATROL KM for Event Management loaded on the PATROL Agent. For more information about loading KMs, see Loading the PATROL for Microsoft Windows Servers KMs on page 85.
For more information about the this rule, see the detailed description in Table 75. Table 74
Rule /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/ NT_CPU/__ANYINST__/CPUprcrProcessorTimePercent
The following table provides a detailed description of the THRESHOLDS configuration rule. Table 75
Item /AS/EVENTSPRING /PARAM_SETTINGS /THRESHOLDS /NT_CPU /__ANYINST__
CPUprcrProcessorTime parameter name Percent 1 0 0 0 indicates that the parameter is active Border settings indicates that the border range is inactive the border begin range the border end range
Appendix B
241
Table 75
Item 0 0 0 1 80 85 0 0 1 1 85 100 0 0 2
242
Appendix
C
244 244 245 246 247 248 249 249 250 250 250
Appendix C
243
244
Component and .kml PATROL KM for Microsoft Windows OS NT_LOAD.kml Note: NT_LOAD.kml includes NT_BASE.kml
Appendix C
245
The NT_LOAD.kml file includes the NT_BASE.kml file, which loads the application classes shown in Table 79. Table 79 PATROL KM for Microsoft Windows OS NT_BASE.kml file
Application classes NT NT_OS NT_CACHE NT_CPU NT_CPU_CONTAINER NT_HEALTH NT_LOGICAL_DISKS NT_LOGICAL_DISKS_CONTAINER NT_MEMORY NT_NTFS_MOUNT NT_NTFS_MOUNT_CONTAINER NT_NTFS_QUOTA NT_NTFS_QUOTA_CONTAINER NT_PAGEFILE NT_PAGEFILE_CONTAINER NT_SYSTEM PATROL_NT
246
Component and .kml PATROL KM for Microsoft Windows Domain Services (uses NTD.kml)
Appendix C
247
Component and .kml PATROL KM for Microsoft Cluster Server (uses MCS_Load.kml)
248
Component and .kml PATROL KM for Microsoft Message Queue (uses MSMQ.kml)
Component and .kml PATROL Wizard for Microsoft Performance Monitor and WMI (NT_PERFMON_WIZARD.kml)
Appendix C
249
NOTE
An asterisk indicates that all KMs that start with the stem are included. For example, NT_CPU* indicates both NT_CPU and NT_CPU_CONTAINER.
250
Table 88
.kml
PRU_ApplicationServer.kml
NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH COM_* NT_EV* NT_PERFMON* NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_EV* NT_PERFMON* NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_EV* NT_PERFMON*
PRU_TerminalServer.kml
I I I I I I I I I I I I I I
PRU_RasVpnServer.kml
I I I I I I I I I I I I I I
Appendix C
251
Table 88
.kml
PRU_PrintServer.kml
NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_EV* NT_PRINT* NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_EV* NT_DOMAIN NT_MEMBER_SERVER AD_AD* NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_DFS* NT_EV* NT_DOMAIN NT_MEMBER_SERVER NT_PHYSICAL_DISKS*
PRU_DomainServer.kml
I I I I I I I I I I I I I I I I
PRU_FileServer.kml
I I I I I I I I I I I I I I I I I
252
Table 88
.kml
PRU_MailServer.kml
NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_EV* NT_PERFMON* NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_DNS_2000 NT_DOMAIN NT_MEMBER_SERVER NT_EV* NT_PERFMON* NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_DOMAIN NT_MEMBER_SERVER NT_EV* NT_WINS*
PRU_DNSServer.kml
I I I I I I I I I I I I I I I I I
PRU_WinsServer.kml
I I I I I I I I I I I I I I I I
Appendix C
253
Table 88
.kml
PRU_DhcpServer.kml
NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_DOMAIN NT_MEMBER_SERVER NT_EV* NT_DHCP* NT NT_OS NT_CACHE NT_CPU* NT_MEMORY NT_PAGEFILE* NT_SYSTEM NT_LOGICAL_DISK* PATROL_NT NT_SERVICES* NT_PROCESS* NT_HEALTH NT_EV* NT_PERFMON*
PRU_MediaServer.kml
I I I I I I I I I I I I I I
254
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
Symbols
%PATROL_CACHE% 60 %PATROL_HOME% 60 .kml COM.kml 84, 249 EVENT_MANAGEMENT.kml 85 HISTORY.kml 84, 251 LOG.kml 85 MSMQ.kml 84, 250 MWD_ACTIVE_Directory_MN.kml 85 NT_BASE 246 NT_LOAD.kml 85, 245 NT_PERFMON_WIZARD.kml 85 NTD.kml 85, 248 .kml files list of 84 vs. .km files 83 __ANYINST__ variable 241, 242 _CollectionStatus parameter 42, 174 services to monitor 235 WMI parameters 135 address book monitoring 21 addresses default 128 email, specifying 131 administrator rights 94 AdPerfCollector parameter 181 advanced user rights, required 40 agents assigning notification servers to 129 configuration variables 189219 configuring 129130 configuring in a cluster 156 PATROL 31 persistent connection to 130 Alarm variable 194 AlarmMax variable 218 AlarmMin variable 218 alarms acknowledging 175 generating 109, 115 tuning 177 AlarmThreshold variable 115, 191 alerts reducing number of 174 troubleshooting 177 allow log on locally (user right) 41 allowsendparamonly variable 178 AnnotateProcCount variable 202 AnnotateProcStatus variable 202 AnnotateTopProcs variable 202 AnnotateValueChange variable 204 Annotation variable 197, 239 AnnotationMode variable 212 application classes NT_CompositeColl 116 NT_DHCP 37, 150 NT_DNS 150 NT_FTP 203 NT_ICMP 204 NT_IP 204 NT_IPX 204 NT_LOGICAL_DISK 94 NT_NETBEUI 204 NT_NETBIOS 204
Numerics
560/562 events 175
A
account requirements PATROL KM for Cluster Server 44, 70 PCC 157 AccountInfo variables 211 accounts requirements 91 setting up for installation 39 Windows 40 AcknowledgeBy variable 197, 239 acknowledging alarms 175 Act as part of operating system (user right) 40, 95 activating parameters 242 Active Directory 19 ActiveX control 124 adding event filters 238 Performance Monitor (PerfMon) counters 134 processes to monitor 111, 236 rules 235
257
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
NT_PROCESS 111 NT_REMOTE_SERVERS 150 NT_SERVICES 94 NT_SHARES 150 NT_TCP 204 NT_TRUST 150 NT_UDP 204 NT_WINS 150 application server, rulesets for monitoring 221 arguments, process 115 arsAction variable 177 AS_AVAILABILITY application 179 AS_CHANGESPRING.kml 64 AS_EVSLocalAlertNotify.bat editing 125 requirements for using 125 AS_EVSLocalAlertNotify.pl 125 Attended Mode Dialog Timeout field 122 auditing, disabling 175 authentication support 21 AutoDiscoveryTimeLimit variable 191 automatic process monitoring 110 AutoRestart variable 110, 194 availability, monitoring 179 CheckPoint variable 196 child_list variable 234 CluDBBackupPath variable 212 cluster administrator account 44, 70, 157 cluster.exe 70 ClusterLogFileError parameter 214 collection method 138, 139, 140 CollectionCount variable 191, 202 colormap option 72 COM.kml 84, 249 command-line arguments 115 commas, escaping 233 components KM files 244251 PATROL Adapter for Microsoft Office 30 PATROL Agent for Microsoft Windows Servers 31 PATROL Cluster Configuration Wizard 26 PATROL Cluster Configuration Wizard (PCC) 26 PATROL History Loader KM 30 PATROL KM for Cluster Server 26 PATROL KM for Event Management 29 PATROL KM for Log Management 28 PATROL KM for Microsoft Cluster Server 26 PATROL KM for Microsoft COM+ 27 PATROL KM for Microsoft Message Queue 27 PATROL KM for Microsoft Windows Active Directory 19 PATROL KM for Microsoft Windows Domain Services 25 PATROL KM for Microsoft Windows OS 18 composite parameters, creating 116 compressing the DHCP database 93 configuration variables 189219 configurations, component-based PATROL KM for History Loader 251 PATROL KM for Microsoft COM+ 249 PATROL KM for Microsoft Message Queue (MSMQ) 250 PATROL KM for Microsoft Windows Domain Services 248 PATROL KM for Microsoft Windows OS 245 configuring composite parameters 116 custom parameters 116 e-mail notification 123 event log monitoring 108 event monitoring 98 in PCM, event monitoring 238 in PCM, process monitoring 236 in PCM, service monitoring 235 monitoring of text files 137 PATROL in a cluster 156 PATROL KM for Microsoft Windows OS 95116 process control 114 process monitoring 110115 quotas 94 remote agents 129130
B
backing up before migration 63 backup domain controllers, monitoring 25 backup notification servers 127 BackupClusterDatabase parameter 212 BackupDir variable 195 batch file 125 BDCADD variable 206 BDCDEL variable 206 blackouts 177 Blat defined 123 version tested with 124 BMC Software, contacting 2 Bourne shell 72 Bypass traverse checking user right 95
C
C shell 72 catalog, event 179 changing account rights 41 security levels 49 system monitoring 96 thresholds and poll times 241 characters, special 233 charting PATROL data 147 CheckIPResourceColl parameter 213
258
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
service monitoring 108?? Windows event monitoring 98 connection, persistent 130 ConsolidateEventTypes variable 102, 197, 239 ConsolidationNumber variable 197, 239 ConsolidationTime variable 197, 239 Core Active Directory service 22 core Active Directory service 23 Counters variable 218 counters, Performance Monitor 180 CreateInstance variable 197 creating custom parameters 116 rules 235 WMI parameters 30 custom installation option 50 customer support 3 customizations migrating manually 66 customized PSL, migrating 67 customizing monitoring of counters 133 scripts 125126 text log monitoring 136 thresholds 180 parameters 242 process monitoring 113 disconnecting DFS users 93 discovery, problems with 174 diskperf 97 disks, monitoring 96 Distributed File System (DFS) 25 DNS name registration 22 DNS reports 150 DNS server, monitoring 23 dns.exe 228 domain controllers rulesets for monitoring 222 domain controllers, monitoring 25 Domain Name Service (DNS) monitoring 25 rulesets 222 DomainInclusionList variable 214 DomainNamingMasterConnStatusSched variable 208 double quotes, escaping 233 Dynamic Host Configuration Protocol (DHCP) 25 dynamic update 23
E
editing notification scripts 125 rulesets 221 ELMError parameter 101 ELMErrorNotification parameter 101, 175 ELMEvFileFreeSpacePercent parameter 119 ELMFailureAudit parameter 101 ELMFailureAuditNotification parameter 101, 175 ELMInformation parameter 101 ELMInformationNotification parameter 175 ELMNotification parameter 101, 175 ELMOtherTypes parameter 101 ELMOtherTypesNotification parameter 175 ELMRptOfNotification parameter 103 ELMRptOfOtherTypes parameter 103 ELMStatus parameter 101, 102 ELMSuccessAudit parameter 101 ELMSuccessAuditNotification parameter 175 ELMWarning parameter 101 ELMWarningNotification parameter 101, 175 e-mail notification 123 EnableAlarmIfProcessDown variable 192 EnableAlarmIfProcessStarts variable 192 enabling event filters 107 event log monitoring 99 parameters 242 environment variables LANG 72 PATH 72, 73 PATROL_BROWSER 73
D
database, parameter history 30 deactivating parameters 242 debug programs (user right) 40 default email account 128 defining notification servers 126 remote agents 126 dependencies 86 deploying settings 127 DestroyAcknowledgeProcess variable 202 DFS (Distributed File System) 25 DFS users, disconnecting 93 DfsConnectionPercent parameter 120 DHCP (Dynamic Host Configuration Protocol) 25 DHCP reports 150 DHCPADD variable 206 DHCPBAK variable 206 DHCPDEL variable 206 diagnosing problems 173184 directory replication 20 DisableAnnotation variable 192, 202, 204 DisableAnnotations variable 208 DisableEventConfig variable 208 DisableServiceRestart variable 110, 192 disabling event filters 107 event log monitoring 99 KMs 152
259
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
PATROL_CACHE 60 PATROL_HOME 60 setting for Help browser 72 setting for the browser 72 equal sign, escaping 233 error messages 183 escaping special characters 233 event catalog 179 event logs monitoring, enabling 97 troubleshooting 175 viewing 116 event monitoring configuring in PCM 238 Core Active Directory service 22 domain controller health 22 file replication service and group policy 22 Kerberos 22 Netlogon 22 time synchronization service 22 EVENT_MANAGEMENT.kml 251 EventLogMonitoring BackupDir variable 195 ExclusionList/list variable 196 IncludeAll variable 195 InclusionList/list variable 195 EventReport variable 197, 239 events monitoring 98 reducing 174 EventType variable 102, 198, 239 EvRptOfError parameter 103 EvRptOfFailureAudit variable 103 EvRptOfInformation parameters 103 EvRptOfStatus parameters 103 EvRptOfSuccessAudit parameters 103 EvRptOfWarning parameter 103 eXceed 72 Excel, Microsoft 94 ExclusionList/list variable 196, 202, 203, 204 expressions, regular 110 ForwardFilteredNTEventstoPEM variable 196 FSMO monitoring 21 FTP/Active variable 203
G
graphing PATROL data 147 group policy monitoring 22
H
HighThresholdOnEvents variable 205 history reports 149 HISTORY.kml 84, 251 HPFS file system 37
I
ICMP/Active variable 204 IdleServerTime variable 206 InactiveonMissingPerfObj variable 191 IncludeAll variable 195, 202, 203, 204 InclusionList list/variable 203 InclusionList/list variable 195, 202, 203, 204 increase quotas (user right) 40 inetinfo.exe 224 InfrastructureMasterConnStatusSched variable 209 installation backing up before migration 63 custom option 50 log files 183 PATROL KM for Cluster Server account requirements 44, 70 PATROL KM for Cluster Server overview 67 preparing for 46 setting up installation accounts 39 system requirements 35, 36 typical option 49 verifying requirements 35 Windows account requirements 40 Installation logs 183 installing clearing cache 65 for the first time 50 upgrading from an earlier version 58 where to install KMs 47 where to install PATROL Agent 47 Instances variable 218 integration with Blat 123 intrasite/intersite monitoring 20 IP/Active variable 204 IPExclusionList variable 213 IPX/Active variable 204 IterationCount variable 205
F
failover, cluster 26 FAT file system 37 file replication service and group policy 23 file server, rulesets for monitoring 221 file systems, supported 37 FileShareExclusionList variable 212 filter, event monitoring 98 FilterDescription variable 198, 239 FilterEnabled variable 108 first time installation 50 Flexible Single Master Operations (FSMO) 21 ForwardAllNTEventstoPEM variable 196
260
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
J
job objects missing 174 monitoring 97 JobObjectMonitoring CollectionCount variable 202 ExclusionList/list variable 202 IncludeAll variable 202 InclusionList/list variable 202 JournalMsgCountThreshold variable 216 JournalMsgSizeThreshold variable 216
lsass.exe 227
M
mail servers, rulesets for monitoring 221 Make Connection Persistent option 130 managed system 19 manual migration of KM customizations 66 process monitoring 110 ManualAcknowledge variable 202 MAPI scripts 125 MaxRecords variable 200 MaxResourceIdleRetainPeriod variable 195 MaxShares variable 207 MaxUsers variable 207 MBRADD variable 206 MBRDEL variable 206 MBREL variable 206 media, streaming 222 MemoryContentionThreshold variable 205 MenuCmdROMode variable 215 messages, error log 183 Microsoft Excel 94, 148 Microsoft Message Queue (MSMQ) 27 Microsoft Transaction Server COM+ 27 migrating customized PSL 67 determining if KM is migratable 58 from an earlier version of the KM 58 KM customizations manually 66 Mode variable 219 monitor requirements 36 Monitor variable 194 MonitoredClusterList variable 215 monitoring Active Directory 19 availability of agents 179 backup domain controllers 25 clusters 26 domain controllers 25 enabling and disabling 96 event logs 97 events 98, 108 files 108 job objects 97 logical disks 97 logical or physical disk drives 97 logs 108 network interfaces 97 network protocols 97 pagefiles 97 physical disks 96 printers 97 processes 110 processors 96
K
Kerberos 22, 24 KM configuration variables 189219 KM customizations migrating manually 66 KMs deploying 16 determining if migratable 58 determining versions of 184 included with product 243251 installing individual 50 installing QuickStart packages 49 loading 8587 preloading 84 unloading 152 upgrading from an earlier version 58 where to install 47 Korn shell 72
L
LANG environment variable 72 LDAP monitoring 21 LDldFreeSpacePercent parameter 119 license, required 36 loading KMs 8587 log files, monitored by default 137 Log on as a service (user right) 41 Log on as batch job user right 94 LOG.kml 85 logical disks, monitoring 97 LogicalDiskMonitoring ExclusionList/list variable 204 IncludeAll variable 204 InclusionList/list variable 204 login accounts requirements 39 Windows 39 logs event, monitoring 97 installation 183
261
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
service executables 109 services 108 strings 108 text files 137 MonitorManualServices variable 193 MonitorNotRespond variable 194 MonitorProcess 194 MonitorProcess variable 202 MSMQ.kml 84, 250 MsPatrolAgentStatus parameter 120 MWD_ACTIVE_Directory_MN.kml 85 NT_LOAD.kml 39, 85, 245 NT_LOGICAL_DISK application class 94 NT_NETBEUI application class 204 NT_NETBIOS application class 204 NT_PERFMON application class 85 NT_PROCESS application class 111, 174 NT_SERVICES application class 94 NT_TCP application class 204 NT_UDP application class 204 NTD.kml 85, 248 NTFS file system 37
N
Name variable 218 Net Logon 22, 24 NETBEUI/Active variable 204 NETBIOS/Active variable 204 Netscape Navigator 71 network interfaces, monitoring 97 network protocols, monitoring 97, 176 NetworkInterfaceMonitoring ExclusionList/list variable 203 IncludeAll variable 203 InclusionList/list variable 203 new PATROL users easy install option 49 installing for the first time 50 notification scripts, using 123126 server 126 notification scripts customizing 125 editing 125 specifying 128 notification servers benefits of 127 configuring 126128 defining 126 primary and backup 127 providing security for 127 notification targets, defining 128 notification, e-mail 123 NOTIFICATION_SERVER1 variable 129 NOTIFICATION_SERVER1.defaultAccount variable 129 NOTIFICATION_SERVER2 variable 129 NotifiedEvents parameter 179 NotRespondCmd variable 194 NT authentication support 21 NT_BASE.kml 39, 246 NT_CompositesColl application class 116 NT_DHCP application class 37 NT_FTP application class 203 NT_ICMP application class 204 NT_IP application class 204 NT_IPX application class 204
O
Objects variable 218 operating system, monitoring 95 output window, system 183 OverrideAutoConfigUpdate variable 205 OverrideGlobalServiceMonitoring variable 194 OverrideGlobalServiceRestart variable 110, 194 OverrideParameterAutoActivate variable 195, 202, 205 OverrideParameterFileFreeSpacePctAutoActivate variable 196 OverrideSummaryAutoCreate variable 176, 196
P
PACFG (PATROL Agent Configuration) utility 178 PagefileMonitoring ExclusionList/list variable 203 IncludeAll variable 203 InclusionList/list variable 203 pagefiles, monitoring 97 parameters 178 _CollectionStatus 42 activating and deactivating 242 AdPerfCollector 181 BackupClusterDatabase 212 CheckIPResourceColl 213 ClusterLogFileError 214 composite 116 creating 30 creating e-mail notifications for 123 creating PerfMon-based 134 creating WMI 135 customizing 116 data, storing and analyzing 30 DfsConnectionPercent 120 ELMError 101 ELMErrorNotification 101, 175 ELMEvFileFreeSpacePercent 119 ELMFailureAudit 101 ELMFailureAuditNotification 101, 175 ELMInformation 101 ELMInformationNotification 101, 175
262
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
ELMNotification 175 ELMOtherTypes 101 ELMOtherTypesNotification 175 ELMRptOfNotification 103 ELMRptOfOtherTypes 103 ELMStatus 101 ELMSuccessAudit 101 ELMSuccessAuditNotification 175 ELMWarning 101 ELMWarningNotification 101, 175 EvRptOfError 103 EvRptOfFailureAudit 103 EvRptOfInformation 103 EvRptOfSuccessAudit 103 EvRptOfWarning 103 history, viewing 84 LDldFreeSpacePercent 119 MsPatrolAgentStatus 120 NotifiedEvents 179 PAWorkRateExecsMin 120 PROCDown 115 PROCProcessColl 115 PROCProcessorTimePercent 119 PROCStatus 115, 119, 202 RegValueChanged 204 ServiceStatus 109, 120 ShConnPercent 44, 120 SvcNotResponding 109 SvcStatus 109 troubleshooting 178 tuning 174 WMIAvailability 119, 205 WpReplicationFailures 120 Parameters variable 218 ParentInstance variable 197 PATH environment variable 73 PATROL account, creating 39 PATROL Adapter for Microsoft Office description 30 installation requirements 148 PATROL Agent configuring in a cluster 156 description 31 installing KMs to 47 where to install 47 PATROL Central - Web Edition loading KMs on 87 PATROL Central - Windows Edition 153 PATROL Configuration Manager description 16 using 232240 PATROL consoles and Netscape Navigator 71 installing KMs to 48 PATROL for Windows Operating System Monitor service 31 PATROL History Loader KM description 30 PATROL KM for Cluster Server account requirements 44, 70 architecture 68 description 26 installation overview 67 installation requirements 70 monitoring features 26 overview 67 PATROL KM for Event Management .kml files 251 configuring 123131 PATROL KM for History Loader KMs 251 PATROL KM for Microsoft COM+ report options 151 troubleshooting 95 Windows configuration 249 PATROL KM for Microsoft Message Queue KMs 250 report options 151 troubleshooting 95 PATROL KM for Microsoft Windows Active Directory description 19 installation requirements 38, 39 requirements 38, 39 troubleshooting 91 PATROL KM for Microsoft Windows Domain Services KMs 248 requirements 37 troubleshooting 92 PATROL KM for Microsoft Windows OS configuring 95116 KMs 245 requirements 37 PATROL KM for Windows Active Directory required defaultAccount permissions 43 PATROL Perform Agent 35 PATROL security overview of levels 48 requirements 36 PATROL Wizard for Performance Monitor and WMI .kml file 250 configuring 133 creating Performance Monitor parameters 134 creating WMI parameters 135 description 30 loading 133 migration 59 PATROL.conf 178 PATROL_BROWSER environment variable 73 PATROL_CACHE 60, 65 PATROL_HOME 60 PatrolAgent service 31 PAWorkRateExecsMin parameter 120 PCC (PATROL Cluster Configuration Wizard) account requirements 157
263
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
description 26 installation requirements 157 overview 156 using 158 pconfig syntax rules for 233 variables 190219 PDCEmulatorConnStatusSched variable 209 Performance Counter (PerfMon) Wizard 30 Performance Monitor counters, customizing 180 perfproc.dll 174 persistent agent connection 130 physical disks, monitoring 96 PhysicalDiskMonitoring ExclusionList/list variable 203 IncludeAll variable 203 InclusionList/list variable 203 PingCount variable 210 PingTimeout variable 210 planning installation 46 notification 126 platforms, supported 36 poll times, changing 178, 241 preloading KMs 84, 88 preparing for installation 46 Primary_Site_Role.cfg 221, 222 print server, rulesets for monitoring 221 PrinterMonitoring DisableAnnotation variable 204 ExclusionList/list variable 204 IncludeAll variable 204 InclusionList/list variable 204 printers, monitoring 97 problem resolution 173184 PROCDown parameter 115 process control, configuring 114 processes configuring in PCM 236 disabling monitoring of 113 missing 174 monitoring 110 restarting 42, 115 run-away 192 stopping 115 troubleshooting 174 ProcessMonitoring StatusSelectedColumns/list variable 191 ProcessName variable 192 ProcessorContentionThreshold variable 204 ProcessorMonitoring DisableAnnotation variable 202 ExclusionList/list variable 202 IncludeAll variable 203 InclusionList/list variable 203 processors, monitoring 96 PROCProcessColl parameter 115 PROCProcessorTimePercent parameter 119 PROCStatus parameter 115, 119, 202 product components 18 configuration tasks 95 product support 3 profile system performance (user right) 41 protocols monitoring 97 troubleshooting 176 PRU_FileServer.cfg 221 PSL, migrating 67 psx_server.xpc 200
Q
Query variable 218 QueueMsgCountThreshold variable 216 QueueMsgSizeThreshold variable 216 quotas, configuring 94 quotes, escaping 233
R
RAS (Remote Access Service) 225 recovery actions about 118 configuring 118122 troubleshooting 42 variables used for 219 redundancy 127 RegistryMonitoring InclusionList/list variable 204 regular expressions 110 RegValueChanged parameter 204 RelativeIDMasterConnStatusSched variable 209 Remote Access Service (RAS) 225 remote agents, assigning notification servers to 129 removing KMs 152 replace a process level (user right) 41 replication monitoring 20 reports 94, 149151 requirements overview 35 PATROL KM for Cluster Server 70 PATROL KM for Cluster Server account 44, 70 PATROL KM for Microsoft Windows Active Directory 38, 39 PCC 157 software 83 system 35, 36 user right 40 Windows account 40 Windows script 124
264
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
ResolveTestList variable 205 ResourceExclusionList variable 213 restarting agent 177 processes 42, 115 RetainEventDescriptions variable 239 rights, required 40, 94 rules, adding 235 rulesets applying 220 editing 221 shipped 219231 run-away processes 192 C 72 Korn 72 Site_Role.cfg 221, 222 sitecomp.exe 230, 231 slashes, escaping 233 SMS (Systems Management Server), rulesets for 221 smsdbmon.exe 230 smsexec.exe 230, 231 SMTP scripts 125 SNMP service 37 SNMP, requirements 37 spoolsv.exe 226 sqlservr.exe 230 starting services 93, 109 startup properties, service 94 StatusNumberofProcessesToDisplay variable 191 StatusSelectedColumns/list variable 191 StatusSortKey variable 191 StdEvents.ctg 179 stopping event log monitoring 99 monitoring 96 processes 115 services 93 streaming media servers, rulesets for monitoring 222 success auditing 175 Summary instance 176 support, customer 3 Suspend Recovery Action field 122 Suspend variable 219 svchost.exe 227 SvcNotResponding parameter 109 SvcStatus parameter 109 syntax pconfig 233 system output window 183 system requirements 35, 36 system roles 47
S
SAM monitoring 21 SAM NT authentication support 21 ScheduledServers variable 216 Scheduling variable 199 SchemaMasterConnStatusSched variable 209 SCOPEADD variable 206 SCOPEDEL variable 206 scripts batch file 125 customizing 125 editing 125126 using 123126 security event log 94 notification server 127 overview of levels 48 Security Account Manager (SAM) 21 send_mapi.vbs 124 sendmail.vbs 124 ServerExcludeList variable 207 ServerIPAddress variable 205, 206 ServerPortNumber variable 205, 206 servers, deploying settings to 127 ServiceMonitoring DisableAnnotation variable 192 MonitorManualServices variable 193 services checking status of 109 configuring in PCM 235 monitoring 108 monitoring executables for 109 PATROL for Windows Servers 31 restarting 42, 109 services.exe 227 ServiceStatus parameter 109, 120 setting environment variables for Help browser 72 ShareExcludeList variable 207 ShConnPercent parameter 44, 120 shells Bourne 72
T
TCP/Active variable 204 TCPorUDP variable 205, 206 technical support 3 templates, PATROL Adapter for Microsoft Office 150 terminal server 221 terminating processes 42, 115 text files, monitoring 137 thresholds changing in PCM 241 customizing 180 rule for 241 tuning 174, 177 time synchronization service 22, 24 TimeLimitForKillRunAwayProcess variable 192 TotalMessageSizeThreshold variable 216
265
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
troubleshooting 173184 TrustExcludeList variable 207 typical installation option 49 warnings, generating 109, 115 WarnMax variable 218 WarnMin variable 218 WBEM_E_INVALID_CLASS error message 181 WIN32_WMISetting 205 Windows 25 Windows account requirements 40 Windows Management Instrumentation (WMI) 30 Windows NT Workstation 125 WINS (Windows Internet Naming Service) recovery actions 120 reports 150 rulesets for monitoring 222 WINSADD variable 206 WINSDEL variable 206 WMI parameters, creating 135 WMI Wizard 30 WMIAvailability parameter 119, 205 WMServer service 229 wpconfig utility 88 wpconfig variables 16 WpReplicationFailures parameter 37, 120
U
UDP protocol 205, 206 UDP/Active variable 204 uninstalling products 75 unloading KMs 153 unresponsive services 109 upgrading 58 backing up current installation before 63 choosing a procedure 59 from an earlier version of the KM 58 UpTimeBaseLine variable 213 UseCheckPoint variable 195, 196 user account 73 user rights, required 40 UserExcludeList variable 207 using PCC 158
V
variable_list variable 234 variables __ANYINST__ 241 child_list 234 FilterEnabled 108 NOTIFICATION_SERVER1 129 NOTIFICATION_SERVER2 129 PATROL KM for Microsoft Active Directory 208211 PATROL KM for Microsoft Cluster Server 211216 PATROL KM for Microsoft COM+ 217 PATROL KM for Windows Domain Services 205208 PATROL KM for Windows Message Queue 216 PATROL KM for Windows OS 190205 PATROL Wizard for Performance Monitor and WMI 218 PATROL_BROWSER 73 variable_list 234 wpconfig 16 VB (Visual Basic) 123 version, determining 184 View Process Status dialog box 191 viewing event logs 116 virtual machines, support for 45 Visual Basic (VB) 123 VMware, support for 45 VPN (virtual private network) 222
X
xpconfig utility 88
W
Wait variable 219
266
Notes