HP SiteScope Release Notes
for the Windows, Solaris, and Linux operating systems
Software version: 10.13
Publication date: November 2010
This file provides information about HP SiteScope 10.13.
Installation Prerequisites and Instructions
Note: For release notes from earlier versions of HP SiteScope, see the root directory on the product installation media.
Documentation Updates
The first page of this release notes document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals
To retrieve a document, select the:
1. Product name.2. Version list.3. Operating System.4. Preferred Language.5. Document title.6. Click Open or Download.You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.
Installation Prerequisites and Instructions
- SiteScope 10.13 must be installed on top of SiteScope 10.1x. It should be installed on a standard SiteScope installation only (not on System Health or other SiteScope type installations).
- You can upgrade SiteScope versions 9.0 and later directly to SiteScope 10.10. For versions of SiteScope earlier than 9.0, you must first upgrade to SiteScope 9.0.
Installation Instructions
Read all information in this section before starting the installation.
- Before installing SiteScope 10.13, it is recommended that you back up your current SiteScope installation directory and all of the subdirectories within the directory.
- Before installing SiteScope 10.13, make sure the SiteScope process/service has been stopped.
- If you already have SiteScope 10.1x installed, install SiteScope 10.13 by double-clicking the setup file and following the on-screen instructions. After installing SiteScope 10.13, restart SiteScope.
- If you do not yet have SiteScope 10.10 installed, install it according to the instructions in the HP SiteScope 10.10 Deployment Guide. After installing SiteScope 10.10, install SiteScope 10.13 by double-clicking the setup file and following the on-screen instructions. After installing SiteScope 10.13, restart SiteScope.
- After upgrading to SiteScope 10.13, you can import monitor configuration data from previous versions of SiteScope directly to SiteScope 10.13 using the Configuration Tool.
SiteScope 10.13 Rollback Instructions (Windows)
- To uninstall SiteScope 10.13, follow the instructions below.
- Stop the SiteScope service.
- Select Control Panel > Add/Remove Programs > Change or Remove Programs, and make sure the Show Updates option is selected to ensure that the service pack version is displayed beneath the root entry. Select HP SiteScope 10.13, click the Change/Remove button, and follow the uninstall wizard instructions.
- When the uninstall process is complete, restart the machine if requested.
- To uninstall SiteScope and any updates installed on top of it:
SiteScope 10.13 Rollback Instructions (UNIX)
- To uninstall SiteScope 10.13, follow the instructions below.
- To uninstall HP SiteScope 10.13 and any updates installed on top of it, follow the instructions below.
- Stop SiteScope by running the stop shell script included in the <install_path>/SiteScope directory. An example command line to run the script is: SiteScope/stop
- If you work in X Windows mode, run the following command: /opt/HP/SiteScope/installation/bin/sis_uninstall.sh
- If you work in console mode, you should:
1. Uninstall SiteScope 10.13 by running the command: /opt/HP/SiteScope/Uninstall/HPSiS1013/setup.bin -i console
2. Uninstall SiteScope 10.10 by running the command: /opt/HP/SiteScope/Uninstall/HPSiteScope/setup.bin -i consoleChanges and Enhancements
Virtualization Enhancements
Performance improvements were made in the VMware Performance monitor user interface and on the server-side. To benefit from these improvements, you must configure the monitor and the system according to the instructions in Best Practices for Configuring Filter Options on the VMware Performance Monitor and Server-Side Improvements in the "Documentation Changes" section below.
- User Interface Improvements. Added filtering capabilities to the VMware Performance monitor in the VMware Performance Monitor Settings panel:
- Get real-time data only. Select to retrieve real-time metrics data only and exclude historical metrics data. Default value: Not selected.
- Get VMs and Hosts in powered on state only. Select to retrieve metrics data from powered on VMs and hosts only (data from powered off VMs/hosts is excluded). Default value: Not selected.
- Virtual machine. Enter a regular expression to match the name of one or more virtual machines. When you apply this filter, only the virtual machines that match this string are displayed in the Get Counters list. Click the Open Tool button to use the Regular Expression tool to check the correctness of your regular expression.
- Host. Enter a regular expression to match the name of one or more system hosts. When you apply this filter, only the system hosts that match this string are displayed in the Get Counters list. Click the Open Tool button to use the Regular Expression tool to check the correctness of your regular expression.
For information on how to correctly configure these settings, see Best Practices for Configuring Filter Options on the VMware Performance Monitor below.- Server-Side Improvements.
- Added a new connection pool mechanism to the VMware Performance monitor that reduces the load on vCenter and SiteScope by reusing connections. (Previously, SiteScope opened a connection against vCenter or an ESX host every time the monitor communicated with vCenter or the host.) For more details on the connection pool and the new configuration properties, see Server-Side Improvements in the "Documentation Changes" section below.
- Enhancement Request Fixes.
- Normalized the values used for reporting percentage metrics (for the CPU and Memory counters). See Enhancement Request Fixes for more details.
- Added option to use the VMware Performance monitor without having to import SSL certificates. See Enhancement Request Fixes for more details.
SiteScope iPhone application
- SiteScope 10.13 supports the SiteScope iPhone application (which will be available shortly from the iPhone App Store, http://www.apple.com/iphone/apps-for-iphone/). This is a free download that enables you to keep track of your monitored IT infrastructure while away from your computer.
- Using the iPhone application, you can access SiteScope via an iPhone, and perform the following actions:
- Search SiteScopes to view monitor and group statistics, and perform actions on the search results to mitigate issues (enable/disable monitor/monitors in group, run monitor/monitors in group, show child monitors in group with same status as the group, set alert actions, generate reports).
- Respond to email alerts when a problem is detected in the IT infrastructure (enable/disable associated alerts, add and view acknowledgements)
- Generate ad hoc reports for monitors, groups, or generated alerts for a specific time periods.
- Add selected monitors and groups to a favorites list.
- For more details on using SiteScope on an iPhone, refer to the help supplied with the SiteScope iPhone application. For additional information on how to use the features that are available on the SiteScope iPhone application, see the relevant topic in the SiteScope Help.
Business Availability Center Integration
- Added a setting to enable data to be compressed before being sent from the SiteScope server to BAC. To enable the setting, set the property _topazCompressDataInGzip= to true in the <SiteScope root directory>\groups\master.config file. When enabled, SiteScope monitor (ss_monitor_t) and SiteScope metric (ss_t) samples are compressed in gzip before being sent to BAC (where it is decompressed). Data compression can be used only when SiteScope is reporting to BAC 8.05 or later.
New Installations
Documentation Changes
The following section supplements the current SiteScope documentation on the VMware Performance monitor. It contains best practices for configuring filter options on the VMware Performance monitor and information on making server-side improvements.
- Best Practices for Configuring Filter Options on the VMware Performance Monitor
The VMware Performance monitor is limited to monitoring 100 counters. Since every VM or host has an average of 80-90 counters, not more than one VM or host can be monitored on the same monitor with the full counter set. Therefore, you should set up the monitoring environment as follows:
1. Create a separate monitor for each VM or host.
2. Configure the following filtering options to avoid overloading the monitor:Note:
- If you do not fill the Virtual machine and Host fields, the monitor attempts to retrieve counters for all VMs, hosts, and resource pools defined in the vCenter. For example, if a vCenter has 800 VMs and 100 hosts, the monitor will try to get 80 counters per VM and 90 counters per host (this is the average number - the actual number depends on the configuration of the VM or host and may be even higher). In total: (800 VMs x 80 counters) + (100 Hosts x 90 counters) = 73 000 counters.
- The number above represents real-time data only. If historical data is not excluded (by selecting Get real-time data only), this number could be much higher, depending on your configuration.
- Since performance data can be retrieved for VMs and hosts in powered on state only, the Get VMs and Hosts in powered on state only check box should be selected. If it is not selected, historical data from powered off VMs and hosts is also retrieved.
- If you do not use filtering options, this puts the monitor under greater load as it tries to create an XML file with all the counters retrieved/configured. This causes performance problems each time the monitor properties are opened, since the monitor attempts to display a very large number of counters and create a heavy cache file.
- Server-Side Improvements
- The connection pool is a set of pools per key. A key is the combination of a vCenter/host URL and a user (the connection cannot be shared between different users due to different permissions). If all VMware Performance monitors are configured with the same vCenter URL and user, one connection pool is created. For two vCenters and two different users for every vCenter, four connection pools are created. You can configure the connection pool properties in the master.config file:
- Maximum idle connections per key (key is a set of vCenter/host URL and user):
_vmWareConnectionPoolMaxIdlePervCenterKey=500- Maximum size of connections per key:
_vmWareConnectionPoolMaxSizePervCenterKey=500- Maximum size of total connections for all keys. This is the total number of connections using all defined in SiteScope vCenters:
_vmWareConnectionPoolMaxTotal=1500- Connection timeout (in minutes):
_vmWareConnectionTimeOut=30- The connection pool configures itself over time to ensure that only working connections stay in the pool. It does this by running an additional thread at the rate of the connection timeout multiplied by two; if the connection timeout is 30 minutes, it will run once every hour and evict idle connections from the pool. Connections that are idle for more than half a minute before the connection timeout are eligible for eviction. For example, if the connection timeout is 30 minutes, the thread will evict connections that were idle for more than 29.5 minutes, but less than 30 minutes, to avoid a connection timeout. As a result, only working connections will stay in the pool.
- We recommend setting the maximum size of total connections (_vmWareConnectionPoolMaxTotal) to the number of configured VM monitors in SiteScope, and let the internal connection pool mechanism optimize itself.
Enhancement Request Fixes
Description
CR ID or SR/E-Sar Number
Area
Added the Edit layout permission to user permissions (in Preferences > User Management > Permissions > Dashboard). Users with this permission can permanently disable fields in the SiteScope Dashboard. For example, if you do not want specific users to see IP addresses of monitored servers, you can permanently hide the Target column in the Dashboard. Users that do not have this permission cannot see the columns that have been disabled.
QCCR1I40010/ 4610877695
Dashboard
Service monitor. Added the Service start mode counter to the Service monitor to indicate when the monitor is running (previously there was no indication if the service was disabled on the target server, or if it had stopped) .
Note: This counter is available when using WMI remote servers only.QCCR1I35519
Monitors
SNMP Monitor. Added a new field in SNMP Monitor Settings to enable using a privacy password when SNMP version 3 is used.
QCCR1I50409/ 4611331759
Monitors
URL Sequence monitor. Fixed issue of no logical break separating the steps into separate html pages, by adding URLs on each step into the monitor's check result page.
QCCR1I45112/ QCCR1I49609/ 4614701983
Monitors
VMware Performance monitor. Normalized the values used for reporting percentage metrics (to values between 0 and 100, instead of 0 and 10000).
QCCR1I37457
Monitors
VMware Performance Monitor. Added option to use this monitor without having to import/check SSL certificates. To do so, set the property
_vmWareConnectionAcceptAllUntrustedCerts=true in the master.config file, and restart SiteScope. (Note: You must add this property when upgrading from older versions of SiteScope.)
QCCR1I51526/ 4613901281
Monitors
VMware Performance monitor. Fixed issue of being unable to set up the monitor against a VMware image with a large number of VMs and hosts by adding filtering options. See Virtualization Enhancements for details.
Monitors
Extended the capability of the LogGrabber utility to include additional files in the output. The following were added to SiteScope\tools\LogGrabber\go.bat:
QCCR1I34439
SiteScope Tools
Added the ability to see when a template was last updated and which SiteScope user.
QCCR1I44594
Templates
Bug Fixes
Fixed issue of being unable to use auto template deployment to deploy a template where the template has no parent group defined. To use this feature, the Allow creation of template monitors directly under template entity option must be selected in Preferences > Infrastructure Preferences > Template Settings, or _allowTemplateMonitorDirectlyUnderTemplate=true must be set in the master.config file.
QCCR1I30513
Auto Template Deployment
SiteScope no longer reports the Host CI operating system attribute to UCMDB.
QCCR1I41098
BAC Integration
Fixed issue of EMS integration monitors losing reported SiteScope Monitor CIs under a high rate of Web service queries when a large number of remote servers are used.
QCCR1I48922
Integration Monitors
Fixed issue of being unable to generate a Management Report when logging on to SiteScope using LDAP authentication.
QCCR1I31883
LDAP Authentication
Fixed issue of Remote Windows SSH connectivity not working by either:
(1). Installing the contents of RemoteNTSSH2003.zip on every remote server monitoring by SSH. The.zip can be found in the <SiteScope root directory>\tools folder.
(2). Installing the required version of the Microsoft Visual C++ 2008 Redistributable (x86) package on the problematic remote server. The package is available from http://www.microsoft.com/downloads/details.aspx?familyid=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en. Since this package is part of the Windows Server 2008 R2 installation, you can skip this step when working on a clean environment.QCCR1I49773
LoadRunner Integration
Fixed issue when SiteScope is installed on Linux, of the UNIX Resources monitor being unable to get counters and instances for all objects. This was also fixed when the target was set to SiteScope server.
QCCR1I51950/ QCCR1I51945/ QCCR1I51949
Monitors
Fixed issue of being unable to clean idle SSH connections from the pool by setting the Time period for cleaning idle SSH connections from pool value in Infrastructure Preferences > General Settings. The default value is 10 minutes.
QCCR1I51437
Monitors
In the documentation for the Script monitor, corrected the information for the script's location. For details, see the Script element in Script Monitor Settings.
QCCR1I44959
Monitors
Fixed issue when using URL monitors of not being able to configure NTLM V2 when a default authorization user name and password are configured in General Preferences > Main Settings.
QCCR1I50352
Preferences
Fixed issue of monitor properties taking a long time to open when a large number of Search/Filter tags are being used.
QCCR1I50215
Performance
Fixed issue of SiteScope using both the SiteScope service account and the Remote NT Account credentials to connect to the remote server. SiteScope now uses the Remote NT Account credentials only.
QCCR1I35675
Security
Fixed issue in Web Service Tool of the Use .NET SOAP check box not working properly.
QCCR1I47605
SiteScope Tools
Fixed issue after upgrading from SiteScope 10.10 on a Linux or Solaris environment, of the Solution Templates container not being displayed.
QCCR1I51816
Solution Templates
When logging in to SiteScope using LDAP authentication and specifying multiple LDAP service providers, you can enter either the hostname and/or the IP address of each LDAP service provider separated by a semi-colon (";") in the LDAP service provider field in User Management Preferences. SiteScope reads the list of LDAP service providers and searches for the available provider from the list. Previously, the IP address of the available server had to be specified, which meant that only one server could be searched.
QCCR1I49649
User Preferences
Escalation Fixes
Notes and Limitations
Description
CR ID or SR/E-Sar Number
Area
To improve performance, SiteScope uses a topology cache when sending topology data to Business Availability Center's CMDB. If SiteScope attempts to send an existing CI to the CMDB, the CI may not be sent, or created in the CMDB, for up to a week because of the way the topology cache works.
This could happen in the following circumstances:
- Cut and paste a monitor from one group into a new group. The original group is left empty. Cut and paste the monitor from the new group back into the original group.
- In HP BAC Integration Settings, disable data and topology reporting for a monitor and then enable again.
- A CI that has been manually deleted from the CMDB is not created again until the cache is cleaned out. (EMS flow - Deleting EMS monitors from the CMDB)
Workaround: If you cannot wait approximately one week to see the CIs, you can manually synchronize the data as follows: In Preferences > Integration Preferences, edit the relevant integration and in the BAC Preferences Available Operations area, click Re-synchronize.
BAC Integration
Deploying SiteScope templates while registering a SiteScope to Business Availability Center may cause a loss of topology data reported to Business Availability Center. It is recommended to avoid making configuration changes while performing Business Availability Center registration.
BAC Integration
When working in System Availability Management Administration, the Link Monitor to CI function within SiteScope monitor configuration may not work properly if popups are blocked by the Business Availability Center server.
Workaround: Create the link in Business Availability Center using the HP Universal CMDB application (Admin > Universal CMDB > IT Universe Manager).BAC Integration
If SiteScope restarts for any reason while SiteScope establishes a Business Availability Center integration, some topology data that SiteScope forwards to Business Availability Center may be lost.
Workaround: If not all topology data was forwarded to Business Availability Center, manually synchronize the data as follows: In Preferences > Integration Preferences, edit the relevant integration and in the BAC Preferences Available Operations area, click Re-synchronize.QCCR1I28152
BAC Integration
When enabling the integration between SiteScope and HP Business Availability Center, if you enter an incorrect value in the New/Edit Integration Preferences dialog box (Preferences > Integration Preferences > Create new integration > BAC Integration), this results in a "Registration in Process" entry that cannot be deleted.
Workaround: Reopen the New/Edit Integration Preferences dialog box and enter the correct integration details, or restart SiteScope.QCCR1I24421
BAC Integration
When working under high load conditions, you should suspend all monitors before connecting to HP Business Availability Center for the first time.
Capacity Limitations
When SiteScope is integrated with HP Business Availability Center, performing various very high load operations might cause problems in SiteScope. Use the following guidelines:
- Do not run the Publish Template Changes Wizard for over 3,000 monitors at once.
- Do not run the Monitor Deployment Wizard to create over 3,000 monitors at once.
- Do not copy/paste over 3,000 monitors in a single action.
- Do not perform a Global Search and Replace to modify Business Availability Center integration properties for over 2,500 monitors at one time.
QCCR1I30633
Capacity Limitations
If SiteScope is installed on Microsoft Windows Server 2008, the time zone offset should be defined manually in Preferences > Infrastructure Preferences > General Settings > Time Zone offset, in hours, from Greenwich Mean Time (GMT). For example, if the time zone is GMT +2, type "-2" as the time zone offset. If the time zone is GMT -5, type "5" as the time zone offset. For GMT, type "-999" or "0".
4605889641 (SR)
Configuration
SiteScope group MG files are deprecated in SiteScope 11.x. Although MG files are still supported in SiteScope 10.13, the Enable configuration files option is no longer selected by default when SiteScope is installed. When upgrading from an earlier version of SiteScope that has this option selected, the MG configuration files are supported.
Configuration
When defining a Script monitor to monitor a Linux remote server using the Telnet connection and the script is defined as USE COMMAND, the match expression may not work properly. This could be caused by a limitation in the number of characters that can be used to run the USE COMMAND. By default, the terminal command line has a length limitation on the size of the command per line.
QCCR1I30899
Configuration
The Dashboard column layout in the Monitor History view cannot be saved during user sessions.
QCCR1I20806
Dashboard
When creating a Diagnostics Integration in Integration Preferences, if you select the option Include additional data, all other Diagnostics and Generic Data integrations are affected and will report additional data in the data SiteScope forwards to these applications. It is recommended to select this option only if you require this additional data for all your Diagnostics and Generic Data integrations. For details on the option, refer to the "New/Edit Diagnostics Integration Dialog Box" in the "Integration Preferences User Interface" section in Using SiteScope help.
Diagnostics Integration
The Review Summary page displays the real host name of the monitored server instead of the name by which the remote machine should be known in SiteScope. This means that you cannot differentiate between multiple remote servers created for the same host machine (for example, where one remote server uses the WMI connection method and another uses NetBios).
Global Search and Replace
When performing a global search and replace operation in a load environment of over 1,000 monitors, you may encounter an out of memory error in the Java applet on the client machine performing the global search and replace.
Workaround: Increase the heap size of the Java applet on the client machine. Click Start > Control Panel > Java > Java tab. View the Java Applet Runtime Settings and enter the following in the Java Runtime Parameters field: -Xmx128m (default is 64m).QCCR1I27880
Global Search and Replace
When using Global Search and Replace, the Server property is available only when monitors from the following group are selected: CPU monitor, Disk Space monitor, Memory monitor, Microsoft Windows Performance Counter monitor, Web Server monitor, or Service monitor. For other monitors, the Server property can only be changed by selecting that specific monitor subtype in the Select Subtype page. For example, if a CPU monitor is selected with a Web Server monitor, the Server property is available. If a monitor not from this group is also selected, the Server property is not available.
QCCR1I36248 / 4605639358
Global Search and Replace
When using the SNMP Browser Tool or the XSL Transformation Tool, the results may not be readable in languages other than English.
Workaround: Click the Save To File button, save the results to an external file, and open the file with an external editor.QCCR1I32444
I18N
For the SiteScope user interface to start, Java Runtime Environment (JRE) must be installed on the SiteScope client machine. If you are using JRE 5, you might get Java script validation errors when opening dialog boxes in SiteScope. Using Firefox 3.0 with JRE 5u14, 5u15, or 5u16 causes the applet to freeze any operation until the browser is closed.
Workaround: Configure you browser to use JRE 6u10 or later.QCCR1I20599, QCCR1I22818, QCCR1I24623
Installation and Upgrade
The SiteScope user interface does not start and the following error message is displayed: "Several Java Virtual machines running in the same process caused an error". This is a known Java defect (http://bugs.sun.com/view_bug.do?bug_id=6516270) that might occur when using Internet Explorer 7.
Workaround: Either:Installation and Upgrade
The SiteScope user interface does not start and an error message is displayed while starting the SiteScope applet (for example: "The Java Runtime Environment cannot be loaded").
Workaround: Perform the steps below. After each step, try to reopen SiteScope. If SiteScope fails again, proceed to the next step.
(1). Close all the browser's windows.
(2). End all remaining browser processes (if any remained) using Windows Task Manager.
(3). Clean the local Java applet cache. Select Start > Control Panel > Java, and in the General tab, click Delete Files and then click OK.
(4). Clean the local Java applet cache by deleting the content of the following folder: C:\Documents and Settings\<user_name>\Application Data\Sun\Java\Deployment\cache.Installation and Upgrade
SiteScope does not start after upgrading a configuration that contains a DHCP monitor if the Java DHCP library has not been installed on the server where SiteScope is running.
Workaround:
(1). Download the jDHCP library (either in .zip or in .tar.gz format) from http://www.dhcp.org/javadhcp/.
(2). Extract the file named JDHCP.jar and copy it to the <SiteScope root directory>\WEB-INF\lib directory.
(3). Restart the SiteScope service.QCCR1I32628
Installation and Upgrade
After upgrading from SiteScope 7.5 to 9.0 and then to 10.1x, if 7.5.x contained an administrator user and a regular user and the username and password for the administrator was blank, some or all of the monitors and alerts may not be displayed in the user interface after the upgrade.
Workaround: After upgrading to SiteScope 9.0, enter the username and password for the administrator user in Preferences > Users Preferences in the user interface.QCCR1I32727
Installation and Upgrade
The SiteScope menu bar opens but the applet fails to start, and you see a blank screen or an "x" image. Click Start > Control Panel > Java, and in the Java Control Panel, click the Advanced tab. Expand the Default Java for browsers folder (or <APPLET> tag support if you are using Java 5), and make sure that Microsoft Internet Explorer and Mozilla family are selected. Click Apply and then click OK.
Installation and Upgrade
If you type the incorrect license number when installing SiteScope, perform the following:
(1). Open the master.config file located in the <SiteScope root>\groups directory, and delete the _license= key value.
(2). Use the PersistencyViewer.bat tool located in <SiteScope root >\SiteScope\bin to search for the following SiteScope objects and delete their _license key value:Installation and Upgrade
The ability to report topology data to Business Availability Center was enhanced with several complex topologies (such as WebSphere, WebLogic, and so forth). SiteScope must collect the properties for these topologies on the first start after an upgrade. This may take some time because it means connecting to the monitored servers and getting the additional data. A problem may arise during this first restart if this takes longer than 15 minutes because SiteScope automatically restarts if there are no monitors running within 15 minutes.
Workaround: After an upgrade, use the following batch file to start SiteScope for the first time: <SiteScope root directory>/bin/go.bat. Once SiteScope is started, for any monitors that are monitoring environments that are not running, select Disable reporting to BAC under the BAC Logging Options. This saves wasted time waiting for the monitored servers to reply.Installation and Upgrade
An Internet Explorer exception error message is thrown inside SiteScope pages, indicating Operation aborted.
Workaround: Remove or disable the Skype add-ons on your system. For further details, see http://support.microsoft.com/default.aspx/kb/927917.Installation and Upgrade
If templates and solution templates are missing from the Templates context after installing SiteScope, copy all the templates from the <SiteScope root>\export directory to the <SiteScope root directory>\persistency\import directory (you might need to create this folder if it does not exist).
Installation and Upgrade
Monitor Thresholds. If you clear or add a counter (from the counters tree in the Monitor Settings panel) that has corresponding thresholds defined in the Threshold Settings panel, the counter might be replaced in the Threshold Settings with the next selected counter in the counter tree, replaced by the default counter, or removed from the Threshold Settings panel. This limitation applies to all browsable monitor counter types in template mode only, and to the Microsoft Windows Resources, Apache, and Health monitors in normal and template mode.
Monitors
Monitor Tree. If there is a large space between group containers in the SiteScope monitor tree, refresh your browser.
Monitors
Composite monitor. The copy to template action is not supported for the Composite monitor (if you click Copy to Template, the server names of the group of monitors that are being monitored by the Composite monitor are copied to the template with the $$SERVER_LIST$$ variable instead of the names of the actual servers).
QCCR1I27803
Monitors
Disk Space monitor. The Disk Space monitor displays slightly different results depending on the protocol that is used (NetBIOS, WMI or non-perfex based SSH).
QCCR1I28593
Monitors
File monitor. If Telnet is used as the connection method for UNIX remote servers running on an HP-UX or Linux operating system, and either (1) the LANG environment variable is unset, or (2) "set -u" is in effect and the LANG or LC_ALL environment variables are unset, the File monitor will not work regardless of the file it is monitoring.
Workaround: Permanently set the LANG and LC_ALL environment variables to the default shell for the SiteScope user.QCCR1I23798
Monitors
Microsoft Windows Event Log monitor. The Microsoft Window Event Log monitor is only able to retrieve partial data when monitoring the event log on a Windows Server 2008 because it cannot read the message DLL file.
QCCR1I30719
Monitors
Microsoft Windows Event Log monitor. The Microsoft Windows Event Log monitor is unable to monitor "Critical" event types on Windows 2008 servers. This is because the event type is not supported in the Event Type list. This limitation is relevant for SiteScopes installed on Windows Server 2008 only.
QCCR1I32441
Monitors
Microsoft Windows Media Server monitor. The Microsoft Windows Media Server monitor is unable get counters from the remote server when monitoring on Windows Server 2008 (64-bit).
QCCR1I34286
Monitors
Ping monitor. When SiteScope is installed on Solaris, the Ping monitor might take longer than expected to run, and exceed the timeout for displaying the monitor status in the popup window (the default timeout is 5 seconds).
Workaround: In the Ping Monitor Settings panel, increase the value in the Timeout (milliseconds) field.QCCR1I26236
Monitors
Script monitor. When defining a Script monitor to monitor a Linux remote server using the Telnet connection and the script is defined as USE COMMAND, the match expression may not work properly. This could be caused by a limitation in the number of characters that can be used to run the USE COMMAND. By default, the terminal command line has a length limitation on the size of the command per line.
QCCR1I30899
Monitors
Service monitor. When running the Service monitor on a Solaris environment, SiteScope is only able to display service names up to a maximum length of 80 characters (this is due to a Solaris limitation).
QCCR1I46193/ 4605843461
Monitors
SNMP monitor. When the SNMP monitor is integrated to report data to HP Diagnostics, the measurement label is sent as a name instead of the real measurement name. Workaround: Use the SNMP by MIB monitor instead.
Monitors
Technology Integration monitor.
- When creating a Technology Integration monitor for integrating measurements into HP Business Availability Center (by selecting Measurements as the Sample type in the Field Mapping area of the monitor properties), SiteScope reports only system topology data for the monitor to HP Business Availability Center. This is the standard host topology SiteScope reports to HP Business Availability Center. This cannot be changed by adding a script in the Topology Settings area. If you add a topology script, the script will fail.
- When creating a Technology Log File Integration monitor, it is recommended to perform the Test Script (during monitor configuration, in the Topology Settings area, select a topology script in the Script field and click Test Script) of the topology script using a short log file. If a long log file is used for testing the topology script, it may take several minutes.
QCCR1I25754
Monitors
After changing the user name or password of a credential profile, any open connections that are using this credential remain open and are not reconnected.
Workaround: Restart SiteScope.QCCR1I30651
Preferences
Due to a bug in Sun Java, SiteScope installed on Solaris 10 is unable to connect to a remote UNIX server via SSH using Internal Java Libraries.
Workaround: In the file <SiteScope root directory>\bin\start-monitor, add the following to the argument list of the JRE (just before the -Dflipper.param.file argument):
-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProviderRemote Servers
The Plink SSH connection method is no longer supported when working with remote servers. You should switch to the Internal Java Libraries connection method instead.
QCCR1I36368, QCCR1I36370
Remote Servers/SSH
If a Monitor Summary report is created using an Internet Explorer browser, and Export to file and Comma-delimited (csv) are selected in the Export Settings, an authentication popup window is displayed after clicking Generate Report.
Workaround: In the authentication window, click Cancel and the file opens in Microsoft Excel.QCCR1I30696
Reports
SiteScope Failover does not reset the integration to BAC when the primary SiteScope starts running again (therefore there are two SiteScope servers are reporting to the same BAC). Workaround: Perform this on both the primary and failover SiteScope: (1). In the master.config file, search for the _serverFilter property (it lists the pages that can be accessed from a browser). (2). Append the values generalprefs and topazprefs to the end of the property. (3). Restart SiteScope.
QCCR1I52159
SiteScope Failover
The current SiteScope Failover solution has been replaced in SiteScope 11.x with a new SiteScope Failover solution. The new solution is not backwards compatible with older versions of SiteScope Failover, and all SiteScopes monitored by the new solution need to be upgraded to SiteScope 11.x.
SiteScope Failover
If you experience monitor skips when using the SSH retries mechanism on a UNIX remote server, check the monitor run frequency and the _numberOfRepeatExecForSSHConnection and _UNIXSSHTimeoutSeconds property values in the master.config file to make sure they are not the cause of the skips (for example, if monitor frequency equals the SSH timeout). Note that time is used from _UNIXSSHTimeoutSeconds for every unsuccessful retry. Therefore, if the number of retries is set too high (so that it is longer than the monitor run frequency), this can increase the number of monitor skips and cause SiteScope to restart.
SSH
F-Secure is no longer officially supported when monitoring remote servers using SSH.
SSH
Copying and pasting from SiteScope 10.1x to earlier versions of SiteScope is not supported.
QCCR1I30669
System Availability Management Administration
When copying monitors, groups, or other entities between multiple SiteScope instances, tag assignments are lost even if the tags that were assigned to the copied entities on the source SiteScope are present on the target SiteScope.
QCCR1I32039
System Availability Management Administration
When copying and pasting a SiteScope monitor into a group, the monitor data can take up to an hour before it is displayed in Dashboard in HP Business Availability Center.
QCCR1I30764
System Availability Management Administration
When copying and pasting a monitor that includes a script alert from one SiteScope into another, the remote server of the script alert may not correctly copy into the target SiteScope.
Workaround: If you are copying script alerts from one SiteScope to another, ensure that the remote server accessed by the script alert exists in the target SiteScope before copying.QCCR1I32040
System Availability Management Administration
The Technology Log File Integration monitor cannot be copied from one SiteScope to another.
Workaround: Create an identical monitor on the target SiteScope (copy all monitor values to it from the original monitor). To copy a sub-tree containing Technology Integration monitors:
(1). Copy the sub-tree to a temporary location in the same SiteScope.
(2). Delete the Technology Integration monitors.
(3). Copy the new sub-tree from the temporary location to the other SiteScope.
(4). Delete the temporary location.
(5). Create the Technology Integration monitors in the other SiteScope.QCCR1I30759
System Availability Management Administration
If a template contains an invalid dependency (the template contains a dependency that existed once but no longer exists in the imported template), no dependency is shown in the template deployment. When running the Publish Template Changes wizard, the Depends on property is displayed as a difference in the Content Changes page even though there is no dependency displayed in the template.
Workaround: Add a new dependency in the template, remove it, and then click Save. This removes the non-existent dependency.QCCR1I32397
Templates
If the Method or Operating system values in a template remote server contain an incorrect value or are not entered using the same case that is displayed in the drop-down list when configuring a remote server, verification does not work properly, and the first value in the drop-down list is inserted instead.
Workaround: Enter the value exactly as it is displayed in the drop-down list on the Remote Servers page.Templates
Mail templates do not support html content. To include html content in mail templates, set the value for the _defaultMailAlertContentType property to =text/html in the master.config file.
QCCR1I32543
Templates
When using the Event Log Tool, if DNS is selected in the Log name box and the target server does not have a DNS server on it, the Application log content is displayed in the Results panel.
QCCR1I32543
Tools
When using the Database Connection Tool to apply properties to the Database Query monitor or Technology Database Integration monitor, the credential data is lost if a credential profile is selected instead of entering the credentials manually.
QCCR1I32050
Tools
System Requirements
Below are the minimum server and client system requirements and recommendations for running SiteScope, based on the various supported operating systems.
Server System Requirements for Windows
Server System Requirements for Solaris
Server System Requirements for Red Hat Linux
Note: SiteScope can be installed as a 32-bit application over 64-bit environments for the supported operating systems listed above.
Server System Requirements for VMware
The following VMware environments are supported in SiteScope according to the configurations tested below:
Use these minimum system requirements when installing SiteScope on VMware environments:
Note: Monitor capacity and velocity can be significantly impacted by numerous factors including, but not limited to the following: SiteScope server hardware, operating system, patches, third-party software, network configuration and architecture, location of the SiteScope server in relation to the servers being monitored, monitor types and distribution by type, monitor frequency, monitor execution time, Business Availability Center integration, and Database Logging. The published maximums should not be assumed to be possible in every environment.
Certified Configuration
The following configuration has been certified in a high load environment for an installation of SiteScope that was integrated with HP Business Availability Center. This configuration replaces the recommended configuration that appears in the SiteScope Deployment Guide.
Client System Requirements
SiteScope client is supported by all Microsoft Windows operating systems (including Microsoft Windows 7) using Microsoft Internet Explorer 6.x-8.0 or Firefox 2.0-3.0x.
HP SiteScope Support Matrices
HP Business Availability Center Integration Support Matrix
Note: SiteScope 10.13 integration with HP Business Availability Center 7.0x has been verified, however it is not officially supported.
HP Software Support
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:
- Search for knowledge documents of interest
- Submit and track progress on support cases
- Submit enhancement requests online
- Download software patches
- Manage a support contract
- Look up HP support contacts
- Review information about available services
- Enter discussions with other software customers
- Research and register for software training
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
To register for an HP Passport ID, go to: HP Passport Registration.
Legal Notices
© Copyright 2010 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
For information about third-party license agreements, see the Third_Party_Agreements directory on the product installation media.
Trademark Notices
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Intel®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.
Java is a registered trademark of Oracle and/or its affiliates.
Microsoft®, Windows®, Windows NT®, and Windows® XP are U.S registered trademarks of Microsoft Corporation.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Acknowledgements
This product includes software developed by the Apache Software Foundation (www.apache.org/).
If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.
© Copyright 2009 Hewlett-Packard Development Company, L.P.