HP Operations Smart Plug-in for BlackBerry® Enterprise Server Release Notes

for the HP Operations Manager for Windows®

Software version: 3.00

Publication date: June 2009

This document provides an overview of the changes made to HP Operations Smart Plug-in for BlackBerry® Enterprise Server 3.00. 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

In This Version

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 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 Notes

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

Installation Problems

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.

 

Known Problems, Limitations, and Workarounds

To display details about each documentation error, click the error summary. To hide details, click again.

ID 3376: Messages in the message browser indicate collection error: (06-01) or (78-53)

Description: When the metric collection takes long in a large environment, the next metic collection may already be starting when the first has not quite finished.
Possible Reason: The concurrency leads to a access conflict of the temporary metric files.
Workaround: Increase the interval of the following schedules:
  • BESPI_Collect_MsgAgent_2m
  • BESPI_Collect_Dispatcher_2m
  • BESPI_Collect_Router_2m
Open the policy in the policy editor and choose the "Schedule" tab. Increase the collection interval from 2 minutes to 4, 5 or 6 minutes. Save and close the policy.

Repeat the steps for all schedule policies listed above.

 

ID 3387: Some metric fail to be collected by the SNMP collector

Description: The following metric IDs fail to be collected using the metric collector: 108,109, 212, 213, 507, 508, 606, 607
Possible Reason: SNMP collector currently does not support to collect OID information from non-BES MIBs.
Workaround: Use the database data collection engine for alerting and reporting on the metrics.

 

ID 3404: Log and trace file size self-monitoring

Description: Currently the log and trace files of the BlackBerry SPI grow in the event of errors or warnings being logged to the files. File sizes are not monitored.
Possible Reason: SNMP collector currently does not support to collect OID information from non-BES MIBs.
Workaround: Ensure that errors forwarded to the console by the BESPI_opcmsg policy are taken care of. In this case the bespi_log.log file should not grow. If you have switched on tracing, be aware that it will consume large amount of you disk space. Ensure that you turn it off after finishing troubleshooting. It is not recommended to run tracing on a permanently.

 

ID 3413: bespi_start.bat does not Accept Brackets in Parameters / Import Certificate may fail

Description: When using the tool "Import Certificate" the full path to the Blackberry Administration Service keystore must be given as parameter. If the path contains unescaped brackets the call will fail.
Possible Reason: bespi_start.bat is currently not able to handle brackets in parameters properly.
Workaround: Escape the brackets putting a ^ in front of each one.
Example:
"c:\Program Files (x86)\Research In Motion\BlackBerry Enterprise Server\BAS\bin\web.keystore"
-->
"c:\Program Files ^(x86^)\Research In Motion\BlackBerry Enterprise Server\BAS\bin\web.keystore"

 

ID 3420: Thresholds are ordered incorrectly: some conditions are never reached

Description: Some thresholds are ordered incorrectly so that some conditions will never be checked:
The following policies are concerned:
  • BESPI_00205_DispSRPLinkLatency
  • BESPI_00602_RouterSRPLinkLatency
Possible Reason: When the second condition ist true, the first condition is true as well and will stop the policy evaluation.
Workaround: Open each of these policies in the policy editior and choose the "Threshold levels" tab. The conditions are ordered as Warning, Minor, Major.

Select the first condition (Warning) and move it down two steps to the end of the list. Select the first condition (Minor) and move it down one step to the middle of the list.

The conditions should now be ordered as Major, Minor, Warning. Save and close the policy.

Repeat the steps with the second policy.

 

ID 3422: Policy BESPI_00116_MsgAgtHAMode does not send messages

Description: In HA BES environments, there is no message from the SPI to inform the status change of a node from primary to standby.
Possible Reason: Policy BESPI_00116_MsgAgtHAMode uses a wrong threshold.
Workaround: Open the policy BESPI_00216_DispHAmode in the policy editor and choose the "Threshold levels"tab.

Change the threshold type to "Maximum" and the threshold limit to "1.9".

Save and close the policy.

 

ID 3423: Policy BESPI_00216_DispHAmode does not send messages

Description: In HA BES environments, there is no message from the SPI to inform the status change of a node from primary to standby.
Possible Reason: Policy BESPI_00216_DispHAmode uses a wrong threshold.
Workaround: Open the policy BESPI_00216_DispHAmode in the policy editor and choose the "Threshold levels" tab.

Change the threshold type to "Maximum" and the threshold limit to "1.9".

Save and close the policy.

 

ID 3425: Misleading messages in HA environments

Description: Log entries like the following are reported by the SPI self-monitoring policies:
  • bespi_snmpcoll.plc (11-06): Error encountered while fetching SNMP metrics
  • bespi_snmpcoll.plc (11-08): SNMP metric 101 failed with error 'Requested entries are empty or do not exist'
Possible Reason: The Metric Collector is not aware of the status of standby nodes.
Workaround: Acknowledge messages with object bespi_snmpcoll.plc for the standby node(s).

 

Verified Environments

HP OM management server

Windows 2003, 2008 with HP Operations Manager for Windows 8.10

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 2007.

Local Language Support

This version of the BlackBerry SPI is not localized in any languages. English is set as standard language for all installations.

Support

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:

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

Legal Notices

©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.

Trademark Notices

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.