NonStop Cluster Performance Essentials User Guide Version 2.2 Part Number 544813-004 Abstract This manual describes the installation, configuration, and user interface of the HP NonStop Cluster Performance Essentials plug-in to HP Systems Insight Manager (SIM). Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.10 and all subsequent H-series RVUs, and G06.
Table of Contents 1. INTRODUCTION..........................................................................................................................................5 2. NEW FEATURES...........................................................................................................................................7 3. 2.1. CLIM PERFORMANCE MONITORING AND REPORTING ..............................................................................7 2.2.
4.3.8. 5. USING THE USER INTERFACE...........................................................................................................39 5.1. OVERVIEW ................................................................................................................................................39 5.2. PERFORMANCE MONITORING ..................................................................................................................40 5.3. TREND GRAPHS ......................................
9.2.1. For LINUX Agent .......................................................................................................................78 9.2.2. For NonStop Agent...................................................................................................................78 9.2.3. For PE SIM Plug-in ...................................................................................................................
1.Introduction The HP NonStop Cluster Performance Essentials software provides plug-in components to HP Systems Insight Manager (SIM) to support performance monitoring of heterogeneous clusters consisting of a combination of NonStop™ and Linux servers. The software allows a user to monitor the performance of Linux and NonStop clusters or individual servers using the HP SIM interface.
threshold values that will trigger an event alert notification. The notifications can be routed via email or SMS text. Product Web site: A web site, www.HPNonStopPerformance.com, is maintained for communication of information about the HP NonStop Cluster Performance Essentials software. Users are encouraged to access and register with this page. Information relevant to the plug-in, such as release history, FAQ’s, feature list, etc. is made available on this site.
2.New Features 2.1. CLIM performance monitoring and reporting HP Performance Essentials 2.2 includes support for monitoring of CLIM entities and reports the related metrics. NonStop specific – CLIMAGT, CIPSSRV, CIPMON and PROV, and Linux specific – CPU, Process, Disk, and Network entities are monitored. Thresholds can be set for each of these entities and applicable notifications are sent out using the Performance Essentials notification delivery methods. 2.2.
3.Overview 3.1. Architecture The following provides an overview of the Performance Essentials product architecture: Figure 1 – Architecture Figure 1 shows the high-level architecture of the product. The directions of arrows indicate flow of information. Linux and NonStop servers can be managed by the Performance Essentials SIM plug-in. A managed server has an agent to collect performance metrics.
Performance Monitor and Alert GUI can be invoked as a web-tool from HP SIM tools menu. The Performance Monitor component queries the performance database for the latest snapshot data for the selected target systems or cluster. All the received data are then categorized and presented in a separate window. This component is responsible for data representation only. Alert Settings in this interface can be used to construct new alerts. Each alert has a unique ID associated with it.
volume. Collectors are expected to read the port number from the configuration file. On the NonStop, the communication takes place through IPC, with the collectors and worker writing to the collator’s $RECEIVE. The names of the various processes are specified in a configuration file and must be consistent. Collectors running in a server report data to the Collator periodically. Collator maintains the latest performance data from each collector.
3.3. Online Help The software provides extensive online help to the user. Every function provides a link to the particular section of the User Manual that is relevant to the function being performed. A click on the icon on the upper right-hand corner invokes the Help information. [Back to TOC] 3.4.
or online help section on Configuring Automatic Discovery and Adding a System Manually. The user name and password information for each of the agents on the servers must also be supplied in the WBEM/WMI section of the System Protocol Settings page in SIM. Once discovery of each system occurs, the system will appear in the All Systems table.
be requested. For the installation of a NonStop agent, here is some of the basic information about the NonStop server that is needed before the installation: Server name IP address or DNS name Port number to be used for communication between the CMS and agent on the managed node Installation volume and subvolume (target directory) User name and password For Linux agent install, see section on Linux Agent Install for details and requirements. [Back to TOC] 3.7.
Make sure that the Serial Number is copied exactly as it is in this output because the registration is case sensitive. For the Node Name of your Linux system, make sure you use exactly the same name as what you used to define the node in Clusters Essentials. For NonStop, you must know the exact Serial Number (including leading zeros) and Node Name of your NonStop system in order to register. It is recommended to use SYSINFO to verify the information before starting the registration process.
Quick Install Guide section. If there were issues with invoking the license, the user will receive an email stating “Unable to retrieve License” and if debug mode is enabled for error logging a message will be recorded in the mxdomainmgr.0.log log stating “Unable to retrieve license SerialNumber Serial Error PE Linux/NonStop, V01/H01 was unable to retrieve a license for this system. Please send an email to PerformanceManagement@hp.com with your system details”.
4.Installation and Dependencies 4.1. Linux Agent Install 4.1.1. Instructions and Requirements Please refer to Hardware and Software Requirements for required hardware and software. The Linux agent installer package is a RPM (Redhat Package Manager) package. The RPM package is located in two separate folders on the Linux Agent cd.
Parameters page, then click Run Now. 10. Verify successful completion. The rpm pre-install process will check for JRE installation as well as its version. If JRE 1.5.0_10 or later is not found, rpm will exit with appropriate error message. Otherwise, successful installation will install Linux agent. Agents are installed in /var/www/html/simagent-0.1 directory because the default web server used by Enterprise Edition Redhat Linux is Apache web server.
/collator - Collator maintains the latest performance data from each collector Collator.jar Collator.sh xerces.jar /collector - Collector gathers data from the Linux server clientV userHz Collector.jar Collector.sh xerces.jar /license - License handler licensehandler.jar licensehandler.sh PELicense.log /pamauth - Pamauth authorizes users on the Linux server PAMAuth.jar pamrun.sh /Native libjass-pam.
4.1.3. Agent Startup In order for the Linux agent to collect data, it needs to be started up and running. To startup the Linux agent, follow these steps: 1. Start up the license handler module by going to /var/www/html/simagent0.1/license directory and executing ./licensehandler.sh 2. Startup the authorization module, PAMAuth by going to /var/www/html/simagent-0.1/pamauth directory and executing ./pamrun.sh. 3. Start up the collator by going to /var/www/html/simagent-0.
Figure 2 – License Handler, PAMAuth, Collator, Collector [Back to TOC] 4.1.4. Checking Agents Running In order for the user to monitor Linux servers, the Linux agents must be running smoothly. To check if Linux agents are running correctly follow these steps: Check that the license handler, collator, collector and pamauth module are running on the Linux server as figured above. Check that the web server is running. For the Apache web server, this can be performed by running: /etc/init.
4.2. NonStop Agent Install 4.2.1. Instructions and Requirements Please refer to Hardware and Software Requirements for required hardware and software. 1. FTP the following files to $system.zpe. (Note: The user may FTP the files to a different $volume.subvolume.
The following files have to be transferred in 'ASCII' Mode: * COLLCONF * INSTPE * MAKELIC * MKMEASDB (Only G-series) * PECONF * RSTCOLL * SQLCONF * SSLCONF * STOPPE * STRTPE * WRKCONF Note: The certificates (SERVCERT, SERVKEY, CACERT) being delivered with the NonStop Agent are for testing purposes only. Do not use them in a production environment! 2. Obey the Install file 'INSTPE'. (Read the following instructions first.) 2.1 Set the working volume to $system.zpe (or to $volume.
d) Opens the STRTPE file in block mode Edit so that the user can set the following basic options: d.1 PARAM LISTENER-PROCESS <$abcd> This is a required parameter. It provides the process manager with the process name with which to start the TCP Listener. Example: PARAM LISTENER-PROCESS $ZPE02 d.2 PARAM TCP-PROCESS <$abcd> This is an optional parameter. This is passed to the TCP listener by the process manager and indicates what TCP process to use to communicate with PE SIM plug-in component.
e) Opens the STOPPE file in block mode edit, so you can set the corresponding process names in the STOPPE file that you specified in the STRTPE file so that all processes will be successfully stopped. e.1 Note: Again, if you are not using CLIMs on your NonStop system, you will need to disable the CLIM collector modules from running by commenting out the following lines: STOP $ZPE08 STOP $ZPE08 f) Opens the PECONF file in block mode edit.
i) Opens the SSLCONF file in block mode edit, so that you can set the following basic options: Note: The SSLCONF file is the SSL Configuration file which you should modify. We have provided test SSL files for you as defaults, but SSL will not work properly if you do not modify these files yourself. i.1 servkeypass This is a required configuration. The user must input the password for their private key file. By default we have used 'test' as the password for the private key. i.
k) Obeys STRTPE to start Performance Essentials agents by starting the following processes: Process Manager, Process Metrics Collector, CPU Metrics Collector, Collator, and other Measure specific collectors. l) To install the NonStop Agent EMS templates which cause Performance Essentials Agent generated messages to show up with the NonStop Agent SSName (instead of the SSID), please refer to Section on Installing NonStop Agent EMS Template. 3.
4.2.2. Installing NonStop Agent EMS Template In order to map the PE Agent Subsystem ID to its Subsystem Name for generated EMS messages by PE Agent, the PE Agent EMS template file needs to be installed. This will cause the PE Agent messages to show up as TANDEM.ZPE instead of TANDEM.282. To install the NonStop PE Agent EMS templates. Please follow the steps listed below: 1. Logon to the system as SUPER.SUPER. Go to the PE Agent installation Subvolume and run the following command. Run PETMPAK 2.
8. Pick a pair of names for your new resident and non-resident template files. Make sure files do not already exist with these names. For our example, let us assume that the new names will be: NewRes (for the new resident template) NewNRes (for the new non-resident template) 9. Enter the following command to create the new template files. INSTALL^TEMPLATES NewRes NewNRes CURRENT^TEMPLATES $SYSTEM.ZTEMPL 10. These files are created in your current subvolume, which we had set to $SYSTEM.
4.2.4. Checking Agents Running In order for the user to monitor the NonStop servers, the NonStop agents must be running smoothly.
Figure 3 – NonStop processes [Back to TOC] 4.3. Performance Essentials SIM Plug-in Install 4.3.1. Instructions and Requirements Please refer to Hardware and Software Requirements for required hardware and software. PE SIM plug-in installer is a self-extracting installation wizard. This simple wizard will ask for the SMTP server settings (SMTP Host, SMTP User Name, and SMTP Password) which are each limited to 50 characters in length.
4.3.2. Initial Setup PE SIM plug-in collects performance data from all live, configured Linux and NonStop servers once per minute. It analyzes the data and determines if any alert is to be triggered. If so, the user is notified according to the notification criteria. By default, 40 intervals of historical data are retained in the database. The actual number of intervals of historical data is divided by the greatest amount of systems that you have Linux or NonStop agents running on.
default, the WBEM port used by Performance Essentials is 8888 for NonStop agents and 443 for Linux agents. The user should not use this port number configuration to specify which port Performance Essentials is running. After the credentials have been supplied the user should click “OK” and then click “Save”. A new entry should be created in the Discovery table. Select the “discovery task” that was created and click “Run Now”. The discovery of the servers invokes the discovery of the cluster.
the user will need to login to SIM and use the top SIM Menu: Configure -> NonStop Cluster Essentials -> Refresh PE... to sync up these modifications. [Note: After the refresh is complete, the status icons in the PE Column for the SIM Homepage are cleared. On retrieving information from the nodes, the status icons are displayed. This may take a couple of minutes depending on the task interval]. After this is completed, the performance task scheduler will automatically start up.
5) After the Performance Essentials has finished, it will automatically restart HP SIM. Once SIM has completely restarted, the PE column should appear in the main SIM table, along with the PE Configuration Management… and Refresh PE… utilities which should be accessible via the Configure -> NonStop Cluster Essentials menu in SIM.
d) Login to SIM and use the top SIM Menu: Configure -> NonStop Cluster Essentials -> Refresh PE... to sync up these modifications. NOTE: i) If you don't have entry for an agent on NONSTOP, the default port 8888 will be used. ii) If you don't have entry for an agent on LINUX, the default port 443 will be used. 9) Wait for the Performance Essentials status icons to appear in the PE column of the SIM Systems Table. Icons for Linux agents may take longer to appear than icons for NonStop agents.
d) Check to ensure that the Ports.properties file has correct IP addresses and corresponding port numbers. For NonStop, the port number should match the configurations inside your WRKCONF file. For Linux, the port number should be the port where your webserver is running. [Back to TOC] 4.3.5. Adding Agents (Nodes) To add an agent to Performance Essentials, either by itself or to an existing configuration, follow these steps.
(2) For SIM v5.3: -----------a) Use the top SIM Menu: Options -> Discovery, click on "New" Note: You may use automatic discovery, but manual discovery seems to work best. b) Give a name to this discovery task and type in the IP address of the agent. c) Uncheck "Automatically execute discovery every _ minutes" Note: Unchecking this option seems to work best. d) Click on "Credentials" and supply the sign-in credentials for the agent.
4.3.7. Upgrading To upgrade from one version of software to the latest, remove the old agent software by following the instructions in Removing Agents section and then use the installation instructions to install your latest version of the software. For the PE SIM Plug-in, follow the instructions in Uninstalling section and then use the installation instructions to install your latest version of the software.
5.Using the User Interface This section provides the operational details of the user interfaces of HP NonStop Cluster Performance Essentials. 5.1. Overview Once the Performance Essentials SIM plug-in component is installed successfully, an additional status column named PE appears in the System and Cluster tables of HP SIM. Only discovered and configured NonStop clusters and their member servers will have status icons in this column.
5.2. Performance Monitoring The Performance Monitoring and Alert Management page can be invoked by clicking the status icon in the PE column for a cluster or a server. The page has a tree view on the left side in a frame, which can be expanded, down to the entity level for a particular NonStop or Linux server. Each node in the tree shows the overall status of that node (tree node) where the most severe status of the sub-tree under that node is propagated upwards.
frame. A simple table shows the time when this page was refreshed last, time in second(s) remaining before the next refresh, and the current selected node in the exploration tree. Like the Last Refresh time shown in the auto-refresh table, the Last Refresh timestamps shown in the Monitor tab reflects the current PC time of the last refresh interval.
Monitor and Alerts. If the user clicks on a node in the tree on the left side, Monitor is automatically selected and a context-sensitive status table is shown. For example, if a particular cluster is selected, the table will list all the servers in the cluster. Each server will be listed on a separate row. The columns represent server name, group name, and entity names. All the names and status icons can be clicked on, and the tree will be expanded to that level accordingly.
If a single entity is selected from the tree or a status icon is clicked on in the status table, the current data for the selected entity will be displayed on the right side panel. When a particular entity is selected, this page also shows trending and trend settings options for the parameters of that entity as seen in the figure below. Note that for each entity, the amount of data that is collected and stored is configurable; refer to Configuration Options section for more details.
5.3. Trend Graphs Trending is only shown when an entity is selected. Trending includes a Trend Settings panel and the actual graph canvas. The trend graph is a paged graph where the user can set the number of intervals to be shown on the page. Pages can be navigated for convenience. The graph is refreshed according to the refresh policy described below. User may choose different settings and click ‘Apply’ to display a different graph under new settings.
5.3.1. Type-I Graphs Figure 9 – Type-I Graph Setting options: Metric/Param Specific or All objects Date / Time to start the display from Number of intervals to show on the graph Whether the graph floor (minimum value of Y-axis) is set to zero or the lowest of the displayed values. Whether the scale (maximum value of y-axis) is set to 100% (when % is reported) or the maximum of all available values in the trend database for the displayed objects.
Display: One line per object per interval Objects identified on the legend Controls: Prev and Next buttons to move through available data Pause/Resume switch button to allow the graph to refresh with the latest data or pause at a static time interval. Legend link to click on, in order to set the graph exclusively to that object. Graph behavior: At first, a default graph of all objects for 4 intervals is displayed.
interval than at the start. In such a case, where negative values are being reported, you might notice that: a) If the Graph floor is set to "Zero", the negative value point will not be plotted. b) If the Graph floor is set to "Minimum value", the graph will adjust itself to show the negative values. [Back to TOC] 5.3.2.
Setting options: Metric/Param Top “N” (1 to maximum configured for that object type) or “Only” one or more selected objects. For processes, the maximum number of objects is different for NonStop and Linux. Linux nodes can view up to 25 processes, whereas NonStop nodes can only monitor up to 10.
At first, a default graph of the top 5 objects for 10 intervals is displayed. If the graph is left as is, it displays the new data as it becomes available when not paused. o If top N is selected, Then, the graph is completely redisplayed as the new data is collected. This is due to the fact that the top N reported for a new interval may be (and in many instances are) different from the top N of the previous interval.
Note that the Top N set may change in the next interval, and the graph may look completely different after refresh. To select a different metric, use the Metric dropdown menu. However, the top N objects are always selected based on the first metric. Therefore, choosing a different metric will cause this metric to be graphed, but the objects shown on the graph will be the top N objects with respect to the first metric.
Figure 11 – SIM configuration settings It is also important to note that if the Threshold Notification Methods are not set, they will be set to the default settings and only the Console notification will occur. Even though the default settings have email as the method of notification, no alert will be sent out without an email address added to the Email box. Similarly, if the SMS radio button is selected, no SMS text alert will be sent out without a valid phone number and service provider.
Figure 12 – Threshold Settings [Back to TOC] 5.4.1. Thresholds Several alert thresholds come predefined with Performance Essentials for serious error conditions. Users can also specify custom alert thresholds or alter the existing ones. Predefined alerts cannot be permanently deleted, however. Thresholds for a given Entity-Metric combination can be set and a severity level can be specified for this combination. The threshold can be given any user-friendly name. The thresholds can trigger a notification.
New thresholds are set using the SET tab, and existing ones can be deleted/modified using the EDIT tab. Note that if an alert is altered, it will change the previously logged alerts. If the alert’s severity is changed, all instances where the alert was logged will become the new status. If the value of the threshold is altered, all instances in the log will be matched against the revised threshold and if it no longer meets the criteria, it will mark the logged instances as “recovered”.
The following table explains the various fields in the above screen: Apply To: Indicates the nodes to which the threshold will be applied. Depending on the selection in the tree, this field will be automatically populated. A threshold set at a tree node will be automatically applied to all the nodes within that sub-tree. Name: Specify/Select the name of the threshold. Note: Can only be up to 15 characters in length. Entity: Select entity to which the threshold is applied.
Also, each metric has a maximum value for which an alert threshold can be set.
CIPSSRV UDP SOCKETS CURR CIPSSRV TCP CONNECTIONS CURR CLIMAGT BUFFER-DENIALS CLIMAGT ITAPI-ERRORS CLIMAGT LINUX-ERRORS CLIMAGT BFR-BYTES-IN-USE-CURR CLIMAGT TOTAL-RECV-MSGS CLIMAGT TOTAL-SEND-MSGS CLIMAGT QUEUED-COMMANDS CLIMAGT FAILED-COMMANDS 10,000 10,000 10,000 10,000 10,000 10,000 CIPMON BUFFER-DENIALS 10,000 CIPMON ITAPI-ERRORS CIPMON LINUX-ERRORS CIPMON BFR-BYTES-IN-USE-CURR CIPMON TOTAL-RECV-MSGS CIPMON TOTAL-SEND-MSGS CIPMON QUEUED-COMMANDS CIPMON FAILED-COMMAND
PROV BUFFER-DENIALS PROV ITAPI-ERRORS PROV LINUX-ERRORS PROV BFR-BYTES-IN-USE-CURR PROV TOTAL-RECV-MSGS PROV TOTAL-SEND-MSGS PROV QUEUED-COMMANDS PROV FAILED-COMMANDS CLIM CPU CPU Busy CLIM CPU Memory Used CLIM Process BUSY CLIM Disk IORATE CLIM Disk Usage CLIM Network General Send Count CLIM Network General Receive Count CLIM Network Protocol TCP Send Count CLIM Network Protocol TCP Receive Count CLIM Network Protocol UDP Send Count CLIM Network Protocol UDP Receive Cou
Note: If you are running both Linux and NonStop agents and want to set an alert for Disk entity with First Notification and/or Recurring Notification set to occur after a selected amount of minutes, create alerts for Disk entity only at the node level. If you create this particular alert at a higher level, then this alert notification will not be enacted for Disk. This consideration applies only for the Disk entity.
these events again, switch back to the “Latest” view. Threshold: Any: Display the alert entries for any threshold. Only: Display the alert entries only for the specified threshold. Severity: Display the alert entries of the specified severity. When the condition for a given threshold is no longer met, an alert recovery notification is sent out. For notifications to be delivered to the console, the recovery information is set for every alert that was logged.
5.4.3. Alert Considerations These are things to consider before creating alerts. All alert names must have unique names meaning that you cannot create an alert with the same name as any other alert, pre-defined or user-defined. There are pre-defined alerts set for CPU Busy counter and Process Busy counter that can be edited, but not deleted. These pre-defined alerts for these two counters are named as CPU CRITICAL, CPU WARNING, PROCESS WARNING and PROCESS CRITICAL.
6. Configuration Options 6.1. Overview With the installation of Performance Essentials plug-in, HP SIM Configuration menu provides the functions to configure NonStop and Linux agents and Performance Essentials SIM plug-in component of the HP NonStop Cluster Performance Essentials.
[Note: After the refresh is complete, the status icons in the PE Column for the SIM Homepage are cleared. On retrieving information from the nodes, the status icons are displayed. This may take a couple of minutes depending on the task interval]. [Back to TOC] 6.2. SIM Configurations 6.2.1. SIM v5.2 For SIM v5.2, the configuration settings can be accessed from HP SIM main menu by following Options -> Protocol Settings-> System Protocol Settings. Figure 17 – Launching System Protocol Settings for SIM v5.
Figure 18 – System Protocol Settings for SIM v5.2 Use the WBEM settings to create access to SIM. Select the “Update values for this protocol” checkbox, and use the “Use values specified below” radio button. It is not necessary to enter the port number. Supply the user name and password of the owner of the agent process running on this particular system. Please make sure to NOT use credentials as “root” in the username/password field.
6.2.2. SIM v5.3 For SIM v5.3, the configuration settings can be accessed from HP SIM main menu by following Options -> Credentials-> System Credentials. Figure 19 – Launching System Credentials for SIM v5.3 From here, target systems will be requested. Select “All Systems” from the target systems dropdown list to get a list of all the systems.
Use the WBEM settings to create access to SIM. Supply the user name and password of the owner of the agent process running on this particular system. Please make sure to NOT use credentials as “root” in the username/password field. After adding all this information, click the “OK” button from the bottom of the page to save the settings.
6.3. PE Refresh Performance Essentials provides a refresh mechanism for the user to be able to refresh SIM and Performance Essentials with updated NonStop Cluster Configurations. To access this tool, use the HP SIM main menu by following Configure -> NonStop Cluster Essentials -> Refresh PE… as depicted in the figure below. Figure 22 System Protocol Settings for SIM v5.
6.4. PE SIM Plug-in Configuration Clicking on the SIM tab shows the PE SIM plug-in configuration settings in a simple table. Currently, PE SIM configuration setting includes Sample Retention value, Refresh Interval value and SMTP server settings. The Sample Retention value determines the size of historical data in number of intervals that are stored in the database. The default is 40 intervals, and the maximum is 500.
6.5. Agent Configuration Figure 24 – Agent Configuration Clicking on the Agent tab shows all the configured clusters in a tree format. The root node lists all the clusters. There are at most two groups of servers under a cluster: NonStop servers and Linux servers. If a particular node is clicked in the tree, a table with all applicable entities appears in the right hand frame. For example, if a particular NonStop server is clicked, the table contains only the NonStop entities.
applicable to a particular entity, no text box appears in that cell. Note that the right-hand table is context-sensitive to the selected node in the lefthand tree. This also means that the configured parameters are applied to all the nodes that are in the sub-tree of the selected node. For example, if Linux Servers is selected and there are three Linux servers under that node, then the Performance Essentials agents in all three Linux servers are updated.
6.6. Agent Configuration Files 6.6.1. Linux Agent Configuration.properties lists configuration properties for the worker, collator, collector and PAMAuth objects. It lists the following properties: o WORKER.FILE - Location of the worker.php o COLLATOR.PORT - Port number that the collator listens on. o PAMAUTH.PORT - Port number that the PAMAuth module listens on. o .MONITOR - Specifies if metrics for the entity are to be collected. Value=true/false o .
specified in XML format. SQLCONF Lists the fully qualified program file names of the SQL Procedures to monitor. Each program file is specified on separate line. STRTPE Obey script to start the NonStop Performance Essentials Agent. It lists Assigns and Params to be used by different program objects. o ASSIGN PROGCONF1 – Name and Location of the configuration file that specifies information for HSCWRK object.
7.Configuration Parameters 7.1. Linux Agent Properties Name File Default Description WORKER.FILE Configuration.p /var/www/html/simag Location of the worker.php roperties ent-0.1/worker.php Configuration.p --dynamically Port number that the collator roperties populated-- listens on. Configuration.p --dynamically Port roperties populated-- PAMAuth module listens on. .MONIT Configuration.p True Specifies if metrics for the OR roperties COLLATOR.PORT PAMAUTH.
7.2. NonStop Agent Assigns Name File Default Description PROGCONF1 STRTPE WRKCONF Name and Location of the configuration file that sp information for HSCWRK object CPUCONF STRTPE COLLCONF Name and Location of the CPU collector file. It is used b CSVRAPP process. DATAFILE STRTPE PEMEASM Name and Location of the datafile to be used by the Me collection started by the measure collectors.
Others The program file names of each of the SQL Procedures that are to be monitored need to be specified in the SQLCONF file. [Back to TOC] 8. Tips and Trouble Shooting Most problems with Performance Essentials can be solved quickly by following the advice in this section. 8.1. Installation If you are not sure the install completed successfully For the PE SIM Plug-in component check the following; o performanceUpdate.
For the Linux Host Agent component check the following; o File list matches files installed and created in your Linux Performance Essentials directory as outlined in 4.1.2 Initial Setup for Linux Agent. If all checks are OK then the component(s) install should be OK, if not then best to un-install and re-install the component using the appropriate steps. [Back to TOC] 8.2.
If all checks are OK then the component(s) activation should be OK, if not then corrective (using the appropriate steps) action is required to satisfy the checklist. [Back to TOC] 8.3. General If the PE status column is present but no data is displayed For the SIM Plug-in component check the following; o Use Refresh PE from SIM menu: Configure -> NonStop Cluster Essentials -> Refresh PE... to resync Performance Essentials with SIM and Cluster Essentials.
If the PE status data stopped refreshing after working OK For the SIM Plug-in component check the following; o Use the checks for the NonStop and Linux agents to see that they are running. o Enable the SIM Debug and set Debug Levels for com -> sim -> performance -> comm to 20. This will log messages to the mxdomainmgr.0.log file within your SIM installation directory on your CMS. For the NonStop Host Agent component check the following; o Measure Subsystem (Meassubsys) needs to be running.
9.Appendix 9.1. Software Support Support is available through HP's 24-hour Global Mission Critical Support Centers (GMCSC) throughout the world. In the U.S. call 1-800-255-5010. International numbers see: http://h71014.www7.hp.com/gcscphone.html [Back to TOC] 9.2. Hardware and Software Requirements 9.2.1. For LINUX Agent Required Hardware: Apache or any other webserver that supports PHP Minimum OS Release: RedHat Enterprise Linux 4.
Microsoft Windows Vista Enterprise or Microsoft Windows XP Professional with Service Pack 2 Required Software: SQL Server 2000 or later HP System Insight Manager (SIM) 5.2 or 5.3 HP NonStop Cluster Essentials V2 Java Runtime Environment (JRE) 1.5.
