HP SiteScope Release Notes
for the Windows, Solaris, and Linux operating systems
Software version: 11.10
Publication date: February 2011 (release notes last updated on 7 August 2011)
This file provides information about HP SiteScope 11.10.
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
- Install SiteScope 11.10 on supported Windows, Solaris, or Linux environments according to the instructions in the HP SiteScope Deployment Guide 11.10. Click here to view the System Requirements.
- If there is an existing SiteScope 11.0x version installed, you must uninstall it before installing SiteScope 11.10.
- You can upgrade SiteScope 10.x or later versions directly to SiteScope 11.10 by exporting SiteScope configuration data using the Configuration Tool. For versions of SiteScope earlier than 10.00, you must first upgrade to SiteScope 10.x. For versions of SiteScope earlier than 9.x, you must first upgrade to SiteScope 9.x.
What's New
What's New Movies
These movies are available on the HP Videos channel on YouTube - http://www.youtube.com/user/HewlettPackardVideos.
Virtualization
New Dynamic VMware Host Monitors
- Added 5 new dynamic VMware Host monitors that enable you to monitor CPU, Memory, Network, State and storage-related counters of the VMware host server and its guest virtual machines.
- These monitors dynamically update themselves over time by adding or removing counters and thresholds as virtual machines are added or removed from the VMware Host.
- Added a solution template for VMware Hosts based on best practices for monitoring VMware Hosts. The solution template uses the 5 new monitors.
- SiteScope supports configurations with up to 550 VMware Host monitors.
- The VMware Host monitors and the solution template require an additional SiteScope license.
VMware Performance Monitor Enhancements
- Various improvements were made to the VMware Performance monitor, with a focus on improving its performance and scalability. To benefit from these improvements, follow the instructions for the monitor in the SiteScope Monitor Reference guide.
- User Interface Improvements. New filtering capabilities for improved performance:
- Get real-time data only. Select to retrieve real-time metrics data only and exclude historical metrics data.
- 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).
- Host. Enter a regular expression to match the name of one or more hosts. Only the hosts that match this expression are displayed in the Counters list.
- 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 Counters list.
- Normalized the values used for reporting percentage metrics (CPU and Memory counters).
- Added option to use the VMware Performance monitor without having to import SSL certificates. See Enhancement Request Fixes for more details.
- Server-Side Improvements.
Performance and Monitoring Capacity Enhancements
- SiteScope new native support for 64-bit environments enables a single 64-bit server to run up to 24,000 monitors and 3,500 monitor runs per minute. Click here to view the list of supported 64-bit environments. Click here to view guidelines for setting the JVM heap size. The SiteScope Capacity Calculator has been updated for 64-bit environments.
- SSH sessions are cleaned from the SSL connection pool if they are idle longer than a predefined amount of time (10 minutes by default). You can change the default value in Preferences > Infrastructure Preferences > General Settings > Time period for cleaning idle SSH connections from pool (minutes).
- Improved performance when monitoring Microsoft Windows Resources using SSH. To benefit from these changes, the RemoteNTSSH.zip file from SiteScope 11.10 must be installed on all monitored remote servers (available from the <SiteScope root>\tools directory).
Enterprise Templates
- Added ability to deploy multiple templates in a single deployment.
- Added ability to export templates for use in other SiteScope installations with their containers.
- Added ability to ignore selected groups under the root group when publishing template changes. This enables:
- Deploying a template inside an existing deployed group, and publishing changes without affecting SiteScope objects that are in the ignored group.
- Deleting objects in deployed groups that were removed from the source template (when the Enable delete on update option is selected), without removing other objects created in the deployed group that were not part of the source template.
- Added auto-complete feature for Template variables. Enter "%%" to display the list of available variables.
- Added ability to use variables in most template fields.
- Added ability to set tags as variables in the template, which enables specifying the tag name and values when deploying the template.
- Added ability to create variables in SiteScope alerts, and specify the schedule for performing alert actions if alert conditions are met and the alert is triggered.
- Added support for more monitor types in template mode (Composite, e-Business Transaction, Formula Composite, and Microsoft Windows Dial-up).
User Management with LDAP Authentication
- New integration with LDAP for SiteScope user authentication and authorization. The integration enables you to define role-based permissions in SiteScope and associate those roles with LDAP user groups. This avoids having to define each SiteScope user manually in SiteScope, making managing user permissions more efficient.
- LDAP user authentication also supports silent login.
Log Analysis Tool
SiteScope iPhone Application
- SiteScope 11.10 supports the SiteScope iPhone application. This is a free app that enables you to keep track of your monitored IT infrastructure while away from your computer using iPhone. iPad, or iPod touch.
- You can perform the following actions:
- Search SiteScopes to view monitor and group statistics, and perform actions on the search results to mitigate issues (enable/disable monitors, run monitors, 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 specified time period.
- 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.
API Enhancements
NNMi Integration
- Added support for sending events and reporting metrics data to Network Node Manager i (NNMi).
- The event integration uses SiteScope SNMP Preferences and alerts for reporting SNMP traps to NNMi. SiteScope sends SNMP traps as a result of alerts triggered by monitor status change. A SiteScope MIB has been created to ease integration with SNMP-based event management systems.
- The metrics integration uses the Generic Data Integration on the SiteScope server to collect monitor data in XML format and pass the collected data to NNMi.
New Solution Templates and Monitors
Support for 64-Bit Environments
- New installers exist for 64-bit environments. Click here to view the list. The Microsoft Exchange 2003 Mailbox, Microsoft Exchange 2003 Public Folder, Microsoft Windows Media Player, Real Media Player, Sybase, Tuxedo, and Web Script monitors do not support working with the 64-bit version of SiteScope. If you intend working with any of these monitors, it is recommended to install the SiteScope 32-bit version.
- Increased monitoring capacity when SiteScope is installed on a 64-bit environment:
- Increased virtual memory address space to 8 TB for 64-bit processes, instead of 4 GB of memory for 32-bit processes.
Note: The SiteScope 64-bit version consumes up to 3 times more memory than the SiteScope 32-bit version. Accordingly, if you are using a SiteScope 64-bit version you should increase the JVM heap size and desktop heap size on the server. On Windows Platforms, you can do this by running the Configuration Tool and selecting the Sizing option. On Solaris and Linux platforms, you must configure this manually by performing the following:
1. Open the SiteScope/bin/start-service file for editing.
2. In the last line, increase parameter -Xmx512m to -Xmx2048m (for 2 GB) or to a higher value, up to a maximum of -Xmx8192m (for 8 GB).Monitor Enhancements/Changes
- Memory monitor. Added new counters for measuring physical memory (physical memory used % and physical memory MB free). Renamed the existing counters for measuring virtual memory (physical and swap memory) from percent used to virtual memory used % and from MB free to virtual memory MB free.
- Service monitor. Added the Service start mode counter to the monitor which indicates when a monitor is not running (for example, if the service was disabled on the target server, or if it has stopped). Note that this counter is available when using WMI remote servers only.
- Microsoft Windows Event Log monitor. The Log name and Event type fields are automatically generated with the relevant values for the selected target server. (Previously they had a predefined static values list.)
- Database monitors. Inet database drivers are no longer supported in SiteScope. If you are using these drivers in database monitors, you should change to an appropriate driver.
Alerts Enhancements
BSM Integration
- The following monitors were enriched with additional counters and are now mapped to HIs and are reported to BSM, Diagnostics, and Data Integrations: e-Business, File, Log File, News, Radius, Siebel Log, SNMP, URL, URL Content, and URL Sequence monitor.
- Added a setting to enable data to be compressed before being sent from the SiteScope server to BSM. 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 BSM (where it is uncompressed). Data compression can be used only when SiteScope is reporting to BAC 8.05 or later.
- The Enable reporting changes in status option was removed from monitor Properties > HP Integration Settings > BSM Logging Options due to the introduction of event management in BSM 9.00. This option can be enabled for backwards compatibility by changing the property _allowToSendOnlyMonitorStatusToBSM9 to =true in the master.config file.( QCCR1I50595)
Operations Manager Integration
- Automatic Node discovery now reports remote nodes which are targets for alert events (previously, it only registered nodes that were targets for status change). For each alert, SiteScope collects and reports the node targets of all its monitors. This can be enabled by selecting Enable node discovery policy in Preferences > Integration Preferences > HP Operations Manager Integration Main Settings (QCCR1I47843)
- Added the Connect directly to BSM option in OM Integration settings. This option impacts node discovery and service health preference. (QCCR1I47850, QCCR1I51412, QCCR1I46468)
- HP OM Event Monitor. Support to install the HP OM Integration Add-on module from the SiteScope file system on a Windows Server 2008 R2 (64-bit) machine. The HP OM Integration Add-on is used to connect to the HP OM message infrastructure, to receive events from the HP OM, and to forward these events to the SiteScope machine. (QCCR1I51692)
Enhancement Request Fixes
Description
CR ID or SR/E-Sar Number
Area
Added the Tags match table to the Filter Settings pane in the New/Edit Alert dialog box. This enables filtering alerts to include only those monitors associated with an alert that has the tag values selected.
QCCR1I38712
Alerts
Added ability to customize the service name that is sent from SiteScope events to HPOM by entering the value of the monitor service ID. To do so, select, Preferences > Common Event Mappings > Custom Attributes tab, and enter a value for Service id.
QCCR1I44830 / 4614344059
Integration - OM (Events)
SiteScope automatically updates the <SiteScope root>\template.mib folder when the MIB structure is updated, instead of requiring a SiteScope restart. The folder is updated at a frequency of not more than once every 60 seconds.
QCCR1I50440/ QCIM1I50439 4001197979
Monitors
Added the Disable monitor option to the group and monitor shortcut menu in the left navigation frame.
QCCR1I43421
Monitors
FTP monitor. This monitor supports Secure FTP (SFTP). You select the mode for the monitor (FTP or SFTP) from the Protocol list in FTP Monitor Settings.
QCCR1I34873 / 4603203924
QCCR1I44999 / 4614508398
Monitors
JMX monitor. Added a timeout field to the monitor, which enables setting a time to wait for a response from the server before timing-out.
QCCR1I33024
Monitors
Microsoft Windows Event Log monitor. Added Audit Failure and Audit Success to the list of available event types to match.
QCCR1I32020/ 2607689007
Monitors
Script monitor. Fixed issue of being unable to run a script on a Script monitor using the start and psexec commands (even though the script was able to run from a command line).
QCCR1I50808/ QCIM1I49945 4618062601
Monitors
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 that this counter is available when using WMI remote servers only.
QCCR1I50373/
Monitors
SNMP monitor. Added the Privacy password check box to the monitor which enables DES privacy encryption when using a version3 connection.
QCCR1I39912/ QCCR1I50407/ 4611331759
Monitors
Technology Log File Integration monitor. Added regular expression tool support to the Technology Log File Integration monitor Content match field.
QCCR1I36029
Monitors
URL Sequence monitor. Added hyperlinks to each URL result in the URL Sequence Steps Results (to avoid having to scroll steps). This is also available when running the URL Tool on a multi-step monitor.
QCCR1I49610/ 4614701983
Monitors
URL Sequence monitor. Fixed issue of no logical break separating the steps into separate html pages, by adding hyperlinks to each individual step in a multiple step URL sequence monitor into the monitor's check result page.
QCCR1I49610
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 to =true in the master.config, 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 for details.
QCCR1I48863/ 4614698677
Monitors
Removed the Best case calculation check box from Management reports and Quick reports.
QCCR1I 48876
Reports
Added the time and date that an acknowledgement is made to the Acknowledge Log.
QCCR1I14344
SiteScope Dashboard
Added the Tools option to the context menu in the monitor tree. This option is available when configuring or editing specific monitors only.
QCCR1I43425
SiteScope Tools
Added functionality to update templates with deployed instances (previously you had to remove the link between the template and deployed monitors, delete the template, and then import it again).
QCCR1I38949/ 4610685424
Templates
Added the ability to see when a template was last updated and by whom (the SiteScope user name is displayed).
QCCR1I44594
Templates
Fixed issue with the URL Tool not displaying the HTTP Response and Page Content when the status is Good.
QCCR1I48045/ 4615800170
Tools
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.
QCCR1I50410 / 4610877695
User Preferences
Bug Fixes
Escalation Fixes
Notes and Limitations
Description
CR ID or SR/E-Sar Number
Area
When generating an Alert report from a sub-group, the report does not include alerts for the parent group (indirectly associated alerts). Only alerts for the specific sub-group are displayed.
Workaround: Run the Alert report from the parent group.QCCR1I50620
Alerts
When working under high load conditions, you should suspend all monitors before connecting to BSM for the first time.
Capacity Limitations
When SiteScope is integrated with BSM, 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 BSM integration properties for over 2,500 monitors at once.
QCCR1I30633
Capacity Limitations
SiteScope applet must have the Keep temporary files on my computer selected in your client Java configuration (Control Panel > Java > General tab > Temporary Internet Files > Settings). Failing to do so will result in: "NoClassDefFound" exception and applet loading will fail.
If security issues require it, delete the temporary files manually when you finish using the SiteScope applet:
1). Close the SiteScope applet.
2). Select Start > Control Panel > Java > General tab.
3). In the Temporary Internet Files section, click Settings and then click Delete Files.QCCR1I37003
Configuration
If SiteScope is installed on Microsoft Windows Server 2008, you should manually define the time zone offset 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
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 Include additional data option, all other Diagnostics and Generic Data integrations are affected (the data SiteScope forwards to these applications also contains this additional data). 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 "Diagnostics Integration Preferences Dialog Box" in the "Integration Preferences User Interface" section of the Using SiteScope help.
Diagnostics Integration
When viewing the online help in an Internet Explorer 8.x browser (32 or 64-bit version), the step numbering might not be incremented.
Workaround:
1). Open the html file in a text editor.
2). Search for <div><li>
3). Delete the div tag: <div>.
4). At the end of the same line, delete the </div> (from </li></div>).For example, change:
<div><li>Text for step 1</li></div>
to
<li>Text for step 1</li>
(The <div> tags around the <ol>...</ol> tags should remain)5). Save the html file.
Documentation
When using Global Search and Replace, unable to replace Credentials values that are used in remote servers and monitors.
QCCR1I42998
Global Search and Replace
Indicator Settings are not supported, and are not available, in Global Search and Replace.
QCCR1I45045
Global Search and Replace
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 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
Unable to display non-English characters in the counters list when configuring the Microsoft IIS Server monitor.
QCCR1I21171
I18N
Non-English strings are not supported when using the post installation Configuration Tool wizard on a Linux environment.
Workaround: Run the post installation Configuration Tool in console mode with parameter "-i console".
QCCR1I50695
I18N
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
Run results for some monitors are shown according to the server locale or in English, instead of according to the client locale.
QCCR1I30190
I18N
When using the Microsoft Windows Resources monitor in a non-English locale, the monitor counters and run status summary is not readable.
Workaround: Configure the monitor to use the Direct registry queries collection method.QCCR1I54985/ QCCR1I54978
I18N
When using the Log File monitor with Server-side processing via SSH v2, the monitor fails when its content match is a non-English string (the monitor ignores the UNIX remote server's encoding).
Workaround In Log File Monitor Settings, clear the Server-side processing check box.QCCR1I40747
I18N
SiteScope log files do not support Unicode characters-all non-English characters appear corrupted in the logs.
Workaround: Use a SiteScope server installed on a corresponding operating system locale. For example, use SiteScope installed on a Japanese Windows operating system for a Japanese locale.QCCR1I35306
I18N
When installing SiteScope with the HP Operations agent on a UNIX environment that previously had the agent installed (even if it was uninstalled), the newly-installed agent is unable to connect to OM or Operations Management (in BSM).
Workaround: Before installing SiteScope with the HP Operations agent on a UNIX environment, delete the following folders: opt/OV and var/opt/OV.QCCR1I47566
Installation - OM Integration
When installing the HP Operations agent during a SiteScope installation on UNIX, the installation might hang if the agent is already installed.
Workaround: Before installing SiteScope, stop the HP Operations agent using the command: #ovc -killQCCR1I51731
Installation - OM Integration
If there is a problem signing and installing the local policies when configuring Operations Manager event integration, the installation hangs.
Workaround: Restart your HP Operations agent, or your SiteScope server.QCCR1I51861
Installation - OM Integration
When SiteScope 11.1x is installed on a UNC path (a UNC path is a requirement for SiteScope Failover, Windows only), the patch install/uninstall prompts you to provide the UNC installation path log-on credentials. The patch (MSI) install executes its post-install/pre-remove logic scripts as user "NT AUTHORITY/SYSTEM". This user does not have a mapping to any UNC drive, and failure to provide the correct log-on credentials causes the patch install to fail. The patch uses these credentials to create a mapping to the UNC installation path for user "NT AUTHORITY/SYSTEM" during the patch installation, and removes the mapping at the end of the installation
Installation and Upgrade
SiteScope might fail to install on a Windows machine if the environment variables %TEMP% and %TMP% point to a directory path that contains an empty space. For example, C:\Documents and Settings\Default User\Local Settings\Temp.
Workaround: Change the environment variables %TEMP% and %TMP% to point to a directory path that does not contain an empty space. For example, C:\Temp.QCCR1I52241
Installation and Upgrade
When installing SiteScope 11.10 from AutoRun, the SiteScope 32-bit version is installed even if you selected the 64-bit installation.
Workaround: Close AutoRun, and install SiteScope from the installation DVD by running Windows_Setup\64Bit\HPSiteScope_11.10_setup.exe.QCCR1I
Installation and Upgrade
The SiteScope installer might not work on Linux 64-bit environments using the graphical user interface wizard.
Workaround: Install SiteScope using the console mode instead.QCCR1I43277
Installation and Upgrade
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: Install JRE 1.6.0_14 or later and configure you browser to use this version of JRE.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
After upgrading from SiteScope 7.5.x 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 > User Management 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.
Workaround: Perform the following:
1). Click Start > Control Panel > Java.
2). In the Java Control Panel, click the Advanced tab.
3). 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.
4) Click Apply and then click OK.Installation and Upgrade
The ability to report topology data to BSM 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 the first restart if it takes longer than 15 minutes because SiteScope automatically restarts if there are no monitors running within this time.
Workaround:
1). After an upgrade, use the following batch file to start SiteScope for the first time: <SiteScope root directory>/bin/go.bat.
2). Once SiteScope is started, for any monitors that are monitoring environments that are not running, select Disable reporting metrics to BSM under BSM Integration Data and Topology Settings in HP Integration Settings. This saves wasting 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
Installation on Turkish Locale Causes an Exception: If you attempt to run the SiteScope Installation procedure using a Turkish locale, the installer does not present the installation screens correctly and, as a result, you cannot answer the installation questions. This is a problem related to the installation software.
Workaround: In order to complete the installation successfully, you need to temporarily set the locale to a United States locale. When you have completed the installation, you can reset the locale to Turkish.QCCR1I55818
Installation and Upgrade
Template Examples or Solution Templates might be missing from the Templates context after installing or upgrading SiteScope.
Workaround:
1). Before installing or upgrading SiteScope, rename existing template examples in SiteScope to avoid name collision during silent import (see next step). Duplicate names will inhibit the import process from completing successfully.
2). If you have performed an upgrade (and the template examples are missing), 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
If uninstalling SiteScope fails, restart the SiteScope server, and then try to uninstall again.
QCCR1I57144
Installation and Upgrade
When upgrading to SiteScope 11.10, the templates.os files are overwritten by the upgraded files, including any files you customized in a previous version of SiteScope. If in a previous version you added new configuration files to the templates.os folder, these files are not affected by the upgrade and remain in the folder.
Workaround: To restore any customizations that you made to the templates.os files:
1). Make a backup of the original SiteScope 11.10 configuration files, since some configuration files from earlier versions of SiteScope are incompatible with 11.10, and might not work after you make changes to them.
2). Unzip the backup files that were made prior to the upgrade by exporting SiteScope configuration data using the Configuration Tool.
3). Manually make changes to the new files.Installation and Upgrade
Historical data is lost in SAM reports after host DNS resolution if the host is resolved with another name (Topaz ID).
Workaround: Manually update the BSM database by searching for the old Topaz ID and replacing it with the new ID for historical data.QCCR1I35093
Integration - BSM
The Running Software CI which is reported by both SiteScope and Real User Monitor is not reconciled, since SiteScope does not report the IpServiceEndpoint CI that should be linked to the Running Software CI.
QCCR1I39607
Integration - BSM
When SiteScope versions earlier than 10.00 are connected to BSM 9.00, EMS integrations reporting the Application CI (HP OVO, NetScout, and generic integrations) fail since the application_id attribute was removed from the Application CI in BSM 9.00.
QCCR1I28808
Integration - BSM
Sending topology fails for some monitors deployed from solution templates (since not all monitors have the report topology to BSM option selected by default).
Workaround: After deploying a monitor using a solution template:
1). Expand HP Integration Settings in the monitor properties.
2). Select Enable reporting monitor status and metrics (in the BSM Integration and Data and Topology Reporting section) to enable the monitor to report to BSM.QCCR1I48052
Integration - BSM
To improve performance, SiteScope uses a topology cache when sending topology data to the BSM's RTSM (Run-time Service Model). If SiteScope attempts to send an existing CI to the ODB, the CI may not be sent or be created in the ODB for up to a week because of the way the topology cache works.
This could happen in the following circumstances:
- When cutting and pasting a monitor from one group into a new group (so the original group is left empty), and then cutting and pasting the monitor from the new group back into the original group.
- When disabling data and topology reporting for a monitor and then enabling it again in HP Integration Settings.
- After a CI has been manually deleted from the ODB, it is not created again until the cache is cleaned out. (EMS flow - Deleting EMS monitors from the ODB)
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 BSM Preferences Available Operations area, click Re-synchronize.
Integration - BSM
Deploying SiteScope templates while registering a SiteScope to BSM may cause a loss of topology data reported to BSM. It is recommended to avoid making configuration changes while performing BSM registration.
Integration - BSM
If SiteScope restarts for any reason while SiteScope is connected to BSM, some topology data that SiteScope forwards to BSM may be lost.
Workaround: If not all topology data was forwarded to BSM, manually synchronize the data as follows:
1). In Preferences > Integration Preferences.
2). Edit the relevant integration.
3). In the BSM Preferences Available Operations area, click Re-synchronize.Integration - BSM
When accessing SiteScope from System Availability Management Administration using Internet Explorer 7, a 408 Request Timeout error is displayed.
Workaround: To be able to login into SiteScope from BAC/BSM, you must enable the option in Internet Explorer to allow session cookies.
1) In Internet Explorer, select Tools > Internet Options > Privacy tab > Advanced button.
2) Select Override automatic cookie handling, make sure First-party cookies and Third-party cookies are set to Accept, and select Always allow session cookies.QCCR1I49144
Integration - BSM
When adding threshold conditions to a monitor that has multiple CIs (SAP CCMS, SAP Work Processes, Siebel Application Server, Siebel Web Server, Solaris Zones, or VMware Performance monitor), the Indicator State and Severity value disappears for all threshold conditions, except for the last condition added.
Workaround: Add and configure threshold by threshold, instead of by adding and configuring each threshold individually. When you save the monitor, indicator values for all threshold conditions are displayed.QCCR1I49550
Integration - BSM
Monitors do not report to BSM if you:
1). Create a monitor with custom topology, and click Save.
2). Clear the Report monitor and related CI topology check box (in HP Integration Settings), and click Save.
3). Select the Report monitor and related CI topology check box, and click Save.
Workaround: Make any change in the monitor properties (for example, change a letter in the monitor name and then change it back), and then click Save.QCCR1I56509
Integration - BSM
If you run the node discovery policy when SiteScope is integrated with Operations Manager for Windows 9.0 (OM) and the nodes that SiteScope reports exist in OM, the node definitions are removed from OM and replaced with an empty node object.
Workaround: Install the relevant OM patch (check the Patches page on the HP Software Support site. After the patch is installed, the HPOM server ignores platform updates from SiteScope.QCCR1I54342
Integration - OM
After installing the HP Operations agent, it is recommended to restart the SiteScope server.
QCCR1I51638
Integration - OM
When SiteScope is installed on the same machine as Operations Manager for Windows 9.x (OMW), the discovery policy integrations (node and monitor service discovery) do not work and a JVM error file is generated. Note that running the integration batch files from a command line returns the discovery XML results to the console, while running it from the agent agtrep command fails.
Workaround: Manually configure the integration scripts to work with Java 32 according to the SiteScope installation.For SiteScope 32-bit:
1). Install SiteScope 32-bit on a machine with OMW 9.0 64-bit.
2). Edit <SiteScope root>\integrations\om\bin\om_discovery_hosts.bat by replacing run_api_call_om.bat with run_api_call.bat.
3). Edit <SiteScope root>\integrations\om\bin\om_discovery_monitors.bat by replacing run_api_call_om.bat with run_api_call.bat.For SiteScope 64-bit:
1). Install SiteScope 64-bit on a machine with OMW 9.0 64-bit.
2). Download Java 32-bit.
3). In the <SiteScope root>\integrations\om\bin folder, make a copy of the run_api_call.bat file, and name it run_api_call_32.bat.
4). Open run_api_call_32.bat in a text editor, and set the java location to the 32-bit location from where you downloaded it.
5). Edit <SiteScope root>\integrations\om\bin\om_discovery_hosts.bat by replacing run_api_call_om.bat with run_api_call_32.bat.
6). Edit <SiteScope root>\integrations\om\bin\om_discovery_monitors.bat by replacing run_api_call_om.bat with run_api_call_32.bat.QCCR1I58340
Integration - OM
When SiteScope is integrated with Operations Manager, the HP Operations agent included with SiteScope requires an OS Instance Advanced license. Nodes registered in Operations Manager through the node discovery policy might also (falsely) request a Target Connector license. For details on Operations Manager licensing requirements, refer to the Operations Manager documentation.
Integration - OM
Operations Manager 9.0 for Windows 64-bit console does not support the tree services view (when OM is integrated with SiteScope). The tree view is available in the left pane, but not in the service map on the right.
Integration - OM
If BSM is using an HTTPS reverse proxy or a load balancer, you need to provide the HP Operations Agent on the SiteScope server with a certificate so that it can communicate securely with BSM. Check for an updated version of these release notes for details on how to manually configure the agent.
QCCR1I59226
Integration - OM
When you have an HP Operations agent on a SiteScope machine that is managed from Operations Manager, you cannot connect SiteScope to BSM with Event Integration.
Integration - OM
When changing the custom topology from reporting Unix to Windows CI type (for reporting the same IP), the old CI and link are not deleted from the monitor's topology.
QCCR1I42212
Integration Monitors
Publishing changes after changing custom topology in an EMS monitor template does not affect a monitor's custom topology in BSM.
QCCR1I48048
Integration Monitors
When logging to SiteScope using LDAP authentication, unable to generate a Management Report due to authentication issues.
Workaround: Define the user password in SiteScope to be the same as the one used in LDAP.QCCR1I31883
LDAP Authentication
When SiteScope 11.01 is integrated with LoadRunner 9.52, unable to create the Microsoft Windows Resources monitor from the LoadRunner side with the default list of the counters.
Workaround: Add the counters manually.QCCR1I49652
LoadRunner Integration
The Monitor Deployment Wizard only supports topology reporting for monitors that have a default topology defined. This means you can select to add a template to a CI only if the CI type is the default CI type for all the monitors in the template.
QCCR1I39697
Monitor Deployment Wizard
SiteScope is unable to retrieve instances and counters from a Microsoft SQL Server 2008.
Workaround: You can monitor Microsoft SQL Server 2008 using the Microsoft Windows Resources monitor.QCCR1I53756
Monitors
Date and time format for monitor status is shown according to the server locale instead of the browser locale.
QCCR1I41203
Monitors
The following Virtualization monitors do not support VM instance-based information on HPOM integration events and metrics: VMware Performance, VMware Host CPU/Memory/Network/State/Storage, Solaris Zones, and Microsoft Hyper-V monitors.
All HPOM events or Performance Manager metrics generated by these monitors are associated with the monitored target (such as ESX or vCenter), instead of with the actual VM embedded within the relevant metric.
Note: When integrating with BSM, events and metrics are correlated with the correct VM CI, based on CI resolution.QCCR1I54666
Monitors
Database Query monitor. The Database Query monitor status is shown according to the server locale. If there are any specific messages from the database, such as error messages, this information might not be displayed properly in the status field where the server locale is different from the client locale, and the information contains non-Latin characters.
QCCR1I41201
Monitors
Disk Space monitor. Due to a limitation with WMI, the WMI connection method returns incorrect results when this monitor is used on Windows Server 2008.
Workaround: To monitor Windows Server 2008 using WMI, you should install the Microsoft hot fix (http://support.microsoft.com/kb/961435/en-us) on the target Windows system.QCCR1I34224
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
DNS monitor. The DNS Monitor does not work on a Microsoft Windows 2008 Japanese environment.
Workaround: In Preferences > Infrastructure Preferences > Monitor Settings, select the Use DNS Java library option.QCCR1I52457/ QCIM1I52316
Monitors
FTP monitor. Summary status for the FTP monitor is shown according to the server locale instead of the browser locale.
QCCR1I41200
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
HP iLO monitor. SiteScope does not support HP iLO version 3.
QCCR1I52088
Monitors
Log File monitor. The Log File monitor is unable to monitor a file through symbolic links on Linux.
QCCR1I39836
Monitors
Memory monitor. WMI returns incorrect values for the memory used % and MB free counters when the WMI connection method is used on a Windows Server 2008. This is due to an issue with WMI (not SiteScope).
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 to get counters from the remote server when monitoring on Windows Server 2008 (64-bit).
QCCR1I34286
Monitors
Microsoft Windows Resources monitor. Unable to receive measurements when monitoring a remote server that contains non-English characters from an English machine using NetBIOS or agent-based SSH.
Workaround: Use the same operating system language on both systems.QCCR1I33005
Monitors
Monitor Thresholds. If, in the counters tree in the Monitor Settings panel, you clear or add a counter that has corresponding thresholds defined in the Threshold Settings panel, the counter might be:
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
Oracle Database monitor. If you have created Oracle Database monitors in SiteScope and afterwards you connected to BSM and you want the monitor and its related topology to be reported to BSM, you must enter values for the database machine in the Name and Server fields and select the Report monitor and related CI topology check box in HP Integration Settings > BSM Integration Data and Topology Settings.
QCCR1I27152
Monitors
Ping monitor. When SiteScope is installed on Solaris, the Ping monitor might take longer than expected to run, and might 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.
Workaround: Change the connection method to SSH on the defined Linux remote server.QCCR1I30899
Monitors
Service monitor. Due to a Solaris limitation, SiteScope is only able to display service names up to a maximum length of 80 characters.
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 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
VMware Host State monitor. The incorrect ESX version is returned by the vCenter and displayed by the VMware Host State monitor. When the VMware Host State monitor monitors ESX directly (not via vCenter), the ESX version is correct.
QCCR1I55409
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
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
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
Unable to send a Server-Centric report by email using the Export option.
Workaround: Save the report as an html file, and then send it manually.QCCR1I57160
Reports
All SiteScope Web Service API methods that are not protected by a user name and password have been deprecated. All API methods with user and password authentication have been renamed and now have an Ex suffix (for example, enableGroupEx) to avoid the same method names being used with different parameters.
QCCR1I4859
SiteScope APIs
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 result in SiteScope restarting.
SSH
F-Secure is no longer officially supported when monitoring remote servers using SSH.
SSH
When upgrading to SiteScope 11.10 in which SSH connections are used for monitoring Windows remote servers, you must replace the RemoteNTSSH package with the latest version from <SiteScope root directory>\tools\RemoteNTSSH.zip on all SSH monitored servers.
SSH
After JBoss Application Server recovers from a server crash, the information in the right pane of the Summary tab in SAM Administration does not show any data.
Workaround: Restart BSM.QCCR1I44570
System Availability Management Administration
Copying and pasting from SiteScope 11.10 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 Service Health in HP Business Service Management.
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
The incorrect CI type is reported when SiteScope 10.x is connected to BAC 8.x or BSM 9.x (the SiteScope server is reported as Host/Node). All measurements related to the SiteScope server only have a Legacy System indicator when the mapping between the indicator and CI type is on a Computer CI type. This impacts Service Health after an upgrade.
QCCR1I54818
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 tooltip on the Remote Servers page in the template.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
The Event Log Tool is not available when configuring the Microsoft Windows Event Log monitor from the Use Tools button. The tool is still available from Tools > Operating System Tools > Event Log Tool.
QCCR1I56272
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 system requirements and recommendations for running SiteScope, based on the various supported operating systems.
System Requirements for Windows
System Requirements for Solaris
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.
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 that these are recommendations based on a tested environment, and are not support limitations):
Support for 64-Bit Environments
The following 64-bit environments are supported in SiteScope:
Certified Configuration
The following configuration has been certified in a high load environment for an installation of SiteScope that was integrated with BSM.
Client System Requirements
SiteScope client is supported by the following:
HP SiteScope Support Matrices
HP Business Service Management Integration Support Matrix
√ = Supported
HP Operations Manager Integration Support Matrix
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 2011 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 Open Source and Third-Party Software License Agreements document in the HP Product Manuals Web Site (http://h20230.www2.hp.com/selfsolve/manuals).
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.
iPod is a trademark of Apple Computer, Inc.
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/).
This product includes software developed by the JDOM Project (http://www.jdom.org/).
If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.
© Copyright 2011 Hewlett-Packard Development Company, L.P.