HP Operations Smart Plug-in for BlackBerry® Enterprise Server Release Notes
for the HP Operations Manager for Windows®
Software version: 3.10
Publication date: December 2009
This document provides an overview of the changes made to HP Operations Smart Plug-in for BlackBerry® Enterprise Server 3.10. It contains important information not included in the manuals or in online help. You can find information about the following in this document:
In This Version
Documentation Updates
Installation Notes
Known Problems, Limitations, and Workarounds
Verified Environments
Local Language Support
Support
Legal Notices
- This version is the first release of the HP Operations Smart Plug-in for BlackBerry® Enterprise Server (further BlackBerry SPI) 3.10
- This version includes monitoring of the BlackBerry Enterprise Server (BES)
- log files
- services and processes
- health and performance by using a metric data collection engine
- health and performance by using SNMP traps
- health by doing advanced log BES log file analysis
- This version includes a service discovery of the BlackBerry domain
- This version includes a Content Pack for HP Operations Manager i
- This version includes tools for managing the BES and devices
The first page of this release notes document contains the following identifying information:
- Version number, which indicates the software version.
- Publish date, which changes each time the document is updated.
To check for recent updates or to verify that you are using the most recent edition, visit the following URL:
http://support.openview.hp.com/selfsolve/manuals
This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to:
https://ovrd.external.hp.com/rd/register
Or click the New users - please register link on the HP Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.
NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system.To download Adobe Acrobat Reader, go to the following web site:
http://www.adobe.com
Installation requirements, as well as instructions for installing BlackBerry SPI, are documented in the Installation Guide for HP Operations Smart Plug-in for BlackBerry® Enterprise Server provided in Adobe Acrobat (.pdf) format. The document file is included on the product's CD or DVD media as:
BlackBerrySPI_InstallGuide.pdf
To display details about each documentation error, click the error summary. To hide details, click again.
ID 3400: OvEpStatusEngine.exe crashes on the start of the console on unpatched OM Server
| Description: |
After installing BlackBerry SPI on an unpatched OM Server, the OvEpStatusEngine.exe crashes on the start of the OM console. |
| Possible Reason: |
OvEpStatusEngine.exe has bugs concerning the service upload. |
| Workaround: |
Delete the stub service with: OVSPIModelCleaner /DSID BlackBerry. Then restart the process OvEpStatusEngine. |
| Solution Proposal: |
Please install the OMW patch OMW_00016 (2008-12-11) or better, OMW_00020 (2009-02-17). In the patch description, there are at least 3 bugs related to OvEpStatusEngine not starting or aborting which were fixed beginning with OMW_00016. |
BlackBerry SPI Version 3.10 does not support direct upgrade from previous versions. Please follow the steps outlined in the
Installation Guide for de-installation. After that follow the installation guidelines in the same document.
To display details about each documentation error, click the error summary. To hide details, click again.
ID 3461: BlackBerry SPI Add-on Policies are not suppported in HA environments
| Description: |
Log entries like the following are reported by the SPI Add-on policies:
|
| Possible Reason: |
The Metric Collector is not aware of the status of standby nodes. |
| Workaround: |
Do not deploy the Add-on policies to any standyby node or disable them on the node as soon as it becomes a standby.
|
ID 3538: User/Device metrics cause long running collector when opcmon integration is used
| Description: |
On systems with a large number of users (>500) user and device based metrics can cause a long running collector process
as per user / device metric and per user a threshold comparison is done (using opcmon) .
Per default alarming for user and device metrics has been disabled.
|
| Possible Reason: |
Spawning 500 or more opcmon() calls can affect system performance as opcmon() calls are in general resource intensive. |
| Workaround: |
On the managed node edit the %ovdatadir%/conf/bespi/bespi_metrics.cfg file
Search for the metric number you like to enable forwarding to opcmon
Remove the line containing the "NO_OVO" keyword
Ensure you created an MT Policy using and "External" data source.
For Metric 105, 107, 200, 201 examples have been provided.
|
ID 3417: HP Performance Agent (PA) Software support for multi-instance logging
| Description: |
When using the HP Performance Agent on the managed node (BlackBerry Server) data is logged into the data sources
but cannot be retrieved by the HP Performance Manager or Reporter.
|
| Possible Reason: |
The HP Performance Manager and Reporter cannot retreive multi-instance data from the HP PA.
It is a known limitation of the HP PA.
|
| Workaround: |
As a workaround performance data logging has to be done in the HP Embedded Performance Component
(EPC also known as CODA).
This requires some simple steps documented in the Administration Guide for HP Operations
Smart Plug-in for BlackBerry® Enterprise Server See chapter: "Override the Default Data Store".
The document file is included on the product's CD or DVD media as:
BlackBerrySPI_AdminGuide.pdf
|
ID 3620: BESPI_BESCoreServices does not work for some core services
| Description: |
Description:
The BESPI_BESCoreServices does not alert if one of the following services is stopped:
BlackBerry Synchronization Service
BlackBerry Policy Service
BlackBerry MDS Connection Service
BlackBerry Mail Store Service
for all the other Services the policy works.
|
| Possible Reason: |
The problem lies within the HP WMI Policies and hence is a defect in a HP component the SPI depends on.
|
| Workaround: |
None. Please use the according status metrics for alert information which the SPI provides.
|
ID 3411: Add-On Policies bases on Messaging Agent log do not show up in the service tree.
| Description: |
Due to BES internal of different service ID in the logs, SNMP and Windows Services, Add-On policies based on
the Messaging Agent log have a different service
ID than the service tree expects. Hence the message do not show up in the service tree.
|
| Workaround: |
Manually adapt the policies and change the service ID to a valid one that is feed in at a higher level at the service tree.
|
ID 3425: BES HA environment: Irritating messages from collector
| Description: |
If the BES SPI is used in a BES HA environment some of the service do not run on the standby node. This causes a warnings of the following type:
BESPI-130: bespi_snmpcoll.plc (11-06): Error encountered while fetching SNMP metrics [Policy: BESPI_SPILog]
additional to this message you will receive a warning for each metric which could not be collected.
|
| Possible Reason: |
The SNMP collector can only collect from active components.
|
| Workaround: |
It is suggested to exclude metrics from the collection for which the data is not available due to the inactivity of the BES component.
This can be best archived by using an automatic action assigned to metric 216 (Dispatcher HA metric) which will indicate a
failover to standby or primary. In case the BES HA node goes into standby the schedule policies collected data for the
components which is unavailable should be disabled. Once it gets back to primary, the policies can be turned on again.
|
ID 3642: Multiple simultaneous SNMP collector cause performance impact
| Description: |
On larger systems it can be observed that multiple Perl processes run at the same time. It might also lead to warning messages of the following type:
BESPI-130: bespi_snmpcoll.plc (11-06): Error encountered while fetching SNMP metrics [Policy: BESPI_SPILog]
Eventually system resources are affected on the BES.
|
| Possible Reason: |
Out of the box the BlackBerry SPI provides one or more schedule policy for each component.
This is a universal approach as not all BES might host all BES components. It is left to the user to customize the
scheduling.
|
| Workaround: |
Create a customer set of schedule templates. For this we suggest to create a list of metrics which are required and define the collection
interval for them.
Then create a maximum of three schedule polices which do not start collection simultaneously.
Please contact support if there are further questions.
|
ID 3618: BlackBerry SPI Status Metric Message Object mismatch
| Description: |
In case a BlackBerry SPI component is unavailable a different system name format might be reported in the data sources
and the alerting. This will result incorrect reports and some message which will not be auto acknowledged.
This is issue can be identified also by messages which contain the "localhost" as message object in the messages.
|
| Possible Reason: |
The BES setup is using a different host name (localhost, FQDB, simple hostname format)
|
| Workaround: |
The easy work around: Please set the correct hostname by using the "Configuration File Update" tool in the BESPI Administration
tool group. Please use the following parameters:
Parameter: BESPI_SNMP_HOST
Value: the hostname returned by the MIB. This is the hostname format your BES was setup with.
|
HP OM management server
Windows 2003, 2008 with HP Operations Manager for Windows 8.10
HPUX 11.23, 11.31 with HP Operations Manager for UNIX 8.3x
Solaris 9, Solaris 10 with HP Operations Manager for UNIX 8.3x
HPUX 11.31 with HP Operations Manager for UNIX 9.0
HP OMi system/server
Windows 2003, 2008 with HP Operations Manager i for Windows 8.10
BlackBerry Enterprise Server
Windows 2003, 2008 (32 and 64 bit) with BlackBerry Enterprise Server 5.0 using Microsoft Exchange 2003, 2007.
Windows 2003 (32 and 64 bit) with BlackBerry Enterprise Server 5.0 using IBM Lotus Domino 8.1x
This version of the BlackBerry SPI is not localized in any languages. English is set as standard language for all installations.
You can visit the HP Software support web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software online 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 using the support site to:
- Search for knowledge documents of interest
- Submit and track support cases and enhancement requests
- Download software patches
- Manage support contracts
- Look up HP support contacts
- Review information about available services
- Enter into discussions with other software customers
- Research and register for software training
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 the following URL:
http://support.openview.hp.com/new_access_levels.jsp
To register for an HP Passport ID, go to the following URL:
https://ovrd.external.hp.com/rd/register
©Copyright 2009 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 and/or open source license agreements, see directory "spi-thirdparty-license-agreements" on the product installation media.
Microsoft®, Exchange Server® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
BlackBerry Enterprise Server is a trademark of Research In Motion (RIM) Corporation.
HP Operations Manager for Windows® and HP Operations Manager for UNIX® are trademarks of Hewlett-Packard Development Company.
All other product names are the property of their respective trademark or service mark holders and are hereby acknowledged.
© 2007–2009 Hewlett-Packard Development Company, L.P.