CA Unified Infrastructure Management

Transcription

1 CA Unified Infrastructure Management rsp Guide v4.0 series

2 Copyright Notice This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the CA Software ). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Legal information on third-party and public domain software used in this product is documented in the Third-Party Licenses and Terms of Use (

3 Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback about Product Documentation Send comments or questions about CA Technologies product documentation to To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the support website at

4

5 Contents Chapter 1: rsp rsp Overview... 9 Chapter 2: rsp Probe Deployment 13 Supported Platforms System Requirements Software Requirements Monitoring System Requirements Probe Deployment Information Chapter 3: rsp Configuration 17 Probe Configuration Interface Installation for rsp Probe Defaults Probe GUI Toolbar Left Pane Right Pane Probe Configuration Setup Monitoring Profiles Templates Edit Machine Properties for Computer Edit Monitoring Properties for Checkpoint Configure Data Collection for Checkpoint Delete Checkpoint Configure General Setup Parameters Manage Logon Credentials Create and Rename New Group Folder Add Hosts for Monitoring Alarm User Interface Configure Process, Windows Services, and Windows Events Configure WMI Objects Chapter 4: rsp Advanced Configuration Mode 65 Groups Add Group Contents 5

6 Edit Group Remove Group Add Section Modify Monitoring Properties Modify Template CPU CPU Alarm Condition Properties Disk Memory Load Paging Processes Template Add Instance Add Alarm Edit Instance Remove Instance Services Add Instance Edit Instance Disable Monitoring for Processes and Services NTEvents Add Instance Edit Instance Remove Instance WMI Objects Template Remove WMI Object WMI Profile Edit WMI Profile WMI Counters Chapter 5: Lua Editor 117 View Existing Scripts Create Script OS Detection Code (OS.LUA) LUA Function Mapping Chapter 6: Hints and Examples 123 Notes on Regexp Constructs rsp Guide

7 Chapter 7: QoS Threshold Metrics 125 rsp QoS Metrics rsp Alert Metrics Default Settings Chapter 8: Troubleshooting 131 Unable to find CPU Stats Determine Process Size Value not Displayed when WMI Profile is Configured Contents 7

8

9 Chapter 1: rsp 4.0 This description applies to the rsp probe version 4.0. Note: The field description for intuitive terms in the GUI has not been included in the document. This section contains the following topics: rsp Overview (see page 9) Documentation Changes (see page 11) rsp Overview The CPU, Disk, Memory Monitoring probe allows you to monitor system metrics. The CPU, Disk, Memory Monitoring probe collects performance data in an agentless manner without having to install proprietary software on the system. Note: The rsp probe supports only password-based and key based authentication. Keyboard-Interactive and authentication less method are not supported. In case the unix-based remote server is not having a password-based or key-based authentication enabled, the rsp probe is not able to discover the remote host. The rsp probe gathers the following statistics on the CPU utilization, disk, memory usage, and load: CPU usage (%) with multi-cpu support Disk The high severity (error) and low severity (warning) alarms for the total CPU usage. The high severity (error) alarms for the individual CPU usage in multi-cpu systems. Automatic local disk discovery Disk Usage (MB or %) Information retrieval on the local disk (Total disk space, Free disk space, and Used (%) disk space). Memory Total memory usage (%) Physical memory usage (%) The page file usage (%) Chapter 1: rsp 4.0 9

10 rsp Overview Swapping or the paging activity page/s Load Load at a specific moment Processes Alarms for the invalid process owner Alarms for the invalid CPU usage Alarms for invalid process size Alarms for the invalid thread count Alarms for the wrong number of process instances Alarms on process up/down Services (Windows Specific) Alarm on the state of a service NTEvents (Windows Specific) Alarms on specified NTevents Custom WMI (Windows Specific) Alarm specific to an object of WMI class 10 rsp Guide

11 rsp Overview Documentation Changes This table describes the version history for this document. Version Date What's New? 4.0 October 2014 Updated the rsp Configuration topic, and its sub-topics corresponding to the fixed defects. 4.0 June 2014 Added a Note in the Software Requirements section. 4.0 March 2014 Updated description of the Add Logon Credential section. 4.0 January 2014 Updated the Software Requirements section. 4.0 December 2013 Added the Configure WMI Objects section and WMI Objects section. 3.0 September 2013 Added a note in the Qos Metrics topic. Added Determine Process Size topic in the Troubleshooting section. Added Unable to find CPU Stats topic in the Troubleshooting section. Updated the Add Logon Credential topic. Added the Hints and Examples section. 3.0 June 2013 Added Generate Key for Password-less Authentication section supported on rsp probe version 3.0. Removed Summary Report from Monitored Hosts section. Removed the View Samples from Checkpoint section. Updated the default parameter values in the Configure General Setup Parameters section. Added Groups section. Updated the note in the Monitoring System Requirements section. Documentation Changes 11

12 rsp Overview Version Date What's New? 2.9 January 2013 Added the information for the password less SSH and updated the Add Logon Credential section. Updated information for the Advance Configuration section. 2.8 March 2012 The discovery feature of address range for IPv6 is supported in this version. 2.7 November 2011 Corrected the process monitoring on Linux with name+command option; corrected process CPU percentage reporting 0% for all processes on the VM ware environment; added support for fetching machine name via SSH and WMI; and updated libraries. 2.3 March 2010 Added support for using sudo instead of root and included group name in alarm message. Related Documentation Documentation for other versions of the rsp probe (../../rsp.html) The Release Notes for the rsp probe Monitor Metrics Reference Information for CA Unified Infrastructure Management Probes ( 12 rsp Guide

13 Chapter 2: rsp Probe Deployment This section contains the prerequisites, system requirements, and deployment information for the rsp probe. This section contains the following topics: Supported Platforms (see page 14) System Requirements (see page 14) Software Requirements (see page 15) Monitoring System Requirements (see page 15) Probe Deployment Information (see page 15) Chapter 2: rsp Probe Deployment 13

14 Supported Platforms Supported Platforms Refer to the Compatibility Support Matrix for the latest information about supported platforms. See also the Support Matrix for Probes for more specific information about the probe. The rsp probe runs on both Windows and Unix or Linux operating systems as specified in the Support Matrix for CA UIM Probes. You cannot monitor Windows machines from an instance of rsp running on a UNIX or Linux Robot using the rsp WMI option. On a Windows machine, you would have to depend on the rsp options for SSH or telnet, since Windows Management Instrumentation (WMI) is Windows-based. Although the WMI client software is available for Linux and Cygwin ( supports SSH connectivity for Windows machines, CA UIM does not test these configurations. Therefore, this functionality is not supported. The following monitoring approaches that are currently supported for the CA UIM rsp probe are: Windows->Windows Windows->Unix Windows->Linux Unix ->Linux Linux->Unix Linux->Linux Unix->Unix Important! The rsp probe cannot be deployed on AIX systems but can monitor remote AIX systems. System Requirements The rsp probe can be installed on systems with the following minimum resources: Memory: 2-4 GB of RAM. The OOB configuration of the probe requires 256 MB of RAM CPU: 3-GHz dual core processor (32 bit or 64 bit) 14 rsp Guide

15 Software Requirements Software Requirements The rsp probe requires the following software environment: Nimsoft Monitor Server 7.1 to 7.6 or CA Unified Infrastructure Management 8.0 or later Robot 6.5 or later RE 1.6 or later Monitoring System Requirements The rsp probe GUI offers functionality for discovering servers, which needs monitoring. The discovery method can be hostname, IP address (with the start IP address and number of addresses), or IP range. Note: You cannot monitor the computer, which is hosting the rsp probe by IP address or hostname. However, you can discover it by its loopback address ( ). Probe Deployment Information There are three ways to distribute archive packages. You can distribute the package within the web-based Admin Console (for supported probes), from within Infrastructure Manager, or use the standalone Distribution application. See Probe Deployment for more information on deploying probes. Chapter 2: rsp Probe Deployment 15

16

17 Chapter 3: rsp Configuration The rsp probe uses WMI (using port 135 and above 1024) to gather remote data on the Windows systems. Note: WMI uses port 135 and above 1024 ports as per Microsoft Windows specifications. For more information, refer to You must create firewall exceptions to allow the ports or you can configure custom port range to gather remote data on the Windows systems. Note: These commands are run as the root user on UNIX or Linux systems. Therefore, CA UIM strongly recommends the use of SSH to avoid the root password being transferred in the clear over the network. The rsp probe monitors thresholds for all the data points. The rsp probe allows you to gather Quality of Service (QoS) data for data points as well. The QoS names match with the QoS used by the CPU, Disk and Memory Performance Probe (CDM) since the data gathered is the same. The rsp probe is multithreaded and allows simultaneous data gathering from a number of servers. This number depends on several factors, which are as follows: Monitoring of the Window computers is less time consuming as compared to UNIX computers Using SSH is faster than using telnet. Note: SSH is more secure and is preferred over Telnet. The capacity and speed of the network The capacity of the computer hosting the rsp probe. The capacity of the computers being monitored. This section contains the following topics: Probe Configuration Interface Installation for rsp (see page 17) Probe Defaults (see page 18) Probe GUI (see page 19) Probe Configuration (see page 25) Probe Configuration Interface Installation for rsp The probe configuration interface is automatically downloaded and installed by the Infrastructure Manager when the probe is deployed on a robot. Chapter 3: rsp Configuration 17

18 Probe Defaults Probe Defaults At the time of deploying a probe for the first time on the robot, some default configuration is deployed automatically. You can drag and drop the test template to the profile. These probe defaults could be alarms, QoS, and profiles, which save time to configure the default settings. These probe defaults appear on a fresh installation. No instance of that probe is already available on that robot in activated or deactivated state. Note: Enable the QoS for inst_default for getting QoS for processes and service. The probe defaults for rsp probe are: CPU Disk Memory Total CPU usage Publish data(qos enabled) ON High Threshold 90 % / Major severity Load Publish data(qos enabled) ON Check Cycle 3 Disk Availability Low Threshold 80% / Minor Sev High Threshold 90% / Major Sev Alarm on Disk % free QoS MB Publish Data (QoS enabled) ON QoS Pct Publish Data (QoS enabled) ON Physical Memory Low Threshold 80% / Minor Sev High Threshold 90% / Major Sev Publish data(qos enabled) ON Swap Memory as MB Publish Data (QoS Enabled) - ON 18 rsp Guide

19 Probe GUI Paging Publish Data (QoS Enabled) - ON Probe GUI The following screen displays the rsp GUI with groups and profiles being monitored: The rsp GUI consists of: A toolbar, containing several buttons. The left pane, containing group folders (and optionally subfolders) and monitoring profiles (machines being monitored). The main window pane, consists of: Profiles when a group is selected in the left pane. Checkpoints, when a profile is selected in the left pane. Chapter 3: rsp Configuration 19

20 Probe GUI Toolbar The rsp toolbar consists of the following buttons: General Setup Defines the general setup parameters for the rsp probe. Manage Logon Credentials Opens the Credentials dialog, which enables you to add the user credentials of the rsp probe for the servers being monitored. Create a New Group Folder Creates a new group folder either at the root level or subgroup level. Create a New Host Profile Opens the Add host dialog, which allows you to search for new hosts to be monitored using the discovery functionality. Advanced Configuration Mode Allows you to switch between normal configuration mode and advanced configuration mode. LUA Editor Opens the Lua script editor, which allows you to edit existing Lua scripts or create your own scripts. Using Lua scripts, the parsing of the data is done. A set of Lua scripts is included with the rsp probe. Process Viewer Lists all the processes on the machine that is selected in the left pane. Windows Services Viewer Lists all the Windows services running on the machine that is selected in the left pane. This button is active only if the machine selected in the left pane is a Windows machine. Windows Events Viewer Lists all the Windows events raised on the machine that is selected in the left pane. This button is active only if the machine selected in the left pane is a Windows machine. Custom WMI Configurator You can configure WMI objects by configuring namespace, class, instances and their respective counters with their thresholds. 20 rsp Guide

21 Probe GUI Left Pane The left pane contains group folders (and optionally subfolders) containing the defined monitoring profiles. The folder My Remote Server is predefined. You can create your own folders as described in the Create New Group Folder section. Chapter 3: rsp Configuration 21

22 Probe GUI The icons representing the host profiles are as follows: This icon indicates that the probe can communicate with the host. The color indicates the highest alarm level from a checkpoint on the host. This indicates that the probe cannot communicate with the host (host is stopped) Right-clicking a profile provides the following options: New: This option opens the Add Host dialog, enabling you to discover one or more profiles. Edit: This option opens the Machine properties dialog for the selected profile, enabling you to edit the monitoring parameters for the profile. Delete: This option allows you to delete the selected profile from the folder. Rediscover: This option allows you to rediscover the checkpoints on the selected host. Processes: This option lists all the processes running on the selected machine. Windows Services: This option lists all the Windows services running on the selected machine. Windows Events: This option lists all the Windows events that are fired on the selected machine. WMI Objects: You can configure WMI objects by configuring namespace, class, instances and their respective counters with their thresholds. Refresh: This option refreshes the contents in the left pane. To add, delete, or rename a folder, right-click the group folder. You can also refresh the contents in the left pane. You can also move a host from one group to another. Select the group folder from where you want to move the hosts, which are listed in the right pane. Select the hosts that you want to move and then drag and drop them on to the new folder. 22 rsp Guide

23 Probe GUI Right Pane The contents on the right pane depend on your selection in the left pane. Group Folder Selected in Left Pane If a group folder is selected in the left pane, the profiles belonging to that group is listed. The icons are colored, indicating the highest severity level that is propagated from a checkpoint on that computer. Right-clicking in the list allows you to: Add a host to be monitored. Edit an existing host. On selecting an existing host, the Machine Properties dialog opens. Using this dialog, you can edit the monitoring properties for the selected computer. Delete a host. Chapter 3: rsp Configuration 23

24 Probe GUI Profile Selected in the Left Pane If a profile is selected in the left pane, the checkpoints belonging to the computer are listed. The icons are colored, indicating the current severity level from that checkpoint on the computer. The values that are displayed are the most recent values that are collected from the checkpoints. The colored icons on the checkpoints indicate: The most recent alarm level from the checkpoint. The black color indicates the unknown status. For example, the status that is received immediately after probe restart. The probe is not able to retrieve a response from the checkpoint. For example, the status that is received when the checkpoint does not exist. Right-clicking in the list allows you to: Edit a checkpoint: On selecting Edit a checkpoint, the Properties dialog for the checkpoint appears enabling you to edit the monitoring properties of the checkpoint. You can override the default template parameters as well as change the template while applying the changes. Clear Override: On selecting the Clear Override option, the template override is cleared, you can use the properties that the template defines. If you have overridden the default template parameters, the Clear Override option is activated. Else, this option is disabled. Configure data collection: On selecting the Configure data collection option, you can configure the data collection from the selected checkpoint, like the sample interval. 24 rsp Guide

25 Probe Configuration Probe Configuration The rsp probe is configured by double-clicking the probe in Infrastructure Manager, which opens the GUI (configuration tool). When the GUI is opened for the first time, the default configuration of the probe appears. Setup Monitoring Profiles To set up monitoring profiles, use the Add Host dialog. If no profiles have been defined yet, this dialog is automatically opened on launching the probe GUI. You can open the dialog by clicking the Create a New Host Profile toolbar button. The dialog lets you specify a range or a number of hosts on your network and find them for you. The checkpoints on the hosts are then monitored as per the properties, which are defined by default templates. These properties are overridden for a single profile and you can modify the template as well. Chapter 3: rsp Configuration 25

26 Probe Configuration Templates By default, the checkpoints on the hosts are monitored as per the properties, which are defined by default templates. These templates can be modified in the Advanced Configuration Mode section. Note: In Windows Services and the Windows Events processes, a single profile or checkpoint can also be added to the group section. All the profiles that are derived from that particular group, start monitoring the checkpoint. Modifying a template can affect all profiles using that template. You can also override the templates for a single profile or checkpoint. The dialog can access information to search and find computers on your network and group them properly: Folder group: One or more groups in which you put the servers to monitor. You can use the My Remote Servers default group or can create new groups and subgroups by clicking the Create a new Group folder button. Logon credentials: The probe needs user credentials for logging on to the different servers to be monitored. Add them by clicking the Manage Logon Credentials button. Edit Machine Properties for Computer You can configure the probe to edit the machine properties of the computer that allows you to rediscover a host. Follow these steps: 1. Right-click the host in the left pane and then select Edit to open the Machine properties dialog. 26 rsp Guide

27 Probe Configuration 2. Modify the field information and click OK. The machine properties for the computer are modified, which allows you to rediscover a host. The Machine properties dialog contains the following fields: Active Activates or deactivates the profile. If the profile is deactivated, the profile remains in the list without being monitored. Specify time interval Name Specifies how often data is collected from the checkpoint. By default, its value is 5 min. Displays the name of the profile. By default, the profile name is same as the hostname, but you can rename it as well. Template Specifies the monitoring properties. Hostname / IP-address Defines the name or IP address of the host. Login credentials Allows you to select one of the logon credentials defined. Chapter 3: rsp Configuration 27

28 Probe Configuration Protocol Specifies the communication protocol to be used between the probe and the hosts. The valid options are wmi (using port 135) for the Windows hosts and telnet (using port 23) or ssh (using port 22) for Unix hosts. Operating System Displays the name of the operating system on which the host is running. Edit Monitoring Properties for Checkpoint The templates that are associated with the profile determine the monitoring properties. To modify these parameters, select a host in the left pane and then double-click the checkpoint in the right pane. You can also modify these parameters by right-clicking the profile and selecting the Edit option. 28 rsp Guide

29 Probe Configuration Click the OK button when you are done with your modifications. You have the following options: If you want your modifications to override the template settings for this host, click the Profile Override button. If you want your modifications to change the template settings, click the Template button. Note: In processes and windows services, monitoring instance is added to the group. The alarm and QoS information are also updated to the template section. This process allows you to configure a profile and monitor the instance across all the machines in a particular group. If you do not want either of the above two options, click the Cancel button to exit the dialog. The Properties - CPU dialog contains the following fields: Alarm settings Low threshold Defines the low threshold. If the defined low threshold is breached, allows you to generate an alarm. Severity If the defined low threshold is breached, you can specify the severity of the alarm to be sent. High threshold Severity If the defined high threshold is breached, allows you to generate an alarm. If the defined high threshold is breached, you can specify the severity of the alarm to be sent. Quality of Service Allows you to send the values that are measured on the checkpoint as QoS data. Some of the checkpoints can have only one QoS while others can have more than one. Note: In the processes, double-click the checkpoint of an alarm to change its condition. All other alarms remain inactive in the user interface. Chapter 3: rsp Configuration 29

30 Probe Configuration Configure Data Collection for Checkpoint You can configure the check interval for a checkpoint. For example, you can configure the probe to provide data for a particular checkpoint. By default, the templates determine the data collection properties for the checkpoints. Follow these steps: 1. Select a host in the left pane and right-click the checkpoint in the right pane. 2. Select Configure data-collection for <checkpoint>. The Data-collection settings for disk dialog appears. 3. Enter the field information. Active Activates or deactivates the profile. The deactivated profile is in the list, but is not monitored. Check cycle Defines how often data is collected from the checkpoint. The value in the Check cycle field * value in the Specify time interval field is the final value of the check cycle field. For example, If the value in the Specify time interval field is 2 and in the Check cycle field is 2 minutes, the time interval when data is collected from the checkpoint is 2 * 2 = 4 minutes. Note: The Specify time interval field is configured while editing machine properties for the computer. Use last sample value only Allows you to use the last measured value, which is compared with the threshold defined (in the template or overridden by custom settings). Note: If the threshold is breached, an alarm is issued. 30 rsp Guide

31 Probe Configuration Use computed average over the last xx samples Uses the average value of the specified number of samples and compares with the threshold defined (in the template or overridden by custom settings). If the threshold is breached, an alarm is issued. 4. Click the OK button. The data collection for a checkpoint for that check interval is configured. Note: If you want your modifications to override the template settings for this host, click Profile Override. If you want your modifications to change the template settings, click Template. If processes and Windows services instance is added to the group, the alarm and QoS information is updated in the Template section. You can configure a profile and can monitor an instance across all the machines in a particular group. Note: You can return to the default data-collection properties determined by the template by selecting the Clear data collection override option. Chapter 3: rsp Configuration 31

32 Probe Configuration Delete Checkpoint You can delete a checkpoint of the parameter type cpu or disk. When you do not need data from all parameters, you can use this option to delete the checkpoint. Follow these steps: 1. Right-click the checkpoint that you want to delete. 2. Select the Delete option. The selected checkpoint is deleted. Note: The Delete context menu option is only available for checkpoints of the parameter types: cpu and disk. For other parameters, such as load, memory, and paging, this option is disabled. 32 rsp Guide

33 Probe Configuration Configure General Setup Parameters You can configure the General Setup parameters in the rsp probe. To increase the efficiency of the probe, you can define the maximum number of threads you want to execute. You can also set the hours for which the data is available in SQLite. To give sufficient time for all the commands to execute successfully, you can edit the command timeout if there are many profiles running. You can define maximum events that can be fetched on the rsp GUI when the Events button is clicked. Follow these steps: 1. Click the General Setup button. The Setup dialog appears. 2. Enter the field information and click OK. The general setup parameters are configured, which increases the efficiency of the probe and provides sufficient time for all commands to execute successfully. Chapter 3: rsp Configuration 33

34 Probe Configuration The Setup dialog contains the following fields: Level Temporarily increases the log level for debugging purposes. Logfile Size Sets the size of the log file to which probe internal log messages are written. By default, the size of the log file is 100 KB. When this size is reached, the contents of the file are cleared. Show passive elements Limits Lists all passive or inactive alarms in the right pane. Max data collection threads Specifies the maximum number of profiles the probe can run simultaneously. By default, its value is 200. Keep data in database Specifies for how long the collected data is kept in the QoS database. By default, its value is 2 hours. You can also enter the value in decimal representation. Command Timeout Defines how long the probe takes to log on to a host. The probe fetches the values for the checkpoints before timing out and sending an alarm. By default, its value is 30 seconds. Max events to fetch Defines the maximum number of events, which the probe can fetch and execute. By default, its value is 100. Max data processing threads Specifies the maximum number of threads that is required for data processing. By default, its value is 100. Max DB Transaction Statements Specifies the maximum number of database transaction statements that can be committed in one attempt. By default, its value is rsp Guide

35 Probe Configuration WMI Connection Timeout Specifies the timeout for the WMI connection to be created. By default, its value is 5 seconds. SSH Connection Timeout Specifies the timeout for the SSH connection to be created. By default, its value is 5 seconds. DB Transaction Timeout Specifies the time after which the profile data is committed to the database. By default, its value is 10 seconds. Note: On selecting the Show passive elements check box in the Setup dialog, the label Show passive elements in the rsp probe GUI displays ON. If this check box is cleared, the label displays OFF. Force Group Override Fetches the instance, section, or alarm condition settings first from profile level, and then from group level. The template settings are overridden if same settings are defined at the group level for the same section, instance, or alarm. If this check box is not selected, then the section, instance, or alarm condition settings are first fetched from profile level, and then from template level. By default, this check box is not selected. If this check box is selected, then the instance configuration, template configuration, and their corresponding alarm conditions at group level are overridden, otherwise the default configuration made through default templates are applied to the discovered hosts. Note: If you select the check box, then you must restart the probe to apply the new configuration. Manage Logon Credentials RSA or DSA Authentication This section lets you manage the logon credentials of the rsp probe. The rsp probe collects data from Windows and Linux and this new feature works only when the probe is collecting data from the Unix boxes. The following scenarios can be considered: Collect data from the Unix machine when the probe is installed on Windows. Collect data from the Unix machine when the probe is installed on Unix. Chapter 3: rsp Configuration 35

36 Probe Configuration Generate Keys for Password-Less Authentication using SSH The rsp probe, version 3.0 and onwards, supports the open SSH key format. In the current version of rsp probe, the format of.ppk does not work. Previously plink only supported.ppk format, but now libssh for SSH support is used and plink is used for supporting telnet. If you want to support the current password-less SSH authentication, use the open SSH key format. This section contains procedures on how you can generate private or public keys using PuTTY and SSH. Generate Public or Private Key using PuTTY Key Generator This procedure is used for Windows to the UNIX SSH communication. Follow these steps: 1. Open PuTTy Key Generator. 36 rsp Guide

37 Probe Configuration 2. Copy the public keys in the SSH server authorized keys. 3. Save the private key in.ppk format. Import the private key and then export it into the Open SSH key format. 4. Export private keys to Open SSH key format and save it to a location. 5. Connect rsp probe with the SSH key format. Note: Add id_rsa or id_dsa key format for UNIX. Generate Public or Private Keys using SSH You can generate private or public keys using SSH. For UNIX to UNIX monitoring, you can generate private or public keys using the SSH Key Gen command. Follow these steps: 1. Generate DSA Key Pair using the SSH Key Gen command. 2. Enter a passphrase that is different from your account password and confirm the same. The public key is written to /home/username/.ssh/id_dsa.pub. The private key is written to /home/username/.ssh/id_dsa. 3. Provide the permissions to your SSH directory. 4. Copy file ~/.ssh/id_dsa.pub on Machine #1 (tom) to the remote server jerry as ~/.ssh/authorized_keys: $ scp ~/.ssh/id_dsa.pub user@jerry:.ssh/authorized_keys The private or public key using SSH is generated. Chapter 3: rsp Configuration 37

38 Probe Configuration Add Logon Credential You can configure the probe to add the logon credential to a server. In order to monitor the host, provide the username or password. Follow these steps: 1. Click the Manage Logon Credentials button. The Credentials dialog appears. 2. Click the Add button to add the user credentials. The Add Credential dialog appears. 3. Enter the field information and click OK. The logon credential is added. The Add Credential dialog contains the following fields: User A valid user name on the server to be monitored. For Windows Computers: Use the domain user or a local user name on the computer. For UNIX Computers: Use the user root. Password Defines the password for the user name. Add the credentials for all servers that you want to monitor as these credentials are required while creating monitoring profiles. 38 rsp Guide

39 Probe Configuration Use sudo Allows you to work with root user privileges, by selecting the Use sudo check box. Note: In order to allow the rsp user to use sudo feature, do the following changes in sudo /etc/sudoers file. Type visudo on the remote machine. Disable requiretty option for the user. By default, its value is rspuser!requiretty. Here rspuser is the username that rsp probe uses with the Sudo check box selected. Enable no password for the rsp user. You can enable this feature by the following: ::rspuser ALL=(ALL) Password Less SSH NOPASSWD:ALL Allows you to log on to the probe using the RSA or DSA encryption. Note: On selecting this check box, the Private Key File and Passphrase fields appear. Private Key File Allows you to select the private key file using the Browse button. Note: The rsp probe version 3.00 onwards does not support interactive mode of authentication for user login. The password mode of authentication must be enabled for the given user. Chapter 3: rsp Configuration 39

40 Probe Configuration Remove Logon Credential In the rsp probe, you can delete the credentials, which are not in use. Follow these steps: 1. Select the credential that you want to remove. 2. Click the Remove button. The Remove Credential dialog box appears. 3. To remove the selected credential, click Yes. The selected logon credential is removed. Create and Rename New Group Folder By default, all hosts are discovered under My Remote Servers. If you want to add the host to some other folder, you can create a group. To sort the hosts, which the probe is monitoring, use group folders. The two types of group folders, which you can create are: Folder at the root level. Subfolder under the root folder that is selected in the left pane. This option is deactivated if a subfolder is selected in the left pane. Follow these steps: 1. Click the Add Group Folders button. The group folder is created. 2. Right-click the new group folder and select Rename. The folder is renamed. 40 rsp Guide

41 Probe Configuration Add Hosts for Monitoring Using this feature, you can discover hosts by hostname or by IP address. To discover a host, select the required login credentials, protocol, and template. Follow these steps: 1. Open the Add Host(s) dialog. 2. Click the Add Hosts Profile(s) icon or right-click a host in the GUI and select New. Chapter 3: rsp Configuration 41

42 Probe Configuration 3. Enter the field information. 4. Click the Discover button. Note: The probe searches for hosts and tries to log on to the hosts found. The Discover button preliminary changes name to Abort during the discovery session. 5. Click OK. The Add Host(s) dialog contains the following fields: Select discovery method Selects the discovery method to be used when searching for hosts. By IP address Specifies a starting IP address and the number of IP addresses in descending order. For example, specify Starting IP address = and Num of addresses = 5, the probe searches for IP addresses in the range to Specifying Starting IP address = and Num of addresses = 5, the probe searches for IP addresses in the range to Note: The computer is omitted if the IP address of the computer hosting the rsp probe is in the range. In IPV6, the probe only supports range of 50 IPs. You can specify maximum 250 IPs. By IP address range Allows you to select a starting IP address and an ending IP address. The probe searches for all hosts in the range specified. Note: If the IP address of the computer hosting the rsp probe is in the range, the system is not omitted. Bypass name lookup Allows you to discover the machine through the IP address. Note: When you select this option, the nslookup command does not start. Login Credentials Protocol Folder Specifies the defined logon credential. On selecting Automatic, all logon credentials that are defined are tried. Specifies the communication protocol to be used between the probe and the hosts. The valid options are wmi (using port 135) for the Windows hosts and telnet (using port 23) or ssh (using port 22) for UNIX hosts. Specifies a folder in which you want to place the profiles. 42 rsp Guide

43 Probe Configuration Template Specifies the template to be used. The template defines the default monitoring properties to be used. The available options are Unix (to be used with the UNIX hosts) and Windows (to be used with Windows hosts). When you select the Automatic option, the probe automatically selects the template matching the different hosts found. Discover Initiates the search. Note: The button name changes to Abort during the preliminary discovery session. Chapter 3: rsp Configuration 43

44 Probe Configuration The Status for the hosts is as follows: OK: The hosts searched appears in the window. The hosts with status OK are added to the preferred folder when you click the OK button. Error: Hosts that are not found or the logon session fails are being assigned this status. Working: The probe is still trying to log on to the host. 44 rsp Guide

45 Probe Configuration The status bar at the bottom of the screen indicates the progress and result of the discovery session: Total: The total number of hosts that are detected while matching selected discovery method. Failed: The number of addresses where the probe failed to connect to a host because of the following reasons: The host is missing. The host is turned off. The host is having login problems. Discovered: The hosts that are found with the successful login processes so far in the discovery session. In progress: The probe is still trying to connect to the host. Alarm User Interface The alarm user interface supports alarm grouping. The alarms can be grouped as per your requirements. Chapter 3: rsp Configuration 45

46 Probe Configuration Configure Process, Windows Services, and Windows Events To monitor a single or group of services, events, and processes, you can create profiles with various parameters. Note: The availability of the Windows Services and Windows Events buttons depends on the operating system of your machine. For the UNIX-based machines, only the process option is enabled. For the Windows-based operating system, all the options are enabled. Create Monitoring Profile for Process To monitor a process, you can configure that process, which is related to a profile. Using the rsp probe can create a monitoring profile and can select features that need monitoring. Follow these steps: 1. Right-click the machine node from the My Remote Servers node in the left pane and click Processes. The shortcut menu displays options for discovered processes, Windows services, or Windows events. Alternatively, you can also view the shortcut menu items by clicking the highlighted buttons in the toolbar. 46 rsp Guide

47 Probe Configuration 2. Right-click the process and click the Create Monitoring profile option. Chapter 3: rsp Configuration 47

48 Probe Configuration The Process Monitoring Profile dialog is displayed. 3. Enter the field information and click OK. The monitoring profile is created. The Process Monitoring Profile dialog contains the following fields: Recognize process by Recognizes process by its name, which is the name of the executable without the path. Optionally, you can also let the processes probe determine the process-based on the complete process command line. Both the name and command-line fields handle regular expressions and pattern matching rules. Pattern matching support two wild characters * and?. For using regular expressions you need to encapsulate text with slashes, such as /Your regex/. For more information on regex, see Hints and Examples section. If you are using wildcards or reg ex, individual alarms would be generated for each process breaching the threshold but there would be single QoS for the whole group. For Example: a* is specified as process name Process CPU % and Number of thread are checked in QoS. CPU usage and Thread Count is checked for alarms and Now if 5 process match this condition then for Process CPU % and Number of threads QoS value would be sent as addition of CPU usage for all processes. But for alarms threshold would be checked for each process(individual CPU %age and number of thread in this case) and alarm would be generated for each process. 48 rsp Guide

49 Probe Configuration Alarms Tab Process Owner Sets an alarm if the process owner matches the specified criteria. The intensity of the alarm can be set using the combo box. CPU Usage Sets an alarm if the process CPU utilization matches the specified criteria. The intensity of the alarm can be set using the combo box. Process Size Sets an alarm if the process size matches the specified criteria. The intensity of the alarm can be set using the combo box. Thread count Sets an alarm if the process thread count matches the specified criteria. The intensity of the alarm can be set using the combo box. Instances Specifies the number of instances that are running. Instances and action are mutually exclusive. Process Up/Down Instructs the probe to generate an alarm. For example, the process has stopped (down) or it is running (up). Note: For an instance, you can view the alarms that are defined at the group level as well as at template level under the Profile Template node in the Advanced Configuration section. QoS Tab Generates the Quality Of Service (QoS) related to the process being watched. The messages are process state, memory usage of the process, CPU usage of the process, and number of process instances and threads. Note: The QoS messages for the memory usage, number of threads, and CPU usage summarize the numbers in the case of multiple instances of a process. Chapter 3: rsp Configuration 49

50 Probe Configuration Create Monitoring Profile for Service To monitor a service, you can create a monitoring profile and can select features to be monitored. Follow these steps: 1. Right-click the machine node from the My Remote Servers node in the left pane and click Windows Services. 2. Right-click the service and click the Create Monitoring profile option. 50 rsp Guide

51 Probe Configuration The Windows Service Monitoring Profile dialog appears. 3. Enter the field information. Expected Running State Specifies whether you expect the service to be running or stopped. Raise an alarm if the actual service state does not match with the expected running state. Quality of service State 4. Click OK. This option lets you send the current service state as QoS. A profile for monitoring a service is created. Chapter 3: rsp Configuration 51

52 Probe Configuration Add Monitoring Profile to an Event You can create a profile for an event or a set of events for monitoring them. To monitor events, you can create a monitoring profile and select features, which the rsp probe monitors. Note: You are recommended to create a profile through Create Monitoring Profile option only, and not through the Advanced Configuration section. Follow these steps: 1. Right-click the machine node from the My Remote Servers folder in the left pane and click Windows Events. 52 rsp Guide

53 Probe Configuration 2. Right-click an event and click the Create Monitoring profile option. The New profile name dialog appears. 3. Enter a profile name and click OK. Once the name is specified, a profile matching the criteria with the appropriate filters is added to the profile list. Chapter 3: rsp Configuration 53

54 Probe Configuration 4. Enter the field information and click OK. The monitoring profile is added to the selected event. The Monitoring Profile dialog contains the following fields: <List> Displays all the defined setup profiles. To display or modify the parameters of a profile, select the profile. The profiles are processed in the order they are listed in the list. You can change their order by right-clicking the list. Description Defines a text string identifying the watcher. Event selection Event selection criteria Specifies regular expressions for identifying the event log messages. An asterisk (*) in one of these fields refers to all the log messages regardless of the contents in the field. Note: You can also use both ranges and commas in the same entry, for example: 1-5, No propagation of events Alarm/Post Allows you to make an event matching the selection criteria for a profile unavailable for the other profiles. Note: You can change the order of the profiles as well as their processing order. Send alarm Allows you to send the CA UIM alarm on the recognition of an event log message. Alarm message Creates or edits an alarm message for the selected profile. You can use the following variables in the messages: $profile $event_desc Event selection criteria $ event_source $ event_code $ event_category 54 rsp Guide

55 . Probe Configuration $ event_logtype $ event_severity $ event_user $ event_computer Level Specifies the severity level of the generated alarms. To use the same severity level as the eventlog message, select from eventlog. QoS Number of events found in time interval This option lets you send the QoS messages on the number of events that are detected within the profile time interval. Exclude Event Using the Windows Events option, you can exclude events so that the alarms are not sent for them. Follow these steps: 1. Right-click the machine node from the My Remote Servers folder in the left pane and click Windows Events. 2. Right-click an event and click the Create Monitoring profile option. Chapter 3: rsp Configuration 55

56 Probe Configuration The New profile name dialog is displayed. 3. Enter a profile name and click OK. 4. Click the Exclude tab. 5. Enter the field information and click OK. The selected event is excluded. 56 rsp Guide

57 Probe Configuration The Exclude tab in the Windows Events Instance dialog contains the following fields: <List> Displays all the defined excluded profiles. To display or modify its parameters, select a profile. Event selection criteria Specifies the parameters identifying the eventlog messages that you are looking for. An asterisk (*) in one of these fields means all log messages regardless of the contents in the field. Note: You can also use both ranges and commas in the same entry, for example: 1-5, Events matching all the criteria in an exclude profile is excluded from monitoring by the defined profiles. The Event ID field does not support the regular expression. Use format as shown in the following example: * 114 1,5,10 1, Note: Multiple instances of Windows events can be added at one time. Configure WMI Objects You can configure that WMI object by selecting its namespace class and instances with their respective counters and thresholds. Chapter 3: rsp Configuration 57

58 Probe Configuration Create Monitoring Profile for WMI Objects You can create monitoring profile for WMI objects to monitor the system details, such as processors and volumes. The WMI objects can also be used for extracting the information of the respective system. You can configure WMI profiles at runtime only. Note: In the Advance Configuration section, you cannot create a new WMI instance for a new group. Follow these steps: 1. Right-click the machine node from the My Remote Servers node in the left pane and click WMI objects. The shortcut menu displays options for WMI objects. Alternatively, you can also view the shortcut menu items by clicking the highlighted buttons in the toolbar. 2. Select Namespace. 58 rsp Guide

59 Probe Configuration Chapter 3: rsp Configuration 59

60 Probe Configuration All the namespace classes get populated. 3. Select Class. The Instance drop-down list populates regarding that particular class. Note: Classes starting with underscore are not included in the drop-down list. 4. Select Instance and then click the Counter tab. Note 1: Go to the Counters tab and configure counters and their thresholds if there are some classes where instances are not present. Click Active in the WMI tab if you want to start monitoring. Note 2: The instances, which do not have the name property are not included in the list. 5. Select one of the counters from the list. Note: Apart from date and time all counters are displayed. 6. Click Send QoS check box to enable the QoS metrics. Note: This check box is only enabled in case of integer data types. 7. Click Add to select the alarm threshold. 60 rsp Guide

61 Probe Configuration Note: Alarm Condition properties dialog appears. 8. Configure the thresholds and click OK to close the Alarm Threshold dialog. 9. Click OK to close the WMI Objects dialog. Chapter 3: rsp Configuration 61

62 Probe Configuration The Add Profile Instance Name dialog appears. 10. Specify the name and click OK. 62 rsp Guide

63 Probe Configuration The Save Checkpoint dialog appears. 11. Click Profile Override if you want to apply these changes to the respective host. You can select Template if you want to apply the changes to all the discovered windows host. 12. Click Apply to save changes. The WMI objects are configured and the monitoring starts. Note: Two wmi-objects can have the same profile name. If you want to modify a configured WMI object, then double-click on it. The WMI tab contains the following fields: Active Activates the WMI object. Namespace Class Instance Specifies the namespace of the WMI to be monitored. Specifies the class to be monitored. Lets you select the instance in case more than one is found. Description Defines a description for the WMI object. The Counters tab contains the following fields: Counters Displays the counters available for the object. Thresholds Lets you define one or more thresholds for the counter. Select a counter in the list and click the Add button to set or modify the threshold value and severity for the selected counter. The counters available in the drop-down list depends on the selected category. Note: The Maximum thresholds, which can be configured are four and two thresholds cannot have the same name. Send QoS Lets the rsp probe send the QoS data on the counters that are defined in this profile. Chapter 3: rsp Configuration 63

64

65 Chapter 4: rsp Advanced Configuration Mode The Advanced Configuration Mode button is a toggle switch between normal configuration mode and advanced configuration mode. In this mode, the contents of the Window panes changes to display the configuration formats and templates. The left pane contains two root nodes: Config Format Profile Templates All host profiles added are listed under the Profile groups root node, which are sorted on the OS the host is running: Unix or Windows. The host profile is placed in the Profile Templates > Windows folder. Chapter 4: rsp Advanced Configuration Mode 65

66 Probe Configuration The host is monitored as per the default monitoring properties for Windows servers. These properties are defined in Config Format > Groups > Windows folder. For example, the Windows computer nimgate.nimsoft.no, placed in the Profile Templates > Windows folder, is automatically assigned: Monitoring properties that are defined under the Config format or Groups or Windows node. Templates (one template for CPU and one for disk) are defined under the Templates child node. These templates describe the monitoring properties for the different checkpoints. The Templates node uses the alarm messages, which are defined under the Messages node. 66 rsp Guide

67 Probe Configuration The host is assigned these monitoring properties, which are mirrored to the host node. Chapter 4: rsp Advanced Configuration Mode 67

68 Groups This section contains the following topics: Groups (see page 68) Modify Monitoring Properties (see page 72) Modify Template (see page 73) CPU (see page 75) Disk (see page 80) Memory (see page 82) Load (see page 84) Paging (see page 86) Processes (see page 87) Services (see page 96) NTEvents (see page 103) WMI Objects (see page 109) WMI Profile (see page 111) Groups Group is a collection of machines, which the rsp probe uses, such as Windows and Unix. You can add and edit a group as well as add a section to the group. Add Group Follow these steps: 1. Click Advanced Configuration Mode. 2. In the left pane, right-click the Groups child folder and click the Add group option. 68 rsp Guide

69 Groups 3. Enter the field information in the Group properties screen. Specify group name Defines the group name. Specify time interval 4. Click OK. Specifies the time interval, which applies to all machines belonging to this group. The group is added. Edit Group Follow these steps: 1. In the left pane, right-click the group that you want to modify. 2. Click the Edit group option. 3. Modify the values in the fields of the Group properties screen and click OK. The selected group is edited. Chapter 4: rsp Advanced Configuration Mode 69

70 Groups Remove Group Follow these steps: 1. In the left pane, right-click the group that you want to remove. 2. Click the Remove group option. The selected group is removed. 70 rsp Guide

71 Groups Add Section Follow these steps: 1. In the left pane, right-click the group for which you want to add a section. 2. Click the Add section option. Chapter 4: rsp Advanced Configuration Mode 71

72 Modify Monitoring Properties 3. Enter the field information in the Section properties screen. For more information on the fields, see the CPU section. Note: You are recommended to always specify a template, and an instance template. You can also change the template, and the instance template at profile level. 4. Click OK. The section is added for the selected group. Modify Monitoring Properties If the monitoring properties defined in the template do not exactly match your computer configuration, you can modify the monitoring parameters for that computer. 72 rsp Guide

73 Modify Template You have the following options: Modify a template under the Config Format node. Modify a template for a specific host under the Profile Templates node. Modify the monitoring properties for checkpoints. Modify Template You can modify a template for a single host or for all hosts belonging to a group: Modify a template under the Config Format node. Modify a template for a specific host under the Profile Templates node. Locate the template that you want to modify under the Config Format node or the Profile Groups node. Follow these steps: 1. Select an option from the right-click menu. You can: Add an instance, like a new disk. Edit or remove a section. Note: The name of the section is auto-populated while editing. Chapter 4: rsp Advanced Configuration Mode 73

74 Modify Template 2. Click the Add alarm condition option. The Properties dialog appears. 3. Modify the parameters. The selected template and the monitoring properties of the host are modified. Note: To apply the modifications, click the Apply button. 74 rsp Guide

75 CPU CPU Using the CPU section, you can modify alarm that is related to CPU. If you are configuring a host with multiple CPU, then a list of multiple CPU instances is displayed in the profile template section. The Section properties dialog contains the following fields: Active Specifies the section as active or not active. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Initially, this option is set to Yes. Yes: The section is active. No: The section is not active. Chapter 4: rsp Advanced Configuration Mode 75

76 CPU Template Cycle CPU Id Specifies the template to be used. Options are default and inst_default. Defines how often data is collected from the checkpoint. The value in the Check cycle field * value in the Specify time interval field is the final value of the check cycle field. For example, If the value in the Specify time interval field is 2 and in the Check cycle field is 2, the time interval when data is collected from the checkpoint is 2 * 2 = 4. Note: The Specify time interval field is configured while editing machine properties for the computer. Displays the CPU identification number. Instance template (for the sections dialog only) Specifies how often the checkpoints are checked. By default, it is 5 m (minutes). CPU average Total usage User Allows you to select the total CPU usage for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially it is set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the CPU usage by users or applications for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially it is set to No. Yes: The QoS message is sent. No: The QoS message is not sent. 76 rsp Guide

77 CPU System Wait Idle Individual CPU Specifies the CPU usage by the system for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially it is set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the CPU wait time for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the CPU idle time for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially it is set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Total usage Specifies the total CPU usage for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to Yes. Yes: The QoS message is sent. No: The QoS message is not sent. Chapter 4: rsp Advanced Configuration Mode 77

78 CPU User System Wait Idle Specifies the CPU usage by users or applications for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the CPU usage by the system for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially it is set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the CPU wait time for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the CPU idle time for all CPUs. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially it is set to No. Yes: The QoS message is sent. No: The QoS message is not sent. 78 rsp Guide

79 CPU CPU Alarm Condition Properties Using the Alarm Condition properties dialog, you can modify alarms that are related to CPU. The Alarm Condition properties dialog contains the following fields: Name Active Specifies the level of the alarm. Specifies the section as active or not active. The options are: Default from template: The active flag from the template is used. Yes: Section is active. No: Section is not active. Note: Select only Yes, or No, if no value is assigned to the active flag of the instance template, or if no similar alarm condition exist for the instance template. In case these options are not selected, the value default from template is set which fetches the settings that is configured at the template level in the Advanced Configuration section. Threshold Defines the alarm threshold. The alarm is sent when this threshold is breached. Message Name Specifies the message name. Chapter 4: rsp Advanced Configuration Mode 79

80 Disk Message overrides Text Level Defines the message text. Specifies the severity level of the alarm. Subsystem Reports the error message. By default, the value is 1.1.1, which means host. See the Subsystems tab on the nas probe user interface for details. Disk Using the Disk section, you can modify the disk as per your requirement. The changes are reflected when that disk is monitored. 80 rsp Guide

81 Disk The fields in the Section properties dialog are as follows: Name Active Displays the name of the section or disk. Defines the section as active or not active. Select one of the following options: Default from template: The active flag from the template is used. Initially set to Yes. Yes: The section is active. No: The section is not active. Template Cycle Specifies the template to be used. Defines how often data is collected from the checkpoint. The value in the Check cycle field * value in the Specify time interval field is the final value of the check cycle field. For example, If the value in the Specify time interval field is 2 and in the Check cycle field is 2, the time interval when data is collected from the checkpoint is 2 * 2 = 4. Note: The Specify time interval field is configured while editing machine properties for the computer. Section specific settings Instance template Adds the instances of a parameter that are discovered, such as the number of CPU, physical or swap memory, and number of disks. Use size percent for disk alarms Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Yes: The QoS message is sent. No: The QoS message is not sent. Quality of Service for disk size The QoS messages on the disk usage are handled as per your selection from the drop-down in megabytes and percent. Chapter 4: rsp Advanced Configuration Mode 81

82 Memory Memory Using the Memory section, you can modify the memory usage for the computer as per your requirement. The Section properties dialog box contains the following fields: Active Specifies the section as active or not active. Select one of the following options: Default from template: The active flag from the template is used. Yes: The section is active and the memory usage value is checked. No: The section is not active and the memory usage value is not checked. Template Specifies the template to be used. The only valid option is default. 82 rsp Guide

83 Memory Cycle Defines how often data is collected from the checkpoint. The value in the Check cycle field * value in the Specify time interval field is the final value of the check cycle field. For example, If the value in the Specify time interval field is 2 and in the Check cycle field is 2, the time interval when data is collected from the checkpoint is 2 * 2 = 4. Note: The Specify time interval field is configured while editing machine properties for the computer. Quality of Service for memory Usage Specifies if the probe sends QoS messages on the memory usage for the computer. Select one of the following options: Default from template: Memory usage QoS messages are handled as described by the default template. Yes: The section is active and the memory usage value is checked. No: The section is not active and the memory usage value is not checked. Chapter 4: rsp Advanced Configuration Mode 83

84 Load Load Using the Load section, you can modify the CPU load on the computer as per your requirement. The Section properties dialog contains the following fields: Active Specifies the section whether active or not. Select one of the following options: Default from template: The active flag from the template is used. Yes: The section is active and the memory usage value is checked. No: The section is not active and the memory usage value is not checked. Template Specifies the template to be used. The only valid option is default. 84 rsp Guide

85 Load Cycle Defines how often data is collected from the checkpoint. The value in the Check cycle field * value in the Specify time interval field is the final value of the Check cycle field. For example, If the value in the Specify time interval field is 2 and in the Check cycle field is 2, the time interval when data is collected from the checkpoint is 2 * 2 = 4. Note: The Specify time interval field is configured while editing machine properties for the computer. Quality of Service for system load Load Specifies if the probe sends QoS messages on CPU load for the computer. Select one of the following options: Default from template: The CPU load QoS messages are handled as described by the default template. Yes: The section is active and the CPU load value are checked. No: The section is not active and the CPU load value are not checked. Chapter 4: rsp Advanced Configuration Mode 85

86 Paging Paging Using the paging section, you can modify the paging of your CPU as per your requirement. The Section properties dialog contains the following fields: Active Displays the section as active or not active. Select one of the following options: Default from template: The active flag from the template is used. Yes: The section is active and the memory usage value is checked. No: The section is not active and the memory usage value is not checked. Template Specifies the template to be used. 86 rsp Guide

87 Processes Cycle Defines how often the probe checks the CPU load value. Quality of Service for paging Paging Specifies if the probe sends QoS messages on CPU load for the computer. Select one of the following options: Default from template: The paging of the QoS messages is handled as described by the default template. Yes: The section is active and the paging value is checked. No: The section is not active and the paging value is not checked. Processes You can update or remove the process profiles that have been configured using the Advanced Configuration Mode section. The configured profiles are added as an instance of the process monitoring template. Chapter 4: rsp Advanced Configuration Mode 87

88 Processes Template You can change the templates for processes by right-clicking the template that you want to modify and click the Edit option. 88 rsp Guide

89 Processes Add Instance You can add a monitor or instance using the Advanced Monitoring section. Follow these steps: 1. Right-click the processes folder and click the Add instance option. Chapter 4: rsp Advanced Configuration Mode 89

90 Processes 2. Enter the field information and click OK. The Instance properties dialog contains the following fields: Active Specifies the instance as active or not active. Select one of the following options: Default from template: The Active flag from the template is used. Initially set to No. Yes: The section is active. No: The section is not active. Template Specifies the template to be used. The default template in case of processes does not define alarms, but only defines the interval and active state. 90 rsp Guide

91 Processes Recognize process by QoS Name Specifies the name of the process that is monitored. Name + command line Acts with the process name filter, which enables you to specify the process name and the location from which the process is executed for monitoring. Process CPU usage Memory usage Instance Specifies QoS on the CPU usage of the process. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the total memory usage for process. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the number of instances of a process. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Chapter 4: rsp Advanced Configuration Mode 91

92 Processes State Threads Specifies the state of the process. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Specifies the number of threads a process spawns. Select one of the following options: Default from template: The template determines if this QoS message is sent or not. Initially set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Add Alarm You can add an alarm condition on an instance and can highlight the threshold, condition, and message. The new alarms can be added to the existing profiles using the Add alarm condition option. 92 rsp Guide

93 Processes Follow these steps: 1. Right-click the instance in the processes folder and select the Add alarm condition option. 2. Enter the field information and click OK. The alarm is added to the existing profile. Chapter 4: rsp Advanced Configuration Mode 93

94 Processes Edit Instance You can edit the existing instance by changing the properties for an instance. Follow these steps: 1. Right-click an instance in the processes folder and select the Edit Instance option. 94 rsp Guide

95 Processes 2. Modify the information in the Instance properties dialog and click OK. The properties for the selected instance are modified. Chapter 4: rsp Advanced Configuration Mode 95

96 Services Remove Instance You can stop the monitoring of an instance by removing it. Follow these steps: 1. Right-click the instance in the processes folder. 2. Select the Remove instance option. The selected instance is removed. Services The service profiles that are configured can be updated or removed using the Advanced Configuration Mode. The configured profiles are added as an instance of the services monitoring template. 96 rsp Guide

97 Services To change the templates for services, right-click the service and select Edit. Chapter 4: rsp Advanced Configuration Mode 97

98 Services Add Instance Using the Add instance option, you can add an instance for a service. Follow these steps: 1. Right-click the services folder. 2. Click the Add instance option. 98 rsp Guide

99 Services 3. Enter the field information in the Instance properties dialog. Active Specifies the instance as active or not active. Select one of the following options: Default from template: The active flag from the template is used. Initially, it is set to No. Yes: The section is active. No: The section is not active. Template State Specifies the template that defines the alarms for the instance. The default template in case of processes does not define alarms, but only defines the interval and active state. Specifies the state of QoS for services. You can select one of the following options: Default from template: The template determines if the QoS message is sent or not. Initially, it is set to No. Yes: The QoS message is sent. No: The QoS message is not sent. Chapter 4: rsp Advanced Configuration Mode 99

100 Services 4. Click OK. The instance is added for the selected service. 100 rsp Guide

101 Services Edit Instance If any modification is required, you can edit the instance being added for a service using the Edit instance option. Follow these steps: 1. Right-click the instance in the services folder and select the Edit instance option. 2. Edit the properties of the instance in the Instance properties dialog and click OK. The selected instance is modified. Disable Monitoring for Processes and Services Disabling the monitoring of a configured process or a service consists of two scenarios: Monitoring profile is set on a specific hub. Monitoring profile is based on a template. Chapter 4: rsp Advanced Configuration Mode 101

102 Services Disable Monitoring of Process Set on Hub To disable monitoring of process that is set on the hub, you can deactivate the instance instead of removing it. Follow these steps: 1. In the left pane, go to the machine on which the process or service is running. 2. Expand the processes or services folder. 3. Right-click the monitoring profile and select the Remove instance option. 4. Click the Apply button. The monitoring of process that is based on a hub, is disabled. 102 rsp Guide

103 NTEvents Disable Monitoring of Process Based on Template To disable monitoring of process on the template, you can deactivate the instance instead of deleting it. Follow these steps: 1. Go to Profile Templates in the left pane. 2. Click the processes or services folder. 3. Right-click the monitoring profile and select the Edit instance option. The Instance Properties dialog appears. 4. From the Active drop-down, select No and click OK. 5. Click the Apply button. The monitoring of process that is based on a template is disabled. NTEvents The NTEvents profiles that are configured can be updated or removed using the Advanced Configuration Mode. The configured profiles are added as an instance of the NTEvents monitoring template. Chapter 4: rsp Advanced Configuration Mode 103

104 NTEvents The templates for NTEvents can be changed by right-clicking the template to be modified and select the Edit option. Add Instance Using the Add instance option, you can add an instance for the events. 104 rsp Guide

105 NTEvents Follow these steps: 1. Right-click the events section and click the Add instance option. 2. Enter the name of the instance and click OK. 3. Enter the field information in Windows Events Instance dialog and click OK. The instance is added for the selected event. The Windows Events Instance dialog contains the following fields: Event selection Event selection criteria Specifies a regular expression identifying the eventlog messages. An asterisk (*) in one of these fields means all log messages regardless of the contents in the field. Note: You can use localhost in the computer field to get only local messages. You can also use both ranges and commas in the same entry, such as 1-5 and Description Defines a text string identifying the watcher. No propagation of events If this check box is selected, an event matching the selection criteria for a profile is unavailable for the other profiles. Note: You can change the processing order of the profiles. Chapter 4: rsp Advanced Configuration Mode 105

106 NTEvents Alarm/Post Send alarm Sends an CA UIM alarm message on the recognition of an event log message. Alarm message Level Creates or edits an alarm message for the selected profile and you can use the following variables in the messages: $profile $description Event selection criteria $source $event_id $category $profile $log $severity $user $computer $time_stamp Specifies the severity level of the generated alarms. Subsystem QoS Defines a text name for the subsystem. Note: Variables can also be used. Number of events found in time interval Sends the QoS messages on the number of events that are detected within the profile time interval. 106 rsp Guide

107 NTEvents The Setup/Exclude tab The fields in the Exclude tab are as follows: <List> Displays all the defined exclude profiles. Event selection criteria Specifies regular expressions identifying the eventlog messages. An asterisk (*) in one of these fields means all log messages regardless of the contents in the field. Note: You can also use both ranges and commas in the same entry, for example: 1-5 or Events matching all the criteria in an exclude profile, is excluded from monitoring by the defined profiles. The Event ID field does not support the regular expression. Use the format as shown in the following examples: * 114 1,5,10 1, Chapter 4: rsp Advanced Configuration Mode 107

108 NTEvents Edit Instance If any modification is required, you can modify the instance. Follow these steps: 1. Right-click the instance and select the Edit instance option. 2. Edit the field information and click OK. The selected instance is updated with the latest modifications. 108 rsp Guide

109 WMI Objects Remove Instance To stop the monitoring of an instance, you can remove it. Follow these steps: 1. Right-click the instance. 2. Select the Remove instance option. The selected instance is removed. WMI Objects You can modify or remove the WMI objects that have been configured using the Advanced Configuration Mode section. Chapter 4: rsp Advanced Configuration Mode 109

110 WMI Objects Template You can change the templates for WMI objects by right-clicking the template that you want to modify and click the Edit option. 110 rsp Guide

111 WMI Profile Remove WMI Object You can remove the WMI_object by selecting the Remove section option. Follow these steps: 1. Right-click the Wmi_object section. 2. Select the Remove section option. 3. Click Yes in the Remove section dialog. The selected Wmi_object section is removed. This procedure is applicable for defined WMI objects and their respective counters. WMI Profile A WMI profile contains all the WMI objects or counters defined for that WMI profile. Chapter 4: rsp Advanced Configuration Mode 111

112 WMI Profile Edit WMI Profile You can edit the existing WMI profile by right-clicking the WMI profile. Follow these steps: 1. Right-click a WMI profile and then select the Edit section option. 2. Modify the information in the WMI Objects dialog and click OK. 112 rsp Guide

113 WMI Profile The properties of the selected instance are modified. Note: Similarly, you can remove a WMI profile by selecting the Remove section option. WMI Counters Edit WMI Counters The WMI Counters section lets you view the configured counters while making the WMI object profile. You can edit the existing WMI profile by right-clicking the WMI profile. Follow these steps: 1. Right-click a WMI profile and then select the Edit Section option. 2. Modify the information in the WMI Objects dialog and click OK. The properties for the selected instance are modified. Note: Similarly, you can remove a WMI profile by selecting the Remove section option. Chapter 4: rsp Advanced Configuration Mode 113

114 WMI Profile Edit or Delete Alarms Using the Alarm Condition properties dialog, you can modify or delete alarms that are related to WMI_object. 114 rsp Guide

115 WMI Profile The fields in the Alarm Condition properties dialog are as follows: Name Specifies the level of the alarm. Active Specifies the section as active or not active. The options are: Default from template: The active flag from the template is used. Yes: Section is active. No: Section is not active. Threshold Defines the alarm threshold. The alarm is sent when this threshold is breached. Condition The conditions are as follows: For integers: >, <, >=, <=,!= and,= For strings: equal, not equal, starts with, ends with, and contains. For boolean: true and false Message Name Specifies the message name. Message overrides Text Defines the message text. Level Specifies the severity level of the alarm. Subsystem Reports the error message. By default, the value is 1.1.1, which means host. Note: You can edit the default alarms as well as deactivated alarms. Chapter 4: rsp Advanced Configuration Mode 115

116

117 Chapter 5: Lua Editor The parsing of the data is done using Lua scripts. A set of Lua scripts is included with the rsp probe. To open the Lua editor, click the Show LUA Editor option. This section contains the following topics: View Existing Scripts (see page 118) Create Script (see page 118) OS Detection Code (OS.LUA) (see page 120) LUA Function Mapping (see page 121) Chapter 5: Lua Editor 117

118 View Existing Scripts View Existing Scripts To view the Lua script, click the tree entries under the Lua Scripts section in the left pane and the corresponding Lua script appears. Create Script You can create and use your own Lua script. Follow these steps: 1. Click the New Lua Script icon on the Lua editor form. 2. Enter the name of the new Lua file and click OK. 118 rsp Guide

119 Create Script Note: The extension of the Lua file must be.lua. 3. Add your Lua functions in the editor: 4. Click Save once the script is complete. 5. Close the editor and click Apply. 6. Restart the probe. The script is created. Note: The script is saved on clicking Apply. Chapter 5: Lua Editor 119

120 OS Detection Code (OS.LUA) OS Detection Code (OS.LUA) The OS.lua is a special script. All the Unix operating systems can be detected using this script. To add support to an operating system that has its roots in Unix, you can add the OS detection code. For example, to add support to AIX 6 version, the following code is added in the AIX section. Click Save to save the changes. 120 rsp Guide

121 LUA Function Mapping LUA Function Mapping You can map the functions in the LUA file with the rsp collectors. Invalid mapping or any scripting errors can lead to invalid checkpoint data alarms. Follow these steps: 1. Click the Map functions icon on the Lua editor. 2. Click the Map function button. The Map function dialog appears. Chapter 5: Lua Editor 121

122 LUA Function Mapping 3. Enter the name of the operating system that is required to be supported, if your OS is not listed. The OS Name drop-down lists all the operating systems that the probe supports. 4. Enter the field information and click Map. The functions in the Lua file are mapped with the rsp collectors. 122 rsp Guide

123 Chapter 6: Hints and Examples This section contains the following topics: Notes on Regexp Constructs (see page 124) Chapter 6: Hints and Examples 123

124 Notes on Regexp Constructs Notes on Regexp Constructs General: [^<]* Anything (or nothing) not a '>'. Useful for getting the rest of a tag without knowing what it might be! \"([^\"]*?)\" Capture anything (or nothing) inside quotes. Note that the quotes themselves are required here, also that the quote needs to be escaped with the backslash \ character. The data you capture inside parentheses is available for use in variables in the logmon probe. You can use these variables in alarm messages, check values and send QoS messages with the contents, if they are numeric, or if the results are as expected <A[^>]*?> Matches and anchor tag up until the end of the tag. Generalizes for other tags as required. <\/A[^<]*? Matches an end anchor tag and anything up until the start of the next tag. Note that a slash / must be escaped with a backslash since it's a reserved character in regular expressions. If the monitoring target is an URL: Avoid using.* since regexps tries to match anything. The page is stripped of newlines when we get it, so everything is on one long line, and '.*' matches more than you probably expect it to. Be restrictive, and try to limit yourself to what is either inside the tag or outside the tag (don't go for a combination unless you really know what you are doing). Carriage Return (\r) and Newline (\n) characters are stripped out and replaced by spaces in the file when we get it. This means that you have to be ready to deal with spaces in places you might not expect them! Either add \s* (zero or more spaces) to your regexp or handle anything up to the next start or end of a tag. 124 rsp Guide

125 Chapter 7: QoS Threshold Metrics CA UIM probes ship with default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds. This section contains the following topics: rsp QoS Metrics (see page 125) rsp Alert Metrics Default Settings (see page 126) rsp QoS Metrics The following table describes the QoS metrics that can be configured using the rsp probe. Monitor Name Units Description QOS_CPU_MULTI_USAGE Percent Individual CPU Usage (used for idle time, system time, total usage, user time, wait time) QOS_CPU_USAGE Percent CPU usage (used for total usage, user time, system time, wait time, idle time) QOS_DISK_USAGE Megabytes Disk usage QOS_DISK_USAGE_PERC Percent Disk Usage (%) QOS_MEMORY_PAGING Kilobytes/Second Memory Paging QOS_MEMORY_PAGING_PGPS Pages/Second Memory Paging QOS_MEMORY_PERC_USAGE Percent Memory usage in percent QOS_MEMORY_PHYSICAL Megabytes Physical Memory Usage QOS_MEMORY_SWAP Megabytes Swap Memory Usage QOS_MEMORY_USAGE Megabytes Memory Usage QOS_NTSERVICE_STATE State NT Service Availability QOS_PROC_QUEUE_LEN Processes Processor Queue Length QOS_PROCESS_CPU_USAGE Percent Process CPU usage QOS_PROCESS_INSTANCE Number Number of process instances Chapter 7: QoS Threshold Metrics 125

126 rsp Alert Metrics Default Settings Monitor Name Units Description QOS_PROCESS_STATE Running Process Availability QOS_PROCESS_THREADS Number Number of Process Threads QOS_PROCESS_MEMORY_USAGE Kilobytes Process Memory Usage QOS_NTSERVICE_STATE State NT Service Availability QOS_NTEVENT_COUNT Count Number of events in interval QOS_WMI_OBJECT_VAL Variant Value of WMI object Note: Individual CPU metrics (User, System, Wait, and Idle) are not supported in Windows platform. These metrics would not return a value even if they are selected during configuration. rsp Alert Metrics Default Settings The following table contains the alert metrics and default settings for the rsp probe. Alarm Metric Generic Warning Threshold Warning Severity Error Threshold Error Severity connection error Major connection timeout Major data collection failure Major database integrity Major Description Alarm to be issued when connection to host failed or login refused. Alarm to be issued when connection to host timed out. Alarm to be issued when data collection failure for checkpoint on host happened. Alarm to be issued when database integrity problem occurred with host. 126 rsp Guide

127 rsp Alert Metrics Default Settings Alarm Metric Warning Threshold Warning Severity Error Threshold Error Severity duplicate data Major duplicate series Minor lua load error Major wmi class missing Major CPU Usage and Thresholds Total CPU Usage (%) 50 Minor 80 Major Total CPU Data not found Major Single CPU Usage (%) 50 Minor 80 Major Single CPU Data not found Major Disk Usage and Thresholds Disk usage (%) free 20 Minor 10 Major Disk usage (Mb) free 20 Minor 10 Major Description Alarm to be issued when possibly duplicated data in QoS series in the database data collection failure occurred for checkpoint as CDM probe is also running on the same host. Alarm to be issued when possibly duplicated data series in the QoS database as CDM probe is also running on the same host. Alarm to be issued when error in loading file occurred. Alarm to be issued when WMI class missing on host. Alarm to be issued when total CPU Usage is above the configured thresholds. Alarm to be issued when CPU data not found. Alarm to be issued when single CPU usages is above the configured thresholds. Alarm to be issued when cpuid data not found. Alarm to be issued when Disk usage (%) free is below the configured thresholds. Alarm to be issued when Disk usage (Mb) free is below the configured thresholds. Chapter 7: QoS Threshold Metrics 127

128 rsp Alert Metrics Default Settings Alarm Metric Warning Threshold Warning Severity Error Threshold Error Severity Disk File System data unavailable Major Memory Usage and Thresholds Physical Memory usage 70 Minor 80 Major Swap Memory usage 70 Minor 80 Major Total Memory usage 50 Minor 80 Major Memory Data unavailable Major Memory Paging and Thresholds Memory Paging 150 Warning 500 Major Memory Paging data unavailable Major Processor Queue Length and Thresholds Processor Queue Length 5 Warning 10 Major Load Data unavailable Major Processes and Threshold Process Owner - - Authority/ System Minor CPU usage Minor Description Alarm to be issued when No data for file system currently available. Alarm to be issued when Physical Memory is above the configured thresholds. Alarm to be issued when Swap Memory is above the configured thresholds. Alarm to be issued when Total Memory is above the configured thresholds. Alarm to be issued when no Memory type data currently available. Alarm to be issued when Memory Paging is above the configured thresholds. Alarm to be issued when Paging data not currently available. Alarm to be issued when Load is above the configured thresholds. Alarm to be issued when Load data not currently available. Alarm to be issued when the configured threshold satisfied. Alarm to be issued when the CPU usage satisfied the configured threshold. 128 rsp Guide

129 rsp Alert Metrics Default Settings Alarm Metric Warning Threshold Warning Severity Error Threshold Error Severity Process size Minor Thread Count Minor Instances Minor Process when up Minor Process when down Minor Events and Threshold NTEvents Count Services and Threshold from eventlog Windows Services State Major WMI WMI Counter Thresholds Description Alarm to be issued when Process size satisfied the configured threshold. Alarm to be issued when Thread Count satisfied the configured threshold. Alarm to be issued when instances satisfied the configured threshold. Alarm to be issued when Process is running. Alarm to be issued when Process is not running. Alarm to be issued when event generates and configured parameter matches. Alarm to be issued when Expected state is not same as service_state. Alarm to be issued when value of WMI object satisfied the configured threshold. Chapter 7: QoS Threshold Metrics 129

130

131 Chapter 8: Troubleshooting Some troubleshooting points for the rsp probe are as follows: If there are SSH failures, increase the limit of number of SSH connections. Verify the DNS settings if more time is taken in sending alarms. If the processes list comes out as empty while using large number of hosts, increase the command timeout (preferably 60 seconds). If you face any controller issue (for example, turning red), clear the NIS cache by deleting the.ci,.dev, and.met entries. Increase the WMI Connection Timeout or SSH Connection Timeout if consistent data not found alarms for any of the monitors is observed. This section contains the following topics: Unable to find CPU Stats (see page 132) Determine Process Size (see page 135) Value not Displayed when WMI Profile is Configured (see page 138) Chapter 8: Troubleshooting 131

132 Unable to find CPU Stats Unable to find CPU Stats Symptom The probe is not able to fetch Process size in the processes dialog and Error status = is generated in the log file. Solution The permissions on My Computer in the component services for the Access Permissions and Launch and Activation Permissions are not set correctly. These permissions are configured on the remote server. Follow these steps on the remote server: 1. Open the Component Services from the Administrative Tools. Note: You can also execute the C:\WINDOWS\system32\Com\comexp.msc command for opening the Component Services window. 2. Expand the Computer section. 3. Right-click the My Computer object and select the Properties option. The My Computer Properties Dialog appears. 4. Click the COM Security tab. You can find the options to Edit Limits and Edit Defaults for both the Access Permissions and the Launch and Activation Permissions. 132 rsp Guide

133 Unable to find CPU Stats Chapter 8: Troubleshooting 133

134 Unable to find CPU Stats 5. Set the Access Permissions as follows: Edit Limits Anonymous Logon => Local Access + Remote Access Distributed COM Users => Local Access + Remote Access Everyone => Local Access + Remote Access Edit Default SELF => Local Access + Remote Access SYSTEM => Remote Access 6. Set the Launch and Activation Permissions as follows: Edit Limits Administrators => Local/Remote Launch + Local/Remote Activation Distributed COM Users => Local/Remote Launch + Local/Remote Activation Everyone=> Local Launch + Local Activation Offer Remote Assistance Helpers => Local/Remote Launch + Local/Remote Activation Edit Default Administrators => Local/Remote Launch + Local/Remote Activation INTERACTIVE => Local/Remote Launch + Local/Remote Activation SYSTEM => Local/Remote Launch + Local/Remote Activation 7. Test the connectivity by using the Windows Management Instrumentation Tester. After configuring the permissions on the remote server, the probe is able to discover the host, read the CPU statistics and Fetch the process size. 134 rsp Guide

135 Determine Process Size Determine Process Size Determine the process size if the RPC ports are accessible from rsp. Note: Fetching the process size is impacted in case you do not open this port. Other features would have no impact. Symptom Error status = ba is generated in the log file while fetching process size that indicates a firewall is blocking the access. Solution Follow these steps for enabling RPC Port from Windows Firewall: 1. Add a rule that allows RPC Dynamic Ports in Windows Firewall. 2. Go to Windows Firewall with Advance Security. 3. Right-click on the Inbound rule and click the new rule. New Inbound Rule Wizard opens. 4. Select Custom and goto Next. Chapter 8: Troubleshooting 135

136 Determine Process Size 5. Select the Protocol type as TCP, Local Port as RPC Dynamic Ports and Remote port as All ports and goto next. 6. Provide the IP addresses of RSP probe or let it remain as Any IP address and click Next. 136 rsp Guide

137 Determine Process Size 7. Select Allow the connection (Default) and goto Next. 8. As per your requirement, select whether the new rule applies to the domain, private, public or all. Chapter 8: Troubleshooting 137

138 Value not Displayed when WMI Profile is Configured 9. Enter the name for the rule and click Finish. Value not Displayed when WMI Profile is Configured If remote system is slow to respond, then it takes long time to fetch class or instance information. If, these values do not appear: Follow these steps: 1. Go to General Setup. 2. Increase Command Timeout and WMI Connection Timeout. 138 rsp Guide