HP SiteScope Release Notes
for the Windows, Solaris, and Linux operating systems
Software version: 11.01
Publication date: September 2010
This file provides information about HP SiteScope 11.01.
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
Installation Prerequisites
- SiteScope 11.01 must be installed on top of SiteScope 11.00. It should be installed on standard SiteScope installations only (not on System Health or other SiteScope type installations).
- You can upgrade SiteScope versions 10.x directly to SiteScope 11.00. 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.
Installation Instructions
Read all information in this section before starting the installation.
- Before installing SiteScope 11.01, it is recommended that you back up your current SiteScope installation directory and all of the subdirectories within the directory.
- Before installing SiteScope 11.01, make sure the SiteScope process/service has been stopped.
- To install SiteScope 11.01 using a silent installation, follow the Silent Deployment Installation instructions below.
- If you already have SiteScope 11.00 installed, install SiteScope 11.01 by double-clicking the setup file and following the on-screen instructions. After installing SiteScope 11.01, restart SiteScope.
- If you do not yet have SiteScope 11.00 installed, install it according to the instructions in the HP SiteScope 11.01 Deployment Guide. After installing SiteScope 11.00, install SiteScope 11.01 by double-clicking the setup file and following the on-screen instructions. After installing SiteScope 11.01, restart SiteScope.
- After upgrading to SiteScope 11.01, you can import monitor configuration data from previous versions of SiteScope directly to SiteScope 11.01 using the Configuration Tool.
Silent Deployment Installation
SiteScope 11.01 Rollback Instructions (Windows)
- To uninstall SiteScope 11.01, 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 11.01, 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 service packs installed on top of it:
SiteScope 11.01 Rollback Instructions (UNIX)
- To uninstall SiteScope 11.01, follow the instructions below.
- To uninstall HP SiteScope 11.00 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 11.01 by running the command: /opt/HP/SiteScope/Uninstall/HPSiS1101/setup.bin -i console
2. Uninstall SiteScope 11.00 by running the command: /opt/HP/SiteScope/Uninstall/HPSiteScope/setup.bin -i consoleWhat's New
Operations Manager Event Integration Enhancements
- Added default severity mappings that control the events severity level of the monitor threshold status in SiteScope when Indicator State and Severity is not used. You can customize the default severity mappings in the Event Integration Settings panel in the HP Operation Manager Integration dialog box. When the Use default severity check box is selected, these mappings are sent in:
Note: The default global severity mappings cannot be sent when SiteScope is connected to BSM.
- Monitor discovery integration. Updated the deployment instructions for this integration in the SiteScopeMonitorDiscoveryPolicy_readme.docx file which is located in the <SiteScope root directory>\sisdocs\pdfs directory.
- Added the option to send "normal" severity messages to the Acknowledged message browser, instead of the Active message browser (to avoid unnecessarily cluttering the Active message browser with such messages). To do so, select True for normal severity in the Log only options of the common event mapping template associated with your events. ( QCCR1I48591)
- Replaced the string "measurement" with "metric" in the message text attribute of the default event mapping template in Preferences > Common Event Mappings.(QCCR1I47025)
- Added ability to customize the service name that is sent from SiteScope events to HPOM by entering the value of the monitor service ID. For details, see Enhancement Request Fixes below.
- Added the <<monitorDrillDownURL>> attribute to the list of available attribute variables that can be used when configuring common event mappings. This attribute enables the URL to the event in SiteScope to be included as a hyperlink in the event text that is forwarded to OM. (QCCR1I48351)
Operations Manager Metrics Integration Enhancements
BSM Integration Enhancements
- Added a status bar below the metrics-to-indicator mapping table in HP Integration Settings which indicates if settings have been changed by the user. (QCCR1I48220)
- Added a setting to enable data to be compressed before being sent from the SiteScope server to BSM/BAC. To enable the setting, set the property _topazCompressDataInGzip= to true in the
\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/BAC(where it is decompressed). Data compression can be used only when SiteScope is reporting to BAC 8.05 or later.EMS Integration Monitor Enhancements
- The options displayed in the Topology template list in Topology Settings now depend on the sample type selected in the Field Mapping panel (only the relevant template options are displayed). When SiteScope is connected to BSM 9.x, the following Field Mapping options are available:
- Metrics. When selected, the following topology script templates are available: "SiteScope topology", "No topology", "Custom". ("No topology" is a new option in which data and configuration samples are sent to BSM, but topology is not sent.)
- Events. When selected, the following topology script templates are available: "Node", "Node - Running Software", "Custom".
- Tickets When selected, the following topology script templates are available: "Tickets", "Custom".
- When SiteScope is connected to BAC 8.x, the following Field Mapping options are available:
- Measurements. When selected, the following topology script templates are available: "SiteScope topology", "No topology", "Custom".
- Events. When selected, the following topology script templates are available: "Hosts", "Hosts - Software element", "Custom".
- Tickets. When selected, the following topology script templates are available: "Tickets", "Custom".
- When SiteScope is connected to BAC versions earlier than 8.0, the Field Mappings are similar to BAC 8.x, except that there is a "Hosts - Applications" script template instead of "Hosts - Software element". (QCCR1I39656)
Monitor Enhancements
System Availability Management Admin
- The SAM Points Used value in the SiteScope Summary table (in Admin > System Availability Management) is now updated once a day. Previously it was updated only when the SiteScope profile was edited. (QCCR1I48047)
- The SAM license includes points used by monitors currently enabled and reporting topology to BSM from SiteScope (previously it included only points used by monitors reporting metrics). (QCCR1I49705)
Upgrade
Enhancement Request Fixes
Bug Fixes
Escalation Fixes
CR ID or SR/E-Sar Number
Description
Area
QCCR1I41517
Fixed issue when publishing template changes to deployed groups, of some monitor counters being shown as "unavailable on server" even though they are available.
Monitors
QCCR1I41214
Fixed issue of SiteScope sending the incorrect parameter for the target server in alerts sent to Operations Manager for UNIX.
Integration - OM Events
QCCR1I49161
Fixed issue when SiteScope is integrated with Operations Manager and not connected to BSM, of not being able to control the event severity level of monitor thresholds. For details, see Operations Manager Event Integration Enhancements.
Integration - OM Events
Notes and Limitations
Description
CR ID or SR/E-Sar Number
Area
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
BSM Integration
If you upgrade to BSM 9.10 (when available), you should manually resynchronize SiteScope instead of waiting for topology data to be sent to BSM based on the Topology resynchronization time interval value.
QCCR1I39744
BSM Integration
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
BSM Integration
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
BSM Integration
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.
BSM Integration
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.
BSM Integration
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.BSM Integration
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
BSM Integration
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
BSM Integration
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
If applet loading fails with a "NoClassDefFound" exception, select the Keep temporary files on my computer option in your client Java configuration (Control Panel > Java > General tab > Temporary Internet Files > Settings).
If security issues require it, delete the temporary files manually when you finished 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
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
The Dashboard column layout in the Monitor History view cannot be saved during user sessions.
QCCR1I20806
Dashboard
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 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.
1) Click Start > Control Panel > Java > Java tab.
2) 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
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
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 uninstalling SiteScope, the HP Operations agent is also uninstalled.
Workaround 1: Before uninstalling SiteScope, delete or rename the\install\components folder.
Workaround 2: If you have already uninstalled SiteScope (and the agent), reinstall the agent.QCCR1I51730
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
When installing the HP Operations agent on a Windows Server 2008 64-bit environment during a SiteScope installation, the agent fails to install.
Workaround: Install SiteScope without the agent and then install the agent manually.QCCR1I52973
Installation / OM Integration
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 1.6.0_14 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
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
Templates and solution templates might be missing from the Templates context after installing SiteScope.
Workaround: 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
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
Date and time format for monitor status is shown according to the server locale instead of the browser locale.
QCCR1I41203
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
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
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
Log File monitor. The Log File monitor is unable to monitor a file through symbolic links on Linux.
QCCR1I39836
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
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
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
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
Non-English characters are displayed correctly in HPOM/Operations Management if they are named with the HP Operations agent machine locale only. HP Operations agent machine locale should be the same as the HPOM management/BSM Gateway server machine.
QCCR1I43630
OM Integration
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.
OM Integration
After installing the HP Operations agent, it is recommended to restart the SiteScope server.
QCCR1I51638
OM Integration
Automatic Node discovery is unable to report remote nodes that are targets for alert events (it only registers nodes that are targets for status change).
QCCR1I47843
OM Integration
When SiteScope 11.01 is integrated with Operations Manager for Windows 9.0 and the SiteScope Monitor discovery policy has been activated, monitors that monitor the SiteScope server are not created in OM service maps.
QCCR1I51316
OM Integration
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.
OM Integration
When SiteScope/HP Operations agent is installed on Windows Server 2008, nodes are not automatically created in Operations Manager for Windows. This is because agtrep cannot run the auto-discovery script on a Windows Server 2008 R2 x64 operating system.
Workaround:
1). Navigate to C:\Program Files\HP\HP BTO Software\lbin\agtrep, right-click agtrep.exe, select Properties > Compatibility tab, and set compatibility for all users to Windows Server 2008 SP1.
2). From the command line, run:
ovc –stop agtrep
ovc -start agtrepOM Integration
HP Operations agent version 8.60.7 installed on a 64-bit console reports itself as 32-bit.
Workaround: If you want to deploy policies, you should manually change the agent bit length and binary format to 64.
1). In Operations Manager, open the Node Configuration editor.
2). In the Nodes list, right-click the agent node and select Properties > System tab.
3). Change Bit Length to "64" and Agent Binary Format to "x64".OM Integration
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
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.00 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 SiteScopeQCCR1I30759
System Availability Management Administration
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
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
SiteScope Installation
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
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):
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, BSM 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 BSM. This configuration replaces the recommended configuration that appears in the SiteScope Deployment Guide.
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 Operations Manager Version
SiteScope 11.x Integration
Events integration
Node discovery Integration
Monitor Discovery Integration
Comments
HP Operations Manager for Windows 8.1x (with patch OMW_00071)
Supported
Supported
Supported
If you are using SiteScope 11.00, patch SIS_00088 is required (it is not required for SiteScope 11.01). The patch is available from the HP Software Support site.
HP Operations Manager for Windows 9.0
Supported
Supported
Supported
If you are using SiteScope 11.00, patch SIS_00088 is required (it is not required for SiteScope 11.01). The patch is available from the HP Software Support site.
HP Operations Manager for Linux/ UNIX/Solaris 9.0
Supported
Not supported
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 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.
AMD and the AMD Arrow symbol are trademarks of Advanced Micro Devices, Inc.
Google™ and Google Maps™ are trademarks of Google Inc.
Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries.
Java™ is a US trademark of Sun Microsystems, Inc.
Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® 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 2010 Hewlett-Packard Development Company, L.P.